[plasmashell] [Bug 484807] New: plasmashell crashes if the ksycoca database is deleted from under it

[K900]

https://bugs.kde.org/show_bug.cgi?id=484807

Bug ID: 484807
   Summary: plasmashell crashes if the ksycoca database is deleted
from under it
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: NixOS
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: m...@0upti.me
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.1-300.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
Be running Plasma -> `rm -rf ~/.cache/ksycoca*` -> open Kickoff -> kaboom.
Reproduces semi-consistently on NixOS and Fedora Rawhide, looks like a race
somewhere? Please don't ask me why I'm doing this.

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Aborted


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 2110]
[New LWP 2124]
[New LWP 2151]
[New LWP 2123]
[New LWP 2162]
[New LWP 2183]
[New LWP 2153]
[New LWP 2155]
[New LWP 3048]
[New LWP 2942]
[New LWP 3047]
[New LWP 3025]
[New LWP 3051]
[New LWP 2152]
[New LWP 2167]
[New LWP 2154]
[New LWP 2156]
[New LWP 2157]
[New LWP 2158]
[New LWP 3360]
[New LWP 2161]
[New LWP 2159]
[New LWP 2163]
[New LWP 2160]
[New LWP 2125]
[New LWP 3045]
[New LWP 3020]
[New LWP 2169]
[New LWP 2378]
[New LWP 2171]
[New LWP 2172]
[New LWP 2164]
[New LWP 2166]
[New LWP 3044]
[New LWP 3053]
[New LWP 2938]
[New LWP 3042]
[New LWP 3018]
[New LWP 2176]
[New LWP 2174]
[New LWP 2170]
[New LWP 2178]
[New LWP 3322]
[New LWP 3664]
[New LWP 2180]
[New LWP 3755]
[New LWP 3043]
[New LWP 3046]
[New LWP 2182]
[New LWP 2177]
[New LWP 3040]
[New LWP 2175]
[New LWP 3052]
[New LWP 3050]
[New LWP 2179]
[New LWP 3049]
[New LWP 2181]
[New LWP 2168]
[New LWP 3751]
[New LWP 3041]
[New LWP 2173]
[New LWP 3062]
[New LWP 3019]
[New LWP 2977]
[New LWP 3754]
[New LWP 2165]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fcca1eab134 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fcc9d553b00 (LWP 2110))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fcc9d553b00 (LWP 2110))]

Thread 66 (Thread 0x7fcc620006c0 (LWP 2165)):
#0  0x7fcca1ea5909 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fcca1ea82d9 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fcc85a9 in cnd_wait () from /usr/lib64/dri/swrast_dri.so
#3  0x7fcc860d6183 in thread_function () from /usr/lib64/dri/swrast_dri.so
#4  0x7fcc85a9dd0c in impl_thrd_routine () from
/usr/lib64/dri/swrast_dri.so
#5  0x7fcca1ea91a7 in start_thread () from /lib64/libc.so.6
#6  0x7fcca1f2b33c in clone3 () from /lib64/libc.so.6

Thread 65 (Thread 0x7fcbd20006c0 (LWP 3754)):
#0  0x7fcca1ea5909 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fcca1ea82d9 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fcca274e17b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt6Core.so.6
#3  0x7fcca4287119 in QSGRenderThread::processEventsAndWaitForMore() ()
from /lib64/libQt6Quick.so.6
#4  0x7fcca428739a in QSGRenderThread::run() () from
/lib64/libQt6Quick.so.6
#5  0x7fcca274562c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#6  0x7fcca1ea91a7 in start_thread () from /lib64/libc.so.6
#7  0x7fcca1f2b33c in clone3 () from /lib64/libc.so.6

Thread 64 (Thread 0x7fcc25a006c0 (LWP 2977)):
#0  0x7fcca1f2b742 in epoll_wait () from /lib64/libc.so.6
#1  0x7fcc6d645416 in impl_pollfd_wait () from
/usr/lib64/spa-0.2/support/libspa-support.so
#2  0x7fcc6d6370c1 in loop_iterate () from
/usr/lib64/spa-0.2/support/libspa-support.so
#3  0x7fcc6d66f2a3 in do_loop () from /lib64/libpipewire-0.3.so.0
#4  0x7fcca1ea91a7 in start_thread () from /lib64/libc.so.6
#5  0x7fcca1f2b33c in clone3 () from /lib64/libc.so.6

Thread 63 (Thread 0x7fcc03e006c0 (LWP 3019)):
#0  0x7fcca1ea5909 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7fcca1ea8642 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7fcca274e0fd in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt6Core.so.6
#3  0x7fcca274aeb3 in QThreadPoolThrea

[plasma-nm] [Bug 471870] With NetworkManager 1.44, the Networks applet disappears or loses all networks after stop/start of NetworkManager, which sometimes happens on wake from sleep in certain distro

