[digikam] [Bug 372158] New: Allow changing metadata of multiple images at once
https://bugs.kde.org/show_bug.cgi?id=372158 Bug ID: 372158 Summary: Allow changing metadata of multiple images at once Product: digikam Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Metadata-Editor Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Maybe I am mistaken but as far as I can see, there is no possibility to batch edit metadata. You can edit metadata one by one in the metadata editor or you can apply a template in the BQM. Both are way too cumbersome for an easy task like adding a photographer name to the "Artist" field of several images. What I would like to see is the possibility to select multiple images and fire up the metadata editor to apply changes to all the selected images simultaneously. The case where images already contain differing metadata could be solved by either greying these conflicting fields out or adding a placeholder like "multiple values". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372159] New: Add option to run only the selected queue in BQM
https://bugs.kde.org/show_bug.cgi?id=372159 Bug ID: 372159 Summary: Add option to run only the selected queue in BQM Product: digikam Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: BatchQueueManager Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Every time one clicks the BQM button in the toolbar a new queue is created and not deleted after closing. So it quickly happens that several queues are open at the same time. In this position it is impossible run only the currently selected queue. One has to cumbersomely select every single queue except the desired one to delete them (adding a shortcut to the "del" key would be nice as well). I would propose to have two possibilities in place of the current "Run": "Run all" that does the same as it does now and "Run selected" to only run the currently selected queue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372164] New: Camera related photograph properties are unavailable (erroneously)
https://bugs.kde.org/show_bug.cgi?id=372164 Bug ID: 372164 Summary: Camera related photograph properties are unavailable (erroneously) Product: digikam Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 102082 --> https://bugs.kde.org/attachment.cgi?id=102082&action=edit Image to reproduce the problem With the pictures from my Panasonic Lumix TZ71 the camera make, model and lens are displayed as "unavailable" in the properties sidebar. With the exiv2 command line utility I can find this information. I did reread metadata from tags, that does not change the situation. I attached an example image. There is nothing related in stdout/stderr of digikam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372164] Camera related photograph properties are unavailable (erroneously)
https://bugs.kde.org/show_bug.cgi?id=372164 --- Comment #1 from Simon --- Correction: I also cannot find the lens property with exiv2 command line tool, so that is not a digikam issue. But not finding camera make and model seems to be. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372027] Adjust grouping behavior [patch]
https://bugs.kde.org/show_bug.cgi?id=372027 --- Comment #10 from Simon --- There are two bug reports (that I found) which are fixed by or related to this patch. As I don't know how the control mechanisms of bugs.kde.org work, I will just list them here: https://bugs.kde.org/show_bug.cgi?id=294579 https://bugs.kde.org/show_bug.cgi?id=307332 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372362] New: Build error due to private function
https://bugs.kde.org/show_bug.cgi?id=372362 Bug ID: 372362 Summary: Build error due to private function Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 102176 --> https://bugs.kde.org/attachment.cgi?id=102176&action=edit Error occuring during build When working on a patch I came across the error attached after merging the master branch. This error occurs on commit ba5d13b of master branch (clean, no patches). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372362] Build error due to private function
https://bugs.kde.org/show_bug.cgi?id=372362 --- Comment #2 from Simon --- Created attachment 102192 --> https://bugs.kde.org/attachment.cgi?id=102192&action=edit Fixes more of the same issues. This fixed this particular problem, but there were more. Now that I knew what it was about I corrected them myself. See attached patch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372362] Build error due to private function
https://bugs.kde.org/show_bug.cgi?id=372362 Simon changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366567] Allow choosing several duplicate results
https://bugs.kde.org/show_bug.cgi?id=366567 --- Comment #1 from Simon --- Created attachment 102207 --> https://bugs.kde.org/attachment.cgi?id=102207&action=edit Allow selection of multiple duplicates This patch adjusts the fuzzysearchview to handle multiple selected duplicates and extends SearchesJob to process all SAlbums, not just the first. The process of displaying albums stays the same, ImageAlbumModel::startListJob has only been adjusted to pass over all SAlbums instead of dropping all but the first. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372433] New: Reduce debug messages from databaseserver with internal mysql
https://bugs.kde.org/show_bug.cgi?id=372433 Bug ID: 372433 Summary: Reduce debug messages from databaseserver with internal mysql Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Database-Mysql Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 102208 --> https://bugs.kde.org/attachment.cgi?id=102208&action=edit reduce logging with internal mysql Every second the following is printed to the console when running with internal mysql backend: digikam.databaseserver: Waiting 1 seconds... This pollutes stdout a lot and makes it difficult to track important messages. This patch reduces this messages gradually to one message per minute. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372435] New: Use multiple cpu cores for duplicate search
https://bugs.kde.org/show_bug.cgi?id=372435 Bug ID: 372435 Summary: Use multiple cpu cores for duplicate search Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Searches-Fuzzy Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- When searching a big amount of pictures for duplicates the search takes a lot of time. One cpu core is at 100% the whole time, the others are almost idle. It would be great if all cpu cores were used to speed the search up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate
https://bugs.kde.org/show_bug.cgi?id=261417 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #10 from Simon --- I just discovered that there is also an issue with the duplicate count ordering. It is done lexicographically not mathematically (e.g. 10 is before 2). I thought this is probably related, if I should open a separate bug, please say so. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372713] New: Add options to unique modifier
https://bugs.kde.org/show_bug.cgi?id=372713 Bug ID: 372713 Summary: Add options to unique modifier Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: AdvancedRename Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 102351 --> https://bugs.kde.org/attachment.cgi?id=102351&action=edit Patch to add some functionality to the unique modifier My aim was to replace my current bash script for renaming my pictures. My renaming scheme is: *date*_*time**uniq*-*title*.*ext* where the uniq modifier is an alphabetic character in case of naming conflicts. So I implemented an option to user alphabetic characters instead of numbers and to use a custom separator (or none at all in my case). Unfortunately it turned out that there is one major problem with the entire advancedrename module: Renaming is done file by file, so a single renaming process can only be aware of already renamed files. Thus the first file that will be conflicting does not get the *uniq* attachment, e.g. two conflicting files are renamed: datetime-title.jpg datetime_1-title.jpg while the desirable thing to happen would be datetime_1-title.jpg datetime_2-title.jpg However I do not see how this could be easily achieved, so I will keep using my script. However this functionality might be useful to someone, so you might as well integrate it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 263949] digikam import obex over bluetooth
https://bugs.kde.org/show_bug.cgi?id=263949 --- Comment #12 from Simon --- Just make the appimage file executable and execute it. On 25/11/16 10:04, Philippe ROUBACH wrote: > https://bugs.kde.org/show_bug.cgi?id=263949 > > --- Comment #11 from Philippe ROUBACH --- > a tutorial about using this bundle? > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361848] When writing metadata to files is disabled, digikam still displays "Writing metadata to files"
https://bugs.kde.org/show_bug.cgi?id=361848 --- Comment #2 from Simon --- Hi Gilles, No, I do not see this behaviour any more. Sorry I completely forgot about this - thanks for the reminder. Cheers, Simon On 25/11/16 15:37, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=361848 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > What's about this file using digiKam AppImage bundle 5.4.0 pre release given > at > this url : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362023] Extremely slow metadata writing via maintenance
https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #17 from Simon --- Hi Gilles, This problem is still the same. I reduced it for me by using internal mysql database and preloading most of the database to memory. When testing with appimage, sqlite on system hd and data on separate hd (no ssl in my laptop :) ), now even the UI gets unresponsive during writing. Maybe it would be more efficient to remember which files were written and issue a rescan after writing of metadata is done? Generally the only issue I have with syncthing is its constant scanning of stuff on the HD. Whenever I start it causes tons of read access (to images, not database) producing command line output like "digikam.dimg***: JPEG file identified" and "digikam.metaengine: Orientation => Exif.Image.Orientation => 1", as if these files were new or modified (they are not). Cheers, Simon On 25/11/16 15:38, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=362023 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #16 from caulier.gil...@gmail.com --- > What's about this file using digiKam AppImage bundle 5.4.0 pre release given > at > this url : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373100] Deleting duplicate image in "Find duplicates" removes all other found duplicates
https://bugs.kde.org/show_bug.cgi?id=373100 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #3 from Simon --- Hi Frank, Why do you want to rescan on a delete? This is extremely time consuming when the duplicate search is done over a big amount of pictures. The expected result described by Kristian would be sane, i.e. just remove the item that is no longer a duplicate, but leave everything else (or even leave everything, having a "duplicate" group with just one picture is ok when the second picture was removed manually). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] New: Kwin freeze when playing, and in particular, when exiting videos
https://bugs.kde.org/show_bug.cgi?id=468280 Bug ID: 468280 Summary: Kwin freeze when playing, and in particular, when exiting videos Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: simon.adr...@ieee.org Target Milestone: --- Created attachment 157953 --> https://bugs.kde.org/attachment.cgi?id=157953&action=edit Output of journald after last crash, filtered for kwin messages. SUMMARY *** I am on a Lenovo X13 Gen 3 AMD running ArchLinux with open source video drivers only. When I watch a video on, for example, Youtube in full screen mode, the video begins to stutter quite from the beginning and it gets worse when I exit by double clicking. If I go to full screen again or I simply wait too long for exiting, it is too late and a total freeze happens. With VLC the situation is better, but typically, after like an 1h or so of watching a video, I end up with a freeze too. Going back and forth to full screen seems to cut down the time till the total freeze happens. *** STEPS TO REPRODUCE 1. Use a browser (tried both Chrome and Firefox) 2. Go to Youtube and start any video 3. Go back and forth to full screen OBSERVED RESULT After at most a few seconds the screen will freeze EXPECTED RESULT The video should play without any stuttering or screen freezing SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 The problem persists at least since version 5.27.0, but maybe even since 5.26.0 ADDITIONAL INFORMATION 1) Under Gnome everything works as expected, so I would exclude hardware problems 2) When I use additional external screens, the problem does *not* exist 3) I normally use 150% scaling throughout all my screens. Going back to 100% did not change the situation (I logged out and logged in again to make sure everything is consistent). 4) I found today this report: https://bugs.kde.org/show_bug.cgi?id=466238 where a similar freeze is describe, however, it occurs in this case only if multiple screens are used. Nonetheless, as suggested in this report, putting KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment fixes also my problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] Kwin freeze when playing, and in particular, when exiting videos
https://bugs.kde.org/show_bug.cgi?id=468280 --- Comment #1 from Simon --- Seems that I was too early to claim “KWIN_DRM_NO_DIRECT_SCANOUT=1” fixes the problem. Indeed, the stuttering is gone, but after 1-2 minutes into the video, I got a freeze. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] Kwin freezes when playing videos, typically, after going a couple of times forth and back to fullscreen
https://bugs.kde.org/show_bug.cgi?id=468280 Simon changed: What|Removed |Added Summary|Kwin freeze when playing, |Kwin freezes when playing |and in particular, when |videos, typically, after |exiting videos |going a couple of times ||forth and back to ||fullscreen -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] New: mremap() call not fully implemented fully and when attempting to resize the same address to a larger size the merman() call failed with FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 Bug ID: 470244 Summary: mremap() call not fully implemented fully and when attempting to resize the same address to a larger size the merman() call failed with FAILED. Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: victor.unitie...@icloud.com Target Milestone: --- Created attachment 159239 --> https://bugs.kde.org/attachment.cgi?id=159239&action=edit program to demonstrate the issue SUMMARY Under valgrind the call to mremap() failed with MAP_FAILED because the overloading valgrind mremap() doesn't implement increasing the size of the memory at the same address fully. I assume this is because the valgrind calls are more malloc/free oriented and assume its ok to change the address on a resize. STEPS TO REPRODUCE 1. Compile example program which uses mmap/mremap/munmap() calls 2. Run from command line with and without valgrind. OBSERVED RESULT # valgrind -v --tool=memcheck ./a.out init mmap: size:8192 grow mmap: oldaddr:0xac oldsize:8192 newsize:16384 Failed mremap mmmap.dat (12:Cannot allocate memory) zsh: abort (core dumped) valgrind -v --tool=memcheck ./a.out EXPECTED RESULT When running the program without valgrind the system allows for the base address to be expanded in size. # ./a.out init mmap: size:8192 grow mmap: oldaddr:0xac oldsize:8192 newsize:16384 mremap: addr:0xac size:16384 That's all folks SOFTWARE/OS VERSIONS Any Linux (I ran my tests on RHEL8.8) Kernel: Linux4.18.0-425.19.2.el8_7.x86_64 #1 SMP Fri Mar 17 01:52:38 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION The solution this code is a key component of a in memory database.. We do out own address management so as not to conflict with HI/LO memory allocation. Hence we start at address 0xACL. When we allocate mmaps we leave enough address space between the addresses so that mremap has enough contiguous memory to succeed with no conflict. If there is a work around for avoiding this issue that would be helpful, for instance can I disable the valgrind mmap support? We don't need it to investigate mmap() issues. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented fully and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added Summary|mremap() call not fully |mremap() call not fully |implemented fully and when |implemented fully and when |attempting to resize the|attempting to resize the |same address to a larger|same address to a larger |size the merman() call |size the mremap() call |failed with FAILED. |responded with MAP_FAILED. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added Summary|mremap() call not fully |mremap() call not fully |implemented fully and when |implemented and when |attempting to resize the|attempting to resize the |same address to a larger|same address to a larger |size the mremap() call |size the mremap() call |responded with MAP_FAILED. |responded with MAP_FAILED. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added CC||victor.unitie...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #2 from Simon --- Its a bug because its not fully implementing the mmap() functionality.. However yes we are using mmap/mremap so that we don't change the base address of the mmap(). That appears to be in conflict with valgrind which is implemented along the lines of expecting malloc/free block style functionally. mmap() can be used in that fashion but its not the only way... We implement out out versions of malloc/free to use the memory pools which we allocate in this fashion. Looking at the valgrind source code I can see it would be a lot of work to implement mmap() style blocks.. Which is why I'm looking for work arounds as valgrind is a valuable tool for finding memory/file handle leaks. We currently we are enable to do. I've added the system trace as an attachment -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #3 from Simon --- Created attachment 159240 --> https://bugs.kde.org/attachment.cgi?id=159240&action=edit --trace-syscalls trace output of valgrind valgrind -v --trace-syscalls=yes --tool=memcheck ./a.out ==157805== Memcheck, a memory error detector ==157805== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==157805== Using Valgrind-3.19.0-8d3c8034b8-20220411 and LibVEX; rerun with -h for copyright info ==157805== Command: ./a.out ==157805== --157805-- Valgrind options: --157805---v --157805----trace-syscalls=yes --157805----tool=memcheck --157805-- Contents of /proc/version: --157805-- Linux version 4.18.0-425.19.2.el8_7.x86_64 (mockbu...@x86-vm-09.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-16) (GCC)) #1 SMP Fri Mar 17 01:52:38 EDT 2023 --157805-- --157805-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-rdtscp-sse3-ssse3-avx --157805-- Page sizes: currently 4096, max supported 4096 --157805-- Valgrind library directory: /usr/libexec/valgrind --157805-- Reading syms from /home/atcore/tmp/a.out --157805-- Reading syms from /usr/lib64/ld-2.28.so --157805-- Warning: cross-CU LIMITATION: some inlined fn names --157805-- might be shown as UnknownInlinedFun --157805-- Reading syms from /usr/libexec/valgrind/memcheck-amd64-linux --157805--object doesn't have a symbol table --157805--object doesn't have a dynamic symbol table --157805-- Scheduler: using generic scheduler lock implementation. --157805-- Reading suppressions file: /usr/libexec/valgrind/default.supp ==157805== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-157805-by-atcore-on-mdev ==157805== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-157805-by-atcore-on-mdev ==157805== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-157805-by-atcore-on-mdev ==157805== ==157805== TO CONTROL THIS PROCESS USING vgdb (which you probably ==157805== don't want to do, unless you know exactly what you're doing, ==157805== or are doing some strange experiment): ==157805== /usr/libexec/valgrind/../../bin/vgdb --pid=157805 ...command... ==157805== ==157805== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==157805== /path/to/gdb ./a.out ==157805== and then give GDB the following command ==157805== target remote | /usr/libexec/valgrind/../../bin/vgdb --pid=157805 ==157805== --pid is optional if only one valgrind process is running ==157805== SYSCALL[157805,1](12) sys_brk ( 0x0 ) --> [pre-success] Success(0x4231000) SYSCALL[157805,1](158) arch_prctl ( 12289, 1fff20 ) --> [pre-fail] Failure(0x16) --157805-- REDIR: 0x4005820 (ld-linux-x86-64.so.2:strlen) redirected to 0x580d0a02 (???) SYSCALL[157805,1](63) sys_newuname ( 0x1ffefffc00 )[sync] --> Success(0x0) --157805-- REDIR: 0x40055f0 (ld-linux-x86-64.so.2:index) redirected to 0x580d0a1c (???) SYSCALL[157805,1](257) sys_openat ( 4294967196, 0x4230a50(/usr/libexec/valgrind/vgpreload_core-amd64-linux.so), 524288 ) --> [async] ... SYSCALL[157805,1](257) ... [async] --> Success(0x3) SYSCALL[157805,1](0) sys_read ( 3, 0x1ffeffe818, 832 ) --> [async] ... SYSCALL[157805,1](0) ... [async] --> Success(0x340) SYSCALL[157805,1](8) sys_lseek ( 3, 2144, 0 )[sync] --> Success(0x860) SYSCALL[157805,1](0) sys_read ( 3, 0x1ffeffe6f0, 32 ) --> [async] ... SYSCALL[157805,1](0) ... [async] --> Success(0x20) SYSCALL[157805,1](5) sys_newfstat ( 3, 0x1ffeffe6a0 )[sync] --> Success(0x0) SYSCALL[157805,1](8) sys_lseek ( 3, 2144, 0 )[sync] --> Success(0x860) SYSCALL[157805,1](0) sys_read ( 3, 0x1ffeffe3f0, 32 ) --> [async] ... SYSCALL[157805,1](0) ... [async] --> Success(0x20) SYSCALL[157805,1](9) sys_mmap ( 0x0, 2101304, 5, 2050, 3, 0 ) --> [pre-success] Success(0x4a31000) SYSCALL[157805,1](10) sys_mprotect ( 0x4a32000, 2093056, 0 )[sync] --> Success(0x0) SYSCALL[157805,1](9) sys_mmap ( 0x4c31000, 8192, 3, 2066, 3, 0 )--157805-- Reading syms from /usr/libexec/valgrind/vgpreload_core-amd64-linux.so --> [pre-success] Success(0x4c31000) SYSCALL[157805,1](3) sys_close ( 3 )[sync] --> Success(0x0) SYSCALL[157805,1](257) sys_openat ( 4294967196, 0x4230fb0(/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so), 524288 ) --> [async] ... SYSCALL[157805,1](257) ... [async] --> Success(0x3) SYSCALL[157805,1](0) sys_read ( 3, 0x1ffeffe818, 832 ) --> [async] ... SYSCALL[157805,1](0) ... [async] --> Success(0x340) SYSCALL[157805,1](8) sys_lseek ( 3, 80856, 0 )[sync] --> Success(0x13bd8) SYSCALL[157805,1](0) sys_read ( 3, 0x1ffeffe6f0, 32 ) --> [async] ... SYSCALL[157805,1](0) ... [async] --> Success(0x20) SYSCALL[157805,1](5) sys_newfstat ( 3, 0x1ffeffe6a0 )[sync] --> Success(0x0) SYSCALL[157805,1](9) sys_mmap ( 0x0, 8192, 3, 34, 4294967295, 0 ) --> [pre-success] Success(0x402e000) SYSCALL[157805,1](8) sys_lseek ( 3, 80856, 0 )[sync] --> Success(0x13bd8) SYS
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #4 from Simon --- Created attachment 159241 --> https://bugs.kde.org/attachment.cgi?id=159241&action=edit strace of the example programs running without issues -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #6 from Simon --- Created attachment 159243 --> https://bugs.kde.org/attachment.cgi?id=159243&action=edit Additional output from debug enabled valgrind mremap() overload The additional output from the valgrind overload of mremap(). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #7 from Simon --- I'd already tried outputting those segments before but I'm not sure why they failed.. My guess was that valgrind had used some of the space itself and was blocking the expansion of the existing memory segment. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 --- Comment #8 from Simon --- It is a strange one.. The segment dump I attached shows nothing in the memory ahead.. But code walking through the do_mremap() function its not obvious to me why its returning MAP_FAILED. Something Subtle no doubt.. :-) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470244] mremap() call not fully implemented and when attempting to resize the same address to a larger size the mremap() call responded with MAP_FAILED.
https://bugs.kde.org/show_bug.cgi?id=470244 Simon changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Simon --- Brillant.. We have lots of smiling developers here now they can find memory leaks again :-) Yes that patch works.. Cheers.. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 469209] New: Session Verification screen is broken
https://bugs.kde.org/show_bug.cgi?id=469209 Bug ID: 469209 Summary: Session Verification screen is broken Classification: Applications Product: NeoChat Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: doc...@tutanota.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 158577 --> https://bugs.kde.org/attachment.cgi?id=158577&action=edit Observed result SUMMARY The Session Verification screen has the emojis overlapping, which makes it pretty much useless STEPS TO REPRODUCE 1. Verify the NeoChat session from another session with emojis OBSERVED RESULT Overlapping emojis EXPECTED RESULT Non-overlapping emojis SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.13-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 469211] New: NeoChat Session Verification buttons don't do anything
https://bugs.kde.org/show_bug.cgi?id=469211 Bug ID: 469211 Summary: NeoChat Session Verification buttons don't do anything Classification: Applications Product: NeoChat Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: doc...@tutanota.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 158578 --> https://bugs.kde.org/attachment.cgi?id=158578&action=edit Observed result SUMMARY STEPS TO REPRODUCE 1. Verify the NeoChat session from another session with emojis OBSERVED RESULT The buttons don't do anything EXPECTED RESULT The buttons can be used to verify the NeoChat session SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.13-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] Kwin freezes when playing videos, typically, after going a couple of times forth and back to fullscreen
https://bugs.kde.org/show_bug.cgi?id=468280 --- Comment #2 from Simon --- Addendum: Also KWin in X11 is doing fine. So there is some issue with KWin + Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] Kwin freezes when playing videos, typically, after going a couple of times forth and back to fullscreen
https://bugs.kde.org/show_bug.cgi?id=468280 --- Comment #3 from Simon --- Another update: 1) I wrote that the problem also persists with 100 % scaling. This is, at least now, no longer true. The problem does not exist with normal scaling, but only with fractional scaling. 2) It seems to be related to adaptive sync. I had used "automatic" as option, which allowed normal desktop usage, but made the problems with full screen videos. If I select "Always", my desktop basically freezes (at least, when there are some applications open). Deactivating "adaptive sync" seems to fix my problem. I need to do some more long term tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468280] Kwin: Fractional scaling + adaptive sync @ automatic -> freezes when playing full screen videos
https://bugs.kde.org/show_bug.cgi?id=468280 Simon changed: What|Removed |Added Summary|Kwin freezes when playing |Kwin: Fractional scaling + |videos, typically, after|adaptive sync @ automatic |going a couple of times |-> freezes when playing |forth and back to |full screen videos |fullscreen | -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 459946] New: can't connect to paired audio device
https://bugs.kde.org/show_bug.cgi?id=459946 Bug ID: 459946 Summary: can't connect to paired audio device Classification: Plasma Product: Bluedevil Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: simonmik2...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY when trying to connect to a paired device, it displays "connection to device failed" STEPS TO REPRODUCE 1. pair device 2. successfully connect to device 3. restart 4. try to connect to device OBSERVED RESULT it fails, and says "connection to device failed" you have to unpair and pair the device again for it to connect. after a restart it fails again EXPECTED RESULT the audio device(earbuds) successfully connects SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION INXI: System: Host: simon-m-zephyrusg14-ga402rkga402rk Kernel: 6.0.0-1-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.25.5 Distro: Manjaro Linux Machine: Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA402RK_GA402RK v: 1.0 serial: Mobo: ASUSTeK model: GA402RK v: 1.0 serial: UEFI: American Megatrends LLC. v: GA402RK.315 date: 09/21/2022 Battery: ID-1: BAT0 charge: 39.2 Wh (59.9%) condition: 65.4/76.0 Wh (86.0%) volts: 15.9 min: 15.9 CPU: Info: 8-core model: AMD Ryzen 9 6900HS with Radeon Graphics bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 1813 min/max: 1600/4934 cores: 1: 3300 2: 1600 3: 1600 4: 1600 5: 1600 6: 1395 7: 1822 8: 1600 9: 3300 10: 1600 11: 1600 12: 1600 13: 1600 14: 1600 15: 1600 16: 1600 Graphics: Device-1: AMD Navi 23 [Radeon RX 6650 XT] driver: amdgpu v: kernel Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel Device-3: Quanta USB2.0 HD UVC WebCam type: USB driver: uvcvideo Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting,radeon gpu: amdgpu,amdgpu resolution: 1707x1067 OpenGL: renderer: AMD Radeon RX 6800S (dimgrey_cavefish LLVM 14.0.6 DRM 3.48 6.0.0-1-MANJARO) v: 4.6 Mesa 22.1.7 Audio: Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.0.0-1-MANJARO running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.57 running: yes Network: Device-1: MEDIATEK driver: mt7921e IF: wlp5s0 state: up mac: b4:8c:9d:5c:77:db Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb Report: rfkill ID: hci0 state: up address: see --recommends Drives: Local Storage: total: 1.89 TiB used: 118.16 GiB (6.1%) ID-1: /dev/mmcblk0 model: SN32G size: 29.72 GiB ID-2: /dev/nvme0n1 vendor: Toshiba model: N/A size: 1.86 TiB Partition: ID-1: / size: 891.53 GiB used: 48.19 GiB (5.4%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: /boot/efi size: 256 MiB used: 67.8 MiB (26.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 93.13 GiB used: 69.9 GiB (75.1%) fs: ntfs dev: /dev/nvme0n1p6 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 70.5 C mobo: N/A Fan Speeds (RPM): cpu: 0 GPU: device: amdgpu temp: 66.0 C fan: 0 device: amdgpu temp: 64.0 C Info: Processes: 364 Uptime: 1h 4m Memory: 30.59 GiB used: 4.76 GiB (15.6%) Shell: Bash inxi: 3.3.21 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459953] New: laptop fans does not turn on
https://bugs.kde.org/show_bug.cgi?id=459953 Bug ID: 459953 Summary: laptop fans does not turn on Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: simonmik2...@gmail.com Target Milestone: --- SUMMARY the fans on my laptop doesn't turn on, resulting in extreme overheating. though in the bootloader the fans work fine, *as far as i can tell*. and sometimes the fans keep spinning at the same rpm as in the bootloader, and continues into infinfity until the laptop turns off (and on windows they do turn on and work as expected) STEPS TO REPRODUCE 1. turn on laptop 2. bootloader(fans work*) 3. sddm ect. (fans doesn't work) OBSERVED RESULT fans won't turn on EXPECTED RESULT fans turn on SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 kernel: 6.0.0-1MANJARO ADDITIONAL INFORMATION INXI: System: Host: simon-m-zephyrusg14-ga402rkga402rk Kernel: 6.0.0-1-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.25.5 Distro: Manjaro Linux Machine: Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA402RK_GA402RK v: 1.0 serial: Mobo: ASUSTeK model: GA402RK v: 1.0 serial: UEFI: American Megatrends LLC. v: GA402RK.315 date: 09/21/2022 Battery: ID-1: BAT0 charge: 22.6 Wh (34.6%) condition: 65.4/76.0 Wh (86.0%) volts: 15.9 min: 15.9 CPU: Info: 8-core model: AMD Ryzen 9 6900HS with Radeon Graphics bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 1765 min/max: 1600/4934 cores: 1: 1600 2: 1352 3: 1337 4: 1600 5: 1600 6: 1600 7: 1600 8: 1351 9: 3300 10: 1600 11: 1600 12: 1600 13: 1600 14: 3300 15: 1600 16: 1600 Graphics: Device-1: AMD Navi 23 [Radeon RX 6650 XT] driver: amdgpu v: kernel Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel Device-3: Quanta USB2.0 HD UVC WebCam type: USB driver: uvcvideo Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting,radeon gpu: amdgpu,amdgpu resolution: 1707x1067 OpenGL: renderer: AMD Radeon RX 6800S (dimgrey_cavefish LLVM 14.0.6 DRM 3.48 6.0.0-1-MANJARO) v: 4.6 Mesa 22.1.7 Audio: Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.0.0-1-MANJARO running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.57 running: yes Network: Device-1: MEDIATEK driver: mt7921e IF: wlp5s0 state: up mac: b4:8c:9d:5c:77:db Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb Report: rfkill ID: hci0 state: up address: see --recommends Drives: Local Storage: total: 1.89 TiB used: 118.4 GiB (6.1%) ID-1: /dev/mmcblk0 model: SN32G size: 29.72 GiB ID-2: /dev/nvme0n1 vendor: Toshiba model: N/A size: 1.86 TiB Partition: ID-1: / size: 891.53 GiB used: 48.44 GiB (5.4%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: /boot/efi size: 256 MiB used: 67.8 MiB (26.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 93.13 GiB used: 69.9 GiB (75.1%) fs: ntfs dev: /dev/nvme0n1p6 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 51.8 C mobo: N/A Fan Speeds (RPM): cpu: 2300 GPU: device: amdgpu temp: 44.0 C device: amdgpu temp: 46.0 C fan: 0 Info: Processes: 367 Uptime: 2h 18m Memory: 30.59 GiB used: 4.59 GiB (15.0%) Shell: Bash inxi: 3.3.21 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487338] Possible regression: Floating point exception
https://bugs.kde.org/show_bug.cgi?id=487338
simon changed:
What|Removed |Added
CC||mappe...@outlook.com
--- Comment #9 from simon ---
I can also reproduce this.
OS: Gentoo Linux amd64
kdiff3 version: 1.11.1
KDE Frameworks Version: 5.116.0
Qt Version: 5.15.14
Graphics Platform: Wayland
Thread 1 "kdiff3" received signal SIGFPE, Arithmetic exception.
0x555ef793 in getBestFirstLine (line=..., nofLines=nofLines@entry=2,
firstLine=..., visibleLines=visibleLines@entry=0)
at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/difftextwindow.cpp:589
589 newFirstLine = std::max(0, line - (visibleLines * numberPages)
/ 3);
(gdb) p visibleLines
$1 = 0
(gdb) list
584 if(nofLines < visibleLines)
585 newFirstLine = std::max(0, (LineType)std::ceil(line -
(visibleLines - nofLines) / 2));
586 else
587 {
588 qint32 numberPages = floor(nofLines / visibleLines);
589 newFirstLine = std::max(0, line - (visibleLines * numberPages)
/ 3);
590 }
591 return newFirstLine;
592 }
593
(gdb) bt
#0 0x555ef793 in getBestFirstLine (line=...,
nofLines=nofLines@entry=2, firstLine=...,
visibleLines=visibleLines@entry=0) at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/difftextwindow.cpp:589
#1 0x555ef8e0 in DiffTextWindow::setFastSelectorRange
(this=0x55cbc1a0, line1=,
nofLines=) at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/difftextwindow.cpp:600
#2 0x768ae4c6 in void doActivate(QObject*, int, void**) () from
/usr/lib64/libQt5Core.so.5
#3 0x5559afd6 in MergeResultWindow::setFastSelectorRange
(this=this@entry=0x55b97930, _t1=..., _t2=)
at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1_build/src/kdiff3_autogen/EWIEGA46WW/moc_mergeresultwindow.cpp:476
#4 0x5561ca12 in MergeResultWindow::setFastSelector
(this=0x55b97930, i=...)
at /usr/include/boost/safe_numerics/checked_result.hpp:26
#5 0x5561e233 in MergeResultWindow::slotGoTop (this=0x55b97930)
at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/mergeresultwindow.cpp:677
#6 MergeResultWindow::merge (this=0x55b97930, bAutoSolve=true,
defaultSelector=, bConflictsOnly=false,
bWhiteSpaceOnly=) at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/mergeresultwindow.cpp:416
#7 0x5561e5cc in MergeResultWindow::init (this=0x55b97930,
pLineDataA=..., sizeA=..., pLineDataB=..., sizeB=...,
pLineDataC=..., sizeC=..., pDiff3LineList=0x55748450,
pTotalDiffStatus=0x55748f60, bAutoSolve=true)
at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/mergeresultwindow.cpp:132
#8 0x555dca66 in KDiff3App::mainInit (this=this@entry=0x55748000,
pTotalDiffStatus=0x55748f60, inFlags=...,
inFlags@entry=...) at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/pdiff.cpp:380
#9 0x555acf02 in KDiff3App::doFileCompare (this=0x55748000) at
/usr/include/qt5/QtCore/qflags.h:121
#10 KDiff3App::completeInit (this=0x55748000, fn1=..., fn2=..., fn3=...)
at /usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/kdiff3.cpp:493
#11 0x555a39f0 in KDiff3Shell::KDiff3Shell (this=0x55738ba0,
fn1=..., fn2=..., fn3=..., __in_chrg=,
__vtt_parm=) at
/usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/kdiff3_shell.cpp:39
#12 0x555a1bb0 in operator() (__closure=0x557432d0)
at /usr/src/debug/kde-misc/kdiff3-1.11.1/kdiff3-1.11.1/src/main.cpp:195
#13 QtPrivate::FunctorCall, QtPrivate::List<>, void,
main(qint32, char**):: >::call (
arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#14 QtPrivate::Functor,
0>::call, void> (arg=, f=...)
at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#15 QtPrivate::QFunctorSlotObject, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x557432c0, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#16 0x768a4d7e in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#17 0x772fa1fe in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#18 0x7687aee8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#19 0x7687e3c3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
from /usr/lib64/libQt5Core.so.5
#20 0x768cc473 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib64/libQt5Core.so.5
#21 0x75521ff2 in g_main_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x755251a7 in g_main_context_iterate_unlocked.isra () from
/usr/lib64/libglib-2.0.so.0
#23 0x755257cc in
[kwin] [Bug 483112] New: Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 Bug ID: 483112 Summary: Pixelated font with fractional scaling Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: simon.adr...@ieee.org Target Milestone: --- Created attachment 166870 --> https://bugs.kde.org/attachment.cgi?id=166870&action=edit KCM using wp-fractional-scale SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I just upgraded from Plasma 5.27 to Plasma 6.0.1 on ArchLinux. I am on Wayland (also on 5.27) and using fractional scaling (150%). On Plasma 6.0.1, the fonts look weird (using Noto Sans at 10 pt): attachment wp-fractional-scale-v1.png is a screenshot of kcm, which shows, for example, that the horizontal line of the letter 'e' (see the search field of kcm) is roughly twice as large as the top or bottom of the letter 'e', which looks weird to me. Or consider the letter 'g' in the word 'Hintergrunddienst' (below 'Sitzung' in the tree menu), where the bottom part of 'g' is too thin. In trying to understand, what my be the cause of my problem, I came across https://bugreports.qt.io/browse/QTBUG-113574 Since I do have the problem with the WebEngine too, I set the environment variable QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor Now not only the WebEngine problem is solved, but also kcm looks like before again. From this, I conclude that before upgrading, the wp-fractional-scale-v1-extension was not used. I am wondering if this is a won't fix. If so, I am a bit underwhelmed with the performance of 'wp-fractional-scale-v1'. Or is there another option that I need to set? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #1 from Simon --- Created attachment 166871 --> https://bugs.kde.org/attachment.cgi?id=166871&action=edit KCM using QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #2 from Simon --- Created attachment 166872 --> https://bugs.kde.org/attachment.cgi?id=166872&action=edit Zoom of letter 'e' using wp-fractional-scale -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #3 from Simon --- Created attachment 166873 --> https://bugs.kde.org/attachment.cgi?id=166873&action=edit Zoom of letter 'g' using wp-fractional-scale -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #4 from Simon --- Created attachment 166874 --> https://bugs.kde.org/attachment.cgi?id=166874&action=edit Zoom of letter 'e' using QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #5 from Simon --- Created attachment 166875 --> https://bugs.kde.org/attachment.cgi?id=166875&action=edit Zoom of letter 'g' using QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483112] Pixelated font with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=483112 --- Comment #6 from Simon --- Potentially a duplication of https://bugs.kde.org/show_bug.cgi?id=481233 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474888] Signing requires (empty) password in document that has password-restriction for modification
https://bugs.kde.org/show_bug.cgi?id=474888
Simon changed:
What|Removed |Added
CC||simon.praetorius@tu-dresden
||.de
Status|RESOLVED|REOPENED
Resolution|FIXED |---
--- Comment #7 from Simon ---
The situation in 24.02.2 seems to be worse, i.e. one cannot sign a document
anymore. The password dialog pops up but now an empty string is not allowed
anymore and one has no way of signing the document ("cancel"/close the dialog
will cancel the signing process). This is tested with the attached document and
also other documents with a signature field.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 481233] System settings sidebar words/fonts gets slightly "trimmed" on fractional scaling
https://bugs.kde.org/show_bug.cgi?id=481233 Simon changed: What|Removed |Added CC||simon.adr...@ieee.org --- Comment #2 from Simon --- I think I observe a similar issue: https://bugs.kde.org/show_bug.cgi?id=483112 Setting QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor seems to go back to Plasma 5.27 behavior. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 483482] New: Latex export file is empty.
https://bugs.kde.org/show_bug.cgi?id=483482 Bug ID: 483482 Summary: Latex export file is empty. Classification: Applications Product: cantor Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: si...@i2cchip.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start from command line to see messages. 2. Any content e.g Octave, scilab 3. File->Export to Latex OBSERVED RESULT Latex file is empty. exporting to Latex: "/home/simon/play.tex" Error XTSE0010 in file:///usr/share/cantor/xslt/latex.xsl, at line 1, column 82: In a simplified stylesheet module, attribute version must be present. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 484027] New: Shortcut keys not indicated in menus (missing underlines)
https://bugs.kde.org/show_bug.cgi?id=484027 Bug ID: 484027 Summary: Shortcut keys not indicated in menus (missing underlines) Classification: Applications Product: cantor Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: si...@i2cchip.com Target Milestone: --- SUMMARY I was going to report that there are not keyboard shortcuts in menus, but it appears that there are. The letter shortcut keys are not underlined as expected, so one does not know what they are or that they even exist. STEPS TO REPRODUCE 1. Press "alt-W T" A new text entry appears, so "T" shortcut exists 2. In menu item "Insert Text Entry" , "T" is not underlined as it should be OBSERVED RESULT No letters are underlined in menu items EXPECTED RESULT Every menu item should have an underlined shortcut SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 419713] KOrganizer deletes events in calendar without prompting
https://bugs.kde.org/show_bug.cgi?id=419713 simon changed: What|Removed |Added CC||sh+...@aboutsource.net --- Comment #6 from simon --- Is there anything we can do, to speed this along? This bug makes the Google Calendar Integration unusable.. At worst, it freezes the whole shell, at best it "just" floods my screen with 100s of the described error messages. For anybody experiencing the same issue and their system freezes: i had some luck killing `korgac` in a different tty (via Ctrl+Alt+F2), switching back to plasma and then disabling compositing (via Alt+Shift+F12), which unfroze plasma and allowed me to dismiss all of the error windows.. Especially helpful, when you're in a video call and don't want to hard reset your computer.. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466554] [Usability] Autocomplete a persons name in the text box when tagging people
https://bugs.kde.org/show_bug.cgi?id=466554 Simon changed: What|Removed |Added CC||iverson.digi...@mailgw.com Version|7.10.0 |8.2.0 --- Comment #2 from Simon --- Name autocomplete causes immediate crash in preview mode when tagging faces. However the dropdown is functional in preview mode. Any keyboard input causes a crash. N.B. This doesn't occur in thumbnail mode, which appears to be fine. This occured in 8.1 as well (both on Windows 10) and it feels like a GUI problem as if the autocomplete list is unpopulated? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473782] New: The Symmetry line and manipulator is always hidden in 5.2 Beta 2
https://bugs.kde.org/show_bug.cgi?id=473782 Bug ID: 473782 Summary: The Symmetry line and manipulator is always hidden in 5.2 Beta 2 Classification: Applications Product: krita Version: 5.2.0-beta2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: thegrayp...@gmail.com Target Milestone: --- SUMMARY If you activate Symmetry (X or Y) the line is always hidden and activating/deactivating the hide symmetry line does not change this. STEPS TO REPRODUCE 1. Open Krita Beta 5.2.0 Beta 2 2. Create a new document. 3. Select brush 4. Activate Symmetry either X or Y or both. OBSERVED RESULT Observe the issue: The symmetry line is not shown including the manipulater is missing for moving the symmetry line. EXPECTED RESULT You should see the symmetry line and handing ui if you do not have it hidden. SOFTWARE/OS VERSIONS Windows: 11 lates version macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Running on Surface Laptop Studio with both Intel and Geforce GPU. Latest drivers and Windows. Running on the Dark Orange contrast Theme but it happens with any theme. Slightly customized UI but no plugins or anything installed beside custom brushes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473782] The Symmetry line and manipulator is always hidden in 5.2 Beta 2
https://bugs.kde.org/show_bug.cgi?id=473782 --- Comment #6 from Simon --- (In reply to Alvin Wong from comment #2) > I managed to reproduce this with Intel graphics on Windows and renderer set > to OpenGL. This is indeed caused by some code changes between 5.1 and 5.2 > and will probably be fixed soon™. > > Regardless, we do not recommend using the OpenGL renderer with Intel > graphics so I strongly recommend you to either change the renderer to ANGLE, > or to ensure that Krita always runs with Nvidia GPU since you have one > (should be configurable from Windows settings). > > (For tracking, probably caused by > https://invent.kde.org/graphics/krita/-/merge_requests/1726) I can confirm that I was running OpenGL for some reasons... (Might be some testing I was doing back a while ago) If I switch to DX it works as intended on my system. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 461176] Applications don't prompt to save unsaved work when logging out on Wayland
https://bugs.kde.org/show_bug.cgi?id=461176 Simon changed: What|Removed |Added CC||freisi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Simon changed: What|Removed |Added CC||freisi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Simon changed: What|Removed |Added Platform|Manjaro |Archlinux Packages CC||simon.adr...@ieee.org --- Comment #3 from Simon --- Same issue on Arch. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 489804] New: Automatic export/save of backend script file
https://bugs.kde.org/show_bug.cgi?id=489804 Bug ID: 489804 Summary: Automatic export/save of backend script file Classification: Applications Product: cantor Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: si...@i2cchip.com Target Milestone: --- SUMMARY I use Cantor to make worksheets which are then included in Latex documents. It would suit me well to have Cantor export/save the (octave) script every time that it saves the CWS file, so that I can run them directly from octave. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 489805] New: Commandline Operation
https://bugs.kde.org/show_bug.cgi?id=489805 Bug ID: 489805 Summary: Commandline Operation Classification: Applications Product: cantor Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: si...@i2cchip.com Target Milestone: --- Cantor lacks any commandline functions beyond file load. I need to be able to - run the (octave) scripts from the commandline "-run" - export the pdf from the commandline "-exportpdf" Also there is: - saveas scriptfile "-exportscript" - export Latex "-exportlatex" and potentially useful is "insert command entry" to put a line at the top of the script file -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 489804] Automatic export/save of backend script file
https://bugs.kde.org/show_bug.cgi?id=489804 --- Comment #2 from si...@i2cchip.com --- Since my main objective is using them automatically, https://bugs.kde.org/show_bug.cgi?id=489805 My actual need would be met by a commandline commands to exportscript, runscript, exportpdf. //-- I realise that Cantor can't import .m files, so what I had in mind probably isn't workable, as editing the external .m file would leave it orphaned. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 489805] Commandline Operation
https://bugs.kde.org/show_bug.cgi?id=489805 --- Comment #1 from si...@i2cchip.com --- Since more than one operation is likely (i.e. load, exportscript, run script, exportpdf) , it should just run multiple operations sequentially as they occur on the commandline -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 Simon changed: What|Removed |Added CC||dragonc...@gmail.com --- Comment #97 from Simon --- This bug is rapidly coming up on its 24th birthday, and with more and more distros ditching X11 and this bug still being a dealbreaker for a lot of people (myself included) It would be nice to know if there was a roadmap or a fix or something in the works for this issue? -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 414047] Apper crashes when applying updates
https://bugs.kde.org/show_bug.cgi?id=414047 Simon changed: What|Removed |Added CC||n...@simonson.se -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 414047] Apper crashes when applying updates
https://bugs.kde.org/show_bug.cgi?id=414047 --- Comment #10 from Simon --- Created attachment 136345 --> https://bugs.kde.org/attachment.cgi?id=136345&action=edit New crash information added by DrKonqi apper (1.0.0) using Qt 5.15.2 - What I was doing when the application crashed: I updated my installation by: "dnf upgrade --refresh" and then started apper where the pacckages I just had upgraded were listed under "updates". I then pressed "Check for new Updates" and when Apper had finished loading the cashes it's window closed immideately. -- Backtrace (Reduced): #4 0x7f0e3e6caa19 in QHashData::nextNode(QHashData::Node*) () from /lib64/libQt5Core.so.5 #5 0x7f0e4018087a in QHash::erase(QHash::const_iterator) () from /usr/lib64/apper/libapper_private.so #6 0x7f0e4017ce4b in PackageModel::clearSelectedNotPresent() () from /usr/lib64/apper/libapper_private.so #7 0x562e8d862ace in Updater::getUpdatesFinished() () #8 0x7f0e3e85c386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 Simon changed: What|Removed |Added CC||si...@ergotech.com --- Comment #4 from Simon --- Could those who are affected by this please do the following: After experiencing the error, run the command: qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp isMounted And report whether that returns true or false, then run qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp mountAndWait Wait for the command to return, then check if browsing the phone through Dolphin works as expected In the above commands, needs to be replaced with your actual device ID. This can be checked by running `kdeconnect-cli --list-devices` If you don't have qdbus installed, any other dbus-poking program is equally useful. The GUI programs qdbus-qt5 and d-feet are nice too. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #7 from Simon --- Well darn. I thought for sure that was the problem. If I think of something else to try, I will post again. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 400326] New: Knotes Crash
https://bugs.kde.org/show_bug.cgi?id=400326 Bug ID: 400326 Summary: Knotes Crash Product: knotes Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: simon.par...@mailbox.org CC: myr...@kde.org Target Milestone: --- Application: knotes (5.2.3) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-8-amd64 x86_64 Distribution: Debian GNU/Linux 9.5 (stretch) -- Information about the crash: I start Knotes to test it and then want to delete the note, after deleting the note, Knotes crash. -- Backtrace: Application: KNotes (knotes), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7fdfa3d940 (LWP 6760))] Thread 9 (Thread 0x7f7fc5e00700 (LWP 6775)): #0 0x7f7ff812667d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7ff00489f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7ff0048b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7ff8c5206b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7ff8bfb9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7ff8a290f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7ff8a2dda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7ff1d5c494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7ff812facf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7f7fc6601700 (LWP 6773)): #0 0x7f7ff812667d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7ff00489f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7ff0048b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7ff8c5206b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7ff8bfb9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7ff8a290f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7ff8a2dda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7ff1d5c494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7ff812facf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f7fc6f02700 (LWP 6772)): #0 0x7f7ff1d6215f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7ff519d2c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f7ff519d309 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f7ff1d5c494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f7ff812facf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f7fd5dec700 (LWP 6768)): #0 0x7f7ff008e0e0 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7ff0048404 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7ff0048994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7ff0048b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7ff8c5206b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7ff8bfb9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7ff8a290f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7ff8a2dda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7ff1d5c494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f7ff812facf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f7fd65ed700 (LWP 6766)): #0 0x7f7ff812667d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7ff00489f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7ff0048b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7ff8c5206b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7ff8bfb9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7ff8a290f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7ff8a2dda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7ff1d5c494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7ff812facf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f7fd6dee700 (LWP 6764)): #0 0x7f
[kdeconnect] [Bug 400344] New: Notifications Plugin Disable All Does Nothing
https://bugs.kde.org/show_bug.cgi?id=400344 Bug ID: 400344 Summary: Notifications Plugin Disable All Does Nothing Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: si...@ergotech.com CC: si...@ergotech.com Target Milestone: --- Flags: corner_case+ SUMMARY The notifications plugin All setting appears to work for enabling notifications for all apps, but does not work to disable all notifications STEPS TO REPRODUCE Case 1: Disable all apps 1. Open notifications plugin settings 2. Double-click "All" checkbox - One click to enable all, one click to disable all 3. Close notifications settings Case 2: Enable a few apps which were previously enabled 1. Open notifications plugin settings 2. Double-click "All" checkbox - One click to enable all, one click to disable all 3. Scroll through the list and enable some apps which were previously *enabled* 4. Close notifications settings Case 3: Enable a few apps which were previously disabled 1. Open notifications plugin settings 2. Double-click "All" checkbox - One click to enable all, one click to disable all 3. Scroll through the list and enable some apps which were previously *disabled* 4. Close notifications settings OBSERVED RESULT Case 1: On reopening the notifications plugin settings, nothing has changed Case 2: On reopening the notifications plugin settings, nothing has changed Case 3: Any apps which were previously disabled and were enabled after de-selecting all are now enabled, all other apps remain untouched EXPECTED RESULT Case 1: All apps should be disabled Case 2: All apps except those selected should be disabled Case 3: All apps except those selected should be disabled SOFTWARE VERSIONS App v1.10, built from master, commit hash cbd4af23783db873f221c327df554fd79d53946b ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400344] Notifications Plugin Disable All Does Nothing
https://bugs.kde.org/show_bug.cgi?id=400344 Simon changed: What|Removed |Added Version|unspecified |1.10 Latest Commit||cbd4af23783db873f221c327df5 ||54fd79d53946b -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400344] Notifications Plugin Disable All Does Nothing
https://bugs.kde.org/show_bug.cgi?id=400344 Simon changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #18 from Simon --- It looks like there is a common thread in these issues that everyone is running some Ubuntu-based distribution Could everyone who is affected by this problem please post: - The result of running the two dbus commands I describe in comment 4: https://bugs.kde.org/show_bug.cgi?id=400178#c4 - Whether or not you are able to manually navigate to the mount point and browse the phone filesystem after running the above dbus commands You can find the mount point(s) by running `qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp getDirectories` - Your system version information, as in the very first comment. Especially, make sure to include your distro and version (but all the other information might be helpful too) Sorry that I don't have better news for you. Hopefully we can get to the bottom of this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400488] New: Messaging app cannot open a conversation with exactly one message
https://bugs.kde.org/show_bug.cgi?id=400488 Bug ID: 400488 Summary: Messaging app cannot open a conversation with exactly one message Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: si...@ergotech.com Target Milestone: --- SUMMARY If a conversation has exactly one message, nothing appears in the ConversationView panel when the conversation is opened STEPS TO REPRODUCE 1. Select a conversation from the ConversationList with only one conversation OBSERVED RESULT The opened ConversationView is blank EXPECTED RESULT The opened ConversationPanel should show a conversation with exactly one message SOFTWARE VERSIONS Fedora Workstation 28 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.48 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 155384] Easily copy properties from one image to another one
https://bugs.kde.org/show_bug.cgi?id=155384 Simon changed: What|Removed |Added CC||ab...@takeadventure.com --- Comment #15 from Simon --- *** Bug 407587 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407587] copy and paste of tags
https://bugs.kde.org/show_bug.cgi?id=407587 Simon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||freisi...@gmail.com --- Comment #1 from Simon --- *** This bug has been marked as a duplicate of bug 155384 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 Simon changed: What|Removed |Added Assignee|si...@ergotech.com |albertv...@gmail.com Component|messaging-application |common -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 Simon changed: What|Removed |Added CC||si...@ergotech.com --- Comment #1 from Simon --- Hi Darin, thanks for the report! Are you able to build kdeconnect from source? This looks like a familiar backtrace and might not have anything to do with Plasma, so we might have already fixed this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 --- Comment #2 from Simon --- Our wiki page has instructions for how to build: https://community.kde.org/KDEConnect#Linux_Desktop -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 --- Comment #3 from Simon --- Potential duplicate of https://bugs.kde.org/show_bug.cgi?id=400010, fixed with https://invent.kde.org/kde/kdeconnect-kde/commit/74e7a90cd8d5752bc1dd17247ad41fdee6c0835a -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Simon changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #18 from Simon --- *** Bug 407785 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 Simon changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #5 from Simon --- *** This bug has been marked as a duplicate of bug 400010 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 --- Comment #6 from Simon --- Thanks for your report and for the test! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407959] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407959 Simon changed: What|Removed |Added Component|messaging-application |common Assignee|si...@ergotech.com |albertv...@gmail.com Severity|critical|normal Platform|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407959] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407959 --- Comment #1 from Simon --- *** Bug 407960 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407960] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407960 Simon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Simon --- *** This bug has been marked as a duplicate of bug 407959 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407960] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407960 Simon changed: What|Removed |Added Platform|Windows CE |MS Windows Severity|critical|normal Component|messaging-application |common Assignee|si...@ergotech.com |albertv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408080] kdeconnectd.exe stops responding to TCP requests after 20 minutes
https://bugs.kde.org/show_bug.cgi?id=408080 Simon changed: What|Removed |Added Component|messaging-application |common Platform|Windows CE |MS Windows Assignee|si...@ergotech.com |piyushaggarwal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405656] Messaging app does not always match a contact with more than one phone number
https://bugs.kde.org/show_bug.cgi?id=405656 Simon changed: What|Removed |Added Latest Commit||a5a0c16b61b72f582489a63479f ||267cbcc3ba191 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399537] Replying to SMS with the wrong sim-card
https://bugs.kde.org/show_bug.cgi?id=399537 Simon changed: What|Removed |Added CC||si...@ergotech.com Status|REPORTED|CONFIRMED Assignee|albertv...@gmail.com|si...@ergotech.com Ever confirmed|0 |1 Component|common |android-application -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401241] Phone locks during typing
https://bugs.kde.org/show_bug.cgi?id=401241 Simon changed: What|Removed |Added Status|REPORTED|RESOLVED CC||si...@ergotech.com Resolution|--- |FIXED Latest Commit||470eab525afd6edf8999b5ba426 ||9eaf851350f7a -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #12 from Simon --- If you are affected by this problem and you are able to build the Android app from source (instructions in the wiki: https://community.kde.org/KDEConnect#Android), could you please build my new merge request (https://invent.kde.org/kde/kdeconnect-android/merge_requests/77) and test whether you now see SMS history? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399537] Replying to SMS with the wrong sim-card
https://bugs.kde.org/show_bug.cgi?id=399537 --- Comment #2 from Simon --- To be clear, the use-case (slash problem) here is when using the pop-up reply box to reply to SMS? I believe this will be fixed with the recent support for reply-able notifications (because this will delegate selection of the proper SIM card to the phone's messaging app). I don't think this has been released yet but I expect it will be part of the next release. (I can't remember whether or not this feature has been released, if you get an MMS, or a non SMS message like WhatsApp or Telegram, do you have the option to reply to that?) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407959] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407959 Simon changed: What|Removed |Added CC||si...@ergotech.com --- Comment #6 from Simon --- We have someone working full-time on improving Windows support and it has recently significantly improved. The improved version will probably not be in the binary factory for awhile because of complicated dependencies. You might want to join our development channel, where new versions get posted as they are being worked on: https://community.kde.org/KDEConnect#Development . For now, I have put the latest development version up here: http://172.245.92.84/kde/kde-connect.exe, but don't save this link because I won't be updating it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407959] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=407959 --- Comment #7 from Simon --- *** Bug 408449 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408449] KDE connect does not work and does not connect windows 10 with Android.
https://bugs.kde.org/show_bug.cgi?id=408449 Simon changed: What|Removed |Added Status|REPORTED|RESOLVED Platform|Windows CE |MS Windows Assignee|si...@ergotech.com |albertv...@gmail.com Component|messaging-application |common Resolution|--- |DUPLICATE Severity|critical|normal --- Comment #2 from Simon --- Instead of re-reporting to the same bug, please update the old bug report. I have written more there. *** This bug has been marked as a duplicate of bug 407959 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 398889] Messaging app does not show conversation if the most-recent message was an MMS
https://bugs.kde.org/show_bug.cgi?id=398889 Simon changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kdeconnect-android/commit/5 ||1e957d82290bc5d07c01bcd55e0 ||3c17868ca14c --- Comment #2 from Simon --- Git commit 51e957d82290bc5d07c01bcd55e03c17868ca14c by Simon Redman. Committed on 10/06/2019 at 05:48. Pushed by sredman into branch 'master'. [SMSApp] Support plain-text MMS ## Summary Not having support for MMS caused some minor problems, like in https://bugs.kde.org/show_bug.cgi?id=398889 . This patch adds basic MMS support for plain-text MMS, including multi-target messages. Android companion to https://invent.kde.org/kde/kdeconnect-kde/merge_requests/97 Currently there are several rough areas: - Multi-target messages do not have the full list of recipients (I am planning to work on this in another patch, because this one is already quite large enough) - Parsing MMS is significantly slower than parsing SMS. This makes sense, since we need to make significantly many more content:// calls for MMS. The only solution I can think of here is to add the ability to request a range of messages, which I need to do anyway, but which should not be part of this patch. - The desktop app is totally busted with regard to multi-target MMS, but that will also be fixed in another MR ## Test Plan ### Before: Open SMS app on desktop, scroll through conversations, notice: - Any single-target message which had the most-recent message as an MMS does not appear - Any multi-target MMS conversations do not appear ### After: Open SMS app on desktop, notice: - Conversations which have an MMS as their most-recent message appear - MMS which consisted of only text are rendered correctly - Multi-target conversations are shown (though pretty busted, as said before. Do not attempt to reply to one!) M +407 -59 src/org/kde/kdeconnect/Helpers/SMSHelper.java M +5-11 src/org/kde/kdeconnect/Plugins/SMSPlugin/SMSPlugin.java https://invent.kde.org/kde/kdeconnect-android/commit/51e957d82290bc5d07c01bcd55e03c17868ca14c -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 398889] Messaging app does not show conversation if the most-recent message was an MMS
https://bugs.kde.org/show_bug.cgi?id=398889 --- Comment #3 from Simon --- Technically, this also needs https://invent.kde.org/kde/kdeconnect-kde/merge_requests/97 in order to be fully resolved, but that patch will be merged soon enough -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399537] Replying to SMS with the wrong sim-card
https://bugs.kde.org/show_bug.cgi?id=399537 --- Comment #4 from Simon --- (In reply to peje66 from comment #3) > Yes! > > (And also which sim to use when using kdeconnect-cli to send sms.) Okay. I am working on a big SMS overhaul right now to be released "when it's ready" which primarily includes a desktop SMS app. I think I have figured out how to do this with requesting the proper SIM card and I will aim to give kdeconnect-cli the ability to choose as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408545] New: More finegrained page navigation
https://bugs.kde.org/show_bug.cgi?id=408545 Bug ID: 408545 Summary: More finegrained page navigation Product: okular Version: 1.7.2 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- It would be very useful to have a feature that ideally allows to navigate forwards, such that only the the last part previously visible at the bottom is then at the top. That would be the ideal option, very flexible towards zoom. Alternatively having an option to go half a page forwards instead of a full page would already help a lot. This is mostly useful when reading dense multi-page e.g. A4 documents, which don't fit fully on a screen in a readable size. And line scrolling is just very cumbersome. I assume I am on 1.7.2, I didn't find those tags on git, only the KDE ones: I compiled v19.04.2 (debian provided package is ancient). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 361525] Most SMS events trigger 2 desktop notifications
https://bugs.kde.org/show_bug.cgi?id=361525 Simon changed: What|Removed |Added CC||linus.kardell+kdebugs@gmail ||.com --- Comment #4 from Simon --- *** Bug 400922 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 361525] Most SMS events trigger 2 desktop notifications
https://bugs.kde.org/show_bug.cgi?id=361525 Simon changed: What|Removed |Added CC||nickagodrid...@gmail.com --- Comment #5 from Simon --- *** Bug 408546 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
