[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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 ?? ()
[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.
[wacomtablet] [Bug 428534] New: Compile error: pressurecurvewidget.cpp missing include [reported fixed - not]
https://bugs.kde.org/show_bug.cgi?id=428534 Bug ID: 428534 Summary: Compile error: pressurecurvewidget.cpp missing include [reported fixed - not] Product: wacomtablet Version: 3.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY wacomtablet-v3.2.0/src/kcmodule/pressurecurvewidget.cpp:185:18: error: aggregate ‘QPainterPath curvePath’ has incomplete type and cannot be defined STEPS TO REPAIR 1. Add: #include Qt Version: 5:15;1 ADDITIONAL INFORMATION g++ v10.2.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427085] New: generators/poppler/generator_pdf.h Poppler::OutlineItem error
https://bugs.kde.org/show_bug.cgi?id=427085 Bug ID: 427085 Summary: generators/poppler/generator_pdf.h Poppler::OutlineItem error Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY tag rv20.08.1+, git clone 2020-09-28 generators/poppler/generator_pdf.h:116:53: error: 'OutlineItem' is not a member of 'Poppler'" In poppler-qt5.h QVector< OutlineItem > children () const I don't understand why QVector produces a compile error. I last successfully compiled tag v20.4.3, which did not include OutlineItem. Using kdesrc-build. Cmake error log also shows ‘class Poppler::FormFieldChoice’ has no member named ‘choicesWithExportValues’ 6 | ffc->choicesWithExportValues(); STEPS TO REPRODUCE Cmake error log: /usr/bin/c++ -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -isystem /usr/include/poppler/qt5 -isystem /usr/include/poppler -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui -pipe -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -DHAVE_POPPLER_0_87 -fPIC -std=c++14 C++ v10.2.0 The system is: Linux - 5.4.68 - x86_64 Configured with: ../configure --prefix=/usr --libdir=/usr/lib64 --mandir=/usr/man --infodir=/usr/info --enable-shared --enable-bootstrap --enable-languages=ada,brig,c,c++,d,fortran,go,lto,objc,obj-c++ --enable-threads=posix --enable-checking=release --enable-objc-gc --with-system-zlib --enable-libstdcxx-dual-abi --with-default-libstdcxx-abi=new --disable-libstdcxx-pch --disable-libunwind-exceptions --enable-__cxa_atexit --disable-libssp --enable-gnu-unique-object --enable-plugin --enable-lto --disable-install-libiberty --disable-werror --with-gnu-ld --with-isl --verbose --with-arch-directory=amd64 --disable-gtktest --enable-clocale=gnu --disable-multilib --target=x86_64-slackware-linux --build=x86_64-slackware-linux --host=x86_64-slackware-linux SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427009] New: cmake error: missing #include
https://bugs.kde.org/show_bug.cgi?id=427009 Bug ID: 427009 Summary: cmake error: missing #include Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Cmake fails to build: okular/CMakeFiles/CMakeTmp/src.cxx:6:10: error: ‘class Poppler::FormFieldChoice’ has no member named ‘choicesWithExportValues’ 6 | ffc->choicesWithExportValues(); STEPS TO REPRODUCE 1. invoke cmake from build folder ADDITIONAL INFORMATION Cmake test for Poppler fails because poppler-form.h, which is where choicesWithExportValues is defined, is not included in "Building CXX object CMakeFiles/cmTC_15f4c.dir/src.cxx.o." -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425467] New: Missing option to disable when mouse present
https://bugs.kde.org/show_bug.cgi?id=425467 Bug ID: 425467 Summary: Missing option to disable when mouse present Product: systemsettings Version: 5.19.4 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Recent update changed the kcm_touchpad menu by deleting the option to disable the touchpad when mouse present. I got bit when I used my laptop without my wireless mouse. KDE/Plasma is difficult to use sans pointer. I opened kcm_touchpad from Konsole kcmshell5 and managed to choose default, the only visible setting. Gone is my speech message proclaiming the mouse unplugged. STEPS TO REPRODUCE 1. kcm_touchpad 2. search for option to disable when mouse present OBSERVED RESULT Baffled, no more such option EXPECTED RESULT Choose option when setting up new profile SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.17.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 424971] New: Wacomtablet Stylus Tracking Relative Mode is now same as Absolute Mode
https://bugs.kde.org/show_bug.cgi?id=424971 Bug ID: 424971 Summary: Wacomtablet Stylus Tracking Relative Mode is now same as Absolute Mode Product: wacomtablet Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Version 3.3.0? Pen Relative Mode no longer works post-3.2.0. Since Windows10 has only Absolute Mode, maybe it was intentional? STEPS TO REPRODUCE 1. Set Wacom Intuos BT M (0378) Tablet, Stylus Tracking Mode to Relative Mode OBSERVED RESULT Stylus Tracking Mode remains in Absolute Mode. EXPECTED RESULT Stylus behaves as if Relative Mode works, just like it does in Version 3.2.0. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15 ADDITIONAL INFORMATION Kernel 5.4.45, 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 419858] Night Colour and Redshift require manual activation and display wrong status
https://bugs.kde.org/show_bug.cgi?id=419858 Henry Pfeil changed: What|Removed |Added CC||hpf...@psnarf.org --- Comment #5 from Henry Pfeil --- With geo-coordinates set to my gps manual location, kcm_nightcolor shows the correct start and end times, but night color is always on (noon). With Custom time, it works as advertised. For reasons I cannot explain, Current location and Detect location are 0, 0. What changed? This used to work as advertised. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 424622] New: kdelibs4support vs Qt6
https://bugs.kde.org/show_bug.cgi?id=424622 Bug ID: 424622 Summary: kdelibs4support vs Qt6 Product: kdesrc-build Version: Git Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: project metadata Assignee: mp...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- KDELibs4Support kdelibs4support/src/solid-networkstatus/kded/CMakeLists.txt relies upon cmake/Qt5DBus/Qt5DBusMacros.cmake to define qt5_add_dbus_adaptor. That file does not exist in Qt6. The remaining two files in cmake/Qt5DBUS do not define qt5_add_dbus_adaptor, so CMake throws an error: "Unknown CMake command "qt5_add_dbus_adaptor". Just a heads-up, kdelibs4support build will break when Qt releases the next major version in Dec 2020. Maybe you could simply copy the Macro definition from Qt5DBusMacros.cmake into CMakelists.txt? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423402] plasma-org.kde.plasma.desktop-appletsrc -wheel:Vertical org.kde.switchdesktop vs qt-5.15.0
https://bugs.kde.org/show_bug.cgi?id=423402 --- Comment #2 from Henry Pfeil --- Not really a duplicate, but a request for info. Now it is not my problem. If it were, I'd be looking at Qt. Qt5-5.14 didn't bother me because KDE worked using Qt5-5.13.2, however now with the latest KDE upgrade, I can't even start KDE because it looks for Qt5.15 in libQt5Core. Previous KDE, I could launch it with Qt5-5.13.2, switch desktops using scrollwheel from the desktop, not the panel; then reboot with Qt5-5.15 no other changes, scrollwheel from desktop no worka dis. Only change was the Qt version. That suggests to me that the problem is not with KDE, not a bug, but a change in functionality of a Qt library. I wanted to know which KDE component the switchdesktop was in to find out the Qt libraries to which it links. Now that this is kicked over to a stalled bug, I'm relieved of that analysis. I'm a retired systems analyst, gotta go check my tee time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423402] New: plasma-org.kde.plasma.desktop-appletsrc -wheel:Vertical org.kde.switchdesktop vs qt-5.15.0
https://bugs.kde.org/show_bug.cgi?id=423402 Bug ID: 423402 Summary: plasma-org.kde.plasma.desktop-appletsrc -wheel:Vertical org.kde.switchdesktop vs qt-5.15.0 Product: plasmashell Version: 5.19.1 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hpf...@psnarf.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Mouse wheel switchdesktop works only in pager since upgrade to qt-5.15.0. Used to click on empty desktop spot and scroll mouse wheel to switch, now nothing happens unless hovering over the pager in the status bar. Which package is responsible for handling desktop scroll wheel? I'd like to investigate how the Qt upgrade hosed that feature. Not a bug, just a request for information. STEPS TO REPRODUCE 1. Click on empty spot between windows on desktop 2. Scroll mouse wheel up/down 3. Nothing happens unless cursor is over the pager. OBSERVED RESULT Nothing happens EXPECTED RESULT Switch desktop forward or backward. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Kernel 5.4.48, 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 422457] New: kdelibs-4.14.38/dnssd/servicemodel.cpp compile error
https://bugs.kde.org/show_bug.cgi?id=422457 Bug ID: 422457 Summary: kdelibs-4.14.38/dnssd/servicemodel.cpp compile error Product: kde Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- Created attachment 129049 --> https://bugs.kde.org/attachment.cgi?id=129049=edit Patch fixes servicemodel compile error SUMMARY servicemodel.cpp:90:7: error: narrowing conversion of ‘DNSSD::ServiceModel::ServicePtrRole’ from ‘unsigned int’ to ‘int’ FIX: servicemodel.h:71 - change ServicePtrRole assignment from unsigned int to int ServicePtrRole = static_cast(0xA06519DE) STEPS TO REPRODUCE 1. g++ -o servicemodel.o servicemodel.cpp --> compile error 2. change ServicePtrRole assignment from unsigned int to int 3. kdelibs-4.14.38 builds with no errors SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.4.44 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION - See Attachment -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 422456] New: kptganttitemdelegate.cpp Qt5.15 compile error
https://bugs.kde.org/show_bug.cgi?id=422456 Bug ID: 422456 Summary: kptganttitemdelegate.cpp Qt5.15 compile error Product: calligraplan Version: 3.2.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dand...@get2net.dk Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY calligraplan-3.2.2/src/libs/ui/kptganttitemdelegate.cpp does not compile with Qt-5.15 Problem: missing header file Fix: add "#include " [might place it below #include ] Qt Version: 5.15.0 Compile errors: kptganttitemdelegate.cpp:550, 562, 583, 673, 693, 705, etc. ‘QPainterPath path’ has incomplete type and cannot be defined ‘QPainterPath p’ has initializer but incomplete type -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 422434] compile error: pressurecurvewidget.cpp missing include
https://bugs.kde.org/show_bug.cgi?id=422434 --- Comment #1 from Henry Pfeil --- Addendum: see also applications-extra/calligraplan-3.2.2/src/libs/ui/kptganttitemdelegate.cpp Same compile error, also fixed by adding #include kptganttitemdelegate.cpp:550, 562, 583, 673, 693, 705, etc. ‘QPainterPath path’ has incomplete type and cannot be defined ‘QPainterPath p’ has initializer but incomplete type -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 422434] New: compile error: pressurecurvewidget.cpp missing include
https://bugs.kde.org/show_bug.cgi?id=422434 Bug ID: 422434 Summary: compile error: pressurecurvewidget.cpp missing include Product: wacomtablet Version: 3.2.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY pressurecurvewidget.cpp missing "#include " wacomtablet-3.2.0/src/kcmodule/pressurecurvewidget.cpp STEPS TO REPRODUCE 1. g++ -o pressurecurvewidget pressurecurvewidget.cpp 2. add "#include " just after "#include " 3. no compile error OBSERVED RESULT Compile error: ‘QPainterPath curvePath’ has incomplete type and cannot be defined pressurecurvewidget.cpp:185 pressurecurvewidget.cpp:190 EXPECTED RESULT wacomtablet-3.2.0/src/kcmodule/pressurecurvewidget.cpp no compile error SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: n/a Qt Version: 5.15.0 ADDITIONAL INFORMATION Fix: add "#include " just after "#include " -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=419406 --- Comment #4 from Henry Pfeil --- I figured out how to launch systemsettings5 in konsole so I could capture the crash output. Hope this helps find and swat this bug. QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "/usr/lib64/qt5/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so" instead of kservice_desktop_to_json() in your CMake code. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 21862 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=419406
--- Comment #3 from Henry Pfeil ---
I copied the following from the tty used to launch kde.
/usr/share/kpackage/kcms/kcm_desktoptheme/contents/ui/main.qml
header: RowLayout { <—cannot anchor an item that isn't a parent or sibling.
Trying to show an empty dialog.
FormLayout.qml:112:21 unable to assign [undefined] to a double
QQmlEngine: setContextForObject() – object already has a context
`kcmshell5 kcm_kwin_virtualdesktops` works as advertised. Crash occurs every
time I click Virtual Desktops in System Settings.
Hope this helps find and swat this bug.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=419406 --- Comment #2 from Henry Pfeil --- Using kcmshell5 kcm_kwin_virtualdesktops, Cube Animation started working when I changed the Rotation Duration to Default. Still crashes from the System Settings module. No longer an issue for me, since I can right-click the Task Manager widget to Configure Virtual Desktops in addition to kcmshell5. Would Qt 5.13.2 have something to do with it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=419406 --- Comment #1 from Henry Pfeil --- `kcmshell5 kcm_kwin_virtualdesktops` works as advertised. /usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml seems to be at fault. Motivation for accessing kcm_kwin_virtualdesktops: Desktop Cube Animation stopped working. Konsole kcmshell5 reports qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to double Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "/usr/lib64/qt5/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so" instead of kservice_desktop_to_json() in your CMake code. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419406] New: System Settings - Workspace Behavior - Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=419406 Bug ID: 419406 Summary: System Settings - Workspace Behavior - Virtual Desktops Product: systemsettings Version: 5.18.3 Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- Application: systemsettings5 (5.18.3) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.4.28 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: In Workspace Behavior, choose Virtual Desktops, instant crash. It was working as advertised, kwinrc contains my 6 virtual desktops. Slackware-current upgrade introduced the crashes. Full system reinstall, created a new user, same crashes. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f048730de40 (LWP 8854))] Thread 29 (Thread 0x7f03e700 (LWP 9050)): #0 0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f047eba4d6b in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f047eba49d7 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #4 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f0409cae700 (LWP 9048)): #0 0x7f048bb51e9f in poll () at /lib64/libc.so.6 #1 0x7f04880a53ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f04880a550f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f048c25739b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f048c20292b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f048c03cc31 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f048dfdca05 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f048c03dc73 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #9 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f04165b5700 (LWP 8991)): #0 0x7f048bb51e9f in poll () at /lib64/libc.so.6 #1 0x7f04880a53ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f04880a5753 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7f040a5e66c6 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7f04880cd13d in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #6 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f04179ee700 (LWP 8990)): #0 0x7f048bb51e9f in poll () at /lib64/libc.so.6 #1 0x7f04880a53ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f04880a550f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f04880a5561 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f04880cd13d in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #6 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f040b6d3700 (LWP 8936)): #0 0x7f048bb4d86c in read () at /lib64/libc.so.6 #1 0x7f0415c959c1 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7f0415d16a2e in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f0415d17460 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f0415d17520 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f0415d24df6 in () at /usr/lib64/libpulse.so.0 #6 0x7f0415cbffc8 in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #8 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f0428965700 (LWP 8880)): #0 0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f047eba4d6b in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f047eba49d7 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #4 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f0429477700 (LWP 8879)): #0 0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f047eba4d6b in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f047eba49d7 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f048b60306b in start_thread () at /lib64/libpthread.so.0 #4 0x7f048bb5d72f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f042a078700 (LWP 8878)): #0
[kate] [Bug 418726] New: Caret does not match the beginning of a line
https://bugs.kde.org/show_bug.cgi?id=418726 Bug ID: 418726 Summary: Caret does not match the beginning of a line Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY When you enter '^' in the find/replace in the find ui QLineEdit widget, no matches are found. You should be able to insert a string at the beginning of a line. It works if you include the first character of the line, you can insert the replace string at the beginning of the line with the fist char appended to the replace, but with different first chars, that is not an option. STEPS TO REPRODUCE 1. Type a caret into the find linedit widget 2. Type a string in the replace linedit widget 3. OBSERVED RESULT No matches found. EXPECTED RESULT There should be a match at the beginning of each line in the file so you don't have to resort to `sed 's/^/somestring/'`. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Suggest replace QRegEx with QRegularExpression, as the Qt docs recommend. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418636] Search/Replace exceeds physical ram on 5mb file
https://bugs.kde.org/show_bug.cgi?id=418636 --- Comment #5 from Henry Pfeil --- >From https://doc/qt.io/qt-5/qregexp.html: Note: In Qt 5, the new QRegularExpression class provides a Perl compatible implementation of regular expressions and is recommended in place of QRegExp. How do you turn off search-while-typing? In a large file, such as slackware64/MANIFEST, a search for "braindump" halts at "brain" as it hunts for matches such as terminfo/s/superbrain or musicbrainz. I prefer to enter the complete search pattern, rather than wait for a long time while search hunts for useless substrings. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418636] Search/Replace exceeds physical ram on 5mb file
https://bugs.kde.org/show_bug.cgi?id=418636 Henry Pfeil changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Henry Pfeil --- I failed to set the case-sensitive button, the upper-case letters was a red-herring. Unable to find files with missing library dependencies, I'm trying to match everything but a filename (a line containing a colon) and the "not found" string. This is not a Kate problem. Please mark this as solved and move on. I got rid of the kernel addresses with the expression \(..\). I apologise for troubling you with this matter. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418636] Search/Replace exceeds physical ram on 5mb file
https://bugs.kde.org/show_bug.cgi?id=418636 --- Comment #2 from Henry Pfeil --- I noticed that the regular expression does not anchor the other expressions in the search criterion. The character class [a-f]+ matches every uppercase and lowercase abcdef in the file. The expression [0-9]+ finds zero matches. The expression [0-9a-f]+ matches every lowercase a..f preceded by a space. I'm going back to "O'Reilly Mastering Regular Expressions". My regex is wrong. Sorry for reporting my incorrect expressions as a bug. I thought [0-9] would match any number. Sorry about that. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418636] Search/Replace exceeds physical ram on 5mb file
https://bugs.kde.org/show_bug.cgi?id=418636 --- Comment #1 from Henry Pfeil --- There appears to be more regex expressions that induce this runaway memory allocation as the number of matches increases. "Processed 0 of x matches" where x increases beyond the number of lines in the file, eventually increasing beyond the number of characters in the file. This began as my feeble knowledge of regexes tried to match a space followed by, for example, (0x7ffc8f6a4000), without resorting to sed '/ \(0x[0-9]|[a-f]+\)/d' I thought if I just replaced the " (0x" with a linefeed, I could just sed '/00/d' and be done with it. Then I noticed that searching for "\/usr\/lib64" also invoked the runaway, only slower, so I could stop the search after Kate's memory footprint rose to 2gb. Could there be a loop in Kate's regex code that does not reach an end condition? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418636] New: Search/Replace exceeds physical ram on 5mb file
https://bugs.kde.org/show_bug.cgi?id=418636 Bug ID: 418636 Summary: Search/Replace exceeds physical ram on 5mb file Product: kate Version: 19.12.2 Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: major Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY Stop button unresponsive during search/replace on a 80K-line text file. KInfoCenter showed swap partition in use. Replace reports processing 27 million found, which should be only 5k. KSysGuard showed 18 threads, watched ram use increase from 10.1gb to 10.7gb, when I killed it. STEPS TO REPRODUCE 1. Capture ldd output into text file. 2. Search for " \(0x" regular expression 3. OBSERVED RESULT 0 of 27,095,586 processed, should be only 5,078. System briefly froze as the unused swap partition invoked. Physical ram allocation went from 4gb out of 14.7gb to 10gb+,leaving only 200kb unallocated. Kate unresponsive. Had to kill it as more processes went to swap and kate allocation increased EXPECTED RESULT Replace (0x with newline for sed deletion SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 64-bit (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Slackware post 14.2 -current Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 14.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410663] paste file into a folder containing a directory with identical name as file
https://bugs.kde.org/show_bug.cgi?id=410663 --- Comment #2 from Henry Pfeil --- Thank you for your kind explanation. My error arose from using "find . -type d" and "find . -type f". I thought that since Bash find could determine the difference between a directory and a file, so should dolphin. Thank you for closing my mistake as Resolved/Not A Bug. It took heroic restraint by not adding "You must be new!" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410663] New: paste file into a folder containing a directory with identical name as file
https://bugs.kde.org/show_bug.cgi?id=410663 Bug ID: 410663 Summary: paste file into a folder containing a directory with identical name as file Product: dolphin Version: 19.04.3 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- SUMMARY [Details View Mode] STEPS TO REPRODUCE 1. Extract a zip file, autodetect folder. 2. Folder created with unziped file name containing the unzipped file 3. Move the unzipped file from new folder to containing folder with the zip file. OBSERVED RESULT Subdirectory has same name as the unzipped file. Unable to move because Dolphin sees the directory as a file that exists with the same name and a newer date stamp, so you have to rename the file. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: X (available in About System) KDE Plasma Version: 5-16-3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Expect: able to move file into a directory containing a subdirectory with the identical name of the file. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 407737] OpenGL from KInfocenter
https://bugs.kde.org/show_bug.cgi?id=407737 --- Comment #1 from Henry Pfeil --- Please ignore and/or delete this Bug 407737. I cannot replicate the failure in KDE5. Obquote: "Sorry about that!" -Maxwell Smart, Secret Agent 86 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 407737] New: OpenGL from KInfocenter
https://bugs.kde.org/show_bug.cgi?id=407737 Bug ID: 407737 Summary: OpenGL from KInfocenter Product: kinfocenter Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: hpf...@psnarf.org Target Milestone: --- Application: kinfocenter (4.11.22) KDE Platform Version: 4.14.38 Qt Version: 4.8.7 Operating System: Linux 4.19.44 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Expand Graphical Information; click on OpenGL. Slackware-current: I will upgrade KDE4 to KDE5 to see if this goes away. The crash can be reproduced every time. -- Backtrace: Application: KDE Info Center (kinfocenter), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f33aa51d540 (LWP 7305))] Thread 15 (Thread 0x7f338bfff700 (LWP 7332)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f33887f8700 (LWP 7331)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f3390ff9700 (LWP 7330)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f33917fa700 (LWP 7329)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f3391ffb700 (LWP 7328)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f33927fc700 (LWP 7327)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f3392ffd700 (LWP 7326)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f33937fe700 (LWP 7325)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f3393fff700 (LWP 7324)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2 0x7f33a274e767 in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #3 0x7f33af4b719c in start_thread () at /lib64/libpthread.so.0 #4 0x7f33ae5264af in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f33a09b2700 (LWP 7323)): #0 0x7f33af4bd1b3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f33a274e9bb in () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so #2