[K900]

https://bugs.kde.org/show_bug.cgi?id=471870

--- Comment #17 from K900  ---
Submitted a PR:
https://invent.kde.org/frameworks/networkmanager-qt/-/merge_requests/49

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 471870] With NetworkManager 1.44, the Networks applet disappears or loses all networks after stop/start of NetworkManager, which sometimes happens on wake from sleep in certain distro

[K900]

https://bugs.kde.org/show_bug.cgi?id=471870

--- Comment #16 from K900  ---
I think I have an idea of what the issue is. Can affected people test this
patch please?
https://github.com/NixOS/nixpkgs/blob/a2b55199b433edabc434469346130391837cad8e/pkgs/development/libraries/kde-frameworks/nmqt.patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 476323] "No connections found" after restarting NetworkManager 1.44

[K900]

https://bugs.kde.org/show_bug.cgi?id=476323

--- Comment #2 from K900  ---
I am actually not entirely sure this is the same bug - 471870 mentions the
applet disappearing entirely, while at least in my case it is still there, just
not listing connections.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 476323] New: "No connections found" after restarting NetworkManager 1.44

[K900]

https://bugs.kde.org/show_bug.cgi?id=476323

Bug ID: 476323
   Summary: "No connections found" after restarting NetworkManager
1.44
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.9
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: m...@0upti.me
  Target Milestone: ---

SUMMARY

When running NetworkManager 1.44 and plasma-nm, and restarting NetworkManager
(e.g. with `systemctl restart NetworkManager`), the plasma-nm applet enters a
weird state where it always shows "No connections found", despite NM operating
properly in the background. Restarting Plasma or the applet (if loaded
separately) fixes it until the next NM restart.

Reported in NixOS: https://github.com/NixOS/nixpkgs/pull/263985
Also reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053707
Also similar issues reported in Arch:
https://www.reddit.com/r/archlinux/comments/16in04o/plasma_nm_applet_does_not_show_any_networks_and/

STEPS TO REPRODUCE
1. Use NetworkManager 1.44
2. `systemctl restart NetworkManager`

OBSERVED RESULT
Applet shows "No connections found"

EXPECTED RESULT
Applet shows connections properly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS unstable
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.110
Qt Version: 5.11 + KDE patchsets

ADDITIONAL INFORMATION
This used to work fine with NM 1.42.x, so something must have changed in
between 1.42.x and 1.44.0 that causes this behavior.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 433890] can not share desktop under wayland, only got a black screen

[K900]

https://bugs.kde.org/show_bug.cgi?id=433890

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 468203] Window buttons are too big and blurry

[K900]

https://bugs.kde.org/show_bug.cgi?id=468203

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 454161] Brightness stuck at 30%

[K900]

https://bugs.kde.org/show_bug.cgi?id=454161

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

--- Comment #26 from K900  ---
Also works for me on Dell Latitude 5420.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 433868] PowerDevil with ACPI resource mode lax causes generates issues with AMDPU

[K900]

https://bugs.kde.org/show_bug.cgi?id=433868

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

--- Comment #3 from K900  ---
AFAICT Powerdevil doesn't actually do any I2C accesses by itself, but it does
call ddcutil, which does. Filed a ddcutil issue:
https://github.com/rockowitz/ddcutil/issues/194

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 275433] [multi-head] multiple window size issues

[K900]

https://bugs.kde.org/show_bug.cgi?id=275433

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[K900]

https://bugs.kde.org/show_bug.cgi?id=373232

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405762] xesam:artist is not read as List

[K900]

https://bugs.kde.org/show_bug.cgi?id=405762

--- Comment #4 from K900  ---
A friend submitted a draft patch that seems to fix this:
https://phabricator.kde.org/D24740

However, I can't actually find a single player that _does_ report xesam:artist
as a single string, so it's possible that a correct patch could be a lot
simpler.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405762] xesam:artist is not read as List

[K900]

https://bugs.kde.org/show_bug.cgi?id=405762

--- Comment #3 from K900  ---
I've got a custom script that pulls data from a web page and feeds it into
MRPIS, and I have it follow the FDO spec. 

Clementine seems to use a list too:
https://github.com/clementine-player/Clementine/blob/17d95b7833fd0f8b7547d70a6dbf3367be31b85e/src/core/song.cpp#L1176
(despite only ever having a single artist per track).

So does Rhythmbox:
https://github.com/GNOME/rhythmbox/blob/4abbd528da0a32d0c343a22d5dfb2c5e98c489f5/plugins/mpris/rb-mpris-plugin.c#L557
(but, again, only with a single track - note the last argument to
add_string_property_2, which is "gboolean as_list").

VLC seems to also use a single item list?
https://github.com/videolan/vlc/blob/f83434ac6488e5cee32e191f9a89859254156b0e/modules/control/dbus/dbus.c#L1305

