[gwenview] [Bug 146811] Wish: Cut and Paste in context menu for files and folders
https://bugs.kde.org/show_bug.cgi?id=146811 --- Comment #2 from Jürgen Scholz --- I am indeed talking about Gwenview. For sorting photos it would be incredibly helpful to be able to cut and paste photos in Gwenview. Even better would be to be able to cut them in Gwenview and paste them with Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable
https://bugs.kde.org/show_bug.cgi?id=343369 Jürgen Scholz changed: What|Removed |Added CC||juergen.scholz...@gmail.com --- Comment #23 from Jürgen Scholz --- agdsgfds -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable
https://bugs.kde.org/show_bug.cgi?id=343369 --- Comment #24 from Jürgen Scholz --- I am sorry for my previous message. I just wanted to add me to the CC list and before doing that I played around with the text color in the comment box. I have the same issue with plasma 5.5.4 and ubuntu 15.10 with the kubuntu backports ppa; selecting the Breeze Dark color scheme makes combo boxes drawn by plasma shell hardly readable. For example in the desktop settings dialog where one can select the scaling mode of the background picture. - As already shown in https://bugs.kde.org/attachment.cgi?id=94386 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] New: plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 Bug ID: 358245 Summary: plasmashell unresponsive/freezes after resuming from suspend to RAM Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: juergen.scholz...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org I am using ubuntu 15.10/wily with the kubuntu backports PPA, which at the moment provides plasmashell 5.5.3. Every time I resume my computer from suspend to RAM plasmashell freezes and does not react to any input. At the same time krunner is working fine and I can start applications or use already open ones normally. The situation can be resolved by issuing killall plasmashell; plasmashell in krunner. Additionally the mouse cursor is reacting with a lot of jitter to mouse movements, until a notification that eth0 has been re-connected appears. Sometimes there is a notification that eth0 has gone down (probably a delayed notification from the suspend process). I created a back trace with gdb - I hope the information necessary to diagnose the problem is in there. If not, I am happy to provide additional details on request. Reproducible: Always Steps to Reproduce: 1. Start KDE session. 2. Suspend machine to RAM. 3. Resume machine. Actual Results: Plasmashell does not react to input. Applications and krunner work. Expected Results: Plasmashell does react to inputs. Applications and krunner work. There is a similar bug report for version 5.4.0, which also showed this behavior on my machine. Please see https://bugs.kde.org/show_bug.cgi?id=352337 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 --- Comment #1 from Jürgen Scholz --- Created attachment 96749 --> https://bugs.kde.org/attachment.cgi?id=96749&action=edit Back trace of plasmashell 5.5.3 freeze after resume -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 337674] kded5 is eating CPU
https://bugs.kde.org/show_bug.cgi?id=337674 Jürgen Scholz changed: What|Removed |Added CC|juergen.scholz...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 --- Comment #2 from Jürgen Scholz --- I am investigating the influence of redshift and and the Redshift Control plasma widget. It seems I can resume my system, when I use the plasmoid to turn redshift off before I suspend the system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 --- Comment #3 from Jürgen Scholz --- After further testing I found, that the presence of redshift does not change the behavior of plasmashell on resume (at least on my machine). There seems to be a possibility to circumvent the crash I am experiencing: 1. Log in normally on boot (Terminal 7) 2. Use the session manager (krunner -> sessions) to create a second session for another user 3. Log in on second session (Terminal 8) and stay on that terminal 4. Suspend system 5. Resume system 6. Switch from Terminal 8 to Terminal 7 with the original session and find the screen locked and plasmashell not crashed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 Jürgen Scholz changed: What|Removed |Added Attachment #96749|0 |1 is obsolete|| --- Comment #4 from Jürgen Scholz --- Created attachment 97085 --> https://bugs.kde.org/attachment.cgi?id=97085&action=edit 20160208: plasmashell back trace This is a more recent back trace of a frozen plasmashell process with most of the debugging symbols loaded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 --- Comment #5 from Jürgen Scholz --- Created attachment 97086 --> https://bugs.kde.org/attachment.cgi?id=97086&action=edit 20160208: Frozen kwin_x11 process back trace This is the backtrace of the kwin_x11 process which handled the screen before the system was suspended. It used 100% CPU and killing it did not get plasmashell back on track. A new kwin_x11 process was spawned and handled the output correctly (applications working, plasmashell still frozen). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359465] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=359465 --- Comment #1 from Jürgen Scholz --- Created attachment 97247 --> https://bugs.kde.org/attachment.cgi?id=97247&action=edit Back trace of plasmashell 5.5.3 freeze after resume -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359465] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=359465 --- Comment #2 from Jürgen Scholz --- Created attachment 97248 --> https://bugs.kde.org/attachment.cgi?id=97248&action=edit Backtrace of kwin_x11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359465] New: plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=359465 Bug ID: 359465 Summary: plasmashell unresponsive/freezes after resuming from suspend to RAM Product: kwin Version: 5.5.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: juergen.scholz...@gmail.com I am using ubuntu 15.10/wily with the kubuntu backports PPA, which at the moment provides plasmashell 5.5.3. Every time I resume my computer from suspend to RAM plasmashell freezes and does not react to any input. At the same time krunner is working fine and I can start applications or use already open ones normally. The situation can be resolved by issuing killall plasmashell; plasmashell in krunner. Additionally the mouse cursor is reacting with a lot of jitter to mouse movements, until a notification that eth0 has been re-connected appears. Sometimes there is a notification that eth0 has gone down (probably a delayed notification from the suspend process). Thomas Lübking noted that this behaviour is caused by a deadlock between kwin and plasmashell. Please see https://bugs.kde.org/show_bug.cgi?id=358245#c6 for details. I will attach the backtraces. Reproducible: Always Steps to Reproduce: 1. Start KDE session. 2. Suspend machine to RAM. 3. Resume machine. There seems to be a possibility to circumvent the crash: 1. Log in normally on boot (Terminal 7) 2. Use the session manager (krunner -> sessions) to create a second session for another user 3. Log in on second session (Terminal 8) and stay on that terminal 4. Suspend system 5. Resume system 6. Switch from Terminal 8 to Terminal 7 with the original session and find the screen locked and plasmashell not crashed. Actual Results: kwin/Plasmashell does not react to input. Applications and krunner work. Expected Results: kwin/Plasmashell does react to inputs. Applications and krunner work. Possibly related bugs: https://bugs.kde.org/show_bug.cgi?id=352423 https://bugs.kde.org/show_bug.cgi?id=355457 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 Jürgen Scholz changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #7 from Jürgen Scholz --- Thomas; thank you for your analysis. It is common to compress the logs for mesa bugs - here I will not do it again. I opened a bug against kwin: https://bugs.kde.org/show_bug.cgi?id=359465 -- You are receiving this mail because: You are watching all bug changes.
