[plasmashell] [Bug 494804] With Qt 6.8, can't log in using external screen when using the Breeze SDDM theme
https://bugs.kde.org/show_bug.cgi?id=494804 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494161] Applications always open on the wrong screen!
https://bugs.kde.org/show_bug.cgi?id=494161 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #2 from S. Bryant --- The "Active screen follows mouse" setting and behaviour are currently missing. It's certainly very counter intuitive to have an application appear on a different screen than the launcher that was used to start it. I'm guessing this is a regression rather than a bug - that it simply hasn't been implemented in 6.x yet. I would suggest changing the title. The definition of "wrong screen" is subjective. The active screen follows the active window but not the mouse. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488749] Screen Recorder error in PipeWire remote in all screen recorders, include obs studio: black screen!
https://bugs.kde.org/show_bug.cgi?id=488749
Malte S. Stretz changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #15 from Malte S. Stretz ---
Closing this since Neon 24.04.1 is available and seems to have fixed this
issue.
I don't know if it was necessary but I removed the pipewire PPA before
upgrading using these commands, followed by a reboot:
sudo true && echo 'DPkg::Options { "--force-overwrite"; };' | sudo tee
/etc/apt/apt.conf.d/99-dpkg-force-overwrite.conf
sudo ppa-purge pipewire-debian/pipewire-upstream
sudo rm /etc/apt/apt.conf.d/99-dpkg-force-overwrite.conf
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 483068] must enter wireless password upon login when systemd boot is disabled
https://bugs.kde.org/show_bug.cgi?id=483068 --- Comment #4 from S. Christian Collins --- This still happens for me in KDE neon 6.2 (Ubuntu 24.04 base), with Plasma 6.2.1, Frameworks 6.7.0, and Qt 6.7.2. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 451171] "Built-In Audio" pop-up when logging in after fresh boot
https://bugs.kde.org/show_bug.cgi?id=451171 S changed: What|Removed |Added CC||wvzoaqcebocqx...@stefan.wf --- Comment #6 from S --- (In reply to Harald Sitter from comment #4) > Is this still a problem? Yes, this issue can be reproduced on different systems running Plasma 6.0 and 6.1 with pipewire (some display the volume level, others the output device) Please let me know if additional information is required. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494755] Wifi unuseable after resume
https://bugs.kde.org/show_bug.cgi?id=494755 David S changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 494529] On X11, screen freeze after waking up screen
https://bugs.kde.org/show_bug.cgi?id=494529 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #6 from S. Umar --- This happens on my screen with no locking enabled. There is a freeze for about 20 sec before things start functioning again. This was not the case in the past (a few months ago). I am on Fedora 40 with daily updates and using Plasma X11. Kernel: 6.11.4 KDE Plasma Version: 6.2.1 (and 6.2.1.1 for kwin and workspace) KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494577] Monitor Brightness Resets to Previous Dimmed Value After Screen Wakeup on Fedora KDE
https://bugs.kde.org/show_bug.cgi?id=494577 --- Comment #5 from S. Umar --- By external monitor you mean you are using a laptop with an external monitor? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494577] Monitor Brightness Resets to Previous Dimmed Value After Screen Wakeup on Fedora KDE
https://bugs.kde.org/show_bug.cgi?id=494577 --- Comment #3 from S. Umar --- In my case it is not happening on my home desktop (same configuration) but a single monitor. Is this true for everyone? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494577] Monitor Brightness Resets to Previous Dimmed Value After Screen Wakeup on Fedora KDE
https://bugs.kde.org/show_bug.cgi?id=494577 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #1 from S. Umar --- I can confirm this on the same setting (Fedora 40 with all updates) but DELL monitors. One has to set brightness every time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 S. Umar changed: What|Removed |Added CC|u...@compsci.cas.vanderbilt | |.edu| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 S. Umar changed: What|Removed |Added CC|u...@compsci.cas.vanderbilt | |.edu| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494611] Poor performance with Nvidia + nightlight
https://bugs.kde.org/show_bug.cgi?id=494611 --- Comment #8 from S. Bryant --- (In reply to medin from comment #4) > The culprit is Night Light, it causes the slowness when it's enabled and > only during its time of activation. > > I disabled it then rebooted and Wayland became usable again. Not in my case - wasn't enabled. I enabled it, and while the colours changed, the performance was the same. :-( Anyway, I see there's already a commit in. Looking forward to trying the new version. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 494866] New: duplicate "preferences.d" folder after OS install
https://bugs.kde.org/show_bug.cgi?id=494866 Bug ID: 494866 Summary: duplicate "preferences.d" folder after OS install Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY After installing the latest neon User Edition (using "neon-user-20241010-1519.iso"), there is a duplicate "preferences.d" folder inside of "/etc/apt/preferences.d", containing copies of the same files that neon adds to "/etc/apt/preferences.d". I have observed this behavior in two separate VirtualBox installs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494652] Plasmashell crashes when i eject dvd drive
https://bugs.kde.org/show_bug.cgi?id=494652 David S changed: What|Removed |Added CC||too.late.ag...@outlook.com --- Comment #2 from David S --- Same here. Operating System: openSUSE Tumbleweed 20241013 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.3 Kernel Version: 6.11.2-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490687] On X11 with multiple screens, desktop widget sizes change after login
https://bugs.kde.org/show_bug.cgi?id=490687 David S changed: What|Removed |Added CC||d...@digitalmonkey.org --- Comment #10 from David S --- I have this same issue and found this report after searching. Im running OpenSuse except with Wayland, not X11. Widgets such as CPU Usage, Weather, Notes etc grow in size and move after reboot. Gets worse over time. Happens on both my desktop and laptop. Would be more than willing to provide more details where needed -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494755] Wifi unuseable after resume
https://bugs.kde.org/show_bug.cgi?id=494755 --- Comment #1 from David S --- Some more details on this. It looks like it only happens if I use S3 sleep state vs Suspend-To-Idle. This is a bios setting I can adjust on the laptop. I have used S3 in the past as I found it better with battery life. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494755] Wifi unuseable after resume
https://bugs.kde.org/show_bug.cgi?id=494755 David S changed: What|Removed |Added CC||d...@digitalmonkey.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494755] New: Wifi unuseable after resume
https://bugs.kde.org/show_bug.cgi?id=494755 Bug ID: 494755 Summary: Wifi unuseable after resume Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: d...@digitalmonkey.org Target Milestone: --- SUMMARY Wifi Connection is not functional when resuming the first item from suspend. The work-around seems to be suspend again and quickly resume. This is never an issue from boot, only after suspend. Airplane mode or shutting off wifi does not fix the issue, only a reboot or suspending and resuming does. GUI freezes on the "Configuring Interface" step. I am using Intel Alder Lake Wifi System Specs: Lenovo T16 Laptop Core i7 1260P OpenSuse Tumbleweed running KDE under Wayland STEPS TO REPRODUCE 1. Log into KDE and allow the system to sleep, manually suspend, close the laptop lid etc 2. Resume the machine 3. Wifi will not conenct, wired connections are fine OBSERVED RESULT No wifi connections function after resuming from sleep/suspend EXPECTED RESULT Wifi reconnects after system resume SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumbleweed KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.3 ADDITIONAL INFORMATION I believe this started happening about 2 weeks ago after one of the kernel updates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494382] KDE 6.2 with lag when moving windows with ICC profiles
https://bugs.kde.org/show_bug.cgi?id=494382 --- Comment #22 from David S --- *** Bug 494496 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494496] Display lag when moving windows in Wayland
https://bugs.kde.org/show_bug.cgi?id=494496 David S changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from David S --- *** This bug has been marked as a duplicate of bug 494382 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494611] Performance and speed severely degraded after upgrading to Plasma 6.2
https://bugs.kde.org/show_bug.cgi?id=494611 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #1 from S. Bryant --- I have a i7-6700K (4GHz), 32GB RAM and an Nvidia 4060, and I'm seeing the exact same problems with Plasma 6.2 (6.1 was fine for me too). The problem doesn't look to be related to any specific hardware. My system has openSUSE Slowroll installed, using the precompiled RPMs. kwin_wayland varies between 130% and 250% CPU; with 6.1 it was a fraction of this. I'll note that VLC can't display video with 6.2. Video playback in the browser (both FF & Chrome) is not at all smooth either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494496] Display lag when moving windows in Wayland
https://bugs.kde.org/show_bug.cgi?id=494496 --- Comment #2 from David S --- (In reply to duha.bugs from comment #1) > This might be https://bugs.kde.org/show_bug.cgi?id=494382 I reviewed 494382 and its very likely this is the same issue. Mine seems related to night light. What made this so confusing is it would be fine in the morning but NOT the evening! Right now its late morning and Im experiencing no issue, but night light hasnt activated yet. I turned it on manually and instant lag! For me at least, if I disable night light the issue is mostly if not totally fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494382] KDE 6.2 with lag when moving windows with ICC profiles
https://bugs.kde.org/show_bug.cgi?id=494382 David S changed: What|Removed |Added CC||d...@digitalmonkey.org --- Comment #18 from David S --- I just reported a similar issue (see below link) and was directed to this thread https://bugs.kde.org/show_bug.cgi?id=494496 For me, I can confirm "Night Light" causes the issue. This is why ever morning I would think "Oh good, looks like the devs fixed it", then later in the day, massive lag. Just confirmed activating Night Light causes my issue and without it, its mostly if not totally ok. Thanks for everyone's work with diag! Interesting issue -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494496] Display lag when moving windows in Wayland
https://bugs.kde.org/show_bug.cgi?id=494496 David S changed: What|Removed |Added CC||d...@digitalmonkey.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494496] New: Display lag when moving windows in Wayland
https://bugs.kde.org/show_bug.cgi?id=494496 Bug ID: 494496 Summary: Display lag when moving windows in Wayland Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: d...@digitalmonkey.org Target Milestone: --- Created attachment 174661 --> https://bugs.kde.org/attachment.cgi?id=174661&action=edit Video showing issue *** 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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY In Wayland only there is massive display lag moving windows around. This is true on a single or multiple monitors. STEPS TO REPRODUCE 1. Install all available updates after 10/07/24 2. Log in using Wayland (no issues in x11) 3. Move windows around the screen OBSERVED RESULT Very noticeable lag moving windows to to point they tear in pieces and jump around EXPECTED RESULT Smooth, buttery motion SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Operating System: openSUSE Tumbleweed 20241009 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.11.2-1-default (64-bit) Graphics Platform: Wayland Processors: 28 × Intel® Core™ i7-14700 Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION See attached video of issue. This goes away if I use X11 or if I revert to my snapshot from 10/7/24 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470266] kwin_wayland crash in QOpenGLContext::shareGroup
https://bugs.kde.org/show_bug.cgi?id=470266 Colin S changed: What|Removed |Added CC||bugs.kde@zetafleet.com --- Comment #7 from Colin S --- I can confirm this crash, or something very similar, still exists in at least version 5.27.11. The backtrace I saw here looks the same as the one David Gow reported, and in my case the crash was triggered when an application with an always-on-top window rule popped up shortly after launching a different fullscreen application in Wine (via Xwayland). This caused the fullscreen application window to minimise, and then after dismissing the pop-up window and trying to Alt-Tab back into the fullscreen application, KWin crashed. After the crash, KWin restarted and Firefox had enough time to pop a “Firefox crashed, do you want to report it?” window before KWin logged “No provider of eglDestroyImageKHR found.” and crashed again in `KWin::EglDmabuf::~EglDmabuf()` (via `KWin::Compositor::stop()`, via a `KWin::Workspace::slotReconfigure()` signal). This second crash happened twice in a row. (This seems like it could be bug #470980 which looks like it was maybe not backported to 5.27.) After finally recovering, autostart applications and some KDE services like kwallet did not restart on their own. Debian testing KWin 5.27.11-2 Qt5 5.15.13+dfsg-4 AMD Radeon 780M (radeonsi, gfx1103_r1, LLVM 18.1.8, DRM 3.57, 6.9.12-amd64) Mesa 24.2.2-1 Best, -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 494186] New: Discovery crash when updating
https://bugs.kde.org/show_bug.cgi?id=494186 Bug ID: 494186 Summary: Discovery crash when updating Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: tandata...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-26-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Notification on securityy update, when clicked open discovery update package page. Its shows progress bar couple seconds then crash. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault PID: 8214 (plasma-discover) UID: 1000 (dsa) GID: 1000 (dsa) Signal: 11 (SEGV) Timestamp: Sun 2024-10-06 05:39:11 WIB (35s ago) Command Line: /usr/bin/plasma-discover Executable: /usr/bin/plasma-discover Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fplasma\x2ddiscover-a6d2dbebab474cde8f83d2af3b7c2c68.scope Unit: user@1000.service User Unit: app-\x2fusr\x2fbin\x2fplasma\x2ddiscover-a6d2dbebab474cde8f83d2af3b7c2c68.scope Slice: user-1000.slice Owner UID: 1000 (dsa) Boot ID: 407b342519ac46028011654dbacce5c8 Machine ID: 1f556eb70c5c4cf6b9988f8ac7286f27 Hostname: dell3410 Storage: /var/lib/systemd/coredump/core.plasma-discover.1000.407b342519ac46028011654dbacce5c8.8214.172816795100.zst (present) Size on Disk: 32.0M Message: Process 8214 (plasma-discover) of user 1000 dumped core. Module libnss_resolve.so.2 from deb systemd-252.30-1~deb12u2.amd64 Module libnss_myhostname.so.2 from deb systemd-252.30-1~deb12u2.amd64 Module libsystemd.so.0 from deb systemd-252.30-1~deb12u2.amd64 Module libudev.so.1 from deb systemd-252.30-1~deb12u2.amd64 Module libnxegl.so without build-id. Stack trace of thread 8214: #0 0x7fb2f02a9e3c n/a (libc.so.6 + 0x8ae3c) #1 0x7fb2f025afb2 raise (libc.so.6 + 0x3bfb2) #2 0x7fb2f2a2b83d _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x583d) #3 0x7fb2f025b050 n/a (libc.so.6 + 0x3c050) #4 0x7fb2f06e8a7d n/a (libQt5Core.so.5 + 0x2e8a7d) #5 0x7fb2f2ab43b2 _ZN13ResultsStream14resourcesFoundERK7QVectorIP16AbstractResourceE (libDiscoverCommon.so + 0x2a3b2) #6 0x7fb2ba7c44d0 n/a (packagekit-backend.so + 0x264d0) #7 0x7fb2ba7be588 n/a (packagekit-backend.so + 0x20588) #8 0x7fb2f06dd730 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd730) #9 0x7fb2f2162fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #10 0x7fb2f06b1738 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1738) #11 0x7fb2f06b46c1 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b46c1) #12 0x7fb2f070a193 n/a (libQt5Core.so.5 + 0x30a193) #13 0x7fb2eef1e7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #14 0x7fb2eef1ea38 n/a (libglib-2.0.so.0 + 0x54a38) #15 0x7fb2eef1eacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #16 0x7fb2f0709876 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309876) #17 0x7fb2f06b01bb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b01bb) #18 0x7fb2f06b8316 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8316) #19 0x55a74d1102a7 n/a (plasma-discover + 0x182a7) #20 0x7fb2f024624a n/a (libc.so.6 + 0x2724a) #21 0x7fb2f0246305 __libc_start_main (libc.so.6 + 0x27305) #22 0x55a74d110811 n/a (plasma-discover + 0x18811) Stack trace of thread 8216: #0 0x7fb2f031b15f __poll (libc.so.6 + 0xfc15f) #1 0x7fb2eaf2fcd6 n/a (libQt5WaylandClient.so.5 + 0x7acd6) #2 0x7fb2f04cbd83 n/a (libQt5Core.so.5 + 0xcbd83) #3 0x7fb2f02a8144 n/a (libc.so.6 + 0x89144) #4 0x7fb2f03287dc n/a (libc.so.6 + 0x1097dc)
[skrooge] [Bug 494079] improve confusing menu item "Open transactions modified by this transaction..."
https://bugs.kde.org/show_bug.cgi?id=494079 S Page changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/offi ||ce/skrooge/-/commit/90a1046 ||63514ccbd10667f3e2c4f827f41 ||d01fb8 Resolution|--- |FIXED --- Comment #3 from S Page --- Git commit 90a104663514ccbd10667f3e2c4f827f41d01fb8 by S Page. Committed on 04/10/2024 at 03:10. Pushed by smankowski into branch 'master'. Improve confusing menu item text Change "Open transactions modified by this transaction…" -> this action M +1-1plugins/skrooge/skrooge_operation/skgoperationplugin.cpp https://invent.kde.org/office/skrooge/-/commit/90a104663514ccbd10667f3e2c4f827f41d01fb8 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 493879] Plasma fails to turn off external monitor
https://bugs.kde.org/show_bug.cgi?id=493879 --- Comment #2 from S. Umar --- On Fedora I had the same problem. They just build kidletime with X11 support to detect idle time. They just built a package with this support and it solved the problem. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 493879] Plasma fails to turn off external monitor
https://bugs.kde.org/show_bug.cgi?id=493879 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #1 from S. Umar --- I had the same issue on Fedora 40 (others as well). It seems like the problem was that kg6-kidletime did not compile the X11 dependency in. They now included and created a new X11 package. Installing that solved my problem, -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 493546] Screen Never Turns Off After Inactivity
https://bugs.kde.org/show_bug.cgi?id=493546 --- Comment #28 from S. Umar --- On my laptop, clicking on battery applet shows "Sleep and screen locking after inactivity automatic", manually block button is off. Naturally, on the desktops there is no battery applet. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 493546] Screen Never Turns Off After Inactivity
https://bugs.kde.org/show_bug.cgi?id=493546 --- Comment #21 from S. Umar --- I don't think this has to do with rearrangement of settings. I created a new user and experienced the same issue. I am suproised that some people are not experiencing it. There are patches in powerdevil upstream that deals with dbus and systemd. They may nor be related but this needs to be addressed. For the time being I set the power button to turn off screen and doing that. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 493546] Screen Never Turns Off After Inactivity
https://bugs.kde.org/show_bug.cgi?id=493546 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #13 from S. Umar --- I can confirm this on six workstations and my laptop, all on Fedora 40, running plasma-desktop 6.1.5, framework 6.6.0. There are some patches I see in powerdevil but not yet applied downstream. My power settings are same as the one reported here. I saw that once in a while after a reboot it works on some workstations (all have same setup and graphics card). If I logout to sddm then it works fine. Perhaps a race condition. I saw these that may be related: https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/commit/8277adb7cd89293fd4d32407eee1596ffbf6acce https://invent.kde.org/plasma/powerdevil/-/merge_requests/425 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 481778] Text in lines is cut in half, only lower half of the line text is visible when font size less than 14
https://bugs.kde.org/show_bug.cgi?id=481778 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 492704] Tabs always hidden
https://bugs.kde.org/show_bug.cgi?id=492704 Malte S. Stretz changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Malte S. Stretz --- I just discovered that I had the "Vertical Tabs" extension enabled but the sidebar was hidden. One could argue that the sidebar should appear once a new tab is opened but I guess this works as designed. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 492704] New: Tabs always hidden
https://bugs.kde.org/show_bug.cgi?id=492704 Bug ID: 492704 Summary: Tabs always hidden Classification: Applications Product: Falkon Version: 24.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m...@apache.org Target Milestone: --- SUMMARY Since while (I think since the Qt6 port) Falkon does not show a tab bar at all anymore. It doesn't matter what value the "Hide tabs when there is only one tab" option is set to. STEPS TO REPRODUCE 1. Open Falkon 2. Go to eg. www.kde.org 3. Press Ctrl+T OBSERVED RESULT No tab bar was visible when the app was started and no tab bar appeared when a new tab was opened EXPECTED RESULT Depending on the "hide tabs" option the tabs should have been visible from the start or not but as soon as a new tab is opened a tab bar should definitely be displayed. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 19.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 492680] can't copy calculation result as expected
https://bugs.kde.org/show_bug.cgi?id=492680 --- Comment #4 from S. Christian Collins --- Created attachment 173370 --> https://bugs.kde.org/attachment.cgi?id=173370&action=edit video showing the bug Hmm, I thought I had attached this to the original bug report. Sorry about that! -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 492680] can't copy calculation result as expected
https://bugs.kde.org/show_bug.cgi?id=492680 --- Comment #2 from S. Christian Collins --- (In reply to Gabriel Barrantes from comment #1) > > 2. Highlighting the contents of the formula view, right-click → Copy appears > > to do nothing. > > This should be working fine, can you double check it?, I got the copied > value as expected. Well, you can see what happens to me in the video I attached to the bug report. It just doesn't copy anything to the clipboard when I do it. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 492680] New: can't copy calculation result as expected
https://bugs.kde.org/show_bug.cgi?id=492680 Bug ID: 492680 Summary: can't copy calculation result as expected Classification: Applications Product: kcalc Version: 24.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: s_chriscoll...@hotmail.com CC: gabriel.barrantes@outlook.com Target Milestone: --- SUMMARY Disclaimer: I don't know the correct terminology for the calculator's display area, since I can't reference the manual due to bug #492142. So, I will refer to the upper, small number display as the "formula view", and the lower, larger number display as the "result view". --- After running a calculation in KCalc and hitting Enter, the number disappears from the result display and only appears in the formula view. Ctrl+C results in an empty clipboard, and attempting to copy the contents of the formula view via right click → Copy fails also. This is a huge usability fail, IMO, as many people are used to hitting the Enter key after a calculation (especially us number pad users). A common workflow is: 1. Make a calculation in KCalc, then hit enter. 2. Ctrl+C to copy the calculation result. 3. Ctrl+V in destination app to paste calculation result. And this workflow fails currently. This bug is really two problems in one: 1. I find it odd that the result view clears after hitting enter. IMO, it should still show the calculated result, especially since this is the view that gets copied to the clipboard. If the KCalc devs insist that the result view should clear after hitting enter, then at least have Ctrl-C copy the formula view to the clipboard if the result view is empty. 2. Highlighting the contents of the formula view, right-click → Copy appears to do nothing. STEPS TO REPRODUCE 1. In KCalc, enter a calculation (e.g., "24*24") and hit enter. OBSERVED RESULT The calculated value disappears from the result view, only appearing in the formula view, and cannot be copied. EXPECTED RESULT The calculated value should still appear in the result view (as it is the result of your calculation) and be copyable. WORKAROUND As a workaround, I am using GNOME Calculator, which functions as expected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 User Edition KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 492142] Help center content is blank
https://bugs.kde.org/show_bug.cgi?id=492142 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #1 from S. Christian Collins --- Created attachment 173344 --> https://bugs.kde.org/attachment.cgi?id=173344&action=edit screenshot showing the bug I can confirm this bug. Here is a screenshot. OS: KDE Neon 6.0 User Edition (Plasma Desktop 6.1.4, KDE Frameworks 6.5.0, Qt 6.7.0) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration possible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 --- Comment #9 from Ralf S --- (In reply to caulier.gilles from comment #7) > Ralf, > Problem still reproducible with current 8.5.0 pre-release AppImage bundle ? > https://files.kde.org/digikam/ > Gilles Caulier Gilles, thanks for asking, but I got rid of AppImagLauncher in the meantime, so I can’t check whether the error ist still reproducible. All in all AppImageLauncher made too many problems without too many benefits. I’m integrating AppImages manually now, which is straightforward enough and works without any issues. Ralf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration possible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 --- Comment #8 from Ralf S --- (In reply to caulier.gilles from comment #7) > Ralf, > > Problem still reproducible with current 8.5.0 pre-release AppImage bundle ? > > https://files.kde.org/digikam/ > > Gilles Caulier Gilles, thanks for asking, but I got rid of AppImagLauncher in the meantime, so I can’t check whether the error ist still reproducible. All in all AppImageLauncher made too many problems without too many benefits. I’m integrating AppImages manually now, which is straightforward enough and works without any issues. Ralf -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492358] New: Values of some form fields are not shown in non-forms mode
https://bugs.kde.org/show_bug.cgi?id=492358 Bug ID: 492358 Summary: Values of some form fields are not shown in non-forms mode Classification: Applications Product: okular Version: 24.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: m...@apache.org Target Milestone: --- Created attachment 173082 --> https://bugs.kde.org/attachment.cgi?id=173082&action=edit PDF document with form SUMMARY I will attach a PDF document which has an embedded form. There are two "date" fields which can be filled out in "Show Forms" mode. When that mode is exited and/or the PDF is printed no value is displayed for these fields. Saving the filled out document and opening it in Firefox (ie. pdf.js) shows the previously entered values. STEPS TO REPRODUCE 1. Start Okular 2. Download the form from https://www.hamburg.de/resource/blob/35658/bf5a89315bba109b3a8664d1ed4adcb1/arbeitszeitennachweis-kindertagespflege-data.pdf or use the attached version 3. Click the "Show Forms" button to switch to edit mode 4. Type in some value for "Name des Kindes" 5. Type in some date for "Geburtsdatum des Kindes". Like 01.01.1970 6. Leave the edit mode again by clicking "Show Forms" 7. Observe that the name will stay but the date will disappear (there is another date-like field "Beginn der Arbeit" which shows the same behaviour) 6. Save the file and close Okular 7. Open the file in Firefox 8. Observe that the values are filled out 9. I couldn't find an option to leave the edit mode there. But the value will stay visible in the print preview via Ctrl+P OBSERVED RESULT The values for those "date" fields disappear when the form edit mode is not active. Neither are they visible on a printout. EXPECTED RESULT The values should not disappear. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 19,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F9CTO1WW System Version: ThinkPad T460s ADDITIONAL INFORMATION libpoppler-qt6-3 24.02.0-0xneon+22.04+jammy+release+build30 libpoppler134 24.02.0-0xneon+22.04+jammy+release+build30 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490563] Task switcher: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
https://bugs.kde.org/show_bug.cgi?id=490563 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=490682 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490682] GL_INVALID_OPERATION errors when alt-tab tries to show window previews
https://bugs.kde.org/show_bug.cgi?id=490682 Malte S. Stretz changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-122819 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=490563 --- Comment #6 from Malte S. Stretz --- This bug was closed as "UPSTREAM" without a comment but I guess the upstream bug is https://bugreports.qt.io/browse/QTBUG-122819 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488869] When snapping a window to a custom tile using shift, kwin prints to journal "kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)"
https://bugs.kde.org/show_bug.cgi?id=488869 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org URL||https://bugreports.qt.io/br ||owse/QTBUG-122819 --- Comment #2 from Malte S. Stretz --- This bug was closed as "UPSTREAM" without a comment but I guess the upstream bug is https://bugreports.qt.io/browse/QTBUG-122819 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490682] GL_INVALID_OPERATION errors when alt-tab tries to show window previews
https://bugs.kde.org/show_bug.cgi?id=490682 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486582] Konsole start new sessions from previous folder ignores symlinks
https://bugs.kde.org/show_bug.cgi?id=486582 --- Comment #6 from Jonathan S --- Please ignore my previous comment. I misread the linked Fedora KDE SIG bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486582] Konsole start new sessions from previous folder ignores symlinks
https://bugs.kde.org/show_bug.cgi?id=486582 Jonathan S changed: What|Removed |Added CC||jonat...@sparky.nz --- Comment #5 from Jonathan S --- I've found this bug ticket while searching for existing tickets for something similar that I have observed on Fedora Kinoite 40. My home directory in /etc/passwd and $HOME are both set to "/home/jonathan", but when I launch Konsole, the initial directory is /var/home/jonathan with a prompt of: jonathan@xps:/var/home/jonathan$ If I do a "cd ~", it changes my present working directory to /home/jonathan and the prompt shows: jonathan@xps:~$ If I switch to a TTY console and log in, my initial directory is /home/jonathan and the prompt is: jonathan@xps:~$ Interestingly, if I go into the configuration of my Konsole profile, the "Initial directory" has "/home/jonathan" in a placeholder text light grey font (presumably loaded from /etc/passwd or $HOME ?), but if I click in there and replace this placeholder text with the same value of "home/jonathan" and relaunch Konsole, my initial directory works as expected (ie. it is /home/jonathan and the prompt is "jonathan@xps:~$"). So, it seems that Konsole is not handling the default value of "Initial directory" until it is explicitly set (to the same value). Apologies if this isn't the same issue as described in the bug report! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453453] IPv6 Address field not populated on existing WireGuard entries
https://bugs.kde.org/show_bug.cgi?id=453453 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=457041 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings if IPv6 is configured
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453453 --- Comment #12 from Malte S. Stretz --- There seem to be quite some issues with the IPv6 support for the Wireguard settings via the KCM: Added addresses (bug 453453) or routes (something I ran into) are not persisted even though the Apply button is not greyed out those cases. I guess that bug 461319 is related as well even though it doesn't mention IPv6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings if IPv6 is configured
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added Summary|Can't save Wireguard VPN|Can't save Wireguard VPN |settings|settings if IPv6 is ||configured -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453453] IPv6 Address field not populated on existing WireGuard entries
https://bugs.kde.org/show_bug.cgi?id=453453 Malte S. Stretz changed: What|Removed |Added Status|ASSIGNED|CONFIRMED CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added Version|5.25.3 |6.1.4 CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #5 from Malte S. Stretz --- *** This bug has been marked as a duplicate of bug 457041 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added CC||gudvinr+...@gmail.com --- Comment #11 from Malte S. Stretz --- *** Bug 458746 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 491401] SMART notification reporting is delayed
https://bugs.kde.org/show_bug.cgi?id=491401 --- Comment #3 from Colin S --- Hi, just wanted to make sure my question didn’t get lost in follow-up. If it is easier, just say what would need to be different to make a lower interval make sense to you. Always happy to understand the thoughts from an expert. Thanks and apologies in advance for the noise! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 491627] New: Import IPv6-only VPN config: ipv4.method: method "auto" is not supported for WireGuard
https://bugs.kde.org/show_bug.cgi?id=491627 Bug ID: 491627 Summary: Import IPv6-only VPN config: ipv4.method: method "auto" is not supported for WireGuard Classification: Plasma Product: plasma-nm Version: 6.1.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: plasma-b...@kde.org Reporter: m...@apache.org Target Milestone: --- Created attachment 172546 --> https://bugs.kde.org/attachment.cgi?id=172546&action=edit Mullvad WireGuard config file SUMMARY The attached config file was generated via https://mullvad.net/en/account/wireguard-config?platform=linux choosing "Only IPv6" for "Tunnel traffic". Plasma NM fails to import this with the error message > ipv4.method: method "auto" is not supported for WireGuard It can be imported successfully via > nmcli connection import type wireguard file dk-cph-wg-001.conf STEPS TO REPRODUCE 1. System Settings -> Wi-Fi & Internet 2. "Plus" 3. "Import VPN connection..." 4. Choose attached file OBSERVED RESULT Error EXPECTED RESULT A successfully imported WireGuard VPN connection SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.5.0-45-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F5S1H800 System Version: ThinkPad X260 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418941] Convert RAF Fuji XT2 to DNG not working
https://bugs.kde.org/show_bug.cgi?id=418941
Ralf S changed:
What|Removed |Added
CC||shopp...@ralfschmid.net
--- Comment #10 from Ralf S ---
> digiKam 8.4.0 pre-release now include last DNG SDK 1.7.1 from Adobe. Can you
> reproduce the dysfunction using AppImage bundle available here :
Though I’m not the thread opener, I can reproduce the described dysfunction in
AppImage 8.4.0 (Kubuntu). My source files are in RAF format taken with a Fuji
X-E2S. The DNG converter works neither in import ('cannot convert to dng') nor
in batch queue manager ('failed to process item, failed to create file').
Best wishes
Ralf
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-disks] [Bug 491401] SMART notification reporting is delayed
https://bugs.kde.org/show_bug.cgi?id=491401 --- Comment #2 from Colin S --- Thanks for your quick reply! Could you help me out and provide a link where the discussion for this decision was made so I can read that instead of making you write it out here? From my perspective, this is a time critical situation for end-users, and smartd has no problem polling on 30 minute interval, so I would like to understand why plasma-disks would decide that 24 hours is a necessary amount of time to wait between checks. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 491401] New: SMART notification reporting is delayed
https://bugs.kde.org/show_bug.cgi?id=491401 Bug ID: 491401 Summary: SMART notification reporting is delayed Classification: Plasma Product: plasma-disks Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@zetafleet.com CC: sit...@kde.org Target Milestone: --- SUMMARY My system experienced a disk hardware failure. The disk fell off the bus and then came back after a reboot with SMART failed status. smartd noticed this immediately and triggered its own reporting mechanism, and now emits critical errors to syslog every 30 minutes. plasma-disks took a whole day to notice that there was a SMART error and raise a notification. Glancing at the source code for plasma-disks, it does look like there is a fixed 24-hour timer in there to scan devices, so I guess that is probably how it finally managed to trigger a check and notify. Restarting the plasma-disks service causes it to report immediately, so I am not sure why it did not trigger on reboot, since the failing device already had to be initialised and on the bus for the system to even boot that far. STEPS TO REPRODUCE 1. Experience a hardware vendor trying to ruin your day OBSERVED RESULT No notification from the OS EXPECTED RESULT plasma-disks notifies immediately (or at least shortly thereafter) about the failure SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.9.10-amd64 (64-bit) ADDITIONAL INFORMATION If that 24 hour timer indeed is the only thing doing re-checks, and there is no easy way or desire to use smartd, it seems like it would be trivial and advisable to reduce the check time to something like 30 minutes. -- You are receiving this mail because: You are watching all bug changes.
[kwrited] [Bug 491272] New: Write Daemon/Local System Message Service does not show notifications sent using wall(1) or write(1)
https://bugs.kde.org/show_bug.cgi?id=491272 Bug ID: 491272 Summary: Write Daemon/Local System Message Service does not show notifications sent using wall(1) or write(1) Classification: Frameworks and Libraries Product: kwrited Version: 5.27.11 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: bugs.kde@zetafleet.com Target Milestone: --- SUMMARY Messages sent with wall(1) or write(1) never appear in the desktop environment (nor in Konsole sessions, for that matter, so this may not just be a Write Daemon issue). STEPS TO REPRODUCE 1. Open Konsole 2. Type `echo 'Hello' |wall` OBSERVED RESULT Nothing happens. EXPECTED RESULT A desktop notification should appear that says 'Hello'. Otherwise, if Write Daemon cannot initialise successfully for some reason, it should probably detect that and report it. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.9.10-amd64 (64-bit) ADDITIONAL INFORMATION I have confirmed that the Write Daemon service is enabled and running in Background Services, and that the Local System Message Service in Notifications is configured to “Show a message in a popup” for “The daemon received a new message sent with wall(1) or write(1)” event. Messages sent with wall/write *do* appear as expected in a plain tty (e.g. Ctrl+Alt+F5). Additionally, when the system shuts down, the wall/write messages are also visible in that tty. kwrited is built and packaged as a module rather than as an executable in Debian. I saw a comment in the CMakeLists.txt file that suggests that libutempter needs to be available; that package (libutempter0) was not installed on my system, so I installed it and restarted the Write Daemon service, and still did not receive notifications. There are no errors or warnings that I can see in logs that might suggest why this is not working. Running `w` shows one login with tty1 for `/usr/bin/startplasma-wayland`, and one login with no tty for `/usr/lib/systemd/systemd --user`. There are never additional logins for Konsole terminals and nothing about kwrited, but I do not know if this is expected or not. I am running KWin using Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 488036] can't re-dock the Colors toolbar
https://bugs.kde.org/show_bug.cgi?id=488036 --- Comment #2 from Vivian S. --- (In reply to Christoph Feck from comment #1) > Seems to be a KWin issue. Are you using a Wayland session? Yes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490968] New: No white icons in dark themes
https://bugs.kde.org/show_bug.cgi?id=490968 Bug ID: 490968 Summary: No white icons in dark themes Classification: Applications Product: digikam Version: 8.4.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Themes Assignee: digikam-bugs-n...@kde.org Reporter: shopp...@ralfschmid.net Target Milestone: --- SUMMARY Choosing a dark theme in Digikam 8.4.0 shows (barely visible) dark icons on dark background, restart doesn’t change this behaviour. Happens on Mint 21.3 and Mint 22 with the 8.4.0 AppImage as well as version 8.3.0. Issue seems to be in Mint only, in Kubuntu/KDE everything is fine. STEPS TO REPRODUåCE 1. Open Digikam in Mint. 2. Choose a dark theme. 3. Restart Digikam. OBSERVED RESULT Icons remain dark. EXPECTED RESULT Icons change to bright ones. SOFTWARE/OS VERSIONS Linux Mint 21.3 and 22, Cinnamon -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 485844] Editing the same comment twice, gives empty edit box.
https://bugs.kde.org/show_bug.cgi?id=485844 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490751] New: KMail crash when checking mail from Microsoft 365 work account
https://bugs.kde.org/show_bug.cgi?id=490751 Bug ID: 490751 Summary: KMail crash when checking mail from Microsoft 365 work account Classification: I don't know Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kashifsma...@gmx.com Target Milestone: --- Application: akonadi_ews_resource (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-23-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: "Check Mail" generated this error when synching with Microsoft 365 work account The crash can be reproduced sometimes. -- Backtrace: Application: Official (akonadi_ews_resource), signal: Segmentation fault [KCrash Handler] #4 0x560be36637f7 in ?? () #5 0x7fcd274e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcd30c9c775 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #7 0x7fcd30c9dc5b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7fcd274e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcd30c9c775 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7fcd30c9dc5b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7fcd274e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fcd30e05713 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7fcd30e03d56 in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7fcd30e08ac9 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7fcd274e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fcd274dd730 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fcd28162fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fcd274b1738 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fcd274b46c1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fcd2750a193 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fcd240127a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcd24012a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcd24012acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fcd27509876 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fcd274b01bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fcd274b8316 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x560be36b46f2 in ?? () #28 0x7fcd2704624a in __libc_start_call_main (main=main@entry=0x560be3653f40, argc=argc@entry=3, argv=argv@entry=0x7ffe12ad6908) at ../sysdeps/nptl/libc_start_call_main.h:58 #29 0x7fcd27046305 in __libc_start_main_impl (main=0x560be3653f40, argc=3, argv=0x7ffe12ad6908, init=, fini=, rtld_fini=, stack_end=0x7ffe12ad68f8) at ../csu/libc-start.c:360 #30 0x560be3659131 in ?? () [Inferior 1 (process 16110) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'akonadi_ews_resource' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490747] Exiftool missing in Windows 8.4 package
https://bugs.kde.org/show_bug.cgi?id=490747 S. Burmeister changed: What|Removed |Added Summary|Exiftool|Exiftool missing in Windows ||8.4 package -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490747] Exiftool
https://bugs.kde.org/show_bug.cgi?id=490747 --- Comment #2 from S. Burmeister --- Created attachment 171950 --> https://bugs.kde.org/attachment.cgi?id=171950&action=edit exiftool missing in windows 8.4 installation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490747] Exiftool
https://bugs.kde.org/show_bug.cgi?id=490747 --- Comment #1 from S. Burmeister --- Created attachment 171949 --> https://bugs.kde.org/attachment.cgi?id=171949&action=edit digikam dialogue when searching for the exiftool just looks for exiftool.exe -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490747] New: Exiftool
https://bugs.kde.org/show_bug.cgi?id=490747 Bug ID: 490747 Summary: Exiftool Classification: Applications Product: digikam Version: 8.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: sven.burmeis...@gmx.net Target Milestone: --- Created attachment 171948 --> https://bugs.kde.org/attachment.cgi?id=171948&action=edit Filename of the original exiftool archive from the official website SUMMARY STEPS TO REPRODUCE 1. Install digikam 8.4 2. start digikam 8.4 3. OBSERVED RESULT Digikam complains about missing exiftool EXPECTED RESULT Exiftool included and working SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION Pointing to the downloaded exiftool is not possible because the type is set to exiftool.exe but the file is actually named exiftool(-k).exe, see attached screenshots. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration possible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 --- Comment #5 from Ralf S --- Fine, thank you very much. I will do as you suggested. Ralf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration possible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 --- Comment #3 from Ralf S --- OK, thanks for your replies. Before I report the issue to AppImmageLauncher, just one more question. I get this, when I use Terminal to integrate the Appimage: $ chmod a+x /home/rs/Applications/digiKam-8.4.0-Qt6-x86-64.appimage $ /home/rs/Applications/digiKam-8.4.0-Qt6-x86-64.appimage install AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1) AppImageLauncher error: appimage_is_terminal_app() failed (returned -1) (process:5399): GLib-CRITICAL **: 10:03:35.339: g_file_test: assertion 'filename != NULL' failed (process:5399): GLib-CRITICAL **: 10:03:46.030: g_path_get_basename: assertion 'file_name != NULL' failed ** (process:5399): CRITICAL **: 10:03:46.030: Failed to find desktop file path Can you see anything AppImage related there? Or does ir rather confirm the AppImageLauncher problem assumption? Off topic: Is there a good method to integrate the AppImage manually the same way as AppImageLauncher does? I’m not too experienced with appimages yet but see pretty much advantages in the concept and plan to use them more often. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration possible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 Ralf S changed: What|Removed |Added Summary|AppImage: No system |AppImage: No system |integration pssible with|integration possible with |AppImageLauncher|AppImageLauncher -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] AppImage: No system integration pssible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 Ralf S changed: What|Removed |Added Summary|AppImage: No system |AppImage: No system |integtaion pssible with |integration pssible with |AppImageLauncher|AppImageLauncher -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490657] New: AppImage: No system integtaion pssible with AppImageLauncher
https://bugs.kde.org/show_bug.cgi?id=490657 Bug ID: 490657 Summary: AppImage: No system integtaion pssible with AppImageLauncher Classification: Applications Product: digikam Version: 8.4.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: shopp...@ralfschmid.net Target Milestone: --- SUMMARY Using the 'Integrate to system and run' command when first clicking the AppImage moves the AppImage to the desired location but shows the error 'Failed to register AppImage in system via libappimage' after. The AppImage won't show in the menu and no .desktop file is created. Until Digikam 8.3.0 it all worked fine. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION AppimageLauncher ist the latest stable PPA. The bug occurs in the same manner on Mint 21.3. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 489980] uppercase exponential not understood
https://bugs.kde.org/show_bug.cgi?id=489980 --- Comment #6 from S. Umar --- I tested the master git (not committed to 24.05 branch yet) and the capital E exponents work now. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490095] Some Extensions & App make my laptop slow
https://bugs.kde.org/show_bug.cgi?id=490095 Abdullah S changed: What|Removed |Added URL||https://elixiruaq.com/artif ||icial-grass/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490095] New: Some Extensions & App make my laptop slow
https://bugs.kde.org/show_bug.cgi?id=490095 Bug ID: 490095 Summary: Some Extensions & App make my laptop slow Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: infinityinsight4...@gmail.com Target Milestone: --- Hi, Some extensions and apps are making my laptop slow, including MS Office and Google Chrome. Can you help me find out which ones are causing the problem and how to fix it? My laptop's slow performance is affecting my work, and I need it to run faster. I would really appreciate your help in identifying and removing the problematic extensions and apps, and optimizing my system for better speed and efficiency. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 489980] uppercase exponential not understood
https://bugs.kde.org/show_bug.cgi?id=489980 --- Comment #2 from S. Umar --- Hi, I believe most FORTRAN compilers use the upper case. I am using the latetst Intel OneApi fortran compilers. One can code lower case e but the output files have the upper case. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 489980] New: uppercase exponential not understood
https://bugs.kde.org/show_bug.cgi?id=489980 Bug ID: 489980 Summary: uppercase exponential not understood Classification: Applications Product: kcalc Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: u...@compsci.cas.vanderbilt.edu CC: gabriel.barrantes@outlook.com Target Milestone: --- If I input 3.6434E+01 into kcalc it gives me "input error" but lowercase version 3.6434e+01 gvies 36.434. Uppercase is iseful when pasting from outputs (like fortran) which uses the uppercase E. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489872] New: DE: Missing translation "Log out Now"
https://bugs.kde.org/show_bug.cgi?id=489872 Bug ID: 489872 Summary: DE: Missing translation "Log out Now" Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: m...@apache.org CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY The German translation is missing a string on the log out screen: Everything is translated except the "Log out Now" caption. STEPS TO REPRODUCE 1. Use German translations 2. Log out from a session OBSERVED RESULT The left button is labelled with "Log out Now" EXPECTED RESULT It should be labelled "Jetzt abmelden" or something like that. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F5S1H800 System Version: ThinkPad X260 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485578] /etc/xdg/autostart/klipper.desktop is obsolete or refers to wrong command
https://bugs.kde.org/show_bug.cgi?id=485578 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Malte S. Stretz --- This seems to be fixed in the current packages. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 Malte S. Stretz changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #5 from Malte S. Stretz --- The crash is caused by the ancient Pipewire version in Ubuntu 22.04. This will be fixed once Neon is rebased on 24.04. As a workaround one can install the packages from the PPA at https://pipewire-debian.github.io/pipewire-debian/ The install will fail due to a dependency issue unless one removes the pipewire-pulse package first (it is reinstalled automatically). It is probably a good idea to downgrade pipewire before the upgrade to 24.04 is applied (eg. via ppa-purge). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=488749 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488749] Screen Recorder error in PipeWire remote in all screen recorders, include obs studio: black screen!
https://bugs.kde.org/show_bug.cgi?id=488749 Malte S. Stretz changed: What|Removed |Added Platform|Other |Neon Ever confirmed|0 |1 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=488924 Status|REPORTED|CONFIRMED CC||m...@apache.org --- Comment #7 from Malte S. Stretz --- This should be fixed once Plasma is rebased on Ubuntu 24.04 which is currently work in progress. In the meantime I worked around this issue by installing pipewire from https://pipewire-debian.github.io/pipewire-debian/ There is a dependency issue which means you have to remove the package pipewire-pulse before you update (it will autoamtically be added again). There are no guarantees though that the upgrade to 24.04 will work so you might want to remove that PPA via ppa-purge before you do that upgrade. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 489134] no menus in LibreOffice with Wayland Session
https://bugs.kde.org/show_bug.cgi?id=489134 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM See Also||https://github.com/flathub/ ||org.libreoffice.LibreOffice ||/issues/234 --- Comment #1 from Malte S. Stretz --- This seems to be an issue in the LibreOffice Flatpak which is tracked here https://github.com/flathub/org.libreoffice.LibreOffice/issues/234 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept rapidly-typed keystrokes for first invocation after login, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489336] SSH connection with key not working in Wayland session
https://bugs.kde.org/show_bug.cgi?id=489336 Malte S. Stretz changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||m...@apache.org --- Comment #1 from Malte S. Stretz --- I am not 100% sure but I guess you expect the ksshaskpass prompt to pop up? Then the issue is in upstream OpenSSH (and will be fixed in some future version, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068044) which doesn't recognize Wayland sessions as graphical sessions and thus never starts the askpass process. You can try env SSH_ASKPASS_REQUIRE=force ssh -i /path/to/key.pem root@ -p 22 to see if that solves your issue. If that doesn't solve it it is probably some other local configuration issue and you should ask on https://discuss.kde.org/tag/neon or https://webchat.kde.org/#/room/#kde-neon-users:kde.org for help. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 489450] Add support for WIM files
https://bugs.kde.org/show_bug.cgi?id=489450 Malte S. Stretz changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login
https://bugs.kde.org/show_bug.cgi?id=488022 S. Umar changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #8 from S. Umar --- per comment #6 the issue is resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483698 S. Christian Collins changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from S. Christian Collins --- This issue is now resolved in Plasma 6.1.1. I am now getting smooth desktop response in Plasma again. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487904] Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the
https://bugs.kde.org/show_bug.cgi?id=487904 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485895] Error loading Vaults
https://bugs.kde.org/show_bug.cgi?id=485895 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 487597] Error loading vaults
https://bugs.kde.org/show_bug.cgi?id=487597 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #4 from Malte S. Stretz --- The Ubuntu pipewire changelog is quite interesting: pipewire (0.3.48-1ubuntu3) jammy; urgency=medium * Revert the previous change to resolve a regression with screencasting. Extra fixes are available upstream but figuring out the details will take longer (https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1994928) -- Sebastien Bacher Wed, 09 Nov 2022 12:12:45 +0100 pipewire (0.3.48-1ubuntu2) jammy; urgency=medium * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057) -- Kai-Chuan Hsieh Mon, 15 Aug 2022 13:52:20 +0800 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #3 from Malte S. Stretz --- Accord to Nate Graham on the Neon Development channel does current Plamsa not work with the old 0.3 pipewire, at least not the jammy version (https://matrix.to/#/!tTRWOsgaQxxZMiAvdi:kde.org/$2w6AojIYScf4KaoIdoPNEAZCM7jDk851LuEQKXIvQOw). I did quick backport of the kinetic version 0.3.58 (instead of jammy's 0.3.48) and that makes KPipeWire crash instead (I saw crashes within xdg-desktop-portal-kde and plasmashell within minutes after the switch). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #2 from Malte S. Stretz --- I found a simpler way to trigger the crash which does not involve flatpak: Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ in Firefox (from the PPA) and try that. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #1 from Malte S. Stretz --- The DrKonqi crash viewer does not pull the debug symbols, here is the same stack trace from gdb: Thread 8 (Thread 0x7768c49ff640 (LWP 22508)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c23f80, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=2, fds=0x59cd11c23f80, timeout=, context=0x59cd11c25590) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=context@entry=0x59cd11c25590, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a423e3 in g_main_context_iteration (context=0x59cd11c25590, may_block=may_block@entry=1) at ../../../glib/gmain.c:4278 #4 0x7768c5a42431 in glib_worker_main (data=) at ../../../glib/gmain.c:6180 #5 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11bf4360) at ../../../glib/gthread.c:827 #6 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #7 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7768bd3fd640 (LWP 22517)): #0 0x7768c52e57f8 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7768bd3fccb0, rem=rem@entry=0x7768bd3fccb0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78 #1 0x7768c52ea677 in __GI___nanosleep (req=req@entry=0x7768bd3fccb0, rem=rem@entry=0x7768bd3fccb0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25 #2 0x7768c52ea5ae in __sleep (seconds=0, seconds@entry=5) at ../sysdeps/posix/sleep.c:55 #3 0x59cd106886f3 in background_monitor (data=) at ../src/background.c:654 #4 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11ce4980) at ../../../glib/gthread.c:827 #5 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #6 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 6 (Thread 0x7768bf7fe640 (LWP 26844)): #0 0x7768c5325e2e in epoll_wait (epfd=26, events=0x7768bf7fd880, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7768c4e18918 in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7768c4e0bd7c in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7768c56ee226 in () at /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 5 (Thread 0x7768b640 (LWP 22509)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c92b70, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=4, fds=0x59cd11c92b70, timeout=, context=0x59cd11c30150) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=0x59cd11c30150, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a442b3 in g_main_loop_run (loop=0x59cd11c30240) at ../../../glib/gmain.c:4413 #4 0x7768c592a81a in gdbus_shared_thread_func (user_data=0x59cd11c22520) at ../../../gio/gdbusprivate.c:282 #5 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11c185e0) at ../../../glib/gthread.c:827 #6 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #7 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 4 (Thread 0x7768c4e61cc0 (LWP 22502)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c4cbf0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=3, fds=0x59cd11c4cbf0, timeout=, context=0x59cd11c1dfb0) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=0x59cd11c1dfb0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a442b3 in g_main_loop_run (loop=0x59cd11c10770) at ../../../glib/gmain.c:4413 #4 0x59cd10656a25 in main (argc=, argv=) at ../src/xdg-desktop-portal.c:496 Thread 3 (Thread 0x7768bdbfe640 (LWP 22516)): #0 0x7768c5325e2e in epoll_wait (epfd=15, events=0x7768bdbfd880, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7768c4e18918 in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7768c4e0bd7c in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7768c56ee226 in () at /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x7768be3ff640 (LWP 22514)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c6dd60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=1
