[kio-extras] [Bug 428369] Refresh View does not always refresh with sftp
https://bugs.kde.org/show_bug.cgi?id=428369 --- Comment #3 from Ernst Jendritzki --- This Happens quite often. Contao Forum says that sftp does caching and it usually takes time to refresh. I think caching is not appropriate as we do want accurate information and not old ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386101] Firefox crashing if launched from plasmashell
https://bugs.kde.org/show_bug.cgi?id=386101 Alexander Trufanov changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Alexander Trufanov --- I can't reproduce this anymore -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429112] Unsynchronizing clock throws error
https://bugs.kde.org/show_bug.cgi?id=429112 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/242 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 379264] Cyrilic encoding of access points in KDialog from Qt4 breaks regularly
https://bugs.kde.org/show_bug.cgi?id=379264 Justin Zobel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Justin Zobel --- Thanks Mikhail, I'll resolve this bug report then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Wayland+, X11- --- Comment #4 from Duncan <1i5t5.dun...@cox.net> --- A comment on another bug made me aware of the wayland/X flags, use 'em. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427433] Unable to run QProcess: invalid file descriptor in syscall clone()
https://bugs.kde.org/show_bug.cgi?id=427433 Paul Floyd changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #14 from Paul Floyd --- Looking more didn't help that much. I wasn't able to get GDB to stop where the error occurs. My conclusion is that this is due to some compiler or linker optimization. Closing this for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429580] New: Can't change screen brightness - OSD appears but brightness does not change
https://bugs.kde.org/show_bug.cgi?id=429580 Bug ID: 429580 Summary: Can't change screen brightness - OSD appears but brightness does not change Product: plasmashell Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: el...@seznam.cz CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I try to change brightness via shortcut Fn+F2/F3, OSD appears, but brightness doesn't change. Only 0 % works, which turns display off. This used to work, but I'm not sure which update broke it. I think I was trying smooth brightness change in 5.20.0 and it worked, so maybe some of the later updates. Changing brightness via Energy Saving doesn't work either. Also I tried lxqt-brightness. Lowering brightness worked fine, raising brightness did work, but looked like it was changing gamma rather than backlight intensity. STEPS TO REPRODUCE 1. Start plasma 2. Use Fn+F2/F3 to change brightness OBSERVED RESULT Brightness does not change. EXPECTED RESULT Brightness should change. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro testing KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429155] Data Range Option isn't preserved
https://bugs.kde.org/show_bug.cgi?id=429155 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/101 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429167] Appearance options aren't preserved
https://bugs.kde.org/show_bug.cgi?id=429167 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/101 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429580] Can't change screen brightness - OSD appears but brightness does not change
https://bugs.kde.org/show_bug.cgi?id=429580 --- Comment #1 from el...@seznam.cz --- I tried changing brightness in Windows 10 and it worked OK. So no hardware failure. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 429581] New: Add these symbols to new Flowchart category (attached odg)
https://bugs.kde.org/show_bug.cgi?id=429581 Bug ID: 429581 Summary: Add these symbols to new Flowchart category (attached odg) Product: karbon Version: 3.0 Alpha Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: usability Assignee: ja...@gmx.net Reporter: terti...@expertmultimedia.com Target Milestone: --- Created attachment 133601 --> https://bugs.kde.org/attachment.cgi?id=133601&action=edit You can copy the symbols from here and add them to the program I am using nightly #968. SUMMARY I attached some symbols I made that you can use for a new Flowcharts category in "Add Shape" STEPS TO REPRODUCE 1. Add Shape OBSERVED RESULT No flowchart category EXPECTED RESULT Flowchart category SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 429582] New: Add these symbols to new Data Flow Diagram category (attached odg)
https://bugs.kde.org/show_bug.cgi?id=429582 Bug ID: 429582 Summary: Add these symbols to new Data Flow Diagram category (attached odg) Product: karbon Version: 3.0 Alpha Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: usability Assignee: ja...@gmx.net Reporter: terti...@expertmultimedia.com Target Milestone: --- Created attachment 133602 --> https://bugs.kde.org/attachment.cgi?id=133602&action=edit You can copy the symbols from here and add them to the program Related to #429581 I am using nightly #968. SUMMARY I attached some symbols I made that you can use for a new Data Flow Diagram category in "Add Shape" STEPS TO REPRODUCE 1. Add Shape OBSERVED RESULT No Data Flow Diagram category EXPECTED RESULT Data Flow Diagram category SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429583] New: Pictures in kio5.pot should be Images
https://bugs.kde.org/show_bug.cgi?id=429583 Bug ID: 429583 Summary: Pictures in kio5.pot should be Images Product: dolphin Version: 20.08.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: freekdekru...@kde.nl CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Apparently Pictures in Places comes from kio5.pot and refers to the folder Images in the Home folder of the user. In localized Home folders Images is localized. In my view it is wrong to have two names, Pictures and Images, referring to the same folder. Better would be to have one place with the translation for the name of the folder with images. STEPS TO REPRODUCE 1. Start Dolphin 2. In places the term Pictures appears when clicking on it the folder Images is opened. 3. OBSERVED RESULT 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.
[plasmashell] [Bug 414834] Plasma crashes on Wayland when I change global theme
https://bugs.kde.org/show_bug.cgi?id=414834 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #14 from Patrick Silva --- This Plasma crash have just happened again on neon unstable when I changed global theme from Breeze Twilight to Breeze. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.1 Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 76668] [New LWP 76765] [New LWP 76781] [New LWP 76782] [New LWP 76783] [New LWP 76784] [New LWP 76832] [New LWP 76835] [New LWP 76837] [New LWP 76838] [New LWP 76839] [New LWP 76843] [New LWP 76879] [New LWP 76956] [New LWP 77267] [New LWP 77327] [New LWP 77328] [New LWP 78438] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f3a0107caff in __GI___poll (fds=fds@entry=0x7ffdb8194528, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f39fd2e02c0 (LWP 76618))] Thread 19 (Thread 0x7f39917fa700 (LWP 78438)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e7dcea5310) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e7dcea52c0, cond=0x55e7dcea52e8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e7dcea52e8, mutex=0x55e7dcea52c0) at pthread_cond_wait.c:638 #3 0x7f3a0140fceb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55e7dcea52c0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55e7e27e7408, mutex=mutex@entry=0x55e7e27e7400, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f3a031a4774 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55e7e27e73f8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55e7e27e7360) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f3a031a4be9 in QSGRenderThread::run() (this=0x55e7e27e7360) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f3a01409b1c in QThreadPrivate::start(void*) (arg=0x55e7e27e7360) at thread/qthread_unix.cpp:329 #9 0x7f3a0046f609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f3a01089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f39927fc700 (LWP 77328)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f3980001960) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f3980001910, cond=0x7f3980001938) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f3980001938, mutex=0x7f3980001910) at pthread_cond_wait.c:638 #3 0x7f3a0140fceb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f3980001910) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55e7d10eeb08, mutex=mutex@entry=0x55e7d10eeb00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f3a031a4774 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55e7d10eeaf8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55e7d10eea60) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f3a031a4be9 in QSGRenderThread::run() (this=0x55e7d10eea60) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f3a01409b1c in QThreadPrivate::start(void*) (arg=0x55e7d10eea60) at thread/qthread_unix.cpp:329 #9 0x7f3a0046f609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f3a01089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f3992ffd700 (LWP 77327)): #0 __GI___libc_read (nbytes=10, buf=0x7f3992ffcb1e, fd=48) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=48, buf=0x7f3992ffcb1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f39d4a84975 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f39d4d49416 in pa_mainloop_prepare () at /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f39d4d49eb4 in pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f39d4d49f70 in pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f39d4d5811d in () at /lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f39d4ab372c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f3a0046f609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3a01089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Threa
[krita] [Bug 429578] Could not synchronize with the database
https://bugs.kde.org/show_bug.cgi?id=429578 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/4eb957740 ||19fdbf091a17725637ef4fdde52 ||d22b Status|REPORTED|RESOLVED --- Comment #2 from Boudewijn Rempt --- Git commit 4eb95774019fdbf091a17725637ef4fdde52d22b by Boudewijn Rempt. Committed on 24/11/2020 at 09:06. Pushed by rempt into branch 'master'. Add a fallback name for resources that have no name M +1-0libs/resources/KoResource.cpp https://invent.kde.org/graphics/krita/commit/4eb95774019fdbf091a17725637ef4fdde52d22b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417983] Nothing happens when "Use" button of GHNS window is clicked
https://bugs.kde.org/show_bug.cgi?id=417983 --- Comment #8 from Alexander Lohnau --- Git commit 07cf18a6b8ca50c65225daca9c1941ff2e2e54ab by Alexander Lohnau. Committed on 24/11/2020 at 09:02. Pushed by alex into branch 'master'. Reload KCM when entry was adopted This solves the UI sync issues when using the adoption command. M +3-6kcms/icons/main.cpp M +1-1kcms/icons/main.h M +6-1kcms/icons/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/commit/07cf18a6b8ca50c65225daca9c1941ff2e2e54ab -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 288493] Add templates for Karbon
https://bugs.kde.org/show_bug.cgi?id=288493 Expert Multimedia changed: What|Removed |Added CC||tertiary@expertmultimedia.c ||om --- Comment #1 from Expert Multimedia --- I have odg files for Flowchart and Data Flow Diagram (DFD) on the following issues (the symbols would be split out for those feature requests, but each of the 2 documents can be used as a whole and used for this issue if saved as template as-is): - https://bugs.kde.org/show_bug.cgi?id=429581 - https://bugs.kde.org/show_bug.cgi?id=429582 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429580] Can't change screen brightness - OSD appears but brightness does not change
https://bugs.kde.org/show_bug.cgi?id=429580 --- Comment #2 from el...@seznam.cz --- Booting with latest Kernel 5.4 LTS solved the issue. So it seems problem lies with kernel and not Plasma. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429566] Certain text in menus dissapearing
https://bugs.kde.org/show_bug.cgi?id=429566 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Severity|major |normal Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- This can happen when testing different versions of Krita. Are you on Windows or on ChromeOS? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429298] No window decoration is highlighted in Window Decorations KCM
https://bugs.kde.org/show_bug.cgi?id=429298 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Patrick Silva --- it's still reproducible. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429371] Impossible to assign tag to a brush in master
https://bugs.kde.org/show_bug.cgi?id=429371 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|ASSIGNED CC||b...@valdyas.org Assignee|krita-bugs-n...@kde.org |b...@valdyas.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429298] No window decoration is highlighted in Window Decorations KCM
https://bugs.kde.org/show_bug.cgi?id=429298 --- Comment #7 from David Redondo --- Does Neon build plasma-workspace with breeze kdecoration available? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429580] Can't change screen brightness - OSD appears but brightness does not change
https://bugs.kde.org/show_bug.cgi?id=429580 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379584] Old "delete" shortcut doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=379584 luisfe changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from luisfe --- I cannot reproduce the problem in kmail 5.15.2, supr, shift+supr, ctrl+supr, ctrl+shift+supr all work as expected. The bug can be closed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429530] KIO::iconNameForUrl() returns wrong icon for mimetype
https://bugs.kde.org/show_bug.cgi?id=429530 Méven Car changed: What|Removed |Added CC||meven@enioka.com --- Comment #5 from Méven Car --- I believe https://phabricator.kde.org/D27539 caused this. Prior to it `db.mimeTypeForUrl(url).iconName();` would become the default icon for non-local files. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 429584] New: growisofs crashes @ 99%
https://bugs.kde.org/show_bug.cgi?id=429584
Bug ID: 429584
Summary: growisofs crashes @ 99%
Product: k3b
Version: 19.12
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Burning/Hardware
Assignee: k...@kde.org
Reporter: i.proud...@oxon.org
CC: mich...@jabster.pl, tr...@kde.org
Target Milestone: ---
SUMMARY
Burning .iso file to DVD-R fails when growisofs reaches 99% independent of file
size, media and hardware. Windows 10 virtual machine with same hardware OK.
Writing to a DVD-RW is OK.
STEPS TO REPRODUCE
1. Insert blank DVD-R into optical drive.
2. Use K3b to burn .iso file.
OBSERVED RESULT
K3b raises an error. Debug information shows:
growisofs: 7.1
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: engaging DVD-R DAO upon user request...
/dev/sr0: reserving 1938739 blocks
/dev/sr0: "Current Write Speed" is 8.2x1352KBps.
..
4511236096/4546260992 (99.2%) @11.9x, remaining 0:03 RBU 100.0% UBU 99.6%
:-[ WRITE@LBA=21df40h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument
:-( write failed: Invalid argument
/dev/sr0: flushing cache
EXPECTED RESULT
.iso file copied to DVD-R
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Ubuntu 20.04.1 LTS
Linux 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
growisofs: 7.1
ADDITIONAL INFORMATION
I have two PCs both running Kubuntu 20.04.1. Both are the result of an upgrade
from Kubuntu 18.04. They have different motherboards and slightly different
optical drives: Samsung SH-S223F & SH-S223B.
I generated a .iso file. 4.511 GB.
Burning the same .iso file to Verbatim 16x DVD-R disks fails on both machines.
On the machine with the SH-S223Bdrive:
Burning the same .iso file to a 4x Philips DVE-RW works.
Burning the same .iso file to an Imation 8x DVD-R disks fails.
This PC has VirtualBox installed and a Windows 10 virtual machine. Burning the
.iso file to a Verbatim 16x DVD-R disk works.
NB. I manually set the writing speed since K3b detected the wrong speed on the
Verbatim disks. They are 16x and K3b initially tried to use 21x. I tried 12x
and 8x with the Verbatim disks without success. I used 8x for the Imation disk.
The 4.511 GB .iso file nearly fills the DVD-r (4.7 GB) so I generated a smaller
.iso file: 3.927 GB.
This also failed:
growisofs
………..
3927834624/3970537472 (98.9%) @8.0x, remaining 0:04 RBU 100.0% UBU 99.7%
:-[ WRITE@LBA=1d9530h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument
:-( write failed: Invalid argument
/dev/sr0: flushing cache
The dmesg output was:
[21592.617939] ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6
frozen
[21592.617946] ata6.00: irq_stat 0x0800, interface fatal error
[21592.617952] ata6: SError: { UnrecovData Handshk }
[21592.617969] ata6.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 31 dma
32768 out
Write(10) 2a 00 00 1d 95 30 00 00 03 00res
50/00:03:00:00:80/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[21592.617973] ata6.00: status: { DRDY }
[21592.617979] ata6: hard resetting link
[21592.932935] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[21592.933932] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[21592.933948] No Local Variables are initialized for Method [_GTF]
[21592.933950] No Arguments are initialized for method [_GTF]
[21592.933954] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20190816/psparse-529)
[21592.934768] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[21592.934782] No Local Variables are initialized for Method [_GTF]
[21592.934784] No Arguments are initialized for method [_GTF]
[21592.934787] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20190816/psparse-529)
[21592.934803] ata6.00: configured for UDMA/100
[21592.935080] ata6: EH complete
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 429171] wayland: window rules, no titlebar and frame, won't auto-apply
https://bugs.kde.org/show_bug.cgi?id=429171 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Wayland+, X11- --- Comment #5 from Duncan <1i5t5.dun...@cox.net> --- Adding flags +wayland -X11, plus this reply... (In reply to Thiago Sueto from comment #3) > I can partially reproduce: > > 1) Window rules are not remembered after closing <-- 100% reproducible with > Qt/KDE and GTK3 apps Thanks. > 2) Force titlebar is remembered for GTK2 apps (tried Claws) <-- Cannot > reproduce Hmm. I wonder if it's working here for claws due to the title update thing? Do you have a mail account setup in it? Presumably it starts with a generic title and updates it to include the default email account. That could trigger the title update... The other thing... your claws is still gtk2/X-based, coming up on wayland via xwayland, right? Mine is. Last I looked into it the claws folks were working on gtk3 and presumably native wayland support with it, but that was probably 6 months or a year ago. I've not looked at it since, and definitely not since switching to kde/plasma-wayland. But if they've updated and the openSUSE tumbleweed build is gtk3/native-wayland that might explain the difference. Definitely more testing required for X/gtk2/etc to see what the difference is here. I just tried xev, being the one X-based app I could think of off the top of my head, and couldn't get the titlebar to force off for it, but it's "strange" in that the window-rules detection couldn't find a window-class for it, and of course it doesn't appear to change window title so I can't test that part of it. I'll have to try some others... > 3) If includes title, rule works after updating title <-- Cannot reproduce Hmm. That's pretty solid here. In fact, for one thing I run here, a text-based pdmenu in a konsole window, FWIW, due to this bug I'm actually having to deliberately script a title change via konsole/xterm escape sequences in ordered to trigger the detection and turn off the titlebar.[1] But if my theory above that my seeing claws obey no-titlebar rules, possible because of a title change I wasn't aware was happening, is correct, then if a title change isn't triggering no-titlebar rule enforcement for you, it would explain that too. Meanwhile, another development, but I'll put that in a different comment. --- [1] pdmenu was designed as a text-based menu and pops up in the middle of the terminal. It has customizable colors, and between them, setting konsole command-line switches for no toolbars/tabbars/scrollbars, and using a custom konsole color-scheme with a 100% transparent background (the menu itself has a background color set so it's not transparent, but the rather bigger konsole window it's appearing in is), I can make it appear as if the relatively small text-based menu is popping up by itself, not in the much bigger konsole/terminal window it's actually in -- as long as the titlebar doesn't appear to destroy the illusion. -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 414281] kcolorchooser always show color from first display on multihead system
https://bugs.kde.org/show_bug.cgi?id=414281 --- Comment #6 from Victor Prudniy --- KColorChooser Version 20.08.3 still occurring -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429171] wayland: window rules, no titlebar and frame, won't auto-apply
https://bugs.kde.org/show_bug.cgi?id=429171 --- Comment #6 from Duncan <1i5t5.dun...@cox.net> --- After yesterday's update, things improved incrementally. I'm not sure what exactly triggered the improvement, but... kwin seems to notice changes in windows and reapply its rules more often now, often triggering no-titlebar if it's set, when it wouldn't before. My /theory/ is that it's noticing when window titles are set, even if they don't actually change from whatever they were set to before, now, whereas before, it would only notice changes if the window title actually changed, not if it was set to the same value it had before. Noticed in kpat and ksudoku, which start with a titlebar now despite a window rule turning it off for them, but which switch to no-titlebar mode, for instance when I start a game. While that happened before if the window title changed, now two reevaluations seem to be triggered, the first of which turns off the titlebar but doesn't reset the window size resulting in a shorter window than the set size because it's accounting for the titlebar which isn't there now, the second of which resets the size to that set by the rule as well. Before, it was only one triggered reevaluation. I can _guess_ that the one trigger sets the title to the same value it had before so it didn't trigger before, leaving on the trigger that actually changed the title, while now they both trigger. But of course since the title doesn't change with the one trigger, it's difficult to /prove/ that, leaving me /guessing/ as to the reasons for the now observed second observed trigger. And while I did read the git log for kwin and some of the updated frameworks (as I routinely do), no single commit log leapt out at me as the reason for the improvement. But it's nice to have, regardless. =:^) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429168] wayland: taskmanager and icons-only taskmanager only show pinned, no running
https://bugs.kde.org/show_bug.cgi?id=429168 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Wayland+, X11- --- Comment #1 from Duncan <1i5t5.dun...@cox.net> --- Setting flags +wayland -x11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429530] KIO::iconNameForUrl() returns wrong icon for mimetype
https://bugs.kde.org/show_bug.cgi?id=429530 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/227 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425864] Aurorae-based windecos vanishing with libglvnd
https://bugs.kde.org/show_bug.cgi?id=425864 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Wayland-, X11+ --- Comment #4 from Duncan <1i5t5.dun...@cox.net> --- Setting flags +X11 -wayland Switched to kde/plasma on wayland now. Generally only starting plasma on X when testing whether some bug showing up on wayland is on X as well, but (as commented on the 18th) the problem was still there on X as of a few days ago. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429468] Screen locker shows clock despite "Clock" being unchecked in Screen Locking KCM
https://bugs.kde.org/show_bug.cgi?id=429468 --- Comment #2 from Patrick Silva --- humm, I can reproduce on neon unstable even with a new user account. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 382681] Crash playing a larger quicktime movie
https://bugs.kde.org/show_bug.cgi?id=382681 Ben Cooksley changed: What|Removed |Added CC|mwhemb...@comcast.net | --- Comment #22 from Ben Cooksley --- Unsubscribing user per abuse report we received. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 Gerrit changed: What|Removed |Added CC||g...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429585] New: Plasma crash when navigating Memory Usage widget settings
https://bugs.kde.org/show_bug.cgi?id=429585 Bug ID: 429585 Summary: Plasma crash when navigating Memory Usage widget settings Product: plasmashell Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-29-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I have added a Memory Usage widget on a horizontal panel and opened its settings window. In the Appearance tab, I switched Display Style to Bar chart and slicked Apply. Then I tried to switch to the Bar Chart Details tab and Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x55a40065 in () #5 0x7f95c915a75b in qQmlPropertyCacheProperty(QJSEngine*, QObject*, QV4::String const*, QQmlContextData*, QQmlPropertyData&) (engine=, obj=obj@entry=0x55a1945a4f40, name=0x7ffcff529290, name@entry=0x7f95c014f598, context=context@entry=0x55a18faa4620, local=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:647 #6 0x7f95c9155f89 in QQmlPropertyCache::property(QJSEngine*, QObject*, QV4::String const*, QQmlContextData*, QQmlPropertyData&) (engine=, obj=obj@entry=0x55a1945a4f40, name=name@entry=0x7f95c014f598, context=context@entry=0x55a18faa4620, local=...) at qml/qqmlpropertycache.cpp:1032 #7 0x7f95c904ff37 in QV4::QObjectWrapper::findProperty(QV4::ExecutionEngine*, QObject*, QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QQmlPropertyData*) (engine=engine@entry=0x55a18c9ee3d0, o=o@entry=0x55a1945a4f40, qmlContext=qmlContext@entry=0x55a18faa4620, name=name@entry=0x7f95c014f598, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, local=local@entry=0x7ffcff5292f0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4engine_p.h:195 #8 0x7f95c9053c77 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=engine@entry=0x55a18c9ee3d0, qmlContext=qmlContext@entry=0x55a18faa4620, object=0x55a1945a4f40, name=0x7f95c014f598, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffcff5293b8, property=0x7ffcff5293c0) at jsruntime/qv4qobjectwrapper.cpp:371 #9 0x7f95c9033f0a in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) (resource=, id=..., receiver=, hasProperty=0x7ffcff529437, base=0x0, lookup=0x0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #10 0x7f95c8fea049 in QV4::Object::get(QV4::PropertyKey, QV4::Value const*, bool*) const (hasProperty=0x7ffcff529437, receiver=0x7f95c014f588, id=..., this=0x7f95c014f588) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:82 #11 QV4::ExecutionContext::getProperty(QV4::String*) (this=0x7f95c014f518, name=0x7f95c014f580) at jsruntime/qv4context.cpp:362 #12 0x7f95c9085593 in QV4::Runtime::TypeofName::call(QV4::ExecutionEngine*, int) (engine=0x55a18c9ee3d0, nameIndex=) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #13 0x7f95c9070ba0 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffcff529640, engine=0x55a18c9ee3d0, code=0x7f95b8b47fe2 "\030\a\022\v^\aL\004.\002H\001\f\030\006\002") at jsruntime/qv4vme_moth.cpp:944 #14 0x7f95c90750b7 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffcff529640, engine=engine@entry=0x55a18c9ee3d0) at jsruntime/qv4vme_moth.cpp:463 #15 0x7f95c901208d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=this@entry=0x55a192782ca0, thisObject=, argv=argv@entry=0x7f95c014f510, argc=, context=) at jsruntime/qv4function.cpp:69 #16 0x7f95c9178a15 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=this@entry=0x55a1950a06a0, callData=0x7f95c014f4e0, isUndefined=isUndefined@entry=0x7ffcff52981f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #17 0x7f95c917ddb8 in QQmlBinding::evaluate(bool*) (this=this@entry=0x55a1950a06a0, isUndefined=isUndefined@entry=0x7ffcff52981f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #18 0x
[bugs.kde.org] [Bug 429576] change plasmashell component from Emoji picker to Emoji Selector
https://bugs.kde.org/show_bug.cgi?id=429576 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org, ||plasma-de...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Ben Cooksley --- Can someone from Plasma please confirm this is correct? -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 414281] kcolorchooser always show color from first display on multihead system
https://bugs.kde.org/show_bug.cgi?id=414281 --- Comment #7 from Frederick Zhang --- can also confirm on Arch. btw apart from the env vars I mentioned above, QT_SCREEN_SCALE_FACTORS='' can also be used as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429586] New: No way to get back to the window rules list after viewing a rule.
https://bugs.kde.org/show_bug.cgi?id=429586 Bug ID: 429586 Summary: No way to get back to the window rules list after viewing a rule. Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwinrules Assignee: kwin-bugs-n...@kde.org Reporter: 1i5t5.dun...@cox.net CC: isma...@gmail.com, plasma-b...@kde.org Target Milestone: --- On git master frameworks/plasma, updated yesterday. When in kde system settings (but not when invoked as a dedicated single kcm view via kcmshell5), viewing a rule in the window rules kcm, there's no way to get back to the rules list. One must click on a different kcm, then back to rules, in ordered to get back to the window list. In the dedicated rules kcm view (not in kde systemsettings), the header-bar at the top has a breadcrumbs path with a left-arrow that can be clicked to get back to the rules list, or the window rules section of the breadcrumbs can be clicked to do the same thing. But that header-bar doesn't appear in kde systemsettings view, so there's no breadcrumbs and no left-arrow or windows-rules section in it to be clicked to get back. =:^( -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 411263] Spectacle does not send screenshot to clipboard when --nonotify is used
https://bugs.kde.org/show_bug.cgi?id=411263 Frederick Zhang changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #16 from Frederick Zhang --- Yes I can confirm this has been fixed! Thank you! (In reply to Antonio Prcela from comment #15) > This one has been fixed, but not sure what commit it was. > Can you test again with the latest Spectacle? Thanks. > > (In reply to Frederick Zhang from comment #0) > > STEPS TO REPRODUCE > > 1. Run spectacle --background --clipboard --region --nonotify > > 2. Select a region, confirm > > > > OBSERVED RESULT > > The screenshot does not get copied to clipboard. And another side effect I > > noticed was that the desktop seemed to be frozen after the screenshot for a > > few seconds (roughly the same as how long a notification stays on screen > > when Spectacle is called without --nonotify), during which I cannot call > > KRunner, cannot pop up Latte Dock, etc. > > > > EXPECTED RESULT > > The screenshot is sent to clipboard. > > > > SOFTWARE/OS VERSIONS > > Linux/KDE Plasma: Arch Linux > > KDE Plasma Version: 5.16.4-1 > > KDE Frameworks Version: 5.61.0-1 > > Qt Version: 5.13.0-7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429574] Smileys & Emotion category missing from Emoji Selector sidebar
https://bugs.kde.org/show_bug.cgi?id=429574 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/243 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429586] No way to get back to the window rules list after viewing a rule.
https://bugs.kde.org/show_bug.cgi?id=429586 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350672] Memory status monitor has cramped rendering in panel
https://bugs.kde.org/show_bug.cgi?id=350672 --- Comment #6 from Lastique --- Created attachment 133603 --> https://bugs.kde.org/attachment.cgi?id=133603&action=edit Memory Usage widget in Text Only mode on a panel I have tried the Memory Usage widget on a horizontal panel in a few modes, and while it looks different from the original screenshot, it doesn't really look well. 1. In Text Only mode, it shows some trimmed number (4.0 or 4.1 in my case). See the attached screenshot. The number doesn't seem to represent allocated or free memory in GiB (at the time of taking the screenshot, I had ~2.9 of 16 GiB allocated). There is enough space available on the panel, so there should be no need to trim the text. 2. In Line Chart mode, the widget simply does not display anything. The panel shows as if there was no Memory Usage widget at all. 3. On Bar Chart mode, the widget shows one bar with no legends or numerical representation. In Bar Chart Details tab, Show Sensors Legends is enabled. 4. When I first added the widget it was working in the Pie Chart mode, and it was showing a pie chart with legends. However, when I switched to another mode and then back to Pie Chart, the widget was not displaying anything at all, as in Line Chart mode. 5. Navigating the widget settings tends to crash Plasma, as reported in bug https://bugs.kde.org/show_bug.cgi?id=429585. I did not test in on a vertical panel. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 283907] enhance configure message
https://bugs.kde.org/show_bug.cgi?id=283907 Toralf Förster changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350672] Memory status monitor has cramped rendering in panel
https://bugs.kde.org/show_bug.cgi?id=350672 Lastique changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Lastique --- The info provided in the previous comment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428914] Many Plasma Components do not work properly with a stylus, but work find with touch
https://bugs.kde.org/show_bug.cgi?id=428914 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #9 from David Edmundson --- >I'm struggling to find a pattern. Then the best next step is to try and make a minimal test case: qmlscene with a few buttons and steps to reproduce on that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429585] Plasma crash when navigating Memory Usage widget settings
https://bugs.kde.org/show_bug.cgi?id=429585 --- Comment #1 from Lastique --- Note that this crash is not 100% reproducible. I had multiple crashes when switching to different tabs in the Memory Usage widget settings after changing the Display Style option. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429585] Plasma crash when navigating Memory Usage widget settings
https://bugs.kde.org/show_bug.cgi?id=429585 Lastique changed: What|Removed |Added Platform|Ubuntu Packages |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429371] Impossible to assign tag to a brush in master
https://bugs.kde.org/show_bug.cgi?id=429371 --- Comment #2 from Boudewijn Rempt --- Git commit bde4d15a9869e84aaaef8466db42a4a7f8f9204b by Boudewijn Rempt. Committed on 24/11/2020 at 10:23. Pushed by rempt into branch 'master'. Remove the extra filter model for the preset chooser M +20 -2libs/resources/KisTagFilterResourceProxyModel.cpp M +11 -3libs/resources/KisTagFilterResourceProxyModel.h M +10 -17 libs/resourcewidgets/KisResourceItemChooser.cpp M +4-1libs/resourcewidgets/KisResourceItemChooser.h M +17 -148 libs/ui/widgets/kis_preset_chooser.cpp https://invent.kde.org/graphics/krita/commit/bde4d15a9869e84aaaef8466db42a4a7f8f9204b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384131] can't configure or resize plasmoids (e.g. picture frame) on second desktop
https://bugs.kde.org/show_bug.cgi?id=384131 David Faure changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from David Faure --- Yep, this is much better indeed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 283907] enhance configure message
https://bugs.kde.org/show_bug.cgi?id=283907 Justin Zobel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423553] No smooth scrolling in small scales after Windows 10 2004 update
https://bugs.kde.org/show_bug.cgi?id=423553 savilov...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from savilov...@gmail.com --- I forgot to change the status. See my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #6 from Markus --- Created attachment 133604 --> https://bugs.kde.org/attachment.cgi?id=133604&action=edit kdepim-runtime patch Missed to add the patch mentioned in comment#4. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429470] Wrong Behavior in Details View - Items are shown in wrong parent folders - video attached -
https://bugs.kde.org/show_bug.cgi?id=429470 cvza...@gmail.com changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 425822] 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 Tomasz Paweł Gajc changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Tomasz Paweł Gajc --- Hi, ive added your commit to clazy-1.8 build. Still same error: https://abf.openmandriva.org/build_lists/917634 /usr/include/llvm/Support/type_traits.h:31:28: error: no template named 'remove_reference_t' in namespace 'std'; did you mean 'remove_reference'? using UnderlyingT = std::remove_reference_t; ~^ https://github.com/OpenMandrivaAssociation/clazy/commit/0a749bf7fd51cce3006737bba22a0fa5acd727a6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428914] Many Plasma Components do not work properly with a stylus, but work find with touch
https://bugs.kde.org/show_bug.cgi?id=428914 --- Comment #10 from Tyson Tan --- I would also like to remind everyone that touchscreen DID NOT work either. The changed title of this bug report does not reflect what I'm actually experiencing. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 364187] Skanlite freezes at some point
https://bugs.kde.org/show_bug.cgi?id=364187 Aleix Pol changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Aleix Pol --- No, works now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 --- Comment #4 from xelnagazch...@hotmail.com --- Created attachment 133605 --> https://bugs.kde.org/attachment.cgi?id=133605&action=edit crashog 4.4.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 --- Comment #5 from xelnagazch...@hotmail.com --- Hey, crash still occurs on 4.4.1 Krita. Attached new crashlog and crashing file ! -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 425822] 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 --- Comment #3 from Sergio Martins --- if you copy that compiler invocation line, but replace -std=c++11 with -std=c++14 , does it work ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #6 from Boudewijn Rempt --- * Does this happen when you open an image with Krita from the finder, or when you open an image from within krita? * Does this happen with all files you open with Krita, or with a specific file? -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 419874] Folder selector does not work with GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=419874 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Summary|GTK3 apps installed via |Folder selector does not |flatpak do not trigger the |work with GTK3 apps |folder selector |installed via flatpak Status|RESOLVED|REOPENED --- Comment #7 from Patrick Silva --- it's still impossible to select a folder with GTK3 apps installed via flatpak. Nothing happens when I click on "Open" button of the dialog. Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 --- Comment #7 from xelnagazch...@hotmail.com --- * it happens specifically when i double clic a .kra file in the finder. * I thought it happened specifically for some files; but apparently now all my files crash when i try opening through double clic. I can't remember the last time it didn't happen, sorry, it's a messy bug report -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429477] Can't directly open "Global Theme" KCM anymore
https://bugs.kde.org/show_bug.cgi?id=429477 Marco Martin changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/systemsettings/commit/22 ||d58adb13770ed5c04779ea24fb2 ||80afff6b73e Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Marco Martin --- Git commit 22d58adb13770ed5c04779ea24fb280afff6b73e by Marco Martin. Committed on 24/11/2020 at 12:07. Pushed by mart into branch 'master'. search also in info() if is the module we want some items that are categories with owning kcms have d->service->desktopEntryName() is not the name of the owning kcm in this case the real desktop name of the kcm is item().fileName() M +6-2core/MenuItem.cpp https://invent.kde.org/plasma/systemsettings/commit/22d58adb13770ed5c04779ea24fb280afff6b73e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 --- Comment #8 from xelnagazch...@hotmail.com --- (In reply to xelnagazchild from comment #5) > Hey, crash still occurs on 4.4.1 Krita. Attached new crashlog and crashing > file ! actually the crashing file i wanted to upload was too big for here, so it's on wetranfer, hope it's an adequate sharing way : https://we.tl/t-Ie0Tkhn2Zf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429574] Smileys & Emotion category missing from Emoji Selector sidebar
https://bugs.kde.org/show_bug.cgi?id=429574 David Redondo changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/6e ||66bf62bbf800443d69a172cc1db ||24e88145e8f --- Comment #3 from David Redondo --- Git commit 6e66bf62bbf800443d69a172cc1db24e88145e8f by David Redondo. Committed on 24/11/2020 at 10:31. Pushed by davidre into branch 'master'. There is no Q_FALLTHROUGH in qml or js CCMAIL:i...@guoyunhe.me M +1-1applets/kimpanel/backend/ibus/emojier/ui/CategoryAction.qml https://invent.kde.org/plasma/plasma-desktop/commit/6e66bf62bbf800443d69a172cc1db24e88145e8f -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429167] Appearance options aren't preserved
https://bugs.kde.org/show_bug.cgi?id=429167 David Redondo changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/libksysguard/commit/744b ||ccf477457e29da1dacda6d75ef0 ||5a0f4b15f Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from David Redondo --- Git commit 744bccf477457e29da1dacda6d75ef05a0f4b15f by David Redondo. Committed on 24/11/2020 at 12:12. Pushed by davidre into branch 'master'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429155, bug 429367 M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/744bccf477457e29da1dacda6d75ef05a0f4b15f -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429155] Data Range Option isn't preserved
https://bugs.kde.org/show_bug.cgi?id=429155 David Redondo changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/libksysguard/commit/744b ||ccf477457e29da1dacda6d75ef0 ||5a0f4b15f --- Comment #4 from David Redondo --- Git commit 744bccf477457e29da1dacda6d75ef05a0f4b15f by David Redondo. Committed on 24/11/2020 at 12:12. Pushed by davidre into branch 'master'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429167, bug 429367 M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/744bccf477457e29da1dacda6d75ef05a0f4b15f -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429367] Does not remember sorted column
https://bugs.kde.org/show_bug.cgi?id=429367 David Redondo changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/libksysguard/commit/744b ||ccf477457e29da1dacda6d75ef0 ||5a0f4b15f Status|CONFIRMED |RESOLVED --- Comment #2 from David Redondo --- Git commit 744bccf477457e29da1dacda6d75ef05a0f4b15f by David Redondo. Committed on 24/11/2020 at 12:12. Pushed by davidre into branch 'master'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429155, bug 429167 M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/744bccf477457e29da1dacda6d75ef05a0f4b15f -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429367] Does not remember sorted column
https://bugs.kde.org/show_bug.cgi?id=429367 David Redondo changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libksysguard/commit/744b |ma/libksysguard/commit/9841 |ccf477457e29da1dacda6d75ef0 |48d39df3da1d726aec9bf8e741e |5a0f4b15f |c2c840541 --- Comment #3 from David Redondo --- Git commit 984148d39df3da1d726aec9bf8e741ec2c840541 by David Redondo. Committed on 24/11/2020 at 12:14. Pushed by davidre into branch 'Plasma/5.20'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429155, bug 429167 (cherry picked from commit 744bccf477457e29da1dacda6d75ef05a0f4b15f) M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/984148d39df3da1d726aec9bf8e741ec2c840541 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429155] Data Range Option isn't preserved
https://bugs.kde.org/show_bug.cgi?id=429155 David Redondo changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libksysguard/commit/744b |ma/libksysguard/commit/9841 |ccf477457e29da1dacda6d75ef0 |48d39df3da1d726aec9bf8e741e |5a0f4b15f |c2c840541 --- Comment #5 from David Redondo --- Git commit 984148d39df3da1d726aec9bf8e741ec2c840541 by David Redondo. Committed on 24/11/2020 at 12:14. Pushed by davidre into branch 'Plasma/5.20'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429167, bug 429367 (cherry picked from commit 744bccf477457e29da1dacda6d75ef05a0f4b15f) M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/984148d39df3da1d726aec9bf8e741ec2c840541 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429167] Appearance options aren't preserved
https://bugs.kde.org/show_bug.cgi?id=429167 David Redondo changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libksysguard/commit/744b |ma/libksysguard/commit/9841 |ccf477457e29da1dacda6d75ef0 |48d39df3da1d726aec9bf8e741e |5a0f4b15f |c2c840541 --- Comment #3 from David Redondo --- Git commit 984148d39df3da1d726aec9bf8e741ec2c840541 by David Redondo. Committed on 24/11/2020 at 12:14. Pushed by davidre into branch 'Plasma/5.20'. Write entries if face config changes If we should not sync we correctly disable autosave. This disables writing to the config and syncing it. However we still want to write to the config even if the config should not be synced automatically, so when it is externally synced the values are saved. This is the same method uses for the other config properties, for example compare with setTitle(). Related: bug 429155, bug 429367 (cherry picked from commit 744bccf477457e29da1dacda6d75ef05a0f4b15f) M +6-0faces/SensorFaceController.cpp https://invent.kde.org/plasma/libksysguard/commit/984148d39df3da1d726aec9bf8e741ec2c840541 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 422289] First delegate of ListView within OverlaySheet it's initially drawn at wrong position
https://bugs.kde.org/show_bug.cgi?id=422289 --- Comment #5 from Patrick Silva --- Created attachment 133606 --> https://bugs.kde.org/attachment.cgi?id=133606&action=edit affected GHNS window I'm attaching a screenshot showing an affected "get how new stuff" window. Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 429587] New: aqbanking setup: lists unavailable TAN methods in edit user dialog
https://bugs.kde.org/show_bug.cgi?id=429587 Bug ID: 429587 Summary: aqbanking setup: lists unavailable TAN methods in edit user dialog Product: kmymoney Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: kde-bugzi...@thequod.de Target Milestone: --- In the edit dialog of an aqbanking user I can select TAN methods in the HBCI settings, which aqbanking itself lists as unavailable (for unknown reasons), e.g. "913 - chipTAN manuell HHD1.4 (Version 6)". % aqhbci-tool4 listitanmodes --user=1 TAN Methods - 6910 (F910/V6/P2): HHD1.3.2OPT (chipTAN optisch HHD1.3.2) ZKA-ID=HHDOPT1 [available] - 6911 (F911/V6/P2): HHD1.3.2 (chipTAN manuell HHD1.3.2) ZKA-ID=HHD [available] - 6912 (F912/V6/P2): HHD1.4OPT (chipTAN optisch HHD1.4) ZKA-ID=HHDOPT1 [not available] - 6913 (F913/V6/P2): HHD1.4 (chipTAN manuell HHD1.4) ZKA-ID=HHD [not available] - 6920 (F920/V6/P2): BestSign (BestSign) ZKA-ID=BestSign [not available] - 6930 (F930/V6/P2): mobileTAN (mobileTAN) ZKA-ID=mobileTAN [available] I think KMyMoney should have those greyed out / made not available there, since I suspect that having selected 6913 before led to unclear errors, because some dialog(s) could not be created. btw: is it possible to find out why the methods are marked as "not available" by aqbanking? Arch Linux, kmymoney 5.1.0-2, aqbanking 6.2.5-1, gwenhywfar 5.4.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 429587] aqbanking setup: lists unavailable TAN methods in edit user dialog
https://bugs.kde.org/show_bug.cgi?id=429587 Daniel Hahler changed: What|Removed |Added CC||kde-bugzi...@thequod.de Version|unspecified |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423553] No smooth scrolling in small scales after Windows 10 2004 update
https://bugs.kde.org/show_bug.cgi?id=423553 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from David Hurka --- Sorry, it is still unclear to me. I understand that you use your touchpad for scrolling. Therefore, you should have pixel-wise scrolling. What we call “smooth scrolling” in Okular (since release 1.10 / 20.04), is not applied to pixel-wise scrolling with a touchpad. Smooth scrolling means to us that the content moves stepwise (like when you press the arrow keys), but with an animated transition. (Apparently you have a 141dpi screen, so I estimate between 150% and 200% your Okular turns on tiled rendering.) Is the problem that the content briefly disappears when you scroll at high zoom scales? (Another theory is that your Okular does not turn on tiled rendering for some reason, and so operates with too big pixmaps.) Is the problem that the performance is bad when you scroll at high zoom scales, so the content moves at irregular large steps instead of pixel-wise? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428715] KDE Connect will forward its own notification
https://bugs.kde.org/show_bug.cgi?id=428715 --- Comment #4 from wereii --- It indeed should be. https://invent.kde.org/network/kdeconnect-android/-/merge_requests/218 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 425822] 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 Tomasz Paweł Gajc changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Tomasz Paweł Gajc --- Sorry for the noise. After proper update to 1.8 version things are compiling without errors. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429588] New: Window rules kcm needs a duplicate button
https://bugs.kde.org/show_bug.cgi?id=429588 Bug ID: 429588 Summary: Window rules kcm needs a duplicate button Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwinrules Assignee: kwin-bugs-n...@kde.org Reporter: 1i5t5.dun...@cox.net CC: isma...@gmail.com, plasma-b...@kde.org Target Milestone: --- So the last couple weeks I've been switching to wayland. As a result I've needed to create new window rules /almost/ duplicating many of my old X-based window rules, except of course with new wayland-style org.kde.whatever window classes. Critically, while I've basically completed the switch now, wayland's now my default and I've deleted many of the old X-based rules, at first I didn't want to touch them as I wasn't yet sure qt/kde/plasma's wayland support was going to be mature enough yet to default to wayland, so I was duplicating rules left and right, adding wayland versions duplicating my X settings but with different class settings. For such a use-case the window-rules kcm seriously needs a duplicate button! With it, I'd have been able to press duplicate, load one of the copies, modify the name to reflect wayland, hit detect to get the new class settings and modify them a bit if necessary, and hit apply, all without losing and having to recreate what the rules actually /did/ or their position in the rule stack. Because that duplicate button isn't there, I had to create a new rule, hit detect to get the new match settings, apply so as not to lose it, back out to the rule list and move the new rule from the bottom into its position next to the old rule, hit apply not to lose that, then repeatedly switch between the two rules copying the settings from the old one to the new one until they basically matched except for the differing class settings. The lack of that duplicate button therefore made the process far more laborious than it should have been. (Of course it was made even worse due to bugs such as bug #429586, as I hadn't yet discovered that there's a back button when the individual kcm is loaded with kcmshell5, so I was having to click out of the rules kcm and back to to get back to the rules list as I was doing it in kde system settings which doesn't have that back button, but that's a different bug.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429588] Window rules kcm needs a duplicate button
https://bugs.kde.org/show_bug.cgi?id=429588 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429485] Sound device is no longer available after 2020-11-20 upgrade (pipewire / pulseaudio conflict?)
https://bugs.kde.org/show_bug.cgi?id=429485 --- Comment #8 from Harald Sitter --- I'm about to land 0.3.16 which may well fix this problem, I expect what happens is some weird device binding race that pipewire happens to win. There is a related fix in .16 and I have high hopes that should fix it. In the meantime you could try > sudo dpkg-reconfigure --force neon-settings-2 and check with > systemctl --user is-enabled pipewire.service if the second line then reads > disabled; vendor preset: disabled) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429268] Viewing PGP-signed messages: signing addresses do not wrap, causing overflow of the PGP frame
https://bugs.kde.org/show_bug.cgi?id=429268 Podagric changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #1 from Podagric --- similar to https://bugs.kde.org/show_bug.cgi?id=424046 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429548] crash on open
https://bugs.kde.org/show_bug.cgi?id=429548 Boudewijn Rempt changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #9 from Boudewijn Rempt --- Thanks for your patience! If it always happens when opening the file through finder, then it;s this issue: https://bugs.kde.org/show_bug.cgi?id=421448. Ivan is working on fixing the bug, but there are some issues with finding a correct solution. *** This bug has been marked as a duplicate of bug 421448 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421448] Crash when opening files from Finder
https://bugs.kde.org/show_bug.cgi?id=421448 Boudewijn Rempt changed: What|Removed |Added CC||xelnagazch...@hotmail.com --- Comment #6 from Boudewijn Rempt --- *** Bug 429548 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 419874] Folder selector does not work with GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=419874 --- Comment #8 from Patrick Silva --- It's not GTK specific. These Qt apps are also affected: https://flathub.org/apps/details/org.musicbrainz.Picard https://flathub.org/apps/details/org.qbittorrent.qBittorrent https://flathub.org/apps/details/com.github.Bleuzen.FFaudioConverter -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429545] Alt-TAB between two windows sometimes focuses another window
https://bugs.kde.org/show_bug.cgi?id=429545 --- Comment #2 from Sander van Grieken --- I see it more often when activating a window (one that is not the two most toplevel windows) from the taskbar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429108] FPX image crashes on selection
https://bugs.kde.org/show_bug.cgi?id=429108 --- Comment #15 from Alastair --- Hi Maik, As I said, no problems with imagemagick. Have you given up on this or can we do more to fix it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 429589] New: Global shortcuts should not be stolen for programs that are not installed
https://bugs.kde.org/show_bug.cgi?id=429589 Bug ID: 429589 Summary: Global shortcuts should not be stolen for programs that are not installed Product: frameworks-kglobalaccel Version: 5.74.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: n...@esperi.org.uk Target Milestone: --- SUMMARY So I have a slightly unusual setup: a main desktop on a homegrown distro that runs LXQt atop fvwm, not KDE, but on which a Konversation started from a VM running Debian testing is almost always running (and often other KDE apps too). I use the M-, and M-. keybindings heavily for switching between tabs in terminator and Konversation and for tags lookup in Emacs. Last weekend Debian testing pulled in Plasma 5.19... and suddenly M-. stopped working as soon as I started any KDE app, while M-, worked fine. Figuring the culprit out took hours and a lot of X restarts and hacking of X to add more capabilities to its grab info reporter and a bug report to Terminator, where I spotted it first. A quick grep showed that /usr/share/kglobalaccel/org.kde.plasma.emojier.desktop was at fault. I don't have the Emoji Chooser installed (or any part of ibus, of which it is apparently part) and I don't want it, but apparently the kglobalaccel code doesn't notice that and grabs the key anyway, then hands it off to a DBus service that doesn't respond because it's not there. Ignoring an apparent Debian mispackaging which prevents me from rebinding or indeed even seeing global keybindings without hand-hacking the config files, and even ignoring the fact that M-. is a key used by a lot of major applications already for all sorts of purposes and stealing it globally is downright unfriendly, and even ignoring the fact that something in KDE should surely have noticed that I had M-. bound as local shortcuts in various KDE apps and that perhaps stealing all of them for a global shortcut was not a good idea... is it really ideal to globally grab and bind shortcut keys when the program that's supposed to be handling them is not even installed? (only the config file is, because it's shipped with plasma-desktop by default) This single helpful keystealing ate ten hours of my time tracking the culprit down. I'd quite like to know that KDE isn't going to steal anything else like this... STEPS TO REPRODUCE (one of many, any application using M-. will be broken systemwide) 1. Install Plasma and uninstall the Emoji chooser. Make sure kglobalaccel is not running yet. 2. Start Emacs. 3. Hit M-. 4. Observe the tag finder pop up in the minibuffer. 5. Start any KDE application. 6. Hit M-. in the already running Emacs. OBSERVED RESULT The second M-. doesn't pop up the tag finder, and nothing else visible happens (kglobalaccel has handed the M-. off to the nonexistent emoji chooser, throwing the keybinding away). EXPECTED RESULT The tag finder pops up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (homegrown, kernel 5.19.10 + GCC 10.2 + glibc 2.32 + X.org 1.20.9 + FVWM + LXQt + a lot of KDE apps, with many KDE apps running in a separate Debian Testing VM with a TCP/IP connection to the X server) KDE Plasma Version: 5.19 and later: observed with 5.19.5 KDE Frameworks Version: KF 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429590] New: Joystick calibration needs friendly UI
https://bugs.kde.org/show_bug.cgi?id=429590 Bug ID: 429590 Summary: Joystick calibration needs friendly UI Product: systemsettings Version: 5.20.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_joystick Assignee: plasma-b...@kde.org Reporter: ivan.plani...@gmail.com Target Milestone: --- SUMMARY Currently the joystick calibration is not intuitive. All it asks about "axes data 1/2/3/4/5" without ever providing WHAT axis, what part of the joystick? No images, no clues. You have to memorize axes values to see which is which. OBSERVED RESULT Asking about axis without ever providing any clue. EXPECTED RESULT Showing exactly what is about to calibrate - throttle, z-index, left/right, up/down etc. like every calibration program does. -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 419874] Folder selector does not work with GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=419874 --- Comment #9 from Jan Grulich --- What is your version of xdg-desktop-portal? I will try to investigate. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420598] kendlive crashes upon start on Ubuntu 20.4
https://bugs.kde.org/show_bug.cgi?id=420598 Olof Andersson changed: What|Removed |Added CC||olof.anders...@gmail.com --- Comment #2 from Olof Andersson --- I have the same crash. I want to add a line above the error log. Before the lines that the original reporter pasted, I also have a 'CRITICAL' error (not sure if the original reporter had this line or not). See below. ``` ** (kdenlive:39472): CRITICAL **: 14:38:45.300: gst_audio_format_from_string: assertion 'format != NULL' failed LC_NUMERIC reset to C Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) /tmp/.mount_kdenli6O2tyb/AppRun: line 26: 39472 Aborted (core dumped) kdenlive --config kdenlive-appimagerc $@ ``` -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427148] Discover shows error messages on opening or checking for updates if fwupd backend is disabled
https://bugs.kde.org/show_bug.cgi?id=427148 Patrick Silva changed: What|Removed |Added Summary|Discover shows error|Discover shows error |messages on opening and |messages on opening or |when checkng for updates if |checking for updates if |fwupd backend is disabled |fwupd backend is disabled -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 --- Comment #11 from Andrey --- Git commit a482d73de2911494ba3a0d89ada945fe4a28235f by Andrey Butirsky. Committed on 24/11/2020 at 13:34. Pushed by butirsky into branch 'master'. feat: expose keyboard layout Short Name via DBus Due space constraints, Short Name is the only name suitable for keyboard layout indication on panels and systray. Usually it's just 2 symbols corresponding to standard ISO country code. libxkbcommon doesn't have this information, so we have to store it in compositor for the exposing: https://github.com/xkbcommon/libxkbcommon/issues/192 It's exposed by getLayoutDisplayName() DBus method now, as it should initially. For Long Name, getCurrentLayoutLongName() method was added. Relevant P-W commits: Keyboard Layout plugin: passthrough Short Name from compositor to QML applet fix: Keyboard Layout plugin: wrong property for passing Short Name X11 part, P-D: feat: expose keyboard layout Long Name via DBus FEATURE: M +9-1keyboard_layout.cpp M +1-0keyboard_layout.h M +8-2xkb.cpp M +4-0xkb.h https://invent.kde.org/plasma/kwin/commit/a482d73de2911494ba3a0d89ada945fe4a28235f -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 419874] Folder selector does not work with GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=419874 --- Comment #10 from Patrick Silva --- (In reply to Jan Grulich from comment #9) > What is your version of xdg-desktop-portal? I will try to investigate. xdg-desktop-portal 1.8.0-1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429591] New: System Settings crash on opening and restarting
https://bugs.kde.org/show_bug.cgi?id=429591 Bug ID: 429591 Summary: System Settings crash on opening and restarting Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: antiheld.dlehitna+kdeb...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-54-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I had Firefox and Sublime Text 3 open and wanted to look something up. Since the newly opened window (Dragged a Tab away from main window) was sent to a different activity I tried to go into the settings in order to adjust the window rules. However when opening the settings program in any way (terminal, App Launcher with mouse or keyboard or search bar) it crashes instantly and I get a notification. As soon as I click the "restart" button on the notification it crashes again and a new notification pops up. I will try a reboot, but maybe there is a bug hidden somewhere that causes this (edge conditions, heisenbugs) or it's the all dreaded side-effects. Hopefully this is useful to someone. If not please disregard it. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8f6c33c800 (LWP 49357))] Thread 5 (Thread 0x7f8f57365700 (LWP 49362)): #0 g_mutex_unlock (mutex=0x7f8f5c30) at ../../../glib/gthread-posix.c:1487 #1 0x7f8f6e5291a3 in g_main_context_poll (priority=, n_fds=1, fds=0x7f8f500029e0, timeout=, context=0x7f8f5c30) at ../../../glib/gmain.c:4345 #2 g_main_context_iterate (context=context@entry=0x7f8f5c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4042 #3 0x7f8f6e5292e3 in g_main_context_iteration (context=0x7f8f5c30, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #4 0x7f8f707ef583 in QEventDispatcherGlib::processEvents (this=0x7f8f5b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f8f707964db in QEventLoop::exec (this=this@entry=0x7f8f57364d80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f8f705ce785 in QThread::exec (this=this@entry=0x56190ce1dc40) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f8f6f8811a9 in QQmlThreadPrivate::run (this=0x56190ce1dc40) at qml/ftw/qqmlthread.cpp:148 #8 0x7f8f705cf9d2 in QThreadPrivate::start (arg=0x56190ce1dc40) at thread/qthread_unix.cpp:361 #9 0x7f8f6ee0d609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f8f70260293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f8f61480700 (LWP 49361)): #0 __GI___libc_read (nbytes=16, buf=0x7f8f6147fb70, fd=12) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=12, buf=buf@entry=0x7f8f6147fb70, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f8f6e57189f in read (__nbytes=16, __buf=0x7f8f6147fb70, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x7f8f5c0039a0) at ../../../glib/gwakeup.c:210 #4 0x7f8f6e528cfe in g_main_context_check (context=context@entry=0x7f8f58000c30, max_priority=2147483647, fds=fds@entry=0x7f8f580025e0, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3825 #5 0x7f8f6e529152 in g_main_context_iterate (context=context@entry=0x7f8f58000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044 #6 0x7f8f6e5292e3 in g_main_context_iteration (context=0x7f8f58000c30, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #7 0x7f8f707ef583 in QEventDispatcherGlib::processEvents (this=0x7f8f58000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #8 0x7f8f707964db in QEventLoop::exec (this=this@entry=0x7f8f6147fd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #9 0x7f8f705ce785 in QThread::exec (this=this@entry=0x56190d1db1b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #10 0x7f8f6f8811a9 in QQmlThreadPrivate::run (this=0x56190d1db1b0) at qml/ftw/qqmlthread.cpp:148 #11 0x7f8f705cf9d2 in QThreadPrivate::start (arg=0x56190d1db1b0) at thread/qthread_unix.cpp:361 #12 0x7f8f6ee0d609 in start_thread (arg=) at pthread_create.c:477 #13 0x7f8f70260293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f8f6a415700 (LWP 49359)): #0 0x7f8f70253aff in __GI___poll (fds=0x7f8f5c0029e0, nfds=
[Breeze] [Bug 429592] New: Subtitle icon
https://bugs.kde.org/show_bug.cgi?id=429592 Bug ID: 429592 Summary: Subtitle icon Product: Breeze Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: snd.no...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 133607 --> https://bugs.kde.org/attachment.cgi?id=133607&action=edit subtitle icon SUMMARY At Kdenlive we are introducing feature to add subtitles. Attached is a proposal for an icon. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 429538] Dolphin 20.04.1 Crashes when closing terminal on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=429538 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/konsole/-/merge_requests/280 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 429592] Subtitle icon
https://bugs.kde.org/show_bug.cgi?id=429592 farid changed: What|Removed |Added CC||snd.no...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429485] Sound device is no longer available after 2020-11-20 upgrade (pipewire / pulseaudio conflict?)
https://bugs.kde.org/show_bug.cgi?id=429485 --- Comment #9 from sp --- Hi, In turning on pc today, I DID see the some updates and one of them being pipewire0.3.16. So I did the upgrade but nothing has change. Problem is still there. I did the commands that you told me and and the second one about "systemctl --user is-enabled pipewire.service" returns a line that just says "disabled". here's a cut/paste of the upgrade mentioned (it isn't too long): -- Log started: 2020-11-24 09:51:14 Selecting previously unselected package libapparmor1:i386. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 234412 files and directories currently installed.) Preparing to unpack .../00-libapparmor1_2.13.3-7ubuntu5.1_i386.deb ... Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... Preparing to unpack .../01-pulseaudio-utils_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-utils (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../02-pulseaudio-module-bluetooth_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-module-bluetooth (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../03-pulseaudio-module-gsettings_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-module-gsettings (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../04-pulseaudio_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../05-libpulsedsp_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking libpulsedsp:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../06-libpulse-mainloop-glib0_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../07-libpulse0_1%3a13.99.1-1ubuntu3.8_amd64.deb ... De-configuring libpulse0:i386 (1:13.99.1-1ubuntu3.7) ... Unpacking libpulse0:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../08-libpulse0_1%3a13.99.1-1ubuntu3.8_i386.deb ... Unpacking libpulse0:i386 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../09-distro-release-notifier_0.0+p20.04+git20201124.0023-0_amd64.deb ... Unpacking distro-release-notifier (0.0+p20.04+git20201124.0023-0) over (0.0+p20.04+git20201120.0023-0) ... Preparing to unpack .../10-libpipewire-0.3-modules_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libpipewire-0.3-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../11-pipewire_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking pipewire:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../12-pipewire-bin_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking pipewire-bin (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../13-libpipewire-0.3-0_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libpipewire-0.3-0:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../14-libspa-0.2-modules_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libspa-0.2-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../15-neon-settings-2_0.4+p20.04+git20201124.1143_all.deb ... Unpacking neon-settings-2 (0.4+p20.04+git20201124.1143) over (0.4+p20.04+git20201117.1211) ... Setting up libapparmor1:i386 (2.13.3-7ubuntu5.1) ... Setting up libpulse0:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up libpulse0:i386 (1:13.99.1-1ubuntu3.8) ... Setting up libpulsedsp:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up libspa-0.2-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up neon-settings-2 (0.4+p20.04+git20201124.1143) ... Installing new version of config file /etc/apt/preferences.d/99-focal-overrides ... Removed /etc/systemd/user/default.target.wants/pipewire.service. Setting up libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up pulseaudio-utils (1:13.99.1-1ubuntu3.8) ... Setting up libpipewire-0.3-0:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up distro-release-notifier (0.0+p20.04+git20201124.0023-0) ... Setting up pulseaudio (1:13.99.1-1ubuntu3.8) ... Setting up libpipewire-0.3-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up pulseaudio-module-
[bugs.kde.org] [Bug 429576] change plasmashell component from Emoji picker to Emoji Selector
https://bugs.kde.org/show_bug.cgi?id=429576 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED CC||n...@kde.org Status|NEEDSINFO |RESOLVED --- Comment #2 from Nate Graham --- Confirmed, and I've gone ahead and made this change. -- You are receiving this mail because: You are watching all bug changes.
