Announcement

**Spadge** · Dec 26, 2012, 12:57 PM

Hi there. Welcome to the forum!

Have you updated KDE beyond the version that ships with 12.10? I know there were bugs logged about plasma/KDE that have subsequently been fixed.

**oznola** · Dec 26, 2012, 01:22 PM

hi Spadge,

thank you for the welcome and possible solution to check. the answer to your question is "i have not."

i am new to kde. but the command line is an old friend.

i suppose the way to do what you have implied would be to type something like "kdesudo apt-get, ,,, ,,, ,,," and press enter.

will you help with that line please?

thank you.

**ronw** · Dec 26, 2012, 02:02 PM

sudo apt-get update, followed by sudo apt-get dist-upgrade.

Use kdesudo for running applications as root.

You may also want to consider adding some ppas, at least Kubuntu updates: https://launchpad.net/~kubuntu-ppa

Starting applications from the command line, in your case dolphin, can also sometimes provide useful output.

**Spadge** · Dec 26, 2012, 03:17 PM

Originally posted by oznola View Post

hi Spadge,

thank you for the welcome and possible solution to check. the answer to your question is "i have not."

i am new to kde. but the command line is an old friend.

i suppose the way to do what you have implied would be to type something like "kdesudo apt-get, ,,, ,,, ,,," and press enter.

will you help with that line please?

thank you.

Like ronw says, get you some PPAs.

Then you can do your updates in Muon or using apt-get on the command line, whichever you prefer. I generally use Muon.

**oznola** · Dec 26, 2012, 03:33 PM

alright,

i ran...

sudo apt-add-repository https://launchpad.net/~kubuntu-ppa
sudo apt-get update
sudo apt-get dist-upgrade

other than adding the ppa and observing the subsequent changes made while the update ran and noting that a few files expected in the update were not found, running the dist-upgrade added no packages so i miss-reported my my actions with respect to KDE update post initial installation. indeed i did run the update that is triggered by the little badge in the system bar on the top of the screen and it seems that is the same as running apt-get dist-upgrade. (there was a notification to run the update shortly after the initial boot and login.)

also, thank you for straitening out my conceptual integrity with respect to when to use kdesudo.

kdesudo should only be used when launching gui applications from the command line which will launch them as su.
^^^ that's cleaver by the way...

it's been a few hours since plasma hung on me. one way to elicit a hang was to click on the "Page one" or "Page 2" areas to the right of "Search and launch" in the system bar. my intent was to switch to these pages as one would do with v-desktops but perhaps doing that is somehow unsound because i am still a novice with plasma.

thank you for the help. i guess we will see how this unfolds.

perhaps i have hung plasma as a result of operator error but if that is true it seems it should have given a more graceful recovery. if one clicks a button that is out of context it should not cause things to hang. last night plasma hung when i launched dolphin from Search and launch. i had to press the power button and restart.

sometimes when plasma has hung i have just wandered off and when i came back it had become unhung on it's own. other
times i have had to press and hold the power button to restart the machine.

**Spadge** · Dec 26, 2012, 04:00 PM

It shouldn't be possible for user-error to hang the system. That's kinda the whole point.

I found, after I first installed 12.10, that pretty much adding any plasmoids to the desktop would crash it. This was fixed in a KDE update very quickly.

I hope it stays stable for you.

**Batty** · Dec 26, 2012, 04:28 PM

try running this - sudo add-apt-repository ppa:kubuntu-ppa
then sudo update
sudo dist-upgrade
it will allow you to update KDE to the latest version

**oznola** · Dec 26, 2012, 05:47 PM

thank you batty,

that was a great thing to do and i have put it in my notebook for future use.

the update ran and ran then finished successfully and things seem a little better. but things still hang when i click on a "Page" in the status bar. one thing that has improved is the rectangular highlight that is usually over Search and launch is now switching completely to the Page i select in the status bar. before it only slid about 1/2 way.

**oznola** · Dec 26, 2012, 07:09 PM

hi,

i have been trying to get some understanding of the problems i am experiencing with switching between the desktops in my netbook plasma environment.

it seems that if i switch between Search and launch and Page 2 things work for the most part as i would expect. however if i click on Page one then stuff hangs. I have two pages on my desktop Page one is i believe the default desktop (not Search and launch) Page 2 is one that i have added using the command bar at the bottom of the screen.

my speculation is Page one (the first desktop in the list of desktops) has not been initialized. subsequently when i click on Page one stuff hangs.

perhaps the desktop functionality in plasma netbook has not been deployed yet or someone has forgot to initialize the '0' desktop?

**oznola** · Dec 26, 2012, 07:30 PM

now i believe that "Pages" may not actually be the desktops because i have discovered one can send applications to the various desktops by right-clicking on the title-bar and selecting a desktop to move that application (such as chrome) to a "desktop <number>". bear in mind that Pages may indeed be the desktops but because they are not one-to-one things aren't sent where you think you are sending them.

it's wonderful and good one can send an app to another desktop that is normal for a multi-desktop system but at present now there seems to be no way to get it back that i can find. it's the largest potential memory leak that i could imagine. e.g. one can start stuffing applications in the inaccessible desktops until the system crashes for memory exhaustion.

