[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 zb4ng changed: What|Removed |Added CC||zb...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 --- Comment #7 from zb4ng --- (In reply to Amol Godbole from comment #6) > The confirmation message will not be displayed if the dolphin setting for > 'remember opened tabs' has been selected. > This is available in Settings->Configure Dolphin->Startup->Show on > startup->Folders, tabs, and window state from last time. > > Could you please confirm if you have not configured dolphin to remember tabs? Yes, it is as you said: If "Folders, tabs, and window state from last time. " is selected, then the confirmation message is not displayed. If the radio button is in the other state (next to the field with the folder), the confirmation box "You have multiple tabs open in this window, are you sure you want to quit?" appears. I tried the second option (= go to some default folder on startup) and when I rebooted, all the folders from last time were there. So this seems to work for me now, but I find it a bit confusing: - Why are those two settings linked ? - Does the second option do anything ? - If I press "Quit Dolphin" in the confirmation box, only the tabs of the current window will be closed (which is what I want!). However, the button text "Quit Dolphin") suggests that all Dolphin windows will be closed, hence I was at first hesitant to try it. If this behavior is deliberate, this issue can be closed from my pov. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 zb4ng changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from zb4ng --- (In reply to Ben Bonacci from comment #1) > On Dolphin version 23.04.3 the confirmation prompt appears as expected. > Have you tried updating to this version (if its available for your LTS > distributions) and see if the problem continues? > > If not, you could consider using the Flatpak version until its available in > the repositories. I tested it now with Flatpak (Dolphin version 23.04.3): didn't change any settings, just tried to reproduce the bug..., it is still there! It appears on my Chromebook also (with Linux Development Environment, but older Dolphin version) . This is really weird... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 --- Comment #3 from zb4ng --- (In reply to zb4ng from comment #2) > (In reply to Ben Bonacci from comment #1) > > On Dolphin version 23.04.3 the confirmation prompt appears as expected. > > I have found an old Suse Tumbleweed partition, so maybe, I'll check it there > later, if I get it running... I checked it in Tumbleweed and the bug occurs there also even with Dolphin 23.04.3... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 --- Comment #2 from zb4ng --- (In reply to Ben Bonacci from comment #1) > On Dolphin version 23.04.3 the confirmation prompt appears as expected. > Have you tried updating to this version (if its available for your LTS > distributions) and see if the problem continues? > > If not, you could consider using the Flatpak version until its available in > the repositories. I have an issue with Flatpak atm, so I couldn't test this... It's fine, if it works in the newer version of Dolphin. I hope Suse upgrades to the next minor version soon. I have found an old Suse Tumbleweed partition, so maybe, I'll check it there later, if I get it running... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 zb4ng changed: What|Removed |Added CC||zb...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472458] New: Confirmation for "Closing Windows with multiple Tabs" doesn't work
https://bugs.kde.org/show_bug.cgi?id=472458 Bug ID: 472458 Summary: Confirmation for "Closing Windows with multiple Tabs" doesn't work Classification: Applications Product: dolphin Version: 22.12.3 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: zb...@arcor.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I click accidentally on a "close" symbol of a dolphin window with multiple folders, it is closed without confirmation, even if I have configured the confirmation. This happens in openSUSE LEAP as well as Ubuntu LTS. Can you please fix this, that I don't have to search for all those folders? STEPS TO REPRODUCE 1. Go to Settings->Configure Dolphin->Confirmations 2. Check the box next to Confirmation for "Closing Windows with multiple Tabs" 3. Open multiple tabs in one dolphin window 4. Click on "x"-symbol in the title bar (presumably the rightmost symbol) OBSERVED RESULT The window is closed at once. EXPECTED RESULT A confirmation message box appears: "Really close this window with multiple tabs? Yes/Cancel" SOFTWARE/OS VERSIONS Linux/KDE Plasma: - openSUSE LEAP: 15.5 - Ubuntu LTS 22.04 KDE Plasma Version: 5.27.4 + 5.24.7 KDE Frameworks Version: 5.103.0+5.92.0 Qt Version: 5.15.8+5.15.3 Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 455533] Kdevelop crashes upon exit
https://bugs.kde.org/show_bug.cgi?id=455533 --- Comment #18 from zb4ng --- (In reply to Igor Kushnir from comment #17) > This bug report is about a crash on exit, not freeze. Could you be > experiencing Bug 379669? You are right. I am sorry, I have missed this while reading... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 455533] Kdevelop crashes upon exit
https://bugs.kde.org/show_bug.cgi?id=455533 zb4ng changed: What|Removed |Added CC||zb...@arcor.de --- Comment #16 from zb4ng --- just wanted to add that i experience this too: dist: openSUSE LEAP 15.4 kdevelop Version 5.7.211203 (21.12.3) KDE Plasma: 5.24.4 kernel: Linux unknown309c23cd67ab 5.14.21-150400.22-default #1 SMP PREEMPT_DYNAMIC Wed May 11 06:57:18 UTC 2022 (49db222) x86_64 x86_64 x86_64 GNU/Linux after exiting kdevelop: the CPU-load of kdevelop is maxed out and it has a bash child process KILL (kill -9) is necessary (TERM (kill -15) has no effect) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 318538] Krunner grabs all key presses when no application has focus. Please make that feature configurable (plasma 4 and plasma 5)
https://bugs.kde.org/show_bug.cgi?id=318538 --- Comment #6 from zb4ng --- This is imho a bit of a security issue: Some time ago, I entered my root password accidentally into there (instead of a "konsole"-window) and it looks like some krunner plugins talk to remote servers (e.g. "Locations" or "OpenStreetMap with Marble") Please add a checkbox "Start krunner when typing on plasma desktop ?" or sth like that to system settings. (I didn't find a way to switch off in a config file.) openSuSE LEAP 15.0 KDE plasma version: 5.12.6 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 318538] Krunner grabs all key presses when no application has focus. Please make that feature configurable (plasma 4 and plasma 5)
https://bugs.kde.org/show_bug.cgi?id=318538 zb4ng changed: What|Removed |Added CC||zb...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402846] baloo crashed after exiting OpenOffice Calc
https://bugs.kde.org/show_bug.cgi?id=402846 zb4ng changed: What|Removed |Added CC||zb...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402846] New: baloo crashed after exiting OpenOffice Calc
https://bugs.kde.org/show_bug.cgi?id=402846 Bug ID: 402846 Summary: baloo crashed after exiting OpenOffice Calc Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: zb...@arcor.de Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.28-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: I edited some file in OpenOffice Calc (6.1.3.2), then I saved and quit. The crash does not seem to be reproducible. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe9265e6100 (LWP 2428))] Thread 3 (Thread 0x7fe91b311700 (LWP 3252)): #0 0x7fe92400907b in poll () from /lib64/libc.so.6 #1 0x7fe9206f01c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe9206f02dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe924c83c0b in QEventDispatcherGlib::processEvents (this=0x7fa90c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe924c2c09a in QEventLoop::exec (this=this@entry=0x7fe91b310b80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x55b11ceb4dbd in Baloo::FileContentIndexer::run (this=0x55b11d3441d0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/filecontentindexer.cpp:73 #6 0x7fe924a5d372 in QThreadPoolThread::run (this=0x55b11d67d190) at thread/qthreadpool.cpp:99 #7 0x7fe924a600ce in QThreadPrivate::start (arg=0x55b11d67d190) at thread/qthread_unix.cpp:368 #8 0x7fe92306a559 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe92401381f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe91bd13700 (LWP 2431)): #0 0x7fe924004b68 in read () from /lib64/libc.so.6 #1 0x7fe920734a90 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe9206efcb7 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe9206f0170 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe9206f02dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe924c83c0b in QEventDispatcherGlib::processEvents (this=0x7fe914000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fe924c2c09a in QEventLoop::exec (this=this@entry=0x7fe91bd12ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fe924a5b4da in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7fe925ea0985 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7fe924a600ce in QThreadPrivate::start (arg=0x7fe926110d60) at thread/qthread_unix.cpp:368 #10 0x7fe92306a559 in start_thread () from /lib64/libpthread.so.0 #11 0x7fe92401381f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe9265e6100 (LWP 2428)): [KCrash Handler] #6 0x7fe923f510e0 in raise () from /lib64/libc.so.6 #7 0x7fe923f526c1 in abort () from /lib64/libc.so.6 #8 0x7fe921d15922 in mdb_assert_fail (env=0x55b11d341610, expr_txt=expr_txt@entry=0x7fe921d173af "rc == 0", func=func@entry=0x7fe921d17ce8 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7fe921d17390 "mdb.c") at mdb.c:1487 #9 0x7fe921d0ae05 in mdb_page_dirty (txn=0x55b11d342ac0, mp=) at mdb.c:2071 #10 0x7fe921d0bfea in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffdb3cb9228, mc=) at mdb.c:2252 #11 0x7fe921d0c259 in mdb_page_touch (mc=mc@entry=0x7ffdb3cb9760) at mdb.c:2370 #12 0x7fe921d0dd2f in mdb_cursor_touch (mc=mc@entry=0x7ffdb3cb9760) at mdb.c:6273 #13 0x7fe921d10eee in mdb_cursor_put (mc=0x7ffdb3cb9760, key=0x7ffdb3cb9b30, data=0x7ffdb3cb9b40, flags=) at mdb.c:6407 #14 0x7fe921d139ab in mdb_put (txn=0x55b11d342ac0, dbi=7, key=key@entry=0x7ffdb3cb9b30, data=data@entry=0x7ffdb3cb9b40, flags=flags@entry=0) at mdb.c:8765 #15 0x7fe9255e31ed in Baloo::IdTreeDB::put (this=this@entry=0x7ffdb3cb9cc0, docId=, subDocIds=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/idtreedb.cpp:71 #16 0x7fe9255f5e41 in Baloo::DocumentUrlDB::replace > (shouldDeleteFolder=..., url=..., docId=, this=0x7ffdb3cb9ca0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/documenturldb.h:105 #17 Baloo::DocumentUrlDB::del > (shouldDeleteFolder=..., docId=5654251430742022, this=0x7ffdb3cb9ca0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/documenturldb.h:56 #18 Baloo::WriteTransaction::removeDocument (this=, id=id@entry=5654251430742022) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:131 #19 0x7fe9255f0489 in Baloo::Transaction::removeDocument
[Skanlite] [Bug 341462] Crash while scanning with scanlite
https://bugs.kde.org/show_bug.cgi?id=341462 zb4ng changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from zb4ng --- (In reply to Andrew Crouthamel from comment #2) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! Looks like issue was fixed a long time ago. Had completely forgotten about it I am going to put status to "RESOLVED" in a couple of days. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 341462] Crash while scanning with scanlite
https://bugs.kde.org/show_bug.cgi?id=341462 zb4ng changed: What|Removed |Added CC||zb...@arcor.de --- Comment #4 from zb4ng --- (In reply to Andrew Crouthamel from comment #2) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 320410] remembering last view mode for each file
https://bugs.kde.org/show_bug.cgi?id=320410 zb4ng changed: What|Removed |Added CC||zb...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373718] New: Plasma (occasionally) crashes after closing firefox.
https://bugs.kde.org/show_bug.cgi?id=373718 Bug ID: 373718 Summary: Plasma (occasionally) crashes after closing firefox. Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zb...@arcor.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I quit firefox. After that, the screen went black, the menu bar on the bottom disappeared and restarted. This might be similar to "Bug 372463 - Plasma crash ". The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3a0a70900 (LWP 2274))] Thread 15 (Thread 0x7fd2ad437700 (LWP 4804)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fd2aea95700 (LWP 4801)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fd2adc38700 (LWP 4728)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fd296ffc700 (LWP 3983)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fd2bfbfe700 (LWP 3116)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fd2c8ddc700 (LWP 2952)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fd2c99dd700 (LWP 2729)): #0 0x7fd3999a10af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd39a88865b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd39e7804eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd39e780995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd39a8879e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd3c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd39a19bd3d in clone () at /lib64/libc.so.6
