[ark] [Bug 409722] Krusader crash when trying to view any archive using the ark part
https://bugs.kde.org/show_bug.cgi?id=409722 Marc Bohets changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #16 from Marc Bohets --- The problem is NOT fixed, Krusader still crashes when trying to view the mscz file using F3. Version 2.7.2 "Peace of Mind" KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.18-1- -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 409722] Krusader crash when trying to view any archive using the ark part
https://bugs.kde.org/show_bug.cgi?id=409722 --- Comment #18 from Marc Bohets --- Thanks for your comment, it is fixed in Version 2.8.0-dev "Bleeding Edge" In the list of comments, I saw someone claiming it was fixed in 2019, so I imagined that this fix would have been pushed longtime and be available in most distro's now, and as I use a rolling distro like Manjaro, that includes new package version rather quick, I was surprised that the problem still existed in the latest version from the repositories. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398148] KDE does not change ssdm when changing keyboard layout usability bug
https://bugs.kde.org/show_bug.cgi?id=398148 --- Comment #3 from Marc Bohets --- In the mean time, I don't use KDE Neon anymore, as I purchased a new laptop (Asus TUF A17 gaming), and KDE Neon, does not work on it because it does not support the recent hardware of this laptop. Manjaro (and probably also Arch) seems to be the only distro that runs well on my new laptop. I tried KDE Neon, Kubuntu, Ubuntu, Fedora and Suse (rolling) and all have issues with hardware support (mainly AMD/NVIDIA graphics and keyboard illumination). Also back in 2018, Manjaro did not have this bug, and it is not present in the current Manjaro version, so I am unable to test it, because my old laptop is broken. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409722] New: Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Bug ID: 409722 Summary: Krusader crash when trying to view a musescore file Product: krusader Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: mboh...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.1 "Peace of Mind") Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: What I was doing when the application crashed: - Open Krusader - Goto file location - Select the file via the touchpad (single click) - Click the F3 View button > CRASH When looking at the file clicking the F4 Edit button, there is no crash, the file opens normally. Using KDE neon The system just got an update, so is completely up to date. To make sure the crash was not caused by doing the manipulation during system upgrade, I rebooted the laptop and tried again --> same result marc@marc-samsung:~$ uname -a Linux marc-samsung 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd24bb110c0 (LWP 2158))] Thread 4 (Thread 0x7fd223ded700 (LWP 2163)): #0 QMutex::lock (this=this@entry=0x5629505ef880) at thread/qmutex.cpp:222 #1 0x7fd245ed8ccc in QMutexLocker::QMutexLocker (m=0x5629505ef880, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:206 #2 QThreadData::canWaitLocked (this=0x5629505ef850) at ../../include/QtCore/5.12.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:269 #3 postEventSourcePrepare (s=0x7fd214004ba0, timeout=0x7fd223decba4) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7fd23fdc9b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd23fdca4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd23fdca6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd245ed8dcb in QEventDispatcherGlib::processEvents (this=0x7fd214000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #8 0x7fd245e7a03a in QEventLoop::exec (this=this@entry=0x7fd223decd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #9 0x7fd245ca14ca in QThread::exec (this=) at thread/qthread.cpp:531 #10 0x7fd2478fa015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7fd245ca2c72 in QThreadPrivate::start (arg=0x7fd247b71d80) at thread/qthread_unix.cpp:361 #12 0x7fd243bea6db in start_thread (arg=0x7fd223ded700) at pthread_create.c:463 #13 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd2295b5700 (LWP 2162)): #0 0x7fd243bf09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56295042d8b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56295042d868, cond=0x56295042d890) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56295042d890, mutex=0x56295042d868) at pthread_cond_wait.c:655 #3 0x7fd22f6c90aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fd22f6c8dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fd243bea6db in start_thread (arg=0x7fd2295b5700) at pthread_create.c:463 #6 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd22a3e6700 (LWP 2161)): #0 0x7fd243bf09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5629504cc9e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5629504cc990, cond=0x5629504cc9b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5629504cc9b8, mutex=0x5629504cc990) at pthread_cond_wait.c:655 #3 0x7fd22f6c90aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fd22f6c8dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fd243bea6db in start_thread (arg=0x7fd22a3e6700) at pthread_create.c:463 #6 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd24bb110c0 (LWP 2158)): [KCrash Handler] #6 0x in ?? () #7 0x7fd245eafc82 in QObjectPrivate::connectImpl (sender=sender@entry=0x562950ba6700, signal_index=3, receiver=receiver@entry=0x562950b87f80, slot=slot@entry=0x7ffe255c0b80, slotObj=slotObj@entry=0x562950b51d60, type=, types=, senderMetaObject=) at kernel/qobject.cpp:4903 #8 0x7fd245eaff2a
[krusader] [Bug 409722] Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Marc Bohets changed: What|Removed |Added CC||mboh...@gmail.com --- Comment #1 from Marc Bohets --- Created attachment 121473 --> https://bugs.kde.org/attachment.cgi?id=121473&action=edit This is the file I tried to view The file contains information on how to display and play music via the musescore3 application. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398148] New: KDE does not change ssdm when changing keyboard layout usability bug
https://bugs.kde.org/show_bug.cgi?id=398148 Bug ID: 398148 Summary: KDE does not change ssdm when changing keyboard layout usability bug Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard_layout Assignee: unassigned-b...@kde.org Reporter: mboh...@gmail.com Target Milestone: --- Hi, When powering up, the login screen uses qwerty layout instead of French azerty like I configured in KDE system settings. Once logged in, the keyboard layout is ok, also when logging out and in using the login screen again. The reason why I have this problem is that when I installed KDE Neon, I forgot to set the Keyboard layout to FR during install. See https://www.kubuntuforums.net/showthread.php/74310-Incorrect-keyboard-layout-at-login?p=419598 Not really a showstopper for me, but it would be more user friendly if KDE would adress this problem, I think it should be an easy fix by adding a few lines in the system settings code, but unfortunately I am not a developper, and I would not know in what file this small extra code would need to be put. Apparently Manjaro KDE already took care of this, It would be nice if it would be solved on KDE level, so the same issue does not turn up in every other distro that uses KDE. This could turn away new users because they are not able to login after installation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398148] KDE does not change ssdm when changing keyboard layout usability bug
https://bugs.kde.org/show_bug.cgi?id=398148 Marc Bohets changed: What|Removed |Added URL||https://www.kubuntuforums.n ||et/showthread.php/74310-Inc ||orrect-keyboard-layout-at-l ||ogin?p=419598 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398148] KDE does not change ssdm when changing keyboard layout usability bug
https://bugs.kde.org/show_bug.cgi?id=398148 --- Comment #1 from Marc Bohets --- Just received a sw update, and the login is back to qwerty :-) So I changed /usr/share/sddm/scripts/Xsetup again, and made it read only. I hope this does not disturb apt-get or dpkg update processes in the future. -- You are receiving this mail because: You are watching all bug changes.
