[kwin] [Bug 485015] Identify doesn't provide useful information - doesn't match preview or device list
https://bugs.kde.org/show_bug.cgi?id=485015 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #1 from Brian Cohen --- I am affected by this bug and I can confirm its behavior on KDE Plasma 6.0.4 on X11. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487307] New: Dragging text file from Dolphin to Kate window crashes instance of Dolphin window and file is not opened in Kate...
https://bugs.kde.org/show_bug.cgi?id=487307 Bug ID: 487307 Summary: Dragging text file from Dolphin to Kate window crashes instance of Dolphin window and file is not opened in Kate... Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: squashyna...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin frequently crashes during file dragging. STEPS TO REPRODUCE 1. Open Dolphin and select a text file. 2. Open Kate and start a new file . 3. Drag the text file you'd like to edit from Dolphin to the Kate window. OBSERVED RESULT Dolphin window crashes and file is not opened in Kate. Other open Dolphin windows seem unaffected.. EXPECTED RESULT Dolphin doesn't crash and Kate opens the text file normally. SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-zen1-2-zen (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Framework Product Name: Laptop System Version: AB ADDITIONAL INFORMATION Tuesday, May 21, 2024 2:32:01 AM EDTsystemd-coredumpProcess 445682 (dolphin) of user 1000 dumped core. Stack trace of thread 445682: #0 0x7bc6c70a8e44 n/a (libc.so.6 + 0x94e44) #1 0x7bc6c7050a30 raise (libc.so.6 + 0x3ca30) #2 0x7bc6c98b945f _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x645f) #3 0x7bc6c7050ae0 n/a (libc.so.6 + 0x3cae0) #4 0x7bc6c778d30b _ZN7QObject11deleteLaterEv (libQt6Core.so.6 + 0x18d30b) #5 0x7bc6c9dd9cce n/a (libKF6KIOFileWidgets.so.6 + 0xb3cce) #6 0x7bc6c8749817 _ZN7QWidget5eventEP6QEvent (libQt6Widgets.so.6 + 0x149817) #7 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #8 0x7bc6c87017d3 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1017d3) #9 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #10 0x7bc6c8760fb4 n/a (libQt6Widgets.so.6 + 0x160fb4) #11 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #12 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #13 0x7bc6c7d7eb64 _ZN22QGuiApplicationPrivate11processDragEP7QWindowPK9QMimeDataRK6QPoint6QFlagsIN2Qt10DropActionEES8_INS9_11MouseButtonEES8_INS9_16KeyboardModifierEE (libQt6Gui.so.6 + 0x17eb64) #14 0x7bc6c7de6f72 _ZN22QWindowSystemInterface10handleDragEP7QWindowPK9QMimeDataRK6QPoint6QFlagsIN2Qt10DropActionEES8_INS9_11MouseButtonEES8_INS9_16KeyboardModifierEE (libQt6Gui.so.6 + 0x1e6f72) #15 0x7bc6c52552e6 n/a (libQt6WaylandClient.so.6 + 0xaf2e6) #16 0x7bc6c4597596 n/a (libffi.so.8 + 0x7596) #17 0x7bc6c459400e n/a (libffi.so.8 + 0x400e) #18 0x7bc6c4596bd3 ffi_call (libffi.so.8 + 0x6bd3) #19 0x7bc6c66a0645 n/a (libwayland-client.so.0 + 0x7645) #20 0x7bc6c66a0e73 n/a (libwayland-client.so.0 + 0x7e73) #21 0x7bc6c66a113c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x813c) #22 0x7bc6c520ab5e n/a (libQt6WaylandClient.so.6 + 0x64b5e) #23 0x7bc6c778c147 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c147) #24 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #25 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #26 0x7bc6c77401d2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1401d2) #27 0x7bc6c79959ac n/a (libQt6Core.so.6 + 0x3959ac) #28 0x7bc6c5e18a89 n/a (libglib-2.0.so.0 + 0x5ca89) #29 0x7bc6c5e7a9b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #30 0x7bc6c5e17f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #31 0x7bc6c7993389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #32 0x7bc6c7748350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #33 0x7bc6c810a59b _ZN10QBasicDrag4dragEP5QDrag (libQt6Gui.so.6 + 0x50a59b) #34 0x7bc6c810af89 _ZN12QDragManager4dragEP5QDrag (libQt6Gui.so.6 + 0x50af89) #35 0x7bc6c810b2cf _ZN5QDrag4execE6QFlagsIN2Qt10DropActionEES2_ (libQt6Gui.so.6 + 0x50b2cf) #36 0x7bc6c9ee5a63 _ZN19KItemListController13startDraggingEv (libdolphinprivate.so.6 + 0xafa63) #37 0x7bc6c9ede0ec _ZN19KItemListController14mouseMoveEventEP24QGraphicsSceneMouseEventRK10QTransform (libdolphinprivate.so.6 +
[dolphin] [Bug 487269] Dragging files or folders to the location bar reliably crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=487269 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486065] dolphin crashed while draggin a video file to another app
https://bugs.kde.org/show_bug.cgi?id=486065 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485520] Remove unlock button that appears after typing password and pressing enter only after resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com --- Comment #2 from Brian M --- I have the same issue except I can't get back into the machine -- After sleep, sometimes unlock screen only displays [Unlock?] button. Click on it or hit enter and it does nothing -- wait and [Unlock?] disappears just leaving background. Let it sit there and display blacks out. Hit [Shift] or [Return] and it displays [Unlock?] button again, but won't let you unlock your machine.\ Rinse, wash, repeat. Only way to avoid rebooting is go to TTY3 and do: $ loginctl unlock-sessions then return to TTY1 and continue working. S/W: Garuda Linux (Arch) KDE Plasma ver: 6.0.3 KDE Frameworks: 6.0.0 QT Version: 6.7.0 Kernel Version: 6.8.5-zen-1-zen (64-bit) Graphics Platform: Wayland H/W Processors: 8 x 11th Gen Intel Core i7-1165G7 @ 2.80GHz RAM Memory: 32 GB Graphics: Mesa Intel Xe Manufacturer: Framework -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485031] screenlocker turns off the screen after 60 seconds and then turns it back on again
https://bugs.kde.org/show_bug.cgi?id=485031 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 Brian changed: What|Removed |Added CC||br...@rachal.us --- Comment #10 from Brian --- I also have the same issue where the 'Discover Notifier' runs, stating I have updates without 'Discover' operating. Without 'Discover' functioning properly, it looks as though no updates are capable of easily being installed. Therefore, besides 'pkcon' and 'Discover', a third method for determining/obtaining necessary updates, such as a web-based solution that is not dependent on 'Discover', may need to be considered - if not already available -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452935] I18N_ARGUMENT_MISSING in CSV import Columns screen
https://bugs.kde.org/show_bug.cgi?id=452935 Brian changed: What|Removed |Added CC||macph...@btinternet.com --- Comment #8 from Brian --- I am seeing this error on Package: kmymoney Version: 5.1.2-4 Priority: optional Section: universe/kde Origin: Ubuntu Very similar scenario re CSV import -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426627] Ability re-arrange existing virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426627 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #11 from Brian Cohen --- +1 Interest -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471853] Plasma 6 Wayland - Firefox (115.0) - Min, Max, Close icons are not displayed in header bar
https://bugs.kde.org/show_bug.cgi?id=471853 Brian Pickles changed: What|Removed |Added CC||brianpick...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450674] It's too easy to accidentally delete virtual desktops
https://bugs.kde.org/show_bug.cgi?id=450674 --- Comment #11 from Brian --- What about a gear icon that takes you to the settings to add/delete virtual desktops? Deleting the label is pretty unintuitive. In any case, still strongly agree that the trash icon is rough. On Tue, Dec 26, 2023 at 8:49 PM Denilson F. de Sá wrote: > https://bugs.kde.org/show_bug.cgi?id=450674 > > Denilson F. de Sá changed: > >What|Removed |Added > > > CC||denilso...@gmail.com > > --- Comment #10 from Denilson F. de Sá --- > Created attachment 164460 > --> https://bugs.kde.org/attachment.cgi?id=164460=edit > Screenshot of the "Trash" button when the user has vertical screens > > The "trash" button is surprising. The UI shows "look at this rectangle, > you can > click on me!". Then when the user clicks on it, "Surprise! There was an > invisible button that showed up as you moved the mouse cursor, and now your > virtual desktop is gone!". Hidden buttons are just bad UX. > > This effect is even worse if the user has a 16:9 vertical screen. (i.e. If > the > monitor is rotated 90°.) Take a look at the attached screenshot, the > invisible > button takes up about 40% of the area. That's a very large danger zone. So > large that I'm always scared to click on it. > > It is so annoying that this person came up with his own "solution" (that > gets > overwritten on each update): > https://romangeber.com/blog/tech/kde-plasma-desktop-delete-button-fix > > ——— > > As alternatives, I would suggest having a drag-and-drop feature, so that > we can > easily reorder the virtual desktops, and so that dragging to a trash area > would > delete the virtual desktop. (And dragging from the "plus" area would > create a > new virtual desktop.) > > I can understand implementing drag-and-drop can be complicated, so I'm > proposing an alternative behavior that is easier to implement: If the user > deletes the label (i.e. clicks on the label and deletes the text), then the > virtual desktop is deleted. In other words, an empty label would trigger a > deletion. This sounds intuitive-ish, as the user is already deleting > something; > while also being very hard to trigger by accident. > > Whatever the solution, please get rid of that trash button. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #20 from Brian Kaye --- I agree that there are situations where keeping old session configs might be useful. I suggest there should be some option to decide how many to retain including all of them an give the use the option of which one to activate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 Brian Kaye changed: What|Removed |Added Version|5.24.0 |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #18 from Brian Kaye --- The problem persists in Fedora 39 with plasma-desktop-5.27.9-1.fc39.x86_64. I have 781 files in .config/session. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 477906] New: Arduino IDE, V. 2.2.1
https://bugs.kde.org/show_bug.cgi?id=477906 Bug ID: 477906 Summary: Arduino IDE, V. 2.2.1 Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: brianv...@borgstrom.cc CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I clicked on an Arduino .ino code file and everything was frozen for some minutes. I The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x5581f04af1cc in ?? () #5 0x7f82eaedd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f82eaeb16cd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f82eaeb4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f82eaf0a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f82e97d27a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f82e97d2a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f82e97d2acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f82eaf09836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f82eaeb017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f82eaeb82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x5581f04ac450 in ?? () #16 0x7f82eaa461ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x7f82eaa46285 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #18 0x5581f04aec81 in ?? () [Inferior 1 (process 1584) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #48 from Brian --- "Permission denied" sounds a lot like a different issue I've had before -- https://bugs.kde.org/show_bug.cgi?id=432368 To fix it, you just need to set the Custom Destination in KDE-C Android to your Downloads folder, navigating there. (Repeat this even if the path looks already set). Also to capture useful traces, you'll need to follow the steps at the first link I sent earlier to configure Wireshark to decrypt the TLS traffic between GSConnect and KDE-C Android. The steps are fairly straightforward -- one-liner modifying GSConnect's daemon.js to add an SSLKEYLOGFILE path, pointing Wireshark to that same path, reboot, and begin logging with Wireshark. (I'm not sure if/how the decryption can be done with a tcpdump cmdline.) Any saved traces should now contain the decrypted traffic -- a decrypted packet should look like the image at that first link. Your phone's live "adb logcat" would also be very useful to see app-level errors. If you like, you can limit both traces and logcat to just the rough time period when you run the tests. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #46 from Brian --- We can probably disregard tests done with the stable version in the Store. For now, we're focused on the latest builds, containing tentative fixes in both KDEConnect-Android and GSConnect. @Albert, do you have any logs (both KDEConnect and GSConnect) and Wireshark traces of your recent failures (using *all* the changes you've made so far)? With these, we should be able to determine at what precise stage the key negotiation fails, and see where the applications still fall short. (FYI, you can decrypt GSConnect's TLS traffic in Wireshark using steps explained here: https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/1548#discussioncomment-4682656 and https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/1548#discussioncomment-5273879) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433079] On Wayland container windows created by XEmbedSNIProxy are not stacked below root window
https://bugs.kde.org/show_bug.cgi?id=433079 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #27 from Brian Cohen --- I am able to reproduce this issue in Plasma 5.27.8. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392484] Add option to hide windows preview from Pager
https://bugs.kde.org/show_bug.cgi?id=392484 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #3 from Brian Cohen --- I would like to see this as well. There is an alternative pager available that offers this functionality, which labels each Virtual Desktop using its name rather than its number. For those of us who name our desktops, this is extremely useful since we don't have to remember what each number stands for. https://github.com/wsdfhjxc/virtual-desktop-bar Unfortunately this widget seems to no longer be maintained by its author and there is no Wayland session support; one fork does introduce Wayland support... sort of. I believe this actually is the current (as of 5.28) behavior of the default Pager, so the only thing needed to resolve this regression would be to suppress the minimap. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 474510] Calamares cant find modules users@users, cancels
https://bugs.kde.org/show_bug.cgi?id=474510 --- Comment #1 from Brian Pickles --- Problem occurs with unstable-20230917-1118.iso -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 474510] Calamares cant find modules users@users, cancels
https://bugs.kde.org/show_bug.cgi?id=474510 Brian Pickles changed: What|Removed |Added CC||brianpick...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Version|23.04.1 |23.04.2 --- Comment #8 from Brian Kaye --- (In reply to Stephan Kulow from comment #7) > Does the version say v23.04.3? No. It says 23.04.2. How do I tell which version of the solver is in it. Or do I have to wait for fedora to pick it up or somehow encourage them to do so? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Platform|Gentoo Packages |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Resolution|FIXED |--- Platform|Other |Gentoo Packages Status|RESOLVED|REOPENED --- Comment #6 from Brian Kaye --- The fedora rpms do not seem to have picked up the change to fix this problem. How do I verify which solver version is being used? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 --- Comment #1 from Brian Kaye --- If you start the golf game after starting kpat, the solver seems to work correctly. If however you start the golf game after running another of the kpat games, the solver does not work. It continually reports that it cannot determine if the game is winnable. You an ask for a re-deal but the response from the solver is always the same. All other games that I tried all seem to work with the solver. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #31 from Brian --- SSH-RSA was enabled here in the KDE-Connect desktop app, as a work-around for this issue: https://invent.kde.org/network/kdeconnect-kde/-/commit/204207f2e66e87e7696ff1c98d70ce41b3e2d396 I'm using GSConnect on GNOME, which lacks the APIs to make similar changes, and so is presently unable to SFTP with the Android app. There are other such desktop apps that support the KDE Connect protocol, as mentioned here: https://userbase.kde.org/KDEConnect The security aspect is also a concern, even if a lesser one. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #29 from Brian --- No, as far as I can tell, the situation is still unchanged -- sshd-core is still stuck at the obsolete version 0.14.0, carrying only "ssh-rsa" support: https://invent.kde.org/network/kdeconnect-android/-/blob/master/build.gradle. Any desktop apps that don't/can't enable support for this algorithm, will fail to establish SFTP/mount sessions with the Android app. As mentioned earlier, we need to get the sshd-core version bumped up to the most recent as possible (likely 2.9.2 or greater) and confirm that it resolves this standing issue of SSH negotiation, while retaining support for Android <= 7 if relevant and possible. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] New: Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Bug ID: 470166 Summary: Solver does not work with golf Classification: Applications Product: kpat Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Solver does not work when running golf. STEPS TO REPRODUCE 1. Run golf game with solver enabled. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #17 from Brian Kaye --- Upon further reflection, I wondered it if someone might want to migrate back to an old session for whatever reason. The system could optionally keep a certain number of old session information and the user could be presented with an option of which one to restore. Perhaps a timer to use the last session configuration like grub2 does on boot and an option to keep old session or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #16 from Brian Kaye --- I did update to Fedora 38 yesterday. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #15 from Brian Kaye --- I did a restart twice and files were retained for twice for systemsettings, kcalc, dolphin, several console sessions, and kpat. These are the ones that were open at the time so I am not sure what other commands are affected. I can understand that it would be wise to keep one copy in case of a system crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #14 from Brian Kaye --- I have not deleted files in .config/session for some time. It appears that instances for some files have disappeared. The only one that continues to be added if for systemsettings. I will delete all the files in .config/session today and see what happens. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 351402] On session restore, all windows are placed on first virtual desktop
https://bugs.kde.org/show_bug.cgi?id=351402 Brian Kaye changed: What|Removed |Added CC|b...@unb.ca | -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 Brian Kaye changed: What|Removed |Added CC|b...@unb.ca | -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 --- Comment #63 from Brian --- This specific issue is about #1. The other issues were brought up here due to their close similarity, but this is really about issue 1. Sorting by krunner type is most simply done by a reorderable list, as it was in KDE a while back. If more complexity is desired, a list with weights on the right hand side. But the first is all that was originally asked for. This issue stalled on addendums. On Tue, Apr 18, 2023, 3:46 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=340283 > > --- Comment #62 from stephan.leinewe...@t-online.de --- > (In reply to Peter Hoeg from comment #61) > > I'm not sure what the best way is to move this forward is - and if we > > possibly should be splitting this into multiple tickets since there are > > multiple issues (although obviously related). > > > > 1. the ordering of groups > >a. statically, or > >b. with weights > > 2. the ordering of items within groups > >a. statically, or > >b. with weights > > 3. issues with the "smarts" where the automatic ordering doesn't seem to > > actually take use frequency into consideration > > > > What's the best way forward from here? > > Sorry guys, I've forgotten to tell here. Issue 3 doesn't exist anymore > since, > at least for me. Since an update the ordering of the mail client is as > expected. Thanks for refining the order of the results! Don't know about > issue > 1 and 2, since those were asked by other persons... > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454693] Okular throws error when saving to mounted Samba share
https://bugs.kde.org/show_bug.cgi?id=454693
Brian changed:
What|Removed |Added
CC||fowl...@gmail.com
--- Comment #13 from Brian ---
When opening Okular from terminal I get a...
Couldn't rename "filename.pdf.part" to "filename.pdf" ( Permission denied )
The document hasn't been reloaded/swapped correctly
Context:
brian@Gig2Deb12:/media/test$ okular Okular-test.pdf
QSocketNotifier: Can only be used with threads started with QThread
kf.kio.widgets: Failed to check which JobView API is supported "The name
org.kde.kuiserver was not provided by any .service files"
kf.kio.workers.file: copy() QUrl("file:///tmp/okular.WxqvUE") to
QUrl("file:///media/test/Okular-test.pdf") mode= -1
kf.kio.workers.file: the file doesn't have any xattr
kf.kio.workers.file: Couldn't rename "/media/test/Okular-test.pdf.part" to
"/media/test/Okular-test.pdf" ( Permission denied )
The document hasn't been reloaded/swapped correctly
brian@Gig2Deb12:/media/test$
--
You are receiving this mail because:
You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #9 from Brian Kaye --- Tried the attached game several times. No crash or quit after selecting klondik any of those times. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #6 from Brian Kaye --- Mine is version 22.12.3 on fedora 37. The failure for me now is only switching after a successful win on golf to a new game on klondike. It does not seem to eever fail with another game sequence. Sometime it doesn't fail which I suspect will make finding a solution difficult. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467498] New: Thumbnails creation causes an assert error
https://bugs.kde.org/show_bug.cgi?id=467498 Bug ID: 467498 Summary: Thumbnails creation causes an assert error Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Maintenance-Thumbs Assignee: digikam-bugs-n...@kde.org Reporter: bmguarded...@yahoo.com Target Milestone: --- Created attachment 157365 --> https://bugs.kde.org/attachment.cgi?id=157365=edit Assert failure SUMMARY Generating a STEPS TO REPRODUCE 1. Tools -> Maintenance 2. Select Whole Album. Select Rebuild thumbnails. and "Scan for changed or non-cataloged items (faster)" 3. Select OK OBSERVED RESULT After 3% processed, an assert failure is raised. EXPECTED RESULT All thumbnails are regenerated without a crash. I cannot proceed without restarting. This has been reproduced every time I try to rebuild thumbnails. SOFTWARE/OS VERSIONS Windows: Windows 10 Version 11H2 (OS Build 19045.2728) ADDITIONAL INFORMATION The most recent DebugView content before it crashes:- [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/py (2019_07_28 10_37_47 UTC).ico (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/py (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/py (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyc (2019_07_28 10_37_47 UTC).ico (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyc (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyc (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyd (2019_07_28 10_37_47 UTC).ico (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyd (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/DLLs/pyd (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).icns (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).icns: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).icns: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).ico (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/idle (2019_07_28 10_37_47 UTC).ico: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata from file with Exiv2 backend: L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/plusnode (2019_07_28 10_37_47 UTC).gif (Error # 11 : "L:/FileHistory/brian/BIGBLACK/Data/D/Downloads/WPy-3670/python-3.6.7.amd64/Lib/idlelib/Icons/plusnode (2019_07_28 10_37_47 UTC).gif: The file contains data of an unknown image type" [6244] digikam.metaengine: Cannot load metadata with Exiv2: (Error # 11 : "L:/FileHistory/bria
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #8 from Brian Kaye --- Created attachment 157343 --> https://bugs.kde.org/attachment.cgi?id=157343=edit New crash information added by DrKonqi kpat (22.12.3) using Qt 5.15.8 Kpatience Version 22.12.3 fedora 37 . Successfully wond Golf game and waited 2 minutes. When I picked klondike it crashed. -- Backtrace (Reduced): #4 MemoryManager::new_from_block (s=48, this=0x56498917e670) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/memory.cpp:156 #5 Solver<9ul>::pack_position (this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:217 #6 Solver<9ul>::insert (node=0x7ffe2949f940, d=0, cluster=, this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:887 #7 Solver<9ul>::new_position (this=this@entry=0x56498add54b0, parent=parent@entry=0x0, m=m@entry=0x7ffe2949f990) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:919 #8 0x5649872cfbbe in Solver<9ul>::doit (this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:505 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 Brian Kaye changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #4 from Brian Kaye --- kpat killed by SIGSEGV. The program now quits switching between golf and patience. Some time it just quits and sometime it quits with a chance of reporting or restarting -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #26 from Brian --- Following that -- Why does KDEConnect Android still bundle an obsolete sshd-core (0.14.0)? The reason given so far has been backward-compatibility with older Android versions, specifically Android 7 and below. This is a relevant commit that gives a bit of detail -- https://invent.kde.org/network/kdeconnect-android/-/commit/ef3fd68f7378398273cb476581bc4f28c6b89515 However, I think this decision should be re-evaluated: * Android 7 was first released 7 years ago, and its final update was in 2019. What is the source of the requirement to support Android <=7? Is this really still required, especially to the detriment of security? * If it is, then is there a way to achieve that backward compatibility, without sacrificing security or usability with newer phones/desktops? For instance, a comment in the above commit says (in the removed lines) that newer versions of sshd-core require the NIO package, which is only available in Android 8+. It sounds like this is the main reason KDE-Connect Android isn't using newer sshd-core. However, that commit also says (in the newly added lines), that adding mina-core somehow makes sshd-core work **without requiring NIO** any longer. So far, this combination seems to have been tested with only sshd-core 0.14.0 -- but perhaps this workaround should also work for newer sshd-core as well, latest being 2.9.2. https://mvnrepository.com/artifact/org.apache.sshd/sshd-core/2.9.2. If that is the case, then it should now be possible to upgrade the sshd-core for all Android, once and for all. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Brian changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||bcej...@gmail.com --- Comment #25 from Brian --- >From the comments above, the root cause of the issue is in the KDE Connect Android app which bundles an obsolete version of a library, sshd-core 0.14.0, which in turn offers only one insecure signature algorithm -- "ssh-rsa". Many desktop environments depend on OpenSSH, which has (2 years ago) since dropped default support for "ssh-rsa" -- thus, desktop apps (like KDEConnect-Desktop and GSConnect) will fail to establish SSH/SFTP sessions with KDE Connect Android. The current workaround has been to quietly enable the use of "ssh-rsa" in the KDE Connect Desktop app: https://invent.kde.org/network/kdeconnect-kde/commit/204207f2e66e87e7696ff1c98d70ce41b3e2d396 But this is problematic: * It obviously enables a known insecure algorithm, as mentioned earlier. Personally, I don't consider this a huge deal, given the tradeoff is to greatly increase user-coverage, for the meantime till ssh-rsa recedes into history. The real problem is ... * There seem to be a few separate desktop apps which implement the KDEConnect protocol, whereas there is only one KDEConnect Android app of note. **Not all desktop apps will have the same easy control over SSH config as KDEConnect Desktop**, thus they cannot enable "ssh-rsa" at will -- GSConnect, for instance. So this issue should ideally be fixed in KDEConnect Android, not just because it is the source of the issue, but also because the alternative workaround is not feasibly implementable in all desktop apps. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #7 from Brian Kaye --- (In reply to Stephan Kulow from comment #6) > Yep, as I expected. I remove the old code, so it won't crash on you anymore. > You won't have a solver either, but that's a bug worthy to report to fedora. I would prefer to have the solver there even if it crashes occasionally. What can I do to help? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #5 from Brian Kaye --- ldd /usr/bin/kpat|grep blackhole generates null output -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #4 from Brian Kaye --- (In reply to Brian Kaye from comment #2) > (In reply to Stephan Kulow from comment #1) > > This is the old solver running that was massakred and is no longer tested > > due to most using blackhole solver. I'll remove it > > How does one determine which solver is being used. The problem persists. The > problem only occurs when switching between golf and klonike. I switch > Freecell>Golf>Kondike>Grandfather'sClock>.>Spider. Then reverse.The > problem does not occur in the reverse direction The version I am running is 22.12.2 from a Fedora RPM -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #2 from Brian Kaye --- (In reply to Stephan Kulow from comment #1) > This is the old solver running that was massakred and is no longer tested > due to most using blackhole solver. I'll remove it How does one determine which solver is being used. The problem persists. The problem only occurs when switching between golf and klonike. I switch Freecell>Golf>Kondike>Grandfather'sClock>.>Spider. Then reverse.The problem does not occur in the reverse direction -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #7 from Brian Tipton --- It (In reply to Nate Graham from comment #5) > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > was interrupted. > > Can you get a backtrace of the crash itself? (In reply to Brian Tipton from comment #6) > (In reply to Nate Graham from comment #5) > > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > > was interrupted. > > > > Can you get a backtrace of the crash itself? > > This gdb was during the "crash", I didn't realize it wasn't actually > crashing the kwin process. (In reply to Brian Tipton from comment #6) > (In reply to Nate Graham from comment #5) > > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > > was interrupted. > > > > Can you get a backtrace of the crash itself? > > This gdb was during the "crash", I didn't realize it wasn't actually > crashing the kwin process. What I see on my side during the "crash" is that the cursor doesn't have the ability to move, the keyboard doesn't do anything except sometimes lets me get to a TTY. And windows seems to be stuck at there last position. Most of the time it requires a reboot to get out of this state -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #6 from Brian Tipton --- (In reply to Nate Graham from comment #5) > The gdb backtrace doesn't show that kwin_wayland crashed but rather than it > was interrupted. > > Can you get a backtrace of the crash itself? This gdb was during the "crash", I didn't realize it wasn't actually crashing the kwin process. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #4 from Brian Tipton --- Created attachment 156744 --> https://bugs.kde.org/attachment.cgi?id=156744=edit Diagnosis Info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #3 from Brian Tipton --- Created attachment 156743 --> https://bugs.kde.org/attachment.cgi?id=156743=edit GDB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #2 from Brian Tipton --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! Yea sorry, I meant to post one the other night. Another couple thing to note, I have 2 GPU's attached to my machine with VFIO setup. Whenever I swap the monitors via KVM I am swapping to the output of the 2nd GPU. The swapping seems to be okay when removing monitors, but when I am attempting to reconnect the monitors via KVM the system gets very laggy on the running monitor (mouse/windows visually jumping around). Then when I go inside the system settings to disable/enable to attempt to get them to work it crashes. Also tested on 5.27.1 with same results. I will also attach diagnosis info. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] New: Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 Bug ID: 466326 Summary: Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings Classification: Plasma Product: kwin Version: 5.27.0 Platform: NixOS OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: brian.p.tip...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Hot swap monitor with a KVM like device or enabling/disabling a monitor in settings 2. 3. OBSERVED RESULT System hangs and a hard reboot is needed to get back to a working state. Sometimes can get to a TTY by CTRL-ALT-F1 EXPECTED RESULT Disabling or enabling monitors as needed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #5 from Brian --- Many thanks for getting back to me. Any idea how I report it to Feren OS? My apologies for this: I thought my report to you was in fact going to Feren. Brain On 06/02/2023 18:12, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Nate Graham --- > This would be something to report to your distro, not KDE. Our code wouldn't > be > able to cause this. Can you report it to Feren OS? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #4 from Brian --- Thanks, Nate, Brian On 06/02/2023 18:34, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > --- Comment #3 from Nate Graham --- > There's a help button at https://ferenos.weebly.com/ that looks helpful. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #2 from Brian --- Many thanks for getting back to me. Any idea how I report it to Feren OS? My apologies for this: I thought my report to you was in fact going to Feren. Brain On 06/02/2023 18:12, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Nate Graham --- > This would be something to report to your distro, not KDE. Our code wouldn't > be > able to cause this. Can you report it to Feren OS? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] New: I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 Bug ID: 464992 Summary: I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7 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: fla...@pm.me 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. Run Zoom. Test mic. No sound. 2. Run Cheese; record video; No Sound 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.5... KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464537] New: Application Appearance crashes systemsettings
https://bugs.kde.org/show_bug.cgi?id=464537 Bug ID: 464537 Summary: Application Appearance crashes systemsettings Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: b...@briandwright.com Target Milestone: --- Application: systemsettings (5.26.5) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 5.15.0-58-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.26 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Application Appearance crashes systemsettings everytime it attempts to open. Uninstalling and reinstall qt5-style-plugins donest not resolve the issue The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139775347375744) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139775347375744) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139775347375744, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f2000c78476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f2000c5e7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f200111bba3 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #10 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcdb9579f0, msg=msg@entry=0x7f2001515de8 "Cannot mix incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)") at global/qlogging.cpp:893 #11 0x7f2001131d9c in QObjectPrivate::checkForIncompatibleLibraryVersion(int) const (this=, version=) at kernel/qobject_p.h:438 #12 QObjectPrivate::checkForIncompatibleLibraryVersion(int) const (version=, this=) at kernel/qobject_p.h:430 #13 QObjectPrivate::QObjectPrivate(int) (this=, version=) at kernel/qobject.cpp:191 #14 0x7f1f9f77af01 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libqgtk2style.so #15 0x7f2001fd8312 in qLoadPlugin(QFactoryLoader const*, QString const&) (key=..., loader=0x7f20024bba80 <(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>) at ../../include/QtCore/5.15.8/QtCore/private/../../../../../src/corelib/plugin/qfactoryloader_p.h:108 #16 QStyleFactory::create(QString const&) (key=) at styles/qstylefactory.cpp:105 #17 0x7f1fdc0c1004 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so #18 0x7f1fff0cd2f2 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f1fff062235 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f1fff06284d in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f1ffc86d363 in () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #22 0x7f1fff588375 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f1fff579e3d in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f1fff586b38 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f1fff58b13e in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x7f1fff58b49a in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f200137e108 in doActivate(QObject*, int, void**) (sender=0x55a8a66ebbe0, signal_index=4, argv=0x7ffcdb9581a0) at kernel/qobject.cpp:3935 #28 0x7f1ffc84003a in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #29 0x7f1ffc860e7c in () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #30 0x7f1ffc8674c2 in () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #31 0x7f1ffc8678c8 in () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #32 0x7f1ffc87305d in QQmlDelegateModel::_q_modelReset() () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #33 0x7f1ffc873ca3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #34 0x7f200137de46 in doActivate(QObject*, int, void**) (sender=0x55a8a5c16290, signal_index=21, argv=0x7ffcdb958400) at kernel/qobject.cpp:3949 #35 0x7f2001377177 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f20015e5680 , local_signal_index=local_signal_index@entry=18, argv=argv@entry=0x7ffcdb958400) at kernel/qobject.cpp:3983 #36 0x7f20012df191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) (this=, _t1=...) at .moc/moc_qabstractitemmodel.cpp:648 #37 0x7f1fdc0bbb81 in () at
[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 #113 from Brian Cohen --- (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. Same thing. I tried and failed this afternoon to establish a baseline by swapping out my hard drive, installing KDE Neon 'User' edition, enabled hibernation (https://askubuntu.com/a/1316444), hooked up my two screens via my USB-c dock, properly arranged them, disconnected from the dock, hibernated, resumed from hibernate, reconnected the dock. Screens both properly activated and were properly arranged. -- 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 #105 from Brian Cohen --- @Nate Graham I am willing to test it for sure. I actually went digging a couple weeks ago to figure out how, including trying to track down a way through KDE Neon but got lost trying to figure out if KDE Neon Unstable had these changes integrated. If you're saying Neon Unstable has 5.27 I can definitely test it, with the caveat that I am currently affected by this under Manjaro so I probably need to first install Neon Stable and verify that I can reproduce the problem there as a baseline. -- 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 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #103 from Brian Cohen --- Reading the description of the overhaul and the reasons behind it were illuminating: https://notmart.org/blog/2022/12/multi-screen/ As a temporary workaround I now have my two monitors both hooked up to my laptop directly by HDMI ports instead of via a USB-c dock. Probably most people won't be able to do this; I have a Framework so I was able to buy another HDMI port to swap into one of the expansion bays. Hopefully the 5.27 release fixes these problems. I love so many things about KDE Plasma but ultimately I need to be productive first, and I can't do that if I have to reboot before connecting external screens. If the overhaul in the 5.27 release doesn't resolve this I will very regrettably have to move to another DE. In the meantime I do plan to collect some debugging info to post here just in case, following these instructions: https://community.kde.org/Solid/Projects/ScreenManagement -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397817] kpat crash when switching games
https://bugs.kde.org/show_bug.cgi?id=397817 --- Comment #25 from Brian Kaye --- On Fedora the latest supplied is kpat-22.04.1-1.fc36.x86_64 and the problem does occur in that version. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397817] kpat crash when switching games
https://bugs.kde.org/show_bug.cgi?id=397817 Brian Kaye changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405335] KDevelop crashes when reopening a project
https://bugs.kde.org/show_bug.cgi?id=405335
--- Comment #3 from brian ---
This is what the crash looks like when running from a terminal:
~ $ kdevelop
kdevplatform.shell: Could not load plugin "kdevperforce" , it reported the
error: "The variable P4CONFIG is not set. Is perforce installed on the system?"
Disabling the plugin now.
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
/bin/cat:
/home/brian/.local/share/kdevelop/sessions/{46199e2d-b3a6-4556-baa3-294f6e633a4f}/default.sh:
No such file or directory
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4181, resource
id: 23069278, major code: 40 (TranslateCoords), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4368, resource
id: 23069283, major code: 40 (TranslateCoords), minor code: 0
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.SktrYI") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/brian/projects/qtqml.qml")
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6431, resource
id: 23069289, major code: 40 (TranslateCoords), minor code: 0
crash happens here: ]]]]]]
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.upNPEg") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = /usr/bin pid = 8674
KCrash: Arguments: /usr/bin/kdevelop
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 69 and type 'Read', disabling...
[1]+ Stopped kdevelop
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 405335] KDevelop crashes when reopening a project
https://bugs.kde.org/show_bug.cgi?id=405335 brian changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from brian --- Yes, I was able to reproduce it in 'Version 5.9.220800 (22.08.0)' Looks like this is also bug 422241 and bug 335412 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 459072] New: When launching KDEnlive from the latest app image, the screen font of the user interface is jagged (no antialiasing)
https://bugs.kde.org/show_bug.cgi?id=459072 Bug ID: 459072 Summary: When launching KDEnlive from the latest app image, the screen font of the user interface is jagged (no antialiasing) Product: kdenlive Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: btspamdu...@gmail.com Target Milestone: --- Created attachment 152036 --> https://bugs.kde.org/attachment.cgi?id=152036=edit Screenshot of display Launching from the latest app image, the user interface fonts are jagged / not antialised ... see attached screen shot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Brian Cohen changed: What|Removed |Added CC|br...@intercarve.net| -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 428373] "Examining (Failed)" notifications some times when trying to save in folders with many files.
https://bugs.kde.org/show_bug.cgi?id=428373 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kbounce] [Bug 457696] New: Background is over-sized and makes game play impossible...
https://bugs.kde.org/show_bug.cgi?id=457696 Bug ID: 457696 Summary: Background is over-sized and makes game play impossible... Product: kbounce Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: roney...@gmail.com Reporter: squashyna...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 151207 --> https://bugs.kde.org/attachment.cgi?id=151207=edit Balls move through "bracketed area" -- game unplayable... Hello, There is a scaling problem with the background of Kbounce. STEPS TO REPRODUCE 1. Just launch the app and try playing the game. 2. The scale of the wall background is over-sized and therefore it doesn't line up with the path of the balls. OBSERVED RESULT Impossible to play the game. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Garuda Linux Kernel ver.5.18.16-zen1-1-zen (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 --- Comment #8 from Brian Kramer --- I may need to revert back to 5.0 version if that's the case because I spent too much invested in presets and can't afford to focus on re-doing currently. I am assuming that this bug is something that will be sorted out overall in the set 5.1 software in the near future. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 --- Comment #6 from Brian Kramer --- Thank you. I will review that however it seems a little above level of competence to execute. I'll try to get some help (unless you can walk me through it). Otherwise I will most likely try to revert back to 5.0 version so I can work until I can focus on the fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 --- Comment #4 from Brian Kramer --- (In reply to Halla Rempt from comment #3) > works for me... I wish I could say the same. Going through every possible solution and still the new krita won't allow me to use touch gestures. I have been a user exclusively for two years and never had this kind of issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 --- Comment #2 from Brian Kramer --- I have additionally re-downloaded/replaced to latest krita 5.1.0 again and the result is still the same. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 --- Comment #1 from Brian Kramer --- I have additionally re-downloaded/replaced to latest krita 5.1.0 again and the result is still the same. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457514] New: After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24
https://bugs.kde.org/show_bug.cgi?id=457514 Bug ID: 457514 Summary: After installing krita 5.1.0 touch gestures won't function on wacom cintinq 24 Product: krita Version: 5.1.0-beta3 Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: briankramerbl...@hotmail.com Target Milestone: --- SUMMARY Just downloaded latest krita 5.1.0, turned on my wacom cintiq 24 and I cannot use any on screen hand gestures like zoom, rotate. I can touch to open and close categories and the touch functions normally outside of krita. I only get a rectangular outline that appears and disappears with canvas touch on screen. I did restarts as well as check drivers, which are up to date. Spoke with wacom support that clarified this is a krita issue. *** 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. 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.
[kpat] [Bug 456934] New: Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 Bug ID: 456934 Summary: Kpat crashes while switching games Product: kpat Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.96.0 Operating System: Linux 5.18.11-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Switching games after golf game success causes crash. Does not occur every time. The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault [KCrash Handler] #4 MemoryManager::new_from_block (s=48, this=0x55cf9cffac30) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/memory.cpp:157 #5 Solver<9ul>::pack_position (this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:217 #6 Solver<9ul>::insert (node=0x7ffdfa218ee0, d=0, cluster=, this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:887 #7 Solver<9ul>::new_position (this=this@entry=0x55cf9e67b190, parent=parent@entry=0x0, m=m@entry=0x7ffdfa218f30) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:919 #8 0x55cf9bea7c2e in Solver<9ul>::doit (this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:505 #9 Solver<9ul>::patsolve (this=0x55cf9e67b190, _max_positions=) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:800 #10 0x55cf9be81c33 in DealerScene::isGameLost (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1844 #11 DealerScene::isGameLost (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1727 #12 0x55cf9be874ba in DealerScene::takeState (this=this@entry=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1331 #13 0x55cf9be89739 in DealerScene::animationDone (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1546 #14 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #17 0x7f8ca8cddfce in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #18 0x7f8ca8cd1525 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f8ca99aec82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f8ca8ca7658 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f8ca8cf7681 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #22 0x7f8ca8cf7fa4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7f8ca6926faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f8ca697c2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7f8ca6924940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f8ca8cf82fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f8ca8ca60ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f8ca8cae162 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x55cf9be77596 in main (argc=, argv=) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/main.cpp:353 [Inferior 1 (process 373529) detached] The reporter indicates this bug may be a duplicate of or related to bug 397817. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456728] Lattedock
https://bugs.kde.org/show_bug.cgi?id=456728 --- Comment #2 from Brian --- (In reply to Michail Vourlakos from comment #1) > use latte git version Thanks. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 --- Comment #7 from Brian Kaye --- I use the X11 version and it now seems to work properly. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456728] New: Lattedock
https://bugs.kde.org/show_bug.cgi?id=456728
Bug ID: 456728
Summary: Lattedock
Product: lattedock
Version: 0.10.8
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: aeon.descrip...@gmail.com
Target Milestone: ---
When application previews are enabled (whether or not 'preview window behaves
as a popup' is checked), I have no images in the previews.
I don't know if this is a system configuration problem, or if this is a latte
issue.
STEPS TO REPRODUCE
1. Enable window previews on tasks mouse hover
2. Hover over a task icon so that the preview appears
3.
OBSERVED RESULT
Preview images are present, but blank.
EXPECTED RESULT
Preview images aren't blank.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Vega 3 Graphics
ADDITIONAL INFORMATION
On hover for Dolphin with one window open, `latte-dock --debug` gives:
[Warning : 15:10:49.889889] - "\"0 instead of 1 arguments to message {On %1}
supplied before conversion.\""
[Warning : 15:10:49.889889] - "\"0 instead of 1 arguments to message {On %1}
supplied before conversion.\""
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
--
You are receiving this mail because:
You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #106 from Brian Kaye --- Hopefully my last comment. Deleted all files in .config/session and started apps one at a time. All old files controlled by ksmserverrc were deleted at each logout/login. So no bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #105 from Brian Kaye --- Ran kwriteconfig5 --file startkderc --group General --key systemdBoot true and installed "plasma-workspace-common-5.25.2-1.fc36.x86_64" and associated packages on my Fedora 36 system. Had to try a number of times before it worked though. Seems to work correctly now. But still does not remove the old files in .config/session. Probably a different bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #90 from Brian Cohen --- Well I'm glad to see I'm not the only one. Since upgrading to 5.24 I can reproduce all of the following: - Upon boot or wake from hibernation (no monitors connected), panel is gone from laptop display. - Upon connecting dual monitors (joined display): - left display correctly has panel, but right display is totally black (no wallpaper, won't accept right-clicks on desktop). - System Settings > Display Configuration is confused as to which monitor is 'Primary' as evidenced by where it displays the panel. The left monitor, which correctly has the panel, has 'Primary' unchecked. If I check 'Primary' on it and 'Apply', the panel incorrectly moves to the right-hand monitor. I have confirmed the 'Primary' is being misapplied after using 'Identify' to confirm which monitor is which. Really this is driving me nuts. My workflow is to move back-and-forth with a laptop between docked environments at home and the office, each with two monitors, while occasionally using the laptop undocked in between. These defects are making the system unusable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Brian Cohen changed: What|Removed |Added CC||br...@intercarve.net --- Comment #402 from Brian Cohen --- I am able to reproduce this problem while running plasma 5.24.5. I had never seen this problem before (only started using KDE around 2018) but after a recent upgrade this problem appeared. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 --- Comment #5 from Brian Kaye --- (In reply to kde.org from comment #4) > Now that David fixed https://bugs.kde.org/show_bug.cgi?id=442380, can you > still reproduce the issue with KDE Plasma 5.25.2, or can we close this one > as well? As soon as the distros pick it up and we can veryify. As of this post Fedora has not so it is hard to test. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #104 from Brian Kaye --- I ran the command "kwriteconfig5 --file startkderc --group General --key systemdBoot false" which seemed to correct the problem. The file .config/startkderc was changed(or created) . The file "/etc/xdg/startkderc" still shows "systemdBoot=true". Once the distros pick this change up (fedora has not as of this post) we will have to delete .config/startkderc or run the command "kwriteconfig5 --file startkderc --group General --key systemdBoot true" . This should be done before the fixed package is installed to verify that the new package fixes the problem. Sure wish fedora would hurry up so we can put this issue to bed. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #103 from Brian Kaye --- (In reply to David Edmundson from comment #102) > >Need to get the various distros to pick this up and then turn systemd boot > >back on. > > Who's turned it off? > > >Is the retention of files in .config/session fixed as well or is it a > >separate bug > > Unrelated to this. I have turned it off as a result of a comment on this bug report.. I wonder if the race condition has created the situation where the files are not deleted in .config/session. Once the distros pick up the change we will see if the deletion is still necessary. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #101 from Brian Kaye --- Need to get the various distros to pick this up and then turn systemd boot back on. Is the retention of files in .config/session fixed as well or is it a separate bug. Still would like to know the what the contents of the .config/session and .config/ksmserverrc files mean. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns instead
https://bugs.kde.org/show_bug.cgi?id=455770 --- Comment #2 from Brian --- (In reply to Nate Graham from comment #1) > Your screenshot shows a column of icons and the "arrange in columns" option > selected. Looks to me like everything is working properly. Can yo clarify > what the problem is, exactly? The icons in the picture are arranged row-wise. Rows go along the y-axis, columns along the x-axis. My problem is that the labels are backwards. When "arrange in columns" is selected I would expect to see a line of icons going along the x-axis, instead of the y-axis like it is on the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns instead
https://bugs.kde.org/show_bug.cgi?id=455770 Brian changed: What|Removed |Added Summary|Arranging icons by rows |Arranging icons by rows |places the icons in |places the icons in columns |columns.|instead -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns.
https://bugs.kde.org/show_bug.cgi?id=455770 Brian changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] New: Arranging icons by rows places the icons in columns.
https://bugs.kde.org/show_bug.cgi?id=455770 Bug ID: 455770 Summary: Arranging icons by rows places the icons in columns. Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: brian.ur...@outlook.com Target Milestone: --- Created attachment 150033 --> https://bugs.kde.org/attachment.cgi?id=150033=edit Screen capture of the selected options, and the icorrectly arranged icons. 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. Right Click on desktop > Arrange In > Rows/Columns OBSERVED RESULT Icons are placed in the wrong order. If Arrange In rows is chosen, the icons are placed column-wise. If arrange in Columns is chosen, the icons are placed row-wise EXPECTED RESULT Icons are arranged in the order the label indicates. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.5-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 455761] New: Failed loading page on a specific page, always
https://bugs.kde.org/show_bug.cgi?id=455761 Bug ID: 455761 Summary: Failed loading page on a specific page, always Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: aeon.descrip...@gmail.com Target Milestone: --- Title says it. STEPS TO REPRODUCE 1. go to https://www.home-assistant.io/blog/2021/07/07/release-20217/ 2. 3. OBSERVED RESULT " Failed loading page Something went wrong while loading this page. Try reloading the page or closing some tabs to make more memory available. " EXPECTED RESULT page loads SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04, Linux 5.15.0-39-generic (64-bit) Falkon Application version: 3.2.0 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION QtWebEngine version 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com --- Comment #15 from Brian M --- Issues: 1) Confirmation of Peter's problem 2) Additionally, current workspace no longer highlights ___ As of 5.25 update, I began observing same behavior as this bug reporter (Peter) demonstrated in both videos. Additionally, in my initial installation of Stable User KDE Neon, about 10 days ago, the desktop grid view emphasized the current desktop at normal brightness, with all other windows dimmed. As you moved around the workspaces, the "brightened" desktop followed the cursor movement indicating the next desktop to be activated if clicked upon -- this highlighting no longer exists just as you can see in Peter's videos. All desktops now appear at full brightness with no implication of workspace change except by watching the cursor. This is the case irrespective of grid layout (same in a single row of windows, as well as a grid configuration). __ System Information: Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Framework Product Name: Laptop System Version: AB __ Thank you for all the work you folks are doing. The gestures and overview are an especially welcomed addition! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #86 from Brian Kaye --- (In reply to Nicolas Pomarede from comment #85) > (In reply to Kishore Gopalakrishnan from comment #70) > > Can someone confirm if disabling Plasma's systemd-based startup fixes the > > issue? To disable it, run > > kwriteconfig5 --file startkderc --group General --key systemdBoot false > > in a terminal and reboot. > > At least for me, session restore seems to work perfectly (remembers which > > virtual desktops and activities windows were on) on X11 when this is > > disabled. > Thanks for this, it fixed my restore issue on my laptop PC. After several > reboots, windows are correctly restored on their respective virtual desktop. > But I have mixed results that might match what other reported : I have 2 PC > with exact same packages (Mageia 9 dev version), 1 laptop and 1 "normal" pc. > On the laptop, session restoring is working again after disabling systemd > for kde, but on the other PC session is still not correctly restored (using > the same apps (konsole, kwrite, kate) than on the laptop). > > So, this really looks like some kind of race condition to me ; starting kde > from systemd seems to start components in the wrong order or not waiting > enough to ensure each component had enough time to start fully and handle > session restoring for example. > On my other PC it still doesn't work as if even when kde starts each > component itself (not with systemd) then some parts are not ready to handle > session restoring. > > In the end, we see that code for restoring session is still working in > recent KDE/Plasme, in the sense that session is saved and can be loaded > later on next login, but it seems to me that the process that try to restore > the session happens too soon / at the wrong time when kde/plasma is not > ready yet. I agree. See my comment 29. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #84 from Brian Kaye --- Firefox always seemed to restore to the correct desktop(s). But without testing every application its hard to tell if all other applications exhibit the incorrect behaviour. Firefox may be aware of its desktop configuration when it shuts down. It is certainly aware of which windows it has open. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #78 from Brian Kaye --- On my fedora system there is a file dolphin_dolphin_dolphin in .config/session which seems to be the configuration of dolphin when it is started after being closed. There are other files dolphin_* which has the configuration of each dolphin window after a session restart -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #75 from Brian Kaye --- Is it enabled by default? -- You are receiving this mail because: You are watching all bug changes.
