[kwin] [Bug 491188] New: KWin crash Dolphin create zip archive of large directory
https://bugs.kde.org/show_bug.cgi?id=491188 Bug ID: 491188 Summary: KWin crash Dolphin create zip archive of large directory Classification: Plasma Product: kwin Version: 5.27.11 Platform: Slackware OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- Application: kwin_x11 (5.27.11) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.9.12 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Used Dolphin to create a zip archive of a 10gb directory to upload for a friend using Windows who can't use a xz-compressed tarball. Click OK, screen went blank then came back, Dolphin created the 5gb zip archive as advertised, up popped this Bug Report. This happened quite often, particulary when using Filezilla to navigate a remote KDE directory tree, until I set folding@home to run only when idle. Those crashes ceased. This is new. I tried to upgrade Plasma using kdesrc-build so K3b could create 50gb Bluray discs, but the build halted on error; troubleshooting that is on to-do list. One of these days I'll get around to looking for a memory leak with valgrind, soon as I can build KWin with debug symbols. Running Slackware-current, kernel 6.9.12, Ryzen 7 1700, X11, Q5.15.14, Frameworks 5.116.14 , Plasma 5.27.11. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x0047206a in ??? () #5 0x0047295a in ??? () #6 0x00473fc3 in ??? () #7 0x7fcc83f2bcfb in ??? () at /usr/lib64/libQt5DBus.so.5 #8 0x7fcc83f2fc96 in ??? () at /usr/lib64/libQt5DBus.so.5 #9 0x7fcc83f30250 in ??? () at /usr/lib64/libQt5DBus.so.5 #10 0x7fcc83f32608 in ??? () at /usr/lib64/libQt5DBus.so.5 #11 0x7fcc854ee5f6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x7fcc8417006e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7fcc854c3868 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fcc854c6951 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #15 0x7fcc8551ac13 in ??? () at /usr/lib64/libQt5Core.so.5 #16 0x7fcc80b143dd in ??? () at /usr/lib64/libglib-2.0.so.0 #17 0x7fcc80b17327 in ??? () at /usr/lib64/libglib-2.0.so.0 #18 0x7fcc80b1790c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7fcc8551a339 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7fcc854c2412 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7fcc854ca400 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x0043b3a0 in ??? () #23 0x7fcc83829d07 in __libc_start_call_main () at /lib64/libc.so.6 #24 0x7fcc83829dc5 in __libc_start_main_impl () at /lib64/libc.so.6 #25 0x0043c801 in ??? () [Inferior 1 (process 15275) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 491030] New: README.md replace "$ kdesrc-build" with "$ ./kdesrc-build"
https://bugs.kde.org/show_bug.cgi?id=491030 Bug ID: 491030 Summary: README.md replace "$ kdesrc-build" with "$ ./kdesrc-build" Classification: Developer tools Product: kdesrc-build Version: Git Platform: Slackware OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mp...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY "./kdesrc-build" would make copy from Kate/paste to Konsole just a bit quicker. Other than that teeny change, building KDE/Qt6 from git goes wonderfully well. Thank you for providing this quite useful tool! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 490371] New: Edit Current Profile - pop-up height ignores bottom panel
https://bugs.kde.org/show_bug.cgi?id=490371 Bug ID: 490371 Summary: Edit Current Profile - pop-up height ignores bottom panel Classification: Applications Product: konsole Version: 23.08.5 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY When editing a profile, the action buttons at the bottom of the pop-up appear behind the bottom panel. Maximize the pop-up to bring the top slivers above the panel to close the editor. STEPS TO REPRODUCE 1. Right-click the Konsole window, choose Edit Curremt Profile. 2. Finish editing, the Ok, Apply, Cancel buttons are behind the bottom panel. 3. Maximize the editor or set the panel to auto-hide to save settings. EXPECTED RESULT I expect the Profile Editor to resize to the visible dimensions. I keep the panel visible to easily switch between virtual desktops. SOFTWARE/OS VERSIONS Operating System: Slackware 15.0 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.116.0 Qt Version: 5.15.14 ADDITIONAL INFORMATION Kernel Version: 6.9.8 (64-bit) Graphics Platform: X11 Processors: 4 × AMD A6-5200 APU with Radeon™ HD Graphics Memory: 7.2 GiB of RAM Graphics Processor: KABINI -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 161115] KDE4 desktop has long delay on start, and all apps have long delay when first opened.
https://bugs.kde.org/show_bug.cgi?id=161115 Henry Thomas changed: What|Removed |Added URL||https://www.universitylivin ||g.com/united-states/city/ph ||iladelphia CC||henrythomas0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 490245] New: DVD with errors, crashed while closing copy dialog.
https://bugs.kde.org/show_bug.cgi?id=490245 Bug ID: 490245 Summary: DVD with errors, crashed while closing copy dialog. Classification: Applications Product: k3b Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Application: k3b (23.08.5) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.9.8 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Error reading sectors, 98% complete iso copy. Clicked Close, clicked fine I really really want to close this you dumb machine, *kaboom* The reporter is unsure if this crash is reproducible. -- Backtrace: Application: K3b (k3b), signal: Aborted [New LWP 5775] [New LWP 5777] [New LWP 5778] [New LWP 5779] [New LWP 5780] [New LWP 5781] [New LWP 5782] [New LWP 5786] [New LWP 5787] [New LWP 5788] [New LWP 5805] [New LWP 6160] [New LWP 10103] [New LWP 7571] [New LWP 9465] [New LWP 9466] [New LWP 9467] [New LWP 9468] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fb1c5491566 in __futex_abstimed_wait_cancelable64 () from /lib64/libc.so.6 Thread 19 (Thread 0x7fb18aa006c0 (LWP 9468) "Thread (pooled)"): #0 0x7fb1c5491566 in __futex_abstimed_wait_cancelable64 () at /lib64/libc.so.6 #1 0x7fb1c5494132 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7fb1c5adb645 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb1c5ad8e6a in ??? () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1c5ad5d0b in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1c5494d57 in start_thread () at /lib64/libc.so.6 #6 0x7fb1c55196a8 in clone3 () at /lib64/libc.so.6 Thread 18 (Thread 0x7fb1890006c0 (LWP 9467) "Thread (pooled)"): #1 0x7fb1c5494132 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7fb1c5adb645 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb1c5ad8e6a in ??? () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1c5ad5d0b in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1c5494d57 in start_thread () at /lib64/libc.so.6 #6 0x7fb1c55196a8 in clone3 () at /lib64/libc.so.6 Thread 17 (Thread 0x7fb17b4006c0 (LWP 9466) "Thread (pooled)"): #1 0x7fb1c5494132 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7fb1c5adb645 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb1c5ad8e6a in ??? () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1c5ad5d0b in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1c5494d57 in start_thread () at /lib64/libc.so.6 #6 0x7fb1c55196a8 in clone3 () at /lib64/libc.so.6 Thread 16 (Thread 0x7fb18be006c0 (LWP 9465) "Thread (pooled)"): #1 0x7fb1c5494132 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libc.so.6 #2 0x7fb1c5adb645 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb1c5ad8e6a in ??? () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1c5ad5d0b in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1c5494d57 in start_thread () at /lib64/libc.so.6 #6 0x7fb1c55196a8 in clone3 () at /lib64/libc.so.6 [KCrash Handler] #4 0x7fb1c5496aab in pthread_kill@@GLIBC_2.34 () at /lib64/libc.so.6 #5 0x7fb1c5442e12 in raise () at /lib64/libc.so.6 #6 0x7fb1c542849f in abort () at /lib64/libc.so.6 #7 0x7fb1c56a9a3d in ??? () at /usr/lib64/libstdc++.so.6 #8 0x7fb1c56baf8a in ??? () at /usr/lib64/libstdc++.so.6 #9 0x7fb1c56a95e9 in std::terminate() () at /usr/lib64/libstdc++.so.6 #10 0x7fb1c56a9508 in ??? () at /usr/lib64/libstdc++.so.6 #11 0x7fb1cff2f884 in ??? () at /usr/lib64/libgcc_s.so.1 #12 0x7fb1cff30285 in _Unwind_Resume () at /usr/lib64/libgcc_s.so.1 #13 0x7fb1c5a99586 in ??? () at /usr/lib64/libQt5Core.so.5 #14 0x7fb1c5acec9e in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) () at /usr/lib64/libQt5Core.so.5 #15 0x7fb1c5bdd700 in QDebug::~QDebug() () at /usr/lib64/libQt5Core.so.5 #16 0x7fb1d0f90f2b in ??? () at /usr/lib64/libk3bdevice.so.8 #17 0x7fb1d0f914aa in ??? () at /usr/lib64/libk3bdevice.so.8 #18 0x7fb1d0f8b3bc in K3b::Device::Device::read10(unsigned char*, unsigned int, unsigned long, unsigned int, bool) const () at /usr/lib64/libk3bdevice.so.8 #19 0x7fb1d12fda6d in ??? () at /usr/lib64/libk3blib.so.8 #20 0x7fb1d12fdc7c in ??? () at /usr/lib64/libk3blib.so.8 #21 0x7fb1d12ff238 in ??? () at /usr/lib64/libk3blib.so.8 #22 0x7fb1d12a0ee5 in K3b::Thread::run() () at
[okteta] [Bug 182577] Okteta unable to load large files
https://bugs.kde.org/show_bug.cgi?id=182577 --- Comment #12 from Henry Pfeil --- Ping. It has been over a dozen years and nobody has figured out how to load a screen-full at a time from a file opened in random-access mode? There is a KDE-compatible development package called Qt6 with functions such as QFileDevice which grabs, piece of data that fits into a buffer where you can use a model to display pages widget or dialog: uchar *QFileDevice::map(), along with 64-bit fun stuff like seek(), pos(), readData() and writeData(). Is it that unreasonable to assume someone with write permission on Okteta can get smart enough on these tools to implement terabyte-sized file I/O which did not exist in C++14 a decade ago? https://doc.qt.io/qt-6/qfiledevice.html -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434687] Git make test kfileitemmodeltest fail
https://bugs.kde.org/show_bug.cgi?id=434687 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #4 from Henry Pfeil --- After a couple of years, I am withdrawing such minor repairs because the implemetation is incomprehensive to code jockys. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442273] application window opens in the currently-active virtual desktop, not the virtual desktop where it was launched
https://bugs.kde.org/show_bug.cgi?id=442273 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #5 from Henry Pfeil --- Obviously not about to be addressed by a competent advanced-degreed computer scientist. I am withdrawing this bug as won't ever happen. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487972] k3b refuses to honor the contents of ~/.config/k3brc
https://bugs.kde.org/show_bug.cgi?id=487972 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Henry Pfeil --- I am withdrawing anything related to such software that is obviously bereft of a well-thought-out design by an advanced-degreed computer scientist -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487211] Ejected a non-readable dvd
https://bugs.kde.org/show_bug.cgi?id=487211 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Henry Pfeil --- It is a fools errand attempting to turn this deplorable kludge into something it is not. I consider it unfortunate that K3b sullies the excellent Plasma Desktop and the KDE applications. Thus, I am withdrawing anything related to such software that is obviously bereft of a well-thought-out design by an advanced-degreed computer scientist. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487972] New: k3b refuses to honor the contents of ~/.config/k3brc
https://bugs.kde.org/show_bug.cgi?id=487972 Bug ID: 487972 Summary: k3b refuses to honor the contents of ~/.config/k3brc Classification: Applications Product: k3b Version: 23.08.5 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video DVD Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY I use /dev/sr0 for digitizing discs stored in a self-storage facility for over a decade; currently using /dev/sr1 for ddrescue the discs that succumbed to bit rot with brown edges. In ~/.config/k3brc I have sr1 commented out, since k3b hangs trying to read a disc with bad sectors, dmesg shows the read errors generated. it just doesn't give up trying to read bit-rotten discs. K3b opens with both drives listed. I highlight sr0. When I open Copy Medium, it hangs on the first page trying once again to read a defective disk on sr1, ignoring ~/.config/k3brc which has that drive commented out. Eventually, over half a minute later, I choose Only Create Image and get into the Image tab where the Source Medium is always the wrong drive. I have to manually select sr0 with a good disc. With the Source Medium showing the DVD title with upper-case first letters of each word, while the Write Image window displays the same title all lower case. Bug: K3brc defines only the internal disc drive, yet k3b ignores that setting and displays info on both drives. This is incorrect, clearly violating the Principal of Least Astonishment. The manual was last touched over a decade ago; a search for k3brc returns empty results. STEPS TO REPRODUCE 1. Open K3b on a box with two DVD drives. Observe both drives in the upper-left window. 2. Choose the Copy Medium from the lower right. 3. OBSERVED RESULT K3b hangs for over half a minute trying to read the wrong disc before opening the medium copy dialog. EXPECTED RESULT Just like audio CD ripping which ignores the bad disc in the other drive. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.116.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I've never used two drives before, so I don't know if it ever worked correctly. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486754] K3b hangs on startup when another process is reading the same device
https://bugs.kde.org/show_bug.cgi?id=486754 Henry Pfeil changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Henry Pfeil --- Upon further rooting around I discovered this is part of a design flaw which I addressed in a different bug. Thus, this bug is closed. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487215] New: Crashes when ejecting a disc with read errors
https://bugs.kde.org/show_bug.cgi?id=487215 Bug ID: 487215 Summary: Crashes when ejecting a disc with read errors Classification: Applications Product: k3b Version: 24.04.90 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I'm digitizing all of my CDs/DVDs because bit rot has damaged a dozen or so discs so far. STEPS TO REPRODUCE 1. Copy medium. Only create image. Begin copying the disc to iso. 2. Things proceed as advertised until k3b starts throwing read errors. 3. Eject the bad disc, either from the menu, or press the eject button. OBSERVED RESULT K3b crashes, a bug report pops up EXPECTED RESULT Produce an iso image like the hundreds of correct discs already digitized. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I tried submitting a bug report, but they always hang trying to log in. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487211] New: Ejected a non-readable dvd
https://bugs.kde.org/show_bug.cgi?id=487211 Bug ID: 487211 Summary: Ejected a non-readable dvd Classification: Applications Product: k3b Version: 23.08.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Application: k3b (23.08.5) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.9.0 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I inserted a DVD to play; unreadable due to bit rot. I ejected the disk, which took an unusally-long time, a hanged process. While the disc was still inside the player, k3b exploded, generating this bug report. I could not attempt to reproduce this, I just tossed in the ddrescue cue. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: K3b (k3b), signal: Aborted [New LWP 25360] [New LWP 25362] [New LWP 25363] [New LWP 25364] [New LWP 25365] [New LWP 25366] [New LWP 25367] [New LWP 25371] [New LWP 25372] [New LWP 25373] [New LWP 25394] [New LWP 25531] [New LWP 30980] [New LWP 24837] [New LWP 24839] [New LWP 24840] [New LWP 24847] [New LWP 24848] [New LWP 24849] [New LWP 24850] [New LWP 24858] [New LWP 24859] [New LWP 24860] [New LWP 24861] [New LWP 24862] [New LWP 24863] [New LWP 24864] [New LWP 24865] [New LWP 24866] [New LWP 24867] [New LWP 24869] [New LWP 24870] [New LWP 24871] [New LWP 24877] [New LWP 24878] [New LWP 24879] [New LWP 24880] [New LWP 24881] [New LWP 24882] [New LWP 24883] [New LWP 24884] [New LWP 24885] [New LWP 24886] [New LWP 24887] [New LWP 24895] [New LWP 24896] [New LWP 24897] [New LWP 24898] [New LWP 24899] [New LWP 24900] [New LWP 27872] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fa021291566 in __futex_abstimed_wait_cancelable64 () from /lib64/libc.so.6 [KCrash Handler] #4 0x7fa021296aab in pthread_kill@@GLIBC_2.34 () from /lib64/libc.so.6 #5 0x7fa021242e12 in raise () from /lib64/libc.so.6 #6 0x7fa02122849f in abort () from /lib64/libc.so.6 #7 0x7fa0214a89db in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7fa0214b7fea in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7fa0214b8055 in std::terminate() () from /usr/lib64/libstdc++.so.6 #10 0x7fa0214b790c in __gxx_personality_v0 () from /usr/lib64/libstdc++.so.6 #11 0x7fa023b6d884 in ?? () from /usr/lib64/libgcc_s.so.1 #12 0x7fa023b6e285 in _Unwind_Resume () from /usr/lib64/libgcc_s.so.1 #13 0x7fa021899410 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x7fa0218cd0ad in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #15 0x7fa0219d65c8 in QDebug::~QDebug() () from /usr/lib64/libQt5Core.so.5 #16 0x7fa02cbd1f2b in ?? () from /usr/lib64/libk3bdevice.so.8 #17 0x7fa02cbd24aa in ?? () from /usr/lib64/libk3bdevice.so.8 #18 0x7fa02cbcc3bc in K3b::Device::Device::read10(unsigned char*, unsigned int, unsigned long, unsigned int, bool) const () from /usr/lib64/libk3bdevice.so.8 #19 0x7fa02cf39a6d in ?? () from /usr/lib64/libk3blib.so.8 #20 0x7fa02cf39c7c in ?? () from /usr/lib64/libk3blib.so.8 #21 0x7fa02cf3b238 in ?? () from /usr/lib64/libk3blib.so.8 #22 0x7fa02cedcee5 in K3b::Thread::run() () from /usr/lib64/libk3blib.so.8 #23 0x7fa0218d3ac9 in ?? () from /usr/lib64/libQt5Core.so.5 #24 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #25 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 51 (Thread 0x7f9f7e0006c0 (LWP 24900) "k3b:sh3"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa0114ecbfb in ?? () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fa01150b3a7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #6 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 50 (Thread 0x7f9f7ea006c0 (LWP 24899) "k3b:gl0"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa0114ecbfb in ?? () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fa01150b3a7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #6 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 49 (Thread 0x7f9f7f4006c0 (LWP 24898) "k3b:gdrv0"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3
[k3b] [Bug 323344] CD ripping: When you cancel ripping, K3b forgets user-entered metadata and reloads all from CDDB
https://bugs.kde.org/show_bug.cgi?id=323344 Henry Pfeil changed: What|Removed |Added CC||hpf...@psnarf.org --- Comment #6 from Henry Pfeil --- <> This issue appears in duckduckgo searches. The solution is to use the floppy disk icon on the bottom left corner of the CD Ripping page that saves your Settings and File Naming changes, which remain active for the rest of the k3b session. In a new session, the curved-arrow icon next to the floppy icon restores your [multiple] saved settings. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486818] Windows-centric filename patterns
https://bugs.kde.org/show_bug.cgi?id=486818 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Henry Pfeil --- I looked at the relevant code. This problem lies with the CDDB database. It appears that the db is sullied by children misusing Windows submissions: full of spaces, apostrophes, parentheses, semicolons, commas, mixed case, different languages and all. This would be a monster task to impose standards-compliancy upon the existing entries, not so much for new entries after the screens are in place. A few sed and tr statements in the get-cddb functions would fix it, but violations of file-naming standards is in cddb.org, not K3b. Since it is relatively easy for me to fix the mess in post-processing, this is not a bug. Who knows who enforces international file-naming standards. Me, I'm more focused upon 'works only in Windows' webbage, making folks aware of https://validator.w3.org and http://www.anybrowser.org/campaign when I can no longer log in to pay my bills because some moron hired a code jockey who is capable only of manipulating a Windows html-design gooey. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486818] New: Windows-centric filename patterns
https://bugs.kde.org/show_bug.cgi?id=486818 Bug ID: 486818 Summary: Windows-centric filename patterns Classification: Applications Product: k3b Version: 24.04.80 Platform: Slackware OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY K3b appears to be Windows-centric. When ripping audio tracks, such as digitizing years-old cds before bit-rot sends it to the ddrescue queue, linux folk have to change the target folder for each disc, then edit the File Naming tab to eliminate spaces from the patterns, the check Replace all blanks. Postproduction requires deleting commas, colons, semicolons, and unprintable chars from the filenames, none of which may not be necessary on windows boxen. STEPS TO REPRODUCE 1. Start Ripping OBSERVED RESULT Need to change target Target Folder, since K3b ignores the temporary folder in settings, remove each space from the Ripped-files and Playlist patterns, and Replace all blanks with underscores. Post production requires a sed script to remove commas, colons, semicolons, unprintable characters, and all to prevent File-Not-Found errors on a command-line interface. EXPECTED RESULT An option in Settings to choose filenames with no spaces, escape the special chars that the bash shell uses, and a default target directory instead of just tossing everything into the $HOME directory. In addition, should be able to set the default ripping filetype, since not everyone wants compression and Copy Medium is broken. [Workaround - cajole the coders into compliance with the Law of Least Astonishment or use ffmpeg concatenate to create a single wav file from all of the Track.wav files using the filename of the tracks directory .] SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442273] application window opens in the currently-active virtual desktop, not the virtual desktop where it was launched
https://bugs.kde.org/show_bug.cgi?id=442273 --- Comment #4 from Henry Pfeil --- Should kwin keep track of the desktop upon which it was launched? Is adding a new variable holding the launch-desktop number, then checking it before painting the window too difficult a task? If so, please close this issue as not-gonna-fixit, rather than leaving it open for years. Maybe change it to wishlist? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486754] K3b hangs on startup when another process is reading the same device
https://bugs.kde.org/show_bug.cgi?id=486754 --- Comment #1 from Henry Pfeil --- I got around the issue by suspending the ddrescue process before launching K3b. Since this is such an obscure instance of incorrect behavior, more pressing matters may push this to the end of the queue. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486737] Copy Medium for audio CD does not create an iso image
https://bugs.kde.org/show_bug.cgi?id=486737 --- Comment #3 from Henry Pfeil --- >From Dolphin, Removable Devices, double-click "Audio CD" which opens audiocd:/?device=/dev/sr0. Choose "Full CD/Full CD.wav". Kioexec opens the file in Videolan's VLC (or whatever is your default for playing wav files), pause the playback. Then `cp -v ~/.cache/kioexec/krun/x-0/Full\ CD.wav " Et voila! I had to resort to such trickery because the k3b Clone tool produces two files, bin and toc, which needs to be converted before players like Elisa can read it. (toc2wav did nothing) I can do no further menu-tree testing because of k3b bug 486754. There might be something in k3b that produces a single wav file, but I can't find it. Ddrescue takes a couple of days to rescue bit rot; I'll not interrupt that process for an application gone wacky when kioexec does what I want out of the box. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486754] K3b hangs on startup when another process is reading the same device
https://bugs.kde.org/show_bug.cgi?id=486754 Henry Pfeil changed: What|Removed |Added Summary|K3b hangs on startup with 2 |K3b hangs on startup when |devices (/dev/sr0, |another process is reading |/dev/sr1) |the same device -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486754] New: K3b hangs on startup with 2 devices (/dev/sr0, /dev/sr1)
https://bugs.kde.org/show_bug.cgi?id=486754 Bug ID: 486754 Summary: K3b hangs on startup with 2 devices (/dev/sr0, /dev/sr1) Classification: Applications Product: k3b Version: 24.04.80 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: GUI/Usability Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY With ddrescue repairing disc rot on /dev/sr1, startup hangs trying to read the damaged disc. STEPS TO REPRODUCE 1. Run ddrescue on /dev/sr1 on another virtual desktop 2. Launch k3b 3. Do something else on a different desktop for a while. OBSERVED RESULT K3b hangs on the startup logo screen for an undetermined long time. Have to kill the process and relaunch, which sometimes works, mostly not EXPECTED RESULT K3b completes launching with the unreadable device grayed out. It should take only a couple of seconds to determine the disc is not readable in its entirety, less time if another process has the device open. [lsof|grep sr1?] SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION Kernel Version: 6.6.30 64-bit -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486737] Copy Medium for audio CD does not create an iso image
https://bugs.kde.org/show_bug.cgi?id=486737 --- Comment #2 from Henry Pfeil --- Correction: "Writing Mode" is greyed out when "Copy Mode" is changed to "Clone Copy." -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486737] Copy Medium for audio CD does not create an iso image
https://bugs.kde.org/show_bug.cgi?id=486737 Henry Pfeil changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Henry Pfeil --- Status - RTFM If you want a CD image, in addition to choosing "Only Create Image," under the Options tab for "Copy Medium," Change "Normal Copy" to "Clone Copy"; under "Writing Mode" choose RAW. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486737] New: Copy Medium for audio CD does not create an iso image
https://bugs.kde.org/show_bug.cgi?id=486737 Bug ID: 486737 Summary: Copy Medium for audio CD does not create an iso image Classification: Applications Product: k3b Version: 24.04.80 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Audio Project Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Audio CD "Copy Medium" does not produce an iso image like it does with data CDs. STEPS TO REPRODUCE 1. Insert audio CD 2. Choose Copy Medium 3. Options - choose "Only Create Image" OBSERVED RESULT Creates new folder with the name of the Image File that contains ripped tracks titled Track0#.wav, e.g, Track01.wav, Track02.wav, EXPECTED RESULT Create an iso image of the audio CD. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 6.6.30 (64-bit) ADDITIONAL INFORMATION If the CD contains data files, Copy Medium creates an iso image as advertised. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 128434] Preview tooltip for hyperlinks to other pages
https://bugs.kde.org/show_bug.cgi?id=128434 Henry Gebhardt changed: What|Removed |Added CC||hsggebha...@gmail.com --- Comment #10 from Henry Gebhardt --- (In reply to Philip from comment #6) > I find Evince's link preview well done. Thank you! As the main person who implemented Evince's link preview behavior (https://gitlab.gnome.org/GNOME/evince/-/commit/f95c24b96de0024f5888e1b11f787ad1432e2263) (just the behavior, not the previews themselves), I can explain the considerations that went into Evince's link previews, as well as common complaints. In order to be useful, Evince's link previews need to have several characteristics. First, the text in the link preview needs to be readable (as already mentioned in the description of this bug). Second, the size of the popup needs to span the entire width of the page, because links only contain a single (x,y) coordinate, and the convention where the content is relative to the link destination (x,y) differs for different types of links (see below). Third, vertically the link preview is at most 1/3 the size of the main view, so that the preview doesn't dominate the view, while still showing sufficiently much around that (x,y) destination. fancy-previews would be awesome (as mentioned in Comment #2), but are not used much, so cannot be depended upon. As to what should be shown inside the preview, I did a survey of the different kinds of links I saw in papers on https://arxiv.org/, many of which have two columns of text side-by-side on each page. The different types of links are: * Section headers, bibliographic references, footnotes, and tables have the link point to the top left of the content they are pointing to. * Equations have the link point to the equation number that is printed to the right of the actual equation. * Links to figures usually point to the caption below the figure. Evince does not try to heuristically fix incorrectly set links (e.g., the problem of Def 2 pointing to Def 4 mentioned in one of the duplicate bugs). The upshot is that the best destination area to show is such that the link points to just a little above the center of the previewed area. I did a (more detailed but somewhat shitty) writeup of all this at http://www.2-node-supercomputer.net/2020/blog-20201114-evince-link-preview.html (sorry no https). Though the most concise explanation is in the previously linked Evince commit https://gitlab.gnome.org/GNOME/evince/-/commit/f95c24b96de0024f5888e1b11f787ad1432e2263. A common complaint about Evince's behavior is that the link preview is automatically triggered when hovering over a link, and this can get annoying when there are many links on the page. Evince maintainers are opposed to adding a configuration option to disable opening a preview. Alternatively, one could also imagine showing the link previews only on some other action, say, when clicking the link (and double click could follow the link - this has not been explored further, just thinking out loud). PDFs with incorrectly set links have also occasionally led to bug reports on Evince. Some people also don't like the aethestics of a preview spanning the entire width. However, this is crucial to get all the aforementioned link types displayed sufficiently, especially for papers with two columns. I hope this helps in deciding to add link previews to Okular, perhaps with a different take on them, perhaps similar to Evince. They are immensely useful when reading papers with lots of equations and references, so I do hope someone will find the time to implement them in Okular, and I am willing to help where I can as I am enjoying Plasma 6 quite a bit. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 484202] Settings in k3brc ignored - Symptoms vanished ==> Closed
https://bugs.kde.org/show_bug.cgi?id=484202 Henry Pfeil changed: What|Removed |Added Resolution|--- |FIXED Summary|Settings in k3brc ignored |Settings in k3brc ignored - ||Symptoms vanished ==> ||Closed Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 484202] Settings in k3brc ignored
https://bugs.kde.org/show_bug.cgi?id=484202 --- Comment #2 from Henry Pfeil --- This issue mysteriously vanished with an update. Status: FMTM [Mystery To Me] -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 484202] Settings in k3brc ignored
https://bugs.kde.org/show_bug.cgi?id=484202 --- Comment #1 from Henry Pfeil --- This issue presents itself both in Fedora 39 and Slackware-current. I have the file-naming strings defined with no spaces in kb3rc, yet k3b presents the default folder/file names with spaces. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 484202] New: Settings in k3brc ignored
https://bugs.kde.org/show_bug.cgi?id=484202 Bug ID: 484202 Summary: Settings in k3brc ignored Classification: Applications Product: k3b Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Application does not honor .config/k3brc. Ripping audio cd, changes wav to ogg, the directory to ~/Music instead of the directory in the rc file. EXPECTED RESULT Expect directory and format to be the same as in the .config/k3brc file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme
https://bugs.kde.org/show_bug.cgi?id=482645 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482941] App icons in system tray not inheriting correct colors
https://bugs.kde.org/show_bug.cgi?id=482941 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 --- Comment #16 from Henry Zhang --- (In reply to Albert Astals Cid from comment #15) > FWIW i still can not reproduce such an issue with a very similar setup, > except i don't have hidpi, are you running some hidpi zoom that is not an > integer number? Yes. I could reproduce on 150% scaling but not 100%. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477700] windows shrink when tabs are added/closed on x11
https://bugs.kde.org/show_bug.cgi?id=477700 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com --- Comment #31 from Henry Zhang --- Downgrading qt5-base from 5.15.11+kde+r147-1 to 5.15.11+kde+r146-1 fixes this issue for konsole on my machine Seems that the only difference is https://invent.kde.org/qt/qt/qtbase/-/commit/56faf7249c3857f80f6483c5070e7408c2d53961 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 --- Comment #13 from Henry Zhang --- Downgrading qt5-base from 5.15.11+kde+r147-1 to 5.15.11+kde+r146-1 fixes this issue for konsole Seems that the only difference is https://invent.kde.org/qt/qt/qtbase/-/commit/56faf7249c3857f80f6483c5070e7408c2d53961 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 480029] New: ./kdesrc-build --initial-setup cannot find linux.ini
https://bugs.kde.org/show_bug.cgi?id=480029 Bug ID: 480029 Summary: ./kdesrc-build --initial-setup cannot find linux.ini Classification: I don't know Product: kde Version: unspecified Platform: Slackware OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY *** kdesrc-build/data/pkg/linux.ini does not exist *** STEPS TO REPRODUCE 1. run `./kdesrc-build --initial-setup` 2. 3. OBSERVED RESULT Only a few distro-centric ini files in kdesrc-build/data/pkg. EXPECTED RESULT No error messages SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION `touch data/pkg/linux.ini` cleared the error message. I checked a couple of distro-centric ini files; everything therein is already installed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479581] Disconnecting external displays leave window out of the laptop screen
https://bugs.kde.org/show_bug.cgi?id=479581 Henry Hu changed: What|Removed |Added Version|unspecified |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479581] New: Disconnecting external displays leave window out of the laptop screen
https://bugs.kde.org/show_bug.cgi?id=479581 Bug ID: 479581 Summary: Disconnecting external displays leave window out of the laptop screen Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: henry.hu...@gmail.com Target Milestone: --- SUMMARY My laptop connects to 2 monitors. When I unplug both, the windows on the right monitor stays out of the screen. STEPS TO REPRODUCE 1. Open windows on both external monitors, maximized. 2. Disconnect both external monitors OBSERVED RESULT The windows on the right monitor are now out of the screen EXPECTED RESULT The windows on the right monitor get moved into the laptop screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Laptop: ThinkPad X1 Carbon Gen 9 Graphics processor: Mesa Intel Xe Graphics Processor: i7-1185G7 My external monitors are 4K at left and 1440p at right. Left one is the main monitor. When plugged in, I set the laptop screen to be disabled. My laptop screen is also 4K. After unplugging, the windows on the right monitor still show up in Alt-Tab, but when you switch to them, they don't show up. I can manually move them back using window menu's 'Move' action, but that's cumbersome. I'm running Plasma with Wayland. In the past I did the same thing with X11, and this was not an issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 --- Comment #10 from Henry Zhang --- Created attachment 164586 --> https://bugs.kde.org/attachment.cgi?id=164586=edit konsole -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 --- Comment #9 from Henry Zhang --- Similar issue here, but in Konsole Maybe the same bug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464326] Status bar shows incorrect symlink path for files
https://bugs.kde.org/show_bug.cgi?id=464326 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Matthew Henry changed: What|Removed |Added CC||matthewjhdec1...@gmail.com --- Comment #42 from Matthew Henry --- Not sure if it's any help, but I'm also encountering this issue. It happens in any situation where the monitors are not in a multiple of 100% (ie 100, 200 are fine but 125% is not) for scaling. I have 2 monitors: 1 4k 60 Hz and 1 4k 120 Hz. Plasma version (wayland) is 5.27.6 Spectacle version is 23.04.3-1 (from arch repository) Nvidia gpu (driver version: 535.54.03-1 3080 Ti) Not sure what information would be useful to track down something like this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 Henry changed: What|Removed |Added CC||henryren@gmail.com --- Comment #23 from Henry --- (In reply to Ondřej Niesner from comment #21) > Same was also happening on GNOME. It doesn't matter how many screens you > have. I have this issue on my laptop which has just one builtin display. > This is really annoying bug especially with touchpad when you always need to > grab the window from wrong position. Also the window is totally messing it's > position when you try to resize it. > > In mutter it was fixed > https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/ > 2942?commit_id=7eb01304259b5977feaee3b2d0a2073b70312d89 > > Is it possible to use in in kwin? Hello, I also have this problem. Maybe an easier approach is to check in `void Window::startDelayedInteractiveMoveResize()` to determine if the window was maximized (and then doing the anchor coordinates) similar to how it is done in `bool Window::startInteractiveMoveResize()` in `window.cpp`. It is my first time posting, please correct me if I did anything wrong -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464930] Graphical glitching in title bars when rearranging windows and pinning them to different sides and corners.
https://bugs.kde.org/show_bug.cgi?id=464930 --- Comment #2 from Matthew Henry --- Created attachment 155746 --> https://bugs.kde.org/attachment.cgi?id=155746=edit Multiple windows with glitched title bars Another example encountered while exploring new features. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464930] Graphical glitching in title bars when rearranging windows and pinning them to different sides and corners.
https://bugs.kde.org/show_bug.cgi?id=464930 Matthew Henry changed: What|Removed |Added Summary|Graphical glitching in |Graphical glitching in |title bars (that only |title bars when |appears to affect GTK |rearranging windows and |applications so far) when |pinning them to different |rearranging windows after |sides and corners. |using the tiling interface | |through the super + T key | |combo. | --- Comment #1 from Matthew Henry --- Upon further use of the beta release I am encountering the same issue even without using super + T, this appears to be a general issue with pinning to sides and corners. I have also seen the behavior occur in QT applications (spectacle) as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464930] New: Graphical glitching in title bars (that only appears to affect GTK applications so far) when rearranging windows after using the tiling interface through the super + T
https://bugs.kde.org/show_bug.cgi?id=464930 Bug ID: 464930 Summary: Graphical glitching in title bars (that only appears to affect GTK applications so far) when rearranging windows after using the tiling interface through the super + T key combo. Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matthewjhdec1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 155719 --> https://bugs.kde.org/attachment.cgi?id=155719=edit Screenshot with glitch on righthand window. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open two or more windows of firefox. 2. Hit super + T and access the tiling screen. 3. Drag to screen corners or super + arrow key. OBSERVED RESULT Graphical corruption of application window title bar see screenshot. This was observed installing beta from kde-unstable repos under EndeavourOS (arch-based). I tried repeating the process with Kate and could not replicate the abnormal behavior, so perhaps a GTK application issue? A screenshot of the behavior and a copy of neofetch for system details are included in the attachments. If there is some log or info output that would be helpful, please let me know! This is my first time reporting so my apologies if there is missing info, this is the wrong spot, or I accidentally duplicated an existing report since I didn't see anything that looked similar in search. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.8-arch1-1/Plasma 5.26.90 (wayland) (available in About System) KDE Plasma Version: 5.26.90 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION matt-82ju% neofetch ./o. matt@matt-82ju ./o--- `:osss+- OS: EndeavourOS Linux x86_64 `:+sso/.Host: 82JU Legion 5 15ACH6H `-/oso/. Kernel: 6.1.8-arch1-1 `-/+o+:`Uptime: 26 mins `-:/+sso+/. Packages: 1556 (pacman) `.://oo++- Shell: bash 5.1.16 .://+ssso++: Resolution: 1920x1080 .:///oso++:DE: Plasma 5.26.90 `:ssso+++. WM: kwin `-+ssso- WM Theme: Shiny-Blur-Aurorae `..-+ooo+/` Theme: Breath2 2021 Light [Plasma], Infinity-GTK [GTK2/3] ./++/:. Icons: Shadows-Light-Icons [Plasma], Shadows-Light-Icons [GTK2/3] `:--`` Terminal: konsole CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 3.200GHz GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series Memory: 3819MiB / 13833MiB -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462914] glitched horizontal lines in text selection @ 150% scale on X11
https://bugs.kde.org/show_bug.cgi?id=462914 Henry Zhang changed: What|Removed |Added CC||henry-...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 461614] It is very simple to obtain WiFi passwords as plain text
https://bugs.kde.org/show_bug.cgi?id=461614 --- Comment #4 from Lt-Henry --- (In reply to Nate Graham from comment #3) > Maybe for standard user accounts, we could require entering the user's > password to show the password of the current wifi network? It sounds good to me. However, would be easily accessible from nmcli/dbus. That's why I thought it is not a specific Plasma bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 461614] It is very simple to obtain WiFi passwords as plain text
https://bugs.kde.org/show_bug.cgi?id=461614 --- Comment #2 from Lt-Henry --- (In reply to Nate Graham from comment #1) > The use case seems legitimate for this to be an issue. > > The thing is, ultimately the way a computer is designed to withstand a > potentially hostile environment is with the screen locker used aggressively. > Like, with a one-minute timeout or something. Because it's going to be next > to impossible to secure a local machine against local attacks when the > screen is unlocked. You can also train your students to lock the screen when > they leave the machine, either with Meta+L or perhaps by putting a > Lock/logout widget on their panels, pre-configured to only have the Lock > action visible by default. That way it's just one click on something big and > obvious to lock the screen. Of course we encourage both teachers and students to lock screen whenever they leave. Also, LliureX always comes with default inactivity lock screen settings. I would like to be more aggressive here with a single minute of inactivity for locking but teachers already complain about that, so for the moment, we are trying to teach them about the risks rather than enforce them. Thing is, if you leave a linux desktop unattended an attacker will never get your unix password by any means, even with root privileges he will only get a hash. That's true even for email or cloud services, where the "only" thing he would achieve is a password reset. WiFi seems against this philosophy :\ > Another question: Do your students have Standard accounts or Administrator > accounts? No, neither students nor teachers accounts have administration privileges. We have the role of classroom administrator, the only one inside sudoers. Teachers are allowed for some tasks that students aren't but nothing critical. Using system wide NM connections and policy kit rules, users can connect to WiFi but can not see password. Password is stored on plain text on /etc, but at least is root protected. Not great, but good enough for me. We are using this trick to hide student credentials from snoopers. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 461614] New: It is very simple to obtain WiFi passwords as plain text
https://bugs.kde.org/show_bug.cgi?id=461614 Bug ID: 461614 Summary: It is very simple to obtain WiFi passwords as plain text Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quique...@gmail.com CC: n...@kde.org Target Milestone: --- Copy from Gitlab: ** I want to share with us an issue I have found with my users experience. I am one of the developers of LliureX, a Neon based distribution used by public schools in Valencia, Spain. We have been using ethernet based classrooms since now. Covid-19 event has changed that, well, politicians. Now classrooms are based on laptops connected to WiFi, with either a common password (classic WPA) or enterprise one, where each student has its own user/password. Thing is, wifi passwords can be seen on plain text easily. So once a student sets up his WPA Enterprise connection, it is two clicks distance from seen his credentials in plain text. Even QR codes can be generated with that. Yes, I am aware that no desktop should be left untended without locking, but we are talking about kids or even teachers, with no IT security training at all. Once credentials are stolen, they can use them to impersonate another user and try to access some probably forbidden pages, or even access to cloud services, as credential is shared. I know this is a bit ill-designed from Wireless standard, where no one found important to keep a password secret, but, would be possible to add an extra step in order to show the password? Perhaps, unlocking with login password. ** Nate asked me on Gitlab how students log in into desktop. Students should log in using their own (private) credentials. Now are ldap backed because laptops are shared between students (we are far from a 1:1 student/laptop ratio), but if a student needs a computer at home, I see no problem with classic local unix accounts. There are some schools using auto-login or some sort of well known user (ie: foo/bar) but of course we advise against this model for obvious security and privacy reasons. I have written this because Aleix asked me to do it. I think it is not Plasma fault here, because hiding passwords on plasma-nm won't stop some smart kid to open a terminal and type: nmcli connection show foo --show-secrets My point is to show that perhaps, we have designed Linux desktops with a safe home environment in mind and we have to spend some time thinking on "hostile" environments. Thank you guys in advance for give me some place to talk about this :D -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 461583] New: Some issues providing a default set of global shortcuts as a distro
https://bugs.kde.org/show_bug.cgi?id=461583 Bug ID: 461583 Summary: Some issues providing a default set of global shortcuts as a distro Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: quique...@gmail.com Target Milestone: --- Konsole global hotkey was default to CTRL+ALT+T. At some point, we upgraded from 5.23 (not sure, sorry) to 5.25 and that key combination broke. As a distro, the only way we have found to fix this, is by supplying a custom kglobalshortcutsrc on skel. We had no luck with $XDG_CONFIG_DIRS. However, there are some problems with this approach: * It only works on a fresh new user home * The file has localized strings inside in the "comment" key I think the mechanism for distros to provide a default set of shortcuts needs another approach. PS: default application shortcut is already on .desktop files. Wouldn't be a good idea to fill global access with this info and let users to only override? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 196051] memory problem in Konqueror
https://bugs.kde.org/show_bug.cgi?id=196051 --- Comment #18 from henry --- Since I have stopped using Konqueror, I am unable to provide any information. Thanks. On 10/16/22 20:40, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=196051 > > Justin Zobel changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #17 from Justin Zobel --- > Thank you for reporting this bug in KDE software. As it has been a while since > this issue was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459011] Insufficient space to move 30 Gb of files to a partition with over a terrabyte of free space
https://bugs.kde.org/show_bug.cgi?id=459011 Henry Pfeil changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Henry Pfeil --- Using a Konsole window I was able to trace the problem to files greater than 1 Gb. This suggests it is not a problem with Dolphin, but with system libraries. I'm closing this as a Dolphin bug, but I have no idea where to report moving files larger than 1Gb (`mv `). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459011] New: Insufficient space to move 30 Gb of files to a partition with over a terrabyte of free space
https://bugs.kde.org/show_bug.cgi?id=459011 Bug ID: 459011 Summary: Insufficient space to move 30 Gb of files to a partition with over a terrabyte of free space Product: dolphin Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** Insufficient space error when moving files/directories between partitions with over a terabyte of free space *** STEPS TO REPRODUCE 1. Move 30Gb of files onto a partition with 1.5 Tb free OBSERVED RESULT ERROR: There is not enough space on the disk to write EXPECTED RESULT Just move the files, there is plenty of free space available on the target partition. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.25.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Could this be a result of using 64-bit btrfs partitions? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 458891] New: Leave action makes no sense
https://bugs.kde.org/show_bug.cgi?id=458891 Bug ID: 458891 Summary: Leave action makes no sense Product: kdeplasma-addons Version: 5.24.6 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Switcher Assignee: plasma-b...@kde.org Reporter: quique...@gmail.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY This applet has three actions available: Change user, Lock session and Leave. Leave action has the power symbol and in fact, it performs a shutdown request, not a session log out. So, this is at least, confusing. On the other hand, I find a Leave=="log out" more appropriate for this applet. I am a developer from LliureX distribution and all users I have talked with agree on this. However, there is room for both "power off" and "leave" actions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458737] New: Unable to remove a Secret Service alias using D-BUS
https://bugs.kde.org/show_bug.cgi?id=458737 Bug ID: 458737 Summary: Unable to remove a Secret Service alias using D-BUS Product: frameworks-kwallet Version: 5.97.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: va...@kde.org Reporter: henr...@yahoo.fr CC: kdelibs-b...@kde.org Target Milestone: --- I was testing the Secret Service D-BUS implementation (provided by https://invent.kde.org/frameworks/kwallet/-/merge_requests/11). I have added a new alias using: gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.Secret.Service.SetAlias test /org/freedesktop/secrets/collection/kdewallet It worked fine. I could see the alias created using qdbusviewer-qt5. Also the alias was in ~/.config/kwalletrc: [org.freedesktop.secrets.aliases] test=kdewallet After this test, I wanted to remove the alias. According to the spec (https://specifications.freedesktop.org/secret-service/latest/re01.html), deleting an alias should be done using the special value '/'. So I tried many variations of: gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.Secret.Service.SetAlias test / But the alias was never removed. Workaround: I had to manually remove it from the kwalletrc file. Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 458712] New: A hex editor with a 2Gb file limit is useless
https://bugs.kde.org/show_bug.cgi?id=458712 Bug ID: 458712 Summary: A hex editor with a 2Gb file limit is useless Product: okteta Version: 0.26.9 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY *** Support for files greater than 2 Gb has not yet been implemented?! *** Terrabyte storage devices have been around for quite some time. Files greater than 2 Gb are now quite common, unlike years ago when a 2 Gb limit might have seemed like a smart idea. In 2022 this limit is an impediment to productivity. I hunted down and installed GHex, which is not impaired by a design flaw. I imagine your target audience is those running 32-bit machines. If so, why not a 64-bit version for those in this century? OBSERVED RESULT Fails to open a 32 Gb file. EXPECTED RESULT A useful tool would open a 32 Gb file. Sadly, okteta is not a useful tool. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konquest] [Bug 458482] Planet displays are invisible (grey text against grey background)
https://bugs.kde.org/show_bug.cgi?id=458482 --- Comment #2 from Matthew Henry --- Created attachment 151694 --> https://bugs.kde.org/attachment.cgi?id=151694=edit Grey Text on Grey Pop-Up -- You are receiving this mail because: You are watching all bug changes.
[konquest] [Bug 458482] New: Planet displays are invisible (grey text against grey background)
https://bugs.kde.org/show_bug.cgi?id=458482 Bug ID: 458482 Summary: Planet displays are invisible (grey text against grey background) Product: konquest Version: 2.4.21123 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: pina...@pinaraf.info Reporter: mathuhe...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Pop-up text over a planet matches the background of the same pop-up. The text is un-readable. STEPS TO REPRODUCE 1. Start a game 2. Hover pointer over a planet OBSERVED RESULT pop-up text (grey) is un-readable against pop-up background (also grey) EXPECTED RESULT pop-up text should have some contrast against the pop-up background SOFTWARE/OS VERSIONS Linux Mint 21 Cinnamon 5.4.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430586] Strangeness when right navigation panel off right edge of screen
https://bugs.kde.org/show_bug.cgi?id=430586 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Henry Pfeil --- I cannot replicate this nonsense with a new user. I humbly apologise for wasting your time by bringing this matter to your attention. I will use the new-user test before darkening your doorstep and infesting this place with my beastly presence. Hokayfine, Laterbye -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430586] Strangeness when right navigation panel off right edge of screen
https://bugs.kde.org/show_bug.cgi?id=430586 --- Comment #1 from Henry Pfeil --- This behavior arises in other KDE applications, such as Qt Creator, Firefox source view,. Consequently please reassign this to KDE/Plasma Mouse, press left button to select. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447664] New: Files selected and moved to another another window carry the selected flag over to the new folder.
https://bugs.kde.org/show_bug.cgi?id=447664 Bug ID: 447664 Summary: Files selected and moved to another another window carry the selected flag over to the new folder. Product: dolphin Version: 21.12.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org CC: kfm-de...@kde.org Target Milestone: --- Two Dolphin instances, each open to folders on different drives, Detail view. Select 40,000 files in one folder, drag/drop to the second folder, choose Move. As each file is transferred, it appears selected in the new folder. The status line on the destination folder shows the number of selected files increasing as the number decreases in the source folder. If you change directory of the source folder so those selected files no longer appear, the remainder of the destination folder's files are not selected, the destination number of selected files remains static, displaying the number of selected files before the source folder changed. The selection status of the source files follows it over to the destination. However, if you then go back to the source folder and re-select the source files, the destination folder's selected files remain as they were. This suggests that only the initial selected files are moved to the destination folder carrying their selection status with them. This experiment was performed while moving 46,000 images from one drive to another, a 4+ hr process while another dolphin instance was moving 75,000 files to a different folder at the same time. [Typical file numbers for post-production video work. All the image frames of the video are extracted, altered via a Gimp script, then re-assembled into a new video. A 40Gb video produces over 3Tb of frames.] EXPECTED RESULT The destination files should be un-selected until they are explicitly selected in the new folder. Operating System: Slackware 15.0 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.15.11 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446555] System Settings crashes upon launch
https://bugs.kde.org/show_bug.cgi?id=446555 Jeff Henry changed: What|Removed |Added CC||jbhe...@gmail.com --- Comment #29 from Jeff Henry --- (In reply to Clay Weber from comment #22) > So I installed the package qml-module-org-kde-sonnet , which seems to > have fixed everything Had the same problem and this fixed it for me too. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445501] New: I wish dolphin could handle large files and directories containing a large number of files
https://bugs.kde.org/show_bug.cgi?id=445501 Bug ID: 445501 Summary: I wish dolphin could handle large files and directories containing a large number of files Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** In video post-production, I typically extract over a hundred thousand files in a directory. If I select 4,000 files and right-click, I can go get a sandwich and a beer before the copy/delete pop-up appears. I selected a 30Gb file for deletion, but dolphin cannot delete, it can only move to trash, which in this case is on a different drive; it's been ten minutes and dolphin is still moving that 1 file to Trash. Whenever I have to delete over a thousand files, I launch Filezilla. Those developers have discovered a secret way to delete thousands of files instantly. Perhaps they could share their secret with dolphin? STEPS TO REPRODUCE 1. Do anything involving thousands of files or tens of gigabytes in size. OBSERVED RESULT Nothing for a very long time. EXPECTED RESULT Expect no difference between selecting one file or ten thousand. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION File system: BTRFS, SSD Kernel Version: 5.15.2 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442273] New: application window opens in the currently-active desktop not the desktop where it was launched
https://bugs.kde.org/show_bug.cgi?id=442273 Bug ID: 442273 Summary: application window opens in the currently-active desktop not the desktop where it was launched Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Software like Qt Creator, or Firefox, takes a minute from the time it is invoked until its window appears on the desktop. While waiting, I may go to another desktop to read a just-arrived e-mail message. Even though I launched the application from, for example, desktop 4, its window appears in desktop 5. Would it not be more elegant if the application window opened on the same desktop from which it was launched? Open Qt Creator on desktop6, go to my e-mail desktop3, Creator window opens in desktop6. When I'm finished with my sub-task, I go back to my IDE desktop6 and Creator is up and running. Instead, while I'm reading a message on desktop3, Creator's window opens and obscures the message window I'm reading. Seems a bit intrusive, perhaps even a violation of the Law of Least Astonishment. Same with Firefox or any other program that takes a significant amount of time after launch before its window opens. Seems like the program busies itself setting up data structures, initialization, allocating memory and all, then when it is ready to open its application window, only then does it check to see which desktop on which to open its window, which could be different than the desktop from which it was launched. There must be a way to lock the application window to the launch desktop, even if the currently-active desktop is different. Linux/KDE Plasma: Slackware 15.0 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437836] Error generating new game
https://bugs.kde.org/show_bug.cgi?id=437836 Henry Pfeil changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Henry Pfeil --- Nevermind. I re-installed all of the KDE packages. Problem vanished after I reset the Setting to Default layout, then Random. Everything works. I'm somewhat curious. I wonder how such behavior can be reproduced. Could be a corrupt .config/kmahjonggrc? I noticed a double virgule in the path: "Layout_file=/usr/share/kmahjongg/layouts//totem.desktop" -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437836] Error generating new game
https://bugs.kde.org/show_bug.cgi?id=437836 --- Comment #1 from Henry Pfeil --- *** Bug 437837 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437837] Error generating new game
https://bugs.kde.org/show_bug.cgi?id=437837 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Henry Pfeil --- *** This bug has been marked as a duplicate of bug 437836 *** -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437837] New: Error generating new game
https://bugs.kde.org/show_bug.cgi?id=437837 Bug ID: 437837 Summary: Error generating new game Product: kmahjongg Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hpf...@psnarf.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Choose Random layout after finishing Default, then blank background, no tiles, status bar says 0 Combinations Left, 0 Removed. (game number random) STEPS TO REPRODUCE 1. Finish a game using Default layout. 2. Settings | Configure KMahjongg | Layout | check Random Layout 3. Click OK OBSERVED RESULT A blank game background, no tiles. Click New and everything proceeds as advertised. EXPECTED RESULT Begin next game using random layout. SOFTWARE/OS VERSIONS KMahjongg: 0.9.21041 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION When I then choose Default layout, a new game appears with a random layout. New game: Default layout, blank background, no tiles. Choose New multiple times, random layouts, Settings shows Random Game not clicked. Perhaps a boundary condition, unanticipated congruence of unlikely events? -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437836] New: Error generating new game
https://bugs.kde.org/show_bug.cgi?id=437836 Bug ID: 437836 Summary: Error generating new game Product: kmahjongg Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hpf...@psnarf.org CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 138867 --> https://bugs.kde.org/attachment.cgi?id=138867=edit Game number imgage SUMMARY Choose Random layout after finishing Default, then blank background, no tiles, status bar says 0 Combinations Left, 0 Removed. (game number attached) STEPS TO REPRODUCE 1. Finish a game using Default layout. 2. Settings | Configure KMahjongg | Layout | check Random Layout 3. Click OK OBSERVED RESULT A blank game background, no tiles. Click New and everything proceeds as advertised. EXPECTED RESULT Begin next game using random layout. SOFTWARE/OS VERSIONS KMahjongg: 0.9.21041 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION When I then choose Default layout, a new game appears with a random layout. New game: Default layout, blank background, no tiles. Choose New multiple times, random layouts, Settings shows Random Game not clicked. Perhaps a boundary condition, unanticipated congruence of unlikely events? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437776] New: Spectacle crashes when closing
https://bugs.kde.org/show_bug.cgi?id=437776 Bug ID: 437776 Summary: Spectacle crashes when closing Product: Spectacle Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: henr...@yahoo.fr CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.6-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Fedora 34 (Thirty Four) -- Information about the crash: - What I was doing when the application crashed: I took a screenshot and then closed the Spectacle window using the top right button (X) I tried again open Spectacle and immediately closed it, same crash. The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f98ea21e205 in kImageAnnotator::FontPicker::~FontPicker() () from /lib64/libkImageAnnotator.so.0 #5 0x7f98ea1e3105 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from /lib64/libkImageAnnotator.so.0 #6 0x7f98ea1e34a2 in kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from /lib64/libkImageAnnotator.so.0 #7 0x7f98ea1d961b in kImageAnnotator::CoreView::~CoreView() () from /lib64/libkImageAnnotator.so.0 #8 0x7f98ea1dbc7d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #9 0x7f98ea1dbe6d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #10 0x7f98e889deda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #11 0x7f98e9342f66 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #12 0x55bec03eb461 in KSWidget::~KSWidget() () #13 0x7f98e889deda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #14 0x7f98e9342f66 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #15 0x55bec03f0715 in SpectacleCore::~SpectacleCore() () #16 0x55bec03e899f in main () [Inferior 1 (process 44492) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 436146] Does not create thumbnails of specific files or folders
https://bugs.kde.org/show_bug.cgi?id=436146 --- Comment #4 from Henry --- Hi I understand that you mean to "Remember display style for each folder" but enabling it does not appear any option that refers to the thumbnails. If you know her, please tell me. El mar, 27 abr 2021 a las 20:39, Nate Graham () escribió: > https://bugs.kde.org/show_bug.cgi?id=436146 > > --- Comment #3 from Nate Graham --- > Konqueror probably has the same setting, but I don't know for sure as I > don't > use it. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 436146] Does not create thumbnails of specific files or folders
https://bugs.kde.org/show_bug.cgi?id=436146 --- Comment #2 from Henry --- But not in Konqueror? El mar, 27 abr 2021 a las 12:47, Nate Graham () escribió: > https://bugs.kde.org/show_bug.cgi?id=436146 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|--- |WORKSFORME > CC||n...@kde.org > Status|REPORTED|RESOLVED > > --- Comment #1 from Nate Graham --- > In Dolphin, you can make it use per-folder settings and turn off > thumbnails for > those folders. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 436146] New: Does not create thumbnails of specific files or folders
https://bugs.kde.org/show_bug.cgi?id=436146 Bug ID: 436146 Summary: Does not create thumbnails of specific files or folders Product: kio-extras Version: 20.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: henry.izuri...@gmail.com Target Milestone: --- Thumbnails are very useful, however there are cases in which it is not convenient to have thumbnails of certain files or folders. They can be, for example, secret files or folders or that their owner simply does not want there to be thumbnails of them. To solve this situation I propose to KDE to include an option in folders and files that tells the thumbnail creator not to do its work with that file or folder. Maybe an exclude files and exclude folders in config file. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419206] Konqueror not present menu to select devices in jitsi
https://bugs.kde.org/show_bug.cgi?id=419206 --- Comment #6 from Henry --- this problem also occurs in konqueror in other distributions. I have worked on KDE under Debian and this problem occurs. Right now I can't prove it because I don't have it installed. I insist on Kali-linux konqueror and all KDE works fine. El lun, 5 abr 2021 a las 23:38, Nate Graham () escribió: > https://bugs.kde.org/show_bug.cgi?id=419206 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|NOT A BUG |--- > Status|RESOLVED|REPORTED > > --- Comment #5 from Nate Graham --- > If it happens in other distros too, sure. :) > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419206] Konqueror not present menu to select devices in jitsi
https://bugs.kde.org/show_bug.cgi?id=419206 --- Comment #4 from Henry --- Don't justify your position that I use Kali-linux. The same error I have had in other distributions, but it is now that I have reported it. You are being easy to locate my bug as resolved when it is not. Also in Kali KDE works very well. You are acting bad El lun, 5 abr 2021 a las 20:00, Nate Graham () escribió: > https://bugs.kde.org/show_bug.cgi?id=419206 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > CC||n...@kde.org > > --- Comment #3 from Nate Graham --- > It appears that you are using Kali Linux, which is not appropriate for > general > use, and you will find a million and a half other little weirdnesses like > this, > because running everything as root is explicitly unsupported and never > recommended. I would encourage you to re-install your system with a more > appropriate general purpose Linux distro, such as one of the ones you can > se at > https://kde.org/distributions. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 419798] Konqueror crash on facebook like
https://bugs.kde.org/show_bug.cgi?id=419798 --- Comment #2 from Henry --- Don't justify your position that I use Kali-linux. The same error I have had in other distributions, but it is now that I have reported it. You are being easy to locate my bug as resolved when it is not. Also in Kali KDE works very well. You are acting bad El lun, 5 abr 2021 a las 20:02, Nate Graham () escribió: > https://bugs.kde.org/show_bug.cgi?id=419798 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |NOT A BUG > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > It appears that you are using Kali Linux, which is not appropriate for > general > use, and you will find a million and a half other little weirdnesses like > this, > because running everything as root is explicitly unsupported and never > recommended. I would encourage you to re-install your system with a more > appropriate general purpose Linux distro, such as one of the ones you can > se at > https://kde.org/distributions. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434687] New: Git make test kfileitemmodeltest fail
https://bugs.kde.org/show_bug.cgi?id=434687 Bug ID: 434687 Summary: Git make test kfileitemmodeltest fail Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The following tests FAILED: 6 - kfileitemmodeltest (Failed) STEPS TO REPRODUCE 1. Git clone 2. cmake-gui [Release] 3. make 4. make test OBSERVED RESULT 93% tests passed, 1 tests failed out of 14 Total Test time (real) = 28.96 sec The following tests FAILED: 6 - kfileitemmodeltest (Failed) Errors while running CTest EXPECTED RESULT 100% tests passed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 Henry Pfeil changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #10 from Henry Pfeil --- Built dolphin from git clone this date against qt5.15.2. Cannot replicate any of the crashes reported herein. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Tree View mode crashes in KFileItemModel::removeItems() and shows duplicate items
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #58 from Henry Pfeil --- Problem resolved with current git clone of Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Tree View mode crashes in KFileItemModel::removeItems() and shows duplicate items
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #56 from Henry Pfeil --- I solved this and related issues by using SDK/kdesrc-build to build a version of Dolphin based upon Qt 5.15.3. `./kdesrc-build --stop-on-failure dolphin` Tested in shell using ~/.config/kde-env-master.sh. Created a folder with 1,000 files. Could not replicate any of the crashes in my DrKonqi crash reports. No duplicate file entries, no F5 crash. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 432585] New: ~.kdesrc-buildrc: ignore-kde-structure true is deprecated
https://bugs.kde.org/show_bug.cgi?id=432585 Bug ID: 432585 Summary: ~.kdesrc-buildrc: ignore-kde-structure true is deprecated Product: kdesrc-build Version: 1.16 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: setup wizard Assignee: mp...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY the option ignore-kde-structure true is deprecated. Please substitute the option directory-layout flat in your ~/.kdesrc-buildrc file. STEPS TO REPRODUCE 0. cd ~/kde/src/kdesrc-build 1. ./kdesrc-build-setup 2. ./kdesrc-build --pretend > ../build-order 3. cat ../build-order OBSERVED RESULT # Use a flat folder structure under ~/kde/src and ~/kde/build # rather than nested directories ignore-kde-structure true EXPECTED RESULT # Use a flat folder structure under ~/kde/src and ~/kde/build # rather than nested directories directory-layout flat SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Tree View mode crashes in KFileItemModel::removeItems() and shows duplicate items
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #52 from Henry Pfeil --- Kate Filesystem Browser does not exhibit this crash behavior. Does this suggest that the problem is within Dolphin code and not Frameworks or Qt? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #9 from Henry Pfeil --- I'll go away now. Most of those valgrind errors are not related to Dolphin. "Conditional jump or move depends on uninitialised value(s)" are from Qt. I've cast a weary eye at Qt ever since Cube Desktop Animation stopped switching virtual desktops by left-click/swipe on the desktop (Qt 5.13?). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #8 from Henry Pfeil --- valgrind --leak-check=full --verbose /usr/bin/dolphin ==1087== ERROR SUMMARY: 117610 errors from 1459 contexts If I had inherited such a project, I'd consider starting over. Just sayin'. Many of those errors are from "Conditional jump or move depends on uninitialised value(s)". A full analysis requires rebuilding Qt and KDE with debug symbols, which sounds a lot like work to me. A repeatable crash just opening a directory full of 400+ files is not something easily ignored. An unanticipated congruence of unlikely events suggests a boundary condition violation somewhere. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #7 from Henry Pfeil --- The magic number appears to be 400 files, for reasons which I cannot explain. Starting dolphin from konsole: double free or corruption (out) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = dolphin path = /usr/bin pid = 21715 KCrash: Arguments: /usr/bin/dolphin KCrash: Attempting to start /usr/lib64/drkonqi [1]+ Alarm clock dolphin Test Method: Copy 200 of the 450 files to /dev/shm Open Dolphin on the directory, split with /dev/shm in the other half. Move ten files at a time from /dev/shm to the test folder. After each move, open another instance of dolphin, navigate to the test folder and press F5 refresh. Results: Up to 399 files in the test folder - no crash, no duplicate files. 400 files ==> duplicate aac file and crash upon deleting one of the duplicates or F5 refresh. Meanwhile in the monitor instance, adding files to the test folder has no effect. I moved a total of 900 files into the open test folder no problem. The crash behavior only appears upon launching a new instance of dolphin and opening the test folder, not upon adding more files to an already open folder in dolphin. Here's hoping this information may isolate the faulty code. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #6 from Henry Pfeil --- Nevermind. Dolphin crashes in Details mode with the 450+ directory open simply by F5 refresh. KfileMetadata update removed some, but not all of the duplicate entries (the aac file is now the only duplicate). Scrolling down so the last dozen files are in view, then F5 = crash. These are png image files extracted from an mp4 using ffmpeg named fu-%03d.png (fu{1..453}.png) plus one aac file. I do not know how many files a folder has to contain before things go boom. That may be something to explore next. [Retired systems analyst, exploring which criteria cause the crashes without examining any code] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #5 from Henry Pfeil --- I am now unable to replicate this crash after upgrading to kfilemetadata-5.78.0. ldd /usr/bin/dolphin reveals /usr/lib64/libKF5FileMetaData.so.3 which is a soft link to /usr/lib64/libKF5FileMetaData.so.5.78.0. I intend to revert to the previous version of kfilemetadata to verify that this upgrade fixed the crashes so you can close this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #3 from Henry Pfeil --- This is not a dolphin issue. I went back to v20.08.0, same issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 --- Comment #1 from Henry Pfeil --- An aac file in the same folder also appears twice, duplicate entries in Details mode. However I'm able to open either one in vlc. I created a text file, it appeared in the folder only once. Moved to Trash no problem. However, when I double-clicked the folder name to make it the top of the file tree, crash. New Dolphin instance, now the text file appears twice. Moved to Trash one of them, crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432443] New: Dolphin: repeatable crash
https://bugs.kde.org/show_bug.cgi?id=432443 Bug ID: 432443 Summary: Dolphin: repeatable crash Product: dolphin Version: 20.12.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.1) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.12 x86_64 Windowing system: X11 Distribution: Slackware 14.2 x86_64 (post 14.2 -current) -- Information about the crash: - What I was doing when the application crashed: Open or delete a 35Mb text file in a directory of 450+ png files - Unusual behavior I noticed: The text file appears twice in Details mode. Right-click-Select either one, choose Open in Kate or Move to Trash. Dolphin crashes KDE Plasma: 5.20.5 KDE Frameworks: 5.78.0 Qt: 5.15.2 Kernel: 5.10.12 x86_64 CPU: Ryzen 7 1700 RAM: 15.6 Gb GPU: Radeon RX550 The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 QHash::isEmpty (this=0x173c698) at /usr/include/qt5/QtCore/qhash.h:285 #5 0x7f07b98406e5 in KFileItemModel::data (this=0xdddfa0, index=90) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kfileitemmodel.cpp:148 #6 0x7f07b98a1bd8 in KStandardItemListWidgetInformant::preferredRoleColumnWidth (this=0x1244ab0, role=..., index=90, view=0x1219c20) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kstandarditemlistwidget.cpp:63 #7 0x7f07b98ce72a in KItemListWidgetCreator::preferredRoleColumnWidth (this=0x126fa60, role=..., index=90, view=0x1219c20) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kitemlistview.h:859 #8 0x7f07b988bad7 in KItemListView::preferredColumnWidths (this=0x1219c20, itemRanges=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kitemlistview.cpp:2221 #9 0x7f07b988be91 in KItemListView::updatePreferredColumnWidths (this=0x1219c20, itemRanges=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kitemlistview.cpp:2276 #10 0x7f07b988c134 in KItemListView::updatePreferredColumnWidths (this=0x1219c20) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kitemlistview.cpp:2315 #11 0x7f07b9886edc in KItemListView::slotItemsRemoved (this=0x1219c20, itemRanges=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kitemlistview.cpp:1130 #12 0x7f07b983b50b in KFileItemListView::slotItemsRemoved (this=0x1219c20, itemRanges=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kfileitemlistview.cpp:339 #13 0x7f07b9896445 in QtPrivate::FunctorCall, QtPrivate::List, void, void (KItemListView::*)(KItemRangeList const&)>::call (f= table offset 536, o=0x1219c20, arg=0x7ffdcdebab40) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #14 0x7f07b9895732 in QtPrivate::FunctionPointer::call, void> (f= table offset 536, o=0x1219c20, arg=0x7ffdcdebab40) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #15 0x7f07b989469a in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x121de20, r=0x1219c20, a=0x7ffdcdebab40, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #16 0x7f07b77fa813 in ?? () from /usr/lib64/libQt5Core.so.5 #17 0x7f07b982b571 in KItemModelBase::itemsRemoved (this=0xdddfa0, _t1=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/build/src/dolphinprivate_autogen/Z3MQH7AOBD/moc_kitemmodelbase.cpp:253 #18 0x7f07b9845e17 in KFileItemModel::removeItems (this=0xdddfa0, itemRanges=..., behavior=KFileItemModel::DeleteItemData) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kfileitemmodel.cpp:1319 #19 0x7f07b9844efc in KFileItemModel::slotItemsDeleted (this=0xdddfa0, items=...) at /home/hpfeil/Downloads/dolphin-v20.12.1/src/kitemviews/kfileitemmodel.cpp:1059 #20 0x7f07b9862ba6 in QtPrivate::FunctorCall, QtPrivate::List, void, void (KFileItemModel::*)(KFileItemList const&)>::call (f=(void (KFileItemModel::*)(KFileItemModel * const, const KFileItemList &)) 0x7f07b9844a90 , o=0xdddfa0, arg=0x7ffdcdebae80) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #21 0x7f07b986081a in QtPrivate::FunctionPointer::call, void> (f=(void (KFileItemModel::*)(KFileItemModel * const, const KFileItemList &)) 0x7f07b9844a90 , o=0xdddfa0, arg=0x7ffdcdebae80) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #22 0x7f07b985d47a in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x1218c40, r=0xdddfa0, a=0x7ffdcdebae80, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #23 0x7f07b77fa813 in ?? () from /usr/lib64/libQt5Core.so.5 #24 0x7f07b8fcadf5 in KCoreDirLister::itemsDeleted(KFileItemList const&) () from /usr/lib64/libKF5KIOCore.so.5 #25 0x7f07b8fce150 in ?? ()
[kontact] [Bug 373197] Kontact Crash when using "Mark All Messages as Read" option
https://bugs.kde.org/show_bug.cgi?id=373197 David henry changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from David henry --- I haven't had the problem again under regular use. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419206] Konqueror not present menu to select devices in jitsi
https://bugs.kde.org/show_bug.cgi?id=419206 --- Comment #2 from Henry --- El jue, 31 dic 2020 a las 8:01, Graham Perrin () escribió: > https://bugs.kde.org/show_bug.cgi?id=419206 > > Graham Perrin changed: > >What|Removed |Added > > > CC||grahamper...@gmail.com > > --- Comment #1 from Graham Perrin --- > Cross reference: > > bug 431004 - Screen sharing non-functional at meet.jit.si (Jitsi Meet) > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430586] New: Strangeness when right navigation panel off right edge of screen
https://bugs.kde.org/show_bug.cgi?id=430586 Bug ID: 430586 Summary: Strangeness when right navigation panel off right edge of screen Product: kate Version: 20.12.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY When the window is moved so the right navigation panel is off the right edge of the screen, cursor hops lines, changed icon blinks. STEPS TO REPRODUCE ... if(foo) { bar; } } With cursor placed at the closing brace of the if-statement, it hops back and forth to the function closing brace. The line and column number at the bottom of the edit window follows the bouncing cursor, the file-changed icon in the tab title flashes. This nonsense stops as soon as I move kate's window leftward enough to reveal the navigation panel, but starts again as soon as the edit window navigation panel is just off the right edge of the screen or the edit changes are saved to disc. (The window was moved to the right side of the screen to follow example code in the browser window on the left side of the screen.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.84 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430205] Named pipes left in /tmp not removed upon exit.
https://bugs.kde.org/show_bug.cgi?id=430205 Henry Pfeil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430205] Named pipes left in /tmp not removed upon exit.
https://bugs.kde.org/show_bug.cgi?id=430205 --- Comment #2 from Henry Pfeil --- I isolated the issue to something in the user's ~/.local folder. A new user did not replicate the issue, a blank ~/.local resolved the vestigial named pipes. Although I'd like to know what in ~/.local could cause kate to create and leave behind named pipes in /tmp, consider this a personal mystery. Will follow up with an FYI should I discover a repeatable config setting. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430205] Named pipes left in /tmp not removed upon exit.
https://bugs.kde.org/show_bug.cgi?id=430205 --- Comment #1 from Henry Pfeil --- This happens on only one of my computers, not the other. Is there something in my .config that would cause these named pipes to appear in /tmp? I am not convinced the named pipes are from Kate code, as I cannot find any instance of QQueue. KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.4.82 CPU: AMD Ryzen 7 1700 GPU: AMD/ATI Lexa Pro [Radeon RX550/550] -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430205] New: Named pipes left in /tmp not removed upon exit.
https://bugs.kde.org/show_bug.cgi?id=430205 Bug ID: 430205 Summary: Named pipes left in /tmp not removed upon exit. Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Version 20.11.90 - issue introduced in 20.08.03 Three named pipes are created in /tmp: stdInFIFOxxx, stdOutFIFOxxx, and stdErrFIFOxxx, where xxx are random letters. Upon exit, those named pipes remain in /tmp. Each time Kate is launched, three more named pipes are created, which are not deleted by the destructor of the class that created them. STEPS TO REPRODUCE 1. Launch Kate 2. Do stuff 3. Close Kate OBSERVED RESULT Three named pipes created at startup remain after exit. I noticed them after I found 24 such pipes in /tmp. EXPECTED RESULT All temporary named pipes are closed and deleted upon exit. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430200] New: Kmail not load kwallet
https://bugs.kde.org/show_bug.cgi?id=430200 Bug ID: 430200 Summary: Kmail not load kwallet Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: henry.izuri...@gmail.com Target Milestone: --- Application: kmail (5.14.1 (20.04.0)) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-kali2-686-pae i686 Distribution: Kali GNU/Linux Rolling -- Information about the crash: - What I was doing when the application crashed: configuring Kmail from mi account in google. previously akkonadi is down - Custom settings of the application: write password of mail server -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xa1cfc0c0 (LWP 4140))] Thread 23 (Thread 0x94998b40 (LWP 5685)): #0 0xb7fd3579 in __kernel_vsyscall () #1 0xb6490003 in __GI___libc_read (nbytes=10, buf=0x94997752, fd=86) at ../sysdeps/unix/sysv/linux/read.c:26 #2 __GI___libc_read (fd=86, buf=0x94997752, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #3 0xa6297638 in pa_read () at /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-13.0.so #4 0xa8f44b37 in pa_mainloop_prepare () at /lib/i386-linux-gnu/libpulse.so.0 #5 0xa8f4560d in pa_mainloop_iterate () at /lib/i386-linux-gnu/libpulse.so.0 #6 0xa8f456dc in pa_mainloop_run () at /lib/i386-linux-gnu/libpulse.so.0 #7 0xa8f53ce1 in () at /lib/i386-linux-gnu/libpulse.so.0 #8 0xa62c5f2e in () at /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-13.0.so #9 0xb3e2d0b4 in start_thread (arg=) at pthread_create.c:477 #10 0xb64a22c6 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 22 (Thread 0x95199b40 (LWP 5026)): #0 0xb6a3fe00 in QElapsedTimer::isMonotonic() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #1 0xb6a3ea26 in QTimerInfoList::repairTimersIfNeeded() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #2 0xb6a3eab6 in QTimerInfoList::timerWait(timespec&) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #3 0xb6a40441 in () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb339ac72 in g_main_context_prepare () at /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb339b734 in () at /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb339b964 in g_main_context_iteration () at /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb6a406ec in QEventDispatcherGlib::processEvents(QFlags) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb69e2dc0 in QEventLoop::exec(QFlags) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb680714f in QThread::exec() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb6807228 in QThread::run() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb680853b in () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb3e2d0b4 in start_thread (arg=) at pthread_create.c:477 #13 0xb64a22c6 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 21 (Thread 0x8ba3cb40 (LWP 5016)): #0 0xb6a404c2 in () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #1 0xb339b1d2 in g_main_context_check () at /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb339b7c6 in () at /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb339b964 in g_main_context_iteration () at /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6a406ec in QEventDispatcherGlib::processEvents(QFlags) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb69e2dc0 in QEventLoop::exec(QFlags) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb680714f in QThread::exec() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb6807228 in QThread::run() () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb680853b in () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb3e2d0b4 in start_thread (arg=) at pthread_create.c:477 #10 0xb64a22c6 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 20 (Thread 0x856ecb40 (LWP 5009)): #0 0xb7fd3579 in __kernel_vsyscall () #1 0xb3e34282 in futex_abstimed_wait_cancelable (private=0, abstime=0x856eb700, clockid=, expected=0, futex_word=0x856eb7fc) at ../sysdeps/nptl/futex-internal.h:320 #2 __pthread_cond_wait_common (abstime=, clockid=, mutex=0x856eb7bc, cond=) at pthread_cond_wait.c:520 #3 __pthread_cond_timedwait (cond=0x856eb7d4, mutex=0x856eb7bc, abstime=0x856eb700) at pthread_cond_wait.c:656 #4 0xae199a78 in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #5 0xae19a604 in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #6 0xae19a7a5 in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #7 0xae152b13 in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #8 0xae15bf4e in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #9 0xae15c451 in () at /lib/i386-linux-gnu/libQt5WebEngineCore.so.5 #10 0xae19c895 in () at