[opensuse] Other problems with 42.2
I've come across a couple of other problems with 42. One, the list of open windows, either the horizontal row of thumbnails or vertical list will open and I can't clear it. The other is clicking on the task bar has no effect. These, along with the locking desktop make 42.2 a pain to use. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 01:19 PM, James Knott wrote:
I've come across a couple of other problems with 42. One, the list of open windows, either the horizontal row of thumbnails or vertical list will open and I can't clear it. The other is clicking on the task bar has no effect. These, along with the locking desktop make 42.2 a pain to use.
Its not enough to tell us you run running 42. You have to tell us which desktop you have selected. List of open windows? WTF? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 04:40 PM, John Andersen wrote:
On 03/20/2017 01:19 PM, James Knott wrote:
I've come across a couple of other problems with 42. One, the list of open windows, either the horizontal row of thumbnails or vertical list will open and I can't clear it. The other is clicking on the task bar has no effect. These, along with the locking desktop make 42.2 a pain to use. Its not enough to tell us you run running 42. You have to tell us which desktop you have selected.
List of open windows? WTF?
KDE. I often have several apps open. I normally can click on the app on the task bar to open up a list of windows for that app. This is what fails. I either have one of the 2 methods of listing open windows displayed and cannot move beyond that or I can't even get the list, by clicking on the task bar. When this happens, I can't even open new apps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 02:04 PM, James Knott wrote:
On 03/20/2017 04:40 PM, John Andersen wrote:
On 03/20/2017 01:19 PM, James Knott wrote:
I've come across a couple of other problems with 42. One, the list of open windows, either the horizontal row of thumbnails or vertical list will open and I can't clear it. The other is clicking on the task bar has no effect. These, along with the locking desktop make 42.2 a pain to use. Its not enough to tell us you run running 42. You have to tell us which desktop you have selected.
List of open windows? WTF?
KDE.
I often have several apps open. I normally can click on the app on the task bar to open up a list of windows for that app. This is what fails. I either have one of the 2 methods of listing open windows displayed and cannot move beyond that or I can't even get the list, by clicking on the task bar. When this happens, I can't even open new apps.
Have you right clicked the task bar and played around with the settings for the Task manager? I'm not having this problem. I have "Only group when task manager is full" UNCHECKED and all the windows from say Thunderbird are grouped with a little green Plus sign cricle to let me know there are multiple. If I hover over it, I will see thumbnails pop up, and can select the one I want. If I click the Tbird taskbar item, I will see a list, and again I can click the one I want. The scroll wheel will step through all the windows for the app I clicked or hovered over. Moving the mouse out of that task area causes the list or the thumbnails go go away. Notice also that you can control the locking interval (or turn it off) in the kde settings. Quite frankly, this version of KDE5/Plasma is one of the best versions I've seen in a while, regardless of the underlying OS. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 05:33 PM, John Andersen wrote:
Have you right clicked the task bar and played around with the settings for the Task manager?
I'm not having this problem. I have "Only group when task manager is full" UNCHECKED and all the windows from say Thunderbird are grouped with a little green Plus sign cricle to let me know there are multiple.
If I hover over it, I will see thumbnails pop up, and can select the one I want. If I click the Tbird taskbar item, I will see a list, and again I can click the one I want. The scroll wheel will step through all the windows for the app I clicked or hovered over.
Moving the mouse out of that task area causes the list or the thumbnails go go away.
Notice also that you can control the locking interval (or turn it off) in the kde settings.
Quite frankly, this version of KDE5/Plasma is one of the best versions I've seen in a while, regardless of the underlying OS.
When the lists are up, I can click on open window, but they're partly covered by the lists. When clicking on the task bar fails, I can use the Alt-tab keys to move around, but I cannot start or open anything on the task bar. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 02:37 PM, James Knott wrote:
When the lists are up, I can click on open window, but they're partly covered by the lists. When clicking on the task bar fails, I can use the Alt-tab keys to move around, but I cannot start or open anything on the task bar.
When the list is up, I can click on an open window and the list instantly disappears. If you can't use the task bar to start anything, and If you had placed things on the task bar as launchers previously, (prior to updating) right click the launchers and remove them. Then use the kde menu to find them again, right click the menu item and select add as a launcher. Old launchers from the prior KDE version don't always work any more due to some change in kde internal structure. This was very recent, and affected KDE/Plasma on Opensuse as well as Manjaro. Not a 42.2 thing. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/20/2017 05:48 PM, John Andersen wrote:
On 03/20/2017 02:37 PM, James Knott wrote:
When the lists are up, I can click on open window, but they're partly covered by the lists. When clicking on the task bar fails, I can use the Alt-tab keys to move around, but I cannot start or open anything on the task bar. When the list is up, I can click on an open window and the list instantly disappears.
If you can't use the task bar to start anything, and If you had placed things on the task bar as launchers previously, (prior to updating) right click the launchers and remove them.
Then use the kde menu to find them again, right click the menu item and select add as a launcher.
Old launchers from the prior KDE version don't always work any more due to some change in kde internal structure.
This was very recent, and affected KDE/Plasma on Opensuse as well as Manjaro. Not a 42.2 thing.
Right now, I'm experiencing the can't click on task bar situation. Neither left or right clicking has any effect. However, I can move through open windows with Alt-tab. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/21/2017 06:49 AM, James Knott wrote:
This was very recent, and affected KDE/Plasma on Opensuse as well as Manjaro. Not a 42.2 thing.
Right now, I'm experiencing the can't click on task bar situation. Neither left or right clicking has any effect. However, I can move through open windows with Alt-tab.
And again now. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [01-01-70 12:34]:
On 03/21/2017 06:49 AM, James Knott wrote:
This was very recent, and affected KDE/Plasma on Opensuse as well as Manjaro. Not a 42.2 thing.
Right now, I'm experiencing the can't click on task bar situation. Neither left or right clicking has any effect. However, I can move through open windows with Alt-tab.
And again now.
have you tried a new user? ps: your mail client is not wrapping -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/21/2017 11:04 AM, Patrick Shanahan wrote:
have you tried a new user?
Not yet.
ps: your mail client is not wrapping It does on the messages I see. I normally use Seamonkey.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-21-17 11:09]:
On 03/21/2017 11:04 AM, Patrick Shanahan wrote:
have you tried a new user?
Not yet.
should be one of the first efforts to determine where the problem is.
ps: your mail client is not wrapping It does on the messages I see. I normally use Seamonkey.
yes, your msg provides: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 graphical and doesn't necessarily show what form it sends. it is *not* wrapping <80 chars. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/21/2017 11:22 AM, Patrick Shanahan wrote:
should be one of the first efforts to determine where the problem is.
The problem with that is all my bookmarks etc. would not be available then. However, I'll have to see if I can even switch to another user when the problem occurs. I do have a "test" user available, that I created years ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-21-17 11:33]:
On 03/21/2017 11:22 AM, Patrick Shanahan wrote:
should be one of the first efforts to determine where the problem is.
The problem with that is all my bookmarks etc. would not be available then. However, I'll have to see if I can even switch to another user when the problem occurs. I do have a "test" user available, that I created years ago.
new != "test" from years ago you cannot create a few bookmarks or even copy them? useradd <new-user> it really seems you are not interested in expending a *little* effort in solving your problem. this also translates to the effort being expended by those trying to assist you. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/21/2017 11:38 AM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-21-17 11:33]:
should be one of the first efforts to determine where the problem is. The problem with that is all my bookmarks etc. would not be available
On 03/21/2017 11:22 AM, Patrick Shanahan wrote: then. However, I'll have to see if I can even switch to another user when the problem occurs. I do have a "test" user available, that I created years ago. new != "test" from years ago
you cannot create a few bookmarks or even copy them?
useradd <new-user>
it really seems you are not interested in expending a *little* effort in solving your problem. this also translates to the effort being expended by those trying to assist you.
It's not a "little* effort to recreate my full normal desktop environment. I do a lot more than use a browser. Regardless, I did create a new account and the problem did not occur. However, as I was only running part of what I normally use, it might not have been a fair test. On the other hand, for some unknown reason, the problem has not yet reoccurred on my regular account, since I switched back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-22-17 13:27]:
On 03/21/2017 11:38 AM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-21-17 11:33]:
should be one of the first efforts to determine where the problem is. The problem with that is all my bookmarks etc. would not be available
On 03/21/2017 11:22 AM, Patrick Shanahan wrote: then. However, I'll have to see if I can even switch to another user when the problem occurs. I do have a "test" user available, that I created years ago. new != "test" from years ago
you cannot create a few bookmarks or even copy them?
useradd <new-user>
it really seems you are not interested in expending a *little* effort in solving your problem. this also translates to the effort being expended by those trying to assist you.
It's not a "little* effort to recreate my full normal desktop environment. I do a lot more than use a browser.
a "test" environment does not necessarily require a "full normal desktop" depending on what you are testing. a miniminal desktop should suffice to determine if your problem related to "clicking on the taskbar" is from a local config or software from the distro.
Regardless, I did create a new account and the problem did not occur. However, as I was only running part of what I normally use, it might not have been a fair test. On the other hand, for some unknown reason, the problem has not yet reoccurred on my regular account, since I switched back.
well, headway w/o much effort :). but answers remain missing. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2017 01:25 PM, James Knott wrote:
It's not a "little* effort to recreate my full normal desktop environment. I do a lot more than use a browser.
Regardless, I did create a new account and the problem did not occur. However, as I was only running part of what I normally use, it might not have been a fair test. On the other hand, for some unknown reason, the problem has not yet reoccurred on my regular account, since I switched back.
Looks like I spoke too soon. The horizontal window list is now up and I can't do anything to get rid of it. The mouse has no effect on either the list or task bar. System Activity shows plasmashell at a solid 13% or so CPU, compared to less than 1% on another computer and over 3.4 MB, compared to about 96.4K on the other computer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2017 04:10 PM, James Knott wrote:
On 03/22/2017 01:25 PM, James Knott wrote:
It's not a "little* effort to recreate my full normal desktop environment. I do a lot more than use a browser.
Regardless, I did create a new account and the problem did not occur. However, as I was only running part of what I normally use, it might not have been a fair test. On the other hand, for some unknown reason, the problem has not yet reoccurred on my regular account, since I switched back.
Looks like I spoke too soon. The horizontal window list is now up and I can't do anything to get rid of it. The mouse has no effect on either the list or task bar.
System Activity shows plasmashell at a solid 13% or so CPU, compared to less than 1% on another computer and over 3.4 MB, compared to about 96.4K on the other computer.
After killing the desktop and logging back in, plasmashell is running less than 1% CPU and about 99K memory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-22-17 16:17]:
On 03/22/2017 04:10 PM, James Knott wrote:
On 03/22/2017 01:25 PM, James Knott wrote:
It's not a "little* effort to recreate my full normal desktop environment. I do a lot more than use a browser.
Regardless, I did create a new account and the problem did not occur. However, as I was only running part of what I normally use, it might not have been a fair test. On the other hand, for some unknown reason, the problem has not yet reoccurred on my regular account, since I switched back.
Looks like I spoke too soon. The horizontal window list is now up and I can't do anything to get rid of it. The mouse has no effect on either the list or task bar.
System Activity shows plasmashell at a solid 13% or so CPU, compared to less than 1% on another computer and over 3.4 MB, compared to about 96.4K on the other computer.
After killing the desktop and logging back in, plasmashell is running less than 1% CPU and about 99K memory.
what about your <new-user> with miniminal desktop/footprint? what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in) have you tried using icewm with your kde apps running? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/03/17 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in)
"Application plasmashell could not be found using service org.kde.plasmashell and path /MainApplication." I tried as both a user and root. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-22-17 19:32]:
On 22/03/17 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in)
"Application plasmashell could not be found using service org.kde.plasmashell and path /MainApplication."
I tried as both a user and root.
I thought you said that plasmashell was using cpu? if so, it has to be running, did you look up it's pid? if it is not running, you can start it using the last part of the command: "kstart5 plasmashell & disown" verrry difficult to solve problems w/o having accurate information :( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/03/17 08:35 PM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-22-17 19:32]:
On 22/03/17 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in) "Application plasmashell could not be found using service org.kde.plasmashell and path /MainApplication."
I tried as both a user and root. I thought you said that plasmashell was using cpu? if so, it has to be running, did you look up it's pid? if it is not running, you can start it using the last part of the command: "kstart5 plasmashell & disown"
verrry difficult to solve problems w/o having accurate information :(
When it fails it uses lots of CPU & memory. When OK it uses about 100K and CPU so low it doesn't show a number. I also tried the last part of the command and got an error: "kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. QXcbConnection: Could not connect to display" It's hard to get accurate info, when you can't open new apps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2017 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in)
I tried again, when the system was running normally and it worked. I've left an open Konsole running on another virtual desktop which I can switch to, when it fails again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/22/2017 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in)
I tried again, when the system was running normally and it worked. I've left an open Konsole running on another virtual desktop which I can switch to, when it fails again.
two hints: - kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination. This is my script for restarting plasmashell, because it hangs quite often here: ------------------------< snip snip snip >----------------------------- #!/bin/bash PSHELL="/usr/bin/plasmashell" killpshell() { killall $( basename "$PSHELL" ) killall -9 $( basename "$PSHELL" ) } startpshell() { $PSHELL --shut-up >/dev/null 2>&1 & } killpshell startpshell ------------------------< snip snip snip >----------------------------- Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
two hints: - kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
Yes, I've experienced the same thing. However, it's a fairly recent problem (past week or so), so it may be due to some recent update. It's nice to see I'm not the only one with this issue. I have created an icon on the desktop, so when the problem occurs, I can switch to another virtual desktop and click on it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
- kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
That doesn't work when it locks. I get the error: $ "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." Like Patrick's suggestion, it will restart plasmashell when everything is normal, but not when the problem occurs. The only way I can get out of it is to use Ctl-Alt-Backspace to force a desktop shutdown. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2017 06:32 AM, James Knott wrote:
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
- kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
That doesn't work when it locks. I get the error:
$ "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Like Patrick's suggestion, it will restart plasmashell when everything is normal, but not when the problem occurs. The only way I can get out of it is to use Ctl-Alt-Backspace to force a desktop shutdown.
Sorry to be joining this thread late, but been on vacation... James, I too have been plagued by this failure on my laptop but for some mysterious reason, not on my desktop systems. They are all running the same version of OpenSuSE Leap42.2 and KDE/Plasma. I and others have also reported it, not only here on OpenSuSE but in other distros as well. Yes, the kicker bar freezes and nothing but open windows respond to the mouse or keyboard input. Something about Plasmashell appears to be sick... The best solution I have found so far is to leave a Konsole shell window open on my desktop. That way I can also get to it so as to issue the following two commands - killall plasmashell plasmashell & Do not issue this as root, but just do it under your own user account. Basically kill the plasmashell and restart it without regard to process ids. There are other ways to do this, as already has been pointed out, but like you I found problems and errors when I tried other approaches. This seems to be the more reliable way for me to get my desktop/plasmashell back. HTHs.... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On March 24, 2017 8:32:35 AM PDT, Marc Chamberlin <marc@marcchamberlin.com> wrote:
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
- kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
That doesn't work when it locks. I get the error:
$ "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or
On 03/24/2017 06:32 AM, James Knott wrote: the
network connection was broken."
Like Patrick's suggestion, it will restart plasmashell when everything is normal, but not when the problem occurs. The only way I can get out of it is to use Ctl-Alt-Backspace to force a desktop shutdown.
Sorry to be joining this thread late, but been on vacation... James, I too have been plagued by this failure on my laptop but for some mysterious reason, not on my desktop systems. They are all running the same version of OpenSuSE Leap42.2 and KDE/Plasma. I and others have also reported it, not only here on OpenSuSE but in other distros as well. Yes, the kicker bar freezes and nothing but open windows respond to the mouse or keyboard input. Something about Plasmashell appears to be sick...
The best solution I have found so far is to leave a Konsole shell window open on my desktop. That way I can also get to it so as to issue the following two commands -
killall plasmashell plasmashell &
Do not issue this as root, but just do it under your own user account. Basically kill the plasmashell and restart it without regard to process
ids. There are other ways to do this, as already has been pointed out, but like you I found problems and errors when I tried other approaches.
This seems to be the more reliable way for me to get my desktop/plasmashell back.
HTHs.... Marc...
This same problem plagued Manjaro months ago, and was resolved by regular kde updates. While it lasted I used Marc's solution keyed into the little command window that popped up after pressing alt-f2. Any need to do this disappeared months ago as Manjaro is a rolling release and regular kde upgrades came along and the problem went away. I believe it was traced to invisible remnants of a screen overlay that had crashed but was not completely shut down and was still intercepting mouse and keyboard inputs on some areas of the screen. There were numerous hits in bugs.kde.org on this issue. For me it occurred on Intel video chipset desktop fwif. I do not see this problem on leap 42.2. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
- kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
That doesn't work when it locks. I get the error:
$ "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
Like Patrick's suggestion, it will restart plasmashell when everything is normal, but not when the problem occurs. The only way I can get out of it is to use Ctl-Alt-Backspace to force a desktop shutdown.
Never had this problem on any of my machines. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
I'll try that next time it fails. Also, as I mentioned, this is a recent problem. I wonder if it's caused by some update. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
I'll try that next time it fails.
Also, as I mentioned, this is a recent problem. I wonder if it's caused by some update.
yes, but update for what? It can be a plasmashell update, but it can be each and every library in the system. And there are lots and lots of bug reports and mailing list entries about plasmashell freezing. Many of them are already fixed, so your case might be the 24th and mine can be numer 37 8-( Too many bugs in plasmashell - if anyone would ask me 8-< Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2017 04:01 PM, Michael Hirmke wrote:
Too many bugs in plasmashell - if anyone would ask me 8-<
or in FW5, all of which can cause the problem. My experience, and I'm 50-60 bug reports into Plasma/FW5, is there is a great deal of difficulty being experienced in coordinating between the kde folks and the Qt folks, and from my experience with dialog problems, a bit of a "whose on 1st" problem as well. Hopefully that gets resolved, and hopefully the priority shifts back to making the kde/fw5 dekstop the most efficient and well thought-out desktop going that minimizes the number of keystrokes and mouse-clicks required to accomplish any task while providing fine-grained user control over the configuration instead of the desktop feeling like a "loosely coordinated collection of applications without much of a guiding purpose" and wholly devoid of the fine-grained configuration control to allow users to tailor it to the way they work. The bellwether will be if they can ever fix konqueror --filemanagment to open with the traditional directory list on the left and file details on the right without the user having to sync and turn of unwanted detail every time the damn application is opened... We shall see... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
Isn't that already in your script? "PSHELL="/usr/bin/plasmashell" killpshell() { killall $( basename "$PSHELL" ) killall -9 $( basename "$PSHELL" )" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
Isn't that already in your script?
yes, it is - I didn't know if you used it as is. But then I really have no clue, why it can't kill your plasmashell 8-< Try this one and hav a look into the log. Perhaps it gives some insight into whats happening. ------------------------< snip snip snip >----------------------------- #!/bin/bash _me=$( basename $0 ) _tmp=${TMP} [ -z "$_tmp" ] && _tmp=${TEMP} [ -z "$_tmp" ] && _tmp=${HOME}/tmp LOG="${_tmp}/${_me}.log" [ -e "${LOG}" ] && rm -f ${LOG} exec 2>${LOG} set -x PSHELL="/usr/bin/plasmashell" killpshell() { killall $( basename "$PSHELL" ) killall -9 $( basename "$PSHELL" ) } startpshell() { $PSHELL --shut-up >>${LOG} 2>&1 & } killpshell startpshell ------------------------< snip snip snip >----------------------------- Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
I just tried that command and it did kill the desktop. However, I was unable to bring it back with running your script. When I did, I got the error: "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus)" Once again, I had to kill the desktop and log back in. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 11:36]:
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
I just tried that command and it did kill the desktop. However, I was unable to bring it back with running your script. When I did, I got the error:
"Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus)"
Once again, I had to kill the desktop and log back in.
guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system.
I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 11:47]:
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system.
I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop.
well, from err msg appear maybe a dbus problem exists also or in addition to. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 11:54 AM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-26-17 11:47]:
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system. I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop. well, from err msg appear maybe a dbus problem exists also or in addition to.
Also, the time between failures varies considerably. It may be as short as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 12:01]:
On 03/26/2017 11:54 AM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-26-17 11:47]:
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system. I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop. well, from err msg appear maybe a dbus problem exists also or in addition to.
Also, the time between failures varies considerably. It may be as short as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so.
I would guess it is time for you to bit-the-bullet and actually try a new user so your current configs can be eliminated. I recently, 6-10 weeks ago, installed 42.2 w/kde-plasma5 remotely on a friends box and he has no such problems, and he has very little computer experteeeese. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 01:09 PM, Patrick Shanahan wrote:
Also, the time between failures varies considerably. It may be as short
as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so. I would guess it is time for you to bit-the-bullet and actually try a new user so your current configs can be eliminated. I recently, 6-10 weeks ago, installed 42.2 w/kde-plasma5 remotely on a friends box and he has no such problems, and he has very little computer experteeeese.
Recreating everything would be a big job. Is there a directory I can rename, so that my desktop starts fresh? I see both .kde and .kde4 directories. Also, it's curious that this problem started recently. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 13:22]:
On 03/26/2017 01:09 PM, Patrick Shanahan wrote:
Also, the time between failures varies considerably. It may be as short
as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so. I would guess it is time for you to bit-the-bullet and actually try a new user so your current configs can be eliminated. I recently, 6-10 weeks ago, installed 42.2 w/kde-plasma5 remotely on a friends box and he has no such problems, and he has very little computer experteeeese.
Recreating everything would be a big job. Is there a directory I can rename, so that my desktop starts fresh? I see both .kde and .kde4 directories. Also, it's curious that this problem started recently.
look also below ~/.config/ curious, doesn't mean that you already had configurations that were already uncompatible but not visible until after updates. if you are *really* interested in a solution, you should begin with a *new* user and slowly add preferences until you reach a stable system or find what is causing your problem. w/o a controlled environment, you will be very lucky to identify a cause. you need to make a choice. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 01:40 PM, Patrick Shanahan wrote:
curious, doesn't mean that you already had configurations that were already uncompatible but not visible until after updates.
if you are *really* interested in a solution, you should begin with a *new* user and slowly add preferences until you reach a stable system or find what is causing your problem. w/o a controlled environment, you will be very lucky to identify a cause.
you need to make a choice.
What if I rename my home directory, recreate the user and start moving stuff back? I have a lot of stuff in there, all my files from over the years, music, various accounts and lots more. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 13:49]:
On 03/26/2017 01:40 PM, Patrick Shanahan wrote:
curious, doesn't mean that you already had configurations that were already uncompatible but not visible until after updates.
if you are *really* interested in a solution, you should begin with a *new* user and slowly add preferences until you reach a stable system or find what is causing your problem. w/o a controlled environment, you will be very lucky to identify a cause.
you need to make a choice.
What if I rename my home directory, recreate the user and start moving stuff back? I have a lot of stuff in there, all my files from over the years, music, various accounts and lots more.
key is beginning with a *new* user and default configs. how you get there is your choice. the idea is to identify and eliminate the problem. you can always alter your present user/configs after you have identified the problem and determined a solution. I cannot see that one is better than the other except that leaving your present user/configs and altering later *may* be less work. in days past, simply moving ~/.kde# would have sufficed but today is somewhat more complex. but you *might* get by just moving present ~/.kde# directories and trying, I am not knowledgeable enough to say. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-26 19:47, James Knott wrote:
On 03/26/2017 01:40 PM, Patrick Shanahan wrote:
curious, doesn't mean that you already had configurations that were already uncompatible but not visible until after updates.
if you are *really* interested in a solution, you should begin with a *new* user and slowly add preferences until you reach a stable system or find what is causing your problem. w/o a controlled environment, you will be very lucky to identify a cause.
you need to make a choice.
What if I rename my home directory, recreate the user and start moving stuff back? I have a lot of stuff in there, all my files from over the years, music, various accounts and lots more.
You can symlink the data directories to the new user. You can rename your home, create a new one with only the default files (you find out which by creating a new user), then move the data directories from your old home. I suggest you do the move with mc in console. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Le 27/03/2017 à 12:15, Carlos E. R. a écrit :
You can symlink the data directories to the new user.
data have no need to be in /home... just adjust the permissions jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/27/2017 07:03 AM, jdd wrote:
Le 27/03/2017 à 12:15, Carlos E. R. a écrit :
You can symlink the data directories to the new user.
data have no need to be in /home... just adjust the permissions
I have a separate partition for /home and would like to keep things that way. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/27/2017 06:15 AM, Carlos E. R. wrote:
You can rename your home, create a new one with only the default files (you find out which by creating a new user), then move the data directories from your old home. I suggest you do the move with mc in console.
That is what I was thinking of doing, after I back up that partition. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/26/2017 01:09 PM, Patrick Shanahan wrote:
Also, the time between failures varies considerably. It may be as short
as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so. I would guess it is time for you to bit-the-bullet and actually try a new user so your current configs can be eliminated. I recently, 6-10 weeks ago, installed 42.2 w/kde-plasma5 remotely on a friends box and he has no such problems, and he has very little computer experteeeese.
Recreating everything would be a big job. Is there a directory I can rename, so that my desktop starts fresh? I see both .kde and .kde4 directories. Also, it's curious that this problem started recently.
you could start moving ~/.config/plasma* out of the way. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 11:58 AM, James Knott wrote:
On 03/26/2017 11:54 AM, Patrick Shanahan wrote:
* James Knott <james.knott@rogers.com> [03-26-17 11:47]:
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system. I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop. well, from err msg appear maybe a dbus problem exists also or in addition to.
Also, the time between failures varies considerably. It may be as short as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so.
This problem seems to have cleared with the recent updates. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/04/2017 05:01 PM, James Knott wrote:
Also, the time between failures varies considerably. It may be as short
as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so.
This problem seems to have cleared with the recent updates.
Apparently not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/06/2017 01:02 PM, James Knott wrote:
On 04/04/2017 05:01 PM, James Knott wrote:
Also, the time between failures varies considerably. It may be as short
as an hour or two. Or it could be a couple of days. However, it seems to have started within the past couple of weeks or so.
This problem seems to have cleared with the recent updates.
Apparently not.
Not for me either, and I have installed all the latest updates that I have been notified about... Marc.. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 08:46 AM, James Knott wrote:
On 03/26/2017 11:45 AM, Patrick Shanahan wrote:
Once again, I had to kill the desktop and log back in. guessing but, aiui you cannot restart dbus/requires reboot. perhaps you need to restart your system.
I have rebooted a few times. It makes no difference whether I reboot or just use Ctl-Alt-Backspace to kill the desktop.
This freeze is a wide-spread problem, seems though it does not hit everyone, nor does it always seem to have *exactly* the same symptoms. It is upstream, IMHO, at either KDE or QT. I have seen multiple reports of this same thing in different distros, not just openSUSE, and the common clue is all are running KDE Plasma5 desktop. The problem shows up sometimes with some update, not tracked down yet AFAIK, and sometimes can disappear as mysteriously as it appeared. It is not GPU specific, as it happens on some AMD systems and some Intel systems, as well as some systems with nVidia (I believe). It is happening on some old machines and some new ones. There are a few threads on the openSUSE Forum about it, if you check. I ran into the same problem a couple days ago when I installed 42.2 on a client's laptop that had to be delivered right away, so I did not have the luxury of the time to investigate it. Instead, I reinstalled and used Xfce as the desktop. Problem gone. ===== Some suggestions you might try: Next freeze, lock the screen (Ctrl-Alt-L), and if that works unlock the screen and see if it frees up the system. If you are using SDDM as the Display Manager, try installing KDM (I understand it is not installed by default anymore), then switch to it and see if the problem continues. Or, consider switching to Xfce for awhile. Or, wait until a solution comes along. Good luck. -- -Gerry Makaro aka Fraser_Bell on the forums, IRC, and mail at openSUSE.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
As I recall from Manjaro, it's a Dbus issue, and they resolved it be creating a special Dbus-kde package. It's been gone from Manjaro for well over 3 months now. Maybe someone knowledgeable could grab that package and see what they do. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 06:04 PM, Fraser_Bell wrote:
If you are using SDDM as the Display Manager, try installing KDM (I understand it is not installed by default anymore), then switch to it and see if the problem continues.
According to the sysconfig editor, it's kdm4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@rogers.com> [03-26-17 20:57]:
On 03/26/2017 06:04 PM, Fraser_Bell wrote:
If you are using SDDM as the Display Manager, try installing KDM (I understand it is not installed by default anymore), then switch to it and see if the problem continues.
According to the sysconfig editor, it's kdm4.
and maybe that is the problem. on my Tw, kdm is offered but no kdm3 or 4. I use sddm and used to have plasmshell glitches, but not now for several months. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 11:59 PM, Patrick Shanahan wrote:
According to the sysconfig editor, it's kdm4. and maybe that is the problem. on my Tw, kdm is offered but no kdm3 or 4. I use sddm and used to have plasmshell glitches, but not now for several months.
I didn't even see sddm listed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2017-03-26 20:56 (UTC-0400):
Fraser_Bell wrote:
If you are using SDDM as the Display Manager, try installing KDM (I understand it is not installed by default anymore), then switch to it and see if the problem continues.
According to the sysconfig editor, it's kdm4.
That's never worked here, only ever kdm or kdm3 or tdm. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/24/2017 11:59 AM, Michael Hirmke wrote:
did you use my suggestion with "killall"? With killall -9 there should be no situation, where plasmashell can survive.
I just tried that command and it did kill the desktop. However, I was unable to bring it back with running your script. When I did, I got the error:
"Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus)"
But this error belongs to the killing action, not the restart action. Sorry to ask: But are you *really* sure that you use my script? The message above looks as if it comes from kquitapp5 - my script should never give a message like that. If you really use my script, you could try to place a "sleep 2" between the two function calls for killing and restarting plasmashell. Perhaps they run too fast consecutivly.
Once again, I had to kill the desktop and log back in.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 04:00 PM, Michael Hirmke wrote:
orry to ask: But are you *really* sure that you use my script? The message above looks as if it comes from kquitapp5 - my script should never give a message like that.
Sorry, my mistake. That was from the command Patrick gave me. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2017 04:00 PM, Michael Hirmke wrote:
If you really use my script, you could try to place a "sleep 2" between the two function calls for killing and restarting plasmashell. Perhaps they run too fast consecutivly.
I just tried it again and it worked this time. I didn't change it to add the sleep 2. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/26/2017 04:00 PM, Michael Hirmke wrote:
If you really use my script, you could try to place a "sleep 2" between the two function calls for killing and restarting plasmashell. Perhaps they run too fast consecutivly.
I just tried it again and it worked this time. I didn't change it to add the sleep 2.
glad to hear that it works now - sort of :) Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/27/2017 02:35 PM, Michael Hirmke wrote:
Hi James,
On 03/26/2017 04:00 PM, Michael Hirmke wrote:
If you really use my script, you could try to place a "sleep 2" between the two function calls for killing and restarting plasmashell. Perhaps they run too fast consecutivly. I just tried it again and it worked this time. I didn't change it to add the sleep 2. glad to hear that it works now - sort of :)
Bye. Michael.
It turns out, I don't have to keep a konsole open on another virtual desktop. All I have to do is press Alt-F2 and enter the name of the script I created. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi James,
On 03/27/2017 02:35 PM, Michael Hirmke wrote:
Hi James,
On 03/26/2017 04:00 PM, Michael Hirmke wrote:
If you really use my script, you could try to place a "sleep 2" between the two function calls for killing and restarting plasmashell. Perhaps they run too fast consecutivly. I just tried it again and it worked this time. I didn't change it to add the sleep 2. glad to hear that it works now - sort of :)
Bye. Michael.
It turns out, I don't have to keep a konsole open on another virtual desktop. All I have to do is press Alt-F2 and enter the name of the script I created.
And - as I wrote in one of my earlier mails in this thread - it will be even easier, if you create a shortcut like Ctrl-Alt-P to run the script :) Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/28/2017 12:24 PM, James Knott wrote:
It turns out, I don't have to keep a konsole open on another virtual desktop. All I have to do is press Alt-F2 and enter the name of the script I created.
Pretty sure I mentioned that in one of my first replies on this subject. Also that you don't need a script because Alt-F2 will remember a long list of prior commands, including the entire killall and restart sequences. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/28/2017 07:26 PM, John Andersen wrote:
On 03/28/2017 12:24 PM, James Knott wrote:
It turns out, I don't have to keep a konsole open on another virtual desktop. All I have to do is press Alt-F2 and enter the name of the script I created. Pretty sure I mentioned that in one of my first replies on this subject. Also that you don't need a script because Alt-F2 will remember a long list of prior commands, including the entire killall and restart sequences.
Yep, it remembers the script name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2017 04:58 PM, Patrick Shanahan wrote:
what happens if you issue: kquitapp5 plasmashell && kstart5 plasmashell & disown (restarts plasmashell w/o having to logout/in)
While that restarts plasmashell when it's working properly, it doesn't when the problem occurs. I just tried it now and got the following: $ Calling appendChild() on a null node does nothing. "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-21 16:22, Patrick Shanahan wrote:
* James Knott <> [03-21-17 11:09]:
yes, your msg provides: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
graphical and doesn't necessarily show what form it sends. it is *not* wrapping <80 chars.
This behaviour is correct and according to the rules. It means that your client is free to wrap instead to the size of your local window, be it 40 chars, 60, 80, 200... -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [03-21-17 11:57]:
On 2017-03-21 16:22, Patrick Shanahan wrote:
* James Knott <> [03-21-17 11:09]:
yes, your msg provides: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
graphical and doesn't necessarily show what form it sends. it is *not* wrapping <80 chars.
This behaviour is correct and according to the rules.
new rules?
It means that your client is free to wrap instead to the size of your local window, be it 40 chars, 60, 80, 200...
I believe that is what I said, his client is *not* wrapping <80 chars. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/21/2017 12:02 PM, Patrick Shanahan wrote:
This behaviour is correct and according to the rules. new rules?
It means that your client is free to wrap instead to the size of your local window, be it 40 chars, 60, 80, 200... I believe that is what I said, his client is *not* wrapping <80 chars.
Actually, it's been that way for as long as I can remember. As Carlos mentioned, it allows the text to properly wrap for whatever you're reading on. For example, I have your message open on both my computer and smart phone. In both cases it wraps to best fit the display. On the computer the line "I believe that is what I said, his client is *not* wrapping <80 chars." is displayed on one line, but on the phone it wraps after "*not*. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-21 17:02, Patrick Shanahan wrote:
* Carlos E. R. <> [03-21-17 11:57]:
On 2017-03-21 16:22, Patrick Shanahan wrote:
* James Knott <> [03-21-17 11:09]:
yes, your msg provides: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
graphical and doesn't necessarily show what form it sends. it is *not* wrapping <80 chars.
This behaviour is correct and according to the rules.
new rules?
No, old. It is called "flowed text". Your client should cope.
It means that your client is free to wrap instead to the size of your local window, be it 40 chars, 60, 80, 200...
I believe that is what I said, his client is *not* wrapping <80 chars.
Which is correctly done. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 03/21/2017 09:45 AM, Carlos E. R. wrote:
On 2017-03-21 17:02, Patrick Shanahan wrote:
* Carlos E. R. <> [03-21-17 11:57]:
On 2017-03-21 16:22, Patrick Shanahan wrote:
* James Knott <> [03-21-17 11:09]:
yes, your msg provides: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
graphical and doesn't necessarily show what form it sends. it is *not* wrapping <80 chars.
This behaviour is correct and according to the rules.
new rules?
No, old. It is called "flowed text". Your client should cope.
It means that your client is free to wrap instead to the size of your local window, be it 40 chars, 60, 80, 200...
I believe that is what I said, his client is *not* wrapping <80 chars.
Which is correctly done.
Be aware there is a maximum line length issue in one or more of the smtp RFCs. Long paragraphs of text can exceed that maximum and are summarily truncated. Its rather long, and the exact number of characters escapes me at the moment, but the limit is still there. Microsoft got burned by this some years ago when they started encouraging the use of this so called flowed text in Exchange. They fixed exchange to work around this limit but you will still see occasional TL;DR wall-of-text paragraphs that get truncated in emails. So its nice when it works but it doesn't always work. -- After all is said and done, more is said than done.
On 2017-03-22 08:21, John Andersen wrote:
On 03/21/2017 09:45 AM, Carlos E. R. wrote:
On 2017-03-21 17:02, Patrick Shanahan wrote:
Be aware there is a maximum line length issue in one or more of the smtp RFCs. Long paragraphs of text can exceed that maximum and are summarily truncated. Its rather long, and the exact number of characters escapes me at the moment, but the limit is still there.
Microsoft got burned by this some years ago when they started encouraging the use of this so called flowed text in Exchange. They fixed exchange to work around this limit but you will still see occasional TL;DR wall-of-text paragraphs that get truncated in emails.
So its nice when it works but it doesn't always work.
Well, Thunderbird uses flowed text for paragraphs, that's certain. I think it normally flows and truncates paragraph text, but does leaves quoted text the same way it was. Maybe it works around by using soft returns, however they are called. Test long paragraph: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
Test long quoted paragraph: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 2017-03-22 10:36, Carlos E. R. wrote:
On 2017-03-22 08:21, John Andersen wrote:
On 03/21/2017 09:45 AM, Carlos E. R. wrote:
On 2017-03-21 17:02, Patrick Shanahan wrote:
...
Maybe it works around by using soft returns, however they are called.
Test long paragraph: helo helo helo helo helo helo helo helo helo helo
...
Test long quoted paragraph: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
This part gets short lines that end with "=[newline]" to mark that it is all a single long line. So that's how it is done. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Am 22.03.2017 um 10:36 schrieb Carlos E. R.:
On 2017-03-22 08:21, John Andersen wrote:
On 03/21/2017 09:45 AM, Carlos E. R. wrote:
On 2017-03-21 17:02, Patrick Shanahan wrote:
Be aware there is a maximum line length issue in one or more of the smtp RFCs. Long paragraphs of text can exceed that maximum and are summarily truncated. Its rather long, and the exact number of characters escapes me at the moment, but the limit is still there.
Microsoft got burned by this some years ago when they started encouraging the use of this so called flowed text in Exchange. They fixed exchange to work around this limit but you will still see occasional TL;DR wall-of-text paragraphs that get truncated in emails.
So its nice when it works but it doesn't always work.
Well, Thunderbird uses flowed text for paragraphs, that's certain. I think it normally flows and truncates paragraph text, but does leaves quoted text the same way it was.
Maybe it works around by using soft returns, however they are called.
Test long paragraph: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
Test long quoted paragraph: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
In fact I prefer flowed text. If I (or somebody) choose a fixed line length, and I look at it with a client window smaller than this fixed length, I always see one-and-a-half lines, because a NewLine is inserted at the end of each line. It looks like this, for example: helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo While flowing text simply adjusts to MY chosen window with. I prefer that by far. -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2017 06:25 AM, Daniel Bauer wrote:
In fact I prefer flowed text. If I (or somebody) choose a fixed line length, and I look at it with a client window smaller than this fixed length, I always see one-and-a-half lines, because a NewLine is inserted at the end of each line.
It looks like this, for example:
helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo helo
I have seen messages like that and find them hard to read, as the text flow is broken. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (11)
-
Carlos E. R. -
Daniel Bauer -
David C. Rankin -
Felix Miata -
Fraser_Bell -
James Knott -
jdd -
John Andersen -
Marc Chamberlin -
mh＠mike.franken.de -
Patrick Shanahan