[muon] [Bug 372343] New: search stops working after muon is first used to install a package
https://bugs.kde.org/show_bug.cgi?id=372343 Bug ID: 372343 Summary: search stops working after muon is first used to install a package Product: muon Version: 5.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: rjst...@talk21.com CC: silh...@gmail.com Target Milestone: --- The muon search bar works correctly when the application is first started but after something has been installed, all searches will return no results. Restarting the application fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] New: rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 Bug ID: 467099 Summary: rendering crash missing ID3 Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: robert.gro...@gmx.de 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. Render Video to any format (tried a few) 2. works until 536 3. rendering crashes OBSERVED RESULT crash error report: Discarding ID3 tags because more suitable tags were found EXPECTED RESULT rending SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04.2 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Also crashes if I like to play my project in Kdenlive. Also crashes if I like to start a new project and like to add files to my project folder. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 --- Comment #1 from Robert --- Created attachment 157139 --> https://bugs.kde.org/attachment.cgi?id=157139&action=edit screen copy rendering -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 --- Comment #2 from Robert --- Created attachment 157140 --> https://bugs.kde.org/attachment.cgi?id=157140&action=edit Playing crashes -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error
https://bugs.kde.org/show_bug.cgi?id=468999 Robert changed: What|Removed |Added CC||ada...@yahoo.com --- Comment #10 from Robert --- Created attachment 158610 --> https://bugs.kde.org/attachment.cgi?id=158610&action=edit Screenshot of Crash This attachment shows what KDENLive looks like when it crashes. Project Bin is populated and Loading Clips reaches 46% before the "Could not recover corrupted file" error pops up. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error
https://bugs.kde.org/show_bug.cgi?id=468999 --- Comment #11 from Robert --- I'm encountering this same issue, I'm running Archlinux which is fully up to date. I am unable to open files created on the previous version of KDENLive. When opening a project file, it looks like it successfully loads all of the clips into the Project Bin, it then asks if I want to rebuild proxies (I tried deleting the cache for the project). When I click okay, it process for a moment before dying at 46% on the "Loading Clips" dialogue box. While the Project Bin is populated, the Project Timeline is completely empty. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 455438] Fortinet VPN doesn't wait for DUO/2FA answer long enough
https://bugs.kde.org/show_bug.cgi?id=455438 Robert changed: What|Removed |Added CC||robertdeja...@tutanota.com --- Comment #1 from Robert --- My company recently enabled 2fa for openfortivpn, and I'm having a similar issue. Only the dialog closes immediately after opening, instead of giving me 3 seconds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Archlinux kernel: 6.2.13-arch1-1 OpenFortiVPN: 1.20.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error
https://bugs.kde.org/show_bug.cgi?id=468999 Robert changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error
https://bugs.kde.org/show_bug.cgi?id=468999 Robert changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Robert --- Confirmed that the problem appears to be resolved. Upgraded to KDENLIVE 23.04.1 and opened a file created in 22.12.3 and it opened as it should. Thank you for addressing the problem! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 463995] After standby, all email accounts stay offline
https://bugs.kde.org/show_bug.cgi?id=463995 robert changed: What|Removed |Added CC||robert.segr...@free.de --- Comment #1 from robert --- I also have this problem. I have tried removing and re-configuring mail accounts but to no avail. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 463995] After standby, all email accounts stay offline
https://bugs.kde.org/show_bug.cgi?id=463995 --- Comment #4 from robert --- (In reply to Martin Tlustos from comment #3) > Sorry, it was a lost internet connection that triggered it. Anyway, after > entering into offline mode, it does not go back to online mode, even if I > try manually. I have to restart akonadi (akonadictl stop and then restart > kontact) to be able to go online again. same here. If I put my laptop into suspend that after waking, it will stay in offline mode until I restart akonadi. When I do restart akonadi from the terminal with akonadictl restart I get some strange error messages like: org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection akonadi_unifiedmailbox_agent (0x55ae3217fa90) : Dude, WTF?!? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440378] Plasma crashes after logging in to wayland session
https://bugs.kde.org/show_bug.cgi?id=440378 Robert changed: What|Removed |Added CC||rstreete...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440378] Plasma crashes after logging in to wayland session
https://bugs.kde.org/show_bug.cgi?id=440378 --- Comment #2 from Robert --- Created attachment 156010 --> https://bugs.kde.org/attachment.cgi?id=156010&action=edit New crash information added by DrKonqi plasmashell (5.26.5) using Qt 5.15.8 I just logged into Plasma using Wayland nothing was visible, it was just a black screen, when I noticed that I could use krunner to open a terminal, I tried to restart the plasma shell, and was greeted with a crash report window. -- Backtrace (Reduced): #4 0x7effc3f2cff7 in xcb_send_request_with_fds64 () from /lib64/libxcb.so.1 #5 0x7effc3f2d8d9 in xcb_send_request () from /lib64/libxcb.so.1 #6 0x7effc3f2ee84 in xcb_intern_atom () from /lib64/libxcb.so.1 [...] #9 0x7effc355f8d4 in NETRootInfo::NETRootInfo(xcb_connection_t*, QFlags, QFlags, int, bool) () from /lib64/libKF5WindowSystem.so.5 #10 0x7eff8ccc6c05 in VirtualDesktopBar::VirtualDesktopBar(QObject*) () from /usr/lib64/qt5/qml/org/kde/plasma/virtualdesktopbar/libvirtualdesktopbar.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440378] Plasma crashes after logging in to wayland session
https://bugs.kde.org/show_bug.cgi?id=440378 --- Comment #3 from Robert --- Fixed my issue by not using virtualdeaktopbar widget. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Blurry graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 --- Comment #25 from Robert --- (In reply to Nate Graham from comment #22) > It looks like all the Frameworks packagers are on vacation right now, so > unfortunately a new Frameworks release from KDE is not likely. I've emailed > distros about this and asked them to backport it themselves, so the good > distros should be shipping the a backport soon. Thanks Nate, Arch has already backported the fix to stable and I just installed the latest KSvg and Plasma 6.1 and can confirm that all artifacts are gone, keep up the good work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] New: Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 Bug ID: 487780 Summary: Fullscreen game stutter when Plasma receives notifications. Classification: Plasma Product: kwin Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: performance Assignee: kwin-bugs-n...@kde.org Reporter: robert.biel...@outlook.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When playing fullscreen games, in particular games using Steam Proton and DXVK (most likely all fullscreen games), there is a momentary drop in frame rate as the desktop notification is received and again as it disappears. It is important to clarify that nothing actually renders over the game, only the momentary stutter that corresponds with the time the notification would appear on the desktop had the game not been running fullscreen. This should not be happening since nothing is actually rendered over the game and nothing should be disturbing the rendering process with direct scanout working consistently. This happens with all notifications and is most noticeable for me with KDE Connect messages from my phone. STEPS TO REPRODUCE 1. Make sure "Screen Tearing: Allow in fullscreen windows" is enabled in Plasma display configuration. 2. Launch a Vulkan game in fullscreen mode. 3. Set VSync in the game or a constant frame rate so that the game is perfectly smooth (Preferably use a Vulkan hood such as DXVK_HUD with frametimes graph overlay). 4. Trigger a desktop notification such as a text message with KDE Connect via Android. 5. Observe a sudden momentary stutter and corresponding spike in the frametime graph when a notification comes in to the desktop such as KDE Connect and once again when it disappears. OBSERVED RESULT A momentary stutter and spike in frametime is observed when Plasma gets a notification in an otherwise perfectly smooth VSync'd game experience. EXPECTED RESULT The frame rate should remain perfectly smooth with no stutter during background notification reception and frametimes should be consistent all the time. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS XTREME System Version: -CF ADDITIONAL INFORMATION Mesa 24.1.0 with RADV drivers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 --- Comment #2 from Robert --- Yes, I will do that when I get the chance tomorrow and follow up with you. Thanks, Robert From: Zamundaaa Sent: June 5, 2024 6:00 AM To: robert.biel...@outlook.com Subject: [kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications. https://bugs.kde.org/show_bug.cgi?id=487780 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Zamundaaa --- Can you test the same scenario after putting KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and rebooting? Do you still see stutter then? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 --- Comment #3 from Robert --- Just following up, I can confirm that after setting the environment variable KWIN_DRM_NO_DIRECT_SCANOUT=1 and rebooting, there is no stutter present and everything is perfectly smooth in the same gaming scenario when receiving desktop notifications. This likely points to a bug in the direct scanout implementation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 Robert changed: What|Removed |Added CC||robert.biel...@outlook.com --- Comment #11 from Robert --- (In reply to Natalie Clarius from comment #9) > Okay, seem reasonable enough. > > It sounds to be like this use case would be even better addressed by adding > support for activating night light based on an ambient light sensor, in > addition to the ability to temporarily turn it off manually (eg for watching > a video). But that would of course only work on devices that actually have > an ambient light sensor. So maybe adding a "Manual mode" makes sense anyway. I have a similar use case like Sin Jeong-hun and a manual mode is definitely needed to make the feature more useful and flexible, it would make the feature behave similarly to Windows 11 and Android which is probably what most users expect as there is a lot more criteria that determines the use of the blue light filter than simply scheduling. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 475937] Unable to print in landscape mode
https://bugs.kde.org/show_bug.cgi?id=475937 Robert changed: What|Removed |Added CC||robert.biel...@outlook.com --- Comment #5 from Robert --- Same issue for me, Landscape printing is broken in all KDE applications, other programs are fine. This isn't a good look for KDE as minor bugs are understandable, while broken basic functionality isn't and some sort of unit testing/quality assurance is required. System info is as follows and as you can see it has been 7 months since this bug has been reported and countless updates: Operating System: EndeavourOS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 KDE Applications Version: 24.05.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS XTREME System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 --- Comment #5 from Robert --- Reviewing the Desktop Effects KCM, the only thing that stands out is the effect called "Fading Popups" as they seem to smoothly fade in and out when they show and disappear. I didn't make any changes to this module and use the default effect settings as packaged by Arch/EndeavourOS. Thanks for looking into this minor, but still important issue. From: Zamundaaa Sent: June 9, 2024 12:42 PM To: robert.biel...@outlook.com Subject: [kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications. https://bugs.kde.org/show_bug.cgi?id=487780 Zamundaaa changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Zamundaaa --- okay, then direct scanout is definitely getting interrupted, when it shouldn't be. Do you have any effects that would be acting on notifications? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 Robert changed: What|Removed |Added CC||robert.biel...@outlook.com --- Comment #10 from Robert --- I can also reproduce, a fresh session works fine, however, when a window is maximized and then closed, the bug appears. The tooltips for panel elements are also defective with cut off corners where some of them don't have rounding. Operating System: EndeavourOS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS XTREME System Version: -CF Video Drivers: Mesa 24.1.1 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 481797] New: Download New Plasma Widgets -- Plasma
https://bugs.kde.org/show_bug.cgi?id=481797 Bug ID: 481797 Summary: Download New Plasma Widgets -- Plasma 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: forsyth1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have no idea what the parent program is, so i am sorry if this is in the wrong place. STEPS TO REPRODUCE 1. Right click on the desktop and click Add Widgets... 2. Click Get new Widgets. 3. Download New Plasma Widgets OBSERVED RESULT The "Contribute your own" button is misleading. it takes you to the kde store. EXPECTED RESULT A link to development information / wiki to learn how to make and "contribute your own" widgets. IDEA A link could be potentially placed in the KDE store section of the window after clicking "Contribute your own" That way users could access the store and how to contribute in the same place. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-18-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7971 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 481798] New: A Search feature is needed
https://bugs.kde.org/show_bug.cgi?id=481798 Bug ID: 481798 Summary: A Search feature is needed Classification: Websites Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: database Assignee: sysad...@kde.org Reporter: forsyth1...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY tried submitting a bug for what i would logically call "widgets". its probably a daughter part of a bigger program but because i am not a developer i have no clue what to call it other than widgets. STEPS TO REPRODUCE 1. not be a developer 2. have a problem with widgets 3. cant find the right application on the website because there is no search facility. OBSERVED RESULT a frustrated user. EXPECTED RESULT a slightly less frustrated user. IDEAS 1)update website with search functionality. 2)add a settings page in kde-plasma that handles bug reports. (it could even have an eye dropper tool, so you can select the app that your having problems with. ) SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-18-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7971 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[season.kde.org] [Bug 481799] New: weird link
https://bugs.kde.org/show_bug.cgi?id=481799 Bug ID: 481799 Summary: weird link Classification: Websites Product: season.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: say...@kde.org Reporter: forsyth1...@gmail.com CC: ly...@kde.org, t...@kde.org Target Milestone: --- SUMMARY click Ideas. it returns a page that has no ideas or text. STEPS TO REPRODUCE google chrome.. ..probably doesn't matter though OBSERVED RESULT no ideas EXPECTED RESULT ideas SOFTWARE/OS VERSIONS Google Chrome Version 122.0.6261.69 (Official Build) (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 481875] New: [PLASMA6] [QT6] Broken UI and unreadable text
https://bugs.kde.org/show_bug.cgi?id=481875 Bug ID: 481875 Summary: [PLASMA6] [QT6] Broken UI and unreadable text Classification: Applications Product: kamoso Version: 24.01.95 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: r1o2b3e4r...@tutanota.com Target Milestone: --- Created attachment 166116 --> https://bugs.kde.org/attachment.cgi?id=166116&action=edit Broken UI Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 481875] [PLASMA6] [QT6] Broken UI and unreadable text
https://bugs.kde.org/show_bug.cgi?id=481875 --- Comment #1 from Robert --- Created attachment 166117 --> https://bugs.kde.org/attachment.cgi?id=166117&action=edit Unreadable text -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 481875] [PLASMA6] [QT6] Broken UI and unreadable text
https://bugs.kde.org/show_bug.cgi?id=481875 Robert changed: What|Removed |Added CC||r1o2b3e4r...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481879] New: system with lid closed suspends after turning off
https://bugs.kde.org/show_bug.cgi?id=481879 Bug ID: 481879 Summary: system with lid closed suspends after turning off Classification: Plasma Product: Powerdevil Version: git-stable-Plasma/5.27 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: r...@bugs.kde.pu.futz.org CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 166121 --> https://bugs.kde.org/attachment.cgi?id=166121&action=edit journal with systemd-logind lidswitch settings set to ignore SUMMARY I'm running fedora 38 kde spin (5.27.10-1.fc38.x86_64). My laptop has an external hdmi monitor mirroring laptop panel, and is configured NOT to sleep when the lid is closed and a external monitor is connected. That works. The other day I also configured it to turn of the display after 15 minutes. This works, but then the system suspends, apparently having forgotten that the external monitor is connected. This is all with AC power, set to never sleep automatically. STEPS TO REPRODUCE 1. connect external monitor 2. configure to not sleep when lid closed with monitor connected 3. close lid 4. configure to turn of screen after 1 minute and apply changes 5. wait one minute OBSERVED RESULT screen is turned off, then laptop sleeps EXPECTED RESULT screen is turned off, but laptop does not sleep SOFTWARE/OS VERSIONS Linux/KDE Plasma: KWin version: 5.27.10 Qt Version: 5.15.11 Qt compile version: 5.15.11 XCB compile version: 1.13.1 Operation Mode: X11 only ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481879] system with lid closed suspends after turning off external monitor
https://bugs.kde.org/show_bug.cgi?id=481879 Robert changed: What|Removed |Added Summary|system with lid closed |system with lid closed |suspends after turning off |suspends after turning off ||external monitor -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484349] New: Feature Request; Add a custom suffix to drives.
https://bugs.kde.org/show_bug.cgi?id=484349 Bug ID: 484349 Summary: Feature Request; Add a custom suffix to drives. Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: forsyth1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY This is a feature request. I have a hot-swappable bays on my computer. I would like either a custom icon or a custom suffix to distinguish them from non-removable drives. (hot swap is an option in the UEFI so, is it detectable by Linux? has Dolphin not implemented the feature?) for example "foo_drive", would become "(hot) Foo_Drive" or "(SATA4) Foo_Drive" etc.. . The suffix shouldn't change when a new drive is inserted into the slot, but the drive name should. very useful for larger systems or servers with lots of drives. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-18-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 62.8 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7971 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453430] New: Dolphin crashed after closing tab
https://bugs.kde.org/show_bug.cgi?id=453430 Bug ID: 453430 Summary: Dolphin crashed after closing tab Product: dolphin Version: 22.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rob...@axium.co.nz CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.4.0-107-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Dolphin had 4 different tabs open and closing the fourth tab was the trigger. Not sure what made it special, but it was largely full of executable binary files. Closing any other tab first would allow that one to close without issue and closing ther others seemed to work reliably. Sometimes closing the tab in question would work without crashing, in which case opening another tab and navigating to the folder allowed it to again be reproduced once closed. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 57051] [New LWP 57052] [New LWP 57053] [New LWP 57054] [New LWP 57055] [New LWP 57056] [New LWP 57057] [New LWP 57659] [New LWP 57678] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc86d2f2508 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 __preamble__ [Current thread is 1 (Thread 0x7fc86a6bf9c0 (LWP 57049))] Thread 10 (Thread 0x7fc8437fe700 (LWP 57678)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fc86f581975 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc8719e176e in QMutexLocker::QMutexLocker (m=, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:238 #3 UpdateItemStatesThread::run (this=0x55bea85778c0) at ./src/views/versioncontrol/updateitemstatesthread.cpp:33 #4 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fc843fff700 (LWP 57659)): [KCrash Handler] #4 0x in ?? () #5 0x7fc8719e186f in UpdateItemStatesThread::run (this=0x55bea8605ca0) at ./src/views/versioncontrol/updateitemstatesthread.cpp:41 #6 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fc859ffb700 (LWP 57057)): #0 __GI___libc_read (nbytes=16, buf=0x7fc859ffa9d0, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=22, buf=0x7fc859ffa9d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fc86d2edb2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc86d2a4ebe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc86d2a5312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc86d2a54a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc86f7c265b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc86f76687b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc86f580442 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fc85a7fc700 (LWP 57056)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fc85a7fbb50, clockid=, expected=0, futex_word=0x55bea7e186f0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc85a7fbb50, clockid=, mutex=0x55bea7e186a0, cond=0x55bea7e186c8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55bea7e186c8, mutex=0x55bea7e186a0, abstime=0x7fc85a7fbb50) at pthread_cond_wait.c:656 #3 0x7fc86f587618 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc86f584b21 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/li
[kde] [Bug 453799] New: KDE Connect setting custom commands
https://bugs.kde.org/show_bug.cgi?id=453799 Bug ID: 453799 Summary: KDE Connect setting custom commands Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: --- Application: kdeconnect-settings (22.04.0) Qt Version: 5.15.2 Frameworks Version: 5.93.0 Operating System: Linux 5.17.5-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was trying to add a custom command, and when I open the settings for that it crashes everytime. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect Settings (kdeconnect-settings), signal: Segmentation fault [KCrash Handler] #4 0x7fc47911dd58 in std::__uniq_ptr_impl >::_M_ptr (this=) at /usr/include/c++/12/bits/unique_ptr.h:191 #5 std::unique_ptr >::get (this=) at /usr/include/c++/12/bits/unique_ptr.h:462 #6 std::unique_ptr >::operator-> (this=) at /usr/include/c++/12/bits/unique_ptr.h:455 #7 qGetPtrHelper > const> (ptr=...) at /usr/include/qt5/QtCore/qglobal.h:1143 #8 KSycocaEntry::d_func (this=) at /usr/src/debug/kservice-5.93.0-1.2.x86_64/src/sycoca/ksycocaentry.h:139 #9 KSycocaEntry::property (this=0x0, name=...) at /usr/src/debug/kservice-5.93.0-1.2.x86_64/src/sycoca/ksycocaentry.cpp:104 #10 0x7fc468b1f425 in KdeConnectPluginKcm::KdeConnectPluginKcm (this=, parent=, args=..., componentName=..., this=, parent=, args=..., componentName=...) at /usr/src/debug/kdeconnect-kde-22.04.0-1.2.x86_64/kcmplugin/kdeconnectpluginkcm.cpp:26 #11 0x7fc468b29339 in RunCommandConfig::RunCommandConfig (args=..., parent=0x5645ddc7b3c0, this=0x7fc464011bb0) at /usr/src/debug/kdeconnect-kde-22.04.0-1.2.x86_64/plugins/runcommand/runcommand_config.cpp:29 #12 KPluginFactory::createInstance (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:875 #13 0x7fc47aafe5c3 in KPluginFactory::create (this=0x5645ddd4ceb0, iface=0x7fc4790be9a0 "KCModule", parentWidget=0x5645ddc7b3c0, parent=0x5645ddc7b3c0, args=..., keyword=...) at /usr/src/debug/kcoreaddons-5.93.0-1.2.x86_64/src/lib/plugin/kpluginfactory.cpp:232 #14 0x7fc47abdd015 in KPluginFactory::create (args=..., parent=0x5645ddc7b3c0, keyword=..., this=0x5645ddd4ceb0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:936 #15 KCModuleLoader::loadModule (metaData=..., parent=0x5645ddc7b3c0, args=...) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleloader.cpp:98 #16 0x7fc47abdfd0d in KCModuleProxyPrivate::loadModule (this=0x5645ddd90e50) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleproxy.cpp:119 #17 0x7fc47abe0338 in KCModuleProxy::realModule (this=) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleproxy.cpp:59 #18 0x7fc47abf2f7c in PluginDelegate::configure (this=this@entry=0x5645ddc40da0, index=...) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kpluginwidget.cpp:486 #19 0x7fc47abf372a in PluginDelegate::slotConfigureClicked (this=0x5645ddc40da0) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kpluginwidget.cpp:471 #20 0x7fc4799e0def in QtPrivate::QSlotObjectBase::call (a=0x7ffcb5d38880, r=0x5645ddc40da0, this=0x5645ddc81640) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x5645ddc8c900, signal_index=9, argv=0x7ffcb5d38880) at kernel/qobject.cpp:3886 #22 0x7fc4799da0cf in QMetaObject::activate (sender=sender@entry=0x5645ddc8c900, m=m@entry=0x7fc47aa6e180 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb5d38880) at kernel/qobject.cpp:3946 #23 0x7fc47a646152 in QAbstractButton::clicked (this=this@entry=0x5645ddc8c900, _t1=) at .moc/moc_qabstractbutton.cpp:308 #24 0x7fc47a6463ba in QAbstractButtonPrivate::emitClicked (this=0x5645ddd38060) at widgets/qabstractbutton.cpp:415 #25 0x7fc47a647f48 in QAbstractButtonPrivate::click (this=0x5645ddd38060) at widgets/qabstractbutton.cpp:408 #26 0x7fc47a648167 in QAbstractButton::mouseReleaseEvent (this=0x5645ddc8c900, e=0x7ffcb5d38e00) at widgets/qabstractbutton.cpp:1044 #27 0x7fc47a595f48 in QWidget::event (this=0x5645ddc8c900, event=0x7ffcb5d38e00) at kernel/qwidget.cpp:9020 #28 0x7fc47a55437e in QApplicationPrivate::notify_helper (this=this@entry=0x5645dd8cf270, receiver=receiver@entry=0x5645ddc8c900, e=e@entry=0x7ffcb5d38e00) at kernel/qapplication.cpp:3632 #29 0x7fc47a55c8c2 in QApplication::notify (this=, receiver=0x5645ddc8c900, e=) at kernel/qapplication.cpp:3076 #30 0x7fc4799a9988 in QCoreApplication::notifyInternal2 (receiver=0x5645ddc8c900, event=0x7ffcb5d38e00) at kernel/qcoreapplication.cpp:1064
[plasmashell] [Bug 456369] New: Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 Bug ID: 456369 Summary: Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery Product: plasmashell Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: robertdeja...@tutanota.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 150427 --> https://bugs.kde.org/attachment.cgi?id=150427&action=edit Some journalctl entries from the previous boot (that got stuck because of this issue) After upgrading to Plasma Desktop 5.25, disconnecting a monitor attached through USB-C (HDMI Alt Mode) results in a black screen. Reconnecting it does not restore video. The only thing that helps is to force a reboot. I cannot try a direct HDMI connection, because my laptop doesn't have one. It happens consistently since upgrading the Plasma Desktop. Version 5.24 worked fine. I have tried a Gnome session to make sure nothing else is causing this issue. In Gnome it works fine. STEPS TO REPRODUCE 1. Start a Plasma Shell session with an external monitor connected using an USB-C dock 2. Disconnect either the monitor, or the whole dock 3. Laptop screen does not turn on 4. Reconnect the external monitor / dock 5. No image on either monitor 6. Try to switch to a virtual terminal (ctrl-alt-f3) 7. Still no picture Black screen, no matter what I do Laptop screen turns on when disconnecting the monitor, external screen shows desktop when plugging it back in. SOFTWARE/OS VERSIONS Linux version: 5.18.9 KDE Plasma Version: 5.25.0 / 5.25.1 / 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5+kde+r167 Mesa Version: 22.1.3 Hardware: Dell XPS 13 9310 2 in 1 Intel Core i7 1165G7 Iris XE Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #42 from Robert --- Are we sure https://bugs.kde.org/show_bug.cgi?id=456369 is a duplicate of this one? I can't find any entries in the uploaded logs that match the ones I attached to the other bug report. Also, the issue here seems to be entirely non functional usb-c monitors. In my experience, the monitor works fine (connected before boot). Both external monitor and built in fail after disconnecting it, until reboot. The log entry that caught my eye was: plasmashell[1693]: requesting unexisting screen 0 There are a lot of those, everytime I reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #3 from Robert --- Created attachment 150473 --> https://bugs.kde.org/attachment.cgi?id=150473&action=edit journalctl log, filtered for kwin_wayland following line was added to /etc/environment QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #4 from Robert --- Comment on attachment 150473 --> https://bugs.kde.org/attachment.cgi?id=150473 journalctl log, filtered for kwin_wayland The following line was added to /etc/environment: QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #5 from Robert --- Created attachment 150474 --> https://bugs.kde.org/attachment.cgi?id=150474&action=edit journalctl log, filtered for plasmashell The following line was added to /etc/environment: QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #6 from Robert --- Nate and Zamundaaa, Thanks for responding so quickly. I have attached the log like you asked, and added one with plasmashell entries just in case. The logs are too big to attach as they are, so I gzipped them. Hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #7 from Robert --- I discovered some more odd behaviour. First of all, disconnecting / reconnecting the dock caused the whole system to freeze for a few seconds, or at least my ssh session. I also tried reproducing the issue with the lid opened, and the laptop monitor enabled, scale 200%. The external monitor was set as primary screen, scale 150%. In this scenario, the laptop monitor took over as expected after disconnecting the dock. Reconnecting it did not give me back my external monitor, but at least the laptop monitor kept working. Other devices connected to the dock (mouse and keyboard) will come online most of the times when plugging it in, but not always. In that case, disconnecting and reconnecting would fix that. Logging out of plasma and back in with the dock plugged in results in a fully working system. Sometimes the scale of the external monitor is wrong (set to 150%, but this is not applied). Switching to another setting and back fixes that too. I'll try to get some more logs for you tomorrow doing what I described above. Is there anything else you want me to try? Have a nice evening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #9 from Robert --- Created attachment 150552 --> https://bugs.kde.org/attachment.cgi?id=150552&action=edit DRM log entries while reproducing the issue Commands: echo 0x1FF | sudo tee /sys/module/drm/parameters/debug sudo dmesg -w > dmesg.log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #11 from Robert --- Great news. Archlinux usually keeps on top of these things, so I expect I can inform you of the results before the end of the week. In the mean time, I discovered an workaround to sort of recover from this: - Make sure the primary (laptop) display is enabled (doesn't have to be primary) - Unplug the dock - Switch to another virtual terminal (ctrl-alt-f4) - Plug in the dock - Wait for the display to reinitialize - Switch back to the Plasma session (ctrl-alt-f2) It seems to crash and restart when I do that, but at least I have full use of my secondary monitor again without having to log out. The background was missing on the primary display, but running "plasmashell --replace" fixed that also. I will let you know if version 5.23 fixes the original issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #12 from Robert --- Correction, 5.25.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #13 from Robert --- I have hotplugged the monitor a few times with plasma 5.25.3, and it turned on every time. Thank you for all your efforts. You guys are awesome. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #6 from Robert --- I will definitely give it a try when I get home from work. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #7 from Robert --- I followed your instructions and it crashed again and this time when I started latte i ran it through konsole and it ended up segfaulting and crashed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #9 from Robert --- Nothing in particular I have pinned a wide variety of applications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441453] New: PIM Calendar Missing
https://bugs.kde.org/show_bug.cgi?id=441453 Bug ID: 441453 Summary: PIM Calendar Missing Product: plasmashell Version: 5.22.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: 1.0 Created attachment 140991 --> https://bugs.kde.org/attachment.cgi?id=140991&action=edit screenshot of missing PIM calendar event section SUMMARY STEPS TO REPRODUCE 1. Removed digital clock widget and re-added 2. Done above and restarted OBSERVED RESULT The same with the above steps EXPECTED RESULT PIM Calendar events to appear SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User Edition (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440753] New: Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 Bug ID: 440753 Summary: Latte Crashes when pinning applications Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I was opening applications so I could pin them to Latte-Dock. I have had this happen a couple of times and so it is definitely reproduceible The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 31415] [New LWP 31416] [New LWP 31417] [New LWP 31418] [New LWP 31419] [New LWP 31420] [New LWP 31423] [New LWP 31435] [New LWP 31443] [New LWP 31444] [New LWP 31445] [New LWP 31446] [New LWP 31447] [New LWP 31448] [New LWP 31449] [New LWP 31450] [New LWP 31451] [New LWP 31452] [New LWP 31453] [New LWP 31454] [New LWP 31459] [New LWP 31467] [New LWP 31468] [New LWP 31469] [New LWP 31470] [New LWP 31471] [New LWP 31477] [New LWP 32068] [New LWP 32069] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x555996a807d0) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fe623cc09c0 (LWP 31414))] Thread 30 (Thread 0x7fe55a619700 (LWP 32069)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x555995fe1a04) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555995fe19b0, cond=0x555995fe19d8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555995fe19d8, mutex=0x555995fe19b0) at pthread_cond_wait.c:647 #3 0x7fe627d2ff2b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x555995fe19b0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x5559a6a96458, mutex=mutex@entry=0x5559a6a96450, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fe629f09b44 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x5559a6a96448) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x5559a6a963b0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7fe629f09fb9 in QSGRenderThread::run() (this=0x5559a6a963b0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7fe627d29dbc in QThreadPrivate::start(void*) (arg=0x5559a6a963b0) at thread/qthread_unix.cpp:329 #9 0x7fe627719609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe62785b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fe55bcf9700 (LWP 32068)): #0 0x7fe6261a14dd in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe626153dac in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe626154312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe6261544a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe627f6afcb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe58c0f99b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe627f0f25b in QEventLoop::exec(QFlags) (this=this@entry=0x7fe55bcf8bc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7fe627d28c22 in QThread::exec() (this=this@entry=0x7fe61c0218d0) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7fe629b8f559 in QQmlThreadPrivate::run() (this=0x7fe61c0218d0) at qml/ftw/qqmlthread.cpp:155 #8 0x7fe627d29dbc in QThreadPrivate::start(void*) (arg=0x7fe61c0218d0) at thread/qthread_unix.cpp:329 #9 0x7fe627719609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe62785b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fe5a2417700 (LWP 31477)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5559a2eca000) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5559a2ec9fb0, cond=0x5559a2ec9fd8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5559a2ec9fd8, mutex=0x5559a2ec9fb0) at pthread_cond_wait.c:647 #3 0x7fe627d2ff2b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5559a2ec9fb0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #2 from Robert --- I had reproduced this by doing the same exact thing I was doing when it happened the first time. I opened four different applications and started pinning them to latte-dock one by one after I pinned them the desktop became unresponsive then latte-dock crashed then restarted itself. Not sure what more steps you might need. If you need more info be specific please. I will definitely help where I can in order to provide more info. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #4 from Robert --- I pinned them to latte by right clicking them and selecting pin to dock on all activities. I’m not sure of the exact wording but it was something in that range. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419399] Laggy interface with kinetic scrolling and canvas and UI glitches.
https://bugs.kde.org/show_bug.cgi?id=419399 Robert changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED CC||rggor...@gmail.com Status|NEEDSINFO |RESOLVED --- Comment #4 from Robert --- It is still an issue on my older Gentoo git build install. However, I just did a fresh install and am using the krita build that is in the portage and there is no lag in the kinetic scrolling. But I have not installed the git version yet to test it for the master version. So, I am not sure why it is still an issue with my previous install, my guess is I have some issues with the compiler on that installation. Sorry it took me a while to re-post on this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] New: Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 Bug ID: 424482 Summary: Album view crashes creating thumbnails Product: digikam Version: 6.4.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: robertlbec...@verizon.net Target Milestone: --- SUMMARY Working with digiKam 6.4.0 on Win10 Lenovo host with solid state drive. DigiKam exits unexpectedly from album view while creating thumbnails from recently added images. STEPS TO REPRODUCE 1. Created (using Windows File Explorer) a new folder within my specified image file tree, containing about 70 16-bit gray-value tiff images newly scanned from prints using VueScan 9.7.28, TIFF compression "On", driving an Epson Perfection V600 scanner. Scanned photos are 5" x 7", scanned at 400 dpi (about 11Mbytes each on disk). Windows File Explorer displays thumbnails for all images as expected. Albums | - digiKam_Photos | - Print Color | - Print Gray <--folder with relevant images | - Trash 2. Launch digiKam. The "Find new items" process completes without complaint. 3. Open the Albums tree to view the image directory. Wait as long as I care to wait -- seconds to minutes. Click on the folder containing the newly scanned images. OBSERVED RESULT 1. On first attempt to view the album, one thumbnail (for the first image) was displayed, then the program exited. 2. With each subsequent launch of digiKam, upon opening the album view for the relevant folder, the previously available thumbnails are displayed, plus 0 to 2 (usually 1) new thumbnails for additional images, but the program then exits. EXPECTED RESULT Creation and display of thumbnails for all images in the folder. SOFTWARE/OS VERSIONS Windows: Win10Pro 10.0.19041 Build 19041 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.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #2 from Robert --- Per suggestion to furnish examples of images triggering the bug, I've placed three files (too large to attach here) at my dropbox public folder. Please see: https://www.dropbox.com/s/3ev74e02346iu4f/PG0006.tif?dl=0 https://www.dropbox.com/s/7q2tixtt99rg9zh/PG0013.tif?dl=0 https://www.dropbox.com/s/in0b1ji4e8xob05/PG0014.tif?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #3 from Robert --- Thanks for your rapid reply! Have posted three images, via update to the bug report file. Criticality of the bug might be overtaken by events, if I can find a good way to scan directly to PNG files. Originally intended to do this using an Acquire Images Tool furnished as part of digiKam -- but have been unable to find the tool through the user interface. An email to the users group asking about this is pending the list moderator's approval of my subscription. -Original Message- From: Maik Qualmann Sent: Monday, July 20, 2020 3:18 PM To: robertlbec...@verizon.net Subject: [digikam] [Bug 424482] Album view crashes creating thumbnails https://bugs.kde.org/show_bug.cgi?id=424482 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Please try digiKam-7.0.0 from here: https://files.kde.org/digikam/ We fixed a memory request problem in digiKam-7.0.0 that could be triggered with large TIFF files. However, we still have an open bug report on TIFF files under Windows. It would be nice if you could provide a test TIFF file through an upload service. Maik -- You are receiving this mail because: You reported the bug.= -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #5 from Robert --- Will be glad to try out digiKam 7.0.0. Am I correct to conclude that the relevant download is: https://download.kde.org/unstable/digikam/digiKam-7.0.0-rc-Win64.exe dated 14-Jun-2020 10:00? Hopefully an automatic installer (analogous to what I used for 6.4.0? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #6 from Robert --- ...oh, I see now the 16 July file postings. Will proceed with the 32 bit version via link https://files.kde.org/digikam/digiKam-7.0.0-20200716T095418-Win32.exe -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #7 from Robert --- ... better yet (I hope), the installable version from https://files.kde.org/digikam/digiKam-7.0.0-20200716T122924-Win64.exe Apologies for the incremental updates. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 --- Comment #8 from Robert --- Version 7.0.0 installed like a dream and zipped licketysplit through creating thumbnails for all 70+ images in the folder. Looks like the relevant bug is history. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424482] Album view crashes creating thumbnails
https://bugs.kde.org/show_bug.cgi?id=424482 Robert changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] New: Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 Bug ID: 479454 Summary: Letter and basic avatars with changeable backgrounds do not work Classification: Applications Product: systemsettings Version: 5.91.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: rob...@greencafe24.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 164699 --> https://bugs.kde.org/attachment.cgi?id=164699&action=edit Screenshot SUMMARY When trying to change the profile picture to the letter or basic avatar, the button to open the background colour selector works, but actually changing the avatar does not. STEPS TO REPRODUCE 1. Open System Settings 2. Go to the Users tab 3. Click Change Avatar 4. Click on the letter or the basic avatar 5. Choose a colour OBSERVED RESULT Nothing works except the back button EXPECTED RESULT The avatar should be applied with the selected background colour SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.7.0-0.rc8.61.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 Robert changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #5 from Robert --- Thank you very much, setting the avatar now works. But what does not work is the preview, if you have selected an avatar it should appear in the preview, instead the placeholder letter always appears. [Screenshot 1] When you click on apply, the avatar is displayed in the preview, although it is displayed in a very square circle, but is also not updated correctly in the user list. [Screenshot 2] Only when you reopen the user settings is everything updated, the square circle remains. [Screenshot 3] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 --- Comment #7 from Robert --- Created attachment 164924 --> https://bugs.kde.org/attachment.cgi?id=164924&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 --- Comment #8 from Robert --- Created attachment 164925 --> https://bugs.kde.org/attachment.cgi?id=164925&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 --- Comment #6 from Robert --- Created attachment 164923 --> https://bugs.kde.org/attachment.cgi?id=164923&action=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479929] New: The preview for avatars with a changeable background does not work properly
https://bugs.kde.org/show_bug.cgi?id=479929 Bug ID: 479929 Summary: The preview for avatars with a changeable background does not work properly Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: rob...@greencafe24.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 164967 --> https://bugs.kde.org/attachment.cgi?id=164967&action=edit Screenshot 1 SUMMARY If you have selected an avatar it should appear in the preview, instead the placeholder letter always appears. [Screenshot 1] When you click on apply, the avatar is displayed in the preview, although it is displayed in a very square circle, but is also not updated correctly in the user list. [Screenshot 2] Only when you reopen the user settings is everything updated, the square circle remains. [Screenshot 3] STEPS TO REPRODUCE 1. Open System Settings 2. Go to the Users tab 3. Click Change Avatar 4. Click on the letter or the basic avatar 5. Choose a colour OBSERVED RESULT See summary EXPECTED RESULT Same behavior as with image-based avatars SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-14-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479929] The preview for avatars with a changeable background does not work properly
https://bugs.kde.org/show_bug.cgi?id=479929 --- Comment #1 from Robert --- Created attachment 164968 --> https://bugs.kde.org/attachment.cgi?id=164968&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479929] The preview for avatars with a changeable background does not work properly
https://bugs.kde.org/show_bug.cgi?id=479929 --- Comment #2 from Robert --- Created attachment 164969 --> https://bugs.kde.org/attachment.cgi?id=164969&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479929] The preview for avatars with a changeable background does not work properly
https://bugs.kde.org/show_bug.cgi?id=479929 Robert changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=479454 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479454] Letter and basic avatars with changeable backgrounds do not work
https://bugs.kde.org/show_bug.cgi?id=479454 Robert changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=479929 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472547] New: KIO-Gdrive hangs adding a new google account
https://bugs.kde.org/show_bug.cgi?id=472547 Bug ID: 472547 Summary: KIO-Gdrive hangs adding a new google account Classification: Applications Product: dolphin Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bowman.robe...@gmail.com CC: kfm-de...@kde.org 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. Open settings, select online accounts, select "google" 2. Enter email in web authentication window 3. Select "next" OBSERVED RESULT Window greys out and hangs, with progress indicator moving across the top EXPECTED RESULT Second page displays asking for password SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 472547] KIO-Gdrive hangs adding a new google account
https://bugs.kde.org/show_bug.cgi?id=472547 Robert changed: What|Removed |Added CC||sit...@kde.org Platform|Other |Kubuntu Product|dolphin |kdenetwork-filesharing Component|general |general Version|23.04.3 |unspecified Assignee|dolphin-bugs-n...@kde.org |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474900] New: Panel steals Keyboard focus in amazon luna fullscreen
https://bugs.kde.org/show_bug.cgi?id=474900 Bug ID: 474900 Summary: Panel steals Keyboard focus in amazon luna fullscreen Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: elles.rob...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When starting a game with amazon luna in chromium (v 117) any key press exits the fullscreen of the game and highlights the kde panel. From that on the game doesn't receive any more key press events. STEPS TO REPRODUCE 1. Start a game in amazon luna 2. Try to play the game using the keyboard 3. the kde panel takes over OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Everything very up to date Linux/KDE Plasma: 5.27.8 (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 474900] Panel steals Keyboard focus in amazon luna fullscreen
https://bugs.kde.org/show_bug.cgi?id=474900 --- Comment #1 from Robert --- The problem still persists even when removing the panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474900] Panel steals Keyboard focus in amazon luna fullscreen
https://bugs.kde.org/show_bug.cgi?id=474900 Robert changed: What|Removed |Added CC||k...@davidedmundson.co.uk Component|Panel |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474900] Panel steals Keyboard focus in amazon luna fullscreen
https://bugs.kde.org/show_bug.cgi?id=474900 --- Comment #3 from Robert --- Removing it or setting the panel to auto hide prevents it from poping into the game. On Wayland still keyboard events after the first key press are not registered by the game anymore. I have to press alt+tab to focus back to the game, then I can do one more key press before the focus is lost again. On X11 the keyboard focus actually remains. It's just the panel has to be hidden too. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475577] New: Failed UPdate Install
https://bugs.kde.org/show_bug.cgi?id=475577 Bug ID: 475577 Summary: Failed UPdate Install Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: messier42or...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org 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. Open Discover 2. Go to update 3. Select packages you want to update 4. Run update OBSERVED RESULTS Failed to update 1 package Error while installing package: trying to overwrite '/usr/lib/x86_64-linux-gnu/libIex-3_1.so.30.11.1', which is also in package libopenexr30 EXPECTED RESULT Install packages without cross package name issues SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475577] Failed UPdate Install
https://bugs.kde.org/show_bug.cgi?id=475577 Robert changed: What|Removed |Added CC||messier42or...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Robert changed: What|Removed |Added CC||robertpaulrush+linux@gmail. ||com --- Comment #63 from Robert --- I have also been experiencing this bug, and it seemed to be happening on its own after random time intervals but I managed to get it to happen consistently and immediately. It's possible this comment should be a new/separate bug with the same behavior, but I think it's very possible people are not actually doing NOTHING until the taskbar becomes unresponsive. I personally did not observe the taskbar freezing if I truly did nothing with the computer. Providing additional steps to reproduce that may lead to a fix: STEPS TO REPRODUCE 1. Boot into Plasma Desktop under Wayland. 2. Right click task manager -> Configure icons-only task manager -> Icons-only task manager settings -> Behavior. 3. Set "Group" to "by program name". 4. Enable "Mouse wheel cycles through tasks", apply if needed. 5. Open multiple windows of any one application that supports multiple windows (I tried this separately with Firefox, Dolphin, and Konsole). 6. Position the cursor over the icon in the icons-only task manager for that application. 7. Use the mouse wheel to cycle between open windows of that application. 8. Notice the unresponsiveness of the panel. Using the mouse wheel to switch between open windows consistently and immediately (or within a few seconds) renders the panel unresponsive. Sometimes, changing the grouping or mouse wheel scroll settings in task manager settings and applying will also cause this behavior. For me at least, this bug is tied directly to "mouse wheel: cycles through tasks" for programs "grouped: by program name" in the icons-only task manager. Using Latte-dock instead may be a temporary workaround for some. Can anyone confirm if they were experiencing this bug when doing absolutely nothing at all, just leaving the computer idle for x amount of time? Are you also able to reproduce with the steps provided / is it applicable to you? I would look into fixing this myself, but I'm not experienced with OS, Kernel, or Desktop development so it would take me a WHILE to find the source code, branch and parse through the source code, learn the appropriate language(s), set up a testing environment, fix it on my end, and push/request merge the fix. Hopefully this helps someone on the KDE team close this bug. PS: please go easy on me, this is my first comment here so I might not know this specific group's standards. RELATED NOTES * Steps 2-4 may be default settings, which could also explain why the issue is so pervasive. * Scrolling just on the taskbar to cycle through all windows does not produce the result, it is only when hovering over a grouped icon which limits the cycle to a single application. * Clicking to cycle also does NOT produce the result, only scrolling. * I saw somewhere that it could be tied to virtual desktops or other widgets, but none were the case for me. * Seems to be an issue across distros, KDE versions, AMD and Intel CPUs, and AMD and NVidia graphics cards. * Linking a related Reddit thread with more people experiencing this issue. It does not have this insight, but has a good summary from KDE ruling things out: https://www.reddit.com/r/kde/comments/snhb2c/kde_panel_plasma_frozen_what_to_try/ * The task manager will generally still open a program if you click on the icon, even though visually it is unresponsive. Since it's not listed here, I'm generally running the following command to reset the taskbar, which may have different behavior from `plasmashell --replace` but there seem to be variations of a similar thing: ``` systemctl --user restart plasma-plasmashell.service ``` ABOUT THIS SYSTEM Operating System: openSUSE Tumbleweed 20230902 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 --- Comment #66 from Robert --- (In reply to Nate Graham from comment #65) > If you have an NVIDIA GPU, you're experiencing Bug 469016; please post > comments there, not here. I didn't see any indication that this bug is exclusive to AMD, and bug 469016 is not exclusive to NVIDIA either, but I'll follow up there. Bug 469016 was reported as happening under "heavy load" and unhiding a hidden task bar, which is not applicable to me. That said, recent discussion tying it to window previews and pipewire is relevant. Going to Configure Icons-only Task Manager -> Appearance -> General -> and disabling "Show small window previews when hovering over tasks" prevents the issues for me. (In reply to Robert Svensson from comment #64) > I can also confirm this behavior. In my case however it DOES happen with > ungrouped windows. In fact when testing it just now I didn't have any grouped > windows in the task manager at all. Just hovering above any given window's > icon in the task manager and scrolling will immediately freeze the panel for > me like how it's described in the initial report. My task manager settings > are however the same as yours otherwise. > > Whether or not this is a separate issue I'm not sure, but at least it's a > consistent repro of the effects of the original reported bug. I will say > though that I never use the scroll wheel to switch between windows normally, > and still experience the issue frequently. So it seems to be triggered by > something else too, perhaps some other window switching/focus related action. I didn't experience it without grouped windows, but scrolling even with the scroll setting disabled still causes it unless "Show small window previews when hovering over tasks" is disabled. Disabling window previews prevents the issue for me, although this workflow is not ideal. Maybe the root cause is the same for both, maybe not, but hopefully this at least points some people in the right direction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 Robert changed: What|Removed |Added CC||robertpaulrush+linux@gmail. ||com --- Comment #58 from Robert --- Was experiencing related bug 449163, same symptoms and different steps to reproduce, and directed here. For me, just scrolling the mouse wheel while hovering over a grouped icon with multiple windows open will immediately freeze the taskbar as described. This only occurs if "Show small window previews when hovering over tasks" is enabled. Disabling window previews prevents the issue for me. The connection to pipewire makes sense - I recently experienced another taskbar bug (duplicate sound devices after sleep, https://forums.opensuse.org/t/audio-devices-remain-after-disconnect-on-plasma-5-27/168398) that also tied back to pipewire. Removing kpipewire breaks plasma5-desktop dependency, so I won't be trying that. Maybe the scrolling issue is related to previews having audio control. ABOUT THIS SYSTEM Operating System: openSUSE Tumbleweed 20230902 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 445466] OTP Popup disappears too fast with networkmanager-fortisslvpn
https://bugs.kde.org/show_bug.cgi?id=445466 Robert changed: What|Removed |Added CC||robertdeja...@tutanota.com --- Comment #2 from Robert --- The Networkmanager project also has a bug report open for this. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1158 The command line interface seems to have the same issue, so I don't think this is a KDE bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 455438] Fortinet VPN doesn't wait for DUO/2FA answer long enough
https://bugs.kde.org/show_bug.cgi?id=455438 Robert changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Robert --- *** This bug has been marked as a duplicate of bug 445466 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 445466] OTP Popup disappears too fast with networkmanager-fortisslvpn
https://bugs.kde.org/show_bug.cgi?id=445466 Robert changed: What|Removed |Added CC||vladimiro...@gmail.com --- Comment #3 from Robert --- *** Bug 455438 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462198] kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid
https://bugs.kde.org/show_bug.cgi?id=462198 --- Comment #5 from Robert --- The issue still presents itself sometimes after reconnecting the external monitor. Does anyone have any idea how to extract some useful information after it happens? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462198] kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid
https://bugs.kde.org/show_bug.cgi?id=462198 --- Comment #7 from Robert --- Ok, I'll wait until 5.27 lands, and try to update this ticket then. Happy holidays. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460880] New: Neochat is Crashing upon opening
https://bugs.kde.org/show_bug.cgi?id=460880 Bug ID: 460880 Summary: Neochat is Crashing upon opening Classification: Applications Product: NeoChat Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: rstreete...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (22.09) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.2-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: I went to open Neochat and it crahsed, I tried opening it via terminal and it crashed again. Here is the output of that if it differs from anything sent with the backtrace : KCrash: Application 'neochat' crashing... KCrash: Attempting to start /usr/libexec/drkonqi QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... [1]+ Stopped neochat The reporter is unsure if this crash is reproducible. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7fcea8cdee17 in QtPrivate::qustrchr(QStringView, unsigned short) () from /lib64/libQt5Core.so.5 #5 0x7fcea8ce9caa in QtPrivate::findString(QStringView, long long, QStringView, Qt::CaseSensitivity) () from /lib64/libQt5Core.so.5 #6 0x7fcea8cefb8b in ?? () from /lib64/libQt5Core.so.5 #7 0x7fcea8cefcb1 in QString::splitRef(QString const&, QFlags, Qt::CaseSensitivity) const () from /lib64/libQt5Core.so.5 #8 0x7fcea8cf1846 in QString::section(QString const&, int, int, QFlags) const () from /lib64/libQt5Core.so.5 #9 0x7fceaa6a51d6 in Quotient::AccountSettings::userId() const () from /lib64/libQuotient.so.0.6 #10 0x55c1d6299c56 in ?? () #11 0x55c1d629b7a2 in ?? () #12 0x7fcea8e7b05d in ?? () from /lib64/libQt5Core.so.5 #13 0x7fceaa581c3f in QKeychain::Job::finished(QKeychain::Job*) () from /lib64/libqt5keychain.so.1 #14 0x7fceaa57afdc in QKeychain::Job::emitFinished() () from /lib64/libqt5keychain.so.1 #15 0x7fceaa57ceb3 in QKeychain::ReadPasswordJobPrivate::kwalletEntryTypeFinished(QDBusPendingCallWatcher*) () from /lib64/libqt5keychain.so.1 #16 0x7fcea8e7b2dc in ?? () from /lib64/libQt5Core.so.5 #17 0x7fcea919b1ef in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib64/libQt5DBus.so.5 #18 0x7fcea8e6f9d0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fcea9aa43fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fcea8e44178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7fcea8e47111 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7fcea8e9c003 in ?? () from /lib64/libQt5Core.so.5 #23 0x7fcea81dfa50 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7fcea81dfe08 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7fcea81dfe9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7fcea8e9b806 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fcea8e42beb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7fcea8e4ad56 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x55c1d622feb8 in main () [Inferior 1 (process 13639) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 461412] New: xdg-desktop-portal-kde core dumped with stacktrace
https://bugs.kde.org/show_bug.cgi?id=461412 Bug ID: 461412 Summary: xdg-desktop-portal-kde core dumped with stacktrace Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.26.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: elles.rob...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Hi, in the journal of my system after login i see xdg-desktop-portal-kde crashing with the following core dumped message: systemd-coredump[1383]: [🡕] Process 1380 (.xdg-desktop-po) of user 175 dumped core. Module linux-vdso.so.1 with build-id 4ab72416a7064edbf8e3dbacd4521e7bbb37ed32 Module libuuid.so.1 with build-id 3c7a9fbf1c591d6cfa06eb5c5d924784ae3c4531 Module libxcb-util.so.1 without build-id. Module libxkbcommon-x11.so.0 without build-id. Module libICE.so.6 without build-id. Module libSM.so.6 without build-id. Module libxcb-xinput.so.0 without build-id. Module libxcb-xkb.so.1 without build-id. Module libxcb-xinerama.so.0 without build-id. Module libxcb-xfixes.so.0 without build-id. Module libxcb-sync.so.1 without build-id. Module libxcb-shape.so.0 without build-id. Module libxcb-render.so.0 without build-id. Module libxcb-render-util.so.0 without build-id. Module libxcb-randr.so.0 without build-id. Module libxcb-shm.so.0 without build-id. Module libxcb-image.so.0 without build-id. Module libxcb-icccm.so.4 without build-id. Module libX11-xcb.so.1 without build-id. Module libQt5XcbQpa.so.5 without build-id. Module libqxcb.so without build-id. Module libmvec.so.1 with build-id 974b3cce29a9ebbe8f11c9921d15ee3fce9eaa86 Module libogg.so.0 without build-id. Module libopus.so.0 without build-id. Module libvorbisenc.so.2 without build-id. Module libvorbis.so.0 without build-id. Module libFLAC.so.12 without build-id. Module libsndfile.so.1 without build-id. Module libcap.so.2 without build-id. Module libexpat.so.1 without build-id. Module libpulsecommon-16.1.so without build-id. Module libpcre2-8.so.0 without build-id. Module libsystemd.so.0 without build-id. Module libresolv.so.2 with build-id 05d515a2629ecec61725d74185444eb226ef6f39 Module libkeyutils.so.1 without build-id. Module libkrb5support.so.0 without build-id. Module libcom_err.so.3 without build-id. Module libk5crypto.so.3 without build-id. Module libkrb5.so.3 without build-id. Module libblkid.so.1 with build-id e3bdf2fc6bd792fb6cf792b181384f35ca893079 Module libgraphite2.so.3 without build-id. Module libXdmcp.so.6 without build-id. Module libXau.so.6 without build-id. Module liblzma.so.5 without build-id. Module libbz2.so.1 without build-id.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 robert changed: What|Removed |Added CC||robert.segr...@free.de --- Comment #20 from robert --- I would also like to report I have this same bug after performing this update. Kmail was removed and when trying to reinstall it I am met with this error: sudo pkcon install kmail Fatal error: The following packages have unmet dependencies: libkf5messageviewer5: Hängt ab von: libqca-qt5-2 (>= 2.3.5) but 2.3.4-1build1 is to be installed I tried: sudo apt -f install libkf5messageviewer5 Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libkf5messageviewer5:amd64 < none -> 4:22.12.1-0xneon+22.04+jammy+release+build24 @un puN Ib > Broken libkf5messageviewer5:amd64 Hängt ab von on libqca-qt5-2:amd64 < 2.3.4-1build1 @ii K > (>= 2.3.5) Considering libqca-qt5-2:amd64 25 as a solution to libkf5messageviewer5:amd64 Done Sorry for the mix of German and English, I have both language pack installed, I'm not sure why it is displaying like this. I can use the web login of my mail in the mean time, does anyone know if libqca-qt5-2 version 2.3.5 is likely to be shipped any time soon? Thanks, -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #22 from robert --- Great, fixed it. Thanks for the quick response! (In reply to Jonathan Riddell from comment #21) > Likely due to the qca package being held back by a pin. > > Put this file into /etc/apt/preferences.d and rm /etc/apt/preferences.d/98* > https://invent.kde.org/neon/neon/settings/-/raw/Neon/unstable/etc/apt/ > preferences.d/99-jammy-overrides?inline=false > > Alas I've no idea what that didn't get updated automatically as part of > neon-settings-2 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 424518] Elisa crashed when scrolling Album list
https://bugs.kde.org/show_bug.cgi?id=424518 Robert changed: What|Removed |Added CC||rstreete...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429786] New: System Settings Crash On App Close
https://bugs.kde.org/show_bug.cgi?id=429786 Bug ID: 429786 Summary: System Settings Crash On App Close Product: systemsettings Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: --- Application: systemsettings5 (5.20.2) Qt Version: 5.15.1 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-54-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I had closed the application and it stated the app had crshed but I had only closed the app. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 83874] [New LWP 83877] [New LWP 83878] [New LWP 83879] [New LWP 83880] [New LWP 83885] [New LWP 83886] [New LWP 83888] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe859cb1aff in __GI___poll (fds=0x7ffde2025ee8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fe85594f880 (LWP 83872))] Thread 9 (Thread 0x7fe82c809700 (LWP 83888)): #0 0x7fe859cb1aff in __GI___poll (fds=0x7fe818004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe857db31ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe857db32e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe85a27b24b in QEventDispatcherGlib::processEvents (this=0x7fe818000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe85a21f43b in QEventLoop::exec (this=this@entry=0x7fe82c808d00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fe85a03b982 in QThread::exec (this=this@entry=0x55b144638d60) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fe859242d69 in QQmlThreadPrivate::run (this=0x55b144638d60) at qml/ftw/qqmlthread.cpp:155 #7 0x7fe85a03cb1c in QThreadPrivate::start (arg=0x55b144638d60) at thread/qthread_unix.cpp:329 #8 0x7fe8586c5609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fe859cbe293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fe82dc89700 (LWP 83886)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:56 #1 0x7fe859cb1ae7 in __GI___poll (fds=0x7fe814004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7fe857db31ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe857db32e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe85a27b24b in QEventDispatcherGlib::processEvents (this=0x7fe814000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe85a21f43b in QEventLoop::exec (this=this@entry=0x7fe82dc88d00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7fe85a03b982 in QThread::exec (this=this@entry=0x55b1447562b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7fe859242d69 in QQmlThreadPrivate::run (this=0x55b1447562b0) at qml/ftw/qqmlthread.cpp:155 #8 0x7fe85a03cb1c in QThreadPrivate::start (arg=0x55b1447562b0) at thread/qthread_unix.cpp:329 #9 0x7fe8586c5609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe859cbe293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fe82f7fe700 (LWP 83885)): #0 0x7fe859cb1aff in __GI___poll (fds=0x7fe820005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe857db31ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe857db32e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe85a27b24b in QEventDispatcherGlib::processEvents (this=0x7fe82b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe85a21f43b in QEventLoop::exec (this=this@entry=0x7fe82f7fdd00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fe85a03b982 in QThread::exec (this=this@entry=0x55b144527d20) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fe859242d69 in QQmlThreadPrivate::run (this=0x55b144527d20) at qml/ftw/qqmlthread.cpp:155 #7 0x7fe85a03cb1c in QThreadPrivate::start (arg=0x55b144527d20) at thread/qthread_unix.cpp:329 #8 0x7fe8586c5609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fe859cbe293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fe8467fc700 (LWP 83880)): #0 futex_wait_cancelable (priva
[krunner] [Bug 363195] Error reported when attempting to open a mail message from krunner
https://bugs.kde.org/show_bug.cgi?id=363195 --- Comment #3 from Robert --- I would check up on this except I no longer use the same computer I used 4 years ago. Not even sure it still runs. I don't have the setup required to provide more information about this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462198] New: kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid
https://bugs.kde.org/show_bug.cgi?id=462198 Bug ID: 462198 Summary: kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid Classification: Plasma Product: kwin Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: robertdeja...@tutanota.com Target Milestone: --- My Wayland session crashes when I close the laptop lid, but only after I have unplugged my external monitor, connected through a USB-C dock. This happens every time I try. Sometimes it also crashes when I plug the monitor back in. *** Will update when I can *** STEPS TO REPRODUCE 1. Plug in USB-C dock with external monitor in HDMI port (or boot up with the external monitor connected) 2. Unplug the USB-C dock 3. Close the lid (or have it closed while unplugging the dock) 4. Open the lid, if you're fast enough you'll still see the terminal before kwin_wayland restarts itself 4a. Note, the session itself is still live, so no need to log in again using SDDM. 4b. If I have the lid closed while unplugging the screen, the session is locked like it is supposed to. In the other scenario, it isn't. OBSERVED RESULT kwin_wayland has crashed, taking all applications running on top with it. EXPECTED RESULT Locked session, and all my application are still running SOFTWARE/OS VERSIONS Arch Linux (Linux 6.0.9) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION This could be a duplicate of https://bugs.kde.org/show_bug.cgi?id=390306, I'm not sure -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462198] kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid
https://bugs.kde.org/show_bug.cgi?id=462198 --- Comment #1 from Robert --- I'm afraid I'm going to need some help with the backtrace. The instructions on the community page cover crashing applications. Can someone tell me what to run? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 493151] New: IP address setting for PTP/IP camera is mishandled
https://bugs.kde.org/show_bug.cgi?id=493151
Bug ID: 493151
Summary: IP address setting for PTP/IP camera is mishandled
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Setup-Cameras
Assignee: digikam-bugs-n...@kde.org
Reporter: grzy...@gmail.com
Target Milestone: ---
SUMMARY
Thank you for creating and maintaning digiKam!
I had troubles configuring PTP/IP camera in digiKam. I was able to make it work
when the camera was joined to my home Wi-Fi (192.168.1.241) but if I tethered
the same camera directly to my laptop (10.42.0.212) it won't work.
While investigating I have realised that digiKam is attempting to connect to a
wrong IP address (8.34.0.212).
It would appear that digiKam saves the content of GUI controls for the IP
address verbatim (including leading zeros).
When the resulting _string_ ("010.042.000.212") is then passed to the gphoto2
library (which is written in C) any individual octet starting with zero will be
(as expected) treated as on octal number - not a decimal.
I was able to workaround this issue by removing the leading zeros from the file
`~/.local/share/digikam/cameras.xml`.
STEPS TO REPRODUCE
1. Add and configure PTP/IP camera, enter an IP address where one or more
octets are in the range 8 to 99 decimal.
2. Attempt to connect to the camera (Camera->Import->TCP/IP Camera) while using
the underlying OS to observe an actual address begin connected to (for example
using `ss` utility)
OBSERVED RESULT
The (innocent) gphoto2 library attempts to connect to wrong IP address (where
each octet of the configured IP address which was greater than 7 or less than
100 is not the same as what was entered on the configuration screen. For
example configuring an IP address 10.42.0.212 results in an attempt to connect
to incorrect host at 8.34.0.212
EXPECTED RESULT
digiKam should attempt to connect to the PTP/IP camera at the IP address
configured (specified) by the user.
SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: n/a
KDE Plasma Version: n/a
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.2 (built against 6.7.2)
Build date: 12/07/2024 16:16 (target: RelWithDebInfo)
Revision: 5e59e2643c4e55ca52b6de00ef58f64fee225025
Branch: HEAD
ADDITIONAL INFORMATION
digikam version 8.4.0
OpenCV Configuration:
Threads features:
Parallel framework: pthreads
Number of Threads: 8
OpenCL availability: No
Hardware features:
SSSE3: Yes
SSE4.2: Yes
SSE4.1: Yes
SSE3: Yes
SSE2: Yes
SSE: Yes
POPCNT: Yes
MMX: Yes
FP16: Yes
FMA3: Yes
AVX2: Yes
AVX: Yes
Manifests:
O2 Snapshoot 2022-02-10:
o2: 99902cc37e083a8311c1f8eee918e93c93cbc937
LIBRAW Snapshoot 2024-07-11:
libraw: 47c7a239496cd17eb9e01aa0c8e7a8a98950fd4c
LIBLQR Snapshoot 2023-11-06:
liblqr: 7b88c05cec2f0e60125e1cfcad18c79721a2b27c
LENSFUN Snapshoot 2024-07-12:
lensfun: 112da18baa0e53d9755abe5beb7fbb3812c8a37b
KF6 Snapshot 2024-06-22:
EXIV2 Snapshoot 2024-07-12:
exiv2: 04207b9c39bf7b3b1a7144f7ed4e4f16b4f29ef6
Libraries:
XMP SDK: 7.0
Qt WebEngine version: 6.7.2
Qt SQL drivers: QSQLITE QMARIADB QMYSQL
Qt Framework: 6.7.2
Libx265: 3.5+1-f0c1022b6
LibTIFF: 4.3.0
LibRaw: 0.22.0
LibPNG: 1.6.37
LibPGF: 7.21.07
LibOpenCV: 4.10.0
LibLCMS: 2120
LibJPEG: 80
LibJasper: 4.2.4
LibHEIF: 1.17.6
LibGphoto2: 2.5.27
LibCImg: 130
LibAVUtil: 58.29.100
LibAVFormat: 60.16.100
LibAVCodec: 60.31.102
LensFun: 0.3.99-0
KDE Framework: 6.2.0
ImageMagick codecs: 7.1.1
Geolocation support: Yes
Exiv2: 0.28.2
ExifTool: 12.88
Eigen: 3.4.0
DNG SDK: 1.7.1
FFmpeg Configuration:
Video Encoders:
vc2: SMPTE VC-2
prores_ks: Apple ProRes (iCodec Pro)
prores_aw: Apple ProRes
ljpeg: Lossless JPEG
libxvid: libxvidcore MPEG-4 part 2
libx265: libx265 H.265 / HEVC
libx264rgb: libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB
libx264: libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
libtheora: libtheora Theora
a64multi5: Multicolor charset for Commodore 64, extended with 5th color
(colram)
a64multi: Multicolor charset for Commodore 64
Video Decoders:
zmbv: Zip Motion Blocks Video
zlib: LCL (LossLess Codec Library) ZLIB
zerocodec: ZeroCodec Lossless Video
yuv4: Uncompressed packed 4:2:0
yop: Psygnosis YOP Video
ylc: YUY2 Lossless Codec
y41p: Uncompressed YUV 4:1:1 12-bit
xwd: XWD (X Window Dump) image
xpm: XPM (X PixMap) image
xl: Miro VideoXL
xface: X-face image
xbm: XBM (X BitMap) image
xbin: eXtended BINary text
xan_wc4: Wing Commander IV / Xxan
xan_wc3: Wing Commander III / Xan
wrapped_avframe: AVPacket to AVFrame passthrough
wnv1: Winnov WNV1
wmv3image: Windows Media Video 9 Image
wmv3: Windows Media Video 9
wmv2: Windows Media Video 8
wmv1: Windows Media Video 7
webp: WebP image
wcmv: WinCAM Motion Video
wbmp: WBMP (Wireless Application Protocol Bitmap) image
vq
[kde] [Bug 492612] New: My Samsung Android phone does not stay connected to my PC
https://bugs.kde.org/show_bug.cgi?id=492612 Bug ID: 492612 Summary: My Samsung Android phone does not stay connected to my PC Classification: I don't know Product: kde Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rba...@hotmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY My Samsung phone does not stay connected to my PC Win10Pro STEPS TO REPRODUCE 1. Connect from phone 2. Accept connection on PC 3. It connects but doesn't stay connected very long OBSERVED RESULT The phone doesn't stay connected EXPECTED RESULT The phone should stay connected SOFTWARE/OS VERSIONS Windows: Win10Pro macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492612] My Samsung Android phone does not stay connected to my PC
https://bugs.kde.org/show_bug.cgi?id=492612 Robert changed: What|Removed |Added CC||rba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 --- Comment #9 from Robert --- Awesome, thanks for fixing it, much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 --- Comment #10 from Robert --- I'm just following up on this bug and have noticed that despite having 6.1.3 and the latest updates, there is still a pronounced stutter that occurs consistently when notifications are received. I'm not sure if this is now direct scanout being interrupted or another problem with the code. -- You are receiving this mail because: You are watching all bug changes.
