Hello there, i just wanted to report these problems i had after a fresh installation of chakra, and now with arch:
The first one is that in ~/.kde4/autostart/ there aren't any file to overwrite to start be-shell instead of plasma.
The second is for the taskbar (and the buttons in it): mode and buttonmode are both set to 1, and every button is set to display a custom label - this worked till the new installations. Now the buttons display the custom labels only when the app is closed, otherwise it shows the window title (the config is the same than before)
Last edit: Hombremaledicto 2012-08-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The be.shell install contains a message on how to replace plasma - it's not done automagically (as is not with the regular installation routine)
Matter of habits.
Second one was actually a bug which lead the taskbuttons not to align to the actual window, ie. it's expected that the button matches the window title (unless of course there's no window)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems i made it: i did not found the autostart folder in ~/.kde4/share/ (there wasn't one) in my previous installations or by compiling. After reinstalling the package from aur this time it was there,and so i copied the files from usr/share/beshell/examples. The only weird thing is that after logout/login there wasn't plasma (of course) nor be.shell. I had to start x manually from a console session... and finally a be.shell session without plasma greeted me!
(i've also checked the " start empty session " option in systemsettings btw)
Thank you for your time, and sorry if i continue to annoy you.
Now i'm happy again :P
Last edit: Hombremaledicto 2012-09-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't worry, i apologize for the delay, i've got less time than before for sitting at the pc.
Yes, i copied all the 3 files to ~/.kde4/share/autostart/ but at every startup the first login displays only the wallpaper chosen from be-shell and a message error that says that kwin crashed (in fact no decoration on the window). I have to logout or enter in console mode, login, and startx manually to start be-shell. The problem is also solved with a second graphical login from kdm.
Days ago i also wrote a guide for installing be-shell for the italian chakra forum. The users that tried it reported problems at login ( for some - the ones who used the ccr package ported from aur - plasma continues to start at login, while be-shell run as a background process, for others it gave my same problem).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If kwin crashes, that's a kwin bug (only) - please file a bug against kwin.
The wallpaper is (i think by default) also placed on the rootwindow with the desktop, so be.shell apparently has started. If it crashed, you should always get a crash handler (dialog to restart) and DrKonqui (with a backtrace to inverstigate on the crash) afterwards -> file a bug against be.shell with the corresponding backtrace.
Otherwise ensure the process is really not running ("ps ax | grep be.shell" on VT1 or similar) because be.shell refuses to start twice.
Also if kwin and be.shell constantly crash on the very first startup, this may -depending on how you start- be related to the session dbus (both are kuniqueapplications and by this require the session dbus to check for an instance)
While both should actually wait for the bus, this might fail - notably if you altered the destop service file. This line
X-DBUS-StartupType=wait
is crucial. If both applications don't wait for the bus while the line is there, that's a bug in kdeinit (but should hit plasma just as well)
If plasma starts and be.shell starts (not as "background process", but likely before plasma, thus below in the window stack) that could mean there's a plasma entry in the session history "~/.kde/share/config/session"
If plasma starts and be.shell does not, the desktop service files are not interpreted, most usually due to ~/.kde ./. ~/.kde4 confusion
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, sorry for the lag, but if before i had less time, now i have no time :|
My apologizes: i'm in the middle of a house move, and i'm moving to the other side of the country, so i forgot to reply to this discussion, even if i was able to use the pc some days. So, again, thanks for your time - i appreciate.
Still here with this problem. I have to say that since i've your message, a month ago, i did not received crash error messages anymore . However the problem at the first startup persists....I checked the files to copy to the autostart folder: the line
X-DBUS-StartupType=wait
Is there for all of them. So i thought maybe the files from the first installation from AUR are still in the directory where they were copied during the installation, and that might interfere with the clean execution of the shell.
THe files i'm referring were copied into /usr/share/autostart/ , don't know if they are the original from kde or the copied ones:
I have to say that since i've your message, a month ago, i did not received crash error messages anymore . However the problem at the first startup persists
So is there a crash or is there not. Do kwin AND be.shell crash on this startup?
Is there a session bus up at that time?
The files i'm referring were copied into /usr/share/autostart/
Those are shadowed by the files in the user path.
There's also plasma.desktop, current, a line:
That's to hide stuff from legacy plasma installations, i assume
Don't know how to fix this problem or what causes it :(
check ~/.xsession-errors (right after the failed initial first login, move to VT1 and read it from there), it it's about dbus and kunique application, you'll find stuff that says sth. like "couldn't connect to kwin it probably crashed" or so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The session errors say kwin crashed and on a wild guess (io error and only on first X11 usage) i'd on a wild guess say:
try replacing nouveau with the nvidia blob
the GPU firmware is likely not correctly initialized at that time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding the initial kwin crash - that's very likely related to the bespin decoration, kwin now starting up threaded and both go for a fight on the compositing state.
I delayed the check on the compositor state by 250ms and expect this to solve the issue.
Can you please update the bespin deco, recompile it and check the result?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It worked!
Now there's no problem at the startup, it just works fine!
Another thing: i updated BE::Shell yesterday. I missed some of the last revisions since for weeks i didn't had an internet connection, and neither time to be at the pc.
I really appreciate the fix to globalmenu,and the support to kwin slide effect.
I noticed that there is a lower consumption of ram too ( on 2 gb it was at 40% of usage. Now it is at 26%) =)
Thank you Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fortunately no =|
Stupid me (i have to be more specific the next time),
i mostly see the ram consumption from the RamMeter of BE::Shell,
which measures the active ram usage of the whole session.
Btw i did not remember the exact amount for the Shell before,
but it was high (confronted to the actual one),
and i'm saying this beacuse i have a weird story
of high ram consumption with Linux running on my awful computer!
Now it's 15.180 kb at an uptime of 58 mins.
Last edit: Hombremaledicto 2012-11-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello there, i just wanted to report these problems i had after a fresh installation of chakra, and now with arch:
The first one is that in ~/.kde4/autostart/ there aren't any file to overwrite to start be-shell instead of plasma.
The second is for the taskbar (and the buttons in it): mode and buttonmode are both set to 1, and every button is set to display a custom label - this worked till the new installations. Now the buttons display the custom labels only when the app is closed, otherwise it shows the window title (the config is the same than before)
Last edit: Hombremaledicto 2012-08-31
From AUR?
The be.shell install contains a message on how to replace plasma - it's not done automagically (as is not with the regular installation routine)
Matter of habits.
Second one was actually a bug which lead the taskbuttons not to align to the actual window, ie. it's expected that the button matches the window title (unless of course there's no window)
There's no message from the aur package, nor by compiling from source.
... must the files in be.shell directory be copied into usr/share/autostart and overwrite? sorry maybe the question is really stupid :S
Or maybe disable the plasma desktop autostart in systemsettings autostart tab ?
Last edit: Hombremaledicto 2012-09-01
It seems i made it: i did not found the autostart folder in ~/.kde4/share/ (there wasn't one) in my previous installations or by compiling. After reinstalling the package from aur this time it was there,and so i copied the files from usr/share/beshell/examples. The only weird thing is that after logout/login there wasn't plasma (of course) nor be.shell. I had to start x manually from a console session... and finally a be.shell session without plasma greeted me!
(i've also checked the " start empty session " option in systemsettings btw)
Thank you for your time, and sorry if i continue to annoy you.
Now i'm happy again :P
Last edit: Hombremaledicto 2012-09-02
Sorry, i didn't get this was actually a help request (but took it for an "AUR installation doesn't work" report)
Did you also copy be.shell.desktop to the autostart?
https://sourceforge.net/p/be-shell/wiki/Installation/
Don't worry, i apologize for the delay, i've got less time than before for sitting at the pc.
Yes, i copied all the 3 files to ~/.kde4/share/autostart/ but at every startup the first login displays only the wallpaper chosen from be-shell and a message error that says that kwin crashed (in fact no decoration on the window). I have to logout or enter in console mode, login, and startx manually to start be-shell. The problem is also solved with a second graphical login from kdm.
Days ago i also wrote a guide for installing be-shell for the italian chakra forum. The users that tried it reported problems at login ( for some - the ones who used the ccr package ported from aur - plasma continues to start at login, while be-shell run as a background process, for others it gave my same problem).
If kwin crashes, that's a kwin bug (only) - please file a bug against kwin.
The wallpaper is (i think by default) also placed on the rootwindow with the desktop, so be.shell apparently has started. If it crashed, you should always get a crash handler (dialog to restart) and DrKonqui (with a backtrace to inverstigate on the crash) afterwards -> file a bug against be.shell with the corresponding backtrace.
Otherwise ensure the process is really not running ("ps ax | grep be.shell" on VT1 or similar) because be.shell refuses to start twice.
Also if kwin and be.shell constantly crash on the very first startup, this may -depending on how you start- be related to the session dbus (both are kuniqueapplications and by this require the session dbus to check for an instance)
While both should actually wait for the bus, this might fail - notably if you altered the destop service file. This line
X-DBUS-StartupType=wait
is crucial. If both applications don't wait for the bus while the line is there, that's a bug in kdeinit (but should hit plasma just as well)
If plasma starts and be.shell starts (not as "background process", but likely before plasma, thus below in the window stack) that could mean there's a plasma entry in the session history "~/.kde/share/config/session"
If plasma starts and be.shell does not, the desktop service files are not interpreted, most usually due to ~/.kde ./. ~/.kde4 confusion
Hi, sorry for the lag, but if before i had less time, now i have no time :|
My apologizes: i'm in the middle of a house move, and i'm moving to the other side of the country, so i forgot to reply to this discussion, even if i was able to use the pc some days. So, again, thanks for your time - i appreciate.
Still here with this problem. I have to say that since i've your message, a month ago, i did not received crash error messages anymore . However the problem at the first startup persists....I checked the files to copy to the autostart folder: the line
X-DBUS-StartupType=wait
Is there for all of them. So i thought maybe the files from the first installation from AUR are still in the directory where they were copied during the installation, and that might interfere with the clean execution of the shell.
THe files i'm referring were copied into /usr/share/autostart/ , don't know if they are the original from kde or the copied ones:
-plasma-desktop.desktop
http://pastebin.com/gtqFw2d6
-krunner.desktop
http://pastebin.com/wUL6nH4a
There's also plasma.desktop, current, a line:
[Desktop Entry]
Hidden=true
The be.shell file is the same of the one in ~/.kde4/share/autostart/ , which contains the 3 files:
be.shell.desktop
[Desktop Entry]
Exec=be.shell
X-DBUS-StartupType=wait
Name=BE::shell
Name[x-test]=xxBE::shellxx
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=0
krunner.desktop
[Desktop Entry]
Exec=krunner
Hidden=true
X-DBUS-StartupType=none
Name=Command Runner
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=1
and plasma-desktop.desktop
[Desktop Entry]
Exec=plasma-desktop
Hidden=true
X-DBUS-StartupType=wait
Name=Plasma Desktop Workspace
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=0
I really don't believe this is the cause, just an idea that passed through my mind. Don't know how to fix this problem or what causes it :(
So is there a crash or is there not. Do kwin AND be.shell crash on this startup?
Is there a session bus up at that time?
Those are shadowed by the files in the user path.
That's to hide stuff from legacy plasma installations, i assume
Hard to say, it behaves differently some times =(
I did as you said,here the response:
http://pastebin.com/KnbvV0DT
The session errors say kwin crashed and on a wild guess (io error and only on first X11 usage) i'd on a wild guess say:
try replacing nouveau with the nvidia blob
the GPU firmware is likely not correctly initialized at that time.
Regarding the initial kwin crash - that's very likely related to the bespin decoration, kwin now starting up threaded and both go for a fight on the compositing state.
I delayed the check on the compositor state by 250ms and expect this to solve the issue.
Can you please update the bespin deco, recompile it and check the result?
Sorry for the lag , again :/
It worked!
Now there's no problem at the startup, it just works fine!
Another thing: i updated BE::Shell yesterday. I missed some of the last revisions since for weeks i didn't had an internet connection, and neither time to be at the pc.
I really appreciate the fix to globalmenu,and the support to kwin slide effect.
I noticed that there is a lower consumption of ram too ( on 2 gb it was at 40% of usage. Now it is at 26%) =)
Thank you Thomas
That is by faar too much - is this the consumption of be.shell or of "just started session" and how do you measure it?
What??? No no....
Fortunately no =|
Stupid me (i have to be more specific the next time),
i mostly see the ram consumption from the RamMeter of BE::Shell,
which measures the active ram usage of the whole session.
Btw i did not remember the exact amount for the Shell before,
but it was high (confronted to the actual one),
and i'm saying this beacuse i have a weird story
of high ram consumption with Linux running on my awful computer!
Now it's 15.180 kb at an uptime of 58 mins.
Last edit: Hombremaledicto 2012-11-03