[systemsettings] [Bug 480632] New: Add (basic) systemd-networkd backend support for System Settings' Network Management
https://bugs.kde.org/show_bug.cgi?id=480632 Bug ID: 480632 Summary: Add (basic) systemd-networkd backend support for System Settings' Network Management Classification: Applications Product: systemsettings Version: git-stable-Plasma/5.27 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_networkmanagement Assignee: plasma-b...@kde.org Reporter: andr...@ohok.org CC: jgrul...@redhat.com Target Milestone: --- SUMMARY Network Connections currently supports Network Manager as a backend, and it does so well. Currently there is no support for systemd-networkd in any DE including Plasma, despite systemd being ubiquitous. Even basic support would thus be a major differentiating factor for Plasma, and it would enable easier desktop use of systemd-networkd. I'm aware that this is likely a very major task for a (currently) nieche use-case, but maybe this issue can also be used to gauge if there is any interest for this. IMO even starting at displaying network status and managing WIFI would already be sufficient. Users who wish to use networkd at this time on their Desktop can be expected to understand limitations in GUI integrations for that. I found this earlier request for this: https://bugs.kde.org/show_bug.cgi?id=417168 I apologize for opening such a similar request again, but IMO enough time has passed since to reconsider this. Networkd is widely available and stable and the main hindrance to adoption on the desktop is a lack of GUI support. STEPS TO REPRODUCE Remove NM and set up systemd-networkd. OBSERVED RESULT Nothing. EXPECTED RESULT System settings and possibly the tray should be able to display network status and possibly allow basic settings, particularly wifi connection management. SOFTWARE/OS VERSIONS All ADDITIONAL INFORMATION Feature request -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479020] New: Attempting to import a wireguard configuration with an invalid name leads to a misleading error message
https://bugs.kde.org/show_bug.cgi?id=479020
Bug ID: 479020
Summary: Attempting to import a wireguard configuration with an
invalid name leads to a misleading error message
Classification: Applications
Product: systemsettings
Version: git-stable-Plasma/5.27
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: kcm_networkmanagement
Assignee: plasma-b...@kde.org
Reporter: andr...@ohok.org
CC: jgrul...@redhat.com
Target Milestone: ---
SUMMARY
NetworkManager requires that when importing a .conf file with a wireguard
config that it contains the name of the interface be included in the filename.
In the Linux kernel, interface names can only be up to 16 bytes in length.
Attempting to import a longer filename with nmcli yields the following error
message:
Error: failed to import 'sadadsadasdasdasdad.conf': The name of the WireGuard
config must be a valid interface name followed by ".conf".
Doing the same with KDE Plasma NetworkManager integration in system settings
("Import VPN connection") yields: "Failed to import VPN connection:
NetworkManager is missing support for OpenVPN" which makes no sense.
STEPS TO REPRODUCE
1. Use import VPN connection to import a valid wireguard .conf file, but with a
name that is longer than 16 bytes.
OBSERVED RESULT
"Failed to import VPN connection: NetworkManager is missing support for
OpenVPN"
EXPECTED RESULT
A correct and helpful error message
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
Happy holidays!
--
You are receiving this mail because:
You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 Andreas Hartmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #8 from Andreas Hartmann --- Ok, I found the problem: openSuSE 15.4 comes with /etc/profile.d/openssh-dbus.sh as part of openssh-server: if test -n "$SSH_CONNECTION" -a -n "$DISPLAY" then dbus-update-activation-environment --systemd --all fi Deactivating this file makes it working again. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 --- Comment #7 from Andreas Hartmann --- Further investigation showed: manually changing the activation-environment after the login has been performed on a local tty, things are working again, too: dbus-update-activation-environment DISPLAY XAUTHORITY Doing the same with a "broken" DISPLAY environment breaks the logout window again (not surprising). The question for me is: Why does a simple ssh -X - login changes the global environment - even for the local running user (at least for processes started by dbus)? This doesn't make any sense to me! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 --- Comment #6 from Andreas Hartmann --- The exactly same behavior can be seen running KDE under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #48 from Andreas Hartmann --- Please ignore my last entry - wrong ticket :-). -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #47 from Andreas Hartmann --- Exactly same problem can be seen even if KDE is run in wayland mode ... . -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 --- Comment #5 from Andreas Hartmann --- It's even more easy to reproduce it (assuming there is a ssh server running on localhost): just do a ssh -X localhost and the problem can be seen. Btw: if you do it like described above, there is a warning: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments The actual workaround is to replace /usr/lib/ksmserver-logout-greeter with a script which explicitly sets DISPLAY to :0 and afterwards start the original ksmserver-logout-greeter. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 Andreas Hartmann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Andreas Hartmann --- I now know what happens. I moved ksmserver-logout-greeter and added instead a small bash script which logs the environment to a log file. And voila, the culprit is: ... DISPLAY=localhost:10.0 SSH_CONNECTION=192.168.1.59 35858 192.168.1.6 22 ... What happened? Before that, I remotely logged in via ssh to this machine with ssh -XC 192.168.1.6 konsole This obviously completely breaks the environment! But why? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432810] On X11 with non-Intel GPU, exiting some apps sometimes hangs plasma for 5-10 secs
https://bugs.kde.org/show_bug.cgi?id=432810 --- Comment #21 from Andreas Hartmann --- I added a trace excerpt at the duplicate bug. If you would have read this, you would have seen, that it's exactly 5 sec. 5-10 sec was an initial guess. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 --- Comment #2 from Andreas Hartmann --- Thanks for your hint! Problem appeared again - and there was no difference in environment compared to before, as it was working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432810] exiting some apps sometimes hangs plasma for 5-10 secs
https://bugs.kde.org/show_bug.cgi?id=432810 --- Comment #19 from Andreas Hartmann --- I was not able to reproduce it using Wayland. But I wasn't able to reproduce it, too, using X11 Gnome ... . I can see it in X11 with nvidia or amd GPU. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432810] exiting some apps sometimes hangs plasma for 5-10 secs
https://bugs.kde.org/show_bug.cgi?id=432810 --- Comment #18 from Andreas Hartmann --- I added some findings here: https://bugs.kde.org/show_bug.cgi?id=463148 Somebody who knows more about the mentioned connection which times out, could most probably solve the problem :-)! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 --- Comment #9 from Andreas Hartmann --- Further strace shows, that the mentioned timed out connection (0x55c409e84f40) is an existing connection in plasmashell which gets reused over and over again (as long as plasmashell isn't stopped). It is exactly reused at the moment of the copy to clipboard with CTRL-u. Maybe there is a problem after clipboard clearing? Keepassxc clears the clipboard after 10 s (but waiting after the clipboard is cleared doesn't "solve" the problem). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148
--- Comment #8 from Andreas Hartmann ---
I did a strace on the keepassxc process. After closing keepassxc (using ALT-F4
e.g.), the app is closed instantly, but the icon hangs for about 5 s in the
plasmashell.
Next, I straced kded and plasmashell. kded exactly reports the end of
keepassxc:
22457 19:30:51 (+ 0.009041) --- SIGCHLD {si_signo=SIGCHLD,
si_code=CLD_EXITED, si_pid=28400, si_uid=1000, si_status=0, si_utime=93,
si_stime=8} ---
22457 19:30:51 (+ 0.13) waitid(P_ALL, 0, {si_signo=SIGCHLD,
si_code=CLD_EXITED, si_pid=28400, si_uid=1000, si_status=0, si_utime=0,
si_stime=0}, WNOHANG|WEXITED|WNOWAIT, NULL) = 0
22457 19:30:51 (+ 0.17) wait4(28400, [{WIFEXITED(s) && WEXITSTATUS(s)
== 0}], WNOHANG, {ru_utime={tv_sec=0, tv_usec=974179}, ru_stime={tv_sec=0,
tv_usec=91589}, ...}) = 28400
After this entry, it takes 5 seconds until plasmashell is "unlocked" again.
This starts with this TIMEOUT:
22471 19:30:56 (+ 0.293456) <... futex resumed>) = -1 ETIMEDOUT (Connection
timed out)
Unfortunately, I can't say which connection exactly timed out.
BTW:
It's even not necessary to paste the copied data anywhere - it's enough to just
do CTRL-u ... .
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 --- Comment #7 from Andreas Hartmann --- I was able to reproduce the same problem as described before after logout from KDE and relogin. Seems that CTRL-b or CTRL-u triggers the problem, but not SHIFT-CTRL-c ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 --- Comment #6 from Andreas Hartmann --- I was able to trigger it a few times at the moment with keepassxc: - Start keepassx - Search for account via search field - mark the desired entry - CTRL-u to copy the URL - paste URL to Firefox - open URL in Firefox - CTRL-B to copy password to Firefox login dialog of website - closed keepasxc - kicker and desktop, ... hangs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 --- Comment #5 from Andreas Hartmann --- No - it happens only sometimes (sporadically) and it is not reproducible (or I don't know how to reproduce it). Using keepassxc via copy / paste of passwords (CTRL-SHIFT-V) doesn't necessarily trigger the problem (tested at the moment again - worked just fine as expected). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 --- Comment #3 from Andreas Hartmann --- Unfortunately not. That's why I wrote "sometimes". If the problem doesn't happen, all apps can be closed without any problem - even keepassxc. If it happens, it happens not only with keepassxc, but any other program, too - like libreoffice e.g. Is it possible to enable some debug output? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 463557] New: Logout sometimes(!!) not possible
https://bugs.kde.org/show_bug.cgi?id=463557 Bug ID: 463557 Summary: Logout sometimes(!!) not possible Classification: Plasma Product: ksmserver Version: 5.26.4 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andihartm...@freenet.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Trying to logout sometimes - not always!! - doesn't work. If it doesn't work, you can see this error in system log: Dec 28 08:36:37 lhost dbus-daemon[5204]: [session uid=1000 pid=5204] Activating service name='org.kde.LogoutPrompt' requested by ':1.18' (uid=1000 pid=5348 comm="/usr/bin/plasmashell --no-respawn ") Dec 28 08:36:37 lhost ksmserver-logout-greeter[23052]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. Dec 28 08:36:37 lhost ksmserver-logout-greeter[23052]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Dec 28 08:37:44 lhost dbus-daemon[5204]: [session uid=1000 pid=5204] Activating service name='org.kde.Shutdown' requested by ':1.63' (uid=1000 pid=23614 comm="/usr/lib/ksmserver-logout-greeter This only happened until now, if the user has been logged on for several hours. I tried to find a reason which could be responsible for the problem - but couldn't find any so far. I suspected switching between users or switching to console could trigger it - but that's not true (at least it isn't reproducible). My workaround is to start the logout screen manually in konsole like this: /usr/lib/ksmserver-logout-greeter - STEPS TO REPRODUCE 1. Start logout via kicker 2. 3. OBSERVED RESULT nothing happens EXPECTED RESULT Logout screen should be started SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION I'm using sddm 0.19.0 and X11 if this should be relevant! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463148] New: Closing an app sometimes freezes complete plasmashell
https://bugs.kde.org/show_bug.cgi?id=463148 Bug ID: 463148 Summary: Closing an app sometimes freezes complete plasmashell Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andihartm...@freenet.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 If a program is closed (like libreoffice. keepassxc, ...) plasmashell sometimes freezes for 5 or 10 seconds. This means: The tasklist is dead e.g. (each click on an existing running program is ignored, you can't start any new program), context menu of desktop doesn't work either. After some time (5 or 10 s) it's suddenly working again as if nothing happened before. The tasklist is now updated. This problem is pretty old and not since today. It happens using X or Wayland - on AMD and nvidia GPUs. STEPS TO REPRODUCE 1. Start several programs 2. End a program 3. OBSERVED RESULT Sometimes (not always), plasmashell freezes. EXPECTED RESULT Plasmashell shouldn't freeze. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 (available in About System) KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463029] New: kwin_wayland and su - or: how to point $WAYLAND_DISPLAY to another location as the default?
https://bugs.kde.org/show_bug.cgi?id=463029
Bug ID: 463029
Summary: kwin_wayland and su - or: how to point
$WAYLAND_DISPLAY to another location as the default?
Classification: Plasma
Product: kwin
Version: 5.26.4
Platform: OpenSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: andihartm...@freenet.de
Target Milestone: ---
SUMMARY
***
To be able to run wayland apps in another user context (after su e.g.), the app
needs access to $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY.
To achieve access to $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY for the su user, the
directory rights of $XDG_RUNTIME_DIR must be changed to group rx to get access
to $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY for the su user (using chmod or setfacl).
If you do this, the log is spammed with entries like this:
[krunner|kioslave5|dolphin|plsamashell|ksmserver|kded|..] QStandardPaths: wrong
permissions on runtime directory /run/user/1000, 0750 instead of 0700
Setting a different $WAYLAND_DISPLAY like /tmp/${USER}_WAYLAND (in
/etc/profile.d/) does not work, because plasma wayland session afterwards won't
start at all (through sddm e.g.):
(from /.local/share/sddm/wayland-session.log)
--
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
---
How is it supposed to run wayland apps as another user without spamming the log
files?
***
STEPS TO REPRODUCE
1. export WAYLAND_DISPLAY=/tmp/${USER}_wayland in /etc/profile.d/wayland.sh
2. Start wayland session in sddm for the primary user
3.
OBSERVED RESULT
Wayland session doesn't start.
EXPECTED RESULT
Wayland session should start using wayland display /tmp/${USER}_wayland instead
of $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.26.4
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
--
You are receiving this mail because:
You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #32 from Andreas Hartmann --- I don't think there are so many Wayland users out there because Wayland has so many restrictions and bugs so far (and I don't see any solution). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #21 from Andreas Hartmann --- Same problem here with Plasma 5.26.3. Left click on an already running app (icon) in the taskbar opens a new instance of the app. This happens with each active program - not just one. Mouse over the program icon until the small preview of the program appears and clicking on this preview works as expected. As zellox wrote, clicking on the notification systray makes the problem disappear here, too. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #27 from Andreas Hartmann --- Same problem here with leap 15.4. Would be really nice to get it fixed ... . -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458417] Elisa doesn't recognize flac audio files, but can play them
https://bugs.kde.org/show_bug.cgi?id=458417 Andreas Hartmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Andreas Hartmann --- Today I started Elisa and it imported the files. I didn't change anything, will open a new issue if it occurs again. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458417] New: Elisa doesn't recognize flac audio files, but can play them
https://bugs.kde.org/show_bug.cgi?id=458417 Bug ID: 458417 Summary: Elisa doesn't recognize flac audio files, but can play them Product: Elisa Version: 22.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: andr...@ohok.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install Elisa on Arch KDE - by default it scans the correct director /home/user/Music which contains subfolders with .flac files 2. On the left, for example under albums, the files aren't listed 3. Scanning the mentioned subdirectories doesn't list them either 4. Directly opening the flac files plays them correctly, incl. album art OBSERVED RESULT Library doesn't contain flac files EXPECTED RESULT Library does contain flac files after scanning SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 81YM System Version: IdeaPad 5 14ARE05 ADDITIONAL INFORMATION I can't upload copyrighted test files, but I have reproduced this with a large number of flacs downloaded from bandcamp. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 454672] Missing logout and screen lock menu entries in desktop context menu
https://bugs.kde.org/show_bug.cgi?id=454672 --- Comment #3 from Andreas Hartmann --- Ok - got it meanwhile! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 454672] Missing logout and screen lock menu entries in desktop context menu
https://bugs.kde.org/show_bug.cgi?id=454672 --- Comment #2 from Andreas Hartmann --- (In reply to ratijas from comment #1) > However, somewhere there is an option to add them back. Right click on a > desktop, choose first option «Configure Desktop & Wallpaper», go to «Mouse > Actions» tab, and click configure button on the Right-Button / Standard Menu > row. There you will find your the checkboxes you are looking for. Thanks for your hint - but I can't find any checkbox to reenable it as you described it above. Maybe a screenshot could help? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 454672] New: Missing logout and screen lock menu entries in desktop context menu
https://bugs.kde.org/show_bug.cgi?id=454672 Bug ID: 454672 Summary: Missing logout and screen lock menu entries in desktop context menu Product: kdeplasma-addons Version: 5.24.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Switcher Assignee: plasma-b...@kde.org Reporter: andihartm...@freenet.de CC: m...@ratijas.tk Target Milestone: --- SUMMARY Since 5.24.90, the context menu you get clicking the right mouse button misses the entries screen lock and leave (instead of pressing CTRL-ALT-DEL or Meta-L). STEPS TO REPRODUCE 1. Search an empty space of the desktop 2. Click the right button of your mouse (context menu) 3. OBSERVED RESULT The menu you're now getting doesn't contain screen lock entry and leave any more. EXPECTED RESULT The menu should contain screen lock entry and leave. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Don't know if the product is the right one - probably not - you may fix it please. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 454671] New: krunner hangs after ALT-F2 and typing in the first letter - must be killed afterwards (wayland / nvidia)
https://bugs.kde.org/show_bug.cgi?id=454671 Bug ID: 454671 Summary: krunner hangs after ALT-F2 and typing in the first letter - must be killed afterwards (wayland / nvidia) Product: krunner Version: 5.24.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: andihartm...@freenet.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Enter ALT-F2 and type something, like konsole. After the first or second letter, krunner hangs. Killing makes it start again, but it will hang again after the first letter. Some time ago, the same problem has been fixed once before (see https://bugs.kde.org/show_bug.cgi?id=432062) STEPS TO REPRODUCE 1. Type ALT-F2 2. Type something to krunner, like konsole or xosview 3. krunner hangs OBSERVED RESULT krunner hangs EXPECTED RESULT krunner should render found results and should not hang. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.32 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 nvidia: 515.43.04 ADDITIONAL INFORMATION Not tested using wayland on non nvidia platform. Works fine using X11 (nvidia - non nvidia not tested) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454354] New: nvidia: Java programs running in Plasma Wayland / Xwayland show massive flickering
https://bugs.kde.org/show_bug.cgi?id=454354 Bug ID: 454354 Summary: nvidia: Java programs running in Plasma Wayland / Xwayland show massive flickering Product: kwin Version: 5.24.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland-nested Assignee: kwin-bugs-n...@kde.org Reporter: andihartm...@freenet.de Target Milestone: --- SUMMARY Running java apps in Plasma Wayland / X-Wayland leads to massive flickering of the Java apps or even QT apps. STEPS TO REPRODUCE 1. Take Mediathekview and run it. Do several actions like Blacklisting of films. After blacklisting a few films, you most probably will get massive flickering. 2. Take a look at https://forums.developer.nvidia.com/t/wayland-massive-flickering-on-xwayland-java/215224 and https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317 (search for "nvidia user01"). You can find an example here: https://magentacloud.de/s/LybHRSF4YjD9brs 3. OBSERVED RESULT Massive flickering after some time of operation (maybe 2 minutes). EXPECTED RESULT No flickering at all. Just as it works in Wayland gnome shell. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.32 / 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Nvidia: 515.43.04 and previous versions -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 453171] New: Option for account deletion
https://bugs.kde.org/show_bug.cgi?id=453171 Bug ID: 453171 Summary: Option for account deletion Product: bugs.kde.org Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: ahartm...@7x.de CC: she...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** This is sort of a formal request that you delete my account from this website, please. I do not want to have this account any longer, but for lack of a proper *Delete my Account* button (at least I didn't find one), I open this ticket instead. STEPS TO REPRODUCE 1. Login to bugs.kde.org 2. Look around the few buttons and pages the site offers OBSERVED RESULT There is no "Delete my Account" button EXPECTED RESULT There should be some "Delete my Account" button, maybe at the bottom of this page or elsewhere. At least a hint whom to turn to for this occasion so one doesn't have to open tickets to request account deletion. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 452214] Printer applet broken. PopupDialog unavailable
https://bugs.kde.org/show_bug.cgi?id=452214 --- Comment #1 from Andreas Hartmann --- SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452217] Tapping inactive in kcm_touchpad.
https://bugs.kde.org/show_bug.cgi?id=452217 --- Comment #3 from Andreas Hartmann --- Created attachment 147928 --> https://bugs.kde.org/attachment.cgi?id=147928=edit tapping options active while using LANG=C on konsole -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452217] Tapping inactive in kcm_touchpad.
https://bugs.kde.org/show_bug.cgi?id=452217 --- Comment #2 from Andreas Hartmann --- Created attachment 147927 --> https://bugs.kde.org/attachment.cgi?id=147927=edit tapping options partly active after all following starts on konsole -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452217] Tapping inactive in kcm_touchpad.
https://bugs.kde.org/show_bug.cgi?id=452217 --- Comment #1 from Andreas Hartmann --- Created attachment 147926 --> https://bugs.kde.org/attachment.cgi?id=147926=edit tapping option active after second start. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452217] New: Tapping inactive in kcm_touchpad.
https://bugs.kde.org/show_bug.cgi?id=452217 Bug ID: 452217 Summary: Tapping inactive in kcm_touchpad. Product: systemsettings Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: andihartm...@freenet.de Target Milestone: --- Created attachment 147925 --> https://bugs.kde.org/attachment.cgi?id=147925=edit all tapping options inactive (regardless how often it's started from start menu). SUMMARY Tapping options are most of the time inactive when starting systemsettings / touchpad configuration. The problem could be seen (long?) before 5.24.4. STEPS TO REPRODUCE 1. Start systemsettings from the start menu. 2. Go to touchpad configuration 3. OBSERVED RESULT Tapping options are disabled EXPECTED RESULT Tapping options should be enabled. Further investigation: Started kcm_touchpad from konsole. After the first startup, the result is the same as described above. Starting it twice (after the first run has been closed), suddenly parts of the tapping options are active. Closing it and starting it again reveals the same problem as it could be seen from beginning: all tapping options are inactive. This behavior is stable from now on - even after the n.th start. Next try: Starting kcm_touchpad in the konsole, but changing the LANG variable: export LANG=C => now it's working as expected. Usual LANG configuration here is: ~> locale LANG=de_DE.UTF-8 LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= I attached some screenshots as example: touchpad-tapping-inactive-1 => all tapping options inactive (regardless how often it's started from start menu). touchpad-tapping-active-after-second-start => all tapping options active on second start on konsole touchpad-tapping-partly-active => tapping options partly active after all following starts on konsole touchpad-tapping-active-LANG=C => tapping options active while using LANG=C on konsole SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 452214] New: Printer applet broken. PopupDialog unavailable
https://bugs.kde.org/show_bug.cgi?id=452214 Bug ID: 452214 Summary: Printer applet broken. PopupDialog unavailable Product: print-manager Version: 22.03.80 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: dantt...@gmail.com Reporter: andihartm...@freenet.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 147923 --> https://bugs.kde.org/attachment.cgi?id=147923=edit Screenshot of the error message of printer applet SUMMARY Printmanager does not work. It states: An error occurred while loading printer. Further messages are: file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/printmanager.qml:56:34: Type PopupDialog unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:61:24: PlasmaExtras.Highlight is not a type STEPS TO REPRODUCE 1. Start Plasma / X11 (Wayland not tested) 2. Click on the printer icon on the right side in the tray 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 Andreas Hartmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Andreas Hartmann --- The proposed patch fixes the problem of not activated apply button for me. I tested against 5.24.2. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 --- Comment #8 from Andreas Hartmann --- I already tested the "konsole" workaround you described - doesn't work here either. Anyway I sometimes could see differences between start via konsole and start via icon in start menu: the two radio options for 2 finger tipping (right click or middle click) are often disabled when starting from start menu - after it has been started via konsole, they are active. If started from konsole, I'm getting the following debug output: ~> systemsettings kcm_touchpad kf.configwidgets: A widget named ' "kcfg_osdKbdLayoutChangedEnabled" ' was found but there is no setting named ' "osdKbdLayoutChangedEnabled" ' kf.configwidgets: A widget named ' "kcfg_repeatRate" ' was found but there is no setting named ' "repeatRate" ' kf.configwidgets: A widget named ' "kcfg_repeatDelay" ' was found but there is no setting named ' "repeatDelay" ' kf.configwidgets: A widget named ' "kcfg_resetOldXkbOptions" ' was found but there is no setting named ' "resetOldXkbOptions" ' kf.configwidgets: A widget named ' "kcfg_configureLayouts" ' was found but there is no setting named ' "configureLayouts" ' kf.configwidgets: A widget named ' "kcfg_repeatRate" ' was found but there is no setting named ' "repeatRate" ' kf.configwidgets: A widget named ' "kcfg_repeatDelay" ' was found but there is no setting named ' "repeatDelay" ' kcm_touchpad: Using X11 backend qml: Touchpad configuration of device '1 : ELAN1200:00 04F3:30BA Touchpad' opened file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:283:9: QML QQuickItem* (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredWidth" qrc:/libinput/touchpad.qml:108:5: QML FormLayout: Binding loop detected for property "implicitHeight" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 --- Comment #6 from Andreas Hartmann --- Maybe you could provide some debug output to the source code to narrow down, where the problem happens? I'm able to recompile https://ftp.lysator.liu.se/pub/opensuse/repositories/KDE:/Frameworks5/openSUSE_Leap_15.3/src/plasma5-desktop-5.24.0-lp153.504.2.src.rpm and may add the debug output before ... . -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 --- Comment #5 from Andreas Hartmann --- Doesn't work with Wayland, either (regardless if amd or nvidia). BTW: I even tested with a fresh account (no existing historic configuration before - same problem). Can you say how to debug the problem? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 --- Comment #1 from Andreas Hartmann --- Reverting to 5.23.5 makes it working again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449843] New: Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode)
https://bugs.kde.org/show_bug.cgi?id=449843 Bug ID: 449843 Summary: Can't save any configuration any more because "Apply" button isn't activated after changing anything (X11 mode) Product: systemsettings Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: andihartm...@freenet.de Target Milestone: --- SUMMARY It's impossible to save any change in system configuration -> touchpad configuration, because the "Apply" button isn't activated. STEPS TO REPRODUCE 1. Start systemsettings 2. Go to Hardware -> Input devices 3. Go to Touchpad 4. Use first tab and change 2 finger mode to middle mouse key. 5. You could try to change any other parameter in any other tab. The apply button never gets activated. OBSERVED RESULT Apply button is not activated EXPECTED RESULT Apply button must be activated SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 Andreas Hartmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #22 from Andreas Hartmann --- Middle-click-paste problem disappeared after switching from libgtk-3-0-3.24.20 to 3.24.30. Now other problems appear: smplayer / mpv doesn't work, because of the --wid option provided by smplayer to mpv (mpv itself works on wayland). Switching to vlc showed one more problem: KDE / Plasma ignores ~/.bashrc and ~/.profile and /etc/profile.d/ ... . Why are you ignoring those basic configuration files? It's a pain to provide standard environment variables like http_proxy e.g. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #19 from Andreas Hartmann --- The konsole and mc problem happens after the profile is changed. You have to restart konsole to make it work again. This happens too in X-mode. On nvidia there is a problem when starting system settings. If you go into any settings module, the system settings window is completely broken. You have to resize it, to get it working again. Afterwards, it's working fine - even after changing the different modules. Middle-click-paste in wayland mode in FF still only works within FF (after doing a middle-click-paste-action in kwrite e.g.). Don't you have any clue about the reason and how to debug it? BTW, this happens with FF esr an actual version. Middle-click-paste between X and Wayland applications seems to be possible - if FF runs in X mode (meanwhile I found a way to force FF to use X under wayland), middle-click-paste between different apps is working fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #18 from Andreas Hartmann --- ok, spoke too soon. Konsole and CTRL-S in conjunction with mc is still broken - sometimes it's working - most of the time not. I can't see any logic behind this behavior - it's just random. To be clear: CTRL-S is caught by the konsole and data flow control is activated - which is wrong. CTRL-S should be given to mc as shortcut for searching. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #17 from Andreas Hartmann --- Some time ago, they dropped the "bad" variant. I can see only the full variant. Today, I got a few updates: plasma5-workspace-lang-5.22.90-lp152.623.1.noarch Mi 22 Sep 2021 18:46:09 CEST plasma5-workspace-5.22.90-lp152.623.1.x86_64 Mi 22 Sep 2021 18:46:06 CEST xembedsniproxy-5.22.90-lp152.623.1.x86_64 Mi 22 Sep 2021 18:46:05 CEST plasma5-workspace-libs-5.22.90-lp152.623.1.x86_64 Mi 22 Sep 2021 18:46:05 CEST konversation-lang-21.08.1-lp152.35.1.noarch Mi 22 Sep 2021 18:46:05 CEST gmenudbusmenuproxy-5.22.90-lp152.623.1.x86_64 Mi 22 Sep 2021 18:46:05 CEST libkolabxml1-1.1.6-lp152.54.53.x86_64 Mi 22 Sep 2021 18:46:04 CEST libva-gl-devel-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:03 CEST libva-devel-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:03 CEST konversation-21.08.1-lp152.35.1.x86_64Mi 22 Sep 2021 18:46:03 CEST libva-x11-2-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:02 CEST libva-wayland2-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:02 CEST libva-glx2-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:02 CEST libva-drm2-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:46:02 CEST libva2-2.13.0-lp152.150.1.x86_64 Mi 22 Sep 2021 18:45:59 CEST The problem w/ mc in konsole has gone - it's working now as expected. But kwin_wayland though is unstable (AMD GPU). To the FF middle click-problem: It's impossible to get data from FF to KDE and vice versa. Further more: middle click paste only works in FF, if you did it once before in kwrite e.g. Data copied in FF can't be seen in clipboard at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #15 from Andreas Hartmann --- I'm doing it as described in the initial bug description: - Start FF - mark a text in FF by doubleclick or by normal marking with the mouse - going to kate, konsole or kwrite - as you like - do middle click => doesn't work (nothing is inserted or the old data, which is there from previously copied data to the clipboard). Btw: FF runs in Wayland mode - how can I force FF to run in X-mode? Problem can't be seen w/ chromium - chromium runs in X mode. I detected one more massive bug with Wayland - now in konsole: Using mc (midnight commander) is mostly impossible, because konsole or whatever intercepts all CTRL-shortcuts like CTRL-S, ... . This doesn't happen in X-mode. Wayland is a pure catastrophe - sorry to say. Yes, you're right, I shouldn't mix up bugs in one ticket. But you may understand, that I'm pretty annoyed because there are countless bugs. Everywhere I'm looking at - basic things are broken / don't work. Not that I'm searching for. I just want to do usual 0815 things and can't do it. This software is very far from alpha state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #13 from Andreas Hartmann --- Maybe the leap packages aren't completely on beta at the moment? But plasma5-desktop-5.22.90-lp152.492.1.x86_64 seems to be 5.23 beta? I can't say ... . -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #12 from Andreas Hartmann --- Ok - tested with leap 15.2 and plasma-framework-5.86.0-lp152.337.1.x86_64 - shouldn't this be 5.23 beta? Still doesn't work here. Unchanged behavior (Firefox runs in wayland mode - xlsclient doesn't show firefox). Another very bad thing: kwin_wayland / compositor is deactivated using nvidia 470.63. Firefox in wayland / nvidia is mostly completely unusable (run youtube video fullscreen and go back - it's awful slow and firefox window and desktop is horribly broken). AMD GPU The tests with AMD GPU are slightly better but far from being usable, too. The actual problem mentioned here isn't fixed, too. wayland and sddm is broken completely - you can't end a wayland session at all - sddm isn't working any more. After reboot, you have to switch to gdm - now it's working. Running FF youtube full screen video: try start another program like xosview using ALT-F2. It's awful slow and temporary hangs the complete screen. Unusable. Touchpad configuration in wayland is absolutely broken, too - it's impossible to change mouse speed. It's awful slow. Compositing is disabled (like on nvidia, too), because it crashed. Transparent windows now are disabled per default (even using X - why that? I had to enable it manually again). There are still so many bugs around wayland that it's massively frustrating - regardless AMD GPU or nvidia GPU. Thank god, Xorg still works fine. Wayland is very far from being usable. No runas and no network transparency e.g. are still criteria for exclusion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #10 from Andreas Hartmann --- I don't have the possibility to install plasma git - therefore please don't wait for test results. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440808] "Run as" does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=440808 --- Comment #2 from Andreas Hartmann --- "One cannot run apps as another user on wayland." You are joking, aren't you? Even Windows is able to run programs as different users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440808] New: "Run as" does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=440808 Bug ID: 440808 Summary: "Run as" does not work using Wayland Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: andihartm...@freenet.de CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Try to start e.g. konsole with a different user compared to the actual active one. STEPS TO REPRODUCE 1. Go to the extended properties to configure a different user to run konsole as. 2. Save the changes (different user) 3. Start the program. You are asked for the password of the new user. 4. After confirmation, nothing happens OBSERVED RESULT nothing happens EXPECTED RESULT konsole is started in another user kontext SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: Qt 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 Andreas Hartmann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #5 from Andreas Hartmann --- Created attachment 140618 --> https://bugs.kde.org/attachment.cgi?id=140618=edit logoutput for middle-click-paste in FF It's only possible to middle-click-paste content which has been marked before in FF. BTW: Firefox and Thunderbird are pretty broken (after resume from S2RAM?). Broken means: both are flickering if a menu is opened and you want to scroll through the menu with the mouse or the arrow keys. There are other problems, too, regarding graphic. It's pretty unusable. GPU is AMD Picasso (rev c1) - Ryzen 7 3750H with Radeon Vega Mobile Gfx. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #3 from Andreas Hartmann --- middle-click-paste in Thunderbird (78.11.0) doesn't work at all (wayland native). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #2 from Andreas Hartmann --- For me, it's impossible, too, to middle-click-paste into Firefox from other apps, like kwrite. It only works within FF itself. One more strange thing I just realized: middle-click-paste actually works in Firefox only, if I used it once before in KDE app (like kwrite). Clipper doesn't realize middle-click-paste at all. I tested with one finger double tap to mark a word and two finger tap to insert it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 Andreas Hartmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 --- Comment #11 from Andreas Hartmann --- I have to apologize! Got it working via UI after installing an actual libinput (1.18.1). Thanks for your hints! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 --- Comment #9 from Andreas Hartmann --- Created attachment 140572 --> https://bugs.kde.org/attachment.cgi?id=140572=edit The attached patch enables one finger tapping in libinput (here 1.10.5). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 --- Comment #7 from Andreas Hartmann --- "You would need to ask the developers to implement that feature" This should be referred to adding a config file? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] New: copy paste by mark / middle click does not work in wayland
https://bugs.kde.org/show_bug.cgi?id=440703 Bug ID: 440703 Summary: copy paste by mark / middle click does not work in wayland Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: andihartm...@freenet.de Target Milestone: 1.0 It's impossible to copy e.g. text from konsole or Firefox by marking it and adding it to another tool, like kate e.g. This is a serious bug and a show stopper ever using Wayland. STEPS TO REPRODUCE 1. Mark some text in Firefox or konsole e.g. (w/o CTRL-C) 2. Try to add it in kate by middleclick 3. The marked text can't even be seen in the clipboard OBSERVED RESULT Can't copy paste by just marking a text and pasting it with middle mouse click. EXPECTED RESULT I'm expecting the default X behavior in Wayland SOFTWARE/OS VERSIONS Linux/KDE Plasma: Leap 15.2 / Linux 5.10.52 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #5 from Andreas Hartmann --- It's impossible to activate "tap to click" using one finger and double click with two fingers (5.22.4). How can I configure this in a config file like in X? I'm really wondering why even basics just don't work in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 --- Comment #11 from Andreas Hartmann --- The workaround fixes some other, similar problems w/ other plasma / KDE programs, like the application menu, e.g., too. But that's anyway not enough to use it, because other programs, like Firefox e.g., don't work, too (ESR and actual version). You have to force them to run in Xwayland - but there are problems with the clipboard (you always have to CTRL-C to copy to clipboard - that's annoying). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437593] Spectacle / Wayland: rectangle snapshots not working
https://bugs.kde.org/show_bug.cgi?id=437593 --- Comment #3 from Andreas Hartmann --- Another hint: using gdm as loginmanager makes the problem completely disappear. It's anyway the better solution as gdm doesn't need a running X server any more (it's pure Wayland). The parallel running X server leads to a hanging system if you're logging out (ok - other problem - at least on Leap 15.2 actually). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 --- Comment #4 from Andreas Hartmann --- Problem disappears if krunner is started with -platform xcb -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 Andreas Hartmann changed: What|Removed |Added Component|wayland-generic |general Product|kwin|krunner Assignee|kwin-bugs-n...@kde.org |alexander.loh...@gmx.de Version|5.20.5 |5.21.90 CC||plasma-b...@kde.org --- Comment #3 from Andreas Hartmann --- Changed product to krunner -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437593] Spectacle / Wayland: rectangle snapshots not working
https://bugs.kde.org/show_bug.cgi?id=437593 Andreas Hartmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Andreas Hartmann --- You're right - the problem disappeared with your option -platform wayland. Yes, I'm using openSuSE, but it's Leap 15.2 using the additional actual KDE repository and QT repository. And yes, it's the mode "Wayland" - and not "Full Wayland". -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437593] New: Spectacle / Wayland: rectangle snapshots not working
https://bugs.kde.org/show_bug.cgi?id=437593 Bug ID: 437593 Summary: Spectacle / Wayland: rectangle snapshots not working Product: Spectacle Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: andihartm...@freenet.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Using Wayland, it's impossible to do a rectangle snapshot. STEPS TO REPRODUCE 1. Start konsole 2. Start spectacle 3. Set capture mode to rectangular region 4. Take a new snapshot OBSERVED RESULT Snapshot doesn't work. EXPECTED RESULT Should work same as with X11. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 ADDITIONAL INFORMATION The following error occurs in shell: kf.service.services: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line kf.service.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found: XWAYLAND0" GPU is AMD and used kernel is 5.10.39. It's on a Notebook - only the internal notebook screen is connected and active - no other screen involved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 --- Comment #2 from Andreas Hartmann --- Should say additionally, that krunner hangs and must be killed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #1 from Andreas Hartmann --- Exactly same problem here. When starting krunner on the konsole, you can see the following output: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() It's on Leap 15.2 using actual KDE / X packages: plasma5-workspace 5.21.90 nvidia 460.80 kwayland-5.82.0-lp152.228.2.x86_64 libqt5-qtwayland-5.15.2-lp152.5.1.x86_64 xwayland-21.1.1-lp152.4.3.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430710] Defining key shortcuts has stopped working
https://bugs.kde.org/show_bug.cgi?id=430710 --- Comment #9 from Andreas Hartmann --- The fix mentioned here https://bugs.kde.org/show_bug.cgi?id=430388 works for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430710] Defining key shortcuts has stopped working
https://bugs.kde.org/show_bug.cgi?id=430710 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #1 from Andreas Hartmann --- Exactly same problem here. Should really be fixed ASAP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #34 from Andreas Hartmann --- Good point regarding KWIN_DRM_USE_EGL_STREAMS: If KWIN_DRM_USE_EGL_STREAMS is set, the following crash disappeared: "The complete session crashes (plasmashell?) if there are e.g. two konsole programs running and you're pointing to the preview of each window in the taskbar." => so this seems to be a software renderer problem. The problem with black screens doesn't disappear using KWIN_DRM_USE_EGL_STREAMS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428088] Restarting compositing breaks the EGLDevice backend
https://bugs.kde.org/show_bug.cgi?id=428088 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #31 from Andreas Hartmann --- Meanwhile I was able to start a wayland plasmashell via sddm (weston doesn't work yet). I did another update of the KDE packages - after this update, the wayland plasmashell is now "working": The versions I'm using at the moment: Framework 5.20.2 QT: 5.15.1 Nvidia: 450.80 SDDM: 0.18.1 It's even not necessary to use the environment variable KWIN_DRM_USE_EGL_STREAMS. But: It's massively unstable: Starting another session or switching to a console (CTRL-ALT-Fx) breaks the previous session - when coming back, the screen is black again. I have to kill it completely with killall -u user. Next problem: krunner is broken - crashes massively. More problems: The complete session crashes (plasmashell?) if there are e.g. two konsole programs are running and you're pointing to the preview of each window in the taskbar. If the theme is changed, the plasmashell crashes, too. => All in all: pretty unusable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 Andreas Hartmann changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #30 from Andreas Hartmann --- I've got black screen and a frozen mouse cursor in the middle of the screen, two, with plasma 5.20.2 / qt 5.15.1. No Optimus system. It's just an easy discrete card (GeForce GT 1030). I tried using weston (it's much more easy) - but the same problem. Screen stays black. Using kwin_wayland or weston in a running X11 KDE session works just fine. Yes, I used the description here: http://blog.davidedmundson.co.uk/blog/running-kwin-wayland-on-nvidia/ On an Ryzen 7 AMD internal VGA device, kwin_wayland is running (but it's not really usable). I couldn't find any usable way of debugging the problem. Maybe here is a person which is interested to find the problem by providing ways to debug the problem? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 420605] New: Neon apt repository contains broken dependencies, update will cause desktop to be uninstalled
https://bugs.kde.org/show_bug.cgi?id=420605 Bug ID: 420605 Summary: Neon apt repository contains broken dependencies, update will cause desktop to be uninstalled Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: andr...@ohok.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Updating KDE neon will remove entire desktop Yesterday I updated my neon user edition with sudo apt dist-upgrade. I should've used pkcon, but it looks like that didn't cause my problem. I noticed too late that the update was going to uninstall everything, and now I can no longer reinstall the neon-desktop package because of dependency issues. I tracked it down to several packages depending on libqt5qml5 5.14.2 or higher, but the version to be installed is 5.14.2-0xneon+18.04+bionic+build56 which somehow doesn't satisfy that dependency? For example I can't install qml-module-qtquick-control because of that, but I need it to get my desktop back. In my sources list I am only using the default bionic repos and archive.neon.org/release bionic main. The issue has been confirmed by another user on reddit: https://www.reddit.com/r/kdeneon/comments/g7xp1r/update_uninstalled_entire_desktop_can_not/?utm_source=share_medium=ios_app_name=iossmf STEPS TO REPRODUCE 1. Update KDE neon from an existing install with the repos mentioned above. OBSERVED RESULT The entire desktop will be uninstalled and can no longer be reinstalled due to incorrect dependencies. EXPECTED RESULT The update works correctly, it is possible to install neon-desktop etc. SOFTWARE/OS VERSION: Linux/KDE Plasma: neon user latest ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400486] Display keyboard shortcut for switching Input modes
https://bugs.kde.org/show_bug.cgi?id=400486 Andreas Hartmann changed: What|Removed |Added CC||ahartm...@7x.de --- Comment #5 from Andreas Hartmann --- I am completely new to KDE and found this Junior Job. I'd like to know: Is somebody still working on this? Because if not I'd really like to do it. I have looked into the issue and don't really know how to solve it. Looking at the way the other options are implemented, they either have a selector (like the **Input Mode** Option discussed here) *OR* a checkbox with the Keyboard-Shortcut shown to the right of the options text. None of the "selectable" options have a keyboard shortcut shown in their respective entry. Should I go ahead and make the *Input Mode* Option a toggle option like e.g. *Block Selection Mode*? I'm asking because the source code reads as if the current behavior on *Input Mode* was intentional to the extent that further input modes be added (some day in the future), which would be incompatible with the "toggle" option. Any advice, anyone? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 --- Comment #78 from Andreas Hartmann <andihartm...@freenet.de> --- (In reply to Bernhard Übelacker from comment #66) > After the latest updates in Debian Testing I am not able to > reproduce the crash anymore by switching from Breeze to Plastik decorations. > > The updates contained mostly Qt from 5.6.1 to 5.7.1~20161021. > And some packages libkf5* and kwin* got just rebuilt at the same version. Leap 42.2: I switched to the QT5.7 / Frameworks5 repository and I couldn't see the problem any more, too. But therefore, I got a lot of other problems / crashes (e.g. with systemsettings5 and the desktop itself being suddenly completely black). Therefore I decided to switch back to original packages again and to use Breeze which works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #3 from Andreas Hartmann <andihartm...@freenet.de> --- Created attachment 102849 --> https://bugs.kde.org/attachment.cgi?id=102849=edit Hardware description and kwin options -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #2 from Andreas Hartmann <andihartm...@freenet.de> --- Created attachment 102848 --> https://bugs.kde.org/attachment.cgi?id=102848=edit example 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 --- Comment #1 from Andreas Hartmann <andihartm...@freenet.de> --- Created attachment 102847 --> https://bugs.kde.org/attachment.cgi?id=102847=edit example 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373800] New: Frequent kwin crashes
https://bugs.kde.org/show_bug.cgi?id=373800 Bug ID: 373800 Summary: Frequent kwin crashes Product: kwin Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andihartm...@freenet.de Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.38-1-desktop x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I did nothing particular. But I can see it most of the time at the beginning of a session. Afterwards it is working mostly for longer time. But comes up again. There are two more crashes from yesterday. Maybe, it is related to starting new programms? I could see it while starting the process list (CTRL-ESC) or Firefox, e.g.. But this is just an assumption. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f84dec5b940 (LWP 3481))] Thread 6 (Thread 0x7f84b2ffe700 (LWP 3749)): #0 0x7f84dba841f9 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #1 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f84d64089b8 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #7 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f84a1bca700 (LWP 3614)): #0 0x7f84de6990af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f84da9f793b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f84da9f7969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f84a2dd3700 (LWP 3609)): #0 0x7f84de6990af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f84b2186533 in () at /usr/lib64/dri/r600_dri.so #2 0x7f84b2185d57 in () at /usr/lib64/dri/r600_dri.so #3 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f84b3fff700 (LWP 3592)): #0 0x7f84de3c6b03 in select () at /lib64/libc.so.6 #1 0x7f84dba82849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba840c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f84d64089b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f84c31fb700 (LWP 3516)): #0 0x7f84de3c6b03 in select () at /lib64/libc.so.6 #1 0x7f84dba82849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f84dba840c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f84dba84527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f84dba33fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f84db86ef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f84d55db1d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f84db8739e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f84de694734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f84de3cdd3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f84dec5b940 (LWP 3481)): [KCrash Handler] #6 0x7f84d63f4dd0 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #7 0x7f84d63f624a in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f84d63ff2f6 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f84d638d93b in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f84d638d9f7 in QQmlComponentPrivate::completeCreate() () at
[kwin] [Bug 347548] Kwin i965 crash on external display connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=347548 Andreas Hartmann <m...@andreashartmann.eu> changed: What|Removed |Added CC||m...@andreashartmann.eu -- You are receiving this mail because: You are watching all bug changes.
