[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Thomas Rother changed: What|Removed |Added CC|t.rot...@netzwissen.de | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465680] Fails to start due to missing library in openSUSE
https://bugs.kde.org/show_bug.cgi?id=465680 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de --- Comment #6 from Thomas Rother --- Confirmend for update to 7.9 on openSUSE Tumbleweed, VERSION="20230213" using the standard repos -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465680] Fails to start due to missing library in openSUSE
https://bugs.kde.org/show_bug.cgi?id=465680 Thomas Rother changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #8 from Thomas Rother --- I reopened this bug, I would not consider it as "resolved" until there is no working build available - even when it will be fixed in a future version ;-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465680] Fails to start due to missing library in openSUSE
https://bugs.kde.org/show_bug.cgi?id=465680 --- Comment #10 from Thomas Rother --- ok, you are right, this should be moved to https://bugzilla.suse.com/ as it is a build issue, not a source code issue -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465680] Fails to start due to missing library in openSUSE
https://bugs.kde.org/show_bug.cgi?id=465680 Thomas Rother changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #17 from Thomas Rother --- confirmed, this version update fixes the dependency issue with libopenblas (version info from /etc/os-release) NAME="openSUSE Tumbleweed" # VERSION="20230221" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20230221" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481975] Plasma 6 Wayland flickering/stuttering/jittering on web and electron apps and games on Nvidia. Seemigly reverting to previous states
https://bugs.kde.org/show_bug.cgi?id=481975 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438162] New: preview rendering fails with nvidia driver
https://bugs.kde.org/show_bug.cgi?id=438162 Bug ID: 438162 Summary: preview rendering fails with nvidia driver Product: kdenlive Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: t.rot...@netzwissen.de Target Milestone: --- SUMMARY preview rendering fails STEPS TO REPRODUCE Perform preview rendering according to https://kdenlive.org/en/project/timeline-preview-rendering/ OBSERVED RESULT [h264_nvenc @ 0x7f850c201c80] Width 6000 exceeds 4096[h264_nvenc @ 0x7f850c201c80] No capable devices found+ + + RENDERING FINISHED + + + EXPECTED RESULT preview rendering finishes successfully SOFTWARE/OS VERSIONS OpenSUSE Tumbleweed MLT version 6.26.1 Operating System: openSUSE Tumbleweed 20210602 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-2-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 No problems with the standard rendering through "f=mp4 movflags=+faststart vcodec=libx264 progressive=1 g=15 bf=2 crf=%quality acodec=aac ab=%audiobitrate+'k'" -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 392980] KOrganizer crashes all times when closing
https://bugs.kde.org/show_bug.cgi?id=392980 Thomas Rother changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Thomas Rother --- worksforme on current releases -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 417042] When new app launched, kdeinit5 always crashes in Baloo::PostingDB::fetchTermsStartingWith() while trying to fetch tags
https://bugs.kde.org/show_bug.cgi?id=417042 Thomas Rother changed: What|Removed |Added CC|t.rot...@netzwissen.de | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing
https://bugs.kde.org/show_bug.cgi?id=445095 Thomas Rother changed: What|Removed |Added Status|RESOLVED|REOPENED CC||t.rot...@netzwissen.de Resolution|FIXED |--- --- Comment #10 from Thomas Rother --- Is this really solved? On the current plasma 6.1 with openSUSE tumbleweed or LEAP 15.x there is no touchpad status indicator. And it can not be found for installation though the rpm repos. I am also on a Dell XPS 15.x and the very sensitive touchpad makes it hard to type - so a visual indicator definitely makes sense! Version info: kde plasma 6.1.2 frameworks: 6.3.0 qt: 6.7.2 X11 and wayland look similar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing
https://bugs.kde.org/show_bug.cgi?id=445095 Thomas Rother changed: What|Removed |Added Version|5.23.2 |6.1.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing on X11
https://bugs.kde.org/show_bug.cgi?id=445095 --- Comment #12 from Thomas Rother --- I don't see it, not on my KDE 6.1/wayland Machine (DELL Precision 7680) and even not on a DELL XPS 15 which is still using X11. So I would still consider this issue as "unsolved/open" ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing on X11
https://bugs.kde.org/show_bug.cgi?id=445095 --- Comment #14 from Thomas Rother --- Hi Nate, thanks for clarification. In my case, the main requirement is the visualization of the touchpad status, whether it is "on" or "off". The actual switching can be done with a function key (f9) which is - I suppose - pre-assigned by the Dell BIOS. Some kind of visualization would be very helpful for both X11 and wayland environment. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 395683] Entry for security-aware messengers
https://bugs.kde.org/show_bug.cgi?id=395683 Thomas Rother changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Thomas Rother --- Status on kaddressbook 5.21.3 Telegram can be added, Threema and Signal still missing A number of messenger seem to be obsolete, pretty obscure or proprietary (AIM, Gadu-Gadu, GroupWise, Meanwhile, MSN Messenger, QQ) -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 384013] Kleopatra does not save revocation certificate
https://bugs.kde.org/show_bug.cgi?id=384013 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de Platform|Fedora RPMs |openSUSE RPMs Version|unspecified |3.1.1 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Thomas Rother --- confirmed for latest opensuse leap 15.1 and kleopatra 3.1.3 (framework 5..55.0, qt 5.9.7) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418712] Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 --- Comment #3 from Thomas Rother --- Created attachment 127570 --> https://bugs.kde.org/attachment.cgi?id=127570&action=edit settings.ini -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418712] Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 --- Comment #4 from Thomas Rother --- xrdb -query | grep dpi gives no "96" I'm now on TW 20200413, Plasma 5.18.4 and just re-checked the issue, something has changed obviously, see screenshot: both kde konsole and gtk thunderbird seem to have the same font size (roboto slab 12) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418712] Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 --- Comment #5 from Thomas Rother --- Created attachment 127571 --> https://bugs.kde.org/attachment.cgi?id=127571&action=edit screenshot native qt/plasma and gtk application -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418712] Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 --- Comment #7 from Thomas Rother --- In the moment it looks like that. Let me observe it the next few days, then I would close the bug again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 415863] New: kdeinit5 frequently crashes on normal operation (tumbleweed)
https://bugs.kde.org/show_bug.cgi?id=415863 Bug ID: 415863 Summary: kdeinit5 frequently crashes on normal operation (tumbleweed) Product: frameworks-kinit Version: 5.65.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: t.rot...@netzwissen.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 124891 --> https://bugs.kde.org/attachment.cgi?id=124891&action=edit crash report kdeinit5 frequently crashes during normal operation (tumbleweed), last seen on tumbleweed 20191231, but this happens since a few weeks, I see no clear root cause for this. OBSERVED RESULT kdeinit5 crash EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Betriebssystem: openSUSE Tumbleweed 20191231 KDE-Plasma-Version: 5.17.4 KDE-Frameworks-Version: 5.65.0 Qt-Version: 5.13.1 Kernel-Version: 5.3.12-2-default Art des Betriebssystems: 64-bit Prozessoren: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Speicher: 31,1 GiB Arbeitsspeicher ADDITIONAL INFORMATION see attachment, reporting through drkonqi not possible -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364441] Option "Symbols/Sort by/Not sorted" does not work for Desktop folder
https://bugs.kde.org/show_bug.cgi?id=364441 Thomas Rother changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Thomas Rother --- works for me in 5.17 (tumbleweed), should be closed -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 418712] New: Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 Bug ID: 418712 Summary: Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small Product: plasma-integration Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: t.rot...@netzwissen.de Target Milestone: --- Plasma 5.18 LTS claims to have this feature: "GTK apps now also automatically inherit Plasma's settings for fonts, icons, mouse cursors and more" instead, in the current Opensuse Tumbleweed, the fonts in Firefox and Thunderbird are tiny and there is no systemsettings applet to change the settings manually. A manual edit of ~/.config/gtk-3.0>settings.ini does not work as workaround. Environment: plasma 5.18.2, frameworks 5.67.0, qt 5.14.1 (current tumbleweed) Bug is reported here on request from f...@suse.com, original report was https://bugzilla.opensuse.org/show_bug.cgi?id=1166267 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418712] Plasma 5.18.2: gtk inheritance of fonts etc. not working, fonts in FB and TB are small
https://bugs.kde.org/show_bug.cgi?id=418712 Thomas Rother changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from Thomas Rother --- no longer valid on current TW release -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388127] Kwin crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=388127 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de --- Comment #11 from Thomas Rother --- As a refererence see https://bugzilla.opensuse.org/show_bug.cgi?id=1101560 for the same issue with switching desktops on current OpenSUSE Leap 15 (KDE 5.12.5, Frameworks 5.45.0, Qt 5.9.4), Kernel 4.12.14). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364441] Option "Symbols/Sort by/Not sorted" does not work for Desktop folder
https://bugs.kde.org/show_bug.cgi?id=364441 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de --- Comment #1 from Thomas Rother --- Confirmed for current Plasma 5 in OpenSUSE Leap 42.3 (Plasma 5.8.7, KDE Framework 5.32.0, QT 5.6.2). The sorting option (e.g. alphabetically) is not saved and folders appear in a "chaotic order" which is a major disadvantage for a professional workflow ... -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 392980] New: KOrganizer crashes all times when closing
https://bugs.kde.org/show_bug.cgi?id=392980 Bug ID: 392980 Summary: KOrganizer crashes all times when closing Product: korganizer Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: t.rot...@netzwissen.de Target Milestone: --- Application: korganizer (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.120-45-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Closing KOrganizer, the crash appears always when closing. Using standard Leap 42.3 and standard KOrganizer from distro repository The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f170b14e980 (LWP 10445))] Thread 4 (Thread 0x7f16d6dee700 (LWP 10451)): #0 0x7f17069ed30d in poll () at /lib64/libc.so.6 #1 0x7f16fdfe9314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f16fdfe942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f170750f1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f17074bcbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f17072f7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f17072fca29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f16fe506724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f17069f5e8d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f16d75ef700 (LWP 10449)): #0 0x7f17069ed30d in poll () at /lib64/libc.so.6 #1 0x7f16fdfe9314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f16fdfe942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f170750f1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f17074bcbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f17072f7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f17072fca29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f16fe506724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f17069f5e8d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f16dcbc3700 (LWP 10448)): #0 0x7f17069ed30d in poll () at /lib64/libc.so.6 #1 0x7f16fdfe9314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f16fdfe942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f170750f1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f17074bcbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f17072f7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1705ee4295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f17072fca29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f16fe506724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f17069f5e8d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f170b14e980 (LWP 10445)): [KCrash Handler] #6 0x in () #7 0x7f17089f97ca in QAbstractSlider::setValue(int) () at /usr/lib64/libQt5Widgets.so.5 #8 0x7f17014b94c9 in () at /usr/lib64/libKF5WidgetsAddons.so.5 #9 0x7f17074e9e26 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7f17088ff28c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f17089038ea in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f17074bebe5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f17074c09ca in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f170750fb03 in () at /usr/lib64/libQt5Core.so.5 #15 0x7f16fdfe9134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x7f16fdfe9388 in () at /usr/lib64/libglib-2.0.so.0 #17 0x7f16fdfe942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x7f170750f18c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7f17074bcbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7f17074c4ae6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #21 0x00409371 in () #22 0x7f1706929725 in __libc_start_main () at /lib64/libc.so.6 #23 0x00409509 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388127] Kwin crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=388127 --- Comment #13 from Thomas Rother --- See comment 11 and referenced bug issue https://bugzilla.opensuse.org/show_bug.cgi?id=1101560. The problem described there was solved with a libxkb patch, it was deployed for both OpenSUSE Leap 15.0 and SLES: openSUSE-RU-2018:3294-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1101560 CVE References: Sources used: openSUSE Leap 15.0 (src):libxcb-1.13-lp150.2.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 395683] New: Entry for security-aware messengers
https://bugs.kde.org/show_bug.cgi?id=395683 Bug ID: 395683 Summary: Entry for security-aware messengers Product: kaddressbook Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: t.rot...@netzwissen.de CC: to...@kde.org Target Milestone: --- Created attachment 113484 --> https://bugs.kde.org/attachment.cgi?id=113484&action=edit Messaging entry in Kontact The pulldown menu of KAdressbook/Kontact should also offer entries for security-aware messengers so that people can add these contact data.Proposed messengers are a) Signal >> Mobile phone number b) Threema >> "Threema ID", 8-digit alphanumeric string c) Telegram >> Username, alphanumeric string, length ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493861] kded6 crashes in OpenconnectAuthWidget::formLoginClicked
https://bugs.kde.org/show_bug.cgi?id=493861 Thomas Rother changed: What|Removed |Added Keywords||regression Status|REPORTED|CONFIRMED Component|general |applet Version|unspecified |6.2.0 Ever confirmed|0 |1 --- Comment #2 from Thomas Rother --- Distro: openSUSE Tumbleweed Initial selection of the openconnect connection group is possible. The crash appears when entering username and password. Sometimes its crashing directly (see drkonqui data). In most cases the UI is just unusable, the "login" button for username/password disappears/flickers. This looks like a functional regression from 6.1.x. Nmcli must be used as fallback. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493861] kded6 crashes in OpenconnectAuthWidget::formLoginClicked
https://bugs.kde.org/show_bug.cgi?id=493861 --- Comment #1 from Thomas Rother --- This bug is still reproducible after the last Tumbleweed update. Therefore I can not open my business VPN which I need every day. Any ideas? Can I help debugging somehow? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 493861] New: kded6 crash
https://bugs.kde.org/show_bug.cgi?id=493861 Bug ID: 493861 Summary: kded6 crash Classification: Frameworks and Libraries Product: frameworks-kded Version: 6.6.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: t.rot...@netzwissen.de CC: kdelibs-b...@kde.org Target Milestone: --- Application: kded6 (6.6.0) Qt Version: 6.7.2 Frameworks Version: 6.6.0 Operating System: Linux 6.11.0-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 6.1.5 [CoredumpBackend] -- Information about the crash: reproducible on two machines, vpn connections fail The crash can be reproduced every time. -- Backtrace: Application: kded6 (kded6), signal: Segmentation fault [New LWP 2888] [New LWP 2949] [New LWP 2896] [New LWP 2894] [New LWP 2952] [New LWP 4021] [New LWP 2951] [New LWP 2950] [New LWP 2968] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/kded6'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fd07fa94c5c in __pthread_kill_implementation () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fd08005b940 (LWP 2888))] python sentry-sdk not installed :( Cannot QML trace cores :( [Current thread is 1 (Thread 0x7fd08005b940 (LWP 2888))] Thread 9 (Thread 0x7fd068a006c0 (LWP 2968)): #0 0x7fd07fb05aff in poll () from /lib64/libc.so.6 #1 0x7fd06944d451 in ?? () from /lib64/libpulse.so.0 #2 0x7fd069437634 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7fd069441be6 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7fd069441c90 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7fd069452104 in ?? () from /lib64/libpulse.so.0 #6 0x7fd068e1cbbf in ?? () from /usr/lib64/pulseaudio/libpulsecommon-17.0.so #7 0x7fd07fa92e22 in start_thread () from /lib64/libc.so.6 #8 0x7fd07fb1433c in __clone3 () from /lib64/libc.so.6 Thread 8 (Thread 0x7fd06b2006c0 (LWP 2950)): #0 0x7fd07fb05aff in poll () from /lib64/libc.so.6 #1 0x7fd0800c3cdf in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fd0800c43ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fd0800c4431 in ?? () from /lib64/libglib-2.0.so.0 #4 0x7fd0800f181e in ?? () from /lib64/libglib-2.0.so.0 #5 0x7fd07fa92e22 in start_thread () from /lib64/libc.so.6 #6 0x7fd07fb1433c in __clone3 () from /lib64/libc.so.6 Thread 7 (Thread 0x7fd06a8006c0 (LWP 2951)): #0 0x7fd07fb05aff in poll () from /lib64/libc.so.6 #1 0x7fd0800c3cdf in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fd0800c43ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fd074a6099d in ?? () from /usr/lib64/gio/modules/libdconfsettings.so #4 0x7fd0800f181e in ?? () from /lib64/libglib-2.0.so.0 #5 0x7fd07fa92e22 in start_thread () from /lib64/libc.so.6 #6 0x7fd07fb1433c in __clone3 () from /lib64/libc.so.6 Thread 6 (Thread 0x7fd043e006c0 (LWP 4021)): #0 0x7fd07fa8f25e in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7fd07fa91fa0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fd0804f8fbb in QWaitConditionPrivate::wait (deadline=..., this=0x559f5b7e9d30) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:102 #3 QWaitCondition::wait (this=, mutex=0x559f5c156098, deadline=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:180 #4 0x7fd04b7af6f8 in OpenconnectAuthWorkerThread::processAuthFormP (this=0x559f5c48a120, form=0x7fd0280079a0) at /usr/src/debug/plasma-nm-6.1.5/vpn/openconnect/openconnectauthworkerthread.cpp:197 #5 OpenconnectAuthStaticWrapper::processAuthForm (obj=0x559f5c48a120, form=0x7fd0280079a0) at /usr/src/debug/plasma-nm-6.1.5/vpn/openconnect/openconnectauthworkerthread.cpp:75 #6 0x7fd04b6f2cf0 in ?? () from /lib64/libopenconnect.so.5 #7 0x7fd04b6febce in ?? () from /lib64/libopenconnect.so.5 #8 0x7fd04b7afcfe in OpenconnectAuthWorkerThread::run (this=0x559f5c48a120) at /usr/src/debug/plasma-nm-6.1.5/vpn/openconnect/openconnectauthworkerthread.cpp:125 #9 0x7fd0804ed139 in operator() (__closure=) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:326 #10 (anonymous namespace)::terminate_on_exception > (t=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:262 #11 QThreadPrivate::start (arg=0x559f5c48a120) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:285 #12 0x7fd07fa92e22 in start_thread () from /lib64/libc.so.6 #13 0x7fd07fb1433c in __clone3 () from /lib64/libc.so.6 Thread 5 (Thread 0x7fd069e006c0 (L
[systemsettings] [Bug 494390] System settings freezes when trying to access energy management and language is set to German
https://bugs.kde.org/show_bug.cgi?id=494390 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de Version|6.1.5 |6.2.2 --- Comment #4 from Thomas Rother --- Same behaviour here on openSUSE, confirmed for Distributor ID: openSUSE Description:openSUSE Tumbleweed Release:20241102 with current kde plasma 6.2.2, frameworks 6.7, Qt 6.8.0. The kcmshell call shows thommie@odysseus4:~> kcmshell6 kcm_powerdevilprofilesconfig qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton* qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton* qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton* qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton* -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494390] System settings freezes when trying to access energy management and language is set to German
https://bugs.kde.org/show_bug.cgi?id=494390 --- Comment #10 from Thomas Rother --- (In reply to Nate Graham from comment #9) > Hmm, is the `org_kde_powerdevil` process running? odysseus4:~ # ps -aux | grep org_kde_powerdevil thommie 4708 0.2 0.1 1331796 115492 ? Ssl 21:26 0:00 /usr/libexec/org_kde_powerdevil root7459 0.0 0.0 3936 1792 pts/2S+ 21:29 0:00 grep --color=auto org_kde_powerdevil -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494390] System settings freezes when trying to access energy management and language is set to German
https://bugs.kde.org/show_bug.cgi?id=494390 --- Comment #8 from Thomas Rother --- (In reply to Nate Graham from comment #7) > Thanks for the data point. Can you provide a rough list of the kinds of > customizations you've made to your user account? Anything significant? Hm, nothing relevant, but what kind of customization could be relevant? As I can not edit the power settings through UI, they are default: thommie@odysseus4:~/.config> powerprofilesctl performance: CpuDriver: intel_pstate PlatformDriver: platform_profile Degraded: no * balanced: CpuDriver: intel_pstate PlatformDriver: platform_profile power-saver: CpuDriver: intel_pstate PlatformDriver: platform_profile Just a note: I saw that the deleted powermanagementprofilesrc was created automagically. It contains [Migration] MigratedProfilesToPlasma6=powerdevilrc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494390] System settings freezes when trying to access energy management and language is set to German
https://bugs.kde.org/show_bug.cgi?id=494390 --- Comment #6 from Thomas Rother --- (In reply to Nate Graham from comment #5) > Cannot reproduce with `LANGUAGE=de_DE kcmshell6 > kcm_powerdevilprofilesconfig` on current git master. Is anyone able to > reproduce this in a new clean user account? I tested this on the machine where I have this issue (its already de_DE). With a "clean" user there is no problem with the kcm_powerdevilprofilesconfig UI. So I assume it has to do with some user-side config setting. But a deletion of the .config/powerdevilrc and powermanagementprofilesrc did not change anything. Any other ideas? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493861] kded6 crashes in OpenconnectAuthWidget::formLoginClicked
https://bugs.kde.org/show_bug.cgi?id=493861 Thomas Rother changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Thomas Rother --- now fixed with openSUSE Tumbleweed 20250209 KDE-Plasma-Version: 6.2.5 KDE-Frameworks-Version: 6.10.0 Qt-Version: 6.8.2 Kernel-Version: 6.13.1-1-default (64-bit) Grafik-Plattform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499773] systemsettings kcm_powerdevilprofilesconfig crashes
https://bugs.kde.org/show_bug.cgi?id=499773 --- Comment #8 from Thomas Rother --- current font is "Roboto 14". I played with different fonts: roboto: crash carlito: no crash <<<< cantarell: crash deja vu serif: crash deja vu sans: crash noto serif: crash noto sans: crash libfreetype6 is 2.13.2-2.3. Note that the crash only happens in the "Energiemanagement" widget, all other settings have no issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499773] New: systemsettings kcm_powerdevilprofilesconfig crashes
https://bugs.kde.org/show_bug.cgi?id=499773 Bug ID: 499773 Summary: systemsettings kcm_powerdevilprofilesconfig crashes Classification: Plasma Product: plasmashell Version: 6.2.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Power management & brightness Assignee: plasma-b...@kde.org Reporter: t.rot...@netzwissen.de Target Milestone: 1.0 KDE Plasma gui for systemsettings kcm_powerdevilprofilesconfig crashes if used. This happens since the update to kde6. I cleaned .config/powerdevilrc and powermanagementprofilesrc and restarted thommie@odysseus4:~/.config> systemctl --user status plasma-powerdevil.service ● plasma-powerdevil.service - Powerdevil Loaded: loaded (/usr/lib/systemd/user/plasma-powerdevil.service; static) Active: active (running) since Mon 2025-02-10 19:42:54 CET; 6s ago Invocation: 15a0fbb1ce194c299a1acc16a710b652 Main PID: 22850 (org_kde_powerde) Tasks: 10 (limit: 76514) CPU: 759ms CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service └─22850 /usr/libexec/org_kde_powerdevil Feb 10 19:42:52 odysseus4 systemd[2684]: Starting Powerdevil... Feb 10 19:42:52 odysseus4 org_kde_powerdevil[22850]: Initializing libddcutil. ddcutil version: 2.1.4, shared library: /u> Feb 10 19:42:52 odysseus4 org_kde_powerdevil[22850]: Options passed from client: Feb 10 19:42:52 odysseus4 org_kde_powerdevil[22850]: Applying combined options: Feb 10 19:42:54 odysseus4 org_kde_powerdevil[22850]: Library initialization complete. Feb 10 19:42:54 odysseus4 org_kde_powerdevil[22850]: org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback Feb 10 19:42:54 odysseus4 systemd[2684]: Started Powerdevil. Feb 10 19:42:54 odysseus4 org_kde_powerdevil[22850]: org.kde.powerdevil: Handle button events action could not check for screen configuration qq ~ starting the systemsetting from the shell shows: thommie@odysseus4:~/.config> systemsettings kcm_powerdevilprofilesconfig Failed to query platform profile choices "No such object path '/org/kde/Solid/PowerManagement/Actions/PowerProfile'" power-profiles daemon is running: odysseus4:~ # systemctl status power-profiles-daemon.service ● power-profiles-daemon.service - Power Profiles daemon Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service; disabled; preset: disabled) Active: active (running) since Mon 2025-02-10 20:10:08 CET; 4min 33s ago Invocation: 370990fd8b3d4ea580816e38d8bb62d7 Main PID: 3749 (power-profiles-) Tasks: 4 (limit: 76514) CPU: 48ms CGroup: /system.slice/power-profiles-daemon.service └─3749 /usr/libexec/power-profiles-daemon Feb 10 20:10:08 odysseus4 systemd[1]: Starting Power Profiles daemon... Feb 10 20:10:08 odysseus4 systemd[1]: Started Power Profiles daemon. System data: Operating System: openSUSE Tumbleweed 20250209 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499773] systemsettings kcm_powerdevilprofilesconfig crashes
https://bugs.kde.org/show_bug.cgi?id=499773 --- Comment #6 from Thomas Rother --- (In reply to Nicolas Fella from comment #5) > Thanks. The crash happens somewhere deep in font handling code (freetype), > so I'm inclined to say that this isn't a bug in KDE code OK, but I have no other issues or rendering effects on this machine which could be linked to freetype stuff. Is this more a distro issue and should thus be transferred to the opensuse bugzilla? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499773] systemsettings kcm_powerdevilprofilesconfig crashes
https://bugs.kde.org/show_bug.cgi?id=499773 --- Comment #3 from Thomas Rother --- Created attachment 178124 --> https://bugs.kde.org/attachment.cgi?id=178124&action=edit coredumpctl gdb 4467 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499773] systemsettings kcm_powerdevilprofilesconfig crashes
https://bugs.kde.org/show_bug.cgi?id=499773 --- Comment #2 from Thomas Rother --- Hm, coredumpctl --reverse shows the crashes: Mon 2025-02-10 20:11:54 CET4467 1000 1000 SIGABRT present /usr/bin/systemsettings12.3M Mon 2025-02-10 19:45:05 CET 22336 1000 1000 SIGABRT present /usr/bin/systemsettings12.5M Mon 2025-02-10 19:26:35 CET 16696 1000 1000 SIGABRT present /usr/bin/systemsettings12.8M Mon 2025-02-10 19:14:40 CET 16039 1000 1000 SIGABRT present /usr/bin/systemsettings12.3M When I start systemsetting "Energieverwaltung" the window is empty and, after a fexw seconds, teh window crashes "systemsettings kcm_powerdevilprofilesconfig" shows no results at all. Enclosed is the result of coredumpctl gdb 4467 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498465] Additional control panel only appears partly after login
https://bugs.kde.org/show_bug.cgi?id=498465
Thomas Rother changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Thomas Rother ---
Yes. But I tried with different task manager widgets ("Anwendungsmenu"). What
you see in the broken screenshot is one of the application widgets, all other
icons are invisible. As soon as you open the control panel settings once, the
control panel is initialized somehow. From this moment it operates as
intended, but only until the next login into the same session. I also checked
if it has to to do with the session settings (save session or empty session).
There is no interference with that setting.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Thomas Rother --- Problem is still visible. Plasma does not start the script even after re-login. Current environment now plasma 6.2.5, frameworks 6.10.0, QT 6.8.1 on openSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #6 from Thomas Rother --- Created attachment 177640 --> https://bugs.kde.org/attachment.cgi?id=177640&action=edit kcm_auostart -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Thomas Rother --- Note: kcm_autostart always shows the "ssh-add.sh not yet started automatically", even after a reboot or re-login. But I can successfully start the script manually from the shell thommie@odysseus4:~> .config/autostart/ssh-add.sh Identity added: /home/thommie/.ssh/[x] Identity added: /home/thommie/.ssh/[x] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #8 from Thomas Rother --- maybe just a side effect without relevance for this, just for info: With a wayland session, the script throws libegl warnings: thommie@locutus:~> .config/autostart/ssh-add.sh libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen Identity added: /home/thommie/.ssh/[] This does not happen with an X11 session. Information for package libnvidia-egl-wayland1: --- Repository : repo-oss Name : libnvidia-egl-wayland1 Version: 1.1.17-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 109.7 KiB Installed : Yes Status : up-to-date Source package : libnvidia-egl-wayland-1.1.17-1.1.src Upstream URL : https://github.com/NVIDIA/egl-wayland Summary: The EGLStream-based Wayland external platform -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498465] New: Additional control panel only appears partly after login
https://bugs.kde.org/show_bug.cgi?id=498465 Bug ID: 498465 Summary: Additional control panel only appears partly after login Classification: Plasma Product: plasmashell Version: 6.2.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: t.rot...@netzwissen.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 177255 --> https://bugs.kde.org/attachment.cgi?id=177255&action=edit screenshot with broken panel display )only one widget visible) Added a second control panel on the lower border. This control panel is only displayed partly after the next login (screenshot 1). If you use the control panel settings (Alt D, ALt S), then the panel re-appears, but only until the next logout/login. Screenshot 1: broken panel Screnshot 2: full panel Deleted .cache for debugging, no change. Re-created panel at different positions: same effect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498465] Additional control panel only appears partly after login
https://bugs.kde.org/show_bug.cgi?id=498465 --- Comment #1 from Thomas Rother --- Created attachment 177257 --> https://bugs.kde.org/attachment.cgi?id=177257&action=edit full panel -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #2 from Thomas Rother --- Created attachment 177226 --> https://bugs.kde.org/attachment.cgi?id=177226&action=edit shell script to add multiple ssh keys for ksshaskpass -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #3 from Thomas Rother --- thommie@odysseus4:~> journalctl --user -b Jan 09 09:12:06 odysseus4 systemd-xdg-autostart-generator[2388]: Configuration file /home/thommie/.config/autostart/ssh-add> Jan 09 09:12:07 odysseus4 systemd[2379]: Configuration file /home/thommie/.config/systemd/user/ssh-agent.service is marked > [...] Jan 09 09:12:07 odysseus4 systemd[2379]: Started SSH agent (ssh-agent). The ssh-agent.service file [Unit] Description=SSH agent (ssh-agent) [Service] Type=simple Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket Environment=DISPLAY=:0 ExecStart=ssh-agent -D -a $SSH_AUTH_SOCK ExecStop=kill -15 $MAINPID [Install] WantedBy=default.target Hmmm, Question: is it possible that the service comes up a bit too late for the script execution? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] New: Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Bug ID: 498397 Summary: Shell autostart not working even after restart/relogin Classification: Applications Product: systemsettings Version: 6.2.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: t.rot...@netzwissen.de CC: nicolas.fe...@gmx.de Target Milestone: --- Created attachment 177210 --> https://bugs.kde.org/attachment.cgi?id=177210&action=edit Autostart of shell scripts not working A shell script located in .config/autostart/ with proper permissions can be added in the UI but is never automatically started, even not after a restart. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #9 from Thomas Rother --- Just for reference, the issue is referenced on these platforms too: - https://discuss.kde.org/t/autostart-login-scripts-no-working/11981 (after migration KDE 5.x >> 6.x) - https://forum.manjaro.org/t/kde-plasma-6-2-4-autostart-not-working/173465 (for Manjaro with Plasma 6.2.4) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added Version|6.2.5 |6.3.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #10 from Thomas Rother --- ... still open in KDE Plasma 6.3.1, Framework 6.11 on Distributor ID: openSUSE Description:openSUSE Tumbleweed Release:20250226 All other autostart settings (Applications ownCloud client and Remmina) work fine, but the shell script is not started upon login. It must be started from shell manually -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494390] System settings freezes when trying to access energy management and language is set to German
https://bugs.kde.org/show_bug.cgi?id=494390 --- Comment #13 from Thomas Rother --- confirmed, no issues any more on openSUSE Tumbleweed, Release 20250315 with framework 6.11.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added Version|6.3.1 |6.3.3 --- Comment #11 from Thomas Rother --- Can please someone have a look at this? Its still open since a number or releases and there was no activity on the bug yet since I reported it at 2025-01-08 . See also referenced reports mentioned in https://bugs.kde.org/show_bug.cgi?id=498397#c9 I'd be happy to help with debugging this ... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added CC||t.rot...@netzwissen.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 501845] New: Crash with screencasts saved in webm/vp9
https://bugs.kde.org/show_bug.cgi?id=501845 Bug ID: 501845 Summary: Crash with screencasts saved in webm/vp9 Classification: Applications Product: Spectacle Version: 6.3.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: t.rot...@netzwissen.de CC: k...@david-redondo.de Target Milestone: --- Spectacle reproducibly crashes when using the webm/vp9 format. The workaround is to use mp4/h264 instead which shows no problems so far. OS:openSUSE Tumbleweed Release: 20250314 Installed lib: ibvpx9 - VP8/VP9 codec library Version: 1.15.0-1.2 crash dump available on request -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 Thomas Rother changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 from Thomas Rother --- worksforme now -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498397] Shell autostart not working even after restart/relogin
https://bugs.kde.org/show_bug.cgi?id=498397 --- Comment #13 from Thomas Rother --- I grabbed the solution from the net, see also other references in #9. The script works fine when started manually from the shell, but not automatically on KDE login. If the script itself or something else is wrong and can therefore not be executed, maybe we can fix it together ... ? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 501845] Crash with screencasts saved in webm/vp9
https://bugs.kde.org/show_bug.cgi?id=501845 --- Comment #2 from Thomas Rother --- ... ok, I just see that I have this effect only on one machine yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499773] systemsettings kcm_powerdevilprofilesconfig crashes on open with certain different fonts, font sizes, or languages/text lengths
https://bugs.kde.org/show_bug.cgi?id=499773 Thomas Rother changed: What|Removed |Added Version|6.2.5 |6.3.4 --- Comment #16 from Thomas Rother --- I am now using font Noto serif 13 without issues. Previously this was one of the fonts which triggered a crash. >From my point of view, this is solved by "upstream magic" ;-) version info: Operating System: openSUSE Tumbleweed 20250403 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.14.0-1-default (64-bit) Graphics Platform: Wayland Processors: 28 × 13th Gen Intel® Core™ i7-13850HX Memory: 62.5 GiB of RAM Graphics Processor 1: Mesa Intel® Graphics Graphics Processor 2: llvmpipe Manufacturer: Dell Inc. Product Name: Precision 7680 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366440] New: Digikam 5.0.0-147.4 with mysql database segfaults upon startup
https://bugs.kde.org/show_bug.cgi?id=366440 Bug ID: 366440 Summary: Digikam 5.0.0-147.4 with mysql database segfaults upon startup Product: digikam Version: 5.0.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: t.rot...@netzwissen.de Application: digikam (5.0.0) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Digikam 5 was installed from obs://build.opensuse.org/KDE and configured for MYSQL database A second installation with SQLITE does not show this error The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5c07692880 (LWP 6710))] Thread 5 (Thread 0x7f5be46a7700 (LWP 6712)): #0 0x7f5c02ab8bfd in poll () at /lib64/libc.so.6 #1 0x7f5bf54c0422 in () at /usr/lib64/libxcb.so.1 #2 0x7f5bf54c200f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f5be67da3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f5c033ca32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f5c059530a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f5c02ac102d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f5be2cef700 (LWP 6714)): #0 0x7f5c0595703f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5c033cb34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f5c06bd2800 in Digikam::ScanController::run() (this=0x7f5c074e9780 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /usr/src/debug/digikam-5.0.0/core/libs/database/utils/scancontroller.cpp:684 #3 0x7f5c033ca32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f5c059530a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5c02ac102d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f5be24ee700 (LWP 6723)): #0 0x7f5c0595703f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5c033cb34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f5c061f6091 in Digikam::ParkingThread::run() (this=0x1d81490) at /usr/src/debug/digikam-5.0.0/core/libs/threads/threadmanager.cpp:115 #3 0x7f5c033ca32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f5c059530a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5c02ac102d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f5bccb77700 (LWP 6726)): #0 0x7f5c0595703f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5bf94ac733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5bf94ac759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c059530a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c02ac102d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f5c07692880 (LWP 6710)): [KCrash Handler] #6 0x7f5bd0658414 in QGstreamerBusHelper::installMessageFilter(QObject*) () at /usr/lib64/libqgsttools_p.so.1 #7 0x7f5bd08af37b in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #8 0x7f5bd08adbda in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #9 0x7f5c020f6a51 in () at /usr/lib64/libQt5MultimediaWidgets.so.5 #10 0x7f5c020f6d28 in QVideoWidget::setMediaObject(QMediaObject*) () at /usr/lib64/libQt5MultimediaWidgets.so.5 #11 0x7f5c00c73c41 in QMediaPlayer::setVideoOutput(QVideoWidget*) () at /usr/lib64/libQt5Multimedia.so.5 #12 0x7f5c06ce1068 in Digikam::MediaPlayerView::MediaPlayerView(QWidget*) (this=0x2d747b0, parent=) at /usr/src/debug/digikam-5.0.0/core/app/views/mediaplayerview.cpp:168 #13 0x7f5c06cdfcfc in Digikam::StackedView::StackedView(QWidget*) (this=0x1cabb40, parent=) at /usr/src/debug/digikam-5.0.0/core/app/views/stackedview.cpp:146 #14 0x7f5c06cdaab0 in Digikam::DigikamView::DigikamView(QWidget*, Digikam::DigikamModelCollection*) (this=0x1cde8b0, parent=, modelCollection=0x1c9c750) at /usr/src/debug/digikam-5.0.0/core/app/views/digikamview.cpp:272 #15 0x7f5c06c25afa in Digikam::DigikamApp::setupView() (this=this@entry=0x1bc6360) at /usr/src/debug/digikam-5.0.0/core/app/main/digikamapp.cpp:556 #16 0x7f5c06c3fc96 in Digikam::DigikamApp::DigikamApp() (this=0x1bc6360, __in_chrg=, __vtt_parm=) at /usr/src/debug/digikam-5.0.0/core/app/main/digikamapp.cpp:246 #17 0x00408881 in main(int, char**) (argc=1, argv=) at /usr/src/debug/digikam-5.0.0/core/app/main/main.cpp:200 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366440] Digikam 5.0.0-147.4 with mysql database segfaults upon startup
https://bugs.kde.org/show_bug.cgi?id=366440 --- Comment #1 from Thomas Rother --- The original crash was caused by a missing vdpau_drv_video.so. With installed VDPAU Driver Bridge for NVidia driver we get the following lines: ... libva info: va_openDriver() returns 0 digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: Face database: have a structure version "2" digikam.facesengine: Face database ready for use digikam.facesengine: Face database ready for use libva info: VA-API version 0.38.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_38 libva info: va_openDriver() returns 0 libva info: VA-API version 0.38.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_38 libva info: va_openDriver() returns 0 KCrash: Application 'digikam' crashing... and: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f31f5428880 (LWP 6943))] Thread 5 (Thread 0x7f31d243d700 (LWP 6944)): #0 0x7f31f084ebfd in poll () at /lib64/libc.so.6 #1 0x7f31e3256422 in () at /usr/lib64/libxcb.so.1 #2 0x7f31e325800f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f31d45703c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f31f116032f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f31f36e90a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f31f085702d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f31d0a85700 (LWP 6945)): #0 0x7f31f36ed03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f31f116134b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f31f4968800 in Digikam::ScanController::run() (this=0x7f31f527f780 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /usr/src/debug/digikam-5.0.0/core/libs/database/utils/scancontroller.cpp:684 #3 0x7f31f116032f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f31f36e90a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f31f085702d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f31cbfff700 (LWP 6952)): #0 0x7f31f36ed03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f31f116134b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f31f3f8c091 in Digikam::ParkingThread::run() (this=0x23c7230) at /usr/src/debug/digikam-5.0.0/core/libs/threads/threadmanager.cpp:115 #3 0x7f31f116032f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f31f36e90a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f31f085702d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f31bb7e3700 (LWP 6957)): #0 0x7f31f36ed03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f31e7242733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f31e7242759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f31f36e90a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f31f085702d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f31f5428880 (LWP 6943)): [KCrash Handler] #6 0x7f31be3e6414 in QGstreamerBusHelper::installMessageFilter(QObject*) () at /usr/lib64/libqgsttools_p.so.1 #7 0x7f31be63d37b in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #8 0x7f31be63bbda in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #9 0x7f31efe8ca51 in () at /usr/lib64/libQt5MultimediaWidgets.so.5 #10 0x7f31efe8cd28 in QVideoWidget::setMediaObject(QMediaObject*) () at /usr/lib64/libQt5MultimediaWidgets.so.5 #11 0x7f31eea09c41 in QMediaPlayer::setVideoOutput(QVideoWidget*) () at /usr/lib64/libQt5Multimedia.so.5 #12 0x7f31f4a77068 in Digikam::MediaPlayerView::MediaPlayerView(QWidget*) (this=0x373b200, parent=) at /usr/src/debug/digikam-5.0.0/core/app/views/mediaplayerview.cpp:168 #13 0x7f31f4a75cfc in Digikam::StackedView::StackedView(QWidget*) (this=0x24576d0, parent=) at /usr/src/debug/digikam-5.0.0/core/app/views/stackedview.cpp:146 #14 0x7f31f4a70ab0 in Digikam::DigikamView::DigikamView(QWidget*, Digikam::DigikamModelCollection*) (this=0x2498990, parent=, modelCollection=0x238bab0) at /usr/src/debug/digikam-5.0.0/core/app/views/digikamview.cpp:272 #15 0x7f31f49bbafa in Digikam::DigikamApp::setupView() (this=this@entry=0x23090c0) at /usr/src/debug/digikam-5.0.0/core/app/main/digikamapp.cpp:556 #16 0x7f31f49d5c96 in Digikam::DigikamApp::DigikamApp() (this=0x23090c0, __in_chrg=, __vtt_parm=) at /usr/src/debug/digikam-5.0.0/core/app/main/digikamapp.cpp:246 #17 0x00408881 in main(int, char**) (argc=1, argv=) at /usr/src/debug/digikam-5.0.0/core/app/main/main.cpp:200 -- You are receiving
[digikam] [Bug 366621] New: Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 Bug ID: 366621 Summary: Crash when performing Transformation resize operation Product: digikam Version: 5.1.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: ImageEditor Assignee: digikam-de...@kde.org Reporter: t.rot...@netzwissen.de Digikam 5.1 crashes reproducibly upon changing the size of an image. Unfortunately there is no stack trace, only the last message when starting through konsole: Scaling with darkness 0, saturation 15783, and multipliers 2,312500 1,00 1,628906 1,00 digikam.rawengine: LibRaw progress: Scaling colors pass 1 of 2 digikam.rawengine: LibRaw progress: Pre-interpolating pass 0 of 2 digikam.rawengine: LibRaw progress: Pre-interpolating pass 1 of 2 Bilinear interpolation... digikam.rawengine: LibRaw progress: Interpolating pass 0 of 3 digikam.rawengine: LibRaw progress: Interpolating pass 1 of 3 digikam.rawengine: LibRaw progress: Interpolating pass 2 of 3 digikam.rawengine: LibRaw progress: Converting to RGB pass 0 of 2 Converting to sRGB colorspace... digikam.rawengine: LibRaw progress: Converting to RGB pass 1 of 2 digikam.rawengine: LibRaw: data info: width= 6016 height= 4016 rgbmax= 255 digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.general: Final "Bildgröße ändern" started... digikam.dimg: Cannot allocate buffer of size 3764662740 KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Unable to start Dr. Konqi memory status: locutus:/home/thommie # free -m total used free sharedbuffers cached Mem: 32116 26883 5233 8289 0 23867 -/+ buffers/cache: 3015 29101 Swap:32763 0 32763 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 --- Comment #2 from Thomas Rother --- It is an OpenSUSE Leap 42.1 x64 with Kernel 4.1.27-27-default #1 SMP PREEMPT Fri Jul 15 12:46:41 UTC 2016 (84ae57e) x86_64 x86_64 x86_64 and 32 GB RAM Any idea how to debug without drkonqi? *-debuginfo packages are installed. Bye, Thommie -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 --- Comment #3 from Thomas Rother --- Maybe there is not enough RAM? But when I do the same resize operation on the same image with GIMP, there are no problems -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 --- Comment #5 from Thomas Rother --- Hmmm, after some testing, I can not see this crash anymore and I don't know why ... Now I get the following lines: digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.dimg: "/mnt/nas/public/Fotos/Nikon D7200/DSC_0098.JPG" : JPEG file identified digikam.metaengine: Loading image history "" digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2016-05-08 14:39:21.000 CEST Qt::TimeSpec(LocalTime)) digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.general: Final "Bildgröße ändern" started... digikam.general: Final "Bildgröße ändern" completed... digikam.general: Free space available in Editor cache [ "/home/thommie/.cache/digikam/" ] in Mbytes: 946328 digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.widgets: Profile white point : x= 0.312713 y= 0.32912 Y= 1 digikam.widgets: dkCmsReadICCMatrixRGB2XYZ(2): [ 0.435852 , 0.38533 , 0.143021 ] [ 0.222382 , 0.717041 , 0.0605927 ] [ 0.013916 , 0.0971375 , 0.713837 ] digikam.widgets: d->Primaries.Red : X= 0.461196 Y= 0.232948 Z= 0.00978772 digikam.widgets: d->Primaries.Green : X= 0.415454 Y= 0.719903 Z= 0.0802877 digikam.widgets: d->Primaries.Blue : X= 0.115485 Y= 0.0520762 Z= 0.536577 digikam.general: Clearing LT true Maybe just a temporary "hickup". On /home/thommie in general I have 925G free space, that should be sufficient for this cache ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 --- Comment #6 from Thomas Rother --- ... half an hour later, same situation: ... digikam.dimg: "/mnt/nas/public/Fotos/Nikon D7200/DSC_0234.JPG" : JPEG file identified digikam.metaengine: Loading image history "" digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2016-08-09 15:46:10.000 CEST Qt::TimeSpec(LocalTime)) digikam.dimg: No X.org XICC profile installed for screen 1 digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.metaengine: Cannot set Iptc tag string into image using Exiv2 (Error # 8 : Value not set digikam.general: Final "Bildgröße ändern" started... digikam.dimg: Cannot allocate buffer of size 2367947736 Unable to start Dr. Konqi I uploaded the file to my Owncloud, you can download it there, Password "digikam51" https://www.netzwissen.de/owncloud/index.php/s/FhxJlfkucJ3XKAK (picture is from the refugee camp where I do some volunteer work) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 --- Comment #8 from Thomas Rother --- Original size is 6000 x 4000 (comes from the camera in jpeg "basic" quality) with 300 dpi resolution. I tried to resize it to 900 width and 480 width (for web publishing) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366621] Crash when performing Transformation resize operation
https://bugs.kde.org/show_bug.cgi?id=366621 Thomas Rother changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Thomas Rother --- I received digikam 5.1.0-149.1 from OpenSUSE/KDE_Extra repo today, tested with various 6000 x 4000 px images, resized to 800 px, no crashes any more. Well done ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368317] New: SDDM login fails with LUKS crypted home partition image
https://bugs.kde.org/show_bug.cgi?id=368317 Bug ID: 368317 Summary: SDDM login fails with LUKS crypted home partition image Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t.rot...@netzwissen.de CC: bhus...@gmail.com, plasma-b...@kde.org My home partition is crypted with LUKS (home partiton as crypted image) according to https://www.suse.com/documentation/sled11/book_security/data/sec_cryptofs_y2_homes.html and https://en.opensuse.org/SDB:Encrypted_filesystems The authentication is done with pam and the image decrypted upon login. After upgrade from OpenSUSE 13.2 to leap 42.1, login with kdm as displaymanager was still successful. I changed /etc/sysconfig/displaymanager from kdm to sddm, then the login failed. The entered PW string (***) is "visible", but after hitting "enter" the mouse icon changes to an "X" and no further pw entries are possible, although the X windows does not crash (at least i can not see a crash). I want to get rid of the old kdm and would welcome some ideas how to debug this ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361544] New: Plasma shell crash when opening WLAN connection
https://bugs.kde.org/show_bug.cgi?id=361544 Bug ID: 361544 Summary: Plasma shell crash when opening WLAN connection Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t.rot...@netzwissen.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Changed from an active WLAN connection to a new one in network plasmoid The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa38d312800 (LWP 15016))] Thread 37 (Thread 0x7fa37627c700 (LWP 15018)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa38b76a422 in () at /usr/lib64/libxcb.so.1 #2 0x7fa38b76c00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fa3789ff3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fa36f1ca700 (LWP 15021)): #0 0x7fa386816c8d in read () at /lib64/libc.so.6 #1 0x7fa37e9bf073 in () at /usr/lib64/tls/libnvidia-tls.so.361.42 #2 0x7fa382f39b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa382ef8999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa382ef8df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fa36270b700 (LWP 15044)): #0 0x7fa382f3acf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa382ef8e4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa360e18700 (LWP 15057)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa382ef8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fa35b3ef700 (LWP 15085)): #0 0x7fa38602803f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa38c9ef86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fa38c9ef899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fa358846700 (LWP 15111)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa382ef8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38adbc282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5C
