[neon] [Bug 489816] Update Error
https://bugs.kde.org/show_bug.cgi?id=489816 Peter Lettenbichler changed: What|Removed |Added CC||lorddreadfight@protonmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 489816] New: Update Error
https://bugs.kde.org/show_bug.cgi?id=489816 Bug ID: 489816 Summary: Update Error Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: lorddreadfi...@protonmail.com CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 171418 --> https://bugs.kde.org/attachment.cgi?id=171418=edit screenshot of the error message Package failed to install: Error while installing package: trying to overwrite /usr/bin/kdevplatform_shell_environment.sh, which is also in package kdevplatform513-libs 4 I tried to update to the newest version, it didn't go through and always throws me that error, I also can't install any applications since i got this error. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #67 from Peter Szabo --- I'm on Kubuntu 24.04 and i do not experience it anymore. $ spectacle --version spectacle 23.08.5 $ hostnamectl Static hostname: legion5 Chassis: laptop Operating System: Ubuntu 24.04 LTS Kernel: Linux 6.8.0-36-generic Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: Lenovo Legion 5 15IMH05 Firmware Version: EFCN59WW Firmware Date: Fri 2023-06-09 Firmware Age: 1y 3w 6d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 489192] Display error in thumbnail caption field
https://bugs.kde.org/show_bug.cgi?id=489192 --- Comment #3 from Peter --- Created attachment 170976 --> https://bugs.kde.org/attachment.cgi?id=170976=edit Sample image The text must be at least two lines long -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 489192] Display error in thumbnail caption field
https://bugs.kde.org/show_bug.cgi?id=489192 --- Comment #4 from Peter --- Created attachment 170978 --> https://bugs.kde.org/attachment.cgi?id=170978=edit The text must be at least two lines long -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 489192] Display error in thumbnail caption field
https://bugs.kde.org/show_bug.cgi?id=489192 Peter changed: What|Removed |Added Component|Thumbs-Album|Tags-Captions -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 489192] New: Display error in thumbnail caption field
https://bugs.kde.org/show_bug.cgi?id=489192 Bug ID: 489192 Summary: Display error in thumbnail caption field Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Album Assignee: digikam-bugs-n...@kde.org Reporter: benedekppe...@gmail.com Target Milestone: --- Created attachment 170970 --> https://bugs.kde.org/attachment.cgi?id=170970=edit Captions rows are shifted vertically Tested in: digiKam-8.4.0-20240623T100654-Qt6-x86-64.appimage Enabled: Settings -- Application Views Settings -- Show digiKam Captions Display error in thumbnail caption field: displayed rows are shifted vertically In previous digiKam versions (Qt5) this worked fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487562] Kicker button too wide with default icon
https://bugs.kde.org/show_bug.cgi?id=487562 --- Comment #7 from Peter --- (In reply to Nate Graham from comment #6) > *** Bug 488064 has been marked as a duplicate of this bug. *** 6.1 solved. Problem solved. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488492] Panel and windows constantly flicker when using a specific tinted color scheme and wallpaper
https://bugs.kde.org/show_bug.cgi?id=488492 Peter Fajdiga changed: What|Removed |Added Summary|Panel and windows |Panel and windows |constantly flicker when |constantly flicker when |using a specific tinted |using a specific tinted |color scheme|color scheme and wallpaper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488492] New: Panel and windows constantly flicker when using a specific tinted color scheme
https://bugs.kde.org/show_bug.cgi?id=488492 Bug ID: 488492 Summary: Panel and windows constantly flicker when using a specific tinted color scheme Classification: Plasma Product: plasmashell Version: 5.27.11 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: peter.fajd...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY This bug is related to the color scheme option "Tint all colors with accent color" and using accent color from current wallpaper (a very nice feature, btw). Panels and windows constantly flicker. This is the same kind of flicker that happens when changing the accent color, except that instead of a single flicker, it flickers continuously. This is a very finicky bug that happens only with a specific color scheme, wallpaper, and even display settings (details below). STEPS TO REPRODUCE 1. Set display resolution to 3440x1440. 2. Make sure the display is either the only display or is set as the primary display. 3. Create a new color scheme based on Breeze Light, but with the option "Tint all colors with accent color" checked. 4. Apply the new color scheme. 5. Select and apply the option "Use accent color: From current wallpaper". 6. Set the display's wallpaper to Fallen Leaf by Martin Klapetek (shipped with Plasma). 7. Make sure wallpaper Positioning is set to "Scaled and Cropped". Note: the order of the steps is not important. OBSERVED RESULT The panel and windows start to flicker continuously, as if constantly reapplying the color from the wallpaper. EXPECTED RESULT The panel and windows should flicker only once as the color from the wallpaper gets applied. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Graphics Platform: X11 ADDITIONAL INFORMATION 3440x1440 is the native resolution of my external display. If I use any other resolution (larger or smaller, even with the same aspect ratio), the bug isn't triggered. Refresh rate doesn't seem to matter. The bug also doesn't trigger when my laptop's built-in screen is set as the primary one, regardless of the resolution set there (it doesn't support 3440x1440, though). The accent color is picked from the primary monitor's wallpaper, and it seems that if that wallpaper is Fallen Leaf scaled and cropped to 3440x1440, the bug triggers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 --- Comment #31 from Peter --- (In reply to Peter from comment #26) > Following a fresh install of KDE Neon 6.0, I've set up a few panel widgets > to run Chrome apps, using the "--app=" argument. These seem to shade > correctly. I thought perhaps these were ignoring the Window Behaviour > system settings altogether, but if I set the Titlebar Action to "Minimse", > rather than "Shade", then they correctly minimise, as do other windows. > Very odd. Just to add to this, I've recently installed Edge. Now I have Chrome which shades and Edge (installed using Flatpak) which maximises. All other windows, including Octave which the only other application I installed using Flatpak, do nothing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488064] Application Launcher icon panel spacing seems to have increased
https://bugs.kde.org/show_bug.cgi?id=488064 --- Comment #2 from Peter --- (In reply to Nate Graham from comment #1) > This was my bad, sorry. It's fixed in Plasma 6.1. > > *** This bug has been marked as a duplicate of bug 487562 *** Thank you, as always. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488064] New: Application Launcher icon panel spacing seems to have increased
https://bugs.kde.org/show_bug.cgi?id=488064 Bug ID: 488064 Summary: Application Launcher icon panel spacing seems to have increased Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: 1.0 Created attachment 170162 --> https://bugs.kde.org/attachment.cgi?id=170162=edit Screenshot of upper panel. SUMMARY Since the 6.0.5 update, the Application Menu icon seems to occupy much more of the panel than previously. So much so, that the flexible-sized panel spacer is reduced to zero width. (In the attached screenshot, there is supposed to be a panel spacer between the MATLAB icon and the Advanced Radio Player, but instead there is excess padding associated with the Application Menu icon.) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file
https://bugs.kde.org/show_bug.cgi?id=487628 --- Comment #8 from Peter Kreussel --- (In reply to tagwerk19 from comment #7) > (In reply to tagwerk19 from comment #5) > > ... I'll have a go at installing paperwork and exploring ... > I've done that although I'm not sure how clean an installation I managed. I > failed at the pacstrap step on a fresh install. > > All the same, pulling an old installation off a backup and bringing it > up-to-date with Plasma 6, installing paperwork, sane, avahi and tesseract, > works (for me...) > > I'd say, not with a large collection of test documents and with a fair > number of crashes caught and reported by paperwork but Baloo indexing seems > OK. > > Not sure what to suggest. Thanks for all your troubles. What we found out is that baloo, perhaps only with qt 6.7.1, crashes on *some* png files. On my Arch Linux system... I have to disable indexing the paperwork directory. Would be nice to have the OCR'd text, which lies there in plain text files, in my KDE filesearch results, but that obviously does not work at the moment. I am not enough into C++/QT/KDE programming to go deeper into this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file
https://bugs.kde.org/show_bug.cgi?id=487628 --- Comment #6 from Peter Kreussel --- (In reply to tagwerk19 from comment #5) > (In reply to Peter Kreussel from comment #4) > > It must be a problem with the filename then? > I've not encountered issues with filenames like "paper.1.png". Not to say > that it is not possible, all sorts of things are possible 8-/ Such things are possible, especially for me. :-) > Are you indexing hidden files? (and content indexing?). Could it be that you > are getting a thumbnail generated and Baloo is crashing when trying to index > that... I do not have "index hidden files" option checked. > You can check whether Baloo has indexed the originals with > balooshow -x paper.png > balooshow -x paper.1.png > although maybe "balooshow6" rather than "balooshow" and also watch the > indexing process with "balooctl monitor" Balooshow say the file is not indexed: balooshow6 /home/peter/papers/20240603_1006_16/paper.1.png 2e18b8b2f2b7d27 791379239 48335755 /home/peter/papers/20240603_1006_16/paper.1.png: No index information found > If you are indexing hidden files/folders, it is sensible to exclude the > .cache and .local/shared/Trash folders as a follow-on step... I have not enabled indexing hidden files and folder. I have now purged my Baloo index an added "/home/peter/papers" as only indexed folder, which caused zillions of crashes... > I'll have a go at installing paperwork and exploring. Were you scanning or > importing something? I was scanning an A4 page. Strange enough, all that.. Peter -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file
https://bugs.kde.org/show_bug.cgi?id=487628 --- Comment #4 from Peter Kreussel --- > Do you mean that the file might have been "half written" (or something) and > Baloo scanned it and crashed - but when the scan was finished, it was OK, > according to pngcheck. That's what is suspected. But in fact, baloo crashes when I touch *one* of the two PNGs. They are called "paper.1.png" (the one causing crash) and "paper.1.edited.png" (no crash) and are identical in md5 sum, strangely enough. Full path: /home/peter/papers/20240527_1641_38/paper.1.png It must be a problem with the filename then? I have no problem attaching a file except that they are 13 M in size an I cannot attach them here. I tried an image hoster, but the files are not identical after download, so that is no use. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file
https://bugs.kde.org/show_bug.cgi?id=487628 --- Comment #2 from Peter Kreussel --- According to pngcheck, all pngs are "OK" *after* the scan. This has definitely not happened earlier. I changed nothing on my system except updating qt6 in Arch Linux. ( https://gitlab.archlinux.org/archlinux/packaging/packages/qt6-base/-/commits/main ). So probably not much KDE devs can do... Thanks for looking at this, though. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #11 from Peter --- FYI, this issue is resolved. I did not end up doing a full clean install, and best I can tell, all parts of my system, including icon visibility and updates with Discover are working perfectly. I did unpin and then replace several icons on task manager and that seems to have addressed all the messed up icons. On Friday, May 24th, 2024 at 4:08 AM, Peter H. Larkam wrote: > > > "No packages requiring newer versions." > > How about you close out the bug and spend zero more of your time & thought > about it. I will do a clean install with latest version of Neon and not use > the install script program that "broke" the system. I was able to get a clean > exe file for Windows apart from the company's packaged script for Linux. > Hopefully I can get all that to work fine just using stock wine and > PlayOnLinux. > > Sorry to have taken your time on a problem I caused that is not a true "bug." > Really appreciate all that you and others do to keep the system so elegant > and functional. > > Cheers. > > > On Thursday, May 23rd, 2024 at 11:32 PM, Harald Sitter > bugzilla_nore...@kde.org wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > > > --- Comment #9 from Harald Sitter sit...@kde.org --- > > > > Your system is in a broken state because of the wine stuff. Not sure what > > to do > > about it though, technically we should be telling you about this in the UI > > somehow but I am not sure which component fails to propagate the error. > > > > What happens when you run `pkcon update` > > > > -- > > You are receiving this mail because: > > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487628] New: Baloo file indexer crashes on addition of new file
https://bugs.kde.org/show_bug.cgi?id=487628
Bug ID: 487628
Summary: Baloo file indexer crashes on addition of new file
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.2.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: pri...@peter-kreussel.de
Target Milestone: ---
Application: baloo_file_extractor (6.2.0)
Qt Version: 6.7.1
Frameworks Version: 6.2.0
Operating System: Linux 6.9.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.5 [CoredumpBackend]
-- Information about the crash:
crashes every time i scan a file with paperwork, which adds a png, jpeg and
some text file.
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo-Dateiinfosammler (baloo_file_extractor), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/lib/kf6/baloo_file_extractor...
[New LWP 238987]
[New LWP 238988]
Downloading separate debug info for /usr/lib/libKF6FileMetaData.so.3...
Downloading separate debug info for /usr/lib/libKF6BalooEngine.so.6...
Downloading separate debug info for /usr/lib/liblmdb.so...
Downloading separate debug info for /usr/lib/libb2.so.1...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/kfilemetadata/kfilemetadata_pngextractor.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/kfilemetadata/kfilemetadata_exiv2extractor.so...
Downloading separate debug info for /usr/lib/libx265.so.199...
Downloading separate debug info for
/usr/lib/qt6/plugins/imageformats/libqpdf.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/imageformats/../../../libQt6Pdf.so.6...
Downloading separate debug info for
/usr/lib/qt6/plugins/imageformats/../../../libmng.so.2...
Downloading separate debug info for system-supplied DSO at 0x7c88e61b9000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/kf6/baloo_file_extractor'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7c88e12ac980 (LWP 238987))]
Cannot QML trace cores :(
Downloading source file
/usr/src/debug/baloo/baloo-6.2.0/src/file/extractor/main.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qtimerinfo_unix.cpp...
Downloading source file
/usr/src/debug/qt6-base/build/src/corelib/Core_autogen/7GB2EGQPHR/../../../../../qtbase/src/corelib/kernel/qsingleshottimer_p.h...
Downloading source file
/usr/src/debug/qt6-base/build/src/corelib/Core_autogen/7GB2EGQPHR/moc_qsingleshottimer_p.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h...
Downloading source file
/usr/src/debug/baloo/baloo-6.2.0/src/file/extractor/app.cpp...
Downloading source file
/usr/src/debug/kfilemetadata/kfilemetadata-6.2.0/src/extractors/pngextractor.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/gui/image/qimagereader.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/plugin/qfactoryloader.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/plugin/qlibrary.cpp...
Downloading source file
/usr/src/debug/qtpbfimageplugin/build6/moc_pbfplugin.cpp...
Downloading source file
/usr/src/debug/qtpbfimageplugin/build6/../QtPBFImagePlugin-3.0/src/pbfplugin.cpp...
Downloading source file
/usr/src/debug/qtpbfimageplugin/build6/../QtPBFImagePlugin-3.0/src/style.cpp...
Downloading source file
/usr/src/debug/qtpbfimageplugin/build6/../QtPBFImagePlugin-3.0/src/font.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/gui/text/qfontdatabase.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp...
Downloading source file
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qglobal.cpp...
Downloading source file /usr/src/debug/glibc/glibc/stdlib/abort.c...
Downloading source file
/usr/src/debug/glibc/glibc/signal/../sysdeps/posix/raise.c...
[Current thread is 1 (Thread 0x7c88e12ac980 (LWP 238987))]
Thread 2 (Thread 0x7c48e08006c0 (LWP 238988)):
#0 0x7c88e531c39d in __GI___poll (fds=0x55b64f56b260, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7c88e3f768fd in g_main_context_poll_unlocked (priority=2147483647,
context=0x7c48d8000c60, timeout=, fds=0x55b64f56b260, n_fds=2)
at ../glib/glib/gmain.c:4521
#2 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7c48d8000c60, block=block@entry=1,
dispatch=dispatch@entry=1, se
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #10 from Peter --- "No packages requiring newer versions." How about you close out the bug and spend zero more of your time & thought about it. I will do a clean install with latest version of Neon and not use the install script program that "broke" the system. I was able to get a clean exe file for Windows apart from the company's packaged script for Linux. Hopefully I can get all that to work fine just using stock wine and PlayOnLinux. Sorry to have taken your time on a problem I caused that is not a true "bug." Really appreciate all that you and others do to keep the system so elegant and functional. Cheers. On Thursday, May 23rd, 2024 at 11:32 PM, Harald Sitter wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > --- Comment #9 from Harald Sitter sit...@kde.org --- > > Your system is in a broken state because of the wine stuff. Not sure what to > do > about it though, technically we should be telling you about this in the UI > somehow but I am not sure which component fails to propagate the error. > > What happens when you run `pkcon update` > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #8 from Peter --- Is this bug unique to me? If yes, I can do a clean Neon Install and we not spend any of your time. I haven't been able to determine of anyone else reported this issue. Marked "waitingforinfo" and I've provided output per requests. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487400] New: Outage? Seems only installed apps are viewable. No other applications are available. "Nothing found" All Applications - 0 items
https://bugs.kde.org/show_bug.cgi?id=487400 Bug ID: 487400 Summary: Outage? Seems only installed apps are viewable. No other applications are available. "Nothing found" All Applications - 0 items Classification: Applications Product: Discover Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: kde.x8...@passmail.net CC: aleix...@kde.org Target Milestone: --- Outage at source maybe? Seems only installed apps are viewable. No other applications are available. "Nothing found" All Applications - 0 items *** 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 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #7 from Peter --- Here's the rest of the output. Nothing truncated although I just copied after prior email paste with a couple of lines of overlap. -- After this operation, 636 MB disk space will be freed. Do you want to continue? [Y/n] Y Get:1 http://archive.neon.kde.org/user jammy/main amd64 kf6-attica amd64 6.2.0-0xneon+22.04+jammy+release+build6 [187 kB] Get:2 http://archive.neon.kde.org/user jammy/main amd64 kf6-kconfig-dev amd64 6.2.0-0xneon+22.04+jammy+release+build6 [879 kB] Get:3 http://archive.neon.kde.org/user jammy/main amd64 kf6-kconfig amd64 6.2.0-0xneon+22.04+jammy+release+build6 [343 kB] Get:4 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcoreaddons amd64 6.2.0-0xneon+22.04+jammy+release+build5 [420 kB] Get:5 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcoreaddons-dev amd64 6.2.0-0xneon+22.04+jammy+release+build5 [744 kB] Get:6 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcrash amd64 6.2.0-0xneon+22.04+jammy+release+build6 [21.3 kB] Get:7 http://archive.neon.kde.org/user jammy/main amd64 kf6-kdbusaddons amd64 6.2.0-0xneon+22.04+jammy+release+build5 [65.7 kB] Get:8 http://archive.neon.kde.org/user jammy/main amd64 kf6-karchive-dev amd64 6.2.0-0xneon+22.04+jammy+release+build5 [255 kB] Get:9 http://archive.neon.kde.org/user jammy/main amd64 kf6-karchive amd64 6.2.0-0xneon+22.04+jammy+release+build5 [152 kB] Get:10 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcodecs amd64 6.2.0-0xneon+22.04+jammy+release+build5 [139 kB] Get:11 http://archive.neon.kde.org/user jammy/main amd64 kf6-ki18n amd64 6.2.0-0xneon+22.04+jammy+release+build7 [1,493 kB] Get:12 http://archive.neon.kde.org/user jammy/main amd64 kf6-kfilemetadata amd64 6.2.0-0xneon+22.04+jammy+release+build17 [232 kB] Get:13 http://archive.neon.kde.org/user jammy/main amd64 kf6-kidletime amd64 6.2.0-0xneon+22.04+jammy+release+build5 [61.0 kB] Get:14 http://archive.neon.kde.org/user jammy/main amd64 kf6-kwindowsystem-dev amd64 6.2.0-0xneon+22.04+jammy+release+build8 [552 kB] Get:15 http://archive.neon.kde.org/user jammy/main amd64 kf6-kwindowsystem amd64 6.2.0-0xneon+22.04+jammy+release+build8 [195 kB] Get:16 http://archive.neon.kde.org/user jammy/main amd64 kf6-kauth amd64 6.2.0-0xneon+22.04+jammy+release+build6 [89.6 kB] Get:17 http://archive.neon.kde.org/user jammy/main amd64 kf6-kguiaddons amd64 6.2.0-0xneon+22.04+jammy+release+build8 [110 kB] Get:18 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcolorscheme amd64 6.2.0-0xneon+22.04+jammy+release+build6 [34.7 kB] Get:19 http://archive.neon.kde.org/user jammy/main amd64 kf6-kwidgetsaddons amd64 6.2.0-0xneon+22.04+jammy+release+build5 [1,659 kB] Get:20 http://archive.neon.kde.org/user jammy/main amd64 kf6-kconfigwidgets amd64 6.2.0-0xneon+22.04+jammy+release+build9 [298 kB] Get:21 http://archive.neon.kde.org/user jammy/main amd64 kf6-kbookmarks amd64 6.2.0-0xneon+22.04+jammy+release+build8 [113 kB] Get:22 http://archive.neon.kde.org/user jammy/main amd64 kf6-kcompletion amd64 6.2.0-0xneon+22.04+jammy+release+build6 [97.1 kB] Get:23 http://archive.neon.kde.org/user jammy/main amd64 kf6-kdoctools amd64 6.2.0-0xneon+22.04+jammy+release+build6 [433 kB] Get:24 http://archive.neon.kde.org/user jammy/main amd64 kf6-breeze-icon-theme amd64 6.2.0-0xneon+22.04+jammy+release+build9 [4,955 kB] Get:25 http://archive.neon.kde.org/user jammy/main amd64 kf6-kiconthemes amd64 6.2.0-0xneon+22.04+jammy+release+build12 [150 kB] Get:26 http://archive.neon.kde.org/user jammy/main amd64 kf6-kitemviews amd64 6.2.0-0xneon+22.04+jammy+release+build5 [113 kB] Get:27 http://archive.neon.kde.org/user jammy/main amd64 kf6-knotifications amd64 6.2.0-0xneon+22.04+jammy+release+build7 [112 kB] Get:28 http://archive.neon.kde.org/user jammy/main amd64 kf6-kjobwidgets amd64 6.2.0-0xneon+22.04+jammy+release+build7 [112 kB] Get:29 http://archive.neon.kde.org/user jammy/main amd64 kf6-kservice amd64 6.2.0-0xneon+22.04+jammy+release+build9 [200 kB] Get:30 http://archive.neon.kde.org/user jammy/main amd64 kf6-solid amd64 6.2.0-0xneon+22.04+jammy+release+build11 [416 kB] Get:31 http://archive.neon.kde.org/user jammy/main amd64 kf6-kio amd64 6.2.0-0xneon+22.04+jammy+release+build15 [3,400 kB] Get:32 http://archive.neon.kde.org/user jammy/main amd64 kf6-baloo amd64 6.2.0-0xneon+22.04+jammy+release+build18 [533 kB] Get:33 http://archive.neon.kde.org/user jammy/main amd64 kf6-bluez-qt amd64 6.2.0-0xneon+22.04+jammy+release+build5 [294 kB] Get:34 http://archive.neon.kde.org/user jammy/main amd64 kf6-extra-cmake-modules amd64 6.2.0-0xneon+22.04+jammy+release+build7 [381 kB] Get:35 http://archive.neon.kde.org/user jammy/main amd64 kf6-kpackage-dev amd64 6.2.0-0xneon+22.04+jammy+release+build8 [160 kB] Get:36 http://archive.neon.kde.org/user jammy/main amd64 kf6-kpackage amd64 6.2.0-0xneon+22.04+jammy+release+build8 [150 kB] Get:37 http://archive.neon.kde.org/user jammy/main amd64 kf6-syndication amd64 6.2.0
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #6 from Peter --- Here's the beginning of the process - in case it gets lost by exceeding Konsole window capacity after I say yes and run the process... :~$ sudo apt dist-upgrade [sudo] password for phl: Sorry, try again. [sudo] password for phl: Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libpoppler-glib8:amd64 < 22.02.0-2ubuntu0.3 | 24.02.0-0xneon+22.04+jammy+release+build30 @ii umH Ib > Broken libpoppler-glib8:amd64 Depends on libpoppler118:amd64 < 22.02.0-2ubuntu0.3 -> 22.02.0-2ubuntu0.4 @ii umU > (= 22.02.0-2ubuntu0.3) Considering libpoppler118:amd64 10 as a solution to libpoppler-glib8:amd64 5 Removing libpoppler-glib8:amd64 rather than change libpoppler118:amd64 Investigating (0) libsane1:amd64 < 1.1.1-5 @ii mK NPb Ib > Broken libsane1:amd64 Depends on libpoppler-glib8:amd64 < 22.02.0-2ubuntu0.3 | 24.02.0-0xneon+22.04+jammy+release+build30 @ii umR > (>= 0.18.0) Considering libpoppler-glib8:amd64 5 as a solution to libsane1:amd64 5 Removing libsane1:amd64 rather than change libpoppler-glib8:amd64 Investigating (0) libksanecore1:amd64 < 24.02.2-0xneon+22.04+jammy+release+build4 @ii mK Ib > Broken libksanecore1:amd64 Depends on libsane1:amd64 < 1.1.1-5 @ii mR NPb > (>= 1.0.27) Considering libsane1:amd64 5 as a solution to libksanecore1:amd64 4 Removing libksanecore1:amd64 rather than change libsane1:amd64 Investigating (0) libpoppler-glib8:i386 < 22.02.0-2ubuntu0.3 | 22.02.0-2ubuntu0.4 @ii umH Ib > Broken libpoppler-glib8:i386 Depends on libpoppler118:i386 < 22.02.0-2ubuntu0.3 -> 22.02.0-2ubuntu0.4 @ii umU > (= 22.02.0-2ubuntu0.3) Considering libpoppler118:i386 1 as a solution to libpoppler-glib8:i386 2 Added libpoppler118:i386 to the remove list Fixing libpoppler-glib8:i386 via keep of libpoppler118:i386 Investigating (0) tracker-extract:amd64 < 3.3.3-0ubuntu0.20.04.3 @ii gK Ib > Broken tracker-extract:amd64 Depends on libpoppler-glib8:amd64 < 22.02.0-2ubuntu0.3 | 24.02.0-0xneon+22.04+jammy+release+build30 @ii umR > (>= 0.18.0) Considering libpoppler-glib8:amd64 5 as a solution to tracker-extract:amd64 2 Removing tracker-extract:amd64 rather than change libpoppler-glib8:amd64 Try to Re-Instate (0) libpoppler118:i386 Re-Instated libpoppler118:i386 (5 vs 4) Investigating (1) hplip:amd64 < 3.21.12+dfsg0-1 @ii mK NPb Ib > Broken hplip:amd64 Depends on libsane1:amd64 < 1.1.1-5 @ii mR NPb > (>= 1.0.27) Considering libsane1:amd64 5 as a solution to hplip:amd64 104 Added libsane1:amd64 to the remove list Fixing hplip:amd64 via keep of libsane1:amd64 Investigating (1) libkf5sane6:amd64 < 24.02.2-0xneon+22.04+jammy+release+build6 @ii mK Ib > Broken libkf5sane6:amd64 Depends on libksanecore1:amd64 < 24.02.2-0xneon+22.04+jammy+release+build4 @ii mR > (>= 24.02.2) Considering libksanecore1:amd64 4 as a solution to libkf5sane6:amd64 7 Added libksanecore1:amd64 to the remove list Fixing libkf5sane6:amd64 via keep of libksanecore1:amd64 Investigating (1) libsane1:amd64 < 1.1.1-5 @ii mK NPb Ib > Broken libsane1:amd64 Depends on libpoppler-glib8:amd64 < 22.02.0-2ubuntu0.3 | 24.02.0-0xneon+22.04+jammy+release+build30 @ii umR > (>= 0.18.0) Considering libpoppler-glib8:amd64 5 as a solution to libsane1:amd64 5 Removing libsane1:amd64 rather than change libpoppler-glib8:amd64 Investigating (1) libksanecore1:amd64 < 24.02.2-0xneon+22.04+jammy+release+build4 @ii mK Ib > Broken libksanecore1:amd64 Depends on libsane1:amd64 < 1.1.1-5 @ii mR NPb > (>= 1.0.27) Considering libsane1:amd64 5 as a solution to libksanecore1:amd64 4 Removing libksanecore1:amd64 rather than change libsane1:amd64 Investigating (1) tracker-miner-fs:amd64 < 3.3.3-0ubuntu0.20.04.3 @ii gK Ib > Broken tracker-miner-fs:amd64 Depends on tracker-extract:amd64 < 3.3.3-0ubuntu0.20.04.3 @ii gR > (= 3.3.3-0ubuntu0.20.04.3) Considering tracker-extract:amd64 2 as a solution to tracker-miner-fs:amd64 3 Added tracker-extract:amd64 to the remove list Fixing tracker-miner-fs:amd64 via keep of tracker-extract:amd64 Investigating (1) libpoppler-glib8:i386 < 22.02.0-2ubuntu0.3 | 22.02.0-2ubuntu0.4 @ii umH Ib > Broken libpoppler-glib8:i386 Depends on libpoppler118:i386 < 22.02.0-2ubuntu0.3 -> 22.02.0-2ubuntu0.4 @ii umU > (= 22.02.0-2ubuntu0.3) Considering libpoppler118:i386 1 as a solution to libpoppler-glib8:i386 2 Added libpoppler118:i386 to the remove list Fixing libpoppler-glib8:i386 via keep of libpoppler118:i386 Investigating (1) tracker-extract:amd64 < 3.3.3-0ubuntu0.20.04.3 @ii gK Ib > Broken tracker-extract:amd64 Depends on libpoppler-glib8:amd64 < 22.02.0-2ubuntu0.3 | 24.02.0-0xneon+22.04+jammy+release+build30
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #5 from Peter --- Ran command without sudo initially and got a msg saying "Are you root" Ran with sudo. Seemed to remove and install several items. Process took at least a few minutes. I did copy the terminal output initially but didn't paste it into an email. Checked Discover icon and there were a couple of plasma items and system packages available. Selected all and let it reboot. The blue dot remains. I think the list of updates is still the same but I haven't checked against the prior output. Here's current: phl@2011iMac:~$ sudo apt list --upgradable [sudo] password for phl: Listing... Done libpoppler-glib8/jammy 24.02.0-0xneon+22.04+jammy+release+build30 amd64 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler-glib8/jammy-updates 22.02.0-2ubuntu0.4 i386 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler118/jammy-updates 22.02.0-2ubuntu0.4 amd64 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler118/jammy-updates 22.02.0-2ubuntu0.4 i386 [upgradable from: 22.02.0-2ubuntu0.3] -- Is there a command line that will tell whether my version of wine is holding things up? I reinstalled the MetaTrader 4 app via its install script yesterday and it booted fine with PlayOnLinux front end to Wine. After doing the updates this morning per your suggestions, that app generated a crash report which I submitted and mentioned Harald Sitter by name to flag it as potentially relevant. I regret taking your time on this since it may only affect me, and I don't like to divert kde resources for a one-off issue if that's what we're dealing with. But I so much appreciate your expertise and the opportunity to improve my linux competence as you suggest things to try. I will run apt dist upgrade again and capture the output. It looked as though the output may have exceeded a Konsole window capacity but I'll capture all that I can in the output window. Cheers On Wednesday, May 22nd, 2024 at 2:18 AM, Harald Sitter wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > --- Comment #4 from Harald Sitter sit...@kde.org --- > > What happens when you run `apt dist-upgrade` > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #4 from Peter --- I ran kmail from a terminal, and got the messages, QAbstractAnimation::pause: Cannot pause a stopped animation org.kde.pim.kmail: setFcc: collection invalid "" Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Is this significant? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #3 from Peter --- phl@2011iMac:~$ apt list --upgradable Listing... Done libpoppler-glib8/jammy 24.02.0-0xneon+22.04+jammy+release+build30 amd64 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler-glib8/jammy-updates 22.02.0-2ubuntu0.4 i386 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler118/jammy-updates 22.02.0-2ubuntu0.4 amd64 [upgradable from: 22.02.0-2ubuntu0.3] libpoppler118/jammy-updates 22.02.0-2ubuntu0.4 i386 [upgradable from: 22.02.0-2ubuntu0.3] phl@2011iMac:~$ On Tuesday, May 21st, 2024 at 6:53 AM, Harald Sitter wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > Harald Sitter sit...@kde.org changed: > > > What |Removed |Added > > CC| |sit...@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Harald Sitter sit...@kde.org --- > > It's possible that the wine issue is somehow causing packages to hold back. > > What does `apt list --upgradable` report when the situation happens? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #2 from Peter --- Hey Harald - where do I find 'apt list --upgradable' ? Discover shows various packages to upgrade - sometimes just "up to date" and sometimes a list. There are no packages that show up in that list that remain after an install. I always click the box to do an immediate reboot and think this machine is on manual software updates. I regret i did not capture the message that showed up on the wine update. i'll try deleting and reinstalling that package to see if the situation resolves itself. If there is somewhere else I need to look or a command line query to get the info you are looking for in 'apt list --upgradable' - please let me know. Sorry you're dealing with someone with novice linux background... Cheers Peter On Tuesday, May 21st, 2024 at 6:53 AM, Harald Sitter wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > Harald Sitter sit...@kde.org changed: > > > What |Removed |Added > > CC| |sit...@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Harald Sitter sit...@kde.org --- > > It's possible that the wine issue is somehow causing packages to hold back. > > What does `apt list --upgradable` report when the situation happens? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] New: Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that
https://bugs.kde.org/show_bug.cgi?id=487150 Bug ID: 487150 Summary: Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updates are available. Classification: Applications Product: Discover Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: kde.kindling...@passmail.net CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Persistent symptom - no specific action to initiate it. 2. Symptom does not disappear / fix itself upon reboot or logout / login. 3. [I think this is low stakes but wanted you to know about it...] 4. Unsure if it is possibly related to a prior recommended installation of a wine update package I did about 10 days ago?? Do not recall if I first observed symptom after that installation, but it did break some previously working windows based software. I have yet to untangle the wine package issue but this report is not to address that issue. OBSERVED RESULT Updates available icon shows blue dot and sometimes I get a message that updates are available. When I install updates (and usually reboot automatically) the blue dot showing non-critical updates available stays on the icon. When I launch Discover to check for updates, I get System is Up to Date message and no listed available updates. So issue is just the discrepancy between "up to date" and the icon / banner alerting me that there ARE updates available EXPECTED RESULT After installation of new software, the blue dot on the icon should disappear as it normally had... SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-2600 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD BARTS Manufacturer: Apple Inc. Product Name: iMac12,2 System Version: 1.0 ADDITIONAL INFORMATION I consider this very low importance compared with other issues and I am super grateful for all you do to keep KDE software running beautifully over many upgrades and updates... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 --- Comment #32 from Peter --- (In reply to Robert Riemann from comment #31) > Created attachment 169482 [details] > screenshot of html reply composer of kmail 6.0.2 This is the problem I get, too. It's one of the more worrying problems, as it's 'outward-facing', i.e. affecting the way Kmail and Kmail users are perceived by the wider, Outlook-only audience. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #3 from Peter --- (In reply to Peter from comment #0) > SUMMARY > I have one HTML email chain, in particular, for which replying causes Kmail > to hang. > > STEPS TO REPRODUCE > 1. Start Kmail > 2. Select HTML email. > 3. Select Reply to. > > OBSERVED RESULT > Kmail hangs. Sometimes it opens the composer after a number of minutes. > However, if I try to compose a reply, the window hangs, with title bar > showing it as 'not responding', after entering a couple of lines. > > Strangely, there is one more kmail task listed in Task Managerthan in > System Monitor. (See screenshot.) > > Even if I kill the kmail process, or reboot, the kmail process is still > there, in the same hung state. > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Operating System: KDE neon 6.0 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.5.0-28-generic (64-bit) > Graphics Platform: Wayland > Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz > Memory: 7.5 GiB of RAM > Graphics Processor: Mesa Intel® Xe Graphics > Manufacturer: Dell Inc. > Product Name: XPS 13 9305 > > ADDITIONAL INFORMATION > I realise this isn't much information to go on, but I can attempt to provide > more if someone lets me know what to provide. (Would a copy of the message > be any help?) > > This seems similar to #484729, but this bug is reported as fixed. What makes the problem worse is that, on terminating and restarting the Kmail process, both a main Kmail window and a composer window for the reply try to open, resulting in Kmail hanging again. This can happen again and again. Eventually, I will manage to restart Kmail properly, but I haven't managed to identify what allows this to happen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486983] New: Switching to another layout (while pressed) does not work correctly
https://bugs.kde.org/show_bug.cgi?id=486983 Bug ID: 486983 Summary: Switching to another layout (while pressed) does not work correctly Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: h...@zytor.com CC: butir...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When using one of the Keyboard > Advanced > Switching to another layout > ... (while pressed) options, KDE will *permanently* switch to the second layout; after that, either pressing or releasing the key has no effect. STEPS TO REPRODUCE 1. Define more than one keyboard layout 2. Set the option Advanced > Switching to another layout > Right Ctrl (while pressed) 3. Type some using the first layout 4. Press Right Ctrl + some key to type using the second layout 5. Release Right Ctrl. Try to type again using the first layout OBSERVED RESULT At point 5, the second keyboard layout will be used. EXPECTED RESULT The first keyboard layout should be used. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40, plasma-systemsettings-6.0.4-1.fc40.x86_64, kwin-wayland-6.0.4.1-2.fc40.x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: qt6-qtbase-6.7.0-5.fc40.x86_64 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486835] New: Composer window geometries are mixed up with kmail main window geometries
https://bugs.kde.org/show_bug.cgi?id=486835 Bug ID: 486835 Summary: Composer window geometries are mixed up with kmail main window geometries Classification: Applications Product: kmail2 Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: h...@urpla.net Target Milestone: --- First of all, still running on X11 because bko#377162, sorry! With earlier kmail versions, the composer windows managed its own geometries, e.g. creating a new mail used the window size and position of the last composer window. With 24.02.2, this behaviour is lost, and kmail main window geometries are mixed up with composer window geometries: a new composer window inherits the main window size. In my setup, I'm running kmail main window vertically expanded on a huge 30" screen (since ages). But now, new composer windows are drawn with the same size. Before, it maintained the composer window geometries independently of the main window, and appeared a lot smaller in my setup. Another indication of this new behaviour and the mix-up is reproduced like this: Start up kmail. Resize vertical size to take the full screen height (up to the control panel, of course). Open a new mail. Resize the composer window to a different size, say half of the main window. Close the main window. Close the composer window. Restart kmail, et voilà, the main window appears with the size of the last composer window. This is a regression from my point of view. The kmail main and composer windows should manage their geometries independently. The new behaviour looks and feels ugly, as well as usability is awkward. Also, semantically, main and composer windows act quite different semantically, hence their geometries should be managed separately as well. Operating System: openSUSE Tumbleweed 20240429 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-7-preempt (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Manufacturer: ASUS kmail 24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484453] Spellchecking uses American English when British English is specified
https://bugs.kde.org/show_bug.cgi?id=484453 --- Comment #1 from Peter --- (In reply to Peter from comment #0) > *** > 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 > Spell checking seems to assume American English spellings - "endeavor" and > "specialize" - even when British English is selected. > > STEPS TO REPRODUCE > 1. Set language to British English > 2. Run spellcheck in Kmail or Kate > 3. > > OBSERVED RESULT > "endeavour" is flagged as incorrect, with "endeavor" suggested as correct > spelling. > > EXPECTED RESULT > "endeavour" should not be flagged as incorrect. > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: KDE Neon 6.0 > (available in About System) > KDE Plasma Version: 6.0.2 > KDE Frameworks Version: 6.0.0. > Qt Version: 6.6.2 > > ADDITIONAL INFORMATION > 'System Settings'.'Region and Language' shows language as 'British English'. "sudo apt-get install hunspell-en-gb" seems to have solved the problem. Not sure why I was being given the option for UK English if the dictionary wasn't installed, but working OK, now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484791] Adjust icon size for Favourites
https://bugs.kde.org/show_bug.cgi?id=484791 --- Comment #2 from Peter --- (In reply to Nate Graham from comment #1) > What's the problem exactly? They may not be the same size, but what problem > is this causing? Absolutely, no problem at all! I just thought it might look better if the icon sizes were consistent. Definitely, one for the bottom of the priority list, though. Thanks and regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings
https://bugs.kde.org/show_bug.cgi?id=482575 --- Comment #22 from Peter --- (In reply to Matty R from comment #2) > Its worth noting that it also doesn't work under X11. For most of this afternoon, I've been using X11, and the Desktop Grid function wasn't working at all - Is that what you meant? - even from the keyboard shortcut. It seems to have started working, making me wonder whether it was a particular window that was inhibiting things. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 --- Comment #3 from Peter --- It happened again, and the journald log was as follows. Does this help? Apr 26 11:42:43 peter-xps139305 akonadiserver[1694]: org.kde.pim.akonadiserver: Subscriber "MessageViewerMonitor - 97617431204032" disconnected Apr 26 11:42:48 peter-xps139305 akonadi_pop3_resource[1738]: DIGEST-MD5 common mech free Apr 26 11:42:50 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37091/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:50 peter-xps139305 kernel: audit: type=1400 audit(1714128170.589:105): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37091/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mas> Apr 26 11:42:12 peter-xps139305 kded6[1270]: Service ":1.127" unregistered Apr 26 11:42:12 peter-xps139305 kded6[1270]: Service ":1.127" unregistered Apr 26 11:42:39 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/27983/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:39 peter-xps139305 kernel: audit: type=1400 audit(1714128159.433:100): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/27983/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:40 peter-xps139305 akonadi_pop3_resource[1736]: DIGEST-MD5 common mech free Apr 26 11:42:43 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37091/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37161/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/41075/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/41172/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 kernel: audit: type=1400 audit(1714128163.249:101): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37091/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 kernel: audit: type=1400 audit(1714128163.249:102): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37161/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 kernel: audit: type=1400 audit(1714128163.249:103): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/41075/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 kernel: audit: type=1400 audit(1714128163.249:104): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/41172/oom_score_adj" pid=27857 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Apr 26 11:42:43 peter-xps139305 akonadiserver[1694]: org.kde.pim.akonadiserver: Subscriber "MessageViewerMonitor - 97617431204032" disconnected Apr 26 11:42:48 peter-xps139305 akonadi_pop3_resource[1738]: DIGEST-MD5 common mech free Apr 26 11:42:50 peter-xps139305 audit[27857]: AVC apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/37091/oom_score_adj&quo
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #2 from Peter --- Created attachment 168897 --> https://bugs.kde.org/attachment.cgi?id=168897=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #1 from Peter --- Created attachment 168896 --> https://bugs.kde.org/attachment.cgi?id=168896=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486119] New: Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 Bug ID: 486119 Summary: Replying to a particular HTML message hangs Kmail Classification: Applications Product: kmail2 Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY I have one HTML email chain, in particular, for which replying causes Kmail to hang. STEPS TO REPRODUCE 1. Start Kmail 2. Select HTML email. 3. Select Reply to. OBSERVED RESULT Kmail hangs. Sometimes it opens the composer after a number of minutes. However, if I try to compose a reply, the window hangs, with title bar showing it as 'not responding', after entering a couple of lines. Strangely, there is one more kmail task listed in Task Managerthan in System Monitor. (See screenshot.) Even if I kill the kmail process, or reboot, the kmail process is still there, in the same hung state. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 ADDITIONAL INFORMATION I realise this isn't much information to go on, but I can attempt to provide more if someone lets me know what to provide. (Would a copy of the message be any help?) This seems similar to #484729, but this bug is reported as fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485587] Tray icons on-click popups not visible
https://bugs.kde.org/show_bug.cgi?id=485587 Peter Shkenev changed: What|Removed |Added CC||santury...@gmail.com --- Comment #5 from Peter Shkenev --- I can confirm it on my OpenSUSE Tumbleweed system. SYSTEM DATA: Operating System: openSUSE Tumbleweed 20240419 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 13th Gen Intel® Core™ i7-1360P Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 21HEA021CD System Version: ThinkPad T14 Gen 4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 --- Comment #2 from Peter --- Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 Peter changed: What|Removed |Added Attachment #168833|Screenshot showing frozen |Screenshot showing frozen description|screeen |screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 Peter changed: What|Removed |Added Attachment #168832|Screenshot showing frozen |Screenshot showing frozen description|screeen |screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 --- Comment #1 from Peter --- Created attachment 168833 --> https://bugs.kde.org/attachment.cgi?id=168833=edit Screenshot showing frozen screeen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486014] New: Desktop Grid sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=486014 Bug ID: 486014 Summary: Desktop Grid sometimes crashes Classification: Plasma Product: kwin Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Created attachment 168832 --> https://bugs.kde.org/attachment.cgi?id=168832=edit Screenshot showing frozen screeen *** 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 Very occasionally, desktop grid crashes or freezes when I select it, using a keyboard shortcut. See attached photos. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[digikam] [Bug 411099] Search: Avoid search without user input (void fields)
https://bugs.kde.org/show_bug.cgi?id=411099 --- Comment #38 from Peter --- (In reply to caulier.gilles from comment #37) > Hi all, > > The digiKam 8.4.0 Appimage bundle pre-release is now based on last modern > frameworks Qt 6.7.0 and KDE 6.2.0. > > File can be downloaded at usual place : https://files.kde.org/digikam/ > Take a care : the bundle is named with the suffix "-Qt6" not "-Qt5". This > bundle is compiled under Ubuntu 22.04 and require a Linux with GlibC version > >= 2.35 to run. > > Can you reproduce the dysfonction with this version? > > Thanks in advance > > Gilles Caulier Yes, this is still valid problem. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483701] unable to launch Software Sources - root password never accepted
https://bugs.kde.org/show_bug.cgi?id=483701 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #4 from Peter --- (In reply to Christopher Smith from comment #2) > I've had the exact same thing happen when I tried opening KSystemLog through > GUI, where a "KDE su" window pops up asking for the root password, and > failing with the same error message. It was fine before Plasma 6 Me, too. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485681] Keyboard is not working
https://bugs.kde.org/show_bug.cgi?id=485681 --- Comment #1 from Peter Tselios --- I created a new Linux user, I still have the same issue with KRDC. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 --- Comment #2 from Peter Tselios --- I created a new Linux user, I still have the same issue with KRDC. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485681] New: Keyboard is not working
https://bugs.kde.org/show_bug.cgi?id=485681 Bug ID: 485681 Summary: Keyboard is not working Classification: Applications Product: krdc Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: ptsel...@outlook.com Target Milestone: --- SUMMARY Apart from the issues with copy-paste that I already mentioned in https://bugs.kde.org/show_bug.cgi?id=484666, another very important issue I have is that keyboard is not working anymore. STEPS TO REPRODUCE 1. Install or update KRDC to 24.02.2 version 2. Open a remote desktop connection to a Windows 10 Pro machine 3. Try to type. Keyboard is not working. At all. OBSERVED RESULT Keyboard is not working. EXPECTED RESULT Everything should work just fine as with KRDC 5. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro Linux/KDE Plasma: KDE Plasma Version: 6.03 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 X11 ADDITIONAL INFORMATION * Using Remmina I have no issue with the keyboard. * I installed the Flatpak version via Discover, I have the same issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 485676] New: Double-sided printing 'long side binding' not working correctly
https://bugs.kde.org/show_bug.cgi?id=485676 Bug ID: 485676 Summary: Double-sided printing 'long side binding' not working correctly Classification: Applications Product: okular Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: p.wibber...@btinternet.com 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 Using Okular double-sided printing, the option for 'long side binding" does the same as 'short side binding'. The 'short side binding' is working as expected, but the 'long side binding' isn't. STEPS TO REPRODUCE 1. Open multi-page PDF document in Okular 2. Select File->Print->Options->Options->Long side binding 3. OBSERVED RESULT Output flips on short side EXPECTED RESULT Output flips on long side SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 --- Comment #1 from Peter Tselios --- I also found a similar bug report here: https://bugs.kde.org/show_bug.cgi?id=484607 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468195] Last task in multi-row Task Manager can overlap with adjacent panel widgets
https://bugs.kde.org/show_bug.cgi?id=468195 Peter Levine changed: What|Removed |Added CC||plevine...@gmail.com --- Comment #5 from Peter Levine --- I've run into this. It seems to happen only if there are any icons pinned to the task manager. If I remove all pinned icons, the overlap goes away. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485417] New: Group windows by Virtual Desktop and Screen
https://bugs.kde.org/show_bug.cgi?id=485417 Bug ID: 485417 Summary: Group windows by Virtual Desktop and Screen Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Window List Assignee: plasma-b...@kde.org Reporter: p.wibber...@btinternet.com CC: uhh...@gmail.com Target Milestone: 1.0 *** 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 The list of windows can become very long, particularly when one has a couple of screens and a number of Virtual Desktops. I'm sure an earlier version allowed the user to group the list of windows by Virtual Desktop, and possibly also by screen. Would it be possible to reinstate this feature? Thanks and regards. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONSOperating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9305 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485128] Disk usage indicator doesn't follow Qt style
https://bugs.kde.org/show_bug.cgi?id=485128 Peter Fajdiga changed: What|Removed |Added Attachment #168215|Disk usage indicator in |Expected: Disk usage description|Fusion style (edited|indicator in Fusion style |screenshot) |(edited screenshot) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485128] Disk usage indicator doesn't follow Qt style
https://bugs.kde.org/show_bug.cgi?id=485128 Peter Fajdiga changed: What|Removed |Added Attachment #168214|Disk usage indicator not|Observed: Disk usage description|following Fusion style |indicator not following ||Fusion style -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485128] Disk usage indicator doesn't follow Qt style
https://bugs.kde.org/show_bug.cgi?id=485128 --- Comment #1 from Peter Fajdiga --- Created attachment 168215 --> https://bugs.kde.org/attachment.cgi?id=168215=edit Disk usage indicator in Fusion style (edited screenshot) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485128] New: Disk usage indicator doesn't follow Qt style
https://bugs.kde.org/show_bug.cgi?id=485128 Bug ID: 485128 Summary: Disk usage indicator doesn't follow Qt style Classification: Applications Product: dolphin Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: peter.fajd...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168214 --> https://bugs.kde.org/attachment.cgi?id=168214=edit Disk usage indicator not following Fusion style SUMMARY The disk usage indicator in the status bar only seems to be properly styled when using the Breeze application style. With other styles, even with those that ship with KDE (Fusion and MS Windows 9x), it looks Oxygen-ish instead of following the selected style. STEPS TO REPRODUCE 1. Select and apply the Fusion Application Style in KDE's System Settings 2. Open Dolphin 3. Observe the disk usage indicator in the status bar OBSERVED RESULT Disk usage indicator is styled similar to the Oxygen style (see attachment). EXPECTED RESULT Disk usage indicator should be styled in the Fusion style. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Note: This is a long-standing bug. ADDITIONAL INFORMATION I've found this possibly related bug: https://bugs.kde.org/show_bug.cgi?id=166650 , which was solved by making the disk usage indicator use KCapacityBar. If I understand correctly, KCapacityBar is not a standard Qt widget and Breeze seems to be the only Qt style that styles KCapacityBar. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467832] Add ability to change position of subject column in classic list view
https://bugs.kde.org/show_bug.cgi?id=467832 --- Comment #5 from Peter --- (In reply to Peter from comment #4) > (In reply to Laurent Montel from comment #1) > > We put it in first column because we have support for thread message. > > => it will be wierd if we change it. > > by default it's better to show subject in first column > (In reply to heinoldk from comment #3) > > (In reply to Laurent Montel from comment #1) > > > We put it in first column because we have support for thread message. > > > => it will be wierd if we change it. > > > by default it's better to show subject in first column > > > > Thank you for the fast reply. > > I don't quite see how having the subject in the first column is coupled to > > supporting message threads. I added another example from Gnome Revolution > > which demonstrates how it could look like. > > Of course, having robust defaults is good and I don't want to convince you > > to change these. > > I was just hoping for more customizability in this regard and thought it > > could be possible without too much effort or additional complexity. > Hi Laurent, > > Ideally, I'd like to have tags displayed in the first column, but if I > right-click the top of the message list, and check Important and/or Action, > I can't drag those extra columns to the left. I see that there's a > Read/Unread icon on the very left-hand side, which seems to be part of the > Subject column, but I can't work out how to add other tags to this ( > although I could swear I succeeded with a previous installation of KMail). > I tried the Message - Mark Message menu, but this is confusing - why is the > functionality different for different tags, i.e. a menu item for 'Mark > Message as Unread' but a checkbox for 'Remove Important Mark'? - and doesn't > appear to have any effect. > > Many thanks and regards. > > KMail 6.0.1 (24.02.1) I've just worked out that you can achieve whatever you want - this must be what I'd done in a previous installation - by defining a new theme under Settings -> Configure KMail - > Appearance -> Message List -> Configure -> Appearance. This includes having anything, other than Subject, in the first column. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485030] New: Crash on Plasma X11 start
https://bugs.kde.org/show_bug.cgi?id=485030
Bug ID: 485030
Summary: Crash on Plasma X11 start
Classification: Plasma
Product: plasmashell
Version: 6.0.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: pri...@peter-kreussel.de
Target Milestone: 1.0
Application: plasmashell (6.0.3)
Qt Version: 6.6.3
Frameworks Version: 6.0.0
Operating System: Linux 6.8.2-arch2-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]
-- Information about the crash:
Plasma crashed on startup.
Happens rarely, has not been the first time,
But I can't tell whether cause for crash was always the same
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/plasmashell...
[New LWP 1394]
[New LWP 1396]
[New LWP 1583]
[New LWP 1397]
Downloading separate debug info for /usr/lib/libPlasmaQuick.so.6...
Downloading separate debug info for /usr/lib/libKF6DBusAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6XmlGui.so.6...
Downloading separate debug info for /usr/lib/libKWaylandClient.so.6...
Downloading separate debug info for /usr/lib/libKF6StatusNotifierItem.so.6...
Downloading separate debug info for /usr/lib/libkworkspace6.so.6...
Downloading separate debug info for /usr/lib/libwayland-client.so.0...
Downloading separate debug info for /usr/lib/libLayerShellQtInterface.so.6...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackCore.so.6...
Downloading separate debug info for /usr/lib/libxcb.so.1...
Downloading separate debug info for /usr/lib/libKF6Crash.so.6...
Downloading separate debug info for /usr/lib/libKF6Solid.so.6...
Downloading separate debug info for /usr/lib/libPlasma.so.6...
Downloading separate debug info for /usr/lib/libKF6WindowSystem.so.6...
Downloading separate debug info for /usr/lib/libKF6Svg.so.6...
Downloading separate debug info for /usr/lib/libPlasmaActivities.so.6...
Downloading separate debug info for /usr/lib/libKF6GlobalAccel.so.6...
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigQml.so.6...
Downloading separate debug info for /usr/lib/libQt6Quick.so.6...
Downloading separate debug info for /usr/lib/libQt6Qml.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigGui.so.6...
Downloading separate debug info for /usr/lib/libQt6WaylandClient.so.6...
Downloading separate debug info for /usr/lib/libKF6Package.so.6...
Downloading separate debug info for /usr/lib/libKF6I18n.so.6...
Downloading separate debug info for /usr/lib/libKF6Service.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigCore.so.6...
Downloading separate debug info for /usr/lib/libKF6CoreAddons.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libc.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6KCMUtilsQuick.so.6...
Downloading separate debug info for /usr/lib/libxcb-shape.so.0...
Downloading separate debug info for /usr/lib/libKF6KIOCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Notifications.so.6...
Downloading separate debug info for /usr/lib/libKF6WidgetsAddons.so.6...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libQt6Xml.so.6...
Downloading separate debug info for /usr/lib/libQt6Network.so.6...
Downloading separate debug info for /usr/lib/libQt6PrintSupport.so.6...
Downloading separate debug info for /usr/lib/libKF6ItemViews.so.6...
Downloading separate debug info for /usr/lib/libKF6IconWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6IconThemes.so.6...
Downloading separate debug info for /usr/lib/libKF6ColorScheme.so.6...
Downloading separate debug info for /usr/lib/libKF6GuiAddons.so.6...
Downloading separate debug info for /usr/lib/libXau.so.6...
Downloading separate debug info for /usr/lib/libxcb-randr.so.0...
Downloading separate debug info for /usr/lib/libffi.so.8...
Downloading separate debug info for /usr/lib/libXdmcp.so.6...
Downloading separate debug info for /usr/lib/libX11.so.6...
Downloading separate debug info for /usr/lib/libudev.so.1...
Downloading separate debug info for /usr/lib/libmount.so.1...
Downloading separate debug info for /usr/lib/libimobiledevice-1.0.so.6...
D
[Discover] [Bug 484983] Failed Offline Update libk ColorPicker.so.0
https://bugs.kde.org/show_bug.cgi?id=484983 Peter changed: What|Removed |Added CC||kde.kindling...@passmail.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484983] New: Failed Offline Update libk ColorPicker.so.0
https://bugs.kde.org/show_bug.cgi?id=484983 Bug ID: 484983 Summary: Failed Offline Update libk ColorPicker.so.0 Classification: Applications Product: Discover Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (offline) Assignee: plasma-b...@kde.org Reporter: kde.kindling...@passmail.net CC: aleix...@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 think I first experienced this error message 4/2/2024 Discover shows update: System upgrade 1 package will be upgraded 22.8 KiB After installation and reboot, I get "Failed Offline Update" message: Failed to update 1 package Error while installing package: trying to overwrite '/usr/lib/x86_64-linux-gnu/libk Color Picker.so.0' which is also in package likcolorpicker0 Two choices in buttons: Open Discover and Repair System Repair System leads to "Repair Failed" STEPS TO REPRODUCE 1. Normal updating of system software 2. System updates, reboots 3. Updates available shows small blue dot indicating something is available. OBSERVED RESULT above in summary EXPECTED RESULT Up to Date message - Sorry if duplicate or resolved - I'm new user not yet skilled in bug reporting... I do not know if this is a true bug, or a problem only on my system... Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-2600 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD BARTS Manufacturer: Apple Inc. Product Name: iMac12,2 System Version: 1.0 Also not sure if this crash report is relevant or rabbit trail: PID: 1389 (xdg-desktop-por) UID: 118 (sddm) GID: 127 (sddm) Signal: 6 (ABRT) Timestamp: Wed 2024-04-03 08:29:33 CDT (27min ago) Command Line: /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde Executable: /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde Control Group: /user.slice/user-118.slice/user@118.service/session.slice/plasma-xdg-desktop-portal-kde.service Unit: user@118.service User Unit: plasma-xdg-desktop-portal-kde.service Slice: user-118.slice Owner UID: 118 (sddm) Boot ID: f1457adea047452e92af32020fd37758 Machine ID: 89b38591ddcf4b138584fb79b1778dec Hostname: 2011iMac Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.118.f1457adea047452e92af32020fd37758.1389.171215097300.zst (inaccessible) Message: Process 1389 (xdg-desktop-por) of user 118 dumped core. Found module linux-vdso.so.1 with build-id: a2e4b4c8a504f98ae04bd0bb1d3c92438cdbe034 Found module libxcb-util.so.1 with build-id: 898a03cabe0d55491c4bf447c7399b8bf4e392d8 Found module libxkbcommon-x11.so.0 with build-id: 99c6b6b6c6010c09544caa3c1de42a6f7780a1c2 Found module libxcb-xinput.so.0 with build-id: f871045f953437452c52724be4a95fe5fe3aef5c Found module libICE.so.6 with build-id: cf39da2f7c723f976c6e676704e218513e2b0b2b Found module libSM.so.6 with build-id: 6b32192c8a8870a8fe04403f537e806da93a1dd8 Found module libX11-xcb.so.1 with build-id: 70f2a36d79c623f42fd70fa7ffb06d8877c74f16 Found module libxcb-xkb.so.1 with build-id: ffda354b1a72e3efe2447a3dbc9c29ba3f4e8d63 Found module libxcb-xfixes.so.0 with build-id: d6f264cc06fb6c92b5ced2c8f373cf5a5bda0e09 Found module libxcb-sync.so.1 with build-id: 657d8516621c4042b4b221ce1b3525f92467ef7e Found module libxcb-shm.so.0 with build-id: edb24ef4079aa423edcc50a3bb0dfb912fe8a57a Found module libxcb-shape.so.0 with build-id: 18eea95584dc231c380edfbac27cd2481b64c079 Found module libxcb-render-util.so.0 with build-id: 7785770a369b562bcf80ad2318f6e9efff59b863 Found module libxcb-render.so.0 with build-id: cb521131fd3b0f2ee6056cbc2014b3b8ef0d5c0e Found module libxcb-randr.so.0 with build-id: 7af27bf3e608d5c06645ad4086788afe8a8447e7 Found module libxcb-image.so.0 with build-id: 81ce7ad4384f3c9629121be5b18f87c82131e023 Found module libxcb-icccm.so.4 with build-id: 38663873ef7ad5e3f30293a6938a762cd1dd8d90 Found module libxcb-cursor.so.0 with build-id: 2998e11e2f21398cd8439c0afa8c84e53053fc38 Found module libQt6XcbQpa.so.6 with build-id: 64b4ff708eebf608728f3acc50cdca25e1ae8cf1 Found module
[valgrind] [Bug 484935] [patch] Valgrind reports false "Conditional jump or move depends on uninitialised value" errors for aarch64 signal handlers
https://bugs.kde.org/show_bug.cgi?id=484935 --- Comment #5 from Peter Edwards --- Thanks for the fast turn-around! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484953] New: Discover UI cosmetic bug with [Select None] button text overlapped with text "Total size: ..." upon Refresh
https://bugs.kde.org/show_bug.cgi?id=484953 Bug ID: 484953 Summary: Discover UI cosmetic bug with [Select None] button text overlapped with text "Total size: ..." upon Refresh Classification: Applications Product: Discover Version: 6.0.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: peterg4...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 168077 --> https://bugs.kde.org/attachment.cgi?id=168077=edit Image (png) of UI bug SUMMARY Discover UI cosmetic bug text on [Select None] button overlap with text "Total size: ..." STEPS TO REPRODUCE 1. Launch Discover 2. Ensure Discover is in Restore state, i.e. not maximised 3. Click the [Updates (x)] button in the left top panel 4. Click on the [Refresh] button in the top right-most Title bar area (directly under the Minimise, Maximise, Close icons) OBSERVED RESULT The [Select None] button text now has it's text overlapped with the Refresh text, e.g. "Total size: 508.7 MiB" on top of it - please refer to attached image. EXPECTED RESULT The text of the [Select None] button should remain unaffected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (version 20240329) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This cosmetic bug does not occur when Discover is maximised. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484935] [patch] Valgrind reports false "Conditional jump or move depends on uninitialised value" errors for aarch64 signal handlers
https://bugs.kde.org/show_bug.cgi?id=484935 --- Comment #1 from Peter Edwards --- Created attachment 168063 --> https://bugs.kde.org/attachment.cgi?id=168063=edit Patch for issue -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484935] New: [patch] Valgrind reports false "Conditional jump or move depends on uninitialised value" errors for aarch64 signal handlers
https://bugs.kde.org/show_bug.cgi?id=484935 Bug ID: 484935 Summary: [patch] Valgrind reports false "Conditional jump or move depends on uninitialised value" errors for aarch64 signal handlers Classification: Developer tools Product: valgrind Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: pea...@arista.com Target Milestone: --- Created attachment 168062 --> https://bugs.kde.org/attachment.cgi?id=168062=edit Test showing erroneous behaviour for linux/aarch64 Accessing the arguments to signal handlers in aarch64 binaries can create "Conditional jump or move depends on uninitialized value" diagnostics. Comparing the code for the aarch64 signal frame creation to that for x86_64 shows the problem - the values for the registers used for passing arguments (X0 thru X3) are modified, but the required `VG_TRACK( post_reg_write, ...` macros are not invoked to indicate that the registers now have well defined values. Adding these VG_TRACK macros in fixes the issue. The attached test.c shows the problem under `valgrind` without the fix, but succeeds with it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467832] Add ability to change position of subject column in classic list view
https://bugs.kde.org/show_bug.cgi?id=467832 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #4 from Peter --- (In reply to Laurent Montel from comment #1) > We put it in first column because we have support for thread message. > => it will be wierd if we change it. > by default it's better to show subject in first column (In reply to heinoldk from comment #3) > (In reply to Laurent Montel from comment #1) > > We put it in first column because we have support for thread message. > > => it will be wierd if we change it. > > by default it's better to show subject in first column > > Thank you for the fast reply. > I don't quite see how having the subject in the first column is coupled to > supporting message threads. I added another example from Gnome Revolution > which demonstrates how it could look like. > Of course, having robust defaults is good and I don't want to convince you > to change these. > I was just hoping for more customizability in this regard and thought it > could be possible without too much effort or additional complexity. Hi Laurent, Ideally, I'd like to have tags displayed in the first column, but if I right-click the top of the message list, and check Important and/or Action, I can't drag those extra columns to the left. I see that there's a Read/Unread icon on the very left-hand side, which seems to be part of the Subject column, but I can't work out how to add other tags to this ( although I could swear I succeeded with a previous installation of KMail). I tried the Message - Mark Message menu, but this is confusing - why is the functionality different for different tags, i.e. a menu item for 'Mark Message as Unread' but a checkbox for 'Remove Important Mark'? - and doesn't appear to have any effect. Many thanks and regards. KMail 6.0.1 (24.02.1) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, mdir_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #17 from Peter Maydell --- The Linux kernel documents which ID registers and which fields in those registers it exposes here: https://www.kernel.org/doc/Documentation/arm64/cpu-feature-registers.txt . Does FreeBSD expose the same set, or a different set? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings
https://bugs.kde.org/show_bug.cgi?id=482575 --- Comment #19 from Peter --- (In reply to Vlad Zahorodnii from comment #18) > Nate probably made a typo. The setting will be available in 6.1 Vlad, Thank you for the update. I'd noticed it wasn't in 6.0.3, too, and had assumed it had missed the boat. It can be a little confusing for us to understand exactly how and when things that get sorted will actually reach our desktops, but please be assured that all the efforts of the likes of you and Nate are hugely appreciated. As I keep saying, you don't get service like this from Microsoft. Regards, P -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484791] New: Adjust icon size for Favourites
https://bugs.kde.org/show_bug.cgi?id=484791 Bug ID: 484791 Summary: Adjust icon size for Favourites Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: 1.0 *** 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 The icon size for applications added to Favourites is inconsistent with (bigger than) the icons next to application names (or descriptions in the drop-down menus. It would be nice to be able to make them the same. Thanks and regards. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 Peter Tselios changed: What|Removed |Added CC||ptsel...@outlook.com --- Comment #10 from Peter Tselios --- I second this bug. Please note that this is happening on X11 and Wayland as well. Identical behavior. My settings are: Bottom positioning, Center Alignment, Fill Width, Always Visible, Translucent, NOT floating. Height was 36px in KDE5 and reduced to 34 when I moved to KDE 6. Feel free to contact me as well for any possible tests. I use the openSUSE theme with Breeze Light style, Breeze decorations and Breeze Light cursors (I was forced to select the BL cursors because after the upgrade I had no mouse pointer on my screen) -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] New: Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 Bug ID: 484666 Summary: Copy - Paste is not working Classification: Applications Product: krdc Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: ptsel...@outlook.com Target Milestone: --- SUMMARY After the upgrade of KDE to KDE 6 in my Tumbleweed desktop, the KRDC was upgraded to 24.02. The upgrade was far for smooth since it could not connect to any remote machine via RDP unless I was specifying to use the best available option. In any case, my issue right now is that I cannot copy-paste from my dekstop to the remote Windows machine or from the windows to the desktop. At first I thought it was a Wayland issue, but the same is happening in X11 as well. Finally, I downgraded to 23.08 and now I have copy-paste working again. STEPS TO REPRODUCE 1. Upgrade your KRDC to 24.02 2. Start an RDP to a remote machine. 3. Try to copy-paste to/from the remote machine OBSERVED RESULT Copy-paste is not working EXPECTED RESULT Copy-paste is working SOFTWARE/OS VERSIONS Windows: Windows 10 Linux/KDE Plasma: Tumbleweed (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467668] [Desktop grid] Superfluous highlighting of desktop on with external monitor
https://bugs.kde.org/show_bug.cgi?id=467668 --- Comment #3 from Peter --- (In reply to Nate Graham from comment #2) > Can you check to see if this is still an issue in Plasma 6? Thanks a lot! Hi Nate, Working fine under Plasma 6. Thanks and regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings
https://bugs.kde.org/show_bug.cgi?id=482575 --- Comment #16 from Peter --- (In reply to Nate Graham from comment #15) > This is fixed for Plasma 6.0.3. Excellent. Thanks, as always. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484453] New: Spellchecking uses American English when British English is specified
https://bugs.kde.org/show_bug.cgi?id=484453 Bug ID: 484453 Summary: Spellchecking uses American English when British English is specified Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: p.wibber...@btinternet.com 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 Spell checking seems to assume American English spellings - "endeavor" and "specialize" - even when British English is selected. STEPS TO REPRODUCE 1. Set language to British English 2. Run spellcheck in Kmail or Kate 3. OBSERVED RESULT "endeavour" is flagged as incorrect, with "endeavor" suggested as correct spelling. EXPECTED RESULT "endeavour" should not be flagged as incorrect. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0. Qt Version: 6.6.2 ADDITIONAL INFORMATION 'System Settings'.'Region and Language' shows language as 'British English'. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 484303] New: On high DPI screens, text on UI controls is too small to read
https://bugs.kde.org/show_bug.cgi?id=484303
Bug ID: 484303
Summary: On high DPI screens, text on UI controls is too small
to read
Classification: Applications
Product: okular
Version: 23.08.4
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: peter.meilst...@gmail.com
Target Milestone: ---
Created attachment 167637
--> https://bugs.kde.org/attachment.cgi?id=167637=edit
Showing too small UI text before and after correction
SUMMARY
On high DPI screens where UI scale is set to 200%, text on UI controls and
popup menus is too small to read.
STEPS TO REPRODUCE
1. Okular 23.08.04 is installed from from the windows store.
2. Using a 4k display, and have Scaling in Windows
Settings>System>Display>Scale is set to 200%.
3. Launch Okular.
OBSERVED RESULT
Labels on buttons/toolbar controls and popup menus is too small to read (see
attached screenshot, upper half.)
EXPECTED RESULT
(see screenshot, lower half)
SOFTWARE/OS VERSIONS
Windows:
Edition Windows 11 Pro
Version 23H2
Installed on12/8/2023
OS build22631.3296
Experience Windows Feature Experience Pack 1000.22687.1000.0
Okular: Okular reports its version as 23.08.04, The Windows Store app reports
the installed version as 23.801.1522.0.
ADDITIONAL INFORMATION
I have found a way to correct the issue by manually updating the application
manifest information.
1. Install the Windows SDK. Then locate the program `mt.exe`. On my system it
is located at `C:\Program Files (x86)\Windows
Kits\10\bin\10.0.22621.0\x64\mt.exe`.
2. At an administrator prompt, use `mt.exe` to extract the manifest from the
okular binary. I used the commands:
cd "C:\Program Files\Okular\bin"
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\mt.exe"
"-inputresource:okular.exe;#1" -out:okular.manifest
Examine the resulting file `okular manifest`. I found:
3. Edit `okular.manifest` to inludes a dpi awareness setting. After editing,
mine looked like this:
```{html}
http://schemas.microsoft.com/SMI/2016/WindowsSettings;>
system
```
4. Make a backup of `okular.exe`, then apply the changed manifest back to the
okular binary. I ran:
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\mt.exe"
-manifest okular.manifest "-updateresource:okular.exe;#1"
After relaunching Okular, it now shows reasonable font sizes in its UI.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 484160] Dolphin crashes after attempting to add timeline to Places
https://bugs.kde.org/show_bug.cgi?id=484160 --- Comment #3 from Peter --- (In reply to Nicolas Fella from comment #1) > Can reproduce. > > As a workaround you can delete/move aside .local/share/user-places.xbel Nicolas, Workaround works perfectly. Many thanks and regards Peter -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484160] New: Dolphin crashes after attempting to add timeline to Places
https://bugs.kde.org/show_bug.cgi?id=484160
Bug ID: 484160
Summary: Dolphin crashes after attempting to add timeline to
Places
Classification: Applications
Product: dolphin
Version: unspecified
Platform: Neon
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: p.wibber...@btinternet.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
***
After attempting to add a timeline:// entry to Places (I'd like to have 'this
month' and 'last month' in Places, which I had configured under KDE neon 5.27),
Dolphin crashes on launch.
***
STEPS TO REPRODUCE
>From memory (as I can't run dolphin in order to reproduce the first steps)
1. Enter timeline:// into editable location bar
2. Right click on March 2024 with a view to adding to Places
OBSERVED RESULT
Dolphin crashes. All subsequent attempts to launch Dolphin fail, with the
following messages:
ASSERT: "path.endsWith(QLatin1String("/today"))" in file
./src/filewidgets/kfileplacesmodel.cpp, line 111
KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2
KCrash: Application Name = dolphin path = /usr/bin pid = 2362
KCrash: Arguments: /usr/bin/dolphin
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
EXPECTED RESULT
Dolphin should start normally.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: KDE neon 6.0
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
I'm not sure whether I've done this correctly, but running 'gdb dolphin', and
using the 'run' command, I get:
(gdb) run
Starting program: /usr/bin/dolphin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef5ff640 (LWP 3940)]
[New Thread 0x7fffeedfe640 (LWP 3941)]
[New Thread 0x7fffedcad640 (LWP 3942)]
[New Thread 0x7fffed4ac640 (LWP 3943)]
[New Thread 0x7fffeccab640 (LWP 3944)]
[New Thread 0x7fffe5dff640 (LWP 3945)]
[New Thread 0x7fffe55fe640 (LWP 3946)]
[New Thread 0x7fffe4dfd640 (LWP 3947)]
[New Thread 0x7fffd8fff640 (LWP 3948)]
[New Thread 0x7fffbbfff640 (LWP 3949)]
[New Thread 0x7fffbb7fe640 (LWP 3950)]
[Thread 0x7fffbb7fe640 (LWP 3950) exited]
[Thread 0x7fffbbfff640 (LWP 3949) exited]
[New Thread 0x7fffbbfff640 (LWP 3951)]
[New Thread 0x7fffbb7fe640 (LWP 3952)]
[Thread 0x7fffbb7fe640 (LWP 3952) exited]
[Thread 0x7fffbbfff640 (LWP 3951) exited]
ASSERT: "path.endsWith(QLatin1String("/today"))" in file
./src/filewidgets/kfileplacesmodel.cpp, line 111
Thread 1 "dolphin" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140737219537600) at
./nptl/pthread_kill.c:44
Download failed: Invalid argument. Continuing without source file
./nptl/./nptl/pthread_kill.c.
44 ./nptl/pthread_kill.c: No such file or directory.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 484149] New: kmail crashes due to missing libZXing.so.3
https://bugs.kde.org/show_bug.cgi?id=484149 Bug ID: 484149 Summary: kmail crashes due to missing libZXing.so.3 Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY *** As of yesterday (20 March 2024) Kmail started crashing every time I tried to launch it. Launching it from Konsole, it reported missing libZXing.so.3. 1. Start kmail 2. 3. OBSERVED RESULT Kmail crashes, reporting libZXing.so.3 EXPECTED RESULT kmail should start normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The problem is fixed by installed libZXing. Is this a new dependency? If not, why did it disappear? Thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480733] Kmail 'Export to PDF' crops message
https://bugs.kde.org/show_bug.cgi?id=480733 --- Comment #4 from Peter --- Hi Laurent, I don't know whether it's the same issue or something entirely different, but I also get the problem with 'Print' and 'Print Preview'. I get it with kmail 6.0.0, too. Thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings
https://bugs.kde.org/show_bug.cgi?id=482575 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436692] Sluggish effects after sleep
https://bugs.kde.org/show_bug.cgi?id=436692 --- Comment #3 from Peter Shkenev --- (In reply to Zamundaaa from comment #2) > This bug report is pretty old, sorry that we couldn't get to it sooner. I > assume it's no longer relevant; if it still happens on Plasma 6, just reopen > this and we'll take a look Thank you for taking a look nonetheless. It's indeed not relevant anymore to me since I've changed my GPU. But if there is any interest, I can install this older card and check whether the bug can be reproduced. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483105] shortcuts does not accept extended keys on a microsoft natural ergonomic keyboard 4000
https://bugs.kde.org/show_bug.cgi?id=483105 Peter L. Steger changed: What|Removed |Added CC||peter.ste...@stptech.at -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483105] shortcuts does not accept extended keys on a microsoft natural ergonomic keyboard 4000
https://bugs.kde.org/show_bug.cgi?id=483105 --- Comment #1 from Peter L. Steger --- Created attachment 166866 --> https://bugs.kde.org/attachment.cgi?id=166866=edit the keyboard The "extended keys" are marked -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483105] New: shortcuts does not accept extended keys on a microsoft natural ergonomic keyboard 4000
https://bugs.kde.org/show_bug.cgi?id=483105 Bug ID: 483105 Summary: shortcuts does not accept extended keys on a microsoft natural ergonomic keyboard 4000 Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: peter.ste...@stptech.at CC: k...@david-redondo.de Target Milestone: --- Created attachment 166865 --> https://bugs.kde.org/attachment.cgi?id=166865=edit Screenshot while hitting the key [calculator] SUMMARY However the keyboard is fully supported the user assignement of shortcuts does not accept the extra keys on the keyboard => calculator, mail, search, home, favorites, etc. For instance: the search key (scancodes 0xe0 0x65 / 0xe0 0xe5) is available in the pre defined assignement of krunner. But if I want to assign the calculator key (scancodes 0xe0 0x21 / 0xe0 0xa1) to kcalc the shortcut module does not react on the keystroke I am running on EndeavourOS Gemini-nova - complete fresh installation with plasma setup from "extra": sudo pacman -S plasma-meta kde-system-meta sudo pacman -S kdeconnect kdenetwork-filesharing kget kio-extras kio-zeroconf sudo pacman -S filelight kate kcalc kdialog koncole ktimer sudo pacman -S gwenview okular spectacle colord-kde kruler sudo pacman -S kdenlive kruler kdeplasma-addons I did not install packages still depending on QT5: -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 270881] Cannot assign launcher key ("1" - "5") on Microsoft Natural Ergonomic Keyboard
https://bugs.kde.org/show_bug.cgi?id=270881 Peter L. Steger changed: What|Removed |Added CC||peter.ste...@stptech.at -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473332] Discover crashes in KNSCore::ResultsStream::fetch when searching
https://bugs.kde.org/show_bug.cgi?id=473332 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #14 from Peter --- Happens for me when searching in Discover 6.0.0 for "Ada" , as well as for "Libreoffice", but not for most other search terms. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #26 from Peter --- Following a fresh install of KDE Neon 6.0, I've set up a few panel widgets to run Chrome apps, using the "--app=" argument. These seem to shade correctly. I thought perhaps these were ignoring the Window Behaviour system settings altogether, but if I set the Titlebar Action to "Minimse", rather than "Shade", then they correctly minimise, as do other windows. Very odd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482220] Plasma 6 double click to shade on titlebar no longer works
https://bugs.kde.org/show_bug.cgi?id=482220 --- Comment #2 from Peter --- (In reply to Peter from comment #1) > (In reply to Ben from comment #0) > > 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. Set Titlebar Action for Double-click to Shade > > 2. Double Click title bar > > > > > > OBSERVED RESULT > > > > On Wayland session > > For most windows nothing happens. Chromium browser using system title bar > > partially works, but leaves a frame, maybe drop shadow of where the window > > was, but contents are shaded. However if a window is revealed in the > > shaded region it can't get focus by clicking on it. > > > > On X11 session. > > > > Window contents gets shaded, however a frame /blur effect is still shown > > where the window existed prior to shading. Clicking on a revealed window in > > the shaded region, does select that window unlike the Wayland session > > > > > > EXPECTED RESULT > > > > Window should shade, with just the title bar visible. Worked fine prior to > > Plasma 6. > > > > SOFTWARE/OS VERSIONS > > > > Linux/KDE Plasma: Neon 6 > > KDE Plasma Version: 6.0.0 > > KDE Frameworks Version: 6.0.0 > > Qt Version: 6.6.2 > > > > ADDITIONAL INFORMATION > > I have updated one PC to Plasma 6 from Plasma 5.27, and Shade seems to work. > However, a fresh install on another doesn't, just as Ben describes. Ah, one is X11 and the other is Wayland! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482220] Plasma 6 double click to shade on titlebar no longer works
https://bugs.kde.org/show_bug.cgi?id=482220 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #1 from Peter --- (In reply to Ben from comment #0) > 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. Set Titlebar Action for Double-click to Shade > 2. Double Click title bar > > > OBSERVED RESULT > > On Wayland session > For most windows nothing happens. Chromium browser using system title bar > partially works, but leaves a frame, maybe drop shadow of where the window > was, but contents are shaded. However if a window is revealed in the > shaded region it can't get focus by clicking on it. > > On X11 session. > > Window contents gets shaded, however a frame /blur effect is still shown > where the window existed prior to shading. Clicking on a revealed window in > the shaded region, does select that window unlike the Wayland session > > > EXPECTED RESULT > > Window should shade, with just the title bar visible. Worked fine prior to > Plasma 6. > > SOFTWARE/OS VERSIONS > > Linux/KDE Plasma: Neon 6 > KDE Plasma Version: 6.0.0 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > > ADDITIONAL INFORMATION I have updated one PC to Plasma 6 from Plasma 5.27, and Shade seems to work. However, a fresh install on another doesn't, just as Ben describes. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 482171] New: KMyMoney not launching after update to Plasma 6.0 2/29/24. I was running most current release of Neon & KMyMoney before Plasma upgrade.
https://bugs.kde.org/show_bug.cgi?id=482171 Bug ID: 482171 Summary: KMyMoney not launching after update to Plasma 6.0 2/29/24. I was running most current release of Neon & KMyMoney before Plasma upgrade. Classification: Applications Product: kmymoney Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: kde.kindling...@passmail.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 *** Wish I could help more - my Linux competence is low... I have default Plasma share info about crashes set to provide max info (slider to far right). STEPS TO REPRODUCE 1. Click on launch icon on dock. OBSERVED RESULT Blue clockwise circle around icon on dock (normal), small bouncing icon just below mouse location (normal) then blue circle stops and bouncing icon collapses into dock and nothing else I can observe... Program never displays launch screen... EXPECTED RESULT Normal launch to data file. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-2600 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD BARTS Manufacturer: Apple Inc. Product Name: iMac12,2 System Version: 1.0 ADDITIONAL INFORMATION I am now depending on (and loving using) KMyMoney. Fully cut strings with Quicken on MacOS so this is my only financial tracking app... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482082] Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 Peter Ped Helcmanovsky changed: What|Removed |Added CC||p...@7gods.org --- Comment #4 from Peter Ped Helcmanovsky --- Disabling splash screen brings the wayland login time from ~30s down to ~2.5s for me too. Still feels like extra 1.5s more than the X11 login time, but now I would need stopwatch to be sure it's not placebo. The X11 session is still ~1s login time even after Plasma 6 upgrade, just like it was before, but I used Wayland first time ever by accident (it was default after upgrade) and it took those ~30s, also after logout/restart (well, once I fixed those as they were not working after upgrade too). Going to test X11 without splash screen if it didn't get slower (to match ~2.5s of Wayland), but if there's no edit/comment from me, then X11 behaves normally with ~1s login. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481988] Updating to neon 6.0 broke plasma (broken dependencies for plasma-desktop)
https://bugs.kde.org/show_bug.cgi?id=481988 --- Comment #5 from Peter --- (In reply to jmeron1991 from comment #4) > (In reply to Peter from comment #3) > > (In reply to Jay Stevens from comment #2) > > > Workaround - run `sudo pkcon install libdecor-0-0 libsdl2-2.0-0 > > > plasma-desktop plasma-desktop-data --allow-reinstall` to force-update the > > > dependencies. You may need to run `sudo apt autoremove` and/or `sudo pkcon > > > refresh` first. > > > > > > On a reboot, Plasma will be fixed. > > > > Hi Jay, > > When I do this, I get ... > > "Resolving [=] > > More than one package matches: > > 1. libdecor-0-0-0.1.0-3build1.amd64 [auto:ubuntu-jammy-main] > > 2. libdecor-0-0-0.2.1-0xneon+22.04+jammy+release+build2.amd64 > > [user_jammy-jammy-main] > > Please choose the correct package: " > > Which should I choose? > > Thanks and regards. > > I chose the newest each time, and it worked. jmeron1991, Jay, Worked! Many thanks and regards. P -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481988] Updating to neon 6.0 broke plasma (broken dependencies for plasma-desktop)
https://bugs.kde.org/show_bug.cgi?id=481988 Peter changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #3 from Peter --- (In reply to Jay Stevens from comment #2) > Workaround - run `sudo pkcon install libdecor-0-0 libsdl2-2.0-0 > plasma-desktop plasma-desktop-data --allow-reinstall` to force-update the > dependencies. You may need to run `sudo apt autoremove` and/or `sudo pkcon > refresh` first. > > On a reboot, Plasma will be fixed. Hi Jay, When I do this, I get ... "Resolving [=] More than one package matches: 1. libdecor-0-0-0.1.0-3build1.amd64 [auto:ubuntu-jammy-main] 2. libdecor-0-0-0.2.1-0xneon+22.04+jammy+release+build2.amd64 [user_jammy-jammy-main] Please choose the correct package: " Which should I choose? Thanks and regards. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481011] The metadata tabs disappear from the right sidebar.
https://bugs.kde.org/show_bug.cgi?id=481011 --- Comment #12 from Peter --- (In reply to Peter from comment #11) > Tested in digiKam-8.3.0-20240219T164912-Win64.exe (Qt 6.6.1) > I can't reproduce anymore. Works well! Ohh, no! Sorry. I was wrong! This version (digiKam-8.3.0-20240219T164912-Win64.exe (Qt 6.6.1)) still contains the fault! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481011] The metadata tabs disappear from the right sidebar.
https://bugs.kde.org/show_bug.cgi?id=481011 --- Comment #11 from Peter --- Tested in digiKam-8.3.0-20240219T164912-Win64.exe (Qt 6.6.1) I can't reproduce anymore. Works well! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480733] Kmail 'Export to PDF' crops message
https://bugs.kde.org/show_bug.cgi?id=480733 --- Comment #3 from Peter --- Laurent, Apologies for not seeing your messages earlier. Do I understand you have the information you need? Thanks and regards. P -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481317] New: Kmail crashed when forwarding a message
https://bugs.kde.org/show_bug.cgi?id=481317 Bug ID: 481317 Summary: Kmail crashed when forwarding a message Classification: Applications Product: kmail2 Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-17-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Kmail crashed when I selected 'Forward' for a particular email. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x7f58712b2aa7 in MimeTreeParser::ObjectTreeParser::processType(KMime::Content*, MimeTreeParser::ProcessResult&, QByteArray const&) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #7 0x7f58712b31fd in MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #8 0x7f58712b34ff in MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #9 0x7f5871e5b982 in TemplateParser::TemplateParserJob::processWithTemplate(QString const&) () from /lib/x86_64-linux-gnu/libKPim5TemplateParser.so.5 #10 0x7f5871e5d0b8 in TemplateParser::TemplateParserJob::process(QSharedPointer const&, long long) () from /lib/x86_64-linux-gnu/libKPim5TemplateParser.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481317] Kmail crashed when forwarding a message
https://bugs.kde.org/show_bug.cgi?id=481317 --- Comment #1 from Peter --- Created attachment 165817 --> https://bugs.kde.org/attachment.cgi?id=165817=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
