[ktimetracker] [Bug 416693] Moving a subtask to another higher-order task scrambles time data of all tasks
https://bugs.kde.org/show_bug.cgi?id=416693 --- Comment #3 from Andreas Kilgus --- (In reply to Alexander Potashev from comment #2) > Andreas, which version of KTimeTracker did you use to create the initial > version of your .ics file? I use ktimetracker continuously since the days it had been called karm. So I guess that initially I used a version that was based on flat files … Through the years the file format was converted several times. I can't tell anymore if this always happened on-the-fly or sometimes by importing the current file containing data in an outdated format. > The screenshot mentions dates back to 2019-02-01, does this imply you used > KTimeTracker 4.14.10 back then? "grep DTSTART ktimetracker.ics | sort" tells me, that the oldest regular entries in my current ktimetracker.ics date back to May 2013. Though there are some irregular entries, too: DTSTART:19800406T01 DTSTART:19800928T03 DTSTART:19810329T02 DTSTART:19971026T03 DTSTART;TZID=Europe/Berlin:20130529T160247 The first four entries of the list don't share the format of the others (timezone data) and point to a date I am sure ;) not to have used karm/ktimetracker. Additionally there are some tasks that are older, me knowing the work was done e. g. in 2011, but they seem to have lost their history. "Total Time" is available and valid but there is no information how "Total Time" gained its value. I can try to anonymize my file and send it to you for testing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416684] New: Feature request: Tagging tabs for quick identification of filesystem location
https://bugs.kde.org/show_bug.cgi?id=416684 Bug ID: 416684 Summary: Feature request: Tagging tabs for quick identification of filesystem location Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: andreas.wallb...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dear KDE/Dolphin developers, Each tab in Dolphin is currently named after the viewed directory. While working/multitasking on complex workloads, I often find myself having 20-30 tabs open in Dolphin, many of which may have identical/similar names because of overlapping directory names. This makes it unnecessarily difficult to rapidly change between the desired tabs. I have two suggestions for how this could be improved, while preserving my type of workflow: 1. Allow manual/automated text tagging of a tab: In addition to showing only the current tab, it could have a separate text tag prepended allowing some arbitrary text label. Input could be offered after right-clicking the tab. Alternatively, dragging a directory name from the path field while in "Navigate" mode and dropping it onto the tab would put that name into the label field. Instead of showing only: --- | dir | The tab would show: -- | label: dir | A new tab opened while viewing the directory shown by a labeled tab would inherit the label. Alternatively, paths could be pre-configured to automatically be associated with a label, such that all directories nested under that path get auto-labelled. This could be done in a setting similar to how paths are excluded from searches in Filelight. Alternatively, while configuring "Places" entry, there could be an option to allow the user to auto-label tabs. 2. Inherited colors for paths. Allow the user to set arbitrary color schemes for different paths. As above, this could be controlled through a setting or while configuring a "Places" entry. For directories nested under that entry, the tabs themselves could be colored accordingly, either fully, or with a bold line along the top of the tab or with a small box/circle/dot in the top left corner of the tab. Alternatively, the tab text field could be colored/underlined. Issue that might need some thinking to resolve are how potentially overlapping settings are resolved, and also, whether labels derived from directory names should be "dead" or updated after a directory name is changed. In any case, perhaps this could inspire some ideas for workflow management in Dolphin. Thanks for a great tool! -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 416693] New: Moving a subtask to another higher-order task scrambles time data of all tasks
https://bugs.kde.org/show_bug.cgi?id=416693 Bug ID: 416693 Summary: Moving a subtask to another higher-order task scrambles time data of all tasks Product: ktimetracker Version: 5.0.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: k...@fuenfsieben.de Target Milestone: --- Created attachment 125368 --> https://bugs.kde.org/attachment.cgi?id=125368=edit Time data before moving a subtask at a completely different position in task hierarchy SUMMARY Changing the hierarchy of tasks scrambles time data of all tasks. STEPS TO REPRODUCE 1. Move a subtask to another higher-order (sub)task OBSERVED RESULT Time data is scrambled, s. attachments. The task shown in the screenshots remained completely untouched. A new task was created with several subtasks with additional subtasks. As soon as one of those subtasks was moved to another position in the hierarchy of this new task, time data of all tasks went nuts - like the one shown in before.png/after.png. EXPECTED RESULT Time data does not change. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 416693] Moving a subtask to another higher-order task scrambles time data of all tasks
https://bugs.kde.org/show_bug.cgi?id=416693 --- Comment #1 from Andreas Kilgus --- Created attachment 125369 --> https://bugs.kde.org/attachment.cgi?id=125369=edit Time data after an independent subtask has been moved in task hierarchy -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 275927] display task as running when task is folded and subtask is running
https://bugs.kde.org/show_bug.cgi?id=275927 Andreas Kilgus changed: What|Removed |Added CC||k...@fuenfsieben.de -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 333159] moving task to subtask is slow
https://bugs.kde.org/show_bug.cgi?id=333159 Andreas Kilgus changed: What|Removed |Added CC||k...@fuenfsieben.de -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 409360] Moving a file creates a symbolic link and deletes the original file
https://bugs.kde.org/show_bug.cgi?id=409360 --- Comment #9 from Andreas Schneider --- I think to fix this, we need https://bugs.libssh.org/T98 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416301] s390x: "compare and signal" not supported
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Attachment #125487|0 |1 is obsolete|| Attachment #125541|0 |1 is obsolete|| --- Comment #8 from Andreas Arnez --- Created attachment 125542 --> https://bugs.kde.org/attachment.cgi?id=125542=edit Updated patch with fixed CxB and added test case Functionally equivalent to the updated patch by Mark. This version also adds testing for the instructions CEB, CDB, KEB, and KDB, which were untested before. The new test would have caught the problem. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416301] s390x: "compare and signal" not supported
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Andreas Arnez --- Pushed as e83c28e10c99d52b22ee69e25857dac8bf3d5240 after approval via IRC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 172615] Gimp 2.6 utility windows do not stay on top of the main window
https://bugs.kde.org/show_bug.cgi?id=172615 Andreas Kilgus changed: What|Removed |Added Status|RESOLVED|REOPENED CC||k...@fuenfsieben.de Resolution|INTENTIONAL |--- --- Comment #29 from Andreas Kilgus --- According to https://manual.ardour.org/ardour-configuration/system-specific-setup/kde-plasma-5/ - if their claim about the behaviour of other window managers is valid - gimp is not the only application that reads the ICCCM standard a different way compared to kwin (and looking at the age of this bug report still compared to the one of Plasma 5). So it does not seem to be one application kwin had to be adjusted to but one window manager that behaves different to all the others - at least in this small but not completely irrelevant case of utility windows. Perhaps this is the reason, too, why I sometimes have to dig for message and dialogue windows behind the main window of applications running with wine. But this just came to mind while typing, I have no prove for it being another instance of the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 --- Comment #1 from Andreas Hencke --- Created attachment 125625 --> https://bugs.kde.org/attachment.cgi?id=125625=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] New: Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 Bug ID: 417072 Summary: Kontact crashes again for no apparent reason Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I was away from machine, when I returned kontacht had crashed. I couldn't find out wether it is a duplicate from bug 416307 and/or bug 415997 The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x in () #7 0x7f997ad3e8ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f997ad3e9fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f997ad3ea29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f997d1b5779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 416986, bug 416900, bug 416816, bug 416730, bug 416721. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #2 from Andreas Arnez --- Created attachment 125751 --> https://bugs.kde.org/attachment.cgi?id=125751=edit Patch to enable "grail" on s390x -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] New: s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 Bug ID: 417281 Summary: s390x: /bin/true segfaults with "grail" enabled Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: ar...@linux.ibm.com Target Milestone: --- When enabling the "grail" support for s390x (currently disabled), a simple program like /bin/true runs into a segmentation fault. This problem occurs on some systems (such as Fedora 31 on an IBM z14) and not on some others. The segfault happens in the dynamic loader, like this: ==319960== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==319960== Access not within mapped region at address 0x0 ==319960==at 0x4009E46: do_lookup_x (dl-lookup.c:350) ==319960==by 0x400AA0D: _dl_lookup_symbol_x (dl-lookup.c:809) ==319960==by 0x400C6E5: elf_machine_rela (dl-machine.h:307) ==319960==by 0x400C6E5: elf_dynamic_do_Rela (do-rel.h:137) ==319960==by 0x400C6E5: _dl_relocate_object (dl-reloc.c:254) ==319960==by 0x4004045: dl_main (rtld.c:2253) ==319960==by 0x4018147: _dl_sysdep_start (dl-sysdep.c:253) ==319960==by 0x4001FB5: _dl_start_final (rtld.c:445) ==319960==by 0x4001FB5: _dl_start (rtld.c:535) ==319960==by 0x40011B3: ??? (in /usr/lib64/ld-2.30.so) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #1 from Andreas Arnez --- The crash happens in glibc's elf/dl-lookup.c in do_lookup_x, when trying to access the first element of the array 'list'. It seems that the register containing the address is corrupted; it was just copied from %r4 into %r6, but the values differ. Some observations: • When using `--vex-guest-max-insns=40' or lower, the problem disappears. • The option `--vex-iropt-register-updates=allregs-at-each-insn' does not help. • When attaching GDB, it seems that the corruption happens on the `lgr' instruction that is supposed to copy the value from %r4. Instead of copying, %r6 is overwritten with some random (?) value: ┌ │ 1: x/i $pc │ => 0x4009e36 : lgr %r6,%r4 │ 2: /x $r4 = 0x4829f90 │ 3: /x $r6 = 0x1fff000260 │ (gdb) si │ 1: x/i $pc │ => 0x4009e3a : cgije %r2,0,0x4009f34 │ 2: /x $r4 = 0x4829f90 │ 3: /x $r6 = 0x10 └ • The `lgr' instruction is affected by grail's transformation. After the transformation, the register move is performed conditionally. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #3 from Andreas Arnez --- Created attachment 125752 --> https://bugs.kde.org/attachment.cgi?id=125752=edit Excerpt of Valgrind output with --trace-flags=1000 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416301] s390x: "compare and signal" not supported
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |ar...@linux.ibm.com Status|REPORTED|CONFIRMED --- Comment #3 from Andreas Arnez --- Created attachment 125487 --> https://bugs.kde.org/attachment.cgi?id=125487=edit Support compare-and-signal instructions This is the patch I was referring to. It should be sufficient unless accurate FP signal handling is needed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416301] s390x: "compare and signal" not supported
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #2 from Andreas Arnez --- (In reply to Julian Seward from comment #1) > Andreas, given that newer GCC and LLVM do emit these now, it sounds like > supporting them is potentially of high priority. What's your view? Absolutely. I have a patch ready, although it doesn't handle the "signalling" part correctly yet. Then again, signalling doesn't seem to be handled correctly for s390x at all yet. Do you know how important the correct handling of FP signals is considered to be on other platforms? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417195] New: Kontact crashes when opening a special mail
https://bugs.kde.org/show_bug.cgi?id=417195 Bug ID: 417195 Summary: Kontact crashes when opening a special mail Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: On KMail I've got four E-Mail accounts but only the posteo.de account is affected and there one Mail (received twice, first at 14:01 o'clock and second at 14:03 o'clock today) When I click to one of these mails Kontact crashes immediatelly, every time I try to. The received mails are from no-re...@deutschepost.de The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b72833f00 (LWP 6934))] Thread 53 (Thread 0x7f49eaefd700 (LWP 7049)): #0 0x7f4b85b5dc2f in __GI___poll (fds=0x7f49e00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4b8420ea3e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4b8420eb73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4b861206c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b860c763b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b85f00a75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4b85f01cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 52 (Thread 0x7f49eb7fe700 (LWP 7046)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec635338) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec6352e8, cond=0x55a7ec635310) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec635310, mutex=0x55a7ec6352e8) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 51 (Thread 0x7f49ebfff700 (LWP 7045)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec53d498) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec53d448, cond=0x55a7ec53d470) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec53d470, mutex=0x55a7ec53d448) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 50 (Thread 0x7f4a0c8f9700 (LWP 7043)): #0 0x7f4b84b676e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f4a0c8f8470, clockid=, expected=0, futex_word=0x7f4a0c8f85b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f4b84b676e0 in __pthread_cond_wait_common (abstime=0x7f4a0c8f8470, clockid=, mutex=0x7f4a0c8f8568, cond=0x7f4a0c8f8590) at pthread_cond_wait.c:520 #2 0x7f4b84b676e0 in __pthread_cond_timedwait (cond=0x7f4a0c8f8590, mutex=0x7f4a0c8f8568, abstime=0x7f4a0c8f8470) at pthread_cond_wait.c:656 #3 0x7f4b7e6ac10b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4b7e6acab2 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4b7e6acba6 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4b7e66e705 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4b7e670c6b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4b7e671258 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4b7e6aec75 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 49 (Thread 0x7f4a0d0fa700 (LWP 7041)): #0
[valgrind] [Bug 417452] s390_insn_store_emit: dst->tag for HRcVec128
https://bugs.kde.org/show_bug.cgi?id=417452 --- Comment #8 from Andreas Arnez --- (In reply to Mark Wielaard from comment #7) > I have also tested the patch against Fedora s390x and things look fine there > too. Good! Unless there are any further comments, I'll push this early next week. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417452] s390_insn_store_emit: dst->tag for HRcVec128
https://bugs.kde.org/show_bug.cgi?id=417452 Andreas Arnez changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Andreas Arnez --- OK, pushed as git commit f27fe920cd321ca3cf4bc03a72879fd18bf2736f. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417979] Kmail crashes when opening a special email
https://bugs.kde.org/show_bug.cgi?id=417979 --- Comment #1 from Andreas Beisemann --- Created attachment 126246 --> https://bugs.kde.org/attachment.cgi?id=126246=edit error.txt -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417979] New: Kmail crashes when opening a special email
https://bugs.kde.org/show_bug.cgi?id=417979 Bug ID: 417979 Summary: Kmail crashes when opening a special email Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: abeisem...@gmail.com Target Milestone: --- Created attachment 126245 --> https://bugs.kde.org/attachment.cgi?id=126245=edit The EMail itself SUMMARY KMail crash, when open 1 special Email with pdf attachments STEPS TO REPRODUCE 1. open KMail 2. klick on email 3. KMail crashs and ask for open again OBSERVED RESULT app starts new EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Comment: opensuse 15.1, Plasma:5.12.8, Framework: 5.55.0, QT:5.9.7, Kernel: 4.12.14-lp151.28.36-default, 64 bit ADDITIONAL INFORMATION EMail is to read in any browser, not in kmail. Please be careful with the passing on of the mail, it is from a church organization where I work on a voluntary basis. No way to install debug symbols, the attempt is immediately terminated with an error. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417979] Kmail crashes when opening a special email
https://bugs.kde.org/show_bug.cgi?id=417979 Andreas Beisemann changed: What|Removed |Added CC||abeisem...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 417988] New: Columns displayed do not match configuration
https://bugs.kde.org/show_bug.cgi?id=417988 Bug ID: 417988 Summary: Columns displayed do not match configuration Product: ktimetracker Version: 5.0.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: k...@fuenfsieben.de Target Milestone: --- Created attachment 126258 --> https://bugs.kde.org/attachment.cgi?id=126258=edit Screenshot config/main SUMMARY ktimetracker shows all columns in main window, not the ones saved in configuration to display. STEPS TO REPRODUCE 1. Disable some columns of main window (in configuration dialogue or main window). 2. Quit ktimetracker. 3. Start ktimetracker. OBSERVED RESULT Ktimetracker shows all columns available. EXPECTED RESULT Ktimetracker shows just the columns configured to display. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] New: vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 Bug ID: 417993 Summary: vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: ar...@linux.ibm.com Target Milestone: --- This is seen on s390x with the test case in `memcheck/tests/vbit-test': ┌ │ valgrind -q --expensive-definedness-checks=yes ./vbit-test │ ==113353== Conditional jump or move depends on uninitialised value(s) │ ==113353==at 0x10012A8: check_result_for_binary (binary.c:372) │ ==113353==by 0x10025A7: test_binary_op (binary.c:683) │ ==113353==by 0x1000B35: main (main.c:192) └ The uninitialised value results from the calculation in int_add_or_sub_vbits(). In the failing case the function receives two 32-bit unsigned integers as arguments, the first of which equals zero, but has its least significant bit undefined, and the second value equals 0x. One step of the calculation determines the value `a_min' as ┌ │ a_min = aa & ~vaa; └ where `aa' has the lowest bit undefined and `vaa' has exactly the lowest bit set. However, the compiler transforms this to ┌ │ a_min = (aa & vaa) ^ aa; └ After that, Valgrind's memcheck considers the lowest bit of `a_min' undefined as well. NOTE: In order to run the test case, I temporarily disabled Iop_Or1 and Iop_And1 for s390x in the `irops' array in irops.c. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402988] SMBSlave::listDir() should use smbc_readdirplus() if available
https://bugs.kde.org/show_bug.cgi?id=402988 --- Comment #3 from Andreas Schneider --- Yes, this is only for listing directory contents. In the meantime we have smbc_readdirplus2() which addresses some bugs created with smbc_readdirplus(). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417647] emoji-picker: Doesn't support fully HiDPI
https://bugs.kde.org/show_bug.cgi?id=417647 Andreas Schneider changed: What|Removed |Added Summary|emoji-picker: Doesn't |emoji-picker: Doesn't |support HiDPI |support fully HiDPI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417647] New: emoji-picker: Doesn't support HiDPI
https://bugs.kde.org/show_bug.cgi?id=417647 Bug ID: 417647 Summary: emoji-picker: Doesn't support HiDPI Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: a...@cryptomilk.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 126025 --> https://bugs.kde.org/attachment.cgi?id=126025=edit screenshot of the emoji picker SUMMARY The new plasma emoji-picker doesn't fully support HiDPI screens, the bar on the left doesn't provide hidpi icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417647] emoji-picker: Doesn't support fully HiDPI
https://bugs.kde.org/show_bug.cgi?id=417647 --- Comment #2 from Andreas Schneider --- I have that font already installed: rpm -q noto-coloremoji-fonts noto-coloremoji-fonts-20180810-1.1.noarch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 172615] Gimp 2.6 utility windows do not stay on top of the main window
https://bugs.kde.org/show_bug.cgi?id=172615 --- Comment #32 from Andreas Kilgus --- (In reply to David Edmundson from comment #30) > If you can explain where we explicitly break the spec I will reopen this. I am no specs expert but I can tell if something works as expected. Below you find the test results of several window managers. Work as expected (plugin gui opened in ardour/mixbus stays in foreground): compiz openbox metacity xfwm4 Work in an alternative, usable way (plugin gui does not stay in foreground in every case of user interaction with main window but the plugin gui is always just an Alt+Tab away because it is part of the windows list): icewm fvwm fvwm2 Main window of ardour/mixbus must be minimized or synth gui must be closed and reopened for the synth gui to be accessible, no return via Alt+Tab: kwin > Thomas above explains that we don't. So if the conclusion is already set there's no need to discuss. My private conclusion: I will have to switch to another window manager that you may claim not being standard-compliant - though I wonder at so many window managers seeming to belong to this group if your claim is true, see above - but that keeps windows accessible at least. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417238] Test memcheck/tests/vbit-test fails on mips64 BE
https://bugs.kde.org/show_bug.cgi?id=417238 Andreas Arnez changed: What|Removed |Added CC||ar...@linux.ibm.com --- Comment #2 from Andreas Arnez --- (In reply to Stefan Maksimovic from comment #0) > [...] > Tested on x86 and mips64 BE. Thanks, this also helps on s390x, once And1 and Or1 are actually supported. However, I wonder why the non-overlapping is a problem, and why it doesn't matter for the other union members. Probably because the logic exploits the overlapping of the least significant bit of u32 with u1 somewhere? Where in the logic does that occur? Also, even if not necessary, I wonder whether the logic could be simplified by eliminating u1 and u16 (and possibly u32) as well. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 --- Comment #3 from Andreas Arnez --- (In reply to Mark Wielaard from comment #2) > Since s390x is also big endian maybe this is related to bug #417238 which > fixes an issue on mips64 BE and ppc64[be]? Thanks for pointing to this bug; I haven't seen that yet. I've retested with the fix from that Bug applied, and the false positive still remains. As far as I can tell, these two problems don't appear to be related. (On the plus side, the patch *does* fix another failure I've seen with vbit-test that occurs when adding s390x support for And1/Or1 and enabling their testing in vbit-test.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 --- Comment #1 from Andreas Arnez --- Created attachment 126262 --> https://bugs.kde.org/attachment.cgi?id=126262=edit Disable And1/Or1 testing in vbit-test Just for completeness, this is the patch used for disabling the And1/Or1 testing in vbit-test. Without this patch, the test case still fails as described above, but then also runs into this: vex: the `impossible' happened: sizeofIRType -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417647] emoji-picker: Doesn't support fully HiDPI
https://bugs.kde.org/show_bug.cgi?id=417647 --- Comment #4 from Andreas Schneider --- Created attachment 126049 --> https://bugs.kde.org/attachment.cgi?id=126049=edit fonts.conf -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416307] New: Kontact crashed for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=416307 Bug ID: 416307 Summary: Kontact crashed for no apparent reason Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Kontact was running while I was reading an Newspaper article using Google Chrome -- Backtrace (Reduced): #6 0x7fc7010ab8d5 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc7010ab9fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc7010aba29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc703522779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fc703521264 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 The reporter indicates this bug may be a duplicate of or related to bug 415997. Possible duplicates by query: bug 416254, bug 416136, bug 416113, bug 415997, bug 415991. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416301] New: s390x: "compare and signal" not supported
https://bugs.kde.org/show_bug.cgi?id=416301 Bug ID: 416301 Summary: s390x: "compare and signal" not supported Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: ar...@linux.ibm.com Target Milestone: --- Valgrind does not currently support the "compare and signal" floating-point instructions (KEBR, KDBR, KXBR, KEB, and KDB). This didn't matter much since they weren't emitted by GCC or LLVM until recently. But that has changed; newer GCC and LLVM versions *do* emit these instructions. Thus Valgrind should support them now. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 416218] New: Annotations get trucated to false but existing tags
https://bugs.kde.org/show_bug.cgi?id=416218 Bug ID: 416218 Summary: Annotations get trucated to false but existing tags Product: kphotoalbum Version: GIT master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import/Export Assignee: kpab...@willden.org Reporter: schleth...@web.de Target Milestone: --- SUMMARY This happens on the import side of an export/import operation via *.kim: For keywords that are new for the existing database (coming from the import), the dialog often suggests some shorter form that is already there. e.g: Instead of using the tag from the *kim file: "Schweinslippfisch Bodianus diplotaenia" the suggested keyword is just "Schwein" (which is an existing one in the current DB). This happens with all the tags where a shorter part of the word is already present and the new tag isn't. This forces me to comb through the list and *manually* type in the long version again (there is no way to copy and paste from the left side of the dialog box to the right (?)). I would much prefer to have the new keyword inserted - maybe highlighted in red and maybe with the option to select from similar ones already in existence ... STEPS TO REPRODUCE 1. you need 2 separate databases with the same categories but (slightly) different tags 2. in one DB tag an image with "sky" 3. in the other DB tag an image with "skyfall" in the same category as before 4. select this image for export to a *.kim file 5. import this kim file into the first DB OBSERVED RESULT 6. when the dialog reaches the point where you can see the tags of the category above, the tag "skyfall" (in the *kim) will be shortened to "sky" EXPECTED RESULT alt-6a. the tag "skyfall" is suggested for import but highlighted (in red?) with the option to select from (a few!) similar tags that are already there. alt-6b. the list can be shortened to optionally only show tag mismatches SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuse 15.1 with Plasma 64bit (available in About System) KDE Plasma Version: KDE Frameworks 5.55.0 Qt 5.9.7 (kompiliert gegen 5.9.7) ADDITIONAL INFORMATION KPA-version: v5.5-150-g323e2b29 (compiled from git master) -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 415102] missing-letter, voices broken on Android
https://bugs.kde.org/show_bug.cgi?id=415102 Andreas Neudecker changed: What|Removed |Added CC||zap...@gmx.net --- Comment #2 from Andreas Neudecker --- Downloading background music files, images for some of the activities, and language audio files for German language fail to download reproducibly; F-Droid apk of version 0.97 on Android 5.11. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] New: Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 Bug ID: 415997 Summary: Kontact had crashed when I returned to machine Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.65.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I made a coffee when I returned to the computer and Kontact crashed - Unusual behavior I noticed: For a few days (before the kernel update) it takes a few seconds (2-3 seconds) when I click on an email in the message list until the message text appears. -- Backtrace (Reduced): #6 0x in () #7 0x7f1087bb88ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1087bb89fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1087bb8a29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f108a02f779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 415991, bug 415973, bug 415962, bug 415960, bug 415956. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 --- Comment #1 from Andreas Hencke --- Created attachment 124968 --> https://bugs.kde.org/attachment.cgi?id=124968=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 346022] kio/sftp cannot handle symlink in chrooted environment
https://bugs.kde.org/show_bug.cgi?id=346022 Andreas Schneider changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Andreas Schneider --- Closing as fixed per comment #2. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418997] s390x: Support Iex_ITE for float and vector types
https://bugs.kde.org/show_bug.cgi?id=418997 Andreas Arnez changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Andreas Arnez --- OK, pushed as git commit abe7f083fdebb40c6f4a5adbdd2b64f5c329969a. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 Andreas Arnez changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #8 from Andreas Arnez --- Pushed all of the changes proposed above: 6a90a15b9 - s390x: Drop spurious register moves in CDAS instruction selector 4970e2002 - s390x: Fix Iex_Load instruction selectors for F128/D128 types 4e9763c61 - s390x: Introduce and exploit new ALU operator S390_ALU_ILIH 1008ab726 - s390x: Fix typos in comments for sub_from_SP and add_to_SP in isel -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 418827] New: Wacom Intuos Pro M connected via bluetooth
https://bugs.kde.org/show_bug.cgi?id=418827 Bug ID: 418827 Summary: Wacom Intuos Pro M connected via bluetooth Product: wacomtablet Version: 3.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: a...@cryptomilk.org Target Milestone: --- SUMMARY The Wacom Intuos Pro M has a different ID if you connect it over bluetooth. Here is the db entry I just copied to the bluetooth ID. [0360] model=PTH-651 layout=bl_4 name=Wacom Intuos Pro M padbuttons=9 statusleds=4 wheel=no touchring=yes touchstripl=no touchstripr=no hwbutton1=1 hwbutton2=2 hwbutton3=3 hwbutton4=8 hwbutton5=9 hwbutton6=10 hwbutton7=11 hwbutton8=12 hwbutton9=13 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #5 from Andreas Arnez --- Created attachment 127248 --> https://bugs.kde.org/attachment.cgi?id=127248=edit Fix Iex_Load instruction selectors for F128/D128 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #6 from Andreas Arnez --- Created attachment 127249 --> https://bugs.kde.org/attachment.cgi?id=127249=edit Drop spurious register moves in CDAS instruction selector -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #2 from Andreas Arnez --- Created attachment 127245 --> https://bugs.kde.org/attachment.cgi?id=127245=edit Drop register arg to s390_isel_int1_expr() -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #3 from Andreas Arnez --- Created attachment 127246 --> https://bugs.kde.org/attachment.cgi?id=127246=edit Fix typos in comments for sub_from_SP and add_to_SP in isel -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #4 from Andreas Arnez --- Created attachment 127247 --> https://bugs.kde.org/attachment.cgi?id=127247=edit Introduce and exploit new ALU operator S390_ALU_ILIH -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #7 from Andreas Arnez --- See the above attachments for fixes of the findings related to this Bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418997] s390x: Support Iex_ITE for float and vector types
https://bugs.kde.org/show_bug.cgi?id=418997 --- Comment #2 from Andreas Arnez --- If there are no objections, I'm going to push this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] New: s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 Bug ID: 419503 Summary: s390x: Avoid modifying registers returned from isel functions Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: ar...@linux.ibm.com Target Milestone: --- As discussed with Julian Seward, host_s390_isel.c contains some questionable logic where registers returned from isel functions are potentially modified, or where it is not sufficiently made clear that they are always left unmodified. As a general rule, rather than modifying a register returned by one of the isel functions, the register should be copied first and the copy modified instead. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417238] Test memcheck/tests/vbit-test fails on mips64 BE
https://bugs.kde.org/show_bug.cgi?id=417238 --- Comment #4 from Andreas Arnez --- (In reply to Aleksandar Rikalo from comment #3) [...] > The other possible way to fix [...] seems like it would be more > complicated, especially because valgrind_[set|get]_vbits() functions (see > valgrind.c) have to be modified. > > [...] I'm not sure how much logic would be simplified > by eliminating the u8, ..., u32 fields (e.g., concat_vbits() function). I > would put that option aside. FWIW, I'd be fine with that. Julian, what do you think? Can we move this forward? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 --- Comment #1 from Andreas Arnez --- Created attachment 127167 --> https://bugs.kde.org/attachment.cgi?id=127167=edit Original "CHECK" markers for host_s390_isel.c by Julian This is a "patch" that marks the questionable logic in host_s390_isel.c Julian detected during his review. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419503] s390x: Avoid modifying registers returned from isel functions
https://bugs.kde.org/show_bug.cgi?id=419503 Andreas Arnez changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|jsew...@acm.org |ar...@linux.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418997] s390x: Support Iex_ITE for float and vector types
https://bugs.kde.org/show_bug.cgi?id=418997 --- Comment #1 from Andreas Arnez --- Created attachment 127000 --> https://bugs.kde.org/attachment.cgi?id=127000=edit Support Iex_ITE for float and vector types This patch fixes the fails I have seen. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420740] adding of inline images broken
https://bugs.kde.org/show_bug.cgi?id=420740 --- Comment #1 from Andreas Kohlbecker --- Created attachment 127976 --> https://bugs.kde.org/attachment.cgi?id=127976=edit mbox file of fixed email -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420740] New: adding of inline images broken
https://bugs.kde.org/show_bug.cgi?id=420740 Bug ID: 420740 Summary: adding of inline images broken Product: kmail2 Version: 5.14.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: a...@neotop.de Target Milestone: --- Created attachment 127975 --> https://bugs.kde.org/attachment.cgi?id=127975=edit mbox file of broken email SUMMARY When adding an inline image to a HTML (rich text) email the image is missing in the send email. Instead an placeholder icon is shown. STEPS TO REPRODUCE 1. create new rich text email 2. paste an image from the clipboard to the email content and choose "add as linine image" or use the "Add image" function from the toolbar. 3. Send the image OBSERVED RESULT The image in the recipients inbox and that which has been copied into the send folder do not show the inline image. DIAGNOSIS The image is attached correctly to the email but he tag is not added to the html code. A broken message can be fixed: 1. save as mbox file (see attached file image-mail-2-pub.mbox) 2. add the missing img tag with the cid of the attachment (image-mail-2-fixed-pub.mbox) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-51-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 420605] New: Neon apt repository contains broken dependencies, update will cause desktop to be uninstalled
https://bugs.kde.org/show_bug.cgi?id=420605 Bug ID: 420605 Summary: Neon apt repository contains broken dependencies, update will cause desktop to be uninstalled Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: andr...@ohok.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Updating KDE neon will remove entire desktop Yesterday I updated my neon user edition with sudo apt dist-upgrade. I should've used pkcon, but it looks like that didn't cause my problem. I noticed too late that the update was going to uninstall everything, and now I can no longer reinstall the neon-desktop package because of dependency issues. I tracked it down to several packages depending on libqt5qml5 5.14.2 or higher, but the version to be installed is 5.14.2-0xneon+18.04+bionic+build56 which somehow doesn't satisfy that dependency? For example I can't install qml-module-qtquick-control because of that, but I need it to get my desktop back. In my sources list I am only using the default bionic repos and archive.neon.org/release bionic main. The issue has been confirmed by another user on reddit: https://www.reddit.com/r/kdeneon/comments/g7xp1r/update_uninstalled_entire_desktop_can_not/?utm_source=share_medium=ios_app_name=iossmf STEPS TO REPRODUCE 1. Update KDE neon from an existing install with the repos mentioned above. OBSERVED RESULT The entire desktop will be uninstalled and can no longer be reinstalled due to incorrect dependencies. EXPECTED RESULT The update works correctly, it is possible to install neon-desktop etc. SOFTWARE/OS VERSION: Linux/KDE Plasma: neon user latest ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 416693] Moving a subtask to another higher-order task scrambles time data of all tasks
https://bugs.kde.org/show_bug.cgi?id=416693 --- Comment #4 from Andreas Kilgus --- (In reply to Andreas Kilgus from comment #3) > (In reply to Alexander Potashev from comment #2) > > "grep DTSTART ktimetracker.ics | sort" tells me, that the oldest regular > entries in my current ktimetracker.ics date back to May 2013. Though there > are some irregular entries, too: > > DTSTART:19800406T01 > DTSTART:19800928T03 > DTSTART:19810329T02 > DTSTART:19971026T03 Meanwhile I recognized that these do not belong to VTODO or VEVENT sections, so there's nothing wrong here probably. > I can try to anonymize my file and send it to you for testing. Unfortunately my email seems not to have reached you. Anyway, another observation: While ktimetracker is running, a lot of entries 'm_sessionStartTime= ""' appear in my system log. The time interval between the groups of these messages seems to correlate with the autosave interval. I cloned your git, extended the contents of the debug message and tried to compile the code to see if I can identify the tasks in ktimetracker that cause these messages. But I already failed at compilation stage. Even after a bunch of additions to the CMakeLists.txt I did not manage to get a working Makefile so I gave up eventually. If you can provide some explanation how the code is supposed to be compiled, I'll give it another try. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] New: Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 Bug ID: 420695 Summary: Dolphin crashes when closing terminal via "Close Session" Product: dolphin Version: 20.04.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: a...@neotop.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.04.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: To reproduce: 1. Open the terminal pane in dolphin 2. Attempt to close it vi the terminal context menu (right klick in terminal > "Close Session") This will crash Dolphin reliably Dolphin does not crash when the Teriminal is closed via the tool bar button. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f645265d800 (LWP 1050))] Thread 4 (Thread 0x7f642199a700 (LWP 1054)): #0 0x7f6451ed10b4 in __GI___libc_read (fd=18, buf=0x7f6421999b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f644399f2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f644395a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f644395a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f644395a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f644ba840db in QEventDispatcherGlib::processEvents (this=0x7f641c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f644ba2363a in QEventLoop::exec (this=this@entry=0x7f6421999da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f644b834317 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f644b8357ec in QThreadPrivate::start (arg=0x55b4fae273d0) at thread/qthread_unix.cpp:342 #9 0x7f6445d446db in start_thread (arg=0x7f642199a700) at pthread_create.c:463 #10 0x7f6451ee288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f642ab3b700 (LWP 1053)): #0 0x7f6445d4a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b4faaf9348) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b4faaf92f8, cond=0x55b4faaf9320) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b4faaf9320, mutex=0x55b4faaf92f8) at pthread_cond_wait.c:655 #3 0x7f642b63decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f642b63dac7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6445d446db in start_thread (arg=0x7f642ab3b700) at pthread_create.c:463 #6 0x7f6451ee288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6433557700 (LWP 1052)): #0 0x7f6451ed5bf9 in __GI___poll (fds=0x7f642c011f40, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f644395a5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f644395a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f644ba840db in QEventDispatcherGlib::processEvents (this=0x7f642c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f644ba2363a in QEventLoop::exec (this=this@entry=0x7f6433556d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f644b834317 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f644bf10555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f644b8357ec in QThreadPrivate::start (arg=0x7f644c188da0) at thread/qthread_unix.cpp:342 #8 0x7f6445d446db in start_thread (arg=0x7f6433557700) at pthread_create.c:463 #9 0x7f6451ee288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f645265d800 (LWP 1050)): [KCrash Handler] #6 0x7f644cdd9c03 in QListData::size (this=0x55b4fb0d2088) at ../../include/QtCore/../../src/corelib/tools/qlist.h:917 #7 QtPrivate::indexOf (from=0, u=@0x7ffebf886528: 0x55b4fb0ccd80, list=...) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1021 #8 QList::indexOf (from=0, t=@0x7ffebf886528: 0x55b4fb0ccd80, this=0x55b4fb0d2088) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1009 #9 QList::removeAll (this=0x55b4fb0d2088, _t=@0x7ffebf886528: 0x55b4fb0ccd80) at ../../include/QtCore/../../src/corelib/tools/qlist.h:919 #10 0x7f644ce13457 in QWidget::removeAction (this=0x55b4fb099530, action=) at kernel/qwidget.cpp:3173 #11 0x7f644f44d519 in KActionCollection::removeAssociatedWidget(QWidget*) () from
[kdevelop] [Bug 421120] New: Kdevelop crashed while typing if statement in C++
https://bugs.kde.org/show_bug.cgi?id=421120 Bug ID: 421120 Summary: Kdevelop crashed while typing if statement in C++ Product: kdevelop Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.6-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was writing an if statement, and when I had written the opening curly brace and a line feed, Kdevelop crashed. Reproducibility: Low. I have only had this a couple of times in about a month, and I'm using Kdevelop every day. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6713d9fcc0 (LWP 13448))] Thread 23 (Thread 0x7f66dcf47700 (LWP 15499)): #0 0x7f672309a4fc in read () from /lib64/libc.so.6 #1 0x7f67163a00f1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7f67172e0a0e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f67172e14b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f67172e1570 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f67172ef439 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f67163cdd78 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f6720755efa in start_thread () from /lib64/libpthread.so.0 #8 0x7f67230a93bf in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f66b27fc700 (LWP 13720)): #0 0x7f672075c795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f67234231db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f6723423299 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #3 0x7f671fcdd6b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f671fcdda1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #26 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #27 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #28 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #29 0x7f671fcd5cce in
[okular] [Bug 421235] No way to share annotations
https://bugs.kde.org/show_bug.cgi?id=421235 --- Comment #3 from Andreas Hurka --- Created attachment 128305 --> https://bugs.kde.org/attachment.cgi?id=128305=edit okular-file that cannot be saved as pdf with annotations -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421235] No way to share annotations
https://bugs.kde.org/show_bug.cgi?id=421235 --- Comment #4 from Andreas Hurka --- As I am not the one who created this file, but received a from a friend seeking help, I don't know exactly, what happened to it. With other files I can save the annotations. I'm sorry for not testing enough on that part in the beginning. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421235] New: No way to share annotations
https://bugs.kde.org/show_bug.cgi?id=421235 Bug ID: 421235 Summary: No way to share annotations Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: andr...@qvxb.de Target Milestone: --- SUMMARY It seems that there is currently no way to share annotations to pdf-files made in okular with users on other devices. All options remove / destroy them. STEPS TO REPRODUCE 1. open a pdf-document and add annotations like text and highlighter / open .okular-file with such annotations 2. try to save it in a way, that others can open it and see the annotations OBSERVED RESULT saving as .pdf seems to not be possible / supported saving as .okular results in the annotations moving to places they don't belong (probably a version-issue between manjaro-repos and neon-repos (just my guess)) and probably cannot be opened by other pdf-readers exporting as pdf removes annotations printing removes annotations EXPECTED RESULT having the option to save the annotations as part of the pdf-file SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: kde-neon 5.18 user edition / manjaro-kde user edition (both up to date) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION the annotations aren't there in html and Open-Document exports as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421235] No way to share annotations
https://bugs.kde.org/show_bug.cgi?id=421235 --- Comment #1 from Andreas Hurka --- My bad, I forgot to mention: It's version 1.10.0 of okular. I didn't specify it at the top, because the drop down menu stops with the 1.* at 1.9.80 and continues with 20.04.0, which I am not sure if it's the same as 1.10.0. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421235] No way to share annotations
https://bugs.kde.org/show_bug.cgi?id=421235 Andreas Hurka changed: What|Removed |Added Platform|Other |Neon Packages CC||andr...@qvxb.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #7 from Andreas Arnez --- Created attachment 126871 --> https://bugs.kde.org/attachment.cgi?id=126871=edit s390x: Fix register usage of conditional moves -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Andreas Kilgus changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #60 from Andreas Kilgus --- Not fixed here. Every time a mount or unmount occurs, memory consumption of running dolphin processes goes up by typically more than 200 K. With several automounters using idle timeouts for NAS exports and several running dolphins this sums up quite fast. As told in https://bugs.kde.org/show_bug.cgi?id=398908#c45, this is not specific to the NAS exports (NFS) but can be provoked identically by mounting and unmounting a USB flash drive. Plasma 5.18.3, Frameworks 5.68.0, Qt 5.14.1, Kernel 5.5.8. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418997] New: s390x: Support Iex_ITE for float and vector types
https://bugs.kde.org/show_bug.cgi?id=418997 Bug ID: 418997 Summary: s390x: Support Iex_ITE for float and vector types Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: ar...@linux.ibm.com Target Milestone: --- After fixing problems with the register allocation that affected "grail" on s390x (Bug 417281), "grail" still shows problems on s390x, due to missing support for Iex_ITE expressions for anything else but integer types. Failures look like this: ITE(t30,t31,t4) vex: the `impossible' happened: s390_isel_float_expr: cannot reduce tree -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 418997] s390x: Support Iex_ITE for float and vector types
https://bugs.kde.org/show_bug.cgi?id=418997 Andreas Arnez changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |ar...@linux.ibm.com Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #9 from Andreas Arnez --- (In reply to Julian Seward from comment #8) > For the NEVER case, it might be more "symmetrical" in relation to > the ALWAYS case, to say that it modifies dst, rather than saying > nothing. (I know it modifies it with the same value). Then > in effect the code says: > > NEVER= read dst, write dst; > ALWAYS = read src, write dst The rationale here was that NEVER results in no s390x instruction being emitted, so nothing is actually read or written. > although I think the absolute safest thing would be to put an assertion > in the construction for this insn to disallow NEVER and ALWAYS, since they > are degenerate cases, and I assume will never occur in practice. It seems that s390_isel_cc can at least theoretically yield NEVER or ALWAYS (in case of an Int1 constant, Ico_U1), so I guess I feel more comfortable with leaving support for that in right now. Unless it's guaranteed that Ico_U1 can't survive until isel? Of course, we could also handle these cases specially instead of always creating a conditional move. Perhaps I'll look into that later, but I prefer to do that independently from this bug. > Second point is .. are there any other cond-move insn variants? > FP, Vector etc? Not yet, but I guess I'll have to add them in order to fix the remaining "grail" fails on s390x. > +1 to land with any of the above changes you think are good (including none). OK, thanks for looking into this! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled
https://bugs.kde.org/show_bug.cgi?id=417281
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED|RESOLVED
--- Comment #10 from Andreas Arnez ---
Pushed as 942a48c1db83ffbcbf1f5781d5607f3b42849b67. This fixes the segfaults
in my testing.
("Grail" still shows problems on s390x, due to missing support for Iex_ITE
expressions for anything else but integer types. Opened Bug 418997 for this.)
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 --- Comment #1 from Andreas Hartmetz --- Created attachment 128687 --> https://bugs.kde.org/attachment.cgi?id=128687=edit Three restored and three newly opened tabs By logging out and back into a session, in which Konsole was open with three tabs, I got three restored tabs. Then I opened three new tabs with Ctrl-Shift-T. Observe the difference in tab color. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] New: Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Bug ID: 421906 Summary: Wrong tab colors after session restore Product: konsole Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- Created attachment 128686 --> https://bugs.kde.org/attachment.cgi?id=128686=edit Tab color settings page for affected session SUMMARY Wrong tab colors after session restore STEPS TO REPRODUCE 1. Open Konsole with any number of tabs (I have six) 2. End Plasma session (for me: shut down the computer) 3. Start new Plasma session (for me: turn on the computer) OBSERVED RESULT The color bar on the restored tabs is black EXPECTED RESULT The color bar on the tabs is light gray (application background color) - which is also the color of newly opened tabs (I use Ctrl-Shift-T). SOFTWARE/OS VERSIONS Linux/KDE Plasma: master as of today (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: compiled from sources, 5.14 branch (may be a few weeks old, almost nothing changed anyway) ADDITIONAL INFORMATION This might be a problem only with old Konsole configuration (Gustavo who did the tab color features might have deleted configuration several times during development, that is how it usually goes). The tab color setting in settings looks strange for me. See screenshot. The text says "user defined" in English. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Andreas Hartmetz changed: What|Removed |Added CC||gcarnei...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Andreas Hartmetz changed: What|Removed |Added CC||ahartm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 426029] [kmail] Segfault when trying to send an PGP encrypted email
https://bugs.kde.org/show_bug.cgi?id=426029
--- Comment #2 from Andreas Schneider ---
(gdb) bt full
#0 0x in ()
#1 0x7fff11cc170a in KMime::Headers::Base::is(char const*) const
(this=this@entry=0x586303b0, t=t@entry=0x7fff11cd9ff4 "Content-Type") at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_headers.cpp:153
#2 0x7fff11cc1767 in KMime::Content::headerByType(char const*) const
(this=this@entry=0x5861c300, type=0x7fff11cd9ff4 "Content-Type") at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:625
h = 0x586303b0
__for_range =
#3 0x7fff11cc1fa9 in
KMime::Content::header(bool) (create=true,
this=0x5861c300) at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.h:693
h =
#4 KMime::Content::contentType(bool) (this=this@entry=0x5861c300,
create=create@entry=true) at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:877
#5 0x7fff111581a6 in
MessageComposer::Util::composeHeadersAndBody(KMime::Content*, QByteArray,
Kleo::CryptoMessageFormat, bool, QByteArray const&) (orig=0x5861c300,
encodedBody=..., format=, sign=, hashAlgo=...) at
/usr/src/debug/messagelib-20.08.0-1.2.x86_64/messagecomposer/src/utils/util.cpp:89
vers =
boundary = {
d = 0x59113ed0
}
code = 0x59ccb1f0
result = 0x59ce1d10
#6 0x7fff110f9a64 in operator() (auditLogAsHtml=..., auditLogError=...,
cipherText=..., result=..., __closure=0x59d7e9e0) at
/usr/include/qt5/QtCore/qrefcount.h:60
d = 0x59ce1750
this = 0x59d8b3f0
#7 QtPrivate::FunctorCall,
QtPrivate::List, void,
MessageComposer::EncryptJob::process():: >::call
(arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#8 QtPrivate::Functor, 4>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#9
QtPrivate::QFunctorSlotObject, 4, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x59d7e9d0, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x76be6116 in () at /usr/lib64/libQt5Core.so.5
#11 0x7fff10bfe0b1 in QGpgME::EncryptJob::result(GpgME::EncryptionResult
const&, QByteArray const&, QString const&, GpgME::Error const&) () at
/usr/lib64/libqgpgme.so.7
#12 0x7fff10c15452 in QGpgME::_detail::ThreadedJobMixin
>::slotFinished() () at /usr/lib64/libqgpgme.so.7
#13 0x76bdbb61 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#14 0x777070cf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#15 0x76bafc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#16 0x76bb2661 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#17 0x76c079f3 in () at /usr/lib64/libQt5Core.so.5
#18 0x7fffede0d2b7 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#19 0x7fffede0d638 in () at /usr/lib64/libglib-2.0.so.0
#20 0x7fffede0d6ef in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#21 0x76c0707f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#22 0x76bae5fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x76bb6860 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#24 0x8fc7 in ()
#25 0x76579cca in __libc_start_main () at /lib64/libc.so.6
#26 0x961a in ()
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 --- Comment #2 from Andreas Nordal --- I have the same symptom with Kdevelop 5.6.0 – sigsegv when parsing the project. I ran kdevelop in gdb to get the backtrace. I did this 3 times to see if it segfaults at the same place every time, and it seems so: clang::InjectedClassNameType::getDecl in tools/clang/lib/AST/Type.cpp:3387 This happens in an extremely deep recursion inside libclang-10: The two functions TransformTypos::RecursiveTransformLoop and TransformTypos::CheckForRecursiveTypos are running in tandem 23214 or 20548 times (not the same every time) before calling the series of functions that lead to the segfault. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 Andreas Nordal changed: What|Removed |Added CC||andreas_norda...@hotmail.co ||m --- Comment #1 from Andreas Nordal --- Created attachment 131672 --> https://bugs.kde.org/attachment.cgi?id=131672=edit Kdevelop backtrace -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 426538] current git master 5.7.0-13 crashes when clicking on the datebar below the histogram
https://bugs.kde.org/show_bug.cgi?id=426538 --- Comment #7 from Andreas Schleth --- I can confirm that this fix solves this issue. That was quick! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 426538] New: current git master 5.7.0-13 crashes when clicking on the datebar below the histogram
https://bugs.kde.org/show_bug.cgi?id=426538 Bug ID: 426538 Summary: current git master 5.7.0-13 crashes when clicking on the datebar below the histogram Product: kphotoalbum Version: GIT master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Datebar Assignee: kpab...@willden.org Reporter: schleth...@web.de Target Milestone: --- Created attachment 131651 --> https://bugs.kde.org/attachment.cgi?id=131651=edit screenshot with marked area that causes the crash Reproducibly, KPA crashes, when I click somewhere on the date bar below the histogram. It even gives some sort of error message: ... [100%] Built target kphotoalbum ((then my script starts kphotoalbum --demo)) QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... Unable to start Dr. Konqi (( this from my system)) Re-raising signal for core dump handling. ASSERT failure in DateBarWidget::unitAtPos: "horizontal offset larger than m_barWidth!", file /home/usr/src/kphotoalbum-git/kphotoalbum/DateBar/DateBarWidget.cpp, line 835 KCrash: Application 'kphotoalbum' crashing... Linux/KDE Plasma: openSuse Leap 15.2 (available in About System) KDE Plasma Version: 5.71.0 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 426029] New: [kmail] Segfault when trying to send an PGP encrypted email
https://bugs.kde.org/show_bug.cgi?id=426029 Bug ID: 426029 Summary: [kmail] Segfault when trying to send an PGP encrypted email Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: a...@cryptomilk.org Target Milestone: --- SUMMARY I get a segfault when trying to send an PGP encrypted email: Thread 1 (Thread 0x7fffe62b5040 (LWP 11283)): #0 0x7fff164c2707 in KMime::Headers::Base::is(char const*) const (this=this@entry=0x58b5bc90, t=t@entry=0x7fff164daff4 "Content-Type") at /usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_headers.cpp:153 #1 0x7fff164c2767 in KMime::Content::headerByType(char const*) const (this=this@entry=0x58e7ce10, type=0x7fff164daff4 "Content-Type") at /usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:625 h = 0x58b5bc90 __for_range = #2 0x7fff164c2fa9 in KMime::Content::header(bool) (create=true, this=0x58e7ce10) at /usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.h:693 h = #3 KMime::Content::contentType(bool) (this=0x58e7ce10, create=) at /usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:877 #4 0x7fff159591a6 in () at /usr/lib64/libKF5MessageComposer.so.5 #5 0x7fff158faa64 in () at /usr/lib64/libKF5MessageComposer.so.5 #6 0x76be6116 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fff153ff0b1 in QGpgME::EncryptJob::result(GpgME::EncryptionResult const&, QByteArray const&, QString const&, GpgME::Error const&) () at /usr/lib64/libqgpgme.so.7 #8 0x7fff15416452 in QGpgME::_detail::ThreadedJobMixin >::slotFinished() () at /usr/lib64/libqgpgme.so.7 #9 0x76bdbb61 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x777070cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x76bafc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x76bb2661 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #13 0x76c079f3 in () at /usr/lib64/libQt5Core.so.5 #14 0x7fffede0d2b7 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #15 0x7fffede0d638 in () at /usr/lib64/libglib-2.0.so.0 #16 0x7fffede0d6ef in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #17 0x76c0707f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #18 0x76bae5fb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x76bb6860 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #20 0x8fc7 in () #21 0x76579cca in __libc_start_main () at /lib64/libc.so.6 #22 0x961a in () STEPS TO REPRODUCE 1. Open Kmail 2. Write a mail and select PGP/GPG encryption and send it SOFTWARE/OS VERSIONS openSUSE Tumbleweed KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 KMail: 5.15.0 (20.08.0) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425324] Trusted links in email messages result in error code below.
https://bugs.kde.org/show_bug.cgi?id=425324 Andreas Kohlbecker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||a...@neotop.de --- Comment #2 from Andreas Kohlbecker --- After upgrading to focal 20.05 with Plasma 5.19.5 I am having the same issue. KIO attempts to open the browser by executing '/usr/bin/_neon.firefox' which does not exists. The symlink in actually is '/usr/bin/firefox'. This results in the error reported here. This is reproducible in Element (matrix client), kmail, dolphin. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425324] Trusted links in email messages result in error code below.
https://bugs.kde.org/show_bug.cgi?id=425324 --- Comment #3 from Andreas Kohlbecker --- The problem can be solved by manually switching the default browser to a different application and then back to firefox: System Settings > Default Applications > Web Browser This fix only removes the symptom. It is unclear why and how the default application setting has been corrupted and if other settings are affected in the same way. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 427760] New: KPA git master crashes if videothumbnails of more than one video at once are advanced by crtl+"+"
https://bugs.kde.org/show_bug.cgi?id=427760 Bug ID: 427760 Summary: KPA git master crashes if videothumbnails of more than one video at once are advanced by crtl+"+" Product: kphotoalbum Version: GIT master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnail Viewer Assignee: kpab...@willden.org Reporter: schleth...@web.de Target Milestone: --- Created attachment 132387 --> https://bugs.kde.org/attachment.cgi?id=132387=edit KDE crash report SUMMARY STEPS TO REPRODUCE 0. You nee a DB with a few videos with proper video thumbnails to start with. 1. select two or more videos with video thumbnails in the browser (can't do this with the demo as it only has one video). 2. click crtl-"+" or crtl-"-" to select the next or the previous thumbnail as the static thumbnail image OBSERVED RESULT 3. crash. EXPECTED RESULT no crash and the next image should be the static image. Funny, enough the same operation seems to work sometimes. When selecting only one video the operation seems to work. I just tested again and it worked a few times with two videos selected and then crashed again when dealing with two other videos. Each of which could be advanced one by one without crash. Dr. Konqui has provided a crash report (attachment). KPA v5.7.0-25-gd2af41aa KDE Frameworks 5.71.0 Qt 5.12.7 (kompiliert gegen 5.12.7) Das xcb Fenstersystem -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404076] s390x: z14 vector instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=404076 Andreas Arnez changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |ar...@linux.ibm.com Status|REPORTED|CONFIRMED --- Comment #4 from Andreas Arnez --- Created attachment 132244 --> https://bugs.kde.org/attachment.cgi?id=132244=edit s390x: Support for z14 (arch12) vector instructions This is a first version of z14 vector instruction support, as outlined in comment #1. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 426705] New: game stored in 0.8 loaded in 0.9 shows inconsistencies and crashes
https://bugs.kde.org/show_bug.cgi?id=426705 Bug ID: 426705 Summary: game stored in 0.8 loaded in 0.9 shows inconsistencies and crashes Product: kmahjongg Version: 0.9 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: andreas.koenig.7os6v...@franz.ak.mind.de CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 131757 --> https://bugs.kde.org/attachment.cgi?id=131757=edit Kmahjongg Game in binary format as described in the report SUMMARY STEPS TO REPRODUCE 1. Load the game from the attached file 2088946915-saved-on-0.8-crashing-on-0.9.kmgame (this file has been produced with a kmahjongg version 0.8 on Ubuntu 16.04) 2. Press Undo 14 times 3. OBSERVED RESULT The first 13 Undo clicks restore pairs of not matching tiles, the fourteenth Undo crashes KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmahjongg path = /usr/games pid = 1291178 KCrash: Arguments: /usr/games/kmahjongg KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSystemTrayIcon::setVisible: No Icon set EXPECTED RESULT Any Undo click should restore the (matching) pairs as they have been played and stored in the file. SOFTWARE/OS VERSIONS KDE Frameworks Version: Package: kde-runtime Version: 4:17.08.3-2.1 Qt Version: Package: libqtcore4 Version: 4:4.8.7+dfsg-20 ADDITIONAL INFORMATION The attached file was produced by kmahjongg 0.8 and has not been tampered. The game number was 2088946915 in the set of solvable games. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 426705] game stored in 0.8 loaded in 0.9 shows inconsistencies and crashes
https://bugs.kde.org/show_bug.cgi?id=426705 Andreas Koenig changed: What|Removed |Added CC||andreas.koenig.7os6vvqr@fra ||nz.ak.mind.de --- Comment #2 from Andreas Koenig --- Created attachment 131956 --> https://bugs.kde.org/attachment.cgi?id=131956=edit Same game stored by kmahjongg 0.9 in current binary format As a reference, I attach the same game played on 0.9 and then stored from there. Maybe you know of a good converter from binary to something human readable, that might reveal something interesting? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] New: Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 Bug ID: 422159 Summary: Akonadi crashes often and can't be restarted Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY Since I installed Kubuntu 20.04, akonadi has crashed once a day and cannot be started again. Akonadi only runs again after a reboot.But it is getting worse, today akonadi has crashed three times. According to the crash tracking, the data of the backtrace are useless STEPS TO REPRODUCE 1.Start akonadi (Kontact) 2.Wait (work with the machine or do nothing) 3. OBSERVED RESULT After a while, akonadi crashes. EXPECTED RESULT Working akonadi SOFTWARE/OS VERSIONS Kubuntu 20.04 LTS Focal Fossa Linux/KDE Plasma:5.4.0-31 generic/5.18.5 (available in About System) KDE Plasma Version:5.18.5 KDE Frameworks Version: 5.68.0 Qt Version:5.12.8 ADDITIONAL INFORMATION Maybe the information about my machine is useful: CPU: AMD Ryzen 5 2400G Motherboard: MSI B450 Gaming pro Carbon ac RAM:16 GB Separate / and / home directory on / dev / nvme0n1 (Samsung SSD 970 EVO Plus 500GB) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #2 from Andreas Hencke --- Not yet, because of the backtraces were marked as useless so I didn't saved one. Right now akonadi crashed again, this time dr. konqi didn't start aswell. I tryed to start akonadi via Konsole and got this output: andreas@rex-PC:~$ akonadictl stop Akonadi is not running. andreas@rex-PC:~$ akonadictl start org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now. Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! I'll report a backtrace asap! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #3 from Andreas Hencke --- Created attachment 128899 --> https://bugs.kde.org/attachment.cgi?id=128899=edit Backtrace from Dr Konqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #4 from Andreas Hencke --- This is a backtrace from my other Desktop machine. It has a MSI A320m motherboard and a Ryzen5 2400G CPU. / and /home are splitted as in the other machine. One point might be importandt: On this machine I installed Kubuntu 20.04 in January from a daily iso, Up to the official release of Kubuntu 20.04 akonadi was working prperly without an issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 Andreas Hencke changed: What|Removed |Added Attachment #128899|0 |1 is obsolete|| --- Comment #6 from Andreas Hencke --- Created attachment 128920 --> https://bugs.kde.org/attachment.cgi?id=128920=edit Here is the missing backtrace Sorry, forr sending the the wrong content as an attachment. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 --- Comment #7 from Andreas Hartmetz --- Great job, thanks for fixing it so quickly! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 428106] No download button in internal pdf viewer.
https://bugs.kde.org/show_bug.cgi?id=428106 --- Comment #2 from Andreas Hurka --- Yes, this isn't a bug. I just have no idea how to mark this as a feature request or wish list item. Is taht even my job? Rightclicking pdf links and saving them works and shows, that the feature itself is already existent - just not in the viewer. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 Andreas Ermler changed: What|Removed |Added CC||aerm...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428095] Drop menu has no borders
https://bugs.kde.org/show_bug.cgi?id=428095 --- Comment #7 from Andreas H --- Created attachment 132782 --> https://bugs.kde.org/attachment.cgi?id=132782=edit Drag Menu With KWin Console -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428095] Drop menu has no borders
https://bugs.kde.org/show_bug.cgi?id=428095 Andreas H changed: What|Removed |Added CC||andreas.harat...@gmail.com --- Comment #6 from Andreas H --- Hey all! Thanks for bringing this up. I've been looking into this for a bit but I'm having a hard time tracking down the root cause. It appears that some transparent menus in X11 (like the drop menu) are totally missing an alpha channel! See my attachment with the KWin debug console. I think my fix moved the glitch into the border; though it isn't the reason those windows are lacking transparency. These windows seem fine in Wayland, except for the "More Actions" KWin menu. I think this could be an issue in Breeze, or Qt. If anyone has any ideas I'm all ears -- You are receiving this mail because: You are watching all bug changes.