It seems like there's some sort of auto-cast involved - doing
`console.log(currentMetadata["xesam:artist"])` gives me `[Artist Name]`, but
the applet still processes it correctly. Adding more than one artist breaks
things though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405762] xesam:artist is not read as List

[K900]

https://bugs.kde.org/show_bug.cgi?id=405762

--- Comment #1 from K900  ---
Moved this to the right component (I hope). Can confirm it's still an issue on
plasma-workspace 5.17.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405762] xesam:artist is not read as List

[K900]

https://bugs.kde.org/show_bug.cgi?id=405762

K900  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
  Component|MediaController |Media Player
Version|unspecified |master
   Assignee|ksi...@gmail.com|k...@privat.broulik.de
Product|plasma-mediacenter  |plasmashell
 CC||m...@0upti.me,
   ||plasma-b...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 384532] Desktop toolbox button jumps around if placed in a corner

[K900]

https://bugs.kde.org/show_bug.cgi?id=384532

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

--- Comment #9 from K900  ---
Can also reproduce with the top screen edge (on a multi-screen setup, which
might matter?); the toolbox jumps horizontally.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

[K900]

https://bugs.kde.org/show_bug.cgi?id=405501

--- Comment #2 from K900  ---
Yeah, that's what I've been doing. Also, it turns out the autoconnect setting
is actually enabled by nmcli by default for some reason, so that one isn't
plasma-nm's fault. Anyway, I might just start hacking on it when I get the time
(but please feel free to snipe me)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

[K900]

https://bugs.kde.org/show_bug.cgi?id=405501

K900  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages
 CC||m...@0upti.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 405501] New: plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

[K900]

https://bugs.kde.org/show_bug.cgi?id=405501

Bug ID: 405501
   Summary: plasma-nm is not compatible with NetworkManager 1.16's
native WireGuard support
   Product: plasma-nm
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: m...@0upti.me
  Target Milestone: ---

SUMMARY
The WireGuard connections are shown as wired connections, and are brought up
automatically on login.

STEPS TO REPRODUCE
1. Install NetworkManager 1.16
2. nmcli connection import type wireguard file my-wg-conf.conf
3. Open plasma-nm

OBSERVED RESULT
WireGuard connection is treated as an Ethernet connection

EXPECTED RESULT
WireGuard connection should be treated as a WireGuard connection

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 397572] New: Add support for the Wireguard plugin

[K900]

https://bugs.kde.org/show_bug.cgi?id=397572

Bug ID: 397572
   Summary: Add support for the Wireguard plugin
   Product: plasma-nm
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: m...@0upti.me
  Target Milestone: ---

There's now a Wireguard plugin for NetworkManager itself at
https://github.com/max-moser/network-manager-wireguard, and it works really
well (in my experience), but the connection editor part isn't there on Plasma's
side, and the applet seems to refuse to bring up the connection (while nmcli
works fine). I'd be up for doing this myself if anyone can help me find my way
around the codebase :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 394580] Wrong icon size on network manager applet

[K900]

https://bugs.kde.org/show_bug.cgi?id=394580

K900  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 CC||m...@0upti.me
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from K900  ---
I can reproduce the issue locally, clearing cache doesn't help :(

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 378718] Yakuake drop-down terminal presenting Spectacle bindings to not work

[K900]

https://bugs.kde.org/show_bug.cgi?id=378718

K900  changed:

   What|Removed |Added

 CC||m...@0upti.me

--- Comment #1 from K900  ---
Can confirm this is still an issue with latest Spectacle/Yakuake on X11.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 198661] Add option to disable scroll on taskbar

[K900]

https://bugs.kde.org/show_bug.cgi?id=198661

K900  changed:

   What|Removed |Added

 CC|m...@0upti.me |

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[K900]

https://bugs.kde.org/show_bug.cgi?id=386892

K900  changed:

   What|Removed |Added

 CC|m...@0upti.me |

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction

[K900]

https://bugs.kde.org/show_bug.cgi?id=381630

K900  changed:

   What|Removed |Added

 CC|m...@0upti.me |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 311636] image previews being embedded into oxygen folder instead of selected icon theme

[K900]

https://bugs.kde.org/show_bug.cgi?id=311636

K900  changed:

   What|Removed |Added

 CC|m...@0upti.me |

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction

[K900]

https://bugs.kde.org/show_bug.cgi?id=381630

K900  changed:

   What|Removed |Added

 CC||k0009...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[K900]

https://bugs.kde.org/show_bug.cgi?id=386892

K900  changed:

   What|Removed |Added

 CC||k0009...@gmail.com

--- Comment #3 from K900  ---
Same issue for me on latest Arch, so it's not just Parabola that's affected.

-- 
You are receiving this mail because:
You are watching all bug changes.