We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
session start takes very long
https://bugs.launchpad.net/bugs/184977
You received this bug notification because you are a member
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? May you please try the same with Karmic? Thanks in advance.
--
session start
Since it's been a very long time since any additional info was added to
this bug, I'm just checking to see if this is still an issue, and find
out what additional work should be done on this bug.
--
session start takes very long
https://bugs.launchpad.net/bugs/184977
You received this bug
Hi Thomas,
Thomas Koechli [2008-04-29 18:58 -]:
I think it was after the Upgrade for Gutsy, when I had such a delay
in the boot process for the first time. Could it be that Gutsy was
the first release which had compiz enabled by default?
Indeed it was.
I do think that the problem at
No more compiz packages on the system as I can see.
[EMAIL PROTECTED]:~$ sudo aptitude search compiz
[sudo] password for thomas:
p compiz
p compiz-bcop
p compiz-core
p compiz-dev
p compiz-fusion-bcop
c compiz-fusion-plugins-extra
c compiz-fusion-plugins-main
p compiz-gnome
p
how exactly did you switch to xfwm4 ?
gnome-session tries to start the WM it finds in the
/desktop/gnome/applications/window_manager/current
and
/desktop/gnome/applications/window_manager/default
gconf keys usually,
try setting xfwm4 there (with gconf-editor) instead of whatever you use
to
Hi Oliver
That's exactly how I changed the window manager. And I just checked
again my settings with gconf-editor and it showed for both of them
(current and default) the path to xfwm4.
I changed window manager on feisty and had no problems what so ever. I
upgraded then to gutsy when it was
** Summary changed:
- gnome-volume-manager hang on session start (Gutsy)
+ session start takes very long
--
session start takes very long
https://bugs.launchpad.net/bugs/184977
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks. One common reason for such delays are a missing loopback network
device and a totally wrong system clock. What is the output of
ping -c 1 localhost
date
? Does the ping work and is the date reasonable? (I. e. not 1970 or so).
Also, your sesssion seems to be a wild mix of GNOME and
Hi Martin
localhost and date are ok.
As I already told I'm using this with the first user account on the system,
going with xfcewm4 as window manager. No problem with the account created for
my girlfriend some time later using the standard metacity window manager.
I will later post a bootchart
** Attachment added: bootchart of the scond (standard) account
http://launchpadlibrarian.net/14023669/hardy-20080429-2.png
--
session start takes very long
https://bugs.launchpad.net/bugs/184977
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
12 matches
Mail list logo
