Registered Member
|
I just upgraded Plasma Active on my tablet from One to Two, and I seem to be having some problems here. Namely, some programs fail to launch.
If I try running KDE System Settings, I can see a new window being opened, but it closes almost immediately. If I launch it through the console, I get an error message:
I can launch the PA settings fine, though. Another program that fails to launch is KWin. If I try to launch it normally, it says that another window manager might be running (although it's not, programs like YaST are shown without any window borders at all). And if I do a kwin --replace, I get this:
And lastly, after the upgrade the system asks me for a password at login, which is of course impossible to enter without a keyboard to begin with. Any ideas about how to solve these issues? I have to say that it feels a lot faster now than before, though I'm not sure if it's because KWin is not working or if it's the optimisations done to the system. Or perhaps both. From what I can see that was changed so far, the lock screen is quite nice. Although I don't really need it all that much. The new turn off dialogue is also rather neat, though I wonder where the suspend to disk button is... And other than that, I haven't found any more major changes there so far, but I see that there was work done on the browser, so that's something else to check once I get around to trying it. Good work on pushing out a new release! |
Registered Member
|
I had similar behavior.
Search for settings in the App Launcher. "System Settings" is displayed. Clicking on that icon produces a grey screen for a few seconds. "systemsettings" in terminal generates message in original post. However, I found that some subsections normally found in System Settings or Personal Settings (in other versions of Plasma) were separate applications in PA2...notifications, power, desktop search. So is System Settings a bug or a feature? |
Administrator
|
Please try running "systemsettings" in a debugger such as gdb with the "--nofork" argument:
Then when it crashes, please generate a backtrace. Also, try running "kbuildsycoca4 --noincremental" to flush out any old caches. Judging by the KWin error messages, it seems you may be missing either upgrades to components of X or the kernel, as compositing does not seem to be available.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
backtrace generated. Should I post it in a message here? Or is there a way to attach a .TXT file?
|
Administrator
|
Pastebin the backtrace somewhere like paste.kde.org, and post a link to it here.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
|
Administrator
|
This appears to be being caused by a infinite loop inside the KCategorizedView code, which is a component of kdelibs used by System Settings. Please file a bug report at bugs.kde.org.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I did upgrade the kernel from 3.1.1 to 3.1.4, and Xorg was upgraded to whatever was in the repository when I did a zypper dup. Though I did have a few issues when upgrading the kernel with initrd generation, so I could reinstall those packages and see if anything changes. |
Administrator
|
Can you please check the KWin output in ~/.xsession-errors? It should indicate if compositing is available with OpenGL.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
It's a rather long log there. I pasted it here:
http://paste.kde.org/175562/ |
Administrator
|
Your system is operating using the Mesa Software Rasterizer.
This explains why the system feels sluggish graphically. You will need to check your Kernel and X configuration and verify their setup to enable Direct Rendering to fix this issue.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
But it's already enabled:
My system is running psb_gfx driver through DirectFB, I believe. Since it's a GMA600 device, the graphics options are rather limited here. |
Administrator
|
Can you please try a native, fresh installation of PA Two?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
OK, I downloaded the Balsam Pro LiveCD and tried it. And there is no change, KWin won't launch there either, with .xsession-errors file being pretty much identical. It did launch fine on PA One, though, so it's puzzling...
While testing that out, I noticed that it has the shutdown button in the system tray, but my upgraded system doesn't have one. Does it need a package to display it, or it is a configuration option somewhere? Speaking about the system tray, why doesn't the icon for NetworkManager appear? It shows me the "?" icon every time, and that was also so in PA One. Oh, and does anyone else get Plasma crashes when you try to turn off the machine? I get them nearly every time both now and on PA One. I also used to get them on PA One when going from one activity to another, although I don't recall if it's still the case in PA Two. |
Registered Member
|
There is no indication in this thread about your hardware. I'm running ExoPC Slate with the Atom N450.
It had openSUSE 11.4 and all the tweaks necessary to run Plasma Active and Contour. Rather than upgrading, I did a fresh install. So the tablet is now running openSUSE 12.1 and the adjustments suggested at community.kde.org/Plasma/Active/Installation. I've also added the available Packman repositories. This installation has the blue sleep button in the System Tray. When pushed, the button brings up a dialog box with choices...lock, sleep, turn off. I also the ? icon for Network Management. But the antenna icon was there in the earlier version. There have been a few crashes when turning off. I don't recall specifically what crashed. Mostly the shutdown happens fine. |
Registered users: Bing [Bot], claydoh, Google [Bot], markhm, rblackwell, sethaaaa, Sogou [Bot], Yahoo [Bot]