And somehow, now it's just working for me a few restarts later. Not sure
what exactly did it. Closing.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launch
Public bug reported:
I can hear the login sound, so I know it booted that far.
If I start in rescue mode, and then pick (I believe it was) failsafe
graphics, it does work and comes up at a low resolution.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignat
It seems that an automatic system closed this bug, even after I
confirmed it still happens.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/894600
Title:
Xorg freeze with neauvou
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/894600/+su
Public bug reported:
The facts:
Xorg freezes.
No display corruption
Mouse moves but does not change like it should (for example when over text).
Alt+SysRQ+R, then Alt+SysRQ+K kills X and lets me log in again.
Happens only with Unity, not unaccelerated environments.
Using Neauvou driver on 11.10.
W
@Bryce Harrington:
I just tried it. It still happens on Oneiric with the Nvidia Driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/846089
Title:
Xorg freeze: logging in wi
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/874819
Title:
Xorg doesn't dectect 1600x1200 resolution for VGA-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
Xorg didn't detect that my screen could do 1600x1200. I have to set it
each time I log in with "xrandr --addmode VGA-1 1600x1200" and then use
the display configuration tool to use the larger resolution.
(Hopefully apport gives you the info you need to know. I don't know what
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/846089
Title:
Xorg freeze: logging in with unity, compiz freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
Public bug reported:
Upon freshly installing Natty and moving all the /home data from a
Maverick install, GLX acceleration no longer works. When I login with
either the Unity or Ubuntu Classic, the screen will change, sometimes
even showing the unity panel. However, it freezes and it unresponsive
@ harrier
What drivers are you using?
@fejes
Do you have a synaptics touchpad? The machine I had this bug occur on has a
synaptics touch pad and harrier's backtrace appears to mention some synaptics
driver stuff.
--
You received this bug notification because you are a member of Ubuntu-X,
whic
Ok, well I guess I'll just let this bug be until they decide that they are
ready to take bug reports.
To tell the truth, I tried these drivers about 6 months ago and I was impressed
by how well they work now. So far, this bug was the only thing wrong with them.
The bug happens so rarely that th
** Description changed:
- It seems that Xorg will eventually lock up, using 100% CPU and not updating
the screen, after the computer is running for a couple of hours. The only way
to get out of it is kill Xorg.
+ It seems that Xorg will eventually lock up, using 100% CPU and not updating
the sc
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
https://bugs.launchpad.net/bugs/714937
Title:
Natty:Xorg uses 100% CPU
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Public bug reported:
It seems that Xorg will eventually lock up, using 100% CPU and not updating the
screen, after the computer is running for a couple of hours. The only way to
get out of it is kill Xorg.
I'm using the Nvidia Experimental 3D drivers from Jockey.
Let me know if there is any way
** Description changed:
Binary package hint: xorg
- On my Nvidia Geforce Go 6100, the text in the Ctrl Alt Fx consoles
- flicker. By flicker, I mean that the text moves up and down a few pixels
- multiple times a second. This happens continually, but the exact
- subsecond spacing of the move
** Description changed:
Binary package hint: xorg
- On my Nvidia Geforce Go 6100, the text in the Ctrl Alt Fx consoles
- flicker. By flicker, I mean that the text moves up and down a few pixels
- multiple times a second. This happens continually, but the exact
- subsecond spacing of the move
** Description changed:
Binary package hint: xorg
On my Nvidia Geforce Go 6100, the text in the Ctrl Alt Fx consoles
flicker. By flicker, I mean that the text moves up and down a few pixels
multiple times a second. This happens continually, but the exact
subsecond spacing of the move
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44398629/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44398630/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44398631/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
On my Nvidia Geforce Go 6100, the text in the Ctrl Alt Fx consoles
flicker. By flicker, I mean that the text moves up and down a few pixels
multiple times a second. This happens continually, but the exact
subsecond spacing of the movement seems to b
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44398629/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44398630/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44398631/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
On my Nvidia Geforce Go 6100, the text in the Ctrl Alt Fx consoles
flicker. By flicker, I mean that the text moves up and down a few pixels
multiple times a second. This happens continually, but the exact
subsecond spacing of the movement seems to b
** Tags added: amd64 lucid
--
nvidia doesn't support randr-1.2
https://bugs.launchpad.net/bugs/148428
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in ubuntu.
___
Mailing
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Fix Released
--
X display corruption switching users, uses 100% CPU, seg faults
https://bugs.launchpad.net/bugs/500066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubu
This seems to not happen to me anymore with the live image from around
2-28-10. If it happens to you go ahead and reset it to new or confirmed.
--
X display corruption switching users, uses 100% CPU, seg faults
https://bugs.launchpad.net/bugs/500066
You received this bug notification because you
** Tags added: amd64
--
There is no way to rotate a display using nvidia proprietary drivers
https://bugs.launchpad.net/bugs/527428
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in ubuntu.
_
So is this fixed, or does the nvidia-graphics-drivers package need
updating too?
--
Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to menu after
installing nvidia driver until you re-login
https://bugs.launchpad.net/bugs/522969
You received this bug notification because you are a m
Works in Lucid, Not in karmic, at least using the link Jouni Mettala
posted.
--
Multi-Pointer X Window Server
https://bugs.launchpad.net/bugs/220036
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
This is the (multiple) backtraces from when I reproduced the bug a
second time.
BTW: If you need more info, just ask (well, and tell me how to get it)
Thanks ubuntu devs, you do a great job.
** Attachment added: "Second session gdb backtrace"
http://launchpadlibrarian.net/37151266/gdb-2Xorg.t
This file resulted after I continued in the first file when I should
have tried to get a backtrace. So I kill all gdbs and started a new gdb,
and reattached it, and got this file.
** Attachment added: "Gdb stack trace, first session, second file"
http://launchpadlibrarian.net/37151219/gdb-Xorg-
** Attachment added: "Gdb stack trace, first session, first file"
http://launchpadlibrarian.net/37151151/gdb-Xorg.txt
--
X display corruption switching users, uses 100% CPU, seg faults
https://bugs.launchpad.net/bugs/500066
You received this bug notification because you are a member of Ubuntu
** Description changed:
To reproduce this bug (on Lucid):
1. login to a user. (We'll call it user #1)
2. Go to switch users
3. Login to another user (i.e. user #2)
4. Go to switch users
5. Try to login to user #1
- 6. Notice screen corruption. Try sshing in and running top. Notice Xorg
** Attachment added: "Screen corruption snapshot for step 6"
http://launchpadlibrarian.net/37150804/DSCF3708.JPG
--
X display corruption switching users, uses 100% CPU, seg faults
https://bugs.launchpad.net/bugs/500066
You received this bug notification because you are a member of Ubuntu-X,
w
** Description changed:
To reproduce this bug (on Lucid):
1. login to a user. (We'll call it user #1)
2. Go to switch users
3. Login to another user (i.e. user #2)
4. Go to switch users
5. Try to login to user #1
6. Notice screen corruption. Try sshing in and running top. Notice Xor
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/37150340/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/37150341/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37150342/Dependencies.txt
** A
Public bug reported:
To reproduce this bug (on Lucid):
1. login to a user. (We'll call it user #1)
2. Go to switch users
3. Login to another user (i.e. user #2)
4. Go to switch users
5. Try to login to user #1
6. Notice screen corruption. Try sshing in and running top. Notice Xorg
processes using
36 matches
Mail list logo
