Fabián Rodríguez, this bug report is being closed due to your last
comment https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/569948/comments/21 regarding you no longer have the original
hardware. For future reference you can manage the status of your own
bugs by clicking on the current st
I don't use Ubuntu anymore nor do I have access to this particular
hardware anymore.
I suppose anyone using Lucid at the time has long since upgraded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/569
Fabián Rodríguez, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live
FWIW, I have the exact same symptom with Lucid on a amd64 Thinkpad with:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
Subsystem: Lenovo Device 20e4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- P
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/569948
Title:
No, nothing works. When the screen is blank / black (one of both logged
in users logs out) then there ist only one possibility: to press reset
button. There's nothing else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
once you get the blank screen, does ctrl-alt-F7, ctrl-alt-F8, ctrl-
alt-F9, ctrl-alt-F10, ... get you back to a graphics console? does ctrl-
alt-F1 through F6 get you to a text login console where you can restart
the gdm service as root?
I often see that on our multi-user systems upon user logout;
Is this bug : https://bugs.launchpad.net/ubuntu/+source/libpam-
usb/+bug/558451 related ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/569948
Title:
When multiple users login, GDM doesn't come back
I get this crash all the time (10.10) and I think that it might be
related to inserting and removing usb flash drives and having multiple
users logged in. It's intermittent so I'll see if I can reproduce it
consistently.
** Changed in: xorg-server (Ubuntu)
Status: Expired => New
--
You re
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
...like all xorg logs in one file
** Attachment added: "xorg.log"
http://launchpadlibrarian.net/49008460/xorg.log
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpad.net/bugs/569948
You received this bug n
some files...
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/49008145/lspci.txt
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpad.net/bugs/569948
You received this bug notification becaus
My Lucid has the same problem. My system is running with a nVidia too.
Don't know if this video card causes that problem.
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpad.net/bugs/569948
You received this bu
I have the same problem here, on a new 10.04 system with a Nvidia
GeForce FX 520 graphics card...
What data is missing here? Why is this bug set to incomplete?
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchp
As a workaround if I don't logout but rather only switch users, there is
no data loss. I will send my logs later today.
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpad.net/bugs/569948
You received this bug
And here is the output of lspci -vvnn :
00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM
Controller/Host-Hub Interface [8086:2560] (rev 03)
Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:9055]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV
I have the same problem.
I installed lucid from a CD, keeping my /home installed on karmic on a
different partition.
As the reporter of this bug doesn't send the xorg logs, I send mine.
These are the logs obtained after I had to manually reboot due to the crash.
** Attachment added: "xorg-logs.ta
Hi Fabián,
Thanks for including the attached files. Could you also include your
/var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?
Please attach the output of `lspci -vvnn` too.
[This is an automated message. Apologies if it has reached you
inappropriately; please just
thank you for your bug report, xrog crashing on xsession switch is an
xorg issue though not a gdm one
** Package changed: gdm (Ubuntu) => xorg-server (Ubuntu)
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpa
I removed the nvidia proprietary drivers and tested again with the
Nouveau drivers. This lead to almost the same result: black screen,
although with responsive mouse cursor, can't access console, can't login
to previously logged users, however X could be restarted
(CtrlAltBackspace was previously e
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45393253/Dependencies.txt
--
When multiple users login, GDM doesn't come back after any of them logs out
leading to DATA LOSS for the others
https://bugs.launchpad.net/bugs/569948
You received this bug notification because
21 matches
Mail list logo
