[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #127 from Benny Zen --- Just tested sleep in KDE Plasma 5.27 on Manjaro testing and wonder what: the bug is still there. Again I had to remove `~/.local/share/kscreen` folder and tediously rearrange all my screens. So annoying. This is just unusable as a daily driver. I'm giving up on this, as months pass and no one seems to really care. Goodbye KDE. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #111 from Benny Zen --- (In reply to Steven Robbins from comment #109) > (In reply to Steven Robbins from comment #108) > > (In reply to Brian Cohen from comment #105) > > > > > so I probably need to first install Neon Stable and verify > > > that I can reproduce the problem there as a baseline. > > > > That sounds like a good idea. I tried last night with Neon "User Edition", > > however, and failed to trigger the bug. Wondering what your experience was. > > Despite not being able to reproduce the problem with "user edition", I tried > the experiment (disconnecting one monitor via an HDMI switch; see comment > 81) using "unstable edition". I discovered a crash in plasmashell if the > monitor is Primary (bug 464334). But the monitor WAS re-enabled when > reconnected. It's unclear what this proves given that that I was unable to > reproduce the bug in the older "user edition" KDE neon. (In reply to Oleksii Zolotarevskyi from comment #110) > I've tried Manjaro "unstable" branch and still have the issue. > The packages were updated to: > plasma-wayland-protocols `1.9.0-1` -> `1.9.0-1` > kwin `5.26.4-1` -> `5.26.5-2` > libkscreen `5.26.4-1` -> `5.26.5-1` > kscreen `5.26.4-1` -> `5.26.5-1` > plasma-workspace `5.26.4.1-1` -> `5.26.5-2` Confirmed. Even on Manjaro testing it's not fixed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #107 from Benny Zen --- Just went over to KDE Neon and tried the `Unstable` image, like Nathan suggested. The about dialog says it's still KDE 5.26.8, but, and this is a huge but, the bug seems fixed. Tried sleep and after wake-up the screens are still assigned correctly. So yes, you were right. Thank you. Now we just need to wait until these changes make it into our distros. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #102 from Benny Zen --- This is truly sad to say, but after more than a decade on KDE, I had to move to another DE. In current times of elevated energy prices having no sleep is just a no-go. No offense intended, but just my reality. Personally, I think a lot of users are affected by this one and do not even get what is going wrong behind the scenes. Looked at the code and tried to figure out how things work myself, but it's way above my horizon. So I leave it up to those guys familiar with it to fix it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #76 from Benny Zen --- Unfortunately, I'm not that lucky. It's not fixed for me. Still experiencing the very same bug as before. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 Benny Zen changed: What|Removed |Added CC||benny.zami...@gmail.com --- Comment #53 from Benny Zen --- My system had the very same issue. I had 2 monitors 34" DP-0 and 24" HDMI-1. Today I switched the second monitor with a second 34" connected using DP-2. Now the problem is gone. No bogus files in `~/.local/share/kscreen` after wake anymore. Sleep just works as before KDE 5.26.x. Maybe this helps someone figuring out the regression in latest releases. No need to mention this was a somehow expensive "fix"^^ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428080] New: Krita does not handle focus gain properly when switching to its workspace using a keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=428080 Bug ID: 428080 Summary: Krita does not handle focus gain properly when switching to its workspace using a keyboard shortcut Product: krita Version: 4.4.0 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bennycaguil...@gmail.com Target Milestone: --- If I switch to a workspace with Krita open using a keyboard shortcut in i3, some functionality breaks until I refocus Krita using a mouse action, restarting i3 in place, or some similar refocus action. Some things that stop working are: 4 and 6 keys to rotate the canvas, shift-drag to resize the brush, and ctrl-click to pick colors. The Krita windows is definitely focused, and other actions such as Ctrl-Z and drawing still work properly. I am guessing the issue is related to the canvas widget itself not receiving a focus event when Krita is focused using a keyboard-shortcut workspace-switch (alt-tab doesn't cause the issue for me on XFCE, so it has to be a workspace switch), and therefore not receiving keyboard events. The issue also occurs for me on XFCE, and another user confirms it occurs similarly on their MATE desktop. Previous discussion on krita-artists.org here: https://krita-artists.org/t/cetrain-key-combinations-dont-work-after-switching-workspace-to-krita-linux/13001 STEPS TO REPRODUCE 1. Open Krita on workspace A 2. Switch to workspace B 3. Switch back to workspace A using a keyboard shortcut OBSERVED RESULT Shift-drag does not change brush size, ctrl-click does not pick color, and 4 and 6 keys do not rotate the canvas. EXPECTED RESULT All actions work as if Krita had been focused using a mouse SOFTWARE/OS VERSIONS Arch Linux KDE Frameworks Version: n/a Qt Version: 5.15 Krita: 4.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420715] Can't read EXIF from Samsung S10 HEIC-file
https://bugs.kde.org/show_bug.cgi?id=420715 --- Comment #20 from Benny --- Sorry, I didn't think about that - just pressed F5 within the album and the orientation got corrected and EXIF-metadata was shown. After using "sync metadata and database > from images metadata to db" the informations are now complete :) Thank you again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420715] Can't read EXIF from Samsung S10 HEIC-file
https://bugs.kde.org/show_bug.cgi?id=420715 Benny changed: What|Removed |Added Resolution|FIXED |UPSTREAM --- Comment #18 from Benny --- I am totally impressed! Thank you Gilles, really good news! Just downloaded the most recent Win64 version, orientation is shown correctly in the albums and within the "Metadata" all EXIF data is shown :) Is there a way to use the newly extraced informations also for geo location (Map) and for "Item Properties" and "Photograph Properties" like for JPG files? Thanks, Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420715] Can't read EXIF from Samsung S10 HEIC-file
https://bugs.kde.org/show_bug.cgi?id=420715 Benny changed: What|Removed |Added CC||jf...@web.de --- Comment #7 from Benny --- Created attachment 129053 --> https://bugs.kde.org/attachment.cgi?id=129053=edit HEIC handling in albums/windows photos/exiftool Dear Gilles, is there a way to handle HEIF/HEIC files separately in digikam albums until someone finally adds support to Exiv2? It seems to become a never ending story in Exiv2, "clanmills" wrote 3 days ago "I will never work on ISOBMFF." https://github.com/Exiv2/exiv2/issues/1066#issuecomment-636839592 and on April 7th "We will not be proceeding with #1066 because the proposal was rejected by the community." https://github.com/Exiv2/exiv2/pull/978#issuecomment-610223481 and 3 days ago he wrote "v0.27.3 does not include support for ISOBMFF containers (CR3, AVIV, HEIF). Perhaps a volunteer will add this to Exiv2." https://github.com/darktable-org/rawspeed/issues/121#issuecomment-636817674 Windows 10 and Exiftool read the EXIF data without problems since May 2018 (see screenshot). It's kind of a show stopper in using digikam with HEIC images. So maybe it's worth a workaround? :) I'm not a programmer and I don't know how hard it would be to implement this... Maybe it's not worth the effort, but maybe it is? Best regards, Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420634] Face thumbnails not zoomed in and have wrong orientation on network shares
https://bugs.kde.org/show_bug.cgi?id=420634 --- Comment #9 from Benny --- Hi Maik, I have to thank you again! Works perfectly with the latest RC "digiKam-7.0.0-rc-20200429T150011-Win64.exe". Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420634] Face thumbnails not zoomed in and have wrong orientation on network shares
https://bugs.kde.org/show_bug.cgi?id=420634 --- Comment #7 from Benny --- Hi Maik, thank you very much for your really fast support! sorry for asking, but is your fix already included in the most recent version at https://files.kde.org/digikam/ ? I've installed "digiKam-7.0.0-rc-20200428T165414-Win64.exe" uploaded 28-Apr-2020 15:16 and the person thumbnails still don't show up correctly on Windows when using UNC-paths. Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420634] Face thumbnails not zoomed in and have wrong orientation on network shares
https://bugs.kde.org/show_bug.cgi?id=420634 --- Comment #3 from Benny --- Created attachment 127905 --> https://bugs.kde.org/attachment.cgi?id=127905=edit Screenshot of face thumbnails and metadata Hi Maik, I use the share directly via \\servername\path and there are no special characters in the path. But metadata is correctly shown in digiKam, see screenshot. Some faces had been recognized in another tool (picasa) and I'm now correcting them in digiKam - but the face thumbnails are not updated at all for the person-albums. In the normal albums the thumbnails are updated when I edit the pictures or for example change orientation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420634] New: Face thumbnails not zoomed in and have wrong orientation on network shares
https://bugs.kde.org/show_bug.cgi?id=420634 Bug ID: 420634 Summary: Face thumbnails not zoomed in and have wrong orientation on network shares Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jf...@web.de Target Milestone: --- Created attachment 127901 --> https://bugs.kde.org/attachment.cgi?id=127901=edit Screenshot of face thumbnails in digiKam 7.0.0-rc Thumbnails are not correctly created or shown in digiKam 6.4.0 or 7.0.0-rc when using "Collections on Network Shares". Some thumbails are zoomed in to the recognized face, but most of the thumbnails just show the whole picture and the thumbnails are not updated, when the face region is changed, edited or the picture is edited or rotated. STEPS TO REPRODUCE 1. Use "Collections on Network Shares" and wait until digikam finishes thumbnail creation 2. Go to People and select an album 3. Have a look at the thumbnails OBSERVED RESULT Thumbnails of peoples show the whole picture and not only the zoomed in view of the face region. Rotated images (exif) are displayed in wrong orientation (in the normal album the same picture is shown correctly even in the thumbnail view). EXPECTED RESULT Show the face region only, use the exif orientation tag to show the correct orrientation. SOFTWARE/OS VERSIONS Windows: 10 1909 FURTHER INFORMATION Just found that other digiKam-users have the same issue: http://digikam.1695700.n4.nabble.com/digiKam-users-People-thumbnail-not-zoomed-to-face-td4709112.html -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #28 from Benny --- Hi Maik, Hi Gilles, I give up. Sorry for wasting your time. I've tested for hours now and I can't find a root cause. Three physical Windows 10 systems reacting the same way, it doesn't matter if it is a local share or remote share. The error comes up every few times. The Windows 8 VM (from 2012, not updated at all) has the same behavior. Now I've installed a clean Windows 10 1909 in vmware, created the local share and it's working! Updated to the latest Windows Defender updates and OS updates, connected to my network, and it keeps working. I am at my wit's end. The physical Windows 10 system all have in common, that they've been upgraded over and over from previous Windows 10 versions... but else, on one Kaspersky security software is running, on the others Windows Defender. On two 1909 is running, on one 1903 with Windows Defender. I checked about Windows Defender and Firewall (as you've mentioned Maik), disabled them. No changes. At the moment I believe it's a wired Windows bug. I can live with it, because everything else is running smoothly. @Maik: Could you please remove the "File:" call again? It's running better without as far as I can see. Thank you again for your fast support. And I love digiKam. Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #27 from Benny --- Hi Gilles, you don't need network access to test this issue. I've tested with a VM (in vmware Player), Virtual Machine Settings: Network Adapter: Not Connected. Just make a local share (Windows Explorer > Go to e.g. C:\Temp, right click, Share... and a share "\\Your-PC-Name\Temp" is created). Install DigiKam with default settings (C:\Users\Benny\Pictures). Go to digiKam settings (Configure digiKam > Collections) and add the created share "\\Your-PC-Name\Temp" to "Collections on Network Shares". If you cannot reproduce the isse, I could try to upload the VM (in German language). Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #23 from Benny --- Created attachment 127288 --> https://bugs.kde.org/attachment.cgi?id=127288=edit Screenshots from legacy windows versions Hi Maik, i've done some testing on older Windows version (virtual machines): Windows 7 does not like you're version with "File:", but even UNC is not working at all with the local test share - doesn't matter for me, because it's an old unsupported OS version :) digiKam_win7_File-UNC.png digiKam_win7_UNC.png Windows 8 has the same issue with the open with dialog, sometimes it's working, sometimes not: digikam_win8_openwith_keine-anwendung.png digikam_win8_openwith_ok.png -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #22 from Benny --- Created attachment 127287 --> https://bugs.kde.org/attachment.cgi?id=127287=edit Recoreded with Problem Step Recorder (V3) Good morning Maik, thank you for the new version, but sadly it does not fix the issue. The message now shows File:\\smb\path in the title bar. Benny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 Benny changed: What|Removed |Added Attachment #127279|0 |1 is obsolete|| --- Comment #20 from Benny --- Created attachment 127280 --> https://bugs.kde.org/attachment.cgi?id=127280=edit Recoreded with Problem Step Recorder (V2) Another complete one... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #19 from Benny --- Created attachment 127279 --> https://bugs.kde.org/attachment.cgi?id=127279=edit Recoreded with Problem Step Recorder I've recorded the steps with the "Microsoft Problem Step Recorder" so you can see what I do :) RC 1223 only occured on the first an the last time. I think you need Internet Explorer to open the MHT file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #18 from Benny --- Created attachment 127278 --> https://bugs.kde.org/attachment.cgi?id=127278=edit Windows Dialog for Unknown Filetype Hi Maik, this is what I get when I try to open a .123-file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #16 from Benny --- I hope it helps narrow down the issue :) And thank you for your time and support! If I could assist you any further we could also do a teamviewer session, if you want to do any further debugging on this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #15 from Benny --- This was kind of tricky, took a while to configure DebugView to capture it (had to enable "Capture Events"): [4376] digikam.general: ShellExecuteEx::openas return code: 1223 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 0 [4376] digikam.general: ShellExecuteEx::openas return code: 1223 The first an the last failed with the known message. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #11 from Benny --- Created attachment 127260 --> https://bugs.kde.org/attachment.cgi?id=127260=edit Tested on a third device with clean install Hi Maik, sorry for the delay. I tested the problem on a third Windows device (notebook with Win10 1909) with a clean install of digiKam 7.0.0-beta3 and the problem occurs. I made a local share on D:\Temp, named it \\a507\Temp and added the collection to digiKam 7.0.0-beta3. Choosed "Open with" in the context menu, the first time worked, using the "Open with" function the second time on the same picture the error message appeared (please have a look at the screenshot). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #9 from Benny --- No, it occurs with every file type I tested: JPG, HEIC and MOV so far. I just thought about that the problem may be caused by blanks in the path - but I don't know why it happens not every time using the "Open With" function. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #7 from Benny --- Created attachment 127149 --> https://bugs.kde.org/attachment.cgi?id=127149=edit This file does not have an app associated with it for performing this action. Dear Maik, thank you very much! It's working and I can choose a program to open my images with on my network share and I am very happy that you've fixed it that fast! But every once in a while Windows displays an error message (I've attached the german version): "This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the Default Apps Settings page." If I try again the "Open With" option it's working as it should... This happens every 2 to 5 times. I've tested this on two different Windows PCs, one with W10 1903 and one with W10 1909, checked with JPG, HEIC and MOV. Both running your beta3. And it seems to happen only with UNC-Paths, on a local collection it does not happen so far. Should I open a new bug? Or maybe it's a Bug in Windows... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #3 from Benny --- Created attachment 127063 --> https://bugs.kde.org/attachment.cgi?id=127063=edit Configuration - Collections on Network Shares -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 --- Comment #2 from Benny --- Hi Maik, thank you for your quick reply. I didn't get any error message in digiKam when I added the network share by UNC-path. And I've found no hint in the digiKam-documentation, that it's not supported to use UNC-paths? Can you tell me which part of digiKam does not support UNC-paths (beside "Open With")? It's working perfectly on my computers (database locally on SSD, album collection on network share with about 100k photos), so I can sync the whole database to a second computer and work on the same album collection in my local network. This is a really huge benefit and I love it. Could you please have a look at the "Open With" menu option? For me it would be really nice if "open with" could be fixed to work with UNC-paths on Windows operating systems :) And I still belief it is the syntax with "//smb/path" instead of "\\smb\path" sent to the file handler in Windows. When I use the Windows-Run-Command with "\\smb\path" it will open correctly, when I use it with "//smb/path" I get the same error message as the menu-option "open with..." in digiKam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419294] New: Open with does not work with collection on network shares (on Windows)
https://bugs.kde.org/show_bug.cgi?id=419294 Bug ID: 419294 Summary: Open with does not work with collection on network shares (on Windows) Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability-Menus Assignee: digikam-bugs-n...@kde.org Reporter: jf...@web.de Target Milestone: --- Created attachment 127043 --> https://bugs.kde.org/attachment.cgi?id=127043=edit Error message with context menu open with (german Windows) SUMMARY I've configured my album via "collections on network shares" to a \\smb\path. When using the context menu "open with" I'm getting an error from the operating system "//smb/path/... could not be found." STEPS TO REPRODUCE 1. Set up an album in "collections on Network Shares" 2. navigate to a picure 3. right click and select "Open With" OBSERVED RESULT Error message ""//smb/path/..." could not be found. Make sure you typed the name correctly, and then try again." Maybe it's the way how the network path is sent to the operating system? //smb/path instead of \\smb\path? EXPECTED RESULT Open the "Open with" dialog SOFTWARE/OS VERSIONS Windows: Window 10 1909 ADDITIONAL INFORMATION Same behavior in digiKam 6.4.0 and 7.0.0-beta-2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411694] New: Krita does not close cleanly because of Dr. Konqi on Arch Linux with XFCE
https://bugs.kde.org/show_bug.cgi?id=411694 Bug ID: 411694 Summary: Krita does not close cleanly because of Dr. Konqi on Arch Linux with XFCE Product: krita Version: 4.2.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bennycaguil...@gmail.com Target Milestone: --- SUMMARY After closing krita, a system notification appears saying krita closed unexpectedly, even though closing it was intentional and done cleanly. STEPS TO REPRODUCE 1. Close Krita, either by shortcut, X button on the window manager, or the Quit option in Krita's file menu. OBSERVED RESULT Krita gives this output after being closed: (process:24790): Gtk-WARNING **: 15:18:42.059: Locale not supported by C library. Using the fallback 'C' locale. Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet krita.lib.widgets: The file could not be parsed. QObject::startTimer: Timers cannot have negative intervals /usr/lib/krita-python-libs/krita added to PYTHONPATH KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krita path = /usr/bin pid = 24790 KCrash: Arguments: /usr/bin/krita KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/drkonqi directly (process:24886): Gtk-WARNING **: 15:18:48.458: Locale not supported by C library. Using the fallback 'C' locale. [1] + 24790 suspended (signal) krita Then, after a minute or so, krita outputs the following: QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. [1] + 24790 segmentation fault (core dumped) krita EXPECTED RESULT Krita closes cleanly and instantly SOFTWARE/OS VERSIONS Linux: Arch Linux, XFCE KDE Plasma Version: n/a KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 Benny <benny.maleng...@gmail.com> changed: What|Removed |Added CC||benny.maleng...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
