[k3b] [Bug 484737] Always add hidden files.
https://bugs.kde.org/show_bug.cgi?id=484737 --- Comment #3 from Gordon --- Thank you for implementing my suggestion, Leslie! I wish you the best of luck for creating good software. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486792] New: Allow renaming files without adding new files.
https://bugs.kde.org/show_bug.cgi?id=486792 Bug ID: 486792 Summary: Allow renaming files without adding new files. Classification: Applications Product: k3b Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: gordon...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 169326 --> https://bugs.kde.org/attachment.cgi?id=169326=edit "Please add files to your project first" K3b does not allow renaming or moving files from an imported session when adding new files. Error message: "Please add files to your project first" This should not be necessary for creating a new session for the sole purpose of renaming or moving files. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 486791] New: Remove missing files from failed burn
https://bugs.kde.org/show_bug.cgi?id=486791 Bug ID: 486791 Summary: Remove missing files from failed burn Classification: Applications Product: k3b Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: gordon...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- If a disc burn fails, the file listings contains files that do not exist on the disc. I refer to such files as "zombie files". There are several reasons a disc burn could fail: - You forget to increase the time until your computer goes into stand-by mode, also known as suspension, causing it to suspend automatically in the midst of a write. - You are using an external drive and it disconnects when you move a cable. - The computer crashes - The operating system closes tasks due to exhausted RAM (because many websites are bloated nowadays and need 10 times the memory they needed a decade ago) - Power outage - You accidentally hit the power switch of an extension cord. For these reasons, K3b needs to let the user remove those "zombie files" from the file list of an imported session when creating a new session. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 484737] New: Always add hidden files.
https://bugs.kde.org/show_bug.cgi?id=484737 Bug ID: 484737 Summary: Always add hidden files. Classification: Applications Product: k3b Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: gordon...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 167931 --> https://bugs.kde.org/attachment.cgi?id=167931=edit K3b asks user for confirmation each time before adding hidden files. I am largely satisfied with K3b, and it is currently the most sophisticated graphical disc authoring tool for Linux. However, the first burden I noticed on K3b in comparison to ImgBurn is the pop-up that reads: "Do you also want to add hidden files?" My answer: If I didn't want to add hidden files, I wouldn't have selected them to be added them to the project in the first place. This dialogue box is like asking "Do you also want to add video files?" - if I didn't want to, I would not be trying to add those files right now. This dialogue box serves no purpose. It is pointless. All it does is add an extra step whenever the user wants to add files. Please always add hidden files to the project without asking. Just like file managers copy everything inside a selected folder, K3b should add everything inside a folder to the project by default. Not only is this message annoying, but the undesirable option "do not add" is pre-selected and if I hit the space bar while that button is highlighted, I need to start over adding the files. On the first glance, "Do you also want to add hidden files?" might seem like a trivial step, but repetition is where the annoyance comes from. When adding thousands of files, the "Do you also want to add hidden files?" pop up usually appears with a delay. So the user has to wait until they can confirm that yes, they want to add hidden files. Anyone who frequently uses K3b will understand how annoying this dialogue is. It gets in the way and interrupts the workflow. I hope you will consider my suggestion to remove this annoyance, because any removed annoyance is progress. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481821] Write RW discs without needing exclusive access.
https://bugs.kde.org/show_bug.cgi?id=481821 --- Comment #1 from Gordon --- There is another problem: some software (such as forensics software and media players) might reserve access to all drives without doing anything, effectively blocking K3b from writing data to it. Therefore, please provide an option to write data without exclusive access. It would be much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 461191] BD-R LOGICAL BLOCK ADDRESS OUT OF RANGE: No space left on device
https://bugs.kde.org/show_bug.cgi?id=461191 --- Comment #2 from Gordon --- Created attachment 167478 --> https://bugs.kde.org/attachment.cgi?id=167478=edit K3b advanced settings I didn't realize I can add attachments to comments too. Here is a copy of the screenshot from the preceding comment I posted to Imgur, in case Imgur fails to keep it. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 461191] BD-R LOGICAL BLOCK ADDRESS OUT OF RANGE: No space left on device
https://bugs.kde.org/show_bug.cgi?id=461191 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #1 from Gordon --- Does it happen if you leave 300 MB free at the end? Try enabling "Allow overburning" in the advanced settings. (screenshot: https://imgur.com/a/MFHaAUQ ) It appears K3b does not calculate file system overhead when calculating the space. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481839] New: Show "recorder information" on DVD-R and DVD-RW
https://bugs.kde.org/show_bug.cgi?id=481839
Bug ID: 481839
Summary: Show "recorder information" on DVD-R and DVD-RW
Classification: Applications
Product: k3b
Version: 21.12.3
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Burning/Hardware
Assignee: k...@kde.org
Reporter: gordon...@web.de
CC: mich...@jabster.pl, tr...@kde.org
Target Milestone: ---
Created attachment 166105
--> https://bugs.kde.org/attachment.cgi?id=166105=edit
source:
https://forum.imgburn.com/topic/1741-cd-dvd-speed-recorder-information/?do=findComment=21077
Please show the drive type used to write a DVD-R and DVD-RW after right
clicking the optical drive name from the top left list, then "Media Info" on
the context menu.
It appears to be part of the DVD standard that optical drives write their model
name ("recorder information") on DVD-R and DVD-RW, but not their plus
counterparts, DVD+R and DVD+RW.
More information:
https://forum.imgburn.com/topic/1741-cd-dvd-speed-recorder-information/
On Windows, Nero DiscSpeed can show the drive type used to record a DVD-R and
DVD-RW.
While this feature is not essential to creating discs, it would still be a
helpful addition and it seems easy to implement, since all it does is reading
some text from the disc and putting it in a box.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 456063] BD-R was actually written on although 'simulation' was ticked
https://bugs.kde.org/show_bug.cgi?id=456063 --- Comment #2 from Gordon --- On an additional note, always perform test burns on write-once discs using data you would have burned anyway. Writing junk data on write-once discs for testing is wasteful. I did it once using Nero DiscSpeed's testing feature to see if Nero's warning is just a bluff, because I could not imagine something as "simulated writing" not to work. But it wrote actual data. What I found out is that it writes the drive model at the end on DVD plus discs in a way only DiscSpeed itself recognizes it. Because only DVD-R and -RW (not sure about -RAM) store the "recorder information" (drive model) in a dedicated section. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 456063] BD-R was actually written on although 'simulation' was ticked
https://bugs.kde.org/show_bug.cgi?id=456063 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #1 from Gordon --- As far as I know, a "simulation" feature is only a part of the standard on CD-R, CD-RW, DVD-R, DVD-RW, and HD-DVD. It seems not to be included DVD+R, DVD+RW, and Blu-ray discs. However, according to https://helpmanual.io:443/man1/cdvdcontrol/ , Plextor drives do support DVD+R writing simulation. One can assume this applies to DVD+RW as well. Nero has a warning that DVD+R writes might not be simulated. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 477929] can't burn
https://bugs.kde.org/show_bug.cgi?id=477929 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #1 from Gordon --- Could you please post a screenshot of the window that shows the error? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 429584] growisofs crashes @ 99%
https://bugs.kde.org/show_bug.cgi?id=429584 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #5 from Gordon --- "independent of file size" - Which file sizes have you tried? If the file size is around the maximum capacity of the disc, some miscalculation such as the size difference between GB (gigabytes) and GiB (gibibytes) might have caused the ISO file to overshoot the capacity of the disc. 1 GiB = 1,073,741,824 bytes 1 GB = 1,000,000,000 bytes -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 86303] on-the-fly ogg to mp3 conversion for data CDs
https://bugs.kde.org/show_bug.cgi?id=86303 Gordon changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 CC||gordon...@web.de --- Comment #6 from Gordon --- You can convert files to MP3 using ffmpeg right now, so this is not so important. Do you mean that the MP3 files created by K3b on-the-fly would replace or be added to the existing FLAC or OGG files? Perhaps the user gets to decide between those. If the former option is selected (keep both original and MP3), the user would have to be warned to leave more space free to avoid overshooting the free space on the disc. The remaining space can be guessed by calculating from the bitrate of the MP3 files to be created. If MP3 files with the target name already exist, K3b would leave those alone. As far as I remember, Nero 7 Essentials had a "jukebox CD" feature which left MP3 and WMA files unaffected while converting everything else to MP3. If this is implemented in K3b, it needs to be a separate mode like "new MP3 CD project" or "new Jukebox CD" project. Introducing this to the data disc mode (accessed through "New Data Project") could introduce unforeseen bugs for other uses such as archival. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481833] Please add UDF 2.60 support.
https://bugs.kde.org/show_bug.cgi?id=481833 --- Comment #1 from Gordon --- Correction: "4. Try to import from Windows." is obviously wrong. I meant "4. Try to import from K3b.". I could not find a way to edit the original post. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 474282] Please add support for disk spanning in K3b
https://bugs.kde.org/show_bug.cgi?id=474282 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #1 from Gordon --- Something you could try out is creating part archives using 7z. However, the limitation is that files need to be extracted before being readable. You can also split files into separate folders using a file manager. The Nemo file manager shows the selection size in real time at the bottom. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481835] Please allow removing files from an imported session.
https://bugs.kde.org/show_bug.cgi?id=481835 Gordon changed: What|Removed |Added Summary|Please allow removing files |Please allow removing files |from an imported project. |from an imported session. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481835] Please allow removing files from an imported project.
https://bugs.kde.org/show_bug.cgi?id=481835 Gordon changed: What|Removed |Added CC||gordon...@web.de -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481835] New: Please allow removing files from an imported project.
https://bugs.kde.org/show_bug.cgi?id=481835
Bug ID: 481835
Summary: Please allow removing files from an imported project.
Classification: Applications
Product: k3b
Version: 21.12.3
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Data Project
Assignee: k...@kde.org
Reporter: gordon...@web.de
CC: mich...@jabster.pl, tr...@kde.org
Target Milestone: ---
Created attachment 166102
--> https://bugs.kde.org/attachment.cgi?id=166102=edit
The "remove" option is greyed out on files and folders from an imported
project.
K3b is unable to remove any files from the file list of an imported session, so
please allow removing files from an imported project.
While this doesn't physically erase the file, it would still be helpful for
file management purposes such as eliminating unwanted duplicates and corrupted
files so they can be replaced. It would also allow removing empty folders after
the files inside have been moved into a different folder.
Windows tools such as Nero, ImgBurn, CDBurnerXP all have this ability for
decades.
STEPS TO REPRODUCE
1. Import an existing session
2. Right click on an existing file, or press the delete key ("del").
OBSERVED RESULT
The "remove" option is greyed out. When pressing the "del" key, no files are
removed.
EXPECTED RESULT
The "remove" option would be clickable and files from an existing session would
be removed.
SOFTWARE/OS VERSIONS
Linux Mint 21 (based on Ubuntu)
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 481833] New: Please add UDF 2.60 support.
https://bugs.kde.org/show_bug.cgi?id=481833 Bug ID: 481833 Summary: Please add UDF 2.60 support. Classification: Applications Product: k3b Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: gordon...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- It would be good if K3b could add files to UDF 2.60 Blu-rays that were created under Windows, and perhaps even initiate UDF 2.60 Blu-rays that Windows can add files to. STEPS TO REPRODUCE 1. Format an empty BD-R through Windows File Explorer or use the Windows command, with a changed drive letter if necessary: format /FS:UDF /R:2.60 /Q E:\ 2. Insert that BD-R into a Linux computer with K3b. 3. Inside K3b, click "New Data Project" 4. Try to import from Windows. OBSERVED RESULT The files are not imported. EXPECTED RESULT Import the files and let the user add new files. SOFTWARE/OS VERSIONS Linux Mint 21 (based on Ubuntu)) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 481821] New: Write RW discs without needing exclusive access.
https://bugs.kde.org/show_bug.cgi?id=481821 Bug ID: 481821 Summary: Write RW discs without needing exclusive access. Classification: Applications Product: k3b Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: gordon...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 166096 --> https://bugs.kde.org/attachment.cgi?id=166096=edit K3b requires exclusive access. Normally, it makes sense to get exclusive access to the optical drive before writing, since nothing must interfere with the writing process. However, when doing test burns with RW discs, the requirement for exclusive access can become an annoyance. Sometimes, I have to close Firefox entirely to unlock access to the drive, even though Firefox is not reading any data and not going to read any data in the one minute it will take to add some data, so nothing would happen during a test burn finished in one minute. If an error happens on RW discs, it is not critical, given that it can be rewritten. In the minute it takes to write some additional data, nothing will access the optical drive unless the user causes it deliberately. Please allow optionally burning without exclusive access so the user does not have close things until the error goes away. Thank you for understanding. STEPS TO REPRODUCE 1. Insert a *-RW or DVD+RW disc containing existing files into an optical drive. For example, a ZIP file. 2. Open that ZIP file inside `file-roller`. 3. Try writing new files to the disc using K3b. OBSERVED RESULT Error "unable to O_EXCL /dev/sr1" occurs, see attachment. EXPECTED RESULT Write data to the disc even if no exclusive access is possible. This should obviously not be the default behaviour but there needs to be an option for this. This is the Linux world. The end user should have the freedom and responsibility to decide about their system. This includes being able to immediately write data without having to get exclusive access first. SOFTWARE/OS VERSIONS Linux Mint 21 (based on Ubuntu) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 349943] Burning and verifying files adding up to more then 20GB errors/crashes at 99% burn completion Code 253 (no verify)
https://bugs.kde.org/show_bug.cgi?id=349943 Gordon changed: What|Removed |Added CC||gordon...@web.de --- Comment #3 from Gordon --- Very likely this happens because the Blu-ray ran out of space. While calculating the remaining space on the Blu-ray, K3b does not consider file system overhead. To avoid this problem, leave a margin of remaining space of about 1%. In my experience, mkisofs crashes if the disc runs out of space before all files were written. Otherwise, it finishes without error. Some optical drives support overburning, which might be able to squeeze out a few hundred megabytes at the end. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475329] Initiating slide show goes to full screen black (or background color) and does not display images.
https://bugs.kde.org/show_bug.cgi?id=475329 --- Comment #4 from Bruce GOrdon --- Yes. Same behavior with digikam 8.2.0 pre-release. -Bruce > On Oct 19, 2023, at 8:37 AM, bugzilla_nore...@kde.org wrote: > > https://bugs.kde.org/show_bug.cgi?id=475329 > > caulier.gil...@gmail.com changed: > > What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #3 from caulier.gil...@gmail.com --- > @Bruce, > > digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110 > frameworks. Installer is available at usual place : > > https://files.kde.org/digikam/ > > Can reproduce the problem with this version? > > Thanks in advance > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475329] Initiating slide show goes to full screen black (or background color) and does not display images.
https://bugs.kde.org/show_bug.cgi?id=475329 --- Comment #2 from Bruce GOrdon --- I see nothing at the bottom left. Only once, after exercising the two function keys did a different screen display briefly (I think it was a slide show preference screen) and there was a floatation ring (help) displayed bottom left. I haven't been able to reproduce that particular result though. Normally: F1 displays "About SlideShow Plugin" window. F2 displays "Rename" window. Once those two function keys have been exercised and I have hit "esc" to exit the slide show, I cannot re-initiate slide show. No response when pressing play. I'm running on a MacBook Air (13-inch, 2017), so no other screens. -Bruce > On Oct 7, 2023, at 12:55 PM, Maik Qualmann wrote: > > https://bugs.kde.org/show_bug.cgi?id=475329 > > --- Comment #1 from Maik Qualmann --- > You don't see anything, not even a toolbar at the bottom left? Is the help > displayed with F1 or the settings with F2? Do you use multiple screens? > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475329] New: Initiating slide show goes to full screen black (or background color) and does not display images.
https://bugs.kde.org/show_bug.cgi?id=475329 Bug ID: 475329 Summary: Initiating slide show goes to full screen black (or background color) and does not display images. Classification: Applications Product: digikam Version: 8.1.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: spam_me1time_and...@verizon.net Target Milestone: --- 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 digikam and from Thumbnails press paly on any image. 2. 3. OBSERVED RESULT Slide show opens to full screen but displays a blank screen (black or background color) but no images. EXPECTED RESULT Slide show should display images sequentially based upon timing entered. SOFTWARE/OS VERSIONS Windows: macOS: Monterey macOS 12.7 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.
[Akonadi] [Bug 473118] New: Crash when trying to adjust server names in IMAP
https://bugs.kde.org/show_bug.cgi?id=473118 Bug ID: 473118 Summary: Crash when trying to adjust server names in IMAP Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: j...@jdgwf.com CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.8 Frameworks Version: 5.108.0 Operating System: FreeBSD 13.2-RELEASE-p1 amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: Every time (this system is FreeBSD, but this bug occurs in Linux as well. The crash can be reproduced every time. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault (lldb) process attach --pid 1472 Process 1472 stopped * thread #1, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000842e7e1b8 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x842e7e1b8 <+8>: syscall 0x842e7e1ba <+10>: jb 0x842e7adb8 0x842e7e1c0 <+16>: retq 0x842e7e1c1: int3 thread #2, name = 'llvmpipe-0', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #3, name = 'llvmpipe-1', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #4, name = 'llvmpipe-2', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #5, name = 'llvmpipe-3', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #6, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #7, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #8, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #9, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #10, name = 'account:disk$0', stop reason = signal SIGSTOP frame #0: 0x000830dc3d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x830dc3d2c <+12>: retq 0x830dc3d2d <+13>: int3 0x830dc3d2e <+14>: int3 0x830dc3d2f <+15>: int3 thread #11, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000842e7dfda libc.so.7`__sys_read + 10 libc.so.7`__sys_read: -> 0x842e7dfda <+10>: jb 0x842e7adb8 0x842e7dfe0 <+16>: retq 0x842e7dfe1: int3 0x842e7dfe2: int3 thread #12, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000842e7df5a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x842e7df5a <+10>: jb 0x842e7adb8 0x842e7df60 <+16>: retq 0x842e7df61: int3 0x842e7df62: int3 thread #13, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000842e7df5a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x842e7df5a <+10>: jb 0x842e7adb8 0x842e7df60 <+16>: retq 0x842e7df61: int3 0x842e7df62: int3 thread #14, name =
[Akonadi] [Bug 471479] New: Application crashes as soon as an attempt is made to chage IMAP server
https://bugs.kde.org/show_bug.cgi?id=471479 Bug ID: 471479 Summary: Application crashes as soon as an attempt is made to chage IMAP server Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Microsoft Windows OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: j...@jdgwf.com CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: FreeBSD 13.2-RELEASE amd64 Windowing System: X11 Distribution (Platform): Microsoft Windows DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: Very unexpected crash. Setup works great until I add a "Genereic IMAP Server" I can change my username and outgoing server but as soon as I keydown the incoming server it crashes hard back to Kmail or (if initial startup) the desktop. The checkbox for Downloading all email is also safe for changing. In addition as soon as I "finish" the Assistant App crashes. The crash can be reproduced every time. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault (lldb) process attach --pid 1503 Process 1503 stopped * thread #1, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00084263e1b8 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x84263e1b8 <+8>: syscall 0x84263e1ba <+10>: jb 0x84263adb8 0x84263e1c0 <+16>: retq 0x84263e1c1: int3 thread #2, name = 'llvmpipe-0', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #3, name = 'llvmpipe-1', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #4, name = 'llvmpipe-2', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #5, name = 'llvmpipe-3', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #6, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #7, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #8, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #9, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #10, name = 'account:disk$0', stop reason = signal SIGSTOP frame #0: 0x00082fdd1d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x82fdd1d2c <+12>: retq 0x82fdd1d2d <+13>: int3 0x82fdd1d2e <+14>: int3 0x82fdd1d2f <+15>: int3 thread #11, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00082fdd95dd libthr.so.3`___lldb_unnamed_symbol619 + 237 libthr.so.3`___lldb_unnamed_symbol619: -> 0x82fdd95dd <+237>: leaq 0x38(%rbx), %rsi 0x82fdd95e1 <+241>: movq $0x0, 0x38(%rbx) 0x82fdd95e9 <+249>: movq %rdx, %rdi 0x82fdd95ec <+252>: shlq $0x4, %rdi thread #12, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x00084263df5a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x84263df5a <+10>: jb
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Gordon changed: What|Removed |Added CC||gor...@dickens.com --- Comment #57 from Gordon --- Please bring back the cube. Its one of the primary reasons why I use KDE Plasma 5 and I am disappointed without it. I guess that I will start looking at using the other desktop environments since this was a differential features for Plasma 5. Thanks for listening! Gordon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448479] kwallet-pam no longer works on Wayland
https://bugs.kde.org/show_bug.cgi?id=448479 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 --- Comment #26 from Gordon Lack --- (In reply to Lukáš Karas from comment #24) > Here is my proposed fix in Gwenview: > https://invent.kde.org/graphics/gwenview/-/merge_requests/125 Do we need a prod on the libexiv2 package as well to indicate that it needs an update to fix the cause of the crash? (The fix for gwenview to handle such crashes better is welcome, but not sufficient). I can't see any bug report with libexiv2 as the product. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 --- Comment #22 from Gordon Lack --- (In reply to Gordon Lack from comment #21) Seems to be related to how old the jpegs are. 2016 and earlier it crashes. 2017 and late its OK. Roughly. If I run gwenview on the command line for a failing one this is what I see reported: [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 --- Comment #21 from Gordon Lack --- Created attachment 144559 --> https://bugs.kde.org/attachment.cgi?id=144559=edit New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: Browsing through images with Dolphin. Select to open one in Gwenview. Crashes every time. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140466192913600) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140466192913600) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140466192913600, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fc0dafab476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc0daf917b7 in __GI_abort () at abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 Gordon Lack changed: What|Removed |Added CC||gordon.l...@dsl.pipex.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436442] [systemd startup] kwallet fails to open at login most of the time
https://bugs.kde.org/show_bug.cgi?id=436442 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439915] No feedback when dragging app from menu to panel when using touch
https://bugs.kde.org/show_bug.cgi?id=439915 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439917] Sometimes unable to rearrange pinned apps via touch
https://bugs.kde.org/show_bug.cgi?id=439917 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 439920] DragArea requires press-and-hold with a touchscreen, which is unintuitive and undiscoverable
https://bugs.kde.org/show_bug.cgi?id=439920 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 --- Comment #13 from Asher Gordon --- I realize it's been a little while, but is there any chance that this patch could be applied soon? I think it's a useful feature, and hardly likely to break compatibility or anyone's workflows, so I don't see any reason not to implement it. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 --- Comment #58 from Gordon Lack --- A workaround is to cancel all jobs, or at least the duplicates(?). See: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/comments/82 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387230] plasmashell information window starts minimized
https://bugs.kde.org/show_bug.cgi?id=387230 --- Comment #6 from Gordon Lack --- Similarly no longer an issue in Kubuntu 19.10 (plasma 5.16.5) -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 --- Comment #50 from Gordon Lack --- >>> Anyone knows what exactly happened on Cups side? I was wondering a similar thing. But rather what the "cups database" of past jobs looked like when it has multiple jobs with teh same id. When I went looking the info was only in /var/spool/cups and the job number was taken from the filename, so what does this look like when there are multiple ids? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] External hard disks should be spun down when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 Gordon Lack changed: What|Removed |Added CC||gordon.l...@dsl.pipex.com --- Comment #69 from Gordon Lack --- And powering off an external drive can be a real pain, as I then need to physically unplug and re-insert as device if I want to use it again. I may well want to unmount a device (as I don;t need it "now"), but leave it plugged in as I may need it later. So I've opened https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1827778 to re-add the option to *just* unmount a device. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 --- Comment #12 from Asher Gordon --- (In reply to Asher Gordon from comment #11) > I'm going to send a patch email to the mailing list so that it can hopefully > reach more developers. Actually never mind. Apparently, I can't send anything to the mailing list unless I'm subscribed (which I don't particularly want to do). :-( Asher -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 --- Comment #11 from Asher Gordon --- (In reply to Asher Gordon from comment #10) Hi, > I noticed that the valgrind-developers mailing list [1] has some patch > emails. Should I send my patch there also so that it can reach more > developers? I haven't received any reply on this. It looks like a lot of the emails are automatically generated from commits, but there are some patch emails which look like they were sent with git send-email. I'm going to send a patch email to the mailing list so that it can hopefully reach more developers. Asher -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 --- Comment #10 from Asher Gordon --- Hello, I noticed that the valgrind-developers mailing list [1] has some patch emails. Should I send my patch there also so that it can reach more developers? Thanks, Asher [1] https://sourceforge.net/p/valgrind/mailman/valgrind-developers/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 Asher Gordon changed: What|Removed |Added Attachment #122747|0 |1 is obsolete|| --- Comment #9 from Asher Gordon --- Created attachment 122828 --> https://bugs.kde.org/attachment.cgi?id=122828=edit Patch which fixes the bug (including documentation) Hello, I've updated the patch to include changes to the documentation (docs/xml/manual-core.xml). I hope this gets incorporated into Valgrind soon! :) Enjoy, Asher -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 --- Comment #7 from Asher Gordon --- Hello, I've written a patch to fix the bug. Please see the attachment (created with git format-patch). Apparently, I'm supposed to use Phabricator for patches. It's usage seems pretty complicated though, so I've just used an attachment. Is that OK? Thanks, Asher -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 93376] Suppressions directory
https://bugs.kde.org/show_bug.cgi?id=93376 Asher Gordon changed: What|Removed |Added CC||asd...@posteo.net --- Comment #6 from Asher Gordon --- Created attachment 122747 --> https://bugs.kde.org/attachment.cgi?id=122747=edit Patch which fixes the bug -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Gordon Lack changed: What|Removed |Added CC||gordon.l...@dsl.pipex.com --- Comment #35 from Gordon Lack --- FWIW. That comment about that multiple jobs with the same id shouldn't exist. I just decided to use the taskbar print-queue viewer (kde-print-queue) and selected "All Jobs". At that point it crashed (but only it - plasma was OK). But "lpstat -W completed" shows this - several multiple entries... [parent]: lpstat -W completed MFCJ4410DW-52 gml44108081408 Sun 01 Sep 2019 22:31:09 BST MFCJ4410DW-51 gml44103419136 Sun 01 Sep 2019 22:28:35 BST MFCJ4410DW-49 gml4410 667648 Sun 01 Sep 2019 22:20:14 BST MFCJ4410DW-48 gml4410 12908544 Sun 01 Sep 2019 22:18:02 BST MFCJ4410DW-47 gml4410 522240 Sun 01 Sep 2019 22:16:27 BST MFCJ4410DW-46 gml4410 667648 Sun 01 Sep 2019 22:15:51 BST MFCJ4410DW-45 gml4410 633856 Sun 01 Sep 2019 22:15:19 BST MFCJ4410DW-44 gml44103618816 Sun 01 Sep 2019 22:13:56 BST MFCJ4410DW-43 gml44103674112 Sun 01 Sep 2019 22:13:06 BST MFCJ4410DW-40 gml44101386496 Sun 01 Sep 2019 21:48:04 BST MFCJ4410DW-39 gml44101386496 Sun 01 Sep 2019 21:47:16 BST MFCJ4410DW-38 gml44101199104 Sun 01 Sep 2019 21:44:59 BST MFCJ4410DW-37 gml44101199104 Sun 01 Sep 2019 21:44:16 BST MFCJ4410DW-36 gml44101832960 Sun 01 Sep 2019 21:42:29 BST MFCJ4410DW-35 gml44105528576 Sun 01 Sep 2019 21:37:53 BST MFCJ4410DW-33 gml44101867776 Sun 01 Sep 2019 21:32:38 BST MFCJ4410DW-33 gml44101867776 Sun 01 Sep 2019 21:32:38 BST MFCJ4410DW-31 gml4410 104448 Tue 13 Aug 2019 12:52:43 BST MFCJ4410DW-31 gml4410 104448 Tue 13 Aug 2019 12:52:43 BST MFCJ4410DW-30 gml4410 256000 Tue 06 Aug 2019 08:09:15 BST MFCJ4410DW-30 gml4410 256000 Tue 06 Aug 2019 08:09:15 BST MFCJ4410DW-29 gml44105049344 Tue 06 Aug 2019 08:08:49 BST MFCJ4410DW-29 gml44105049344 Tue 06 Aug 2019 08:08:49 BST MFCJ4410DW-28 gml4410 131072 Mon 05 Aug 2019 03:10:27 BST MFCJ4410DW-28 gml4410 131072 Mon 05 Aug 2019 03:10:27 BST MFCJ4410DW-27 gml4410 437248 Sat 03 Aug 2019 05:52:51 BST MFCJ4410DW-27 gml4410 437248 Sat 03 Aug 2019 05:52:51 BST MFCJ4410DW-26 gml4410 178176 Fri 02 Aug 2019 00:24:39 BST MFCJ4410DW-26 gml4410 178176 Fri 02 Aug 2019 00:24:39 BST MFCJ4410DW-25 gml4410 312320 Sat 15 Jun 2019 08:55:55 BST MFCJ4410DW-25 gml4410 312320 Sat 15 Jun 2019 08:55:55 BST MFCJ4410DW-24 gml44101629184 Sun 09 Jun 2019 18:51:18 BST MFCJ4410DW-24 gml44101629184 Sun 09 Jun 2019 18:51:18 BST MFCJ4410DW-23 gml4410 211968 Sun 02 Jun 2019 11:11:43 BST MFCJ4410DW-23 gml4410 211968 Sun 02 Jun 2019 11:11:43 BST MFCJ4410DW-22 gml4410 521216 Sun 02 Jun 2019 11:05:51 BST MFCJ4410DW-22 gml4410 521216 Sun 02 Jun 2019 11:05:51 BST MFCJ4410DW-21 gml4410 32768 Wed 15 May 2019 12:17:19 BST MFCJ4410DW-21 gml4410 32768 Wed 15 May 2019 12:17:19 BST MFCJ4410DW-20 gml4410 294912 Wed 15 May 2019 10:58:47 BST MFCJ4410DW-20 gml4410 294912 Wed 15 May 2019 10:58:47 BST MFCJ4410DW-19 gml4410 250880 Wed 15 May 2019 10:58:16 BST MFCJ4410DW-19 gml4410 250880 Wed 15 May 2019 10:58:16 BST MFCJ4410DW-18 gml4410 81920 Tue 14 May 2019 10:25:39 BST MFCJ4410DW-18 gml4410 81920 Tue 14 May 2019 10:25:39 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-11 gml4410 137216 Wed 24 Apr 2019 18:56:44 BST MFCJ4410DW-11 gml4410 1372
[plasmashell] [Bug 387230] plasmashell information window starts minimized
https://bugs.kde.org/show_bug.cgi?id=387230 --- Comment #2 from Gordon Lack --- I have no solution. This still happens for me. [Kubuntu 18.10] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368389] No window decoration on windows created with SDL2
https://bugs.kde.org/show_bug.cgi?id=368389 Ryan C. Gordon changed: What|Removed |Added CC||iccu...@icculus.org --- Comment #3 from Ryan C. Gordon --- Just a quick follow up in case someone finds this bug via Google: SDL supports both the KDE-specific SSD protocol for legacy systems and xdg-decoration for future machines. This will be in SDL 2.0.10 and later. --ryan. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 356614] ksmserver crashes after unlocking screens
https://bugs.kde.org/show_bug.cgi?id=356614 Gordon Robert Speirs changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Gordon Robert Speirs --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! Unable to reproduce and has not been an issue for quite a while. This bug can likely be closed. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 276432] capture device order not obeyed
https://bugs.kde.org/show_bug.cgi?id=276432 Gordon Wells changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Gordon Wells --- My apologies I forgot about this. I haven't used KDE for quite some time now -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 394976] New: skippy cursor
https://bugs.kde.org/show_bug.cgi?id=394976 Bug ID: 394976 Summary: skippy cursor Product: kolourpaint Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: gord.cass...@yahoo.com Target Milestone: --- cursor has a mind of its own. Skipping to elsewhere on page random problem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392427] Cannot add collection on network drive
https://bugs.kde.org/show_bug.cgi?id=392427 P Gordon <p...@youpie.ch> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from P Gordon <p...@youpie.ch> --- this solved it. thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392427] New: Cannot add collection on network drive
https://bugs.kde.org/show_bug.cgi?id=392427 Bug ID: 392427 Summary: Cannot add collection on network drive Product: digikam Version: 5.9.0 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Setup-Collections Assignee: digikam-bugs-n...@kde.org Reporter: p...@youpie.ch Target Milestone: --- Created attachment 111688 --> https://bugs.kde.org/attachment.cgi?id=111688=edit printscreen macos add network collection On MacOS: When trying to add a collection from a network drive, only local drives appear, therefore impossible to add a network location. This behaviour was working properly until version 5.6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387230] plasmashell information window starts minimized
https://bugs.kde.org/show_bug.cgi?id=387230 Gordon Lack <gordon.l...@dsl.pipex.com> changed: What|Removed |Added CC||gordon.l...@dsl.pipex.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387230] New: plasmashell information window starts minimized
https://bugs.kde.org/show_bug.cgi?id=387230 Bug ID: 387230 Summary: plasmashell information window starts minimized Product: plasmashell Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: gordon.l...@dsl.pipex.com CC: plasma-b...@kde.org Target Milestone: 1.0 This is for the KDE in Kubuntu 17.10. I have the folder view set to display the Desktop folder. If I right-click on an Icon and select "Properties" or "Delete" then a window starts up (with the info or asking for confirmation). HOWEVER, this window starts minimized! That is unless I *already* have such a window open already (even a minimized one), in which case it opens onto the desktop (i.e. it's visible). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 382349] Installed mplayer from Discover, erased a search term, then Discover crashed and won't restart. Kubuntu 17.04
https://bugs.kde.org/show_bug.cgi?id=382349 --- Comment #3 from Gordon Bried <gbr...@gmail.com> --- Sorry, i don't have a backtrace. Thought it was creating 1 in the auto bug process, but i don't know where it would be filed. Discover mostly crashes after installing an app, when i enter a search term. How do i make a backtrace next time? Cheers On Jul 15, 2017 5:06 PM, "Aleix Pol" <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=382349 > > --- Comment #2 from Aleix Pol <aleix...@kde.org> --- > Hi, > Do you have a backtrace for which it's not starting again? > Or can you check if it's still running? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 382399] New: If I install an app from Discover, then put in a search term, the app crashes.
https://bugs.kde.org/show_bug.cgi?id=382399 Bug ID: 382399 Summary: If I install an app from Discover, then put in a search term, the app crashes. Product: Discover Version: 5.9.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: gbr...@gmail.com Target Milestone: --- If I install an app, then put in a search term, the app crashes. May have to do with video acceleration. Other elements crash too, but Discover crashes most consistantly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 382349] New: Installed mplayer from Discover, erased a search term, then Discover crashed and won't restart. Kubuntu 17.04
https://bugs.kde.org/show_bug.cgi?id=382349 Bug ID: 382349 Summary: Installed mplayer from Discover, erased a search term, then Discover crashed and won't restart. Kubuntu 17.04 Product: Discover Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: gbr...@gmail.com Target Milestone: --- Discover crashes often, just looking up app packages ordisplaying the info box for an app. This crash: I searced for a term found a list of software, installed one, and after finished, I erased the term in the search box and Discover disappeared immediately. Discover would not restart after that. PS. in auto bug report there is no opportunity to give info about what happened, so what good is that? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381803] New: Renaming an icon in system settings sometimes causes it to crash
https://bugs.kde.org/show_bug.cgi?id=381803 Bug ID: 381803 Summary: Renaming an icon in system settings sometimes causes it to crash Product: systemsettings Version: 5.8.6 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sillyas...@gmail.com Target Milestone: --- When you drag the folder icon that says "Drag me" in the touchpad settings pane of input devices, it sometimes crashes. I think it crashes more often if you rename the folder by double clicking it and typing a name--I assume you're not supposed to be able to rename it? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376493] New: Dolphin crashes after copying file to NTFS partition over NFS
https://bugs.kde.org/show_bug.cgi?id=376493 Bug ID: 376493 Summary: Dolphin crashes after copying file to NTFS partition over NFS Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: chicagosox...@gmail.com Target Milestone: --- Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-62-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: After copying a file from a POSIX-compliant NFS share to an NTFS partition exported over NFS (which doesn't support permissions), Dolphin attempts to change permissions on the new file and crashes. The expected behavior would be to show the error message that permissions could not be changed, but to remain open. While this is certainly not a typical situation that would be encountered very often, the uncaught exception causing the program to crash is very disruptive and should be handled differently. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8127b3e8c0 (LWP 4304))] Thread 11 (Thread 0x7f8113ca2700 (LWP 4526)): #0 0x7f81311a4a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f813115f929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f81311602bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f813116049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f81357757eb in QEventDispatcherGlib::processEvents (this=0x7f810c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f813571cb4a in QEventLoop::exec (this=this@entry=0x7f8113ca1d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f8135539834 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f813553e7be in QThreadPrivate::start (arg=0x12f7ce0) at thread/qthread_unix.cpp:331 #8 0x7f8131cec6ba in start_thread (arg=0x7f8113ca2700) at pthread_create.c:333 #9 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f8117626700 (LWP 4449)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f811ed41aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f811ed41907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f8131cec6ba in start_thread (arg=0x7f8117626700) at pthread_create.c:333 #4 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f8117e27700 (LWP 4448)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f811ed41aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f811ed41907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f8131cec6ba in start_thread (arg=0x7f8117e27700) at pthread_create.c:333 #4 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f8118628700 (LWP 4447)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f811ed41aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f811ed41907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f8131cec6ba in start_thread (arg=0x7f8118628700) at pthread_create.c:333 #4 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8118e29700 (LWP 4446)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f811ed41aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f811ed41907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f8131cec6ba in start_thread (arg=0x7f8118e29700) at pthread_create.c:333 #4 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f811962a700 (LWP 4445)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f811ed41aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f811ed41907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f8131cec6ba in start_thread (arg=0x7f811962a700) at pthread_create.c:333 #4 0x7f813a97882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f8119e2b700 (LWP )): #0 pthread_cond_wait@@GLIBC_2.3.2 () at
[plasmashell] [Bug 356090] Plasmashell crashes often
https://bugs.kde.org/show_bug.cgi?id=356090 --- Comment #5 from Gordon Dexter <kmputer...@gmail.com> --- Just copied and pasted this from DrKonqui Backtrace of the crash I experienced: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f258db378c0 (LWP 2796))] Thread 10 (Thread 0x7f24c3600700 (LWP 3050)): #0 0x7f258823ee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2584fd439c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f24bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f24c35ffcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f258892f8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f24c5ade7d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f258893484e in QThreadPrivate::start (arg=0x34e32a0) at thread/qthread_unix.cpp:331 #8 0x7f2587a216fa in start_thread (arg=0x7f24c3600700) at pthread_create.c:333 #9 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f25589fe700 (LWP 2898)): #0 0x7f258823a9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2585017740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd3e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f24d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f25589fdc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f258892f8a4 in QThread::exec (this=this@entry=0x2ac6ce0) at thread/qthread.cpp:503 #8 0x7f258bb5ded6 in QQuickPixmapReader::run (this=0x2ac6ce0) at util/qquickpixmapcache.cpp:817 #9 0x7f258893484e in QThreadPrivate::start (arg=0x2ac6ce0) at thread/qthread_unix.cpp:331 #10 0x7f2587a216fa in start_thread (arg=0x7f25589fe700) at pthread_create.c:333 #11 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f255b3ef700 (LWP 2873)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f258d57cbd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f258d57cc19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2587a216fa in start_thread (arg=0x7f255b3ef700) at pthread_create.c:333 #4 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f2560d3d700 (LWP 2868)): #0 0x7f2584fd13c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2584fd3cfa in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f25540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f2560d3cce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f258892f8a4 in QThread::exec (this=this@entry=0x28f3490) at thread/qthread.cpp:503 #7 0x7f258b1d73c5 in QQmlThreadPrivate::run (this=0x28f3490) at qml/ftw/qqmlthread.cpp:141 #8 0x7f258893484e in QThreadPrivate::start (arg=0x28f3490) at thread/qthread_unix.cpp:331 #9 0x7f2587a216fa in start_thread (arg=0x7f2560d3d700) at pthread_create.c:333 #10 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f2562bf6700 (LWP 2843)): #0 0x7f2584fd3dd1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f255c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f2562bf5ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f258892f8a4 in QThread::exec (this=this@entry=0x2824130) at thread/qthread.cpp:503 #6 0x7f258b1d73c5 in QQmlThreadPrivate::run (this=0x2824130) at qml/ftw/qqmlthread.cpp:141 #7 0x7f258893484e in QThreadPrivate::star
[plasmashell] [Bug 356090] Plasmashell crashes often
https://bugs.kde.org/show_bug.cgi?id=356090 Gordon Dexter <kmputer...@gmail.com> changed: What|Removed |Added CC||kmputer...@gmail.com --- Comment #4 from Gordon Dexter <kmputer...@gmail.com> --- This shouldn't be marked as a duplicate of that bug. It has nothing to do with POP or Akondai as far as I can tell. I'm getting crashes of plasma shell as much as several times an hour during normal use in my Proxmox KVM running Kubuntu 16.04 (just upgraded from 14.04) with qxl display driver. I've tried to attach the crash report to this bug but the crash reporter doesn't seem to want to let me because it's marked as a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 361008] "Require password after locking" setting is not respected in plasma 5.6
https://bugs.kde.org/show_bug.cgi?id=361008 Gordon <gor...@dickens.com> changed: What|Removed |Added CC||gor...@dickens.com --- Comment #10 from Gordon <gor...@dickens.com> --- I can confirm this bug in KDE Plasma 5.6.1 with Qt 5.6.0 on OpenSUSE Leap 42.1 where the time delay specified for "Require password after locking" is ignored and a password is required immediately after locking. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 360190] Time to ask for password after locking doesn't work
https://bugs.kde.org/show_bug.cgi?id=360190 Gordon <gor...@dickens.com> changed: What|Removed |Added CC||gor...@dickens.com --- Comment #6 from Gordon <gor...@dickens.com> --- I can confirm this bug in KDE Plasma 5.6.1 with Qt 5.6.0 on OpenSUSE Leap 42.1 where the time delay specified for "Require password after locking" is ignored and a password is required immediately after locking. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346858] Sliders for minimum/maximu width of panel is not visible
https://bugs.kde.org/show_bug.cgi?id=346858 Gordon <gor...@dickens.com> changed: What|Removed |Added CC||gor...@dickens.com --- Comment #5 from Gordon <gor...@dickens.com> --- @Ivan, any chance that you will fix this problem in the Slim Glow theme for Plasma 5 any time soon? I really like the Slim Glow Theme and I think that this is the only issue using it with Plasma 5. Thanks, Gordon Dickens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 356614] New: kdeinit5 crashes after unlocking screens
https://bugs.kde.org/show_bug.cgi?id=356614 Bug ID: 356614 Summary: kdeinit5 crashes after unlocking screens Product: frameworks-kinit Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: fa...@kde.org Reporter: g...@xhdev.com CC: kdelibs-b...@kde.org Created attachment 96040 --> https://bugs.kde.org/attachment.cgi?id=96040=edit kcrash data kinit5 crashed after the screens were unlocked. libxcb version is 1.11.1-1.1 (from opensuse tumbleweed packages) Qt version is 5.5.1 Unable to provide more information other than attachment due to the following bug: https://bugs.kde.org/show_bug.cgi?id=335932 I went through the journal as well as the X logs and there was no indications that anything went wrong. -- You are receiving this mail because: You are watching all bug changes.
