[NeoChat] [Bug 483220] New: Dark theme readability issues on non-KDE environment
https://bugs.kde.org/show_bug.cgi?id=483220 Bug ID: 483220 Summary: Dark theme readability issues on non-KDE environment Classification: Applications Product: NeoChat Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: porke...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166948 --> https://bugs.kde.org/attachment.cgi?id=166948&action=edit Screenshots of many places with dark theming issues outside of KDE. SUMMARY Many places have readability issues with dark theme on a non-KDE environment (here, Gnome). This includes invisible or almost icons, checkboxes, radio buttons for what I could spot. STEPS TO REPRODUCE 1. Launch NeoChat in Gnome, and inspect the different places in the application. OBSERVED RESULT Many invisible or almost icons, radio buttons, checkboxes, … EXPECTED RESULT Those should be easily visible and present to issues to be seen. . SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux, NeoChat 24.02 Qt Version: 6.6.2 ADDITIONAL INFORMATION With another computer I wanted to check that on Hyprland I'm playing a little bit with, but couldn't yet figure out how to request a dark version of the application. Screenshots attached as an archive to avoid having to add 11 screenshots one by one, as you can't do multiple attachments at once in Bugzilla. See also the "About NeoChat" part at the left of settings, which is easy to miss. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] Esc key is supposed to turn off the display but doesn't
https://bugs.kde.org/show_bug.cgi?id=466344 --- Comment #6 from Porkepix --- (In reply to Nate Graham from comment #5) > Ok looks like it's running. But those warnings make me think it might be be > working properly. > > What distro are you using? Up-to-date ArchLinux. This is a years-old setup (including KDE's install), with pretty much the default settings of the installation time. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] Esc key is supposed to turn off the display but doesn't
https://bugs.kde.org/show_bug.cgi?id=466344 --- Comment #4 from Porkepix --- $ systemctl status --user plasma-powerdevil.service ● plasma-powerdevil.service - Powerdevil Loaded: loaded (/usr/lib/systemd/user/plasma-powerdevil.service; static) Active: active (running) since Thu 2023-02-23 18:57:38 CET; 3 days ago Main PID: 1269 (org_kde_powerde) Tasks: 7 (limit: 9352) Memory: 5.9M CPU: 46.763s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service └─1269 /usr/lib/org_kde_powerdevil févr. 23 18:57:37 T470-clement systemd[976]: Starting Powerdevil... févr. 23 18:57:38 T470-clement systemd[976]: Started Powerdevil. févr. 23 18:57:38 T470-clement org_kde_powerdevil[1269]: org.kde.powerdevil: Handle button events action could not check for screen configuration févr. 25 14:21:26 T470-clement org_kde_powerdevil[1269]: org.kde.powerdevil: Failed to start suspend job "org.freedesktop.login1.OperationInProgress" "There's already a shutdown or sleep operation in progress" févr. 27 07:46:46 T470-clement org_kde_powerdevil[1269]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted févr. 27 07:46:51 T470-clement org_kde_powerdevil[1269]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] Esc key is supposed to turn off the display but doesn't
https://bugs.kde.org/show_bug.cgi?id=466344 --- Comment #2 from Porkepix --- X11; Wayland session isn't even available with base packages from default setup, I would need to install additional ones (which I can, though KDE isn't the main environment I'm using). Not many logs nor useful ones I think, but just incase, here's what can be found from journalctl after locking session and pressing esc a couple of times: ``` févr. 24 19:32:47 T470-clement kscreenlocker_greet[206224]: Qt: Session management error: networkIdsList argument is NULL févr. 24 19:32:47 T470-clement kscreenlocker_greet[206224]: file:///usr/lib/qt/qml/QtQuick/Controls.2/ToolButton.qml: QML IconImage: Error decoding: file:///usr/share/icons/breeze-dark/actions/24/edit-copy.svg: Unsupported image format févr. 24 19:32:47 T470-clement kscreenlocker_greet[206224]: kf.kirigami: Failed to find a Kirigami platform plugin févr. 24 19:32:47 T470-clement kscreenlocker_greet[206224]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed févr. 24 19:32:47 T470-clement plasmashell[1237]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner févr. 24 19:32:47 T470-clement kscreenlocker_greet[206224]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml:82:9: QML Image: Binding loop detected for property "sourceSize.height" févr. 24 19:32:47 T470-clement plasmashell[1237]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner févr. 24 19:32:49 T470-clement dbus-daemon[486]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.592' (uid=1000 pid=206224 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra") févr. 24 19:32:49 T470-clement dbus-daemon[486]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. févr. 24 19:32:49 T470-clement kscreenlocker_greet[206224]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found ``` -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 Porkepix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466345 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466345] Turn off keyboard backlight the same way as done for the display when using escape key
https://bugs.kde.org/show_bug.cgi?id=466345 Porkepix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466023 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] Esc key is supposed to turn off the display but doesn't
https://bugs.kde.org/show_bug.cgi?id=466344 Porkepix changed: What|Removed |Added Summary|Esc key is supposed to turn |Esc key is supposed to turn |off the display but |off the display but doesn't |doesn't.| See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466345 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466345] Turn off keyboard backlight the same way as done for the display when using escape key
https://bugs.kde.org/show_bug.cgi?id=466345 Porkepix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466344 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 Porkepix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466344 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] Esc key is supposed to turn off the display but doesn't.
https://bugs.kde.org/show_bug.cgi?id=466344 Porkepix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466023 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 --- Comment #6 from Porkepix --- Still seeing the same thing on 5.27.1, so I filed https://bugs.kde.org/show_bug.cgi?id=466344 and https://bugs.kde.org/show_bug.cgi?id=466345 Also, if the escape key is a toggle on/off for the display, maybe then it could start turned off but then bu turned back on by using the key? Anyway, let's see what happens with those two bugs first. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466345] New: Turn off keyboard backlight the same way as done for the display when using escape key
https://bugs.kde.org/show_bug.cgi?id=466345 Bug ID: 466345 Summary: Turn off keyboard backlight the same way as done for the display when using escape key Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: --- SUMMARY Follow-up bug requested on https://bugs.kde.org/show_bug.cgi?id=466023 but would also require fixing https://bugs.kde.org/show_bug.cgi?id=466344 for me >From what I was explained in #466023, escape key should turn the display off, so it could also toggle the keyboard backlight off or on on sync with the display. SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.27.1 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466344] New: Esc key is supposed to turn off the display but doesn't.
https://bugs.kde.org/show_bug.cgi?id=466344 Bug ID: 466344 Summary: Esc key is supposed to turn off the display but doesn't. Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: --- SUMMARY Follow-up bug to https://bugs.kde.org/show_bug.cgi?id=466023 Esc key is supposed to turn the display off from what I was said in #466023, but here it's only hiding media controllers and password input from lockscreen (so, it only displays date/time and lockscreen wallpaper), and display them again if I hit esc again (so, it's a toggle between those two states), but it never turn the display off. STEPS TO REPRODUCE 1. Lock the session 2. Press esc key 3. Display isn't turned off OBSERVED RESULT Display doesn't turn off EXPECTED RESULT Display should turn off SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.27.1 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Settings are pretty much defaults, but this is a years-old KDE setup so it might contain different defaults from today's. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 --- Comment #4 from Porkepix --- (In reply to Nate Graham from comment #3) > (In reply to Porkepix from comment #2) > > You might want to turn the screen off and locked while not putting the > > system to sleep, for example if you play music/radio on it. > For this use case, you can lock the screen and hit the Esc key to turn off > the display completely. So, I just learned it's supposed to do that, but for me it isn't: pressing esc just hide everything else than wallpapers and date/time, but it doesn't turn off the screen, nor does it for the keyboard backlight. > > Why would one lock its screen to watch a password input after that? > When using the lock screen as an old-school screensaver (e.g. with an > animated background) that you like to be able to see. This turns out to be a > surprisingly common thing for people to want to do, believe it or not. So, I didn't knew it could be animated, and I'm sorry if it sounded mean or unfriendly toward people, I didn't mean for that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 --- Comment #2 from Porkepix --- You might want to turn the screen off and locked while not putting the system to sleep, for example if you play music/radio on it. For a personal situation, I do so when going to sleep and had such behavior with other lockscreens, I found this pretty handy, and I never saw a situation where I manually lock my screen and… want to watch it after…? Why would one lock its screen to watch a password input after that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled can get blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 --- Comment #8 from Porkepix --- Okay* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled can get blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 --- Comment #7 from Porkepix --- Oka, I tried to lookup for information about these _KDE_NET_WM_DESKTOP_FILE or _GTK_APPLICATION_ID but couldn't find satisfactory enough ones. Are these supposed to be properties in the .desktop file? Is it something that you intend to have fixed by the distribution maintainers/packagers? Or the software developers themselves? For the latter I highly doubt some of these devs will bother managing the special case of every desktop environment/window manager/compositor, which is why I was looking for pretty standardized ways working for every environment: from the software I was running, not many of them were affected by such issues (at least for those I ran there, many are more casually launched). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466027] alt-tabbing after a media player was used in fullscreen and then quitted or put in windowed result in empty previews for Firefox and sometimes Thunderbird
https://bugs.kde.org/show_bug.cgi?id=466027 --- Comment #1 from Porkepix --- Created attachment 156528 --> https://bugs.kde.org/attachment.cgi?id=156528&action=edit Screenshot with both Firefox and Thunderbird Additional screenshot, where we can see that Firefox preview is completely empty while Thunderbird have the window decoration but everything else is empty. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled can get blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 --- Comment #4 from Porkepix --- (In reply to Vlad Zahorodnii from comment #3) > mpv disables compositing, so kwin stops providing previews and falls back to > displaying icons. > > Electron based applications don't provide desktop file hints, so kwin uses > whatever icons are provided in the X11 windows. Usually, those icons are low > resolution and look blurry when upscaled. It can be fixed if the application > provides _KDE_NET_WM_DESKTOP_FILE or _GTK_APPLICATION_ID properties. I don't know what are desktop file hints, but while Element is indeed an electron application, Alacritty isn't one. So, kwin isn't checking `/usr/share/icons/hicolor/` by itself at all? Shouldn't it? No idea about _KDE_NET_WM_DESKTOP_FILE or _GTK_APPLICATION_ID but it seems to be very DE-specific; I think the task switcher should be able to get the correct pictures by itself with generic locations, shouldn't it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled can get blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 Porkepix changed: What|Removed |Added Summary|Big icons in task switcher |Big icons in task switcher |when previews are disabled |when previews are disabled |get be blurry, despite |can get blurry, despite |qualitative enough icons|qualitative enough icons |available |available -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 --- Comment #2 from Porkepix --- Created attachment 156458 --> https://bugs.kde.org/attachment.cgi?id=156458&action=edit Screenshot with Alacritty blurry icon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 --- Comment #1 from Porkepix --- Created attachment 156457 --> https://bugs.kde.org/attachment.cgi?id=156457&action=edit Screenshot with Element blurry icon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 Porkepix changed: What|Removed |Added Product|plasmashell |kwin Component|Task Manager and Icons-Only |tabbox |Task Manager| Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466029] New: Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 Bug ID: 466029 Summary: Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: 1.0 SUMMARY When using a player such as mpv in fullscreen, it disables window previews in the task switcher (don't know why, and would definitely be interested to understand why - I just noticed GIMP shows the document we work on besides its own icon - it's still not the window preview anymore) When previews get disable, task switcher shows high quality icons. But for some software, the icon is blurry and shows a bad quality, despite having high quality material available. I don't know which size the task switcher is looking for, and at first I thought it was a bad quality conversion with Alacritty icon as, by looking into `/usr/share/icons/hicolor/` (I'm guessing this is where icons are picked from) I saw there was only a svg, svg that was able to be high quality whatever the size, but could end-up with a bad quality conversion to png. But then I noticed that Element was also affected. And element had a large choice of sizes available: ``` $ fd element /usr/share/icons/hicolor/ /usr/share/icons/hicolor/128x128/apps/io.element.Element.png /usr/share/icons/hicolor/16x16/apps/io.element.Element.png /usr/share/icons/hicolor/24x24/apps/io.element.Element.png /usr/share/icons/hicolor/256x256/apps/io.element.Element.png /usr/share/icons/hicolor/48x48/apps/io.element.Element.png /usr/share/icons/hicolor/512x512/apps/io.element.Element.png /usr/share/icons/hicolor/64x64/apps/io.element.Element.png /usr/share/icons/hicolor/96x96/apps/io.element.Element.png /usr/share/icons/hicolor/scalable/apps/io.element.Element.svg ``` See the screenshots I'll join STEPS TO REPRODUCE 1. Open affected software such as Element or Alacritty 2. Play a video with mpv in fullscreen mode so that previews get disabled 3. Use task switcher and see how these icons are blurry. OBSERVED RESULT Some icons are blurry in the task switcher when previews are off EXPECTED RESULT These icons shouldn't be blurry SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.27.0 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466027] alt-tabbing after a media player was used in fullscreen and then quitted or put in windowed result in empty previews for Firefox and sometimes Thunderbird
https://bugs.kde.org/show_bug.cgi?id=466027 Porkepix changed: What|Removed |Added Product|plasmashell |kwin Component|Task Manager and Icons-Only |tabbox |Task Manager| Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466027] New: alt-tabbing after a media player was used in fullscreen and then quitted or put in windowed result in empty previews for Firefox and sometimes Thunderbird
https://bugs.kde.org/show_bug.cgi?id=466027 Bug ID: 466027 Summary: alt-tabbing after a media player was used in fullscreen and then quitted or put in windowed result in empty previews for Firefox and sometimes Thunderbird Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: 1.0 Created attachment 156455 --> https://bugs.kde.org/attachment.cgi?id=156455&action=edit Screenshot of a messed-up preview for Firefox STEPS TO REPRODUCE 1. Open Firefox and Thunderbird 2. Play whatever video in mpv, and switch mpv to fullscreen. I don't know why, but in such modes, task switcher doesn't show window previews anymore but only big icons. (I'm btw curious why most applications doesn't shows preview in such situations - and even stranger, GIMP present a pseudo-preview, showing the picture we work on, but not the window itself) 3. Escape full screen or quit mpv. Firefox and sometimes Thunderbird previews will be messed up as visible in the joined screen. When Thunderbird's one is messed up, hovering it in the task switcher fixes the preview. For Firefox, the only way is to switch to the application completely. OBSERVED RESULT Messed-up previews. EXPECTED RESULT Previews shouldn't be messed up. SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.27.0 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 466023] New: Locking the screen manually should turn off display and keyboard backlight
https://bugs.kde.org/show_bug.cgi?id=466023 Bug ID: 466023 Summary: Locking the screen manually should turn off display and keyboard backlight Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: --- SUMMARY It's likely anyone doing a manual screenlock don't need to see anything on it in the next couple of seconds/minutes, so instead of waiting the timer that turns it off because of idling, locking the screen could just turn off display and keyboard backlight instantly, until a key is pressed. (A bonus could even be to have a way of turning them off from the lockscreen if they were accidentally awaken). SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.27.0 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465859] New: Audio applications can inhibit and prevent automatic screen lock
https://bugs.kde.org/show_bug.cgi?id=465859 Bug ID: 465859 Summary: Audio applications can inhibit and prevent automatic screen lock Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: porke...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Have automatic session lock after X minutes enabled 2. Use a software playing audio such as https://gitlab.gnome.org/World/Shortwave/ and have it play whatever you want 3. Wait the timer for the automatic session lock to pass: while dimming and display shutdown will happen, session lock won't OBSERVED RESULT Session doesn't lock EXPECTED RESULT While this behavior is perfectly fine and wished when playing video, it's not when only player audio. On top of that, this have a "dangerous" side-effect in that by reflexes one can type its session password because the screen is still shutdown, and notice too late that the password wasn't typed on the screen lock but on whatever application that's on foreground, and that can be eg. an IM client. SOFTWARE/OS VERSIONS ArchLinux Linux/KDE Plasma: 5.26.5 (available in About System) I'm not seeing an "About System", where should it be looked for? KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #161 from Porkepix --- (In reply to Nate Graham from comment #160) > The LMDB developers have responded and are asking for an affected database > file. > > For anybody who can reproduce this issue, I have three questions: > 1. Is it reliable? If you restart Baloo, does it immediately crash again? > 2. Is your database file below, say, 100 Mb? `balooctl status` will tell you. > 3. Are you willing to upload your database to a public location so the LMDB > developers can debug it? It's located at ~/.local/share/baloo/index For me, the crashes were kinda random, but (I'm not sure anymore), could happen during high usage computer, causing micro-freezes, or intensive writes (might be related, due to swap), especially, I sometimes suspected it would kind of dislike files that were only partially written and there constantly "reevaluated". Only bare feeling as I have no knowledge on how does it work here. If this might be related, the disk is a SSD and is fully encrypted through LUKS, which might cause read and write to be much more CPU-intensive. The file currently weight 2.4G. I disabled baloo quite a long time ago now, as you can see: .rw-r--r-- 2.4G clement 22 Feb 0:33 /home/clement/.local/share/baloo/index It would be hard to upload because, well, I would need to control content for privacy reasons to sanitize data, but it both seems it's a huge amount, and that I have no knowledge of data structure. But I can provide more information if I'm told how to do so. Looking at what you said above, the size is a lot bigger than it should be, so, maybe if the bug was considered to fixed and it was a database corruption the solution would be to wipe that file out? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #148 from Porkepix --- (In reply to Stefan Brüns from comment #147) > (In reply to Nate Graham from comment #146) > > I'm seeing at least three of these every day. :( Anything I can do to debug, > > Stefan? > > And I haven't seen any of these crashes on any of my systems - IIRC, ever. I > am indexing most of my disk, though I have excluded sources, so my index is > definitely not small either. > > There is no clear pattern. Purging the DB seems to help (which indicates the > internal structure got broken), but then sometimes the problem reappears. Well, to be honest, I never commented nor opened new bug as it seemed to be linked to this one and I saw some threads of people telling there was no point in opening anything new, and it might even be bothersome because devs were aware of the issue. But to give you an idea of how much of a problem this can be, I went through months on my Linux with some random freezes of the system, most of the time leading to full crash of the OS when it didn't un-freeze after several *minutes*. This stopped the day I disabled baloo from systemd. If this may help you, I'm not an exclusive KDE user, have several DE/WM installed and sometimes jump from one to another, and it seems that services like Baloo are started, whether KDE is started or not rather than being part of it, so may it conflict with other similar services such as Gnome's one? Can't tell, I don't know enough of all of this. But imho, this is clearly worth investigating when we talk about minutes OS freezes and most of the time full OS crashes. Unfortunately, the crashes were so sudden that I never found anything useful from journald nor dmesg. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 417976] New: Baloo got a complete crash with stack trace ; it is probably involved in system freezes and OS crashes
https://bugs.kde.org/show_bug.cgi?id=417976 Bug ID: 417976 Summary: Baloo got a complete crash with stack trace ; it is probably involved in system freezes and OS crashes Product: frameworks-baloo Version: 5.67.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: porke...@gmail.com Target Milestone: --- SUMMARY There's a crash report visible in systemctl STEPS TO REPRODUCE 1. Nothing specific, just use the computer and at some point it crashes. 2. 3. OBSERVED RESULT System freez or crashes. The freezes and crashes might be unrelated, I can't know for sure EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux, Plasma 5.18.1 (available in About System) KDE Plasma Version: 5.18.1 No other informations as I can't have them by the about menu: I installed several DE/WM on this computer and sometimes use one or another. The current crash report happened on a Gnome session, but it seems that Baloo service is anyway running everytime once instealled with the KDE DE, whether it's a KDE session or not. ADDITIONAL INFORMATION The system is encrypted through LUKS, which might explain heavier resource usage. Here's the stacktrace from journalctl: Feb 19 00:28:10 T470-clement systemd-coredump[46933]: Process 46873 (baloo_file) of user 1000 dumped core. Stack trace of thread 46880: #0 0x7f9592f89ce5 raise (libc.so.6 + 0x3bce5) #1 0x7f9593bdb6b0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x46b0) #2 0x7f9592f89d70 __restore_rt (libc.so.6 + 0x3bd70) #3 0x7f9592f89ce5 raise (libc.so.6 + 0x3bce5) #4 0x7f9592f73857 abort (libc.so.6 + 0x25857) #5 0x7f959252a753 n/a (liblmdb.so + 0x10753) #6 0x7f95925229a3 n/a (liblmdb.so + 0x89a3) #7 0x7f9592525d61 mdb_cursor_put (liblmdb.so + 0xbd61) #8 0x7f95925284ab mdb_put (liblmdb.so + 0xe4ab) #9 0x7f9593aa64d2 _ZN5Baloo10PositionDB3putERK10QByteArrayRK7QVectorINS_12PositionInfoEE (libKF5BalooEngine.so.5 + 0x284d2) #10 0x7f9593ac2551 _ZN5Baloo16WriteTransaction6commitEv (libKF5BalooEngine.so.5 + 0x44551) #11 0x7f9593ab1e50 _ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5 + 0x33e50) #12 0x556a44cc06a5 n/a (baloo_file + 0x196a5) #13 0x7f95935101f2 n/a (libQt5Core.so.5 + 0xcd1f2) #14 0x7f959350cfc6 n/a (libQt5Core.so.5 + 0xc9fc6) #15 0x7f959258546f start_thread (libpthread.so.0 + 0x946f) #16 0x7f959304d3d3 __clone (libc.so.6 + 0xff3d3) Stack trace of thread 46876: #0 0x7f9593042abf __poll (libc.so.6 + 0xf4abf) #1 0x7f9591d62120 n/a (libglib-2.0.so.0 + 0x6c120) #2 0x7f9591d621f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1) #3 0x7f9593741020 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2fe020) #4 0x7f95936e74cc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a44cc) #5 0x7f959350be52 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc8e52) #6 0x7f9593ae3b28 n/a (libQt5DBus.so.5 + 0x15b28) #7 0x7f959350cfc6 n/a (libQt5Core.so.5 + 0xc9fc6) #8 0x7f959258546f start_thread (libpthread.so.0 + 0x946f) #9 0x7f959304d3d3 __clone (libc.so.6