[systemsettings] [Bug 467039] With SDDM using Wayland, syncing settings does not send along the correct scaling as it does with X11
https://bugs.kde.org/show_bug.cgi?id=467039 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478768] kdeconnect crashes every time the phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=478768 --- Comment #1 from Gerhard Kulzer --- Created attachment 164310 --> https://bugs.kde.org/attachment.cgi?id=164310=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478768] New: kdeconnect crashes every time the phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=478768 Bug ID: 478768 Summary: kdeconnect crashes every time the phone tries to connect Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gerha...@gmx.ch CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.11 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: Wayland Distribution: KDE neon Testing Edition DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: This has been going on for several month across at least 10 updates of the system. The crash can be reproduced every time. -- Backtrace (Reduced): #6 Device::reloadPlugins (this=this@entry=0x56426aaee260) at ./core/device.cpp:184 #7 0x7fd321b2f591 in Device::addLink (this=0x56426aaee260, link=) at ./core/device.cpp:292 #8 0x7fd321b2a3a1 in Daemon::onNewDeviceLink (this=0x7ffee734c3d0, link=0x56426ac09830) at ./core/daemon.cpp:170 #9 0x7fd3204f43e4 in QtPrivate::QSlotObjectBase::call (a=0x7ffee734aa40, r=0x7ffee734c3d0, this=0x56426ab03180) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x56426aa073d0, signal_index=3, argv=0x7ffee734aa40) at kernel/qobject.cpp:3925 The reporter indicates this bug may be a duplicate of or related to bug 438721, bug 474993, bug 478265. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478502] project plugin is slowing down kate start
https://bugs.kde.org/show_bug.cgi?id=478502 --- Comment #2 from Gerhard S. --- > Try disabling the setting above and that should fix the issue for you > hopefully I'm trying to find a solution for my colleagues. Is there no config option I can put somewhere in /etc or /usr to disable certain plugins? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478502] New: project plugin is slowing down kate start
https://bugs.kde.org/show_bug.cgi?id=478502 Bug ID: 478502 Summary: project plugin is slowing down kate start Classification: Applications Product: kate Version: 22.04.1 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: gerhard.stran...@airbus.com Target Milestone: --- SUMMARY *** When launching kate, it takes "forever" before the GUI comes up. *** STEPS TO REPRODUCE Unfortunately, I don't know what to do. OBSERVED RESULT When launching kate, it takes "forever" before the GUI comes up. When I do an strace, I can see that kate is opening every file in a directory with lots of them, probably the last directory in use. Sometimes it's doing a git ls-remote, causing the git server to overload if everyone starts multiple kates in directories with lots of files. EXPECTED RESULT quick start of an empty kate, no matter how many files there are in some directories that are not currently in use. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: RHEL 8.8 (available in About System) KDE Plasma Version: plasma-desktop-5.24.7-1.el8.x86_64 from the EPEL repository KDE Frameworks Version: ? Qt Version: qt5-qtbase-5.15.3-1.el8.x86_64 ADDITIONAL INFORMATION It seems to be caused by the project plugin, this helps: sed -i s/kateprojectplugin=true/kateprojectplugin=false/ \ /home/$LOGNAME/.local/share/kate/anonymous.katesession Unfortunately, this is user-specific, so everyone would have to do that. How do I properly disable the project plugin for everyone? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478265] New: kdeconnect always crashes when phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=478265 Bug ID: 478265 Summary: kdeconnect always crashes when phone tries to connect Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gerha...@gmx.ch CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.11 Frameworks Version: 5.113.0 Operating System: Linux 6.2.0-39-generic x86_64 Windowing System: Wayland Distribution: KDE neon Testing Edition DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Not changing crashing during several updates of plasma packages in the last two months, kdeconnect systematicall crashes when the phone tries to pair or tries to connect to my computer. The crash can be reproduced every time. -- Backtrace (Reduced): #6 Device::reloadPlugins (this=this@entry=0x55aa0b895840) at ./core/device.cpp:184 #7 0x7f0aec1f7591 in Device::addLink (this=0x55aa0b895840, link=) at ./core/device.cpp:292 #8 0x7f0aec1f23a1 in Daemon::onNewDeviceLink (this=0x7ffd972db8b0, link=0x55aa0b9b3ef0) at ./core/daemon.cpp:170 #9 0x7f0aeaaf4394 in QtPrivate::QSlotObjectBase::call (a=0x7ffd972d9f20, r=0x7ffd972db8b0, this=0x55aa0b8ce3b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x55aa0b7bf520, signal_index=3, argv=0x7ffd972d9f20) at kernel/qobject.cpp:3925 The reporter indicates this bug may be a duplicate of or related to bug 438319, bug 438721. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478265] kdeconnect always crashes when phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=478265 --- Comment #1 from Gerhard Kulzer --- Created attachment 164008 --> https://bugs.kde.org/attachment.cgi?id=164008=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 456301] Kcalc high CPU usage when idle in background...
https://bugs.kde.org/show_bug.cgi?id=456301 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net --- Comment #2 from Gerhard --- Can confirm that on: Linux/KDE Plasma: openSUSE Tumbleweed 20230619 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Quite annoying because the CPU fans start to rev up after a while... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456765] Dolphin Wastebin Sound notifications not working when emptying the wastebin via Left Panel
https://bugs.kde.org/show_bug.cgi?id=456765 --- Comment #6 from Gerhard --- On openSuse Tumbleweed, this error was introduced between snapshot 20230422 (Plasma 5.27.4, KF 5.105, Qt 5.15.8, Apps 22.12.3) and 20230430 (Plasma 5.27.4, KF 5.105, Qt 5.15.9, Apps 23.04.0). KDE sounds work fine otherwise, but if you want to throw a file into the trash in Dolphin, the confirmation dialogue comes up without the usual notification sound. Maybe that helps tracing this regression. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456765] Dolphin Wastebin Sound notifications not working when emptying the wastebin via Left Panel
https://bugs.kde.org/show_bug.cgi?id=456765 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 469548] New: kmplot does not label scale tics
https://bugs.kde.org/show_bug.cgi?id=469548 Bug ID: 469548 Summary: kmplot does not label scale tics Classification: Applications Product: kmplot Version: 1.3.230390 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- Created attachment 158809 --> https://bugs.kde.org/attachment.cgi?id=158809=edit tics in coordinate system not numbered kmplot labels the axes correctly with x and y, but it doesn't label the tics. STEPS TO REPRODUCE 1. Draw any function 2. go to Configure | Diagram 3. make sure "show labels" is checked OBSERVED RESULT Only the horizontal and vertical axis label are drawn in the coordinate system, but no numbers at the tics, see screenshot EXPECTED RESULT tics should have numbers SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230508 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION KmPlot version: 1.3.23040 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468717] The hamburger menu next to the device name cannot be opened.
https://bugs.kde.org/show_bug.cgi?id=468717 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net --- Comment #2 from Gerhard --- Can confirm: Operating System: openSuse Tumbleweed KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465291] New: systemsettings autostart shows logon / logoff scripts with inconsistent path
https://bugs.kde.org/show_bug.cgi?id=465291 Bug ID: 465291 Summary: systemsettings autostart shows logon / logoff scripts with inconsistent path Classification: Applications Product: systemsettings Version: 5.26.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: nicolas.fe...@gmx.de Reporter: gsten...@gmx.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 155942 --> https://bugs.kde.org/attachment.cgi?id=155942=edit Autostart with inconsistent path of logon and logoff script When you add a logon and a logoff script to systemsettings -> autostart, logon scripts are shown without path, logoff scripts are shown with absolute path. This should be consistent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed 20230201 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373034] auto correction
https://bugs.kde.org/show_bug.cgi?id=373034 --- Comment #6 from Gerhard Lehnhoff --- @Justin Zobel, well, this error was reported 6 years ago. With newer versions this error seems not to be there anymore. Saying that, from my point of view this issues can be closed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 414266] Certain (not all) QQC2 buttons have vertically stretched and pixellated text when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=414266 --- Comment #23 from Gerhard --- Created attachment 153341 --> https://bugs.kde.org/attachment.cgi?id=153341=edit Buttons with horizontal line offset at 150% scaling -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 414266] Certain (not all) QQC2 buttons have vertically stretched and pixellated text when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=414266 --- Comment #22 from Gerhard --- Seems that this bugs has returned with Plasma 5.26.0 with Qt 5.15.6. One example is the mouse/keyboard battery in KInfoCenter (see screenshot). This was definitely fixed before. Reopen? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 413275] Kontact crashes when answering author
https://bugs.kde.org/show_bug.cgi?id=413275 Gerhard Riener changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 --- Comment #9 from Gerhard --- can confirm. openSUSE Tumbleweed 20220714 KDE Plasma 5.23.3 KDE-Frameworks 5.96 KDE-Apps 22.04.3 Qt 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 450872] Text input can't get out of Category input field.
https://bugs.kde.org/show_bug.cgi?id=450872 Gerhard Kulzer changed: What|Removed |Added CC||gerha...@gmx.ch -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 450872] New: Text input can't get out of Category input field.
https://bugs.kde.org/show_bug.cgi?id=450872 Bug ID: 450872 Summary: Text input can't get out of Category input field. Product: skrooge Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: gerha...@gmx.ch CC: steph...@mankowski.fr Target Milestone: --- SUMMARY Once I filled in something in the 'Category' field, I can't get out of it anymore even if I click into another field of move on with the TAB key. All text I enter somewhere else gets written into the 'Category' field STEPS TO REPRODUCE 1. click into 'Category' entry field and write something 2. continue with TAB of click into another entry field and write a text OBSERVED RESULT 3. despite the cursor showing up in the new field, the text is being annexed to 'Category' 4. It doesn't happen systematically, but more often than not 5. To get out of that trap I can change to another tab or Dashboard and come back EXPECTED RESULT 6. Text being written into the selected field SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] User names get elided quite early now that text size is bigger
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #8 from Gerhard --- Yes, the elision of our last names is definitely a problem, too. However, I think the font and widget size of the lock screen are perfect, so this is IMO what would be the best design for the login screen, too. As big as it is now, it's just a bit exaggerated. This could be a result of some scaling that the X server applies for my High-DPI monitor (4k 32"), too. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #6 from Gerhard --- Created attachment 147037 --> https://bugs.kde.org/attachment.cgi?id=147037=edit Login screen as it was with plasma 5.23.5 (plasma settings not applied) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #5 from Gerhard --- Created attachment 147036 --> https://bugs.kde.org/attachment.cgi?id=147036=edit Lock screen, sizing of fonts and widgets as it should be -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #4 from Gerhard --- Created attachment 147035 --> https://bugs.kde.org/attachment.cgi?id=147035=edit Login screen with plasma settings applied -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #3 from Gerhard --- Created attachment 147034 --> https://bugs.kde.org/attachment.cgi?id=147034=edit Login screen with plasma 5.24, plasma settings not applied -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 --- Comment #2 from Gerhard --- OK, the plasma settings were not synced. I did that now, and in fact, it became a bit better, but still the fonts are too big. I attached a few photos from my mobile (very unprofessional, but I don't know how to do screenshots of these screens). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450673] New: Fonts of user names became too big on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=450673 Bug ID: 450673 Summary: Fonts of user names became too big on SDDM login screen Product: plasmashell Version: 5.24.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net CC: visual-des...@kde.org Target Milestone: 1.0 Before plasma 5.24.0, the font size of the user names and avatar sizes on the SDDM login screen was very similar to the lock screen. This is IMO how it should be. Now after upgrading to >= 5.24.0, the fonts became too big and they now look clumsy. This is a regression somehow connected to plasma 5.24 I'm using a monitor with 144 DPI and have explicitly set the DPI in /etc/sddm.conf.d in a file containing [XDisplay] ServerArguments=-dpi 144 Setting it to t.ex. 142 DPI gives smaller fonts on the login screen, but that affects the avatars a lot, they become too small. So there's no way to work around the problem. I tried the KDE breeze theme and openSUSE, the effect is the same. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20220219 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450288] New: Night colors aren't applied if login takes place during the "night"
https://bugs.kde.org/show_bug.cgi?id=450288 Bug ID: 450288 Summary: Night colors aren't applied if login takes place during the "night" Product: systemsettings Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net CC: kwin-bugs-n...@kde.org Target Milestone: --- If you log in during the "night", i.e. before normal colors start to reapply, the system coloring is still on normal color. It should be on night colors at this time. If you wait until the point in time when normal colors start to apply, the night colors are applied all of a sudden. It seems to be some sort of initialisation problem. The system always seem to be in day color mode until it notices it's time to transition from night to normal colors. If you toggle night colors manually, the correct coloring is applied. I checked the times and location in the kcm modules, all seems correct. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TUmbleweed 20220213 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428990] High DPI scaling works on display :0 only
https://bugs.kde.org/show_bug.cgi?id=428990 --- Comment #8 from Gerhard --- Meanwhile, I'm on openSUSE Tumbleweed 20220112, usinf Plasma 5.23.5, KF 5.90, Qt 5.15.2, and digikam 7.4. The high DPI problem is gone now. digikam, showfoto and krita scale as desired on X displays > :0. :-) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 440794] Dolphin needs to be re-opened in order to access MTP device, after state changed between "No file transmission" and "File transmission"
https://bugs.kde.org/show_bug.cgi?id=440794 --- Comment #9 from Gerhard --- Sorry, at the end of comment 7 I meant "charge only" ;-) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 440794] Dolphin needs to be re-opened in order to access MTP device, after state changed between "No file transmission" and "File transmission"
https://bugs.kde.org/show_bug.cgi?id=440794 --- Comment #8 from Gerhard --- Tested with Plasma 5.23.4, KF 5.89 and Qt 5.15.2, Apps 21.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 440794] Dolphin needs to be re-opened in order to access MTP device, after state changed between "No file transmission" and "File transmission"
https://bugs.kde.org/show_bug.cgi?id=440794 Gerhard changed: What|Removed |Added Status|RESOLVED|REOPENED CC||gsten...@gmx.net Resolution|FIXED |--- --- Comment #7 from Gerhard --- This problem seems to be fixed only if you uncheck the box in Dolphins settings "Start | Open new folders in tabs". If you have this box checked, the dolphin instance seems to remember the first transfer state. If you t.ex. activate transfer mode MTP on the Android phone, and you open Dolphin via the system tray, it will correctly display all files on the phone. If you then change the USB-settings on the phone to PTP, and open Dolphin again via the system tray, the new tab will still show MTP! If you do the same without checking the setting "Start | Open new folders in tabs", Dolphin will create a new window each time and all will work file. This behaviour is a bit annoying because I very often forget to set the USB transfer mode when I connect the phone, but leave it in "change only". The result is that Dolphin will correctly show me an error. However, as I usually like to work with tabs in Dolphin", it will still show me this error after correcting the transfer mode and attempting to open the phone again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448088] New: Button "Properties | General | Explore in Filelight" does not work on MTP devices
https://bugs.kde.org/show_bug.cgi?id=448088 Bug ID: 448088 Summary: Button "Properties | General | Explore in Filelight" does not work on MTP devices Product: dolphin Version: 21.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gsten...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 145206 --> https://bugs.kde.org/attachment.cgi?id=145206=edit Error message after pressing "Explore in Filelight" If you right click on a folder in Dolphin, you can choose the "Properties" menu. In the tab "General", there is a button "Explore in Filelight" which normally opens Filelight which displays a graphical statistics about the directory's content. If you try to do the same with a folder of an MTP device like an Android phone, this function fails with an error message popping up that the folder could not be read. Note that it is possible to open the folder of the MTP device from within Filelight directly, so this is why I think Dolphin is to blame here. STEPS TO REPRODUCE 1. Plug in an Android phone by USB, choose the USB setting "Files" on the phone 2. Browse into the phone's file system with Dolphin, right click on any folder and press the button "Explore in Filelight" OBSERVED RESULT An error message pops up, see screenshot EXPECTED RESULT Filelight should be opened and show a statistics of the folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20220106 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar
https://bugs.kde.org/show_bug.cgi?id=334213 Gerhard Riener changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #18 from Gerhard Riener --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1
https://bugs.kde.org/show_bug.cgi?id=445561 --- Comment #19 from Gerhard Hellmann --- The problem still seems to be around in the final 5.0 version published just now. I still have the problem with the output which means I can't use 16bit integer, which is unfortunately the depth I am using all the time. Any way to work around this?! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1
https://bugs.kde.org/show_bug.cgi?id=445561 Gerhard Hellmann changed: What|Removed |Added CC||je...@jerri.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398783] Error message when sending emails, likely linked to failure to add "replied" tag
https://bugs.kde.org/show_bug.cgi?id=398783 --- Comment #4 from Gerhard Lehnhoff --- Created attachment 143164 --> https://bugs.kde.org/attachment.cgi?id=143164=edit Screenshot Identity -> Extras When I disable "Ordner für gesendete Nachrichten" in "Identities -> Extras" (I hope these are the correct translations, see attached screenshot) the error does not show up. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398783] Error message when sending emails, likely linked to failure to add "replied" tag
https://bugs.kde.org/show_bug.cgi?id=398783
--- Comment #3 from Gerhard Lehnhoff ---
Not sure, whether this helps:
{
"ancestorsAttributes": [
],
"ancestorsDepth": 2,
"collections": {
"type": "UID",
"value": "298"
},
"depth": 0,
"displayPref": false,
"enabled": false,
"fetchStats": true,
"indexPref": false,
"mimeTypes": [
],
"resource": "akonadi_imap_resource_4",
"response": false,
"syncPref": true,
"tag": 21180,
"type": "FetchCollections"
}
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 398783] Error message when sending emails, likely linked to failure to add "replied" tag
https://bugs.kde.org/show_bug.cgi?id=398783 Gerhard Lehnhoff changed: What|Removed |Added CC||pub...@glehnhoff.de --- Comment #2 from Gerhard Lehnhoff --- Same Problem: Das Ergebnis kann nicht im Objekt gespeichert werden. [LLCONFLICT] Resource akonadi_imap_resource_4 tries to modify item 49260 (3) (in collection 298) with revision 1; the item was modified elsewhere and has revision 2, aborting STORE. Whenever I send an email, this message turns up. In the send-folder is my message sent; however, marked as not read. I wonder whether this was like that before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442728] Data rate read/write does not work for md RAID devices
https://bugs.kde.org/show_bug.cgi?id=442728 --- Comment #1 from Gerhard --- Meanwhile, I've upgrade my openSUSE Tumbleweed installation a bit and it works now! SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20211012 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel 5.14.9 So, a major difference is the kernel version and that most Qt packages now have a version 5.15.2+kde222. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442728] New: Data rate read/write does not work for md RAID devices
https://bugs.kde.org/show_bug.cgi?id=442728 Bug ID: 442728 Summary: Data rate read/write does not work for md RAID devices Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Monitoring hard disk data rate read/write works fine for individual hard disks or NVMes, but if I try to monitor a soft raid (md device), the data rate is always zero. The interesting thing is that the data rate sensors of the hard disks that form the md device (sda and sdb in my case) show correct values. The behaviour is the same using ksysguard or the plasma widget. The sensor's names in ksysguard are disk/mdXXX_(X:XXX)/Rate/rblk disk/mdXXX_(X:XXX)/Rate/wblk SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20210916 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel 5.13.13 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 439032] crash at startup
https://bugs.kde.org/show_bug.cgi?id=439032 Gerhard changed: What|Removed |Added CC||vienna...@hotmail.com --- Comment #1 from Gerhard --- Hello there, exactly (incl. error-message) the same issue here. Steps to reproduce: - start Tellico It crashes with: tellico: symbol lookup error: tellico: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKcm, version Qt_5 KDE Neon with all the latest updates installed KDE-Plasma-Version: 5.22.3 KDE-Frameworks-Version: 5.83.0 Qt-Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 435422] kdeinit5 crashes after screenshot with spectacle
https://bugs.kde.org/show_bug.cgi?id=435422 --- Comment #1 from Gerhard --- Created attachment 137381 --> https://bugs.kde.org/attachment.cgi?id=137381=edit backtrace of kdeinit5 after showing a thumbnail of spectacle in the notification area -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 435422] New: kdeinit5 crashes after screenshot with spectacle
https://bugs.kde.org/show_bug.cgi?id=435422 Bug ID: 435422 Summary: kdeinit5 crashes after screenshot with spectacle Product: kio-extras Version: 20.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- If a screenshot is triggered by a keyboard shortcut, a thumbnail of the screenshot is shown in the notification area. Shortly after, a message is shown in the notification area that kdeinit5 has crashed. See attachment for a backtrace. STEPS TO REPRODUCE 1. Set keyboard shortcut to spectacle, t.ex. Shift + Printscreen to take a snapshot of the whole desktop 2. Press the shortcut 3. Observe the notification bar. OBSERVED RESULT a thumbnail of the screenshot is correctly shown in the notification area, followed by a crash notification of kdeinit5 This worked fine in KDE a few weeks ago. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumbleweed KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 434484] New: battery fill indicators not perfectly horizontal
https://bugs.kde.org/show_bug.cgi?id=434484 Bug ID: 434484 Summary: battery fill indicators not perfectly horizontal Product: kinfocenter Version: 5.21.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Energy Information Assignee: k...@privat.broulik.de Reporter: gsten...@gmx.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 136730 --> https://bugs.kde.org/attachment.cgi?id=136730=edit Screenshot of energy information tab There's a small graphical glitch, the battery indicators for mouse and keyboard aren't perfectly horizontal, but slighly tilted by 1 to 2 pixels, see attached screenshot. Maybe relevant in this context, I'm using a high DPI monitor (144 dpi) and set the scaling to 150%. Linux/KDE Plasma: openSuse Tumbleweed 20210312 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 432917] KInfocenter detects keyboard battery as mouse battery
https://bugs.kde.org/show_bug.cgi?id=432917 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 345697] Add Layout only lists German, Swiss not German
https://bugs.kde.org/show_bug.cgi?id=345697 --- Comment #5 from Gerhard Dittes --- (In reply to Justin Zobel from comment #4) > I've just tested against systemsettings 5.20.2 and I can't reproduce this > issue, the ger language shows EurKEY (US), English (US) and German layouts. > > Can you please test and confirm if this issue is still occurring or if this > bug report can be marked as resolved. I'm setting status to "needsinfo" > pending your response, please change back to "reported" or "resolved" when > you respond, thanks Jonathan. I can confirm that the issue seems to be resolved meanwhile also for me. Sysinfo: Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.0-1-amd64 OS Type: 64-bit Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428990] High DPI scaling works on display :0 only
https://bugs.kde.org/show_bug.cgi?id=428990 --- Comment #5 from Gerhard --- Good point, in fact, it's quite a lot of programs that suffer from this problem. I tried krita, k3b, kdenlive, showfoto, gwenview (best seen if they have a splash at startup). However, gimp works correctly on both screens. Maybe it only affects Qt applications? /Gerhard -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428990] High DPI scaling works on display :0 only
https://bugs.kde.org/show_bug.cgi?id=428990 --- Comment #2 from Gerhard --- #> echo $QT_SCREEN_SCALE_FACTORS DisplayPort-0=1.5;DisplayPort-1=1.5;HDMI-A-0=1.5;HDMI-A-1=1.5; It's the same on both displays :0 and :1 /Gerhard -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428990] New: High DPI scaling works on display :0 only
https://bugs.kde.org/show_bug.cgi?id=428990 Bug ID: 428990 Summary: High DPI scaling works on display :0 only Product: digikam Version: 7.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- In the settings dialogue | Miscellaneous, tab "System" there are two settings about high DPI, "Use high DPI scaling from the screen factor" and "Use pixmaps with high DPI resolution". The settings work as expected if the KDE session uses display :0. However, if digikam is started in a session using another display, it no longer works, i.e. fonts and images are too small on a high DPI screen. STEPS TO REPRODUCE 1. log in as first user, start digikam, set the two options named above and restart digikam 2. observe the splash screen on startup is bigger, i.e. the option works 3. start a new KDE session with the same user and start digikam OBSERVED RESULT high DPI scaling no longer works EXPECTED RESULT should be independent of the display SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20201108 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION DPI set to 144, 144 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428616] Group of sensors always has black color in the line graph
https://bugs.kde.org/show_bug.cgi?id=428616 --- Comment #3 from Gerhard --- Created attachment 133031 --> https://bugs.kde.org/attachment.cgi?id=133031=edit Screenshot of system monitor widget after adding a group of sensors Note that all CPU load sensors are black in the graph -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428616] Group of sensors always has black color in the line graph
https://bugs.kde.org/show_bug.cgi?id=428616 --- Comment #2 from Gerhard --- Created attachment 133030 --> https://bugs.kde.org/attachment.cgi?id=133030=edit Screenshot before adding a group of sensors -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428678] New: Plasma wayland crashes on login
https://bugs.kde.org/show_bug.cgi?id=428678 Bug ID: 428678 Summary: Plasma wayland crashes on login Product: plasmashell Version: 5.20.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gerhard.rie...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.2) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.1-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: login to new plasma wayland session this always happens when I log in. Plasma then restarts and works as expected The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 8986] [New LWP 9024] [New LWP 9033] [New LWP 9034] [New LWP 9035] [New LWP 9036] [New LWP 9182] [New LWP 9192] [New LWP 9222] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f2a02505e7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f2a003ff840 (LWP 8967))] Thread 10 (Thread 0x7f29cd5f4640 (LWP 9222)): #0 0x7f2a01a61082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2a0289792b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x560526a54070) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x7f29d0010d40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f2a04547b57 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f2a04549fe9 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7f2a02891911 in QThreadPrivate::start (arg=0x7f29d0010ca0) at thread/qthread_unix.cpp:329 #6 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #7 0x7f2a02510ccf in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f29e29f3640 (LWP 9192)): #0 0x7f2a02505e7f in poll () from /lib64/libc.so.6 #1 0x7f2a00ed6fbe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2a00ed70df in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2a02ac85cb in QEventDispatcherGlib::processEvents (this=0x7f29d0005d50, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2a02a6fa1b in QEventLoop::exec (this=this@entry=0x7f29e29f2c80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f2a028907ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f2a0449b926 in ?? () from /usr/lib64/libQt5Quick.so.5 #7 0x7f2a02891911 in QThreadPrivate::start (arg=0x7f29f00a9360) at thread/qthread_unix.cpp:329 #8 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2a02510ccf in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f29e21ca640 (LWP 9182)): #0 0x7f2a01a61082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2a0289792b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x560526b5d480) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x560526a20f50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f2a04547b57 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f2a04549fe9 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7f2a02891911 in QThreadPrivate::start (arg=0x560526a20eb0) at thread/qthread_unix.cpp:329 #6 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #7 0x7f2a02510ccf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f29f5155640 (LWP 9036)): #0 0x7f2a01a61082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f29f703bedb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f29f703b727 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2a02510ccf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f29f5956640 (LWP 9035)): #0 0x7f2a01a61082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f29f703bedb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f29f703b727 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2a02510ccf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f29f6157640 (LWP 9034)): #0 0x7f2a01a61082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f29f703bedb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f29f703b727 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f2a01a5aeb1 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2a02510ccf in clone () from /lib64/libc.so.6
[plasmashell] [Bug 428616] New: Group of sensors always has black color in the line graph
https://bugs.kde.org/show_bug.cgi?id=428616 Bug ID: 428616 Summary: Group of sensors always has black color in the line graph Product: plasmashell Version: 5.20.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 When adding a group of sensors, t.ex. [Group] CPU(%) to the new system monitor sensor 1.0 widget, after pressing "Apply", this group is correctly expanded to individual sensors with individual colors in the configuration dialogue. However, these colors aren't used in the line graph, it's always black. STEPS TO REPRODUCE 1. Open configuration of system monitor wiget "CPU" 2. Go to sensor details, click into free space in edit box "sensors". Choose [Group] CPU / [Group] CPU(%) 3. Press "Apply" OBSERVED RESULT Group is expanded to individial CPU load with correct colors in the edit box. In the line graph, all sensors of the group are black EXPECTED RESULT The colors as in the edit box shall be used SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20201030 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423526] "Switch user" functionality has disappeared from Kicker and Kickoff
https://bugs.kde.org/show_bug.cgi?id=423526 Gerhard changed: What|Removed |Added CC||gsten...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417147] Not possible to add a blank when markdown preview pane is open
https://bugs.kde.org/show_bug.cgi?id=417147 --- Comment #1 from Gerhard Riener --- I have exactly the same problem on opensuse tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417147] Not possible to add a blank when markdown preview pane is open
https://bugs.kde.org/show_bug.cgi?id=417147 Gerhard Riener changed: What|Removed |Added CC||gerhard.rie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 426943] New: Composer settings dialog: Word wrap at column is limited to 78
https://bugs.kde.org/show_bug.cgi?id=426943 Bug ID: 426943 Summary: Composer settings dialog: Word wrap at column is limited to 78 Product: kmail2 Version: 5.15.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- SUMMARY Behind the item "Word wrap at column" in the settings dialogue of the email composer there's a spin box. The range of values you can enter is limited to 78 which is too small number. STEPS TO REPRODUCE 1. open Configure, select composer 2. click check box "Word wrap at column" 3. try to increase value beyond 78 OBSERVED RESULT stays at 78 EXPECTED RESULT Reasonable limit would be maybe 200 Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 386315] Media Frame widget memory leak
https://bugs.kde.org/show_bug.cgi?id=386315 --- Comment #10 from Gerhard --- The bug is still present. I tried it on Plasma 5.19.5,KF 5.73.0 on openSUSE Tumbleweed If you leave the change interval to 10 sec and show a slide show with hundrets of images (jpeg, 3 to 5 MB each), my system memory of 32 GB is eaten up within half a day. You can easily see with KInfocenter / Memory tab how each new image eats up more and more memory. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 386315] Media Frame widget memory leak
https://bugs.kde.org/show_bug.cgi?id=386315 Gerhard changed: What|Removed |Added Status|RESOLVED|REOPENED CC||gsten...@gmx.net Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422095] New: Bad printout quality of kmail
https://bugs.kde.org/show_bug.cgi?id=422095 Bug ID: 422095 Summary: Bad printout quality of kmail Product: kmail2 Version: 5.14.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- Printing any mail from kmail2 to a printer or to pdf file results in a printout that has a low resolution and is slightly blurred. On a real printer, the printout shows small dithered "clouds" around the text. If you print to a pdf, the text has a low resolution. It seems as if the text is printed out as some sort of graphics, even if it's plain text. The expected result is that the printed text is crisp and if printed to pdf, that you can change the zoom in a pdf-viewer and the text stay crisp. SOFTWARE/OS VERSIONS openSUSE Tumbleweed KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.14.1 ADDITIONAL INFORMATION I can rule out problems with the printer or printer driver. Printout from other KDE apps like kate just work perfectly. I toggled the setting "print background color and pictures", but it's the same. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420175] New: Not possible to set a default web browser in Default Applications
https://bugs.kde.org/show_bug.cgi?id=420175 Bug ID: 420175 Summary: Not possible to set a default web browser in Default Applications Product: systemsettings Version: 5.18.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_componentchooser Assignee: plasma-b...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- In the Default Applications module, it's not possible to apply any changes of the default web browser. The UI always opens up with the radio button being active on the custom command text field. It's possible to change the radio button to something else, but the "Apply" button on the bottom right never gets active. If a change has been done on the settings page and it is left, a dialogue would normally pop up whether to discard the changes or not, but this never happens, too. STEPS TO REPRODUCE 1. Go to Default Applications / Web browser 2. Choose another browser 3. Try to apply the change OBSERVED RESULT "Apply" button stays inactive EXPECTED RESULT "Apply" should become active SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418437] Global Menu causes thunderbird to crash when using enigmail (pgp extension)
https://bugs.kde.org/show_bug.cgi?id=418437 --- Comment #4 from Gerhard Dittes --- All right, thanks! I've meanwhile created a corresponding bug report over there: https://bugzilla.mozilla.org/show_bug.cgi?id=1622852 Regards, Gerhard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 --- Comment #8 from Gerhard Dittes --- Hi Nate, thanks for your active contribution here! Of course lots of us do not have strong feelings about this -- me neither! ;-) But one should take into account that people discussing here, are (most likely) longtime Plasma users and therefore already used to it ... at least kind of. Users, trying Plasma the first time, form also a party out there -- potentially (and hopefully) the biggest party we also want to give a warm welcome... ;-) Imho, it's no big deal in neither direction. Leaving it as it is, or changing the default ... But doing one thing -- even if it's a small thing -- differently than others, should imho provide profound arguments for doing so. (Filip and veggero seem to feel my way, by the way... :-) ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418437] Global Menu causes thunderbird to crash when using enigmail (pgp extension)
https://bugs.kde.org/show_bug.cgi?id=418437 Gerhard Dittes changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #2 from Gerhard Dittes --- Hi David, I guess you've overseen something. Thunderbird works quite fine in every situation (and on every desktop (and OS)). It only crashes if one makes use of Plasma's "Globel Menu" widget. (If you don't use the widget and stay with vanilla Plasma, everything's fine!) I don't think that non-KDE developers develop against an extension of Plasma, do you? ;-) Imho, whatever the reason might be, "Global Menu" widget should be improved to not cause other applications to crash. Regards, Gerhard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418437] Global Menu causes thunderbird to crash when using enigmail (pgp extension)
https://bugs.kde.org/show_bug.cgi?id=418437 Gerhard Dittes changed: What|Removed |Added CC||markus.heidelb...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418437] New: Global Menu causes thunderbird to crash when using enigmail (pgp extension)
https://bugs.kde.org/show_bug.cgi?id=418437 Bug ID: 418437 Summary: Global Menu causes thunderbird to crash when using enigmail (pgp extension) Product: plasmashell Version: master Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: g-...@web.de CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Thunderbird crashes when trying to write an email. This happens right after clicking on the "write" button -- but only if enigmail is enabled! "Opening" the corresponding new window (for writing) might be the cause, as this should actually lead to update the global menu entries. (It also happens when trying to respond to an email.) I've raised the severity to major, as not being able to write encrypted emails could have critical impact (at least for some people). STEPS TO REPRODUCE 1. Open Thunderbird 2. Enable enigmail extension 3. Click on "write" button OBSERVED RESULT Crash of (whole) Thunderbird. EXPECTED RESULT New window should be opened in order to be able to start writing. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31,1 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 Gerhard Dittes changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Gerhard Dittes --- Hi, I just want to point out (again) that "arrangement in columns" had also been standard on our side till the "rejection of desktop icons" took place with "Plasma 4" coming out. I'm quite sure that the switch to "rows" (only) took place as part of the introduction of the "folderview plasmoid"...: - KDE 3: https://upload.wikimedia.org/wikipedia/commons/d/d7/KDE_3.0n.jpg - Plasma 4: https://kde.org/announcements/4.1/screenshots/desktop.png ...but with the _reintroduction_ of "standardly showing icons on the desktop" (Plasma >= 5.10), I really think one should think about "earlier" behavior/settings/thoughts, too. Again, this is not a big deal and it's probably an extremely minor issue. But as KDE/Plasma is still kinda famous for its complexity due to its massive configuration abilities, it's just (/ even more) important to deliver the best default configuration possible... (I'm gonna reopen this issue in the hope to give some more awareness/time for overthinking...) Thx & regards, Gerhard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 --- Comment #2 from Gerhard Dittes --- Hi David, thanks for your quick reply! I guess we've been talking at cross purposes. I already know the option to change the mentioned behavior. And of course you're right that defaults are very subjective! But my thoughts are based on the basis of providing something as default what people are already familiar with. Also, I'm not referring to file managers (in general). Just talking about the Desktop in particular (what only from a technically standpoint could be seen as a file manager). Do you now any other desktop environment arranging icons in a row? ;-) Please have a look at these desktops (arranging in columns): - Windows: https://upload.wikimedia.org/wikipedia/en/f/fa/Windows_10_1909_Desktop.png - MacOSX: https://en.wikipedia.org/wiki/Mac_OS_X_Jaguar#/media/File:Jaguar_on_G4.png - Ubuntu: https://en.wikipedia.org/wiki/Ubuntu#/media/File:Ubuntu_19.10_Eoan_Ermine.png - Mate, XFCE, Cinnamon, ... I know that you guys have a lot of other (much more) important stuff to work on. And this would be only a minor improvement (imho)... ...perhaps you reconsider one day. Thanks and keep on your excellent work, Gerardo -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 Gerhard Dittes changed: What|Removed |Added CC||markus.heidelb...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 Gerhard Dittes changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] New: Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 Bug ID: 418339 Summary: Improve default icon arrangement on desktop Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: g-...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 On a freshly installed plasma desktop, icons (on the desktop) are arranged "in rows", what imho is not a sane "default"! The 2 main reasons, why it would be a better solution to standardly arrange icons "in columns" are the following: 1. Other common desktop environments (Linux, Windows, MacOS) arrange their icons in columns, too! Therefore, new users would not be somewhat confused (or forced to reconfigure), when trying plasma the first time. 2. Usually, users use "landscape" displays! If icons are arranged in column, it's (normally) much easier to "drag & drop" files between the desktop and other applications (e.g. dolphin): ++ | o o +---+ | | o o | dolphin | | | o o | o o o o o | | | o| o o o o o | | | o| o o o | | | o+---+ | ++ Please consider changing the mentioned default behavior (back to where it was even on KDE <= version 3). Thx & regards, Gerhard (alias Gerardo) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385862] Introduce standard shortcuts for switching desktops and moving windows in a certain direction
https://bugs.kde.org/show_bug.cgi?id=385862 --- Comment #7 from Gerhard Dittes --- Yeah, thanks! :-) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417147] New: Not possible to add a blank when markdown preview pane is open
https://bugs.kde.org/show_bug.cgi?id=417147 Bug ID: 417147 Summary: Not possible to add a blank when markdown preview pane is open Product: kate Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugin-preview Assignee: kwrite-bugs-n...@kde.org Reporter: gerhard.rie...@gmail.com Target Milestone: --- SUMMARY When Writing and the markdown preview is open it is not possible to add a blank. STEPS TO REPRODUCE 1. Start new markdown file 2. Open markdown preview pane 3. Write a text containing blanks OBSERVED RESULT Blanks are not written in the md file EXPECTED RESULT blanks are written in the md file SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.4.14 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408878] 'Open with' shows nothing
https://bugs.kde.org/show_bug.cgi?id=408878 Gerhard Hoogterp changed: What|Removed |Added CC||gerh...@frappe.xs4all.nl --- Comment #12 from Gerhard Hoogterp --- For me the solution was in the directory /etc/xdg/menus As there Digikam was searching for an file applications.menu which wasn't available there. I symbolic linked the file kde4-applications.menu t0 applications.menu which solved the problem. The "open with" menu was filled with the expected applications. so: cd /etc/xdg/menus sudo ln -s kde4-applications.menu applications.menu Worked for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414562] New: drag-and-drop to kmail crashes plasma
https://bugs.kde.org/show_bug.cgi?id=414562 Bug ID: 414562 Summary: drag-and-drop to kmail crashes plasma Product: plasmashell Version: 5.17.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gerhard.rie...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.3) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: drag-and-drop atttachment to a new message. Kmail was opened with kontact suite The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff9d7847800 (LWP 18535))] Thread 18 (Thread 0x7ff9791eb700 (LWP 25030)): #0 0x7ff9d90d76a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff9d9bf70af in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x564e6cc99390) at thread/qwaitcondition_unix.cpp:146 #2 0x7ff9d9bf70af in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x564e6cc99210, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7ff9d9bf7199 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x564e6cc99218, mutex=0x564e6cc99210, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7ff9db8f92f9 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7ff9db8f959d in () at /usr/lib64/libQt5Quick.so.5 #6 0x7ff9d9bf11a2 in QThreadPrivate::start(void*) (arg=0x564e6cc99190) at thread/qthread_unix.cpp:360 #7 0x7ff9d90d0f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7ff9d98784af in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7ff9a0ad1700 (LWP 25023)): #0 0x7ff9d90d76a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff9d9bf70af in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x564e61cc3d90) at thread/qwaitcondition_unix.cpp:146 #2 0x7ff9d9bf70af in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x564e65c76470, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7ff9d9bf7199 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x564e65c76478, mutex=0x564e65c76470, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7ff9db8f92f9 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7ff9db8f959d in () at /usr/lib64/libQt5Quick.so.5 #6 0x7ff9d9bf11a2 in QThreadPrivate::start(void*) (arg=0x564e65c763f0) at thread/qthread_unix.cpp:360 #7 0x7ff9d90d0f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7ff9d98784af in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7ff97a5ed700 (LWP 19775)): #0 0x7ff9d90d76a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff9d9bf70af in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x564e691aaa60) at thread/qwaitcondition_unix.cpp:146 #2 0x7ff9d9bf70af in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x564e5ffbba80, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7ff9d9bf7199 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x564e5ffbba88, mutex=0x564e5ffbba80, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7ff9db8f92f9 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7ff9db8f959d in () at /usr/lib64/libQt5Quick.so.5 #6 0x7ff9d9bf11a2 in QThreadPrivate::start(void*) (arg=0x564e5ffbba00) at thread/qthread_unix.cpp:360 #7 0x7ff9d90d0f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7ff9d98784af in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7ff97adee700 (LWP 19674)): #0 0x7ff9d83bc5f4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff9d837119e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff9d837139f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff9d9e0f98b in QEventDispatcherGlib::processEvents(QFlags) (this=0x564e61e1ad90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ff9d9db80cb in QEventLoop::exec(QFlags) (this=this@entry=0x7ff97adedda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7ff9d9bf0021 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7ff9d9bf11a2 in QThreadPrivate::start(void*) (arg=0x564e630ddcc0) at thread/qthread_unix.cpp:360 #7 0x7ff9d90d0f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7ff9d98784af in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7ff97b5ef700 (LWP
[systemsettings] [Bug 374474] Add buttons which pause and resume baloo indexing
https://bugs.kde.org/show_bug.cgi?id=374474 --- Comment #7 from Gerhard Dittes --- (In reply to Nate Graham from comment #6) > I've submitted a patch that adds this feature: > https://phabricator.kde.org/D25447 Very nice! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374474] Add buttons which stop and start baloo indexing
https://bugs.kde.org/show_bug.cgi?id=374474 --- Comment #5 from Gerhard Dittes --- Hi, any news on this? I know, it's not that urgent (as we are not talking about a major bug or the like), but nevertheless this issue exists for quite some time now and it would be really nice to see it resolved for upcoming Plasma LTS version... ...especially as we claim that usability is one of our main focuses these days. Thx & regards, Gerhard -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374474] Add buttons which stop and start baloo indexing
https://bugs.kde.org/show_bug.cgi?id=374474 Gerhard Dittes changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391315] Blurred previews for landscape images on desktop
https://bugs.kde.org/show_bug.cgi?id=391315 Gerhard Dittes changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413432 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 Gerhard Dittes changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=391315 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391315] Blurred previews for landscape images on desktop
https://bugs.kde.org/show_bug.cgi?id=391315 Gerhard Dittes changed: What|Removed |Added Flags||VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413833] Odd (or missing) location to start/suspend file indexer
https://bugs.kde.org/show_bug.cgi?id=413833 Gerhard Dittes changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413833] Odd (or missing) location to start/suspend file indexer
https://bugs.kde.org/show_bug.cgi?id=413833 --- Comment #2 from Gerhard Dittes --- Created attachment 123731 --> https://bugs.kde.org/attachment.cgi?id=123731=edit Also suspending should rather be done via "System Settings" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413833] Odd (or missing) location to start/suspend file indexer
https://bugs.kde.org/show_bug.cgi?id=413833 --- Comment #1 from Gerhard Dittes --- Created attachment 123730 --> https://bugs.kde.org/attachment.cgi?id=123730=edit It's rather a "setting" than an "information" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413833] New: Odd (or missing) location to start/suspend file indexer
https://bugs.kde.org/show_bug.cgi?id=413833 Bug ID: 413833 Summary: Odd (or missing) location to start/suspend file indexer Product: systemsettings Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: g-...@web.de Target Milestone: --- If the "file indexer" is not running for whatever reason, you cannot start it from "the obvious" location, aka "System Settings". Instead you have to open up "Info Center" to perform such actions. (Please see attached screenshots.) IMHO doing such a setting should be placed where most people expect it to be. InfoCenter indicates to retrieve information rather than changing it. Please consider moving this feature to "System Settings". SOFTWARE/OS VERSIONS Sistema operativo: Debian GNU/Linux Versión de KDE Plasma: 5.14.5 Versión de Qt: 5.12.5 Versión de KDE Frameworks: 5.62.0 Versión del kernel: 5.2.0-3-amd64 Tipo de OS: 64 bits Procesadores: 8 × Intel® Core™ i7-4770 CPU @ 3.40GHz Memoria: 15,7 GiB de RAM ADDITIONAL INFORMATION This issue is also valid for current/newest version of plasma. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413812] Discover displays empty area for screenshots that are invalid
https://bugs.kde.org/show_bug.cgi?id=413812 Gerhard Dittes changed: What|Removed |Added CC||g-...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Sometimes left and right margins of full-size preview image sheets are too large and image is too small
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #14 from Gerhard Dittes --- @Nate: Inspired by you, I did some tests on Tumbleweed, too. There (as well as on other distributions) I've found another related issue: Sometimes Discover reserves space for thumbnails even though no image is shown finally. Looks pretty untidy. Please see newly attached screenshot (showing entry for virtualbox). (Could we tackle this problem here, too?) Thx! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Sometimes left and right margins of full-size preview image sheets are too large and image is too small
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #13 from Gerhard Dittes --- Created attachment 123717 --> https://bugs.kde.org/attachment.cgi?id=123717=edit Discover produces empty space for "non-existent/transparent" images -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Sometimes left and right margins of full-size preview image sheets are too large and image is too small
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #12 from Gerhard Dittes --- Hi, as suggested, I've meanwhile filed a corresponding bug in Debian (to potentially tackle one of the mentioned problems there): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944117 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Left and right margins of full-size preview image sheets are sometimes too large
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #8 from Gerhard Dittes --- @Nate: Thanks for your information. The distro-thing is really a pity, as I actually use Debian stable/testing (where I experience the same issues, too). I guess, that all Debian derivatives suffer from the same circumstance... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #6 from Gerhard Dittes --- FWIW, the mentioned issues are valid for (most likely all) previous versions of Plasma, too. Regards, Gerhard (aka Gerardo) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 Gerhard Dittes changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #5 from Gerhard Dittes --- Created attachment 123594 --> https://bugs.kde.org/attachment.cgi?id=123594=edit Better make the thumbnail not clickable... ;-) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #3 from Gerhard Dittes --- Created attachment 123592 --> https://bugs.kde.org/attachment.cgi?id=123592=edit Insane (tiny) size compared to thumbnail -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #4 from Gerhard Dittes --- Created attachment 123593 --> https://bugs.kde.org/attachment.cgi?id=123593=edit Pretty unsharp -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413629] Discover often shows messy images even if preview images/thumbnails are looking good
https://bugs.kde.org/show_bug.cgi?id=413629 --- Comment #2 from Gerhard Dittes --- Created attachment 123591 --> https://bugs.kde.org/attachment.cgi?id=123591=edit Insane margins (especially the left and right one) -- You are receiving this mail because: You are watching all bug changes.
