[plasmashell] [Bug 437808] Desktop freezes after sleep on fresh upgrade to Fedora 34/KDE
https://bugs.kde.org/show_bug.cgi?id=437808 --- Comment #16 from keitalbame --- I'm having almost similar issues with Plasma 5.22.5-1 on Fedora 34 (upgrading since 31) but in my case, no mouse cursor is seen. Turning monitor off and on again does not help here. I can replicate with two situations: 1. By setting the power management to turn monitor off after one minute. Wait for the monitor turns off, and press any key on the keyboard or mouse and move the mouse. The UI does not come back, CAPS LOCK is still responsive. 2. Logout from the session. Login manager (sddm) is not displayed, CAPS LOCK is still responsive. In both situations, only manual reset allows to restart the system. CTRL+ALT+any F function key does not work into to get any shell. Situation 1 does not happen on X11 but #2 does so not sure if it is specific to Wayland or sddm. System info: Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-100.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Monitor: LG 5K ultrawide connected using displayport connection. No scaling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437808] Desktop freezes after sleep on fresh upgrade to Fedora 34/KDE
https://bugs.kde.org/show_bug.cgi?id=437808 keitalbame changed: What|Removed |Added CC||sv...@nunocosta.dev -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 437364] krunner shortcuts stopped working (upgrade to plasma-5.21.90)
https://bugs.kde.org/show_bug.cgi?id=437364 --- Comment #35 from keitalbame --- I upgraded to Fedora 34 recently and following the same steps mentioned in Comment 1, made KRunner shortcuts work again. I remember being affected by Bug 413368 in Fedora 31. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 437364] krunner shortcuts stopped working (upgrade to plasma-5.21.90)
https://bugs.kde.org/show_bug.cgi?id=437364 keitalbame changed: What|Removed |Added CC||sv...@nunocosta.dev -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request
https://bugs.kde.org/show_bug.cgi?id=438839 keitalbame changed: What|Removed |Added CC||sv...@nunocosta.dev -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439321] Wayland connection error thrown
https://bugs.kde.org/show_bug.cgi?id=439321 keitalbame changed: What|Removed |Added CC||sv...@nunocosta.dev -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382522] Connecting/disconnecting external displays: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=382522 --- Comment #5 from keitalbame --- To add that I have the taskbar to only show applications that are on that specific screen(Only this setting is enabled >> “Show only tasks: From current screen”). Tested on Fedora 31 and 32 and issue was there. After upgrade to 33, I can’t reproduce the issue anymore. Seems to be solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382522] Connecting/disconnecting external displays: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=382522 keitalbame changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from keitalbame --- I can replicate the issue I reported on bug 390766 with different hardware. This time the segmentation error does not appear but taskbar on secondary screen does not show any apps. My setup now only 1 external monitor and a laptop connected with HDMI. External monitor is the main screen and have a “normal” taskbar. Laptop screen have a vertical icon only taskbar. If I disconnect the HDMI cable, the apps go back to laptop screen, taskbar becomes a normal (not icon only) taskbar but the apps but not appear in the taskbar. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418322] dolphin: sometimes(?) launches window on session restore when 'dolphin --daemon' runs in background
https://bugs.kde.org/show_bug.cgi?id=418322 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413564] Add save tabs feature to Dolphin
https://bugs.kde.org/show_bug.cgi?id=413564 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413480] KDE crash on login when using wayland
https://bugs.kde.org/show_bug.cgi?id=413480 --- Comment #4 from keitalbame --- Just adding that I have a laptop where I do not see this crash. The crash only happens on my desktop. Both have Fedora 31 fully updated as of today. On my desktop I'm using and Radeon 5700 with a 4k monitor. My laptop is using an integrated graphic from Intel i5-3320m CPU on a 1366x768 screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413480] KDE crash on login when using wayland
https://bugs.kde.org/show_bug.cgi?id=413480 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417062] Plasma crashes after recovering from power loss while suspended.
https://bugs.kde.org/show_bug.cgi?id=417062 keitalbame changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #2 from keitalbame --- Closing this issue and #417063 since they were both related. I reloaded the desktop with a new install so I cannot investigate further but if someone is having a similar issue, it could do some additional investigation. PS: There should be a "Cannot replicate/Not confirmed" status/substatus for this type of cases. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 417063] KRunner crashed when running from cli
https://bugs.kde.org/show_bug.cgi?id=417063 keitalbame changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #2 from keitalbame --- Hi Christoph, Can you expand on how to check dynamic library loader status/configuration? I reloaded the desktop with a new install so I cannot investigate further but if someone is having a similar issue, it could do some additional investigation. Not sure if you checked my related issue #417062 where all the problems started after recovering from powerloss while on sleep mode. I will close both issues as resolved since I can no longer continue troubleshoot. PS: There should be a "Cannot replicate/Not confirmed" status/substatus for this type of cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417062] Plasma crashes after recovering from power loss while suspended.
https://bugs.kde.org/show_bug.cgi?id=417062 --- Comment #1 from keitalbame --- I have a shell with the previous opened applications (I have keep session enabled). KRunner and task manager are not available. KRunner crashes while runnng from the cli. Check https://bugs.kde.org/show_bug.cgi?id=417063 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 417063] New: KRunner crashed when running from cli
https://bugs.kde.org/show_bug.cgi?id=417063 Bug ID: 417063 Summary: KRunner crashed when running from cli Product: krunner Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: keitalb...@posteo.net Target Milestone: --- Application: krunner (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.3.15-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: KRunner crashed when running from cli. I'm also having issues reported on bug https://bugs.kde.org/show_bug.cgi?id=417062 I was trying to make possible to open other KDE applications. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7657975800 (LWP 4166))] Thread 21 (Thread 0x7f75f2562700 (LWP 4187)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f765bc1c8e3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f765bc1c971 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #3 0x7f765d5ee4e9 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #4 0x7f765d5ee78d in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #5 0x7f765bc16dc6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #7 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f75f2d63700 (LWP 4186)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f76432b4cfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f760dffb700 (LWP 4185)): #0 0x7f765b887a6f in poll () from /lib64/libc.so.6 #1 0x7f765a5f579e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f765a5f58d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f765be1b8b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f765bdc524b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f765bc15c75 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f765d272399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f765bc16dc6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f760e7fc700 (LWP 4183)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f76432b4cfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f760effd700 (LWP 4182)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f76432b4cfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f760f7fe700 (LWP 4181)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f76432b4cfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f760700 (LWP 4180)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f76432b4cfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f765af5c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f765b892693 in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f7634a8c700 (LWP 4179)): #0 0x7f765af62d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76432b50eb i
[plasmashell] [Bug 417062] New: Plasma crashes after recovering from power loss while suspended.
https://bugs.kde.org/show_bug.cgi?id=417062 Bug ID: 417062 Summary: Plasma crashes after recovering from power loss while suspended. Product: plasmashell Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keitalb...@posteo.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.3.15-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Starting KDE after a powerloss while in suspend mode. I've had been suspending session for some time. Not really sure for how long. Some applications were installed but no issues were seen and apps were working ok. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5541ed3800 (LWP 3689))] Thread 23 (Thread 0x7f54c3bb9700 (LWP 3720)): #0 0x7f554584b44c in read () from /lib64/libc.so.6 #1 0x7f55444274cf in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f55443df2e7 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f55443df742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f55443df8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5545de38b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5545d8d24b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5545bddc75 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f54d027bc4c in KCupsConnection::run() () from /lib64/libkcupslib.so #9 0x7f5545bdedc6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #11 0x7f554585a693 in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f54d0f06700 (LWP 3711)): #0 0x7f554584fa6f in poll () from /lib64/libc.so.6 #1 0x7f55443df79e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f55443df8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5545de38b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5545d8d24b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5545bddc75 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5545bdedc6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f554585a693 in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f54e88e0700 (LWP 3710)): #0 0x7f55450a2d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5545be48e3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f5545be4971 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #3 0x7f55478404e9 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #4 0x7f554784078d in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #5 0x7f5545bdedc6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #7 0x7f554585a693 in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f54ea7fc700 (LWP 3709)): #0 0x7f55450a2d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f552ca4b0eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f552ca4acfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f554585a693 in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f54eaffd700 (LWP 3707)): #0 0x7f55450a2d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f552ca4b0eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f552ca4acfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f554585a693 in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f54eb7fe700 (LWP 3706)): #0 0x7f55450a2d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f552ca4b0eb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f552ca4acfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f554509c4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f554585a693 in clone () from /lib64/libc.so
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #3 from keitalbame --- You are right. When I read "directory tree is not created", remembered about the bug I mentioned because when I first saw the issue, the folders where not being created in the filesystem. I found out later that they where created on a different (incorrect) path. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #1 from keitalbame --- Related with bug 408354. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 --- Comment #8 from keitalbame --- I no longer see the folder file: being created on my home folder but the issue of not being able to use a custom path to the maildir is still present. Createig any maildir type account always defaults to being created on ~/.local/share/akonadi_maildir_resource_xx. On Fedora 30, KDE Spin: kmail 19.04.2-2.fc30 akonadi 1.13.0-113.fc30 plasma-desktop 5.15.5-1.fc30 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360194] Archiving takes current date, not date of messages
https://bugs.kde.org/show_bug.cgi?id=360194 keitalbame changed: What|Removed |Added Version|5.1 |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360194] Archiving takes current date, not date of messages
https://bugs.kde.org/show_bug.cgi?id=360194 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #2 from keitalbame --- This is still an issue on kmail 5.8.3 on Fedora 28. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397573] New: Panel crashed when applied System Tray settings.
https://bugs.kde.org/show_bug.cgi?id=397573 Bug ID: 397573 Summary: Panel crashed when applied System Tray settings. Product: plasmashell Version: 5.13.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keitalb...@posteo.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.3) Qt Version: 5.10.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.11-200.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Removing clipboard from system tray and modifying the visibility of multiple entries. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3c2f54c400 (LWP 21916))] Thread 7 (Thread 0x7f3b705c8700 (LWP 21928)): #0 0x7f3c33c134b8 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f3c33bcc11c in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f3c33bccb1b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f3c33bccd10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f3c3c665c2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f3c3c61412b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f3c3c4629c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f3b72f7cb5b in KCupsConnection::run() () from /lib64/libkcupslib.so #8 0x7f3c3c46711d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f3c3aae8594 in start_thread () from /lib64/libpthread.so.0 #10 0x7f3c3b7a40df in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f3b85092700 (LWP 21926)): #0 0x7f3c3b7950c4 in read () from /lib64/libc.so.6 #1 0x7f3c33c12070 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f3c33bcc6db in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f3c33bccb90 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f3c33bccd10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f3c3c665c2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f3c3c61412b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f3c3c4629c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f3c4046994a in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #9 0x7f3c3c46711d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f3c3aae8594 in start_thread () from /lib64/libpthread.so.0 #11 0x7f3c3b7a40df in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f3c12db5700 (LWP 21925)): #0 0x7f3c3aaee52c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3c427e99f8 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f3c427e9a63 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f3c3aae8594 in start_thread () from /lib64/libpthread.so.0 #4 0x7f3c3b7a40df in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f3c19a90700 (LWP 21923)): #0 0x7f3c3b799659 in poll () from /lib64/libc.so.6 #1 0x7f3c33bccbe6 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f3c33bccd10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f3c3c665c2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f3c3c61412b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f3c3c4629c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f3c401f93a9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f3c3c46711d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f3c3aae8594 in start_thread () from /lib64/libpthread.so.0 #9 0x7f3c3b7a40df in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f3c1b4d6700 (LWP 21922)): #0 0x7f3c33bc9ab7 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f3c33bcc063 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f3c33bccb1b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f3c33bccd10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f3c3c665c2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f3c3c61412b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f3c3c4629c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f3c3e10d299 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 --- Comment #5 from keitalbame --- Created attachment 114406 --> https://bugs.kde.org/attachment.cgi?id=114406&action=edit Plasmashelrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 --- Comment #4 from keitalbame --- Created attachment 114405 --> https://bugs.kde.org/attachment.cgi?id=114405&action=edit kscreen config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #3 from keitalbame --- I believe issues bug 387901 and bug 391033 are reporting similar simptoms that could be cause by the same issue. I'm seeing this multimonitor bugs since at least August, 2017(I know, I should have filed a bug earlier but life... :) ), on a Arch install on my Dell E6400. I was hopping that Plasma 5.13 would resolve this but it only seems to attenuate a little bit. At the moment, my main laptop (Dell E6230 with dock) is on Fedora 28 with Plasma 5.13 and I'm still seeing similar issues. The "missing" applications seems to be more localized when I close the lid of the laptop while the external monitor is connected. If I undock the laptop(with lid open to keep the laptop to suspend), all applications are visible in task manager. Docking again, all aplications on external monitor, are now visible in task manager. If I want to have the lid closed while docked and applications showing correctly, I use the workaround "kquitapp5 plasmashell && plasmashell". This make the applications to reappear in the task manager. It sometime happens when I've turn off monitor while lid is closed(laptop suspends) and I resume from suspend undocked, but I cannot reproduce everytime. I noticed that a file with suffix _lidOpened is created in ~/.local/share/kscreen, when I close the lid(while docked and external monitor connected), and the file is removed when lid is reopened, while in the dock. The _lidOpened file is not deleted when I've turn off monitor while lid is closed(laptop suspends) and I resume from suspend undocked. Not sure if related, but I see 5 different panel ids configured in cat ~/.config/plasmashellrc, when I only use 2 panels. When I remove the panels, they are not removed from the config file. If I move a panel to another position on the same or other monitor, the previous configuration is not removed. Sometimes, the configuration is not correct, for example, showing a horizontal panel as vertical and incorrect resolution. Also, if you manually remove a panel from the config, it will not reappear on the config after laptop restart or plasmashell restart. I deleted ~/.config/plasmashellrc, restarted plasmashell, created new panels and moved the panels to its final position to have a cleaner config file but task manager still have the same behaviour. My normal setup is: Laptop screen only: Default Panel with only filter "show only windows from current screen" enabled. Laptop and External monitor: * Laptop on the left side: Left Vertical Empty Panel with Icons Only and with only filter "show only windows from current screen" enabled. * External screen on the Right side: Bottom Horizontal Default Panel with only filter "show only windows from current screen" enabled. External monitor is connected to the dock using direct (no adaptador of any sort) DisplayPort-DisplayPort cable. I will try to change my setup to use a DVI-DVI and see if there is any changes. Attached kscreen and plasmashellrc config files. I know this comment is long and apologies if its not very clear. If someone has more information on how to troubleshoot this further let me know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375372] Ability to choose activity to pin apps while they are not running
https://bugs.kde.org/show_bug.cgi?id=375372 --- Comment #7 from keitalbame --- Forgot to add that I'm on Fedora 28, Plasma 5.13.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375372] Ability to choose activity to pin apps while they are not running
https://bugs.kde.org/show_bug.cgi?id=375372 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #6 from keitalbame --- I'm also seeing that there is no option to pin to task manager, when you search for kmail in the Application Launcher although you can pin Kmail Header Theme Editor application. Maybe this Pin option is some missing configuration in the application itself, that needs to expose this feature? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360250] Missing option to "Move to current desktop" for clicking on task icon with middle mouse button
https://bugs.kde.org/show_bug.cgi?id=360250 --- Comment #3 from keitalbame --- (In reply to Nate Graham from comment #2) > Yes, but it doesn't have the requested "Bring to current desktop" option. Yes, you are right, my bad. Got tricked with the reproducible steps and thought what was missing was the on middle-click option. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391572] Add an option to "always show icon only" for tasks, but continue to show others icon + text.
https://bugs.kde.org/show_bug.cgi?id=391572 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396566] Add "Move to screen" to task manager
https://bugs.kde.org/show_bug.cgi?id=396566 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #1 from keitalbame --- Also think this would be a nice to have. Workaround with setting on Global Shortcuts - KWin, key shortcuts to the desired Move to Screen x option. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360250] Missing option to "Move to current desktop" for clicking on task icon with middle mouse button
https://bugs.kde.org/show_bug.cgi?id=360250 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #1 from keitalbame --- Task manager settings -> general -> On middle-click is available on Fedora 28 with Plasma 5.13. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] Baloo File Extraction Error
https://bugs.kde.org/show_bug.cgi?id=387672 --- Comment #26 from keitalbame --- I upgraded to Fedora 28 and still had the same issue. While reading comment 23, I noticed that I had baloo running but had a strange behavior when checking it status. balooctl status wasn't finishing and needed to CTRL-C. $ balooctl status Baloo File Indexer is running ^C Stopping baloo with balooctl stop and checking the status, was still showing as running. I rerun the balooctl stop, shutdown and started the computer. Then started baloo with balooctl start and I had a normal output, showing that the index as started and displaying the remaining files to index. After several shutdown/reboots, I'm no longer seeing the error on initial login. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] Baloo File Extraction Error
https://bugs.kde.org/show_bug.cgi?id=387672 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] Baloo File Extraction Error
https://bugs.kde.org/show_bug.cgi?id=387672 --- Comment #18 from keitalbame --- Created attachment 113167 --> https://bugs.kde.org/attachment.cgi?id=113167&action=edit New crash information added by DrKonqi baloo_file_extractor (5.46.0) using Qt 5.9.4 - What I was doing when the application crashed: Start Fedora 27 from a cold boot. I restart the application, baloo process starts using 30% of cpu and not stopping until a new reboot. -- Backtrace (Reduced): #8 0x7f8f0b8c3bf2 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x7f8f0b8b8b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x7f8f0b8b9dab in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x7f8f0b8ba039 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x7f8f0b8bbc64 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390766] New: Plasma crashed and restarted while disconnecting external monitors
https://bugs.kde.org/show_bug.cgi?id=390766 Bug ID: 390766 Summary: Plasma crashed and restarted while disconnecting external monitors Product: plasmashell Version: 5.11.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keitalb...@posteo.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.5) Qt Version: 5.9.4 Frameworks Version: 5.42.0 Operating System: Linux 4.15.3-300.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Disconnecting DP connected monitor. After recover, no icons from open applications are seen on task manager. Need to run kquitapp5 plasmashell && plasmashell command for the icons to reappear. - Custom settings of the application: Use of laptop (HP Zbook 14) dock station, 1 22" monitor connected with VGA and 1 connected to Display Port (directly on laptop, not dock). VGA monitor using hotizontal panel with default task manager. DP monitor using empty horizontal panel with icons only task manager (Main monitor). Laptop monitor with vertical panel and icons only task manager. On Fedora 27 (installed from the KDE iso version) at the moment, but I already had same issue on Arch. Started to see this behaviour around 20170825. 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 0x7f776db2e940 (LWP 2661))] Thread 9 (Thread 0x7f767f4e4700 (LWP 3219)): #0 0x7f77654553db in poll () from /lib64/libc.so.6 #1 0x7f775d6fee99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f775d6fefac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f77662c190b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f776626f62a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f77660c08ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f776a32de75 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f77660c4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f776479161b in start_thread () from /lib64/libpthread.so.0 #9 0x7f776546198f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f7696e05700 (LWP 3152)): #0 0x7f775d7443d9 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f775d6fdd8e in g_main_context_acquire () from /lib64/libglib-2.0.so.0 #2 0x7f775d6fed55 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f775d6fefac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f77662c190b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f776626f62a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f77660c08ca in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f76997755a7 in KCupsConnection::run() () from /lib64/libkcupslib.so #8 0x7f77660c4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f776479161b in start_thread () from /lib64/libpthread.so.0 #10 0x7f776546198f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f76ac054700 (LWP 3054)): #0 0x7f77654553db in poll () from /lib64/libc.so.6 #1 0x7f775d6fee99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f775d6fefac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f77662c190b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f776626f62a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f77660c08ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f776aecd116 in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #7 0x7f77660c4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f776479161b in start_thread () from /lib64/libpthread.so.0 #9 0x7f776546198f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f773b5a8700 (LWP 3028)): #0 0x7f7764797cbb in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f776d1f5604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f776d1f5649 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f776479161b in start_thread () from /lib64/libpthread.so.0 #4 0x7f776546198f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f774579e700 (LWP 2954)): #0 0x7f7765450888 in read () from /lib64/libc.so.6 #1 0x7f775d7430a0 in g_wakeup_acknowledge () from
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #36 from keitalbame --- Created attachment 107898 --> https://bugs.kde.org/attachment.cgi?id=107898&action=edit Pacman log from previous system update. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #35 from keitalbame --- Created attachment 107897 --> https://bugs.kde.org/attachment.cgi?id=107897&action=edit Crash report -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #34 from keitalbame --- (In reply to Antonio Rojas from comment #33) > (In reply to keitalbame from comment #32) > > Started to have this core dumps after last update, on Friday, 15th (usually > > I update once a week). > > > > I'm on Arch. > > Please confirm that it is indeed the same crash (same backtrace, and fixed > by installing flatpak). If it is, please post the pacman log of your last > update. I can confirm the issue seems the same. Attached the crash report. Did a full system update (due to the security updates available) and the issue persisted after reboot. Installed flatpak as mentioned and after that, Discover opened sucessfully, even without reboot. Also attached the previous system update log, where I detected the issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #32 from keitalbame --- Started to have this core dumps after last update, on Friday, 15th (usually I update once a week). I'm on Arch. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360811] markdown preview
https://bugs.kde.org/show_bug.cgi?id=360811 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360260] Add a scroll bar for some modules
https://bugs.kde.org/show_bug.cgi?id=360260 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378498] Power settings missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=378498 --- Comment #6 from keitalbame --- Seems similar to bug 360260 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378498] Power settings missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=378498 --- Comment #5 from keitalbame --- I confirm that also have issues while opening Display(#380079) and Energy settings from krunner or from the tray. HINT: The scrollbar is shown if you access from "System Settings >> Display and Monitor" or "System Settings >> Power Management" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378498] Power settings missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=378498 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376910] Scrolling does not follow system settings
https://bugs.kde.org/show_bug.cgi?id=376910 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 373432] [User manager] - New users are not created
https://bugs.kde.org/show_bug.cgi?id=373432 --- Comment #2 from keitalbame --- Command mentioned on the previous comment was from my Arch box. Using adduser on Neon will provide the same output. uid 1001 user is available on sddm for login, on both Arch and Neon. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 373432] [User manager] - New users are not created
https://bugs.kde.org/show_bug.cgi?id=373432 --- Comment #1 from keitalbame --- Manually creating 4 users with command: sudo useradd -m -G wheel,storage,power -s /bin/bash mytestuser - create 2nd user. - is shown on User Manager (UM) right after creation but on UM close and reopen, the user is no longer visible. It is present on /etc/passwd with uid 1001. - create 3rd user - is shown on UM and is present on /etc/passwd - create 4th user - is shown on UM and is present on /etc/passwd Adding for example, the user Real Name using UM, triggers the dialog for sudo/root password and the change is seen on /etc/passwd Removing user with UM works as expected(removing user from UM list and passwd file). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373432] New: [User manager] - New users are not created
https://bugs.kde.org/show_bug.cgi?id=373432 Bug ID: 373432 Summary: [User manager] - New users are not created Product: systemsettings Version: 5.8.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcmshell Assignee: kdelibs-b...@kde.org Reporter: keitalb...@posteo.net Target Milestone: --- The newly created user is not created on /etc/passwd nor is displayed on User Manager after finishing creation. In previous versions, the new users weres created. The only issue was that the user with uid 1001 never appeared on User Manager but all users were created on /etc/passwd. Same issue on a fully updated Arch box. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343427] kcm_sddm : Allow keyboard layout selection
https://bugs.kde.org/show_bug.cgi?id=343427 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #10 from keitalbame --- (In reply to Florian Jacob from comment #9) > This is still an issue. While the default theme of sddm now has a keyboard > layout chooser since November 2015, the breeze theme, which is developed as > part of plasma and not of sddm, still lacks one in plasma workspace 5.8.3. At the moment, using Neon user edition 5.8.4, the Layout selector only appears when start typing and a second layout different from en_US on system settings >> keyboard >> layouts. Seems that the layouts are not being added to SDDM. Using for example, I needed to use localectl set-x11-keymap --no-convert pt , to add the European portugues keyboard layout to SDDM. NOTE: The always showing US layout (although the correct one is set) is still ongoing. Manually selecting US and then, the second layout, workarounds the problem until logout/reboot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371230] Neon installer crash after language installation (nb-no)
https://bugs.kde.org/show_bug.cgi?id=371230 --- Comment #9 from keitalbame --- Created attachment 102690 --> https://bugs.kde.org/attachment.cgi?id=102690&action=edit Ubuntu-bug ubiquity Ubuntu-bug ubiquity command output -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371230] Neon installer crash after language installation (nb-no)
https://bugs.kde.org/show_bug.cgi?id=371230 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #8 from keitalbame --- Similiar issue using neon-useredition-20161124-1018-amd64.iso with settings: English version location: Poland keyboard: European Portuguese (pt_PT) and English version location: Poland keyboard: en_US The only way I was able to finish the instalation was with settings: English version location: US, New York keyboard: en_US Errors seen were the same as the screenshot "screenshot after crash" The result of the "ubuntu-bug ubiquity" command was: "Problem cannot be reported" "This is not an official KDE Package. Please remove any third party package and try again" Screenshot in attach. The same happens in both Virtualbox and bare metal. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368135] Kmail crashes every time when I try to preview certain emails
https://bugs.kde.org/show_bug.cgi?id=368135 --- Comment #1 from keitalbame --- Same behavior on Arch when previewing email. After some attempts of running kmail and crashes happens, kmail process becames zombie. Reboot is needed to be able to open kmail again. Hint: A few days ago, kio-pim was removed since it was replaced by klapd. https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/kldap&id=ae1e0280601b9ac512fd70e1b5771103076dce66 kmail 16.08.0-2 qt5-base 5.7.0-2 Possible duplicate >> https://bugs.kde.org/show_bug.cgi?id=368016 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368016] Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368135] Kmail crashes every time when I try to preview certain emails
https://bugs.kde.org/show_bug.cgi?id=368135 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
