I am still being prompted to log in while gnome is loading (with login
screen disabled)
--
gdm 2.26 locks running session on Jaunty upgrade
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubun
This bug was fixed in the package gdm - 2.26.1-0ubuntu3
---
gdm (2.26.1-0ubuntu3) karmic; urgency=low
* Add 03_hide_system_users.patch: Do not show system users in the "frequent
users" list. (LP: #395281)
* debian/rules: Call dh_installinit with --no-scripts, to avoid restarti
** Changed in: gdm (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
gdm 2.26 locks running session on Jaunty upgrade
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a membe
It's entirely possible that this is just a side effect of bug 395302.
I'm going to test the 2.20 -> 2.26 upgrade again with that bug fixed.
--
gdm 2.26 locks running session on Jaunty upgrade
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubu
** Changed in: gdm (Ubuntu)
Importance: Low => Medium
** Changed in: gdm (Ubuntu)
Status: Incomplete => Triaged
** Summary changed:
- gdm 2.26 kills or switches away from active X sessions on upgrading
+ gdm 2.26 locks running session on Jaunty upgrade
--
gdm 2.26 locks running sessi
OK, I just upgraded another machine from gdm 2.20 to 2.26, and can
confirm that for that upgrade, the new gdm is erroneously started on vt8
/ X screen :1 whilst the previous session remains happily alive on vt7 /
:0.
I am attaching apt-term.log from that upgrade - in particular I find it
suspiciou
My 2 cents:
The first upgrade gave me a new login screen and I stayed logged in like
everybody else.
Now for the second one... I don't think It killed the session but simply logged
out. At least aptitude that was running in yakuake didn't get killed until all
updates were processed and firefox
The "7" should be "&"
--
gdm 2.26 kills or switches away from active X sessions on upgrading
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs
I had update-manager minimized whilst I was doing a forum posting (about
this problem) & the ?random? typing b0rked things rather well...I
rebooted 7 everything came back---but it now looks more like the Fedora
login--so I would gather that something was lost in passing..
--
gdm 2.26 kills or
I had to alt F1. logged in on that console. "sudo /etc/init.d/gdm
restart" got back to the greeter.
--
gdm 2.26 kills or switches away from active X sessions on upgrading
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
for me on amd64 it killed X , I had to alt F1 and startx from a console
screen it dumped me into , cmds were visible and the last one had not
returned in that console . pannels were overlapped on the desktop with a
partial bottom panel sitting on top of the top panel .
--
gdm 2.26 kills or switch
For my gdm 2.20 to 2.26 upgrade I'm not sure - my experience was that I
was taken from my X session to a new-style gdm, and on logging in, back
to my previous X session.
For my gdm 2.26.1-0ubuntu1 to -0ubuntu2 upgrade, it definitely killed my
session outright.
--
gdm 2.26 kills or switches away
did it actually close the session or just switch vts?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
** Changed in: gdm (Ubuntu)
Status: Confirmed => Incomplete
--
gdm 2.26 kills or switches away from active X sessions on upgrading
https://bugs.launchpad.net/bugs/395313
You
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28670581/Dependencies.txt
--
gdm 2.26 kills or switches away from active X sessions on upgrading
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
This also happens with x86--during upgrade, xsession will close without
warning. There NEEDS to be a disclaimer or warning about this--I lost
work by doing a update in the background & then GDM updated.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
gdm 2.26 kills or switches awa
Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gdm 2.26.1-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-1.14-generic
Uname: Linux 2.6.31-1-generic i686
UserGroups: adm
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28670406/Dependencies.txt
--
gdm 2.26 kills or switches away from active X sessions on upgrading
https://bugs.launchpad.net/bugs/395313
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
Public bug reported:
Binary package hint: gdm
On upgrading from gdm 2.20 to 2.26, I was ejected from my X session, but
on logging in, was returned to the same session.
On upgrading from gdm 2.26.1-0ubuntu1 to -0ubuntu2, my X session was
killed outright.
ProblemType: Bug
Architecture: amd64
Date
18 matches
Mail list logo