i believe that plasma workspaces netbook is not deployed as implemented and that's mostly why this thread is here.

i hope i am wrong because the implementation of plasma workspaces is the most elegant multiple desktop design i have ever seen.

if someone can tell me how to get to those desktops and operate with applications sent them please do because i really want to use plasma workspaces as i have been reading about it.

thank you everyone. :lol:

**oznola** · Dec 27, 2012, 04:29 PM

hi,

the instance of chrome that i sent to Desktop 2 is persisting between restarts of the machine. i know this because it is briefly displayed during shut down now. allot of weird things that appear to be memory related seem to be happening such as portions of the Search and launch configuration panel are being displayed as semi-transparent over the main display.

i believe the persistent instance of chrome that is living in an otherwise undefined memory space is making the install unstable.

subsequently, i will re-install 12.10 and wait until i get confirmation that netbook plasma workspaces has been deployed as implemented before trying to use it again.

thank you to everyone who offered solutions. i am grateful to you and i have written everyone of your command line suggestions down in my KDE notebook.

unless someone has something to add i think this will be the end of the thread.

**oznola** · Jan 01, 2013, 02:17 AM

the answer to my fundamental question is that one must add the Pager widget to the widget panel before they can add desktops and navigate among them.

click the cashew select Add Widgets search for Pager then drag it onto the desktop. next right click, add some desktops, etc,,,

the other thing about plasma crashing when one clicks on "Page one" is a known bug that has not been resolved yet.

does anyone know what that "Page one" thing is suppose to do? can i remove it?

i tried right clicking on it but that hung my system too.

**Couch_Potato** · Jan 05, 2013, 11:47 AM

Originally posted by oznola View Post

alright,

i ran...

other than adding the ppa and observing the subsequent changes made while the update ran and noting that a few files expected in the update were not found, running the dist-upgrade added no packages so i miss-reported my my actions with respect to KDE update post initial installation. indeed i did run the update that is triggered by the little badge in the system bar on the top of the screen and it seems that is the same as running apt-get dist-upgrade. (there was a notification to run the update shortly after the initial boot and login.)

also, thank you for straitening out my conceptual integrity with respect to when to use kdesudo.

kdesudo should only be used when launching gui applications from the command line which will launch them as su.
^^^ that's cleaver by the way...

it's been a few hours since plasma hung on me. one way to elicit a hang was to click on the "Page one" or "Page 2" areas to the right of "Search and launch" in the system bar. my intent was to switch to these pages as one would do with v-desktops but perhaps doing that is somehow unsound because i am still a novice with plasma.

thank you for the help. i guess we will see how this unfolds.

perhaps i have hung plasma as a result of operator error but if that is true it seems it should have given a more graceful recovery. if one clicks a button that is out of context it should not cause things to hang. last night plasma hung when i launched dolphin from Search and launch. i had to press the power button and restart.

Oznola.

Instead of performing a power cycle a more gracefull way (and merciful for your system) would be to use the following key combinations:

hold down:<cntrl><alt><SysRq> then press <r><e><s> and either to reboot or <o> to just shutdown. Now there was a little limmerick/verse that someone wrote to help people remember this, but of course I don't remember, but this works and unmouts the file system and puts the system in a state more accomodating to a shutdown w/o fragging your system/data. Or just check out this link:

http://en.wikipedia.org/wiki/Magic_SysRq_key

I know that this doesn't help with your current problem, but I hope it can save you from future issues.

Best Regards,

Couch_Potato

sometimes when plasma has hung i have just wandered off and when i came back it had become unhung on it's own. other
times i have had to press and hold the power button to restart the machine.

**oznola** · Jan 05, 2013, 12:26 PM

thank you Couch_Potato,

using "hold down:<cntrl><alt><SysRq> then press <r><e><s> and either to reboot or <o>" is the wisdom i ~should~ follow. i have known of this method for a long time (10 years?).

i could usually remember <contrl><alt>SysRq> but then to recall <r><e><s> and or <o> seemed to be far more difficult than just holding down the power button.

that said? i shall immediately take steps to ensure <contrl><alt><SysRq> followed by <r><e><s> punctuated by or <o> finally becomes my practice during a system hang.

<contrl><alt><SysRq> is easy enough. i shall remember the subsequent string of lower case letters with a melodic mnemonic M, I, C, K, E, Y.... <r><e><s>,,,, then press to reboot or <o> to shutdown. (i really dig using <o> as a mnemonic for off).

in fact? i had it so good that i used to have a reference to what each of those key presses did.

i'll have to track down what those key-strokes do again. while i don't have my teacher to hand me that cheat-sheet one more time. Couch_Potato? i am grateful i have you to point me in the right direction.

and this time? i shall ~finally~ get the proper way of cycling the system under my fingers the way my teacher was telling me to do more than 10 years ago...

<Ctrl><Alt><SysRq> M, I, C, K, E, Y,,, <r><e><s>,,,, (then or <o>)....

Announcement

plasma hangs a lot

plasma hangs a lot

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment