[kde] [Bug 485008] Upgrade failure
https://bugs.kde.org/show_bug.cgi?id=485008 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 --- Comment #27 from Jason Playne --- (In reply to Lars Veldscholte from comment #26) > Same issue here. I didn't have this issue on Plasma 5.27 (I was already > using Wayland back then). > > Straight after booting, it always works fine, but after using Plasma for a > while and starting up a game, the mouse doesn't work anymore. I've also > noticed that sometimes it spontaneously starts working fine again after > trying some things (alt-tabbing, clicking, mashing some buttons) but I've > not been able to narrow it down to some specific trigger. > > The issue still exists on Plasma 6.02 / Qt 6.6.2. I can concur that a reboot does indeed allow me to play the game, i wonder if sleep/resume is the thing that breaks it? -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 432720] Tag management window needs a search/filter field
https://bugs.kde.org/show_bug.cgi?id=432720 --- Comment #5 from Jason Straight --- (In reply to tagwerk19 from comment #4) > You can have a look at the "Tags:" option in the information (F11) panel. > There are (unfortunately) several different dialogs in use for manipulating > tags Yeah. I can tag files from several different places, but they all lack the ability to set multiple tags at one time by typing them. I either have to scroll through the list of hundreds of tags to find what ones I want to apply, or I have to type one, save it, open the tag editor again, type another one, save it, etc. I would hope I would be able to just type something like "dog; picture; outside; home", and have it apply all 4 tags to it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 432720] Tag management window needs a search/filter field
https://bugs.kde.org/show_bug.cgi?id=432720 --- Comment #2 from Jason Straight --- Tagging is such a nuisance. Was just doing some and it would be really nice if it got some attention. Also, being able to tag with just typing. Like in the input field it could autocomplete tag names, and just enter several of them with commas. Any that don't exist would be created. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482507] New: Crash when opening local outbox e-mail that failed to send
https://bugs.kde.org/show_bug.cgi?id=482507 Bug ID: 482507 Summary: Crash when opening local outbox e-mail that failed to send Classification: Applications Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lethbridgeja...@gmail.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I made a mistake in my e-mail where the from address did not match the SMTP account that was trying to send it. Naturally the server reject sending and KMail immediatly notified me the "E-mail Sending Failed". I did the typical thing one would when one sees an email hasn't been send and tried to open it from the local outbox with a double click. This caused a crash to desktop The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f264fed9232 in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7f2650095f9c in QCoreApplicationPrivate::lockThreadPostEventList(QObject*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2650096729 in QCoreApplication::postEvent(QObject*, QEvent*, int) () at /usr/lib64/libQt5Core.so.5 #7 0x7f26500c6f94 in ??? () at /usr/lib64/libQt5Core.so.5 #8 0x7f26592eef6e in ??? () at /usr/lib64/libkmailprivate.so.5 #9 0x7f26500c6f94 in ??? () at /usr/lib64/libQt5Core.so.5 #10 0x7f26511a03f3 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #11 0x7f26511a18bb in ??? () at /usr/lib64/libKF5CoreAddons.so.5 #12 0x7f26500befb5 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f2650b6320e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f2650093f28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f26500974a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7f26500e5fc3 in ??? () at /usr/lib64/libQt5Core.so.5 #17 0x7f264bd10e22 in ??? () at /usr/lib64/libglib-2.0.so.0 #18 0x7f264bd14017 in ??? () at /usr/lib64/libglib-2.0.so.0 #19 0x7f264bd1463c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7f26500e5ac6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f265009294b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7f265009accd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x55809b082b54 in ??? () #24 0x7f264f845f0a in ??? () at /usr/lib64/libc.so.6 #25 0x7f264f845fc5 in __libc_start_main () at /usr/lib64/libc.so.6 #26 0x55809b083111 in ??? () [Inferior 1 (process 2403) detached] The reporter indicates this bug may be a duplicate of or related to bug 471223. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482100] Maximize/minimize windows animations are very choppy because of the panel settings and Nvidia
https://bugs.kde.org/show_bug.cgi?id=482100 Jason Crevier changed: What|Removed |Added CC||ja...@jasoncrevier.com --- Comment #3 from Jason Crevier --- (In reply to Çağan from comment #2) > I can reproduce this with NVIDIA 550 driver, on X11 too. Weighing in to say I can reproduce this on 545 and 550 (and Vulkan beta 535) on NixOS with X11. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 401892] Have tab notification icons show up in kde tray
https://bugs.kde.org/show_bug.cgi?id=401892 --- Comment #2 from Jason Straight --- I've recently learned that the non-qt applications used libunity in the past to do notification badges, which is what I was thinking without knowing the correct terminology. Windows does it, and a lot of apps used to do it in the past if libunity was installed. I don't know how many still support that? That is, of course, on the task bar, and not in the tray, but the same outcome I'm looking for - a way for website notifications to be easily visible when there are unread messages. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480817] When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked.
https://bugs.kde.org/show_bug.cgi?id=480817 Jason Straight changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Jason Straight --- Fixed for me with smb:// locations on 6.0. No longer presents for user/pass, and logs in with saved credentials. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 Jason Straight changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Jason Straight --- Working in 6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 --- Comment #4 from Jason Straight --- (In reply to Vlad Zahorodnii from comment #3) > Cannot reproduce I reproduced with a fresh user. Are you on the same version (rc2/5.93) as me? Maybe it's already fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > Are all of the tested apps using XWayland? They are. What do you know - an actual use for xeyes. >Are you using the Slide Back effect? No. I am using squash, but I also tried without it. >Do you have any other non-default KWin effects active? No. Everything is Defaults under Desktop Effects. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] New: Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 Bug ID: 481862 Summary: Minimizing of non-kde/qt windows doesn't give focus to last active window Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- In wayland (not tested on xorg), when I minimize a non QT application, focus is not given to the last active window. I noticed this to be an issue while trying to get Keepass auto-type working on Wayland with the KPUinput plug-in. When Keepass minimizes itself to perform the auto-type, the last active window is not given focus, and the password is not properly sent to the intended window because of that. I experimented by minimizing and restoring some windows and realized this to be the case with every non QT application I tried. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #19 from Jason Straight --- I found a workaround for the momentary freezes of desktop contents. It's not ideal, but it's more ideal than disabling compositing on kwin_x11. I really wish I could use wayland, but I just can't not have working autotype in my password manager for the amount of remote work I do, where copy/paste isn't an option. The workaround I found was to disable glamor (acceleration) in the modesetting x11 driver with `Option "AccelMethod" "none"`. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 338999] [unspecific] Desktop freezes time to time on plasma 5 (collection of various unrelated problems, WONTFIX)
https://bugs.kde.org/show_bug.cgi?id=338999 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #18 from Jason Straight --- Created attachment 165767 --> https://bugs.kde.org/attachment.cgi?id=165767=edit kwin_x11 gdb.txt 5.93.0-1 I'm no dev, so I can't really say if it's the same issue from looking at the trace, but this is with X and on arch this time. The last trace on X was with opensuse TW. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #16 from Jason Straight --- Xorg still freezes, but at least I can say that wayland does not, including on RC2. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480817] New: When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked.
https://bugs.kde.org/show_bug.cgi?id=480817 Bug ID: 480817 Summary: When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked. Classification: Applications Product: dolphin Version: 24.01.95 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j.straight-...@straights.net CC: kfm-de...@kde.org Target Milestone: --- When connecting to a remote share, for which I previously had a password saved (on plasma/frameworks 5), I was asked for the authentication credentials for it, and not given an option to save them. Maybe this belongs in kio? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #14 from Jason Straight --- I can't say what changed from last night to today with certainty, but the wayland session is no longer having this issue. kernel, qt, libgl, or kde updates? But I'm happy about that. I guess I'll have to try an X session to see. Operating System: openSUSE Tumbleweed 20240130 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #12 from Jason Straight --- No problems on kwinft, compiz, Gnome. Definitely a kwin only issue. Compiled kwinft for dev branch last night and it's been going without a freeze, or at least for a lot longer than I could have gone on kwin without one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #11 from Jason Straight --- With plasma6, this is now also present in Wayland, but the behavior changed a little, and my fix no longer works. Now, it'll freeze for several seconds and recover, every few minutes. It seems watching videos in the browser makes it happen more often. Most of the time, I'm lucky to get 5-10 minutes. On Xorg, It's still dependent on compositing being enabled. If disabled, it doesn't happen. I've tried turning off every effect, to no avail. I've tried every environment variable option for kwin. Still only happens with intel driver. Switching to nvidia driver doesn't have issue. Tried w/o a task bar, in case it was something to do with thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480286] New: Mouse pointer only shows up on one screen on Wayland
https://bugs.kde.org/show_bug.cgi?id=480286 Bug ID: 480286 Summary: Mouse pointer only shows up on one screen on Wayland Classification: Plasma Product: kwin Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- On my intel/nividia optimus laptop, using intel drivers, with external monitor connected, the mouse cursor only shows up on one of the external screens. It disappears moving to other screens. At work (including the built-in), I have 3 screens. At home I have 2. Both locations, only one screen has a visible mouse cursor. It disappears while moving. I can right click and get the desktop context menu pop-up. So, it's working. It's just not visible. I've tried with a new user / profile. Same outcome. Operating System: EndeavourOS KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Kernel Version: 6.7.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 478329] New: Would it be possible to have browser integration create a system tray icon for message notifications?
https://bugs.kde.org/show_bug.cgi?id=478329 Bug ID: 478329 Summary: Would it be possible to have browser integration create a system tray icon for message notifications? Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: j.straight-...@straights.net Target Milestone: --- I wonder if this would be the application to hand such a thing? When you have several browser windows and tabs open and some of them are messaging, calendar, e-mail, etc., unless you go checking them every few seconds, you have no good way to know if you have messages that require attention. Plasma's notifications are hard to filter through, and don't cut it. My thought is that if browser integration could create a system tray icon and show a message count there, or at least an unread indicator badge, since I know every site isn't exactly the same with its title updates, then I could use my browser for those types of pages much more efficiently. Maybe you could configure which domains, tabs, or only have pinned tabs monitored, etc. I know apps like Ferdium exist, but I really miss my browser extensions when I use a messaging app. I can use PWA's, but that's an even worse issue of having to check more windows for waiting messages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens
https://bugs.kde.org/show_bug.cgi?id=351175 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 469468] Unable to open repo's
https://bugs.kde.org/show_bug.cgi?id=469468 --- Comment #2 from Jason Playne --- (In reply to Hamed Masafi from comment #1) > Could you please test with new version? > Now I don't think there is such a problem. > Please test with the latest version and let me know the result Hi Hamed, So sorry for not doing this sooner (I only just found it in my inbox) I found that the snap version was unable to open my existing repos the flatpak version was able to. So it's going to be a snap packaging issue. How I tested: * I still had Kommit installed via snap (v1.0.2) and opened it up and attempted to open my repo, nothing * I performed the following actions from the dialog ```ATTENTION sudo snap connect kommit:gpg-keys :gpg-keys sudo snap connect kommit:ssh-keys :ssh-keys if you wish to use your pre-existing keys``` * Opened a git repo - noithing Installed Kommit via Flatpak and it just worked. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #10 from Jason Straight --- I'm no longer on Tumbleweed (for now). Using Endeavour. Just today I decided to see if I still have the problem by disabling my startup script that runs `kwin_x11 --replace` on login. A little while later, kwin froze. Just thought it was worth mentioning that it still exists and it's not isolated to a single distro. Operating System: EndeavourOS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 263174] Fingerprint support for kwallet
https://bugs.kde.org/show_bug.cgi?id=263174 Jason changed: What|Removed |Added CC||rocki...@gmail.com Platform|openSUSE|Archlinux -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475267] Crash when opening a large tif image
https://bugs.kde.org/show_bug.cgi?id=475267 Jason Wolfram changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 475426] New: Stamps are rendered sideways
https://bugs.kde.org/show_bug.cgi?id=475426 Bug ID: 475426 Summary: Stamps are rendered sideways Classification: Applications Product: okular Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Created attachment 162186 --> https://bugs.kde.org/attachment.cgi?id=162186=edit screen recording of a stamp being placed (mouse down) and then rotated after release SUMMARY When adding a stamp to my PDF, it appears sideways on the PDF after adding it. Unfortunately this document has lots of PII as it is for building plans - I was wanting to use a stamp sign "sign" it. PDFs generated by Firefox (printing a page) did not exhibit this behaviour. One lead might be that the problem PDF has a page rotation of 270 degrees whereas the Firefox one does not. PDF DETAILS PdfInfo for the PDF (A3, Landscape) that exhibits the problem: Producer:iLovePDF ModDate: Tue Oct 10 13:34:36 2023 AWST Custom Metadata: no Metadata Stream: no Tagged: no UserProperties: no Suspects:no Form:none JavaScript: no Pages: 3 Encrypted: no Page size: 842 x 1191 pts (A3) Page rot:270 File size: 1241154 bytes Optimized: no PDF version: 1.7 --- PDF Info for a Firefox Print to PDF (A3, Landscape) that does not exhibit the problem Creator: Mozilla Firefox 118.0.1 Producer:cairo 1.17.4 (https://cairographics.org) CreationDate:Tue Oct 10 21:09:20 2023 AWST Custom Metadata: no Metadata Stream: no Tagged: no UserProperties: no Suspects:no Form:none JavaScript: no Pages: 2 Encrypted: no Page size: 1191 x 842 pts (A3) Page rot:0 File size: 55240 bytes Optimized: no PDF version: 1.5 --- STEPS TO REPRODUCE 1. Find a PDF that exhibits the problem (hopefully one without lots of PII) 2. Select a Stamp 3. Left Mouse Down and observe the stamp in the correct orientation 4. Release left mouse button and see the stamp rotated OBSERVED RESULT While mouse button down, see stamp in correct orientation on mouse button release see image rotated 90 degrees Counter Clockwise (or 270 degrees clockwise) EXPECTED RESULT Stamp is in correct orientation SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.6-060506-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475267] New: Crash when opening a large tif image
https://bugs.kde.org/show_bug.cgi?id=475267 Bug ID: 475267 Summary: Crash when opening a large tif image Classification: Applications Product: krita Version: 5.1.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jason.wolf...@gmail.com Target Milestone: --- Application: krita (5.1.5) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-34-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Krita crashes while opening a 1.6 GB tif image exported from Agisoft Metashape. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fef0d4c3cad in QMetaObject::cast(QObject const*) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fef0e1c1737 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fef0e174cd5 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fef0f4130d6 in KisApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkritaui.so.18 #9 0x7fef0d4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fef0d514201 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fef0d514aec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fef0ae6149d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fef0aebc178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fef0ae601b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fef0d514e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fef0c91c467 in KoProgressUpdater::update() () from /lib/x86_64-linux-gnu/libkritawidgetutils.so.18 #17 0x7fef0d4e7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fef0e16bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fef0f4130d6 in KisApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkritaui.so.18 #20 0x7fef0d4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fef0d4bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fef0d5157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fef0ae6149d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fef0aebc178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fef0ae601b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fef0d514e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fef0d4b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fef0d4c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x55cee80ef3c6 in ?? () #30 0x7fef0ca23a90 in __libc_start_call_main (main=main@entry=0x55cee80ecc00, argc=argc@entry=2, argv=argv@entry=0x7ffd7c3e4328) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7fef0ca23b49 in __libc_start_main_impl (main=0x55cee80ecc00, argc=2, argv=0x7ffd7c3e4328, init=, fini=, rtld_fini=, stack_end=0x7ffd7c3e4318) at ../csu/libc-start.c:360 #32 0x55cee80f0fc5 in ?? () [Inferior 1 (process 12197) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475232] New: "Using an empty domain, fix the code." - "Hi,\n\nplease find attached the user id '%UIDNAME%' of your key %KEYID% signed by me. ............"
https://bugs.kde.org/show_bug.cgi?id=475232 Bug ID: 475232 Summary: "Using an empty domain, fix the code." - "Hi,\n\nplease find attached the user id '%UIDNAME%' of your key %KEYID% signed by me. " Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jason.khan...@gmail.com Target Milestone: --- SUMMARY *** ki18n5 version 5.110.0-1 kgpg version 23.08.1-1 In `journalctl` I've been seeing this a lot for many days, even over a week ago: kgpg[2042]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Hi,\n\nplease find attached the user id '%UIDNAME%' of your key %KEYID% signed by me. This mail is encrypted with that key to make sure you control both the email address and the key.\n\nIf you have multiple user ids, I sent the signature for each user id separately to that user id's associated email address. You can import the signatures by running each through `gpg --import` after you have decrypted them with `gpg --decrypt`.\n\nIf you are using KGpg store the attachment to disk and then import it. Just select `Import Key...` from `Keys` menu and open the file.\n\nNote that I did not upload your key to any keyservers. If you want this new signature to be available to others, please upload it yourself. With GnuPG this can be done using gpg --keyserver subkeys.pgp.net --send-key %KEYID%.\n\nWith KGpg you can right click on the key once you imported all user ids and choose `Export Public Key...`.\n\nIf you have any questions, don't hesitate to ask.\n" msgid_plural: "" msgctxt: "" It appears thousands of times in `journalctl`. Today alone `journalctl` shows 60 repeats per hour except one hour, 240 instances. I'm trying to track it down where it's coming from, and I think ki18n is the source maybe. I found this infos which maybe leads to a different source https://wiki.debian.org/caff huh, "caff is part of the package signing-party. caff will mostly be used after a keysigning party." and I did not install that package: extra/signing-party 2.11-1 otherwise maybe the source is kgpg? https://github.com/KDE/kgpg/blob/master/kgpg.h aha, file /usr/share/locale/en_GB/LC_MESSAGES/kgpg.mo is probably the source, from kgpg 23.08.1-1 but what can I do to make that message stop repeatedly appearing in journalctl? There does not seem to be much discussion about it either https://google.com/search?q=kgpg%20%22Using%20an%20empty%20domain%2C%20fix%20the%20code.%22 "Using an empty domain, fix the code." what does this mean? Maybe one of the variables is code that needs to be fixed? %UIDNAME% or %KEYID% ? someone suggested this issue sounds like a bug, and mentioned https://old.reddit.com/r/kde/comments/12fv1jb/am_i_the_only_one_having_an_issue_with_baloo/ and to maybe file a bug report here, so I'm reporting the issue here. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471892] Konsole crashes when opening a new tab in Windows 11
https://bugs.kde.org/show_bug.cgi?id=471892 Jason Craig changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Jason Craig --- Good, news, this crash no longer happens with the recently built konsole-master-199-windows-cl-msvc2019-x86_64.exe from binary-factory.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474994] New: baloo needs to support logical NOT
https://bugs.kde.org/show_bug.cgi?id=474994 Bug ID: 474994 Summary: baloo needs to support logical NOT Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- It would be nice if searching with baloo frameworks supported NOT as well as the supported AND and OR. For example: I would like to be able to search `tags:"Automobiles" AND NOT tags:"1970 C-10"` -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437401] Jagged freehand annotations when using a high-resolution stylus
https://bugs.kde.org/show_bug.cgi?id=437401 Jason changed: What|Removed |Added CC||jasonindestructible@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472218] Freehand annotation jagged / frayed lines with drawing tablet (Windows)
https://bugs.kde.org/show_bug.cgi?id=472218 --- Comment #3 from Jason --- Related: Bug 437401 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472218] Freehand annotation jagged / frayed lines with drawing tablet (Windows)
https://bugs.kde.org/show_bug.cgi?id=472218 Jason changed: What|Removed |Added Version|23.04.3 |23.08.1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472218] Freehand annotation jagged / frayed lines with drawing tablet (Windows)
https://bugs.kde.org/show_bug.cgi?id=472218 Jason changed: What|Removed |Added CC||jasonindestructible@gmail.c ||om --- Comment #2 from Jason --- I can reproduce this issue as well. I use Windows 11 on a Samsung Galaxy Book Pro 360 with a Samsung Pen. Samsung uses Wacom tech and drivers, so the nature of the issue is similar to those with drawing tablets. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 474344] No Default Window Rules for Arch Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=474344 --- Comment #1 from Jason --- Another idea is notifications have window decorations. I don't personally like the look and don't see a point of window decorations for transient windows. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474371] Window decorations are not honoured in the Breeze theme
https://bugs.kde.org/show_bug.cgi?id=474371 --- Comment #2 from Jason --- Created attachment 161542 --> https://bugs.kde.org/attachment.cgi?id=161542=edit Global theme set to Breeze Dark with Window Decoration theme set to Breeze -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474371] Window decorations are not honoured in the Breeze theme
https://bugs.kde.org/show_bug.cgi?id=474371 Jason changed: What|Removed |Added Attachment #161540|Global theme set to Breeze |Accidental screenshot, description|Dark with Window Decoration |please disregard/delete |theme set to Breeze | Attachment #161540|0 |1 is obsolete|| --- Comment #1 from Jason --- Comment on attachment 161540 --> https://bugs.kde.org/attachment.cgi?id=161540 Accidental screenshot, please disregard/delete Spectacle does not refresh the active window automatically, I should have selected it again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474371] New: Window decorations are not honoured in the Breeze theme
https://bugs.kde.org/show_bug.cgi?id=474371 Bug ID: 474371 Summary: Window decorations are not honoured in the Breeze theme Classification: Applications Product: systemsettings Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwindecoration Assignee: kwin-bugs-n...@kde.org Reporter: jason.mcfadye...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 161540 --> https://bugs.kde.org/attachment.cgi?id=161540=edit Global theme set to Breeze Dark with Window Decoration theme set to Breeze SUMMARY = The Breeze theme and variants do not honour user defined window decorations in Wayland. As far as I understand, Breeze is maintained by KDE. Ideally this would be possible to force. It seems most themes do not honour it. Plastik may be a good reference; it is the only theme I have installed that does honour window decorations. SOFTWARE/OS VERSIONS = Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 474344] New: No Default Window Rules for Arch Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=474344 Bug ID: 474344 Summary: No Default Window Rules for Arch Plasma Wayland Classification: Plasma Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: jason.mcfadye...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY = On a base install of Plasma Wayland from Arch repos, there are no default window rules. I assume there is some basic set of window rules installed on Neon. There are simple, expected window behaviours missing that may turn off a more advanced user from adopting KDE before they discover window rules. Even knowing about the rules, one would likely be using an established DE to avoid the hassle of maintaining basic rules. This likely also applies to X11. If you are not the maintainer of the Arch package, I would appreciate either forwarding this bug and/or championing it to be added. EXAMPLE Prompting the user for credentials is not automatically shown above the active window. EXPECTED RESULT === I would like to have some maintained set of rules that align with industry standards. SOFTWARE/OS VERSIONS = Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION === I suggest this is added as a post-install/post-update script in pacman. I'm not familiar with the pacman package format, but I imagine it necessitates the same mechanism. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 Jason changed: What|Removed |Added CC||jriv...@gmail.com --- Comment #18 from Jason --- I too can report having this issue for what feels like years. Because of the randomness, I have never been able to figure out what is happening, and just thought I was going insane. Now that I have found a workaround (disabling the chrome flag #hardware-media-key-handling) my overall life frustration level has dropped. LifeTip: Randomly dropping key-presses is a good way to agitate a human over a long period of time. If there is any debugging info devs need I'd be glad to help. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472373] New: Extract Frame/Extract Frame to project always extracts the same (wrong) frame
https://bugs.kde.org/show_bug.cgi?id=472373 Bug ID: 472373 Summary: Extract Frame/Extract Frame to project always extracts the same (wrong) frame Classification: Applications Product: kdenlive Version: 21.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jaherr...@usa.net Target Milestone: --- SUMMARY *** Regardless of position in the clip the same incorrect frame is extracted. Seems dup of older bug 410486 unresolved in this version. *** STEPS TO REPRODUCE 1. position clip to desired frame to capture 2. right-click "extract frame..." 3. save and incorrect image is created OBSERVED RESULT Incorrect image created from clip EXPECTED RESULT The exact frame displayed in clip monitor should be created SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux (x86_64) release 5.14.18-100.fc33.x86_64 KDE Plasma Version: kde-settings-plasma-33.0-3.fc33.noarch KDE Frameworks Version: KDE Frameworks 5.79.0 Qt Version: Qt 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Jason Straight changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468480] Crash when playing fourth video
https://bugs.kde.org/show_bug.cgi?id=468480 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #23 from Jason Straight --- Mine was crashing all the time. I tried the 8.1.0 appimage and it was also doing it, until I did two things, and I don't know which of the two, or both?, made the difference. Now I'm trying to crash it on videos and can't. What I think fixed it was going to settings in video and removing all the codecs for video, restarting digikam, then enabling ffmpeg again and restarting it again. The other thing I did before that, but it was still doing it after, was to remove the digikam thumbnails files in my Pictures folder. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471892] Konsole crashes when opening a new tab in Windows 11
https://bugs.kde.org/show_bug.cgi?id=471892 --- Comment #2 from Jason Craig --- Created attachment 160068 --> https://bugs.kde.org/attachment.cgi?id=160068=edit output from GDB This is (some) of what GDB had to say right before the crash, and then the backtrace. Let me know if there is something more helpful I can do. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471892] New: Konsole crashes when opening a new tab in Windows 11
https://bugs.kde.org/show_bug.cgi?id=471892 Bug ID: 471892 Summary: Konsole crashes when opening a new tab in Windows 11 Classification: Applications Product: konsole Version: master Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: os-...@jacraig.com Target Milestone: --- When attempting to open an new tab through any method I've tried (shortcut, menu) or opening a new window from a running instance results in a crash. STEPS TO REPRODUCE 1. Run Konsole 2. Try to open a new tab OBSERVED RESULT crash EXPECTED RESULT no crash, new tab or window opens SOFTWARE/OS VERSIONS Using konsole-master-41-windows-cl-msvc2019-x86_64.exe from binary-factory.kde.org Windows 11 KDE Frameworks Version 5.105.0 Qt Version 5.15.8 ADDITIONAL INFORMATION It works on another computer running Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #7 from Jason Straight --- I noticed something else about my "fix" for this, where I have a script run to dbus toggle compositing off/on. During the last couple weeks, I have never had a freeze using this method, but there's another bug that disappeared for me as well. Most times I would shut down or reboot my machine, it wouldn't finish shutting down. It would get stuck on a "shutting down" type message on the TTY. I was able to toggle to TTY7 and back and it would continue shutting down. But, since I've been toggling compositing on every login, I have not had that issue. I know there's another bug (saw mentioned on reddit) where SDDM is supposedly addressing that bug, but it could be related, or maybe some people are suffering that issue for another reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #6 from Jason Straight --- Comment on attachment 160034 --> https://bugs.kde.org/attachment.cgi?id=160034 kwin_x11 gdb backtrace This was taken as per instructed, after kwin_x11 was frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #5 from Jason Straight --- Created attachment 160034 --> https://bugs.kde.org/attachment.cgi?id=160034=edit kwin_x11 gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #4 from Jason Straight --- Dur. I had a stupid moment, apparently. I was thinking your instructions included a kill and restarting with gdb. lol. I'll try this weekend. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #3 from Jason Straight --- (In reply to Jason Straight from comment #2) > (In reply to Nate Graham from comment #1) > > From the description, it does sound like kwin_x11 is what's freezing here, > > not xorg. While frozen, switch to a real tty and run the following: > > > > sudo gdb --pid `pidof kwin_x11` > > > > wait for that to load and type: > > set logging on > > set pagination off > > bt > > quit > > > > This will save a file called gdb.txt in your home directory with the > > backtrace. > > Thanks. The problem is that if I kill it, or toggle it, it never crashes > then. lol Freezes, I mean. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > From the description, it does sound like kwin_x11 is what's freezing here, > not xorg. While frozen, switch to a real tty and run the following: > > sudo gdb --pid `pidof kwin_x11` > > wait for that to load and type: > set logging on > set pagination off > bt > quit > > This will save a file called gdb.txt in your home directory with the > backtrace. Thanks. The problem is that if I kill it, or toggle it, it never crashes then. lol -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Jason Straight changed: What|Removed |Added Version|git-stable-Plasma/5.27 |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] New: kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Bug ID: 471136 Summary: kwin_x11 freezes xorg under certain conditions Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- I had previously filed another bug, but it was closed as we were thinking it was kernel/i915 driver fault at the time. New information brings me back to kwin being at fault. ## ISSUE: Starting in February sometime, Tumbleweed updated from 6.1.8 to 6.1.10 kernel. Since then, and every kernel newer than 6.1.8, I have been experiencing freezing with kwin. ## WHY I THINK IT'S KWIN NOW: Through trials and tribulations of 4 months, I have found that if, after logging in, I disable compositing with ctrl-alt-f12, and then re-enable it with ctrl-alt-f12, it will not freeze. I have tested this method for 4 days now and not had a single freeze with many hours long sessions (12+). Normally, I'd be lucky to go anywhere from minutes to a few hours before freezing. It seems like causing the freeze might be expedited by playing video in a browser (tested with Vivaldi and Firefox). I've been testing by always having a browser window open playing a youtube video of 10 hours of oceanscapes, or something, on mute. ## DETAILS OF FREEZE: - Entire desktop image is frozen - Pointer still works - Pointer still operates on desktop under frozen image (more on that below) - killall -9 kwin_x11 and relaunching kwin_x11 recovers - If during the freeze, I tried to operate on any windows with pointer, they now show up in updated positions/sizes, etc. - Does not happen if compositing is disabled - Does not happen on kernels older than 6.1.9 - Does not happen with any other program - Does not happen on Gnome/Xorg - Does not happen on Wayland (But too many other things don't work for me) - Does not happen if compositing is toggled off then on after logging in - Does not happen a 2nd time if kwin is killed and restarted - Happens with a new user and user profile with default settings ## DEBUG? I would be willing to get a backtrace if I can. I've already installed debug symbols. I don't know exactly how - especially since it doesn't seem to want to do it if I launch kwin manually. ## SYSTEM: Operating System: openSUSE Tumbleweed 20230614 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 469468] New: Unable to open repo's
https://bugs.kde.org/show_bug.cgi?id=469468 Bug ID: 469468 Summary: Unable to open repo's Classification: Applications Product: kommit Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: hamed.mas...@gmail.com Reporter: ja...@jasonplayne.com CC: mon...@kde.org Target Milestone: --- SUMMARY Unable to open a code repo. Note: I was able to use view a repo on Friday (3 days ago) on a different computer Ok, STEPS TO REPRODUCE 1. Install commit v 0.4.0 from snap 2. attempt to open a repo, either from the File -> Open menu or "File -> Recent Repositories" menu OBSERVED RESULT no error (either dialog or on the stderr/stdout output), but also no display of my repo EXPECTED RESULT A view of the repo SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451938] Triple Monitor via Displayport exhibits graphical corruption on monitor Wake
https://bugs.kde.org/show_bug.cgi?id=451938 --- Comment #3 from Jason A. Zelek --- I haven't had any video crashes like the one I described back in 2022 since the kernel moved to 6.0. Currently running Linux 6.2.12-zen1-1-zen x86_64 and things have been great. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466923] XWayland crash on wake with DP monitor that takes 6 seconds to turn on
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #10 from Jason Playne --- (In reply to Nate Graham from comment #9) > There's no set threshold, but the longer it takes to turn back on, the > higher the chance that it will trigger a re-layout of stuff which runs a lot > of code and could be the cause of this crash. That's why I was asking. it's about 6 seconds from sleep to monitor on showing SDDM - if that helps -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #8 from Jason Playne --- (In reply to Nate Graham from comment #7) > Thanks. We're still missing a lot of debug symbols but it seems like it's > crashing when screens change? Do you have multiple screens, and are any of > them slow to turn on/reconnect? Are any of them using a DisplayPort cable? I have a single monitor (AOC 34" 3440x1440 doing 144hz) plugged in via Display Port. I personally wouldn't call it "A long time", <6 seconds for the whole system to resume and screen to turn on I would guess - but what's the threshold there? how many seconds? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #6 from Jason Playne --- with xwayland-dbgsym installed I get this warning: Section `.reg-xstate/42875' in core file too small. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f31ec7788c0 (LWP 42875))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139852397381824, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f31ecc42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f31ecc287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x564cd6182080 in OsAbort () at ../os/utils.c:1353 #6 0x564cd618db2f in AbortServer () at ../os/log.c:879 #7 FatalError (f=0x564cd61e1020 "Caught signal %d (%s). Server aborting\n") at ../os/log.c:1017 #8 0x564cd6180274 in OsSigHandler (unused=, sip=0x7fff9ce043f0, signo=11) at ../os/osinit.c:156 #9 OsSigHandler (signo=11, sip=0x7fff9ce043f0, unused=) at ../os/osinit.c:110 #10 #11 xwl_screen_destroy_drm_lease_device (xwl_screen=0x564cd8d5b380, wp_drm_lease_device_v1=0x564cd8d80d00) at ../hw/xwayland/xwayland-drm-lease.c:430 #12 0x7f31ece6ee2e in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #13 0x7f31ece6b493 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #14 0x7f31ed3e0b20 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x7f31ed3e12c3 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #16 0x7f31ed3e14bc in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #17 0x564cd60594bb in xwl_read_events (xwl_screen=0x564cd805a550) at ../hw/xwayland/xwayland-screen.c:482 #18 xwl_read_events (xwl_screen=0x564cd805a550) at ../hw/xwayland/xwayland-screen.c:469 #19 0x564cd6181841 in ospoll_wait (ospoll=0x564cd8056210, timeout=) at ../os/ospoll.c:657 #20 0x564cd60c1cb0 in WaitForSomething (are_ready=0) at ../os/WaitFor.c:208 #21 Dispatch () at ../dix/dispatch.c:492 #22 0x564cd604fc63 in dix_main (envp=, argv=, argc=) at ../dix/main.c:271 #23 main (argc=, argv=, envp=) at ../dix/stubmain.c:34 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #5 from Jason Playne --- seems to be a lot of question marks there, how do I tell which debug libs I need to install? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #4 from Jason Playne --- Sure warning: Section `.reg-xstate/264915' in core file too small. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f49a4f318c0 (LWP 264915))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139954276735168, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f49a5442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f49a54287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x55bd2cded080 in ?? () #6 0x55bd2cdf8b2f in ?? () #7 0x55bd2cdeb274 in ?? () #8 #9 0x55bd2ccbf389 in ?? () #10 0x7f49a53fae2e in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #11 0x7f49a53f7493 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #12 0x7f49a5b99b20 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #13 0x7f49a5b9a2c3 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #14 0x7f49a5b9a4bc in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x55bd2ccc44bb in ?? () #16 0x55bd2cdec841 in ?? () #17 0x55bd2cd2ccb0 in ?? () #18 0x55bd2ccbac63 in ?? () #19 0x7f49a5429d90 in __libc_start_call_main (main=main@entry=0x55bd2ccb9420, argc=argc@entry=13, argv=argv@entry=0x7ffc5a458b48) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x7f49a5429e40 in __libc_start_main_impl (main=0x55bd2ccb9420, argc=13, argv=0x7ffc5a458b48, init=, fini=, rtld_fini=, stack_end=0x7ffc5a458b38) at ../csu/libc-start.c:392 #21 0x55bd2ccbc495 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #2 from Jason Playne --- xwayland installed version is 2:22.1.1-1ubuntu0.5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #1 from Jason Playne --- The first entry in systemd's coredump list for /usr/bin/Xwayland is from Fri 2022-12-09 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] New: XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 Bug ID: 466923 Summary: XWayland Crash on Wake Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Created attachment 157029 --> https://bugs.kde.org/attachment.cgi?id=157029=edit The the back traces in systemd after resume 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. Log into a wayland session 2. open an xwayland app (for example, discord) 3. push system to sleep 4. wake system OBSERVED RESULT No XWayland apps are running EXPECTED RESULT The software I started before putting the machine to sleep is there when I wake it up SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION this happens every time i put the computer to sleep and wake it again. It has been happening for a while now (sometime during the 5.26 release cycle) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 --- Comment #3 from Jason Straight --- I was just about to call it quits to pack in to go to work and it froze again - compositing disabled. It looks like maybe they've seen (figured something out?) over on the i915 bug page. So we'll see where it goes from there. > Ville Syrjälä commented on a discussion: > Looks like the vblank worker somehow got stuck. > Let's try to add a timeout and some extra debugs: > https://github.com/vsyrjala/linux.git vblank_work_debug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > Thanks for the detailed bug report. Info from > https://gitlab.freedesktop.org/drm/intel/-/issues/8226 indicates that it may > even be a kernel bug. But I'll let the KWin developers handle this. > > Does it happen when compositing it turned off? Compositing turned off? Ee. lol I was hoping there would be progress (an answer) before I had to resort to testing that. :D I've been watching video (the thing that seems to make it most obvious) since you suggested it w/o issue, but that's not definitive yet. I'll continue to test and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] New: kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 Bug ID: 466622 Summary: kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915) Classification: Plasma Product: kwin Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- I'm not really sure if this is entirely upstream, because the only thing it seems to affect is kwin. No other programs freeze or crash. My desktop will randomly freeze and require me to switch to a vtty and kill kwin_x11, which then gets restarted and everything is fine. The image is frozen - the desktop is not. So I'm _guessing_ it's related to compositor and effects. Even though the desktop image is frozen, the audio continues to play, and I can click where the (now frozen) video controls are to pause and restart the audio. I have filed this bug on the i915 drivers bug tracker here: https://gitlab.freedesktop.org/drm/intel/-/issues/8226 It only started happening after changes to i915 post 6.1.8. Linux 6.1.8 has been perfectly stable for me. Originally, I thought it only happened during playing videos in a browser, but it has since happened while not doing that, but it seems to happen more (often) while playing videos. I might go a couple days, or I might have 2 freezes in 10 minutes. Maybe someone can tell me what I might be able to do to enable some debugging logging for kwin and the compositor effects to help us pinpoint what's causing this? Thanks. Next time it happens, I'll try alt-shift-f12 before killing it. I tried that earlier today, but I had the key combo wrong I think. Operating System: openSUSE Tumbleweed 20230227 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-1-default+ (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466391] New: Program crashes when adding Bezier Curve effect to clip
https://bugs.kde.org/show_bug.cgi?id=466391 Bug ID: 466391 Summary: Program crashes when adding Bezier Curve effect to clip Classification: Applications Product: kdenlive Version: 22.12.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: gip...@hotmail.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. Load a clip 2. Attempt to add the Bezier Curves effect 3. OBSERVED RESULT Program crashes EXPECTED RESULT Be able to use the plugin SOFTWARE/OS VERSIONS Windows: 11 Pro macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 464176] New: events in a different time zone can display on the wrong day
https://bugs.kde.org/show_bug.cgi?id=464176 Bug ID: 464176 Summary: events in a different time zone can display on the wrong day Classification: Applications Product: kalendar Version: 22.12.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: os-...@jacraig.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When events in a calendar are in a different time zone (e.g. when they are imported) they will show up on the wrong day if the local time zone puts the event on a different day from what it is in the event's time zone. Creating this bug and trying to describe this turned out to be more challenging than I thought it would be so hopefully it is clear. STEPS TO REPRODUCE 1. Create an event in a different time zone. 2. Have the time of that event be on a different day in that time zone than in the zone of your computer (e.g. 1 AM UTC and your local time zone is EST). 3. Use the month view in Kalendar. OBSERVED RESULT The event shows the correct local time (e.g. 8 PM EST in the example given) but is shown on the wrong day (the day the event occurs in UTC in the example). EXPECTED RESULT The event should show with the correct local time as well as on the correct day. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456988] On X11, Panel autohide with "Keep Window Thumbnails = Always" leaves panel image always visible but non-interactive
https://bugs.kde.org/show_bug.cgi?id=456988 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 463154] New: Plasma Network Manager Widget list of networks glitches during connection
https://bugs.kde.org/show_bug.cgi?id=463154 Bug ID: 463154 Summary: Plasma Network Manager Widget list of networks glitches during connection Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- When using Network Manager Widget as a drop down/pop-up, during negotiation of a connection it corrupts the output of the list of networks and displays a large blank area. Scrolling jumps around. It's impossible to click on anything until the connection times out. If I add the widget to the desktop, expanded to a size that displays the list, it doesn't seem to exhibit the same behavior and works properly. It only seems to do this if you use the icon mode and have it pop-up/down to display the list. It has always been like this, and for some reason I just kept forgetting to file a report on it. I do have many wireless networks in my list, and several VPN's. Video example: https://youtube.com/shorts/7GhpGsmkaKI?feature=share -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #15 from Jason Straight --- It seems that what really makes the Windows come up in the wrong spot is when they're snapped to a screen edge. Where I see it is my 2nd monitor, which is an ultra wide, and I often have windows snapped to one side or the other. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 --- Comment #2 from Jason Straight --- More details: I think it might be limited to changing the background color. I've tried changing some other attributes and it created no duplicates. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 --- Comment #1 from Jason Straight --- I should elaborate that if you go to right click a message and tag it; Then you'll see the duplicates in the context menu. The duplicates do not show up immediately in Appearance until you close and re-open kmail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] New: Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 Bug ID: 462859 Summary: Modifying message tags appearance creates duplicate message tags Classification: Applications Product: kmail2 Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- Go to settings > appearance > Message Tags Create a couple to few tags. Change the background color on any of them and hit okay. Every change to any tag attribute seems to create a duplicate of the most recently created tag. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462134] New: When compositing is disabled, border calculations are wrong
https://bugs.kde.org/show_bug.cgi?id=462134 Bug ID: 462134 Summary: When compositing is disabled, border calculations are wrong Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: ja...@zx2c4.com Target Milestone: 1.0 Created attachment 153944 --> https://bugs.kde.org/attachment.cgi?id=153944=edit Screenshot showing the problem When compositing is disabled, there bottom task manage bar does not resize to be flush against the edges, resulting in the background showing through and click targets being ignored. See the attached picture to see what I mean. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 401863] baloo creates multiple entries for files residing on multi-device btrfs file systems
https://bugs.kde.org/show_bug.cgi?id=401863 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 378106] Update plasmoid doesn't refresh if updates installed from terminal
https://bugs.kde.org/show_bug.cgi?id=378106 Jason changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Jason --- Closing as issue is five years old and I have not used KDE in quite some time. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 Jason Gibson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 --- Comment #7 from Jason Gibson --- Marking as resolved. Turns out a permissions issue. Linux was mounting it as root. Adding -o uid=5004,gid=5004 (my user) and it works fine. I'll see what the equivalent on Windows is. On Linux it saved just fine. Thank you much. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 --- Comment #6 from Jason Gibson --- Must be my samba config I guess. Just almost the same error. Unable to open file '/mnt/OurFinances.kmy' for writing. /build/kmymoney-N273ro/kmymoney-5.1.1/kmymoney/plugins/xml/xmlstorage.cpp:529 This was mounting to my Debian side of my desktop with cifs-utils. I can't imagine why though as I didn't change anything on the defaults, just added my shares. I'll investigate further on my end. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 --- Comment #4 from Jason Gibson --- Indeed. That is my server's lan ip. I can open the file just fine browsing to it through the file manager once I've added the share. But saving is another story. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 Jason Gibson changed: What|Removed |Added Summary|Failure to save to samba|Failure to save to samba |share on remove Debian |share on remote Debian |server |server -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] Failure to save to samba share on remove Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 Jason Gibson changed: What|Removed |Added OS|Other |Microsoft Windows Version|unspecified |5.1.3 --- Comment #2 from Jason Gibson --- I thought I had selected it in the info above. Kmymoney version 5.1.3-55e5c3c37 Cmd output - Unable to write changes to: //192.168.1.2/kmymoney/OurFinances.kmy Reason: Unable to open file '//192.168.1.2/kmymoney/OurFinances.kmy' for writing. C:\_\9b0777e7\kmymoney\kmymoney\plugins\xml\xmlstorage.cpp:510 As for any file I create I can modify and save to my hearts content. The permissions under the settings in the file manager is everyone has full control of the .kmy file. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461557] New: Failure to save to samba share on remove Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 Bug ID: 461557 Summary: Failure to save to samba share on remove Debian server Classification: Applications Product: kmymoney Version: unspecified Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jmgibso...@gmail.com Target Milestone: --- SUMMARY *** Failure to save changed files on samba share. *** An error is thrown when trying to save. This results in inability to close Kmymoney. You need to kill it via Task Manager to stop it. STEPS TO REPRODUCE 1. Move files to remote server. 2. Create samba share to the proper directory. 3. Open file with Kmymoney, make any changes. Then try to save the file. OBSERVED RESULT Error - Unable to open file '//$SERVER/kmymoney/OurFinances.kmy' for writing. C:\_\9b0777e7\kmymoney\kmymoney\plugins\xml\xmlstorage.cpp:510 EXPECTED RESULT Save as normal and move on with my life. SOFTWARE/OS VERSIONS Edition Windows 10 Home Version 22H2 Installed on9/8/2022 OS build19045.2193 Experience Windows Feature Experience Pack 120.2212.4180.0 ADDITIONAL INFORMATION The specific samba config for kmymoney is as follows. [kmymoney] comment = our finances via kmymoney path = /home/jason/Documents/Kmymoney browseable = no read only = no guest ok = no valid users = jason create mask = 0644 directory mask = 0755 Debian samba version - $ apt policy samba samba: Installed: 2:4.13.13+dfsg-1~deb11u5 I am able to create and delete files manually via the Windows file manager, just can't save a changed .kmy file. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 371475] OSD textBuffer has unbounded size
https://bugs.kde.org/show_bug.cgi?id=371475 Jason Tibbitts changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Jason Tibbitts --- Yes, the behavior still exists. I normally keep the OSD disabled because of this, so I turned it on and when I started konversation the this morning, the OSD just slowly went through through the znc backlog for 20 minutes until I turned it off again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #74 from Jason Playne --- I too believe that the upgrade to KDE Neon 22.04 has resolved this issue (just did a log out/in and it worked as expected) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460917] New: Enter key does not work on second login
https://bugs.kde.org/show_bug.cgi?id=460917 Bug ID: 460917 Summary: Enter key does not work on second login Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- SUMMARY *** If you logout and then attempt to login, the enter key does not submit the login request (you have to click the button) *** (sorry, not sure how to file this bug correctly) STEPS TO REPRODUCE 1. from SDDM login with your user/password 2. Log Out from your session 3. Enter your password and push the "enter" key. OBSERVED RESULT One does not simply login a second time using the enter key EXPECTED RESULT You should be logged in SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.3-060003-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #10 from Jason Playne --- Adding in some notes (to see if my usage patterns jive with yours) I have 3 virtual desktops. When I primarily use just one of them (#3) the issue does not manifest When I am regularly switching between each the problem manifests (but not on change) On each desktop I have #1 Java XWayland (jetbrains ide) + Opera Web Browser (Wayland) #2 Vivaldi (Wayland) and Teams (X11, Electron) #3 Discord (X11) and Firefox (X11) I am wondering if this might be a Chromium/Wayland caused thing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #12 from Jason Playne --- (In reply to space9301 from comment #9) > (In reply to Jason Playne from comment #1) > > it appears this segfault didn't create a core dump? > > > > $ coredumpctl > > No coredumps found. > > Do you have core dumps enabled? If coredumpctl still returns the same > result, they might be disabled. > Places to check: https://wiki.archlinux.org/title/Core_dump, > https://linux-audit.com/understand-and-configure-core-dumps-work-on-linux/ > - sysctl kernel.core_pattern > - /usr/lib/sysctl.d/50-coredump.conf > - ulimit -c Thank you for the help, I did install coredumpctl after the first crashes, and one of of the subsequent ones did produce something. Thank you for making me look again! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #11 from Jason Playne --- oh and following the documentation I get a slightly more rich output jason@jason-desktop:~ $ coredumpctl gdb /usr/bin/plasmashell PID: 248057 (plasmashell) UID: 1000 (jason) GID: 1000 (jason) Signal: 6 (ABRT) Timestamp: Sat 2022-10-15 11:20:36 AWST (2 days ago) Command Line: plasmashell --replace Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/session-171.scope Unit: session-171.scope Slice: user-1000.slice Session: 171 Owner UID: 1000 (jason) Boot ID: 9123c4115a9743108f1f78feb5e71e19 Machine ID: 0b8920f9b79a4d7aa86de3faed35fe2d Hostname: jason-desktop Storage: /var/lib/systemd/coredump/core.plasmashell.1000.9123c4115a9743108f1f78feb5e71e19.248057.1665804036.lz4 Message: Process 248057 (plasmashell) of user 1000 dumped core. Stack trace of thread 248057: #0 0x7fb5b8a6f00b __GI_raise (libc.so.6 + 0x4300b) #1 0x7fb5b8a4e859 __GI_abort (libc.so.6 + 0x22859) #2 0x7fb5b8e92bd9 qt_message_fatal (libQt5Core.so.5 + 0x92bd9) #3 0x7fb5b9539d9b init_platform (libQt5Gui.so.5 + 0x139d9b) #4 0x7fb5b953a218 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13a218) #5 0x7fb5b90bbb06 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bbb06) #6 0x7fb5b953d333 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13d333) #7 0x7fb5b9f741bd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1741bd) #8 0x55b198773a0d main (plasmashell + 0x28a0d) #9 0x7fb5b8a50083 __libc_start_main (libc.so.6 + 0x24083) #10 0x55b19877491e _start (plasmashell + 0x2991e) Stack trace of thread 248058: #0 0x7fb5b8b3e99f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fb5b754336e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7fb5b75434a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7fb5b910fb82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7fb5b90b3b3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7fb5b8ecd342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7fb5b9c9ef4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7fb5b8ece543 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xce543) #8 0x7fb5bb185609 start_thread (libpthread.so.0 + 0x8609) #9 0x7fb5b8b4b133 __clone (libc.so.6 + 0x11f133) GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/plasmashell... Reading symbols from /usr/lib/debug/.build-id/22/87b8620679417738a0acf1dba04885bb86a4bb.debug... [New LWP 248057] [New LWP 248058] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `plasmashell --replace'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. [Current thread is 1 (Thread 0x7fb5b4f572c0 (LWP 248057))] (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fb5b8a4e859 in __GI_abort () at abort.c:79 #2 0x7fb5b8e92bd9 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #3 QMessageLogger::fatal (this=this@entry=0x7ffecbcb36f0, msg=msg@entry=0x7fb5b99f9a05 "%s") at global/qlogging.cpp:893 #4 0x7fb5b9539d9b in init_platform (argv=, argc=@0x7ffecbcb395c: 2, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:209 #5 QGuiApplicationPrivat
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #10 from Jason Playne --- i have managed to find a coredump PID: 248057 (plasmashell) UID: 1000 (jason) GID: 1000 (jason) Signal: 6 (ABRT) Timestamp: Sat 2022-10-15 11:20:36 AWST (2 days ago) Command Line: plasmashell --replace Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/session-171.scope Unit: session-171.scope Slice: user-1000.slice Session: 171 Owner UID: 1000 (jason) Boot ID: 9123c4115a9743108f1f78feb5e71e19 Machine ID: 0b8920f9b79a4d7aa86de3faed35fe2d Hostname: jason-desktop Storage: /var/lib/systemd/coredump/core.plasmashell.1000.9123c4115a9743108f1f78feb5e71e19.248057.1665804036.lz4 Message: Process 248057 (plasmashell) of user 1000 dumped core. Stack trace of thread 248057: #0 0x7fb5b8a6f00b __GI_raise (libc.so.6 + 0x4300b) #1 0x7fb5b8a4e859 __GI_abort (libc.so.6 + 0x22859) #2 0x7fb5b8e92bd9 qt_message_fatal (libQt5Core.so.5 + 0x92bd9) #3 0x7fb5b9539d9b init_platform (libQt5Gui.so.5 + 0x139d9b) #4 0x7fb5b953a218 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13a218) #5 0x7fb5b90bbb06 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bbb06) #6 0x7fb5b953d333 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13d333) #7 0x7fb5b9f741bd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1741bd) #8 0x55b198773a0d main (plasmashell + 0x28a0d) #9 0x7fb5b8a50083 __libc_start_main (libc.so.6 + 0x24083) #10 0x55b19877491e _start (plasmashell + 0x2991e) Stack trace of thread 248058: #0 0x7fb5b8b3e99f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fb5b754336e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7fb5b75434a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7fb5b910fb82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7fb5b90b3b3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7fb5b8ecd342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7fb5b9c9ef4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7fb5b8ece543 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xce543) #8 0x7fb5bb185609 start_thread (libpthread.so.0 + 0x8609) #9 0x7fb5b8b4b133 __clone (libc.so.6 + 0x11f133) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #8 from Jason Playne --- (In reply to space9301 from comment #7) > (In reply to Jason Playne from comment #6) > > *** Bug 460336 has been marked as a duplicate of this bug. *** > > I'm not sure this is a duplicate. For me, my programs remained open -- only > plasmashell crashed. They were only lost when I killed kwin_wayland. There > were no segfaults in either kwin_wayland or plasmashell. > > To reproduce the black screen with movable cursor: > - killall plasmashell(the screen is now black, as the desktop background > is handled by plasmashell, but all the programs are open. In the original > bug, plasmashell failed to relaunch) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ?Ssl0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 237394 ?Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > - killall kwin_wayland(the screen is black, and all the programs are > gone, but I can still move my cursor and launch a terminal with ctrl-alt-t) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ?Ssl0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 238586 ?Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > (kwin_wayland has automatically been restarted. Killing kwin_wayland_wrapper > gets me to the login screen) > - kstart plasmashell (I can now use my session again) > > Sorry if the original bug description was misleading. "Output of journalctl > /usr/bin/kwin_wayland, including crashes" should have been "including > crashes of plasmashell". Your description describes what I am seeing (better than I am able to put into words) The segfault's and back traces I have seen I am thinking are incidental. I believe what I see is what you are describing. I suddenly get a back screen with a movable cursor, kwin_wayland is still running - lots of complains from the apps about losing their connection to the wayland server. I *think* the apps are still alive - I work around the problem with restarting sddm (the big hammer approach) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #11 from Jason Straight --- Update: I switched to OpenSuSE Tumbleweed and no longer have the problems with the resolution being change after waking the screens, but the positions of the windows are not restored. They're shifted to the right, with whatever window was snapped to the right being partially off-screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #6 from Jason Playne --- *** Bug 460336 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 Jason Playne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #8 from Jason Playne --- *** This bug has been marked as a duplicate of bug 460513 *** -- You are receiving this mail because: You are watching all bug changes.
