[kscreenlocker] [Bug 478815] kscreenlocker_greet fails to display UI after upgrade to beta 2, blocks screen forcing intervention / reboot
https://bugs.kde.org/show_bug.cgi?id=478815 Eric Hameleers changed: What|Removed |Added CC||al...@slackware.com --- Comment #4 from Eric Hameleers --- Thanks, I ran into a similar issue preparing for a Slackware release of Plasma6 Beta2: logout from the desktop stalled (the logout greeter would not appear) and I would be forced to logon remotely and change the runlevel, or else forcibly reboot. The error messages in SDDM's xorg and wailand logs brought me to this bug report and indeed I did not include a qqc2-breeze-style package assuming it would be used by Plasma Mobile only. I am going to add that package now if it is a workaround to the bug. Thanks for fixing it in git. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 --- Comment #57 from Eric Hameleers --- Was fixed in Slackware 6 days ago even... https://git.slackware.nl/ktown/commit/?id=d443f4f78cd553a37326f005a90b5a8f8030bf3c as we are skipping the .1 release. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 --- Comment #39 from Eric Hameleers --- The fix works for me too (Slackware). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Eric Hameleers changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414003] Systemsettings crashes when I'm trying to open any icon but second time.
https://bugs.kde.org/show_bug.cgi?id=414003 --- Comment #3 from Eric Hameleers --- Hi Nate, I thought I was pretty specific in my report (the duplicate bug 414039) on how I can consistently trigger this bug. What is missing? Let me re-phrase to help you understand better. 1- Start system settings, either from the menu or via commandline 2- Click on the icon 'startup and shutdown' 3- Perform any action in the configuration window that appears (some random clicking, or changing some setting, it does not matter what you do here) 4- Return to the system settings main window by clicking the 'back' button in the top left 5- Click 'startup and shutdown' a second time 6- At this moment, the crash occurs. This crash occurs only and always when applying the above sequence of actions to 'startup and shutdown'. Other icons in the main screen of systemsettings do not make systemsettings crash when I access them a second time. Eric -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414039] New: System settings crash after attempt to open 'startup and shutdown' the second time
https://bugs.kde.org/show_bug.cgi?id=414039 Bug ID: 414039 Summary: System settings crash after attempt to open 'startup and shutdown' the second time Product: systemsettings Version: 5.17.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: al...@slackware.com Target Milestone: --- Application: systemsettings5 (5.17.2) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.0-rc6 x86_64 Distribution: Slackware 14.2 x86_64 (post 14.2 -current) -- Information about the crash: I can consistently crash system settings by clicking on 'startup and shutdown'; performing any action (either some random clicking, or changing some setting), then returning to the system settings main window, and then clicking 'startup and shutdown' a second time. At this moment, the crash occurs. This crash behaviour seems to occur only with the 'startup and shutdown'. I tried other icons in the main screen but those don't make system settings crash when I open them a second time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f88066447c0 (LWP 10157))] Thread 9 (Thread 0x7f87f1dba700 (LWP 10241)): #0 0x7f880b16686c in read () at /lib64/libc.so.6 #1 0x7f880769003f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f880764a81e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f880764ac2a in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f880764ad9f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f880b86739b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f880b81292b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f880b64cc81 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f880d5b18d5 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f880b64dcc3 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f880abc306b in start_thread () at /lib64/libpthread.so.0 #11 0x7f880b17672f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f87e35ef700 (LWP 10239)): #0 0x7f880b16686c in read () at /lib64/libc.so.6 #1 0x7f880769003f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f880764a81e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f880764ac2a in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f880764ad9f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f880b86739b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f880b81292b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f880b64cc81 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f880d5b18d5 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f880b64dcc3 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f880abc306b in start_thread () at /lib64/libpthread.so.0 #11 0x7f880b17672f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f87e1e29700 (LWP 10178)): #0 0x7f880b16ae9f in poll () at /lib64/libc.so.6 #1 0x7f87f008f47d in () at /usr/lib64/libpulse.so.0 #2 0x7f87f007b715 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f87f007bae8 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f87f007bb5c in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f87f008f56c in () at /usr/lib64/libpulse.so.0 #6 0x7f87e25bc1df in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f880abc306b in start_thread () at /lib64/libpthread.so.0 #8 0x7f880b17672f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f87f25bb700 (LWP 10171)): #0 0x7f880b16686c in read () at /lib64/libc.so.6 #1 0x7f880769003f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f880764a81e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f880764ac2a in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f880764afe3 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7f87f2f75306 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7f880767291d in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f880abc306b in start_thread () at /lib64/libpthread.so.0 #8 0x7f880b17672f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f87f2dbc700 (LWP 10170)): #0 0x7f880b16ae9f in poll () at /lib64/libc.so.6 #1 0x7f880764ac7e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f880764ad9f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f880764adf1 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f880767291d in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f880abc306b in start_thread
[partitionmanager] [Bug 407414] Partition Manager shows no disk information
https://bugs.kde.org/show_bug.cgi?id=407414 Eric Hameleers changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||al...@slackware.com --- Comment #2 from Eric Hameleers --- This is indeed a packaging bug, thanks for putting me on the right path there Andrius. Those dbus files were installed incorrectly to /etc/kde/dbus-1/system.d/ and after I moved them manually to the correct location and reloaded the messagebus, partitionmanager works as expected. I will fix the Slackware package. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355763] Plasmashell crashes on start
https://bugs.kde.org/show_bug.cgi?id=355763 Eric Hameleers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Eric Hameleers --- Please close this report as WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355763] Plasmashell crashes on start
https://bugs.kde.org/show_bug.cgi?id=355763 --- Comment #4 from Eric Hameleers --- This was a 3 years old drkonqi bug report. The crash is no longer occurring on present-day KDE Plasma Desktop. The bug report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395115] print-manager v18.04.1 interacts badly with recent cups v2.2.8, numerous errors leading to high system load
https://bugs.kde.org/show_bug.cgi?id=395115 --- Comment #14 from Eric Hameleers --- Slackware has applied the upstream patch to its cups-2.2.8 package and that solved the issue with print-manager in KDE Plasma5. I agree that there's no need to keep this KDE bug open since it is not an issue in print-manager. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395115] print-manager v18.04.1 interacts badly with recent cups v2.2.8, numerous errors leading to high system load
https://bugs.kde.org/show_bug.cgi?id=395115 Eric Hameleers changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’
https://bugs.kde.org/show_bug.cgi?id=393372 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #5 from Eric Hameleers <al...@slackware.com> --- The patch solves one occurrence of build failure but uncovers further errors. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’
https://bugs.kde.org/show_bug.cgi?id=393372 --- Comment #4 from Eric Hameleers <al...@slackware.com> --- Created attachment 11 --> https://bugs.kde.org/attachment.cgi?id=11=edit Build log of kopete 18.04.0 evidencing further compilation errors -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’
https://bugs.kde.org/show_bug.cgi?id=393372 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com --- Comment #2 from Eric Hameleers <al...@slackware.com> --- Exact same issue here on Slackware, using KDE Frameworks 5.45.0, Plasma 5.12.4 and Applications 18.04.0 on top of Qt 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 377029] Crash in connection editor when importing openvpn connection
https://bugs.kde.org/show_bug.cgi?id=377029 --- Comment #3 from Eric Hameleers <al...@slackware.com> --- (In reply to Jan Grulich from comment #2) > Ping? Can you please provide requested information? IN my original post I already mentioned "Even with gdb I do not get a useful backtrace". -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 377029] Crash in connection editor when importing openvpn connection
https://bugs.kde.org/show_bug.cgi?id=377029 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 377029] New: Crash in connection editor when importing openvpn connection
https://bugs.kde.org/show_bug.cgi?id=377029 Bug ID: 377029 Summary: Crash in connection editor when importing openvpn connection Product: plasma-nm Version: 5.9.2 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: al...@slackware.com Target Milestone: --- When using the Plasma 5 connection editor to import an existing openvpn connection, I get consistent crash after selecting the .ovpn file and clicking "OK". Even with gdb I do not get a useful backtrace but when using gdb I noticed that the crash occurs when the "copying certificate" window is drawn. I get the window borders but not the window content. In the same Plasma 5 desktop session I can however start the GTK-based nm-applet and successfully import that same .ovpn definition file. The resulting OpenVPN entry is also visible in the Plasma 5 widget and can successfully be used. System: Slackware-current 64bit (post-14.2) with Plasma 5.9.2, KF 5.31.0 and Qt 5.7.1. Using NetworkManager 1.6.0 and NetworkManager-openvpn 1.2.8. The OpenVPN .ovpn file I tried to import is any one from https://www.privateinternetaccess.com/openvpn/openvpn.zip -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 356529] I18N_PLURAL_ARGUMENT_MISSING in various places
https://bugs.kde.org/show_bug.cgi?id=356529 --- Comment #1 from Eric Hameleers <al...@slackware.com> --- Confirmed on Slackware-current also. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357057] Ark requires rar and unrar for opening/extracting RAR archives (same for e.g. zip)
https://bugs.kde.org/show_bug.cgi?id=357057 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com --- Comment #2 from Eric Hameleers <al...@slackware.com> --- Please note: Slackware does not ship rar *nor* unrar and will not likely ever change that. Is it possible to add a compile option so that "unrar" is not required and the RAR support of libarchive >= 3.02 (https://github.com/libarchive/libarchive/wiki/ReleaseNotes#libarchive-302) can be used instead? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 356529] I18N_PLURAL_ARGUMENT_MISSING in various places
https://bugs.kde.org/show_bug.cgi?id=356529 Eric Hameleers <al...@slackware.com> changed: What|Removed |Added CC||al...@slackware.com -- You are receiving this mail because: You are watching all bug changes.
