Public bug reported:
Binary package hint: xorg
start
end
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
Uname: Linux 2.6.34-999-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun May 2 14:25:49 2010
EcryptfsInUse: Yes
ProcEnviron:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47247988/Dependencies.txt
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/47247989/RelatedPackageVersions.txt
--
pointer selection is ineffective
https://bugs.launchpad.net/bugs/573628
You
** Description changed:
Binary package hint: xorg
- start
+ The “Appearance Preferences” applet offers the option to “Customize” the
+ display theme. When using this option, the last tab of the “Customize
+ Theme” dialog offers customization of the pointer (mouse cursor) theme.
+ Several
Sorry for being off-topic, but isn’t the -proposed repository useful for
making such fixes available during freezes?
--
(Needs 195.36.15) X crashes during suspend/resume
https://bugs.launchpad.net/bugs/534754
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags added: apport-collected
--
After suspend, screen is dead until switching terminals
https://bugs.launchpad.net/bugs/530622
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
That said, during the last week or so the behavior of the bug changed:
the screen is still blank and I have to play with Ctrl-Alt-F7 to turn it
on, but now I’m always sent to the GDM login window. I’m not sure what
happens with the suspended session, I don’t see crash reports after the
login,
I just tried that, and I encountered bug #516381, several times. Example
output with GTK_DEBUG=all at
https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/516381/comments/5
(Tangential: how can I make a wiki-style link in these comments, ie have
something else than the link address
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047
Hmm. I’ll have to do some more testing. After sending the bug report I
noticed that indeed the Return key caused the problem, so I’ve just
uninstalled Plymouth a few days ago.
This is what’s in my apt’s
Public bug reported:
Hello! I just updated to Lucid, and I've been noticing a bug.
I have my computer set-up to login automatically. This seems to work:
the login process works correctly, I can start some applications. The
problem is that _sometimes_ (I'm 95% sure it doesn't happen every time)
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/40243804/BootDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40243805/Dependencies.txt
** Attachment added: GdmLog.txt
http://launchpadlibrarian.net/40243806/GdmLog.txt
** Attachment added:
Public bug reported:
Binary package hint: xorg
Hello!
I recently updated to Lucid. I noticed this problem:
When I suspend the computer, everything seems OK. However, when I
resume, the screen remains turned off. I can see the system turned
on—for example, the numlock key turns the LED on and
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39955937/Dependencies.txt
--
After suspend, screen is dead until switching terminals
https://bugs.launchpad.net/bugs/530622
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
** Description changed:
Binary package hint: xorg
Hello!
I've just updated to Lucid*; the most visible change is that suspend
stopped working correctly. Actually, suspend works, but resuming seems
to have a problem. First, when resuming the screen doesn't turn on
- immediately;
** Tags added: lucid
** Tags removed: karmic
--
After suspend, screen is dead until switching terminals
https://bugs.launchpad.net/bugs/530622
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
** Tags added: lucid
** Tags removed: karmic
--
garbage on screen after suspend
https://bugs.launchpad.net/bugs/528138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
Public bug reported:
Binary package hint: xorg
Hello!
I've just updated to Lucid*; the most visible change is that suspend
stopped working correctly. Actually, suspend works, but resuming seems
to have a problem. First, when resuming the screen doesn't turn on
immediately; I lost patience every
** Attachment added: Screenshot right after resume
http://launchpadlibrarian.net/39799676/Screenshot-3.png
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/39799677/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
** Attachment added: same computer after restarting Nautilus
http://launchpadlibrarian.net/39800396/Screenshot-5.png
--
garbage on screen after suspend
https://bugs.launchpad.net/bugs/528138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
** Description changed:
Binary package hint: xorg
Hello!
I've just updated to Lucid*; the most visible change is that suspend
stopped working correctly. Actually, suspend works, but resuming seems
to have a problem. First, when resuming the screen doesn't turn on
- immediately; I
** Attachment added: lspci -vvnn.txt
http://launchpadlibrarian.net/28040871/lspci%20-vvnn.txt
--
application icons mangled after suspend
https://bugs.launchpad.net/bugs/364590
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
I've added the lspci output.
The bad news is that I can't attach the Xorg.log file; the good news is
that it's because I can't seem to reproduce the bug anymore :D
I don't use the laptop that often these days, so I can't tell which
update fixed it. But it seems fixed: I tried to suspend several
At least in my case they're working now. However I've customized my
keyboard settings a lot since, I'm not sure if it's because of that.
--
Keyboard Layout options: The X86AudioRaiseVolume button stopped working in
Logitech keyboard models
https://bugs.launchpad.net/bugs/35824
You received this
For the record, I get the exact same tearing behavior I described
originally with 180.* drivers (even earlier ones IIRC) and with
185.18.10.
Also, with mplayer at least it happens similarly with VDPAU and with
other output methods (xv, x11 and opengl). The tearing is not exactly
similar in that
23 matches
Mail list logo
