[kasts] [Bug 454674] Feature request: custom server URL for syncing
https://bugs.kde.org/show_bug.cgi?id=454674 Moritz changed: What|Removed |Added CC||moritz...@protonmail.com --- Comment #3 from Moritz --- Just as an additional reason to change it: the official gpodder.net site fails at adding new users and I had to change to an alternative provider. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management stopped working
https://bugs.kde.org/show_bug.cgi?id=462695 Moritz changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Moritz --- I can confirm, it is working again! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #18 from Moritz --- > Are y'all sure that nothing was blocking sleep at the time? The battery & > Brightness widget will tell you. No it was not. The screen turned into the lockscreen and eventually locked at some time, but it was not turning off. I think 5.27.0 has no fix included, it is fixed on unstable only. Probably in 5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358240] KeePass2 system tray icon is shown as white square
https://bugs.kde.org/show_bug.cgi?id=358240 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #13 from Moritz --- @Frederick Zhang Here are the logs for `journalctl --since 2022-09-01 -g 'org.freedesktop.impl'`, when I search for uid=996 in them I can't find anything BUT I have since then used Timeshift many times to jump back and forth between snapshots and again since I added `XDG_CURRENT_DESKTOP=KDE` as a workaround to `/etc/environment/` I don't have this issue anymore so I don't know how useful the logs will be! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #14 from Moritz --- Created attachment 151957 --> https://bugs.kde.org/attachment.cgi?id=151957&action=edit journalctl --since 2022-09-01 -g 'org.freedesktop.impl' Output -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #23 from Moritz --- (In reply to Frederick Zhang from comment #21) > @Moritz Thank you. I guess uid=970 is sddm in your system? According to my `coredumpctl info 912` attachment I do think so. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #28 from Moritz --- @Harald, Thank you for the fix. > delay ksplash until after env is set up I removed my `XDG_CURRENT_DESKTOP=KDE` in `/etc/environment/` work-around, installed the newest Arch updates and rebooted my system: your fix works for me! But I also still get the same `sudo coredumpctl list` entry as before / as @Frederick Zhang: > Wed 2022-09-14 18:15:26 CEST 927 970 970 SIGABRT present > /usr/lib/xdg-desktop-portal-kde With this backtrace: > sudo coredumpctl gdb 927 > (gdb) bt #0 0x7f289eca149c in ?? () from /usr/lib/libc.so.6 #1 0x7f289ec51958 in raise () from /usr/lib/libc.so.6 #2 0x7f289ec3b53d in abort () from /usr/lib/libc.so.6 #3 0x7f289f29fede in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #4 0x7f289ff3caa5 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/libQt5Gui.so.5 #5 0x7f289ff3d109 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/libQt5Gui.so.5 #6 0x7f289f49218b in QCoreApplicationPrivate::init() () from /usr/lib/libQt5Core.so.5 #7 0x7f289ff3d1b9 in QGuiApplicationPrivate::init() () from /usr/lib/libQt5Gui.so.5 #8 0x7f28a0d75e0e in QApplicationPrivate::init() () from /usr/lib/libQt5Widgets.so.5 #9 0x5613c611f0c6 in ?? () #10 0x7f289ec3c290 in ?? () from /usr/lib/libc.so.6 #11 0x7f289ec3c34a in __libc_start_main () from /usr/lib/libc.so.6 #12 0x5613c6120535 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 Moritz changed: What|Removed |Added CC||moritz1...@googlemail.com --- Comment #2 from Moritz --- I have the same issue. I installed Arianna via the AUR: https://aur.archlinux.org/packages/arianna ``` $ arianna Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Broken filename passed to function Broken filename passed to function [...] (it repeats a few times) search started starting query Baloo::QueryRunnable(0x55af4c803430) Broken filename passed to function Broken filename passed to function [...] (it repeats a few times) Segmentation fault (core dumped) ``` ___ Arianna opens for half a second and then immediately crashes. In that short amount of time when Arianna is open I can see that it lists some of my ebooks from e.g. `Documents/Calibre Library`. -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #4 from Moritz --- Created attachment 158269 --> https://bugs.kde.org/attachment.cgi?id=158269&action=edit coredumpctl info -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #5 from Moritz --- Created attachment 158270 --> https://bugs.kde.org/attachment.cgi?id=158270&action=edit coredumpctl gdb - (gdb) bt -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #6 from Moritz --- My attempt at creating a backtrace, I hope this is somewhat helpful: $ coredumpctl list Fri 2023-04-21 13:29:58 CEST 5768 1000 1000 SIGSEGV present /usr/bin/arianna 12.5M $ coredumpctl match 5768 -> see info_5768.txt $ coredumpctl gdb 5768 $ Enable debuginfod for this session? (y or [n]) y $ (gdb) bt -> see bt_5768.txt -- You are receiving this mail because: You are watching all bug changes.
[kio-admin] [Bug 468793] New: Can't cancel "Manage files as adiministrator" dialog
https://bugs.kde.org/show_bug.cgi?id=468793 Bug ID: 468793 Summary: Can't cancel "Manage files as adiministrator" dialog Classification: Frameworks and Libraries Product: kio-admin Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: moritz1...@googlemail.com CC: sit...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Dolphin 2. Go to e.g.: '/' 3. Right click on 'root' > "Open as Administrator" 4. Click "Cancel" in the "Manage files as administrator" dialog where you can enter your password https://imgur.com/a/fKdEGuN OBSERVED RESULT - The dialog just appears again - Clicking "Cancel" just repeats the same thing, the dialog keeps on appearing. EXPECTED RESULT - The dialog gets closed and the operation canceled. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS / Arch KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION: Dolphin: 23.04.0-1 kio-admin: 23.04.0-1 Also I noticed that I sometimes have to enter my password two times into the "Manage files as administrator" dialog. 1) I enter it once and press "OK" 2) The same dialog pops up again and I need to enter my password a second time and press "OK" again. I don't know if this has something to do with my issue reported above. -- You are receiving this mail because: You are watching all bug changes.
[kio-admin] [Bug 468793] Can't cancel "Manage files as administrator" dialog
https://bugs.kde.org/show_bug.cgi?id=468793 Moritz changed: What|Removed |Added Summary|Can't cancel "Manage files |Can't cancel "Manage files |as adiministrator" dialog |as administrator" dialog -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 468793] Can't cancel "Manage files as administrator" dialog
https://bugs.kde.org/show_bug.cgi?id=468793 Moritz changed: What|Removed |Added Product|kio-admin |policykit-kde-agent-1 Version|23.04.0 |5.27.4 CC||d...@kde.org, ||jgrul...@redhat.com, ||jrez...@redhat.com Component|general |general --- Comment #1 from Moritz --- EDIT: I noticed that I can't cancel a single " Authentication Required - PolicyKit1 KDE Agent" dialog. e.g. when opening "GParted" I get asked for my password and I can't cancel the dialog. It just keeps on appearing over and over again. https://imgur.com/a/XAI9BS8 I am sorry for the confusion, I thought my problem is just related to "kio-admin". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470173] New: Plasmashell freezes sometimes when opening a new windows
https://bugs.kde.org/show_bug.cgi?id=470173 Bug ID: 470173 Summary: Plasmashell freezes sometimes when opening a new windows Classification: Plasma Product: plasmashell Version: master Platform: Debian unstable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 159207 --> https://bugs.kde.org/attachment.cgi?id=159207&action=edit backtrace SUMMARY I just opened a new window and plasmashell froze. It is happening sometimes, not specific. STEPS TO REPRODUCE Not quite sure. OBSERVED RESULT It froze SOFTWARE/OS VERSIONS Operating System: siduction 22.1.0 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.3.3-1-siduction-amd64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Product Name: X370 Killer SLI ADDITIONAL INFORMATION I attached a gtb backtrace (`apply thread all bt´``) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410760] While copying files which dolphin, the graphics hangs up
https://bugs.kde.org/show_bug.cgi?id=410760 --- Comment #9 from Moritz --- https://bugs.kde.org/show_bug.cgi?id=469533 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 461057] Dragged text in SelectableLabels inside a FormLayout can cause bad text rendering
https://bugs.kde.org/show_bug.cgi?id=461057 Moritz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Moritz --- I can not scroll anymore, so I guess it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470173] Plasmashell freezes sometimes when opening a new windows
https://bugs.kde.org/show_bug.cgi?id=470173 --- Comment #2 from Moritz --- It freezes forever. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470834] New: Updated version reversed with installed version
https://bugs.kde.org/show_bug.cgi?id=470834 Bug ID: 470834 Summary: Updated version reversed with installed version Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- Created attachment 159569 --> https://bugs.kde.org/attachment.cgi?id=159569&action=edit Signal flatpak update SUMMARY When clicking on Updates, discover shows the current version -> new version (e.g. 6.18.0 -> 6.20.0). The problem is, that is reversed for flatpak (so it shows 6.20.0 -> 6.18.0) STEPS TO REPRODUCE 1. See flatpak updates SOFTWARE/OS VERSIONS Operating System: siduction 22.1.0 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.3.5-1-siduction-amd64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Product Name: X370 Killer SLI ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470834] Updated version reversed with installed version
https://bugs.kde.org/show_bug.cgi?id=470834 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465864] Discover thinks Breeze gtk theme from flathub will be "updated" from 5.27 to 5.26.5
https://bugs.kde.org/show_bug.cgi?id=465864 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de --- Comment #17 from Moritz --- Its not fixed in 5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471166] New: Vlume controls on the lockscreen broken
https://bugs.kde.org/show_bug.cgi?id=471166 Bug ID: 471166 Summary: Vlume controls on the lockscreen broken Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY When the screen is locked, volume controls are not working properly. I am clicking volume up (keyboard) and the overlay shows, but is rarly (1 in 20 tries) incrementing/decrementing the volume. STEPS TO REPRODUCE 1. Lock screen 2. Increase/Decrease volume via keyboard OBSERVED RESULT Not changing SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471166] Vlume controls on the lockscreen broken
https://bugs.kde.org/show_bug.cgi?id=471166 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471166] Volume controls on the lockscreen broken
https://bugs.kde.org/show_bug.cgi?id=471166 Moritz changed: What|Removed |Added Summary|Vlume controls on the |Volume controls on the |lockscreen broken |lockscreen broken -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469532] New: KDE laggs horrible when io is active
https://bugs.kde.org/show_bug.cgi?id=469532 Bug ID: 469532 Summary: KDE laggs horrible when io is active Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- Created attachment 158800 --> https://bugs.kde.org/attachment.cgi?id=158800&action=edit System monitor SUMMARY KDE is lagging horrible on all sorts of io events. It also affects other applications. STEPS TO REPRODUCE 1. Copy files from one drive to another (or extract an archive, ...) OBSERVED RESULT KDE is lagging as hell EXPECTED RESULT Working fine, no lag spikes SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION I do have an NVME SSD installed, I can also see this on a lot of other devies that run KDE software. I am observing this for years, but now (I am just copying 50 GB over the network) it is really REALLY annoying. See the system monitor attachment. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469532] KDE laggs horrible when io is active
https://bugs.kde.org/show_bug.cgi?id=469532 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469533] New: Dolphin freezes and eventually crashes when I am conntected to a network without internet
https://bugs.kde.org/show_bug.cgi?id=469533 Bug ID: 469533 Summary: Dolphin freezes and eventually crashes when I am conntected to a network without internet Classification: Applications Product: dolphin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bixi...@bixilon.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 158801 --> https://bugs.kde.org/attachment.cgi?id=158801&action=edit backtrace SUMMARY I recently was on the ICE and while I was connected to the hotspot but did not authenticate through their captive web portal, I started dolphin and it pretty much instantly froze and eventually crashed. Disconnecting from the network/logging in solved that problem and it seemed to work fine again. STEPS TO REPRODUCE 1. Run `sudo iptables -A INPUT -i wlp2s0 -j DROP` (adjust your interface name) 2. Start dolphin (To remove the rule again, run `sudo iptables -D INPUT -i wlp2s0 -j DROP` or reboot your computer) OBSERVED RESULT Work normal EXPECTED RESULT Frozen SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION It seems like it tries to connect to a samba share, but I do not have any mounted/trying to access it. I do use it from time to time (accessing a smb:// domain). Found it in a previous stack trace, not this one. Might be a complete wrong guess gdb backtrace (and px -aux) is attached, can not post it directly...blocked because of spam -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469533] Dolphin freezes and eventually crashes when I am conntected to a network without internet
https://bugs.kde.org/show_bug.cgi?id=469533 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469536] New: Freeze when disconnecting from networks
https://bugs.kde.org/show_bug.cgi?id=469536 Bug ID: 469536 Summary: Freeze when disconnecting from networks Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.26 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Sometimes when disconnecting from networks, plasma shell freezes for a couple of seconds. It does not matter what network, it is random imho. But for every wireguard connection it happens. STEPS TO REPRODUCE 1. Connect to a network 2. Add a wireguard network 3. Conenct to the wireguard vpn 4. Disconenct from vpn via gui OBSERVED RESULT Normal disconenct or loading bar EXPECTED RESULT Freeze SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION Backtrace: Thread 1 (Thread 0x7ff25ad0e9c0 (LWP 170313) "plasmashell"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55a2a045ae30) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55a2a045ae30) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55a2a045ae30, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7ff25ea93ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a2a045ade0, cond=0x55a2a045ae08) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55a2a045ae08, mutex=0x55a2a045ade0) at ./nptl/pthread_cond_wait.c:627 #5 0x7ff25f2d476b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55a2a045ade0) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait (this=this@entry=0x7ff25409cb20, mutex=mutex@entry=0x7ff25409cb18, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7ff25ffdf656 in QDBusPendingCallPrivate::waitForFinished (this=this@entry=0x7ff25409cae0) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #8 0x7ff25ff9af12 in QDBusConnectionPrivate::sendWithReply (this=0x7ff254006820, message=..., sendMode=1, timeout=) at ./src/dbus/qdbusintegrator.cpp:2088 #9 0x7ff25ff86a0b in QDBusConnection::call (this=this@entry=0x55a2a026a448, message=..., mode=mode@entry=QDBus::Block, timeout=) at ./src/dbus/qdbusconnection.cpp:680 #10 0x7ff25ffa3f5b in QDBusAbstractInterfacePrivate::property (this=this@entry=0x55a2a026a3f0, mp=..., returnValuePtr=returnValuePtr@entry=0x7fff1e69d090) at ./src/dbus/qdbusabstractinterface.cpp:179 #11 0x7ff25ffa6719 in QDBusAbstractInterfacePrivate::property (returnValuePtr=0x7fff1e69d090, mp=..., this=0x55a2a026a3f0) at ./src/dbus/qdbusabstractinterface.cpp:154 #12 QDBusAbstractInterfaceBase::qt_metacall (this=this@entry=0x55a2a021de00, _c=_c@entry=QMetaObject::ReadProperty, _id=, _a=_a@entry=0x7fff1e69d0d0) at ./src/dbus/qdbusabstractinterface.cpp:290 #13 0x7ff25ffa689b in QDBusAbstractInterface::qt_metacall (this=this@entry=0x55a2a021de00, _c=_c@entry=QMetaObject::ReadProperty, _id=, _a=_a@entry=0x7fff1e69d0d0) at .moc/moc_qdbusabstractinterface.cpp:104 #14 0x7ff1cc3bdffa in OrgFreedesktopNetworkManagerDeviceInterface::qt_metacall (this=0x55a2a021de00, _c=QMetaObject::ReadProperty, _id=, _a=0x7fff1e69d0d0) at ./obj-x86_64-linux-gnu/src/KF5NetworkManagerQt_autogen/KS3UX4TNHX/moc_deviceinterface.cpp:294 #15 0x7ff25f4c99fa in QMetaProperty::read (this=this@entry=0x7fff1e69d130, object=object@entry=0x55a2a021de00) at kernel/qmetaobject.cpp:3198 #16 0x7ff25f4efe1c in QObject::property (this=this@entry=0x55a2a021de00, name=name@entry=0x7ff1cc460124 "ActiveConnection") at kernel/qobject.cpp:4140 #17 0x7ff1cc3dfc4a in OrgFreedesktopNetworkManagerDeviceInterface::activeConnection (this=0x55a2a021de00) at ./obj-x86_64-linux-gnu/src/KF5NetworkManagerQt_autogen/EWIEGA46WW/../../../../src/dbus/deviceinterface.h:48 #18 NetworkManager::DevicePrivate::propertyChanged (this=0x55a2a021ddf0, property=..., value=...) at ./src/device.cpp:236 #19 0x7ff1cc3d97b2 in NetworkManager::DevicePrivate::propertiesChanged (this=0x55a2a021ddf0, properties=...) at ./src/device.cpp:620 #20 0x7ff1cc3c7861 in NetworkManager::DevicePrivate::qt_static_metacall (_a=0x7fff1e69d3a0, _id=1, _c=QMetaObject::InvokeMetaMethod, _o=0x55a2a021ddf0)
[plasmashell] [Bug 469536] Freeze when disconnecting from networks
https://bugs.kde.org/show_bug.cgi?id=469536 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469538] New: Some keys get stuck
https://bugs.kde.org/show_bug.cgi?id=469538 Bug ID: 469538 Summary: Some keys get stuck Classification: Plasma Product: kwin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY Sometimes I spam [FN] + [F3] often to increase the volume on my laptop. I don't keep it down, it is faster when pressing it multiple times. Sometimes the key then gets stuck and the volume is increased to the maximum value and I have to press the key again and then lower the volume again. I also experience it sometimes that the middle mouse button gets "stuck" and whatever button I press on my mouse, it results in the same as the middle key (when clicking on windows a new one opens) and I have to logout and login again. STEPS TO REPRODUCE Not quite sure, it is not happening always. But pretty much spam a key and hava a chance it stays pressed OBSERVED RESULT Don't get stuck SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION I know this is really hard to debug or reproduce, tell me what you need, I can (try) to give it to you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469538] Some keys get stuck
https://bugs.kde.org/show_bug.cgi?id=469538 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #31 from Moritz --- It is not only kmail specific, it is also happening to caldav and card dav resources. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 --- Comment #26 from Moritz --- You can run the following command to work around this issue: sudo n -s /usr/lib/x86_64-linux-gnu/libKF5TextAutoCorrectionCore.so.1 /usr/lib/libKF5TextAutoCorrection.so.1 It links the library to the correct path and name. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #41 from Moritz --- I can confirm, that made it work (I used the packages from debian sid, version 1.42.4-1 amd64) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469538] Some keys get stuck
https://bugs.kde.org/show_bug.cgi?id=469538 --- Comment #1 from Moritz --- I can trigger this "middle click" only in kde plasma (maybe other kde applications?), other applications (like chromium) are not affected. It just hit me after resuming from stand by. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #43 from Moritz --- No, even after upgrading network-manager, my caldav calendar is offline again. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459845] New: System gets unresponsive when aborting screen fade out animation
https://bugs.kde.org/show_bug.cgi?id=459845 Bug ID: 459845 Summary: System gets unresponsive when aborting screen fade out animation Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY I have a very low screen timeout (1 minute) on my laptop and before the screen turns off, there is an animation that makes the screen darker and darker and then turns it of. There are 2 bugs: - (only visual, minor) the screen flickers shortly up again before it gets turned off - When interrupting the animation (i.e pressing a key or moving the mouse) the screen gets lit up again, I can move the cursor but I can not click on anything, the keyboard is not working and key combinations are also not working. I need to close the lid of the laptop, go into stand by and then it start it again and everything is back to normal STEPS TO REPRODUCE 1. Set low screen timeout 2. Wait for the screen to turn off (don't do anything with it) 3. Exactly when the animation is there, move the mouse or press a key SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.12-051912-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC Please fix this, this is pretty annoying. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459845] System gets unresponsive when aborting screen fade out animation
https://bugs.kde.org/show_bug.cgi?id=459845 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459846] New: kscreenlocker crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=459846 Bug ID: 459846 Summary: kscreenlocker crashes with segfault Classification: Plasma Product: kscreenlocker Version: git-master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: bhus...@gmail.com Target Milestone: --- When locking the screen something crashes and it just shows a black screen with white text (something like the screen locker is broken) STEPS TO REPRODUCE 1. Update to latest kde neon unstable 2. Lock the screen SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.12-051912-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION Logs: Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25287]: kf.kirigami: Failed to find a Kirigami platform plugin Sep 30 10:55:56 moritz-82k kernel: kscreenlocker_g[25287]: segfault at 18 ip 7fe4eb20aabd sp 7ffc915e0eb0 error 4 in libLayerShellQtInterface.so.5.26.80[7fe4eb209000+3000] Sep 30 10:55:56 moritz-82k kernel: Code: 8d 6c 24 40 4c 8d 64 24 38 48 89 ee 4c 89 e7 e8 29 fc ff ff 48 89 ef e8 51 fc ff ff 4c 89 e6 4c 89 ef 89 44 24 24 49 8b 46 30 <4c> 8b 48 18 4c 89 4c 24 18 e8 55 ea ff ff 48 8b 44 24 40 48 03 40 Sep 30 10:55:56 moritz-82k kwin_wayland_wrapper[2301]: not a valid new object id (2), message get_registry(n) Sep 30 10:55:56 moritz-82k kwin_wayland_wrapper[2301]: error in client communication (pid 2301) Sep 30 10:55:56 moritz-82k kwin_wayland_wrapper[25317]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25317]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25317]: The Wayland connection experienced a fatal error: Das Argument ist ungültig Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25321]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25321]: The Wayland connection broke. Did the Wayland compositor die? Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25325]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 30 10:55:56 moritz-82k kscreenlocker_greet[25325]: The Wayland connection broke. Did the Wayland compositor die? DrKonqui does not start, how to get the full crashlog with gdb? (no clue how to do that with the library: https://community.kde.org/KWin/Debugging) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459846] kscreenlocker crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=459846 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459847] New: Touchpad gestures (4 fingers up and down) laggs horrible
https://bugs.kde.org/show_bug.cgi?id=459847 Bug ID: 459847 Summary: Touchpad gestures (4 fingers up and down) laggs horrible Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY The 4 finger touchpad gesture swiping up (like showing all activities and their windows) laggs horrible (like 1 fps). The other one (showing all windows, the one with the search bar) also laggs and party even freezes the system. I can't even turn them off, please add an option for that too. STEPS TO REPRODUCE 1. Swipe up or down SOFTWARE/OS VERSION SOperating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.12-051912-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) doesn't follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) doesn't follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 --- Comment #5 from Moritz --- Will there be an update in the next version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459847] Touchpad gestures (4 fingers up and down) laggs horrible
https://bugs.kde.org/show_bug.cgi?id=459847 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459847] Touchpad gestures (4 fingers up and down) laggs horrible
https://bugs.kde.org/show_bug.cgi?id=459847 Moritz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Moritz --- No, I just thought somebody else will report that they are laggy, but when I update kde I update my whole system. They where always laggy. Actually the animation is smoother with a key combination? (how does this happen?) But still, after the animation the whole screen hangs for a couple of 100ms. Then it works as before. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459846] kscreenlocker crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=459846 --- Comment #1 from Moritz --- This bug should have the highest priority, it destorys all KDE neon user (maybe even whole plasma 5.26?) experience. And if we take it in consideration that plasma 5.26 should be released in 3 days. It makes my laptop unuseable, I don't even want to update my other ones. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 459846] kscreenlocker crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=459846 --- Comment #4 from Moritz --- You are right. When updating libqt5waylandclient5 libqt5waylandcompositor5 plasma-wayland-protocols qtwayland5 to debian sid packages and rebooting it works. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 459846] kscreenlocker crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=459846 --- Comment #7 from Moritz --- seems to work again (at least for me) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] New: Taskbar minimum height is too high (28 vs 20)
https://bugs.kde.org/show_bug.cgi?id=464774 Bug ID: 464774 Summary: Taskbar minimum height is too high (28 vs 20) Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.26 Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Hi there, I just updated to the newest neon testing and now my taskbar is large. I mean large for my small screen. It has a minimum height of 28 now and I can not further decrease it. Before the update I had it at 20 and it was way better for me. Please decrease the limit again to something like 20. Thanks! SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.0.9-060009-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] Taskbar minimum height is too high (28 vs 20)
https://bugs.kde.org/show_bug.cgi?id=464774 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] Taskbar minimum height is too high (28 vs 20)
https://bugs.kde.org/show_bug.cgi?id=464774 --- Comment #2 from Moritz --- Yes I do use Otto (https://store.kde.org/p/1358262/), but I used it before and there where no updates in the past month. Can a theme even set a limit there? I mean it does not look buggy, I can not set it lower. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] Taskbar minimum height is too high (28 vs 20) with 3rd-party theme
https://bugs.kde.org/show_bug.cgi?id=464774 --- Comment #4 from Moritz --- Is there any way to force disable this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] Taskbar minimum height is too high (28 vs 20) with 3rd-party theme
https://bugs.kde.org/show_bug.cgi?id=464774 --- Comment #7 from Moritz --- > No because then the panel would look broken with that theme, and you would > file a bug on that instead. :) Yes, users could do. I never made a bug report with theming issues, that should be reported to the theme creator. How about an option in `plasmashellrc` that is only available when editing the file? Could look like this: ``` [PlasmaViews][Panel 3][Defaults] thickness=28 ignoreMinThickness=1 ``` It sounds minor, but acutally I feel kind of disturbed by the taskbar. I normally don't use it, only to check the clock and maybe do wifi settings. I'd love to use autohide, but that is bugged in some circumstances, I please you to add it this small feature. Thanks! (Commit: https://invent.kde.org/plasma/plasma-desktop/-/commit/0910a8b17095700fbed0a4fe1980d012336f6505, bug: https://bugs.kde.org/show_bug.cgi?id=461506). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464774] Taskbar minimum height is too high (28 vs 20) with 3rd-party theme
https://bugs.kde.org/show_bug.cgi?id=464774 --- Comment #9 from Moritz --- Actually not a bad idea. The folder of the theme was different, but now I can finally make it small again. Thanks a lot @veggero. It was not the solution I wanted but it works, hopefully the next theme update does not break it again. Oh no, it looks broken. (actually not, just kidding) Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465017] New: Screen is not turned off anymore after a specific delay
https://bugs.kde.org/show_bug.cgi?id=465017 Bug ID: 465017 Summary: Screen is not turned off anymore after a specific delay Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY Since the plasma testing update (from 5.26) laste week my laptop screen is not turned off anymore. I set a delay of 2 minute of turning off the screen and 2 minutes for standby, it is not working anymore (not on battery nor ac) SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.0.9-060009-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION I do use wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465017] Screen is not turned off anymore after a specific delay
https://bugs.kde.org/show_bug.cgi?id=465017 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465017] Screen is not turned off anymore after a specific delay
https://bugs.kde.org/show_bug.cgi?id=465017 Moritz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Moritz --- *** This bug has been marked as a duplicate of bug 462695 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management stopped working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=462695 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de --- Comment #5 from Moritz --- *** Bug 465017 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management stopped working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #6 from Moritz --- Is this daemon unmaintained? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 488888] New: Impossible to differentiate between two different microphone inputs in 6.1 audio volume system tray widget
https://bugs.kde.org/show_bug.cgi?id=48 Bug ID: 48 Summary: Impossible to differentiate between two different microphone inputs in 6.1 audio volume system tray widget Classification: Plasma Product: plasma-pa Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: moritz1...@googlemail.com CC: isma...@gmail.com, m...@ratijas.tk Target Milestone: --- Created attachment 170746 --> https://bugs.kde.org/attachment.cgi?id=170746&action=edit screenshot Hello, I just got KDE Plasma 6.1 on Arch Linux. When opening the audio volume system tray widget it's now impossible for me to differentiate between the two inputs in my Behringer UMC202HD audio interface. STEPS TO REPRODUCE 1. Open audio volume system tray widget 2. Look at the "microphone section" at the bottom OBSERVED RESULT You will see two items with exactly the same name: "UMC202HD 192k" EXPECTED RESULT You would see two items with different names: 1) "UMC202HD 192k Input 1" 2) "UMC202HD 192k Input 2" SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION It's the change described here: https://pointieststick.com/2024/02/02/this-week-in-kde-converging-on-a-release/ Here is a similar bug: https://bugs.kde.org/show_bug.cgi?id=487658 but the person reporting it was not using Plasma 6.1 - so it must be different(?). Also in their case the problem is described as "not great" in my case it's "impossible" to differentiate. The cause of this "bug" is probably the 'node.nick = "UMC202HD 192k"' property in wpctl. > wpctl status > [...] > Audio > [...] > ├─ Sources: > │ 52. UMC202HD 192k Input 2 [vol: 1.00] > │ 62. Starship/Matisse HD Audio Controller Analog Stereo [vol: 1.00] > │ * 65. UMC202HD 192k Input 1 [vol: 1.00] > wpctl inspect 65 > [...] > alsa.card_name = "UMC202HD 192k" > device.profile.description = "Input 1" > node.description = "UMC202HD 192k Input 1" > node.nick = "UMC202HD 192k" etc. The "device.profile.description" property could differentiate between "Input 1" and "Input 2" ___ Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 488888] Impossible to differentiate between two different microphone inputs in 6.1 audio volume system tray widget
https://bugs.kde.org/show_bug.cgi?id=48 --- Comment #1 from Moritz --- Created attachment 170747 --> https://bugs.kde.org/attachment.cgi?id=170747&action=edit wpctl status + wpctl inspect on the two microphone inputs. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once
https://bugs.kde.org/show_bug.cgi?id=487658 --- Comment #14 from Moritz --- I kind of dislike that Bug 488917 & Bug 48 where marked as duplicate of this. I get that their background / "cause" is the same as Bug 487658 but..: Bug 487658 says that the device names are "very samey" in Comment 7. VS While in Bug 488917 & Bug 48 the device names ARE literally the same. I would argue that this much worse and makes this issue more urgent than Bug 487658 would makes it appear. I created Bug 48 thinking about all the users who don't know how to workaround this issue and are now unable to configure their audio devices because suddenly the names are exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once
https://bugs.kde.org/show_bug.cgi?id=487658 --- Comment #17 from Moritz --- Thank you z...@omaera.org. You summarized the problem better than I could have. The point is that in my (our?) case the crucial information for being able to different devices is not stored in 'node.nick' but in 'device.profile.description' / 'node.description'. 'node.nick' is exactly the same. > wpctl status > [...] > Audio > [...] > ├─ Sources: > │ 52. UMC202HD 192k Input 2 [vol: 1.00] > │ * 65. UMC202HD 192k Input 1 [vol: 1.00] > wpctl inspect 52 > [...] > alsa.card_name = "UMC202HD 192k" > device.profile.description = "Input 2" > node.description = "UMC202HD 192k Input 2" > node.nick = "UMC202HD 192k" > wpctl inspect 65 > [...] > alsa.card_name = "UMC202HD 192k" > device.profile.description = "Input 1" > node.description = "UMC202HD 192k Input 1" > node.nick = "UMC202HD 192k" -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #19 from Moritz ---
@Comment 18
This is my workaround until I proper fix is being implemented.
I am manually overwriting the 'node.nick' property:
> # File location:
> # /home/username/.config/wireplumber/wireplumber.conf.d/51-device-rename.conf
>
> monitor.alsa.rules = [
> {
> matches = [
> {
> node.name =
> "alsa_input.usb-BEHRINGER_UMC202HD_192k-00.HiFi__umc202hd_mono_in_U192k_0_0__source"
> }
> ]
> actions = {
> update-props = {
> node.nick = "UMC202HD Input 1"
> }
> }
> }
> {
> matches = [
> {
> node.name =
> "alsa_input.usb-BEHRINGER_UMC202HD_192k-00.HiFi__umc202hd_mono_in_U192k_0_1__source"
> }
> ]
> actions = {
> update-props = {
> node.nick = "UMC202HD Input 2"
> }
> }
> }
> ]
I followed section 2.3 & 2.4 on the WirePlumber ArchWiki page:
https://wiki.archlinux.org/title/WirePlumber#Obtain_interface_name_for_rules_matching
https://wiki.archlinux.org/title/WirePlumber#Changing_a_device/node_property
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 482480] New: Key Codes F13 - F24 don't get handled as expected in KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=482480 Bug ID: 482480 Summary: Key Codes F13 - F24 don't get handled as expected in KDE Plasma Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: moritz1...@googlemail.com Target Milestone: --- Created attachment 166432 --> https://bugs.kde.org/attachment.cgi?id=166432&action=edit Example: F23 gets recognized as "Touchpad Off" SUMMARY *** I have a macropad (running QMK Firmware) which is able to produce key codes such as F13 - F24. When trying to assign shortcuts in the System Settings e.g.: F23 will get recognized as "Touchpad Off" or F13 as "Launch (9)". I'd expect the system to show F23 as the shortcut button when I assign F23 as the shortcut - and not "Touchpad Off". The System settings shortcuts do work but the F13 - F24 keys don't get recognized in all applications - not even "wrongly" as e.g.: "Touchpad Off". *** STEPS TO REPRODUCE 1. Have a keyboard/macropad where you know for sure that it's able to produce the key codes for F13-F24. 2. Try to assign a key - that sends F13, F14 etc. - to a shortcut in the System Settings. OBSERVED RESULT The populated key under Custom shortcuts will not show F13 - F24 but things like "Launch (9)", "Launch (A)", "Touchpad Off" etc. EXPECTED RESULT The populated key under Custom shortcuts shows e.g.: F13 since I pressed F13 on my macropad. ___ In the shortcut System settings this is only a "visual bug" (I can use the shortcut) but e.g.: I can't use F22 at all in my music-player DeaDBeef - only after creating the .Xmodmap described in ADDITIONAL INFORMATION. Plasma's correct handling of F13 - F24 is thus also needed for user applications. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION On X11 I was able to "fix" this by using a .Xmodmap file containing: keycode 191 = F13 F13 F13 keycode 192 = F14 F14 F14 [...] keycode 202 = F24 F24 F24 This made F13-F24 be recognized as such by the system. But this does not work under KDE Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482480] Key Codes F13 - F24 don't get handled as expected in KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=482480 --- Comment #1 from Moritz --- EDIT: I can confirm this bug on Arch Linux/KDE Plasma 5.27.10 & on KDE Neon 6.0 I also forgot to mention that I can't assign F24, F21 and F19 AT ALL - not even "wrongly" but this got already reported in https://bugs.kde.org/show_bug.cgi?id=422401 I guess. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482480] Key Codes F13 - F24 don't get handled as expected in KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=482480 --- Comment #3 from Moritz --- (In reply to fanzhuyifan from comment #2) > What is the output of `xmodmap -pke`? Do you see F13-F24 in there? Thank you for your reply! No, I see: ``` [...] keycode 191 = XF86Tools NoSymbol XF86Tools keycode 192 = XF86Launch5 NoSymbol XF86Launch5 keycode 193 = XF86Launch6 NoSymbol XF86Launch6 keycode 194 = XF86Launch7 NoSymbol XF86Launch7 keycode 195 = XF86Launch8 NoSymbol XF86Launch8 keycode 196 = XF86Launch9 NoSymbol XF86Launch9 keycode 197 = keycode 198 = XF86AudioMicMute NoSymbol XF86AudioMicMute keycode 199 = XF86TouchpadToggle NoSymbol XF86TouchpadToggle keycode 200 = XF86TouchpadOn NoSymbol XF86TouchpadOn keycode 201 = XF86TouchpadOff NoSymbol XF86TouchpadOff keycode 202 = [...] ``` So this would "explain" why Plasma thinks that e.g.: F23 => keycode 201 => "TouchpadOff" I guess..? And also why keycode 197 (F19) & keycode 202 (F24) are not being registered at all - because they are empty. ___ If I use my .Xmodmap file (for example:) keycode 200 = F22 F22 F22 The output of `xmodmap -pke` obviously changes to ``` [...] keycode 200 = F22 F22 F22` [...] ``` as well (at least in X11 - NOT in wayland) ___ I'd suggest that this should be changed to F13-F24... It's frustrating that Plasma seems to just assume that everyone is using a laptop and assigns things like XF86TouchpadOn, XF86TouchpadOff etc. instead of F13-F24. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482570] New: Right clicking on taskbar allows user to change Panel Spacer " ☑️ Set flexible size " option even when NOT in Edit Mode
https://bugs.kde.org/show_bug.cgi?id=482570 Bug ID: 482570 Summary: Right clicking on taskbar allows user to change Panel Spacer " ☑️ Set flexible size " option even when NOT in Edit Mode Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Spacer Assignee: plasma-b...@kde.org Reporter: moritz1...@googlemail.com Target Milestone: 1.0 Created attachment 166498 --> https://bugs.kde.org/attachment.cgi?id=166498&action=edit My taskbar in "Edit Mode" to highlight where the flexible Panel Spacers are located (1 + 2) SUMMARY *** I just upgraded to Plasma 6. I noticed that when I right click on my taskbar (on a Panel Spacer) I have the option to change " ☑️ Set flexible size ". This is possible even though I am not in Edit Mode. I don't think this makes any sense because it allows me to accidentally mess up my whole taskbar. The taskbar should only be editable in Edit Mode! I'll add some screenshots for clarification. *** STEPS TO REPRODUCE 1. Have a taskbar with a Panel Spacer set to flexible. 2. Make sure to not be in Edit Mode 3. Right click the taskbar, right where the Panel Spacer is OBSERVED RESULT I get a menu with the following options 1) " ☑️ Set flexible size " 2) ➕ Add Widgets... 3) Enter Edit Mode EXPECTED RESULT I only get a menu with the following options: 1) ➕ Add Widgets... 2) Enter Edit Mode SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482570] Right clicking on taskbar allows user to change Panel Spacer " ☑️ Set flexible size " option even when NOT in Edit Mode
https://bugs.kde.org/show_bug.cgi?id=482570 --- Comment #1 from Moritz --- Created attachment 166499 --> https://bugs.kde.org/attachment.cgi?id=166499&action=edit Right clicking on my taskbar when NOT in Edit Mode -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 481031] New: Crash when opening
https://bugs.kde.org/show_bug.cgi?id=481031 Bug ID: 481031 Summary: Crash when opening Classification: Applications Product: korganizer Version: GIT (master) Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY KOrganizer pretty much instantly crashes when opening it (after upgrading from neon 5.27 to plasma 6 unstable). STEPS TO REPRODUCE 1. Open it SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.6.5-060605-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 33.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION Application: KOrganizer (korganizer), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=133488492291072) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=133488492291072) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=133488492291072, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x796849a42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x796849a287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x79684a6d86f3 in qAbort() () at ./src/corelib/global/qglobal.cpp:161 #10 0x79684a6d4055 in qt_message_fatal (message=..., context=) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=, msg=, ap=ap@entry=0x7ffc1f270b00) at ./src/corelib/global/qlogging.cpp:378 #12 0x79684a6d909f in QMessageLogger::fatal(char const*, ...) const (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x79684a6a9261 in qt_assert(char const*, char const*, int) (assertion=assertion@entry=0x79684c4ab9c0 "mIncidences[type].value(uid) == incidence", file=file@entry=0x79684c4ab730 "./src/memorycalendar.cpp", line=line@entry=291) at ./src/corelib/global/qassert.cpp:68 #14 0x79684c40a8a8 in KCalendarCore::MemoryCalendar::Private::insertIncidence(QSharedPointer const&) (this=0x6193af1eda20, incidence=...) at ./src/memorycalendar.cpp:291 #15 0x79684c460989 in KCalendarCore::MemoryCalendar::addIncidence(QSharedPointer const&) (this=0x796830016030, incidence=...) at ./src/memorycalendar.cpp:299 #16 0x796849918edf in Akonadi::CalendarBasePrivate::internalInsert(Akonadi::Item const&) (this=, item=) at ./src/calendarbase.cpp:132 #17 0x79684993119f in Akonadi::ETMCalendarPrivate::itemsAdded(QList const&) (this=0x6193af0f5390, items=...) at ./src/etmcalendar.cpp:264 #18 0x796849931277 in Akonadi::ETMCalendarPrivate::onRowsInsertedInFilteredModel(QModelIndex const&, int, int) (this=0x6193af0f5390, index=, start=, end=) at ./src/etmcalendar.cpp:405 #19 0x79684a6287ae in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc1f271020, r=0x6193af0f5390, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #20 doActivate(QObject*, int, void**) (sender=0x6193af17e880, signal_index=13, argv=0x7ffc1f271020) at ./src/corelib/kernel/qobject.cpp:4021 #21 0x79684a4d6472 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=, _t1=, _t2=, _t3=, _t4=...) at ./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1356 #22 0x79684a4cf896 in QAbstractItemModel::endInsertRows() (this=0x6193af17e880) at ./src/corelib/itemmodels/qabstractitemmodel.cpp:2908 #23 0x79684a4ee745 in QSortFilterProxyModelPrivate::insert_source_items(QList&, QList&, QList const&, QModelIndex const&, Qt::Orientation, bool) (this=this@entry=0x6193af181230, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=true) at ./src/corelib/itemmodels/qsortfilterproxymodel.cpp:932 #24 0x79684a4ef12b in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) (this=0x6193af181230, source_parent=..., start=, end=, orient=Qt::Vertical) at ./src/corelib/itemmodels/qsortfilterproxymodel.cpp:1043 #25 0x79684a4fad87 in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (this=0x6193af181230, source_parent=..., start=0, end=1664) at ./src/corelib/itemmodels/qsortfilterproxymodel.cpp:1685 #26 0x79684a6287ae in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc1f2714a0, r=0x6193af17e880, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #27 doActivate(QObject*, int, void**) (sender=0
[korganizer] [Bug 481031] Crash when opening
https://bugs.kde.org/show_bug.cgi?id=481031 --- Comment #1 from Moritz --- Additionally it prints the following messages: moritz@moritz-82k:~$ korganizer qt.core.qobject.connect: QObject::disconnect: Unexpected nullptr parameter org.kde.pim.akonadicalendar: Error occurred "" "Unable to create persistent search" org.kde.pim.akonadicalendar: Error occurred "" "Unable to create persistent search" ASSERT: "mIncidences[type].value(uid) == incidence" in file ./src/memorycalendar.cpp, line 291 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445695] New: Crash in normal usage: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=445695 Bug ID: 445695 Summary: Crash in normal usage: Segmentation fault Product: Akonadi Version: GIT (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- Created attachment 143692 --> https://bugs.kde.org/attachment.cgi?id=143692&action=edit Crashdump SUMMARY Pretty randomly the desktop crashes. It is really annoying, all my programs get killed, data gets lost. STEPS TO REPRODUCE I really have no clue. But when my graphic tablet (walcom) is attached, the crash happens far more often (and it is really annoying there). Sometimes (but only when I press CTRL + SHIFT + K to make a git push in IntelliJ) it also happens. OBSERVED RESULT I get a black screen that shows some @ chars in the first line, then I have to wait some seconds and I see my (killed; no programms open anymore) desktop again. EXPECTED RESULT Work normal SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Testing Edition KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel: 5.15.1 generic I am using wayland. I got an AMD Ryzon 5500U with an integrated Radeon RENOIR graphics card. ADDITIONAL INFORMATION See the crash.txt file for the crash information (with debug symbols installed). The crash report daemon tells me, that the information *is useful*. This bug has really high priority to me, I use KDE Plasma with its applications every day (also in school with my laptop). This device has to work 100%. Please take a look at is asap. Thanks -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445695] Crash in normal usage: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=445695 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445695] Crash in normal usage: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=445695 Moritz changed: What|Removed |Added Version|GIT (master)|5.18.3 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445695] Crash in normal usage: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=445695 --- Comment #1 from Moritz --- I can observe this in dmesg: [ 9617.567876] xdg-desktop-por[20173]: segfault at 0 ip 7efdcd6a45f4 sp 7efdc67fbc78 error 4 in libglib-2.0.so.0.6400.6[7efdcd68+84000] [ 9617.567905] Code: f8 5b 5d c3 66 90 f3 0f 1e fa 48 83 ec 08 e8 33 ce fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa <0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] New: kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 Bug ID: 446255 Summary: kwin_wayland randomly crashes: segfault Product: kwin Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- SUMMARY This happens every time before akondai crashes, see here for details: https://bugs.kde.org/show_bug.cgi?id=445695 Crash in dmesg: kwin_wayland[1898]: segfault at 4c ip 7f3f77d1da62 sp 7ffd18420f30 error 4 in libQt5Quick.so.5.15.3[7f3f77c5b000+318000] [24407.692257] xdg-desktop-por[36735]: segfault at 0 ip 7f9952e1d5f4 sp 7f9943ffec78 error 4 in libglib-2.0.so.0.6400.6[7f9952df9000+84000] ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #2 from Moritz --- Created attachment 144152 --> https://bugs.kde.org/attachment.cgi?id=144152&action=edit gdb crash report 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #3 from Moritz --- Created attachment 144153 --> https://bugs.kde.org/attachment.cgi?id=144153&action=edit gdp backtrace 2 (newer) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #4 from Moritz --- Created attachment 144154 --> https://bugs.kde.org/attachment.cgi?id=144154&action=edit support information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 Moritz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #5 from Moritz --- The 2nd backtrace is newer, it had no @ chars in the top left corner and was cought directly after switching from tty3 to tty2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #6 from Moritz --- Maybe those are even 2 different bugs. The first (1) snapshot was made after the crash while working in IntelliJIdea (no walcom attached). The second was made while drawing in with the walcom in Xournal++. I switched to tty3 to see gdb attachment status and then switched back to tty2 (it instantly crashed) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 Moritz changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #7 from Moritz --- I don't want to rush you, but could you please fix this prioritized? My walcom tablet is completely unsuable on this device. Also without the tablet the crash is occuring pretty often, plasma is really unusable to me. Thanks Moritz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446255] kwin_wayland randomly crashes: segfault
https://bugs.kde.org/show_bug.cgi?id=446255 --- Comment #8 from Moritz --- Please take a look at it asap, it crashes several times per day while working on this device. It is unusable! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417271] Plasma crashes when leaving Network in Stand By
https://bugs.kde.org/show_bug.cgi?id=417271 Moritz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Moritz --- Can not reproduce it anymore for quite a while, I guess it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451359] Can not wake up device with walcom tablet pen
https://bugs.kde.org/show_bug.cgi?id=451359 --- Comment #2 from Moritz --- Maybe waykeup is not the correct word. I mean turning the screen on. I can turn on my laptop when moving the cursor (mouse or touchpad) or pressing keys or pressing the power button. I can wake up pmy device when pressing any key or the power button. I should be abke ti turn on the screen when moving the cursor with the pen. I don't know if it is to kwin, but it could be, it is the display manager? -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 410760] While copying files which dolphin, the graphics hangs up
https://bugs.kde.org/show_bug.cgi?id=410760 Moritz changed: What|Removed |Added Product|dolphin |gcompris Component|general |general Version|19.04.3 |unspecified Assignee|dolphin-bugs-n...@kde.org |jaz...@gmail.com --- Comment #8 from Moritz --- Acutally I can reproduce this really well and it is really annoying. Some things I have notices over the time: - It is not specific to dolphin, the whole plasma ui hangs (including all applications, so it migth be a kwin or frameworks problem). - I can create a high disk usage with any tool or just force plasma and all its components to not be able to have a high throughpoint - Prefectly recreateable with a really slow virtual machine A general thing is: the lower the io, the more it hangs. If I (e.g. start kde neon via pxe) and remove/stop the nfs server, the whole ui hangs completely until the server is back up again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410760] While copying files which dolphin, the graphics hangs up
https://bugs.kde.org/show_bug.cgi?id=410760 Moritz changed: What|Removed |Added Product|gcompris|kwin Assignee|jaz...@gmail.com|kwin-bugs-n...@kde.org Component|general |general Target Milestone|--- |5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452071] New: Akondai is not synchronizing all caldav appointments
https://bugs.kde.org/show_bug.cgi?id=452071 Bug ID: 452071 Summary: Akondai is not synchronizing all caldav appointments Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- STEPS TO REPRODUCE 1. Create a cal dav server (e.g. https://sabre.io/baikal/) 2. Import (not via akondai) a ton of appointments (let's say 100) spread out (over several months) 3. Add the resource to akondai and let it synchronize all appointments (without a time limit) 4. Not all appointments can be seen in akondai (e.g. in korganizer or in the dev console) Another way to reproduce is: 1. have 2 cal dav resource configured 2. move an appointment from 1 cal dav resource to another 3. oberserve that it does not get synchronized to the cal dav server SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17-051700-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.5 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION This is a production device and it used fully normal data. I am using it on 2 devices (both on newest version) and the appointments don't get synchronized correctly. (With correctly I mean: Some events get synchronized and some will. If you take a look into the dev console, you can see the appointment ids. they start (in my case) at 1, go up to 15, then some gaps and then suddently from 104 to 423. there may be some missing, because they got delteted, but not 300. On my android device with davx5 everything works fine.) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452071] Akondai is not synchronizing all caldav appointments
https://bugs.kde.org/show_bug.cgi?id=452071 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452071] Akondai is not synchronizing all caldav appointments
https://bugs.kde.org/show_bug.cgi?id=452071 --- Comment #1 from Moritz --- Hey, ist there anybody who could take a look at this? It makes Korganizer pretty useless, I really like the program. It forces me to switch back to thunderbird. Thanks -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452071] Akondai is not synchronizing all caldav appointments
https://bugs.kde.org/show_bug.cgi?id=452071 --- Comment #2 from Moritz --- Switching to Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442177] New: Plasmashell crashes after moving mouse on task bar
https://bugs.kde.org/show_bug.cgi?id=442177 Bug ID: 442177 Summary: Plasmashell crashes after moving mouse on task bar Product: plasmashell Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: moritz+...@thinksilicon.de CC: plasma-b...@kde.org Target Milestone: 1.0 Plasma crashes on occasions when moving the mouse onto the taskbar, or when focusing different windows. STEPS TO REPRODUCE 1. Move mouse on task bar / alt-tab to different window OBSERVED RESULT Plasma crashes and sometimes restarts. Sometimes has to be restarted manually by running plasmashell start EXPECTED RESULT Plasma doesn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: plasma5-desktop-5.22.5-1.1.x86_64 KDE Frameworks Version: plasma-framework-5.85.0-2.1.x86_64 Qt Version: libQt5Core5-5.15.2+kde222-1.1.x86_64 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442177] Plasmashell crashes after moving mouse on task bar
https://bugs.kde.org/show_bug.cgi?id=442177 --- Comment #1 from Moritz --- Created attachment 141391 --> https://bugs.kde.org/attachment.cgi?id=141391&action=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.2 - What I was doing when the application crashed: Moved mouse from Window onto task bar. This also happens occasionally when just switching windows. -- Backtrace (Reduced): #6 0x7fd07ee7ab44 in __glXInitialize (dpy=dpy@entry=0x55ae137387a0) at ../src/glx/glxext.c:886 #7 0x7fd07ee7b584 in GetGLXPrivScreenConfig (dpy=dpy@entry=0x55ae137387a0, scrn=scrn@entry=0, ppriv=ppriv@entry=0x7fd07f7fd5a8, ppsc=ppsc@entry=0x7fd07f7fd5b0) at ../src/glx/glxcmds.c:173 #8 0x7fd07ee7b93f in glXQueryExtensionsString (dpy=0x55ae137387a0, screen=0) at ../src/glx/glxcmds.c:1319 #9 0x7fd0ae76d6a5 in Plasma::WindowThumbnail::resolveGLXFunctions() (this=0x7fd070016fe0) at /usr/src/debug/plasma-framework-5.85.0-2.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:552 #10 Plasma::WindowThumbnail::windowToTextureGLX(Plasma::WindowTextureNode*) (textureNode=, this=0x7fd070016fe0) at /usr/src/debug/plasma-framework-5.85.0-2.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:379 -- You are receiving this mail because: You are watching all bug changes.
