Thank you Martin.
I've upgraded from 2.20.10-ubuntu5 and the process has renamed custom,
deleted some obsolete conffiles and installed the new ones. Gdm action
"reload" failed but installation finished correctly without closing any
active screen. When trying to reboot the system asked me for
autho
I've reported to bugzilla.gnome.org
(http://bugzilla.gnome.org/show_bug.cgi?id=587732)
** Bug watch added: GNOME Bug Tracker #587732
http://bugzilla.gnome.org/show_bug.cgi?id=587732
--
'These windows do not support "save current setup"' metacity warning when
logging in with gdm 2.26
http
** Attachment added: "0.log"
http://launchpadlibrarian.net/28682674/0.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment added: "0-slave.log"
http://launchpadlibrarian.net/28682672/0-slave.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of Ubuntu
D
** Attachment added: "0-greeter.log"
http://launchpadlibrarian.net/28682666/0-greeter.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of Ubun
** Description changed:
Binary package hint: gdm
Yesterday I did upgrade from gdm 2.20.10-0ubuntu5 to gdm 2.26.1-0ubuntu2
on my HP2133 netbook.
Ubuntu 9.10
Kernel: 2.6.31-1-generic
GNOME: 2.27.3
After rebooting erratic behavior is observed:
1) login is asked in correct
Public bug reported:
Binary package hint: gdm
Yesterday I did upgrade from gdm 2.20.10-0ubuntu5 to gdm 2.26.1-0ubuntu2
on my HP2133 netbook.
Ubuntu 9.10
Kernel: 2.6.31-1-generic
GNOME: 2.27.3
After rebooting erratic behavior is observed:
1) login is asked in correct resolution (1024x600). I'm
This bug also affected me more or less in the same way.
On a clean installation I started Evolution for first time and it
crashed like mentioned by Khorne. Tried some more times with the same
result.
After running Evolution on valdrind it started normally. I setup my
account against exchange and
** Package changed: gnome-power-manager (Ubuntu) => devicekit-power
(Ubuntu)
--
cannot suspend, GpmControlError.Code0: Cannot suspend as not allowed from
policy Failed
https://bugs.launchpad.net/bugs/393021
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Martin, I had the same problem, but it's now solved in the lastest
devicekit-power package update (008-1ubuntu2).
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Fix Released
--
cannot suspend, GpmControlError.Code0: Cannot suspend as not allowed from
policy Failed
https://bu
10 matches
Mail list logo