Thank you for taking the time to report this issue and help to improve
Ubuntu.
There is no bug here; the acl binary package in karmic was in universe,
not in main. It has been promoted to main in Lucid as a conscious
decision of the server team, but this doesn't change that it wasn't in
main for
I'm pleasantly surprised to report that this bug seems to be resolved
now, it's no longer reproducible for me.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Fix Released
--
[i945GM] X server segfault on lid close
https://bugs.launchpad.net/bugs/494680
You received this bug
It would be nice indeed, but some users have gotten the idea that it's
appropriate to run apport-collect against bugs unsolicited, and everyone
cc:ed on the bug receives notifications of the new attachments. I'm
afraid there's not much that can be done about this problem in the short
term.
--
please don't change bug statuses without explanation.
** Changed in: xorg (Ubuntu Lucid)
Status: In Progress = Fix Released
--
Failsafe X support added in proposed upload still doesn't work
https://bugs.launchpad.net/bugs/477149
You received this bug notification because you are a member
** Changed in: linux (Ubuntu Lucid)
Milestone: ubuntu-10.04 = ubuntu-10.04-beta-1
--
[lucid] desktop runs out of video memory on ATI Radeon Mobility 7500
https://bugs.launchpad.net/bugs/507148
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned) = Steve Conklin (sconklin)
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because
** Changed in: linux (Ubuntu)
Assignee: Steve Conklin (sconklin) = (unassigned)
--
Elantech touchpad is incorrectly recogonised as a ImPS/2 Logitech Wheel Mouse
https://bugs.launchpad.net/bugs/123775
You received this bug notification because you are a member of Ubuntu-X,
which
*** This bug is a duplicate of bug 506717 ***
https://bugs.launchpad.net/bugs/506717
** Package changed: nvidia-graphics-drivers (Ubuntu) = plymouth
(Ubuntu)
** This bug has been marked a duplicate of bug 506717
[Lucid] plymouth does not display when using nvidia drivers
--
Lucid
*** This bug is a duplicate of bug 426582 ***
https://bugs.launchpad.net/bugs/426582
I've marked this as a duplicate of bug #426582. It's a problem with the
new Xorg and ATI Radeon 7500 chipsets. There's a few workarounds noted
on the other bug report.
** This bug has been marked a duplicate
The freeze happens /at/ the kernel level. If mesa can cause this, it's
still a bug in the kernel driver for permitting it to get into that
state. :)
--
[i945] another happy X freeze in karmic [i945GM]
https://bugs.launchpad.net/bugs/445719
You received this bug notification because you are a
Yes, there is a task open on this bug report for the gdm-2.20 package,
but it doesn't appear that anyone has taken responsibility yet for
fixing the bug there.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
** Also affects: mesa (Ubuntu Lucid)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: Triaged
** Changed in: mesa (Ubuntu Lucid)
Importance: Medium = High
** Changed in: mesa (Ubuntu Lucid)
Milestone: None = lucid-alpha-3
--
Some GL apps won't run:
dmesg shows:
[ 213.812640] [TTM] Failed moving buffer. Proposed placement 0x00060004
[ 213.812650] [TTM] Out of aperture space or DRM memory quota.
[ 213.812660] [drm:radeon_object_create] *ERROR* Failed to allocate TTM object
(5914624, 0x00060004, 0)
[ 213.812667]
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
I updated Karmic just now, after not having done so for several weeks.
After rebooting after the update, and logging back in, I find that edge-
scrolling on the laptop's touchpad no longer works. Nor does tap-in-
corners.
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37788539/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37788540/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37788541/Dependencies.txt
**
** This bug is no longer a duplicate of bug 494627
nv driver crashing with segmentation fault in libpthread.so.0
--
[i945GM] X server segfault on lid close
https://bugs.launchpad.net/bugs/494680
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Doh, happened again here, running the new X server; not on lid close,
but perhaps when the screensaver was set to start based on idle time,
after I had previously plugged in a VGA display and subsequently
disconnected it. So not entirely fixed, though as I still can't
reproduce it when plugging
Where do you see that this is related to 3d operations?
I don't think a kernel-level dri freeze can reasonably be considered a
mesa bug in any case.
I'm now running lucid on this laptop and have not seen this freeze with
the current 2.6.32 kernel; that also means I'm unlikely to invest any
time
this issue.
Thanks,
Steve Jerard
stevejer...@gmail.com
ProblemType: Bug
Architecture: i386
CheckboxCommand: resolution_test
CheckboxDescription:
This display is using the following resolution:
$output
Is this acceptable for your display?
CheckboxTest: resolution
Date: Wed Dec 30 05:13:14 2009
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37286846/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37286847/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37286848/Dependencies.txt
**
Apport is enabled on this system. Rather than giving me an apport crash
report, the signal handler apparently hangs indefinitely - I have to ssh
in to the system after the SIGSEGV, confirm the failure in the logs, and
then kill -9 the X server to restart it. Do you have any advice on how
I can
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Invalid
--
Touchpad not working
https://bugs.launchpad.net/bugs/487804
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
Well, things are different now, but not better. I now get the
following crash instead:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1ff8]
1: /usr/bin/X (0x40+0x64cd9) [0x464cd9]
2: /lib/libpthread.so.0 (0x7fe199d5b000+0xf190) [0x7fe199d6a190]
3: /usr/bin/X (xf86GetGammaRampSize+0x75)
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
--
[i945GM] X server segfault on lid close
https://bugs.launchpad.net/bugs/494680
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
** Also affects: xserver-xorg-video-nv (Ubuntu Lucid)
Importance: Undecided
Status: New
--
nv driver crashing with segmentation fault in libpthread.so.0
https://bugs.launchpad.net/bugs/494627
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Changed in: xserver-xorg-video-nv (Ubuntu Lucid)
Importance: Undecided = Critical
** Changed in: xserver-xorg-video-nv (Ubuntu Lucid)
Importance: Critical = High
** Changed in: xserver-xorg-video-nv (Ubuntu Lucid)
Milestone: None = lucid-alpha-2
--
nv driver crashing with
Public bug reported:
Binary package hint: xorg
X segfaulted on me when I closed my laptop lid. Backtrace included in
Xorg.0.log.old; no apport collection since apport is not yet enabled by
default in lucid.
ProblemType: Bug
Architecture: amd64
Date: Wed Dec 9 11:25:52 2009
DistroRelease:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/36635354/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/36635355/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36635356/Dependencies.txt
**
This bug report has nothing to do with gdm+kdm causing failsafe-X to
start, that was a regression introduced *after* this bug was filed.
Please do not hijack this bug report for unrelated issues.
** This bug is no longer a duplicate of bug 491483
Since failsafe-x was enabled in karmic it
** This bug is no longer a duplicate of bug 491483
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm
is used. (low graphics mode error)
--
after ubuntu upgrade computer only works in low graphics mode
https://bugs.launchpad.net/bugs/477288
You received this bug
*** This bug is a duplicate of bug 491483 ***
https://bugs.launchpad.net/bugs/491483
Sensiva,
Your bug report has been marked as a duplicate of a bug specific to
Kubuntu systems that have the gdm package installed. Are you running
Kubuntu, or Ubuntu? Do you still see this issue after
Unmarking this as a duplicate of 491483, because 'nosplash' should have
no effect in that case. Do you have the gdm package installed? Does
enabling gdm instead of kdm fix this problem for you? If so, then it is
a duplicate after all; if not, then this is a separate bug.
** This bug is no
That bug should also be fixed in gdm 2.28.1-0ubuntu2.1; so if you do
have gdm installed, upgrading this should be enough to show if this is
the same bug.
--
[i945gm] Recent update broke graphics
https://bugs.launchpad.net/bugs/491565
You received this bug notification because you are a member of
If you don't have gdm installed, you don't have this bug. The
failsafe-X job is only ever run when gdm tries to run and fails.
I've reviewed the set of bugs marked as duplicates of this one, and un-
duped those that don't match - including bug #459639, which appears to
be the one under
This bug also affected single-user mode.
It affected only systems that had both kdm and gdm installed, with kdm
configured as the preferred DM. Users with only gdm installed were not
affected by this bug, with or without booting in single-user mode,
because the gdm job already exits '0' if it
looks like this is reproducible - closing the lid when I have my
laptop's VGA output connected is enough to trigger it.
** Changed in: xorg (Ubuntu)
Importance: Undecided = Medium
--
[i945GM] X server segfault on lid close
https://bugs.launchpad.net/bugs/494680
You received this bug
*** This bug is a duplicate of bug 426582 ***
https://bugs.launchpad.net/bugs/426582
Since your lspci.txt shows that you have a Radeon Mobility 7500 graphics
chipset, this is definitely bug #426582. See that report for some more
information and possible workarounds.
I am marking this report
I think this is the wrong fix - the gdm job shouldn't exit non-zero when
it's configured to not run, it should instead stop cleanly using '|| {
stop; exit 0; }'.
--
Since failsave-x was enabled in karmic it starts if gdm is disabled and kdm is
used
https://bugs.launchpad.net/bugs/491483
You
Bartosz wrote:
Hi.
Try to enable DRI and disable AIGLX.
This worked for me. I can log into KDE again.
--
[K8M800]with kernel 2.6.31-14-generic my X server crashes during KDE 4.3.2
startup
https://bugs.launchpad.net/bugs/471646
You received this bug notification because you are a member of
** Tags added: regression-release
** Tags removed: regression-potential
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
** Changed in: xorg-server (Ubuntu Karmic)
Status: Confirmed = Fix Committed
--
xvfb-run totally broken
https://bugs.launchpad.net/bugs/481591
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
** Tags added: verification-needed
--
xvfb-run totally broken
https://bugs.launchpad.net/bugs/481591
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Mailing list:
Public bug reported:
Binary package hint: xserver-xorg-video-intel
crashed when cycling video modes rapidly w/ hotkey. backtrace is in the
attached XorgLogOld.
ProblemType: Bug
Architecture: amd64
Date: Wed Dec 2 16:26:58 2009
DistroRelease: Ubuntu 10.04
MachineType: LENOVO 6371CTO
Package:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/36353736/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/36353737/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36353738/Dependencies.txt
**
Hi Martin,
The SRU package in -proposed worked for me. I didn't see any regression,
but I didn't really search for any.
--
Add support for TouchPack family touchscreens (Clevo TN120 series tablets /
ASUS eeeTOP and other devices)
https://bugs.launchpad.net/bugs/401039
You received this bug
Can anyone confirm that this bug is fixed with the new upload?
--
Rename /etc/X11/Xsession.d/60x11-localhost to match convention
https://bugs.launchpad.net/bugs/340807
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
(copied to lucid)
** Changed in: xorg (Ubuntu Karmic)
Status: Fix Released = Fix Committed
** Changed in: xorg (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
Failsafe X support added in proposed upload still doesn't work
https://bugs.launchpad.net/bugs/477149
You received
for the
same
-- Steve Langasek steve.langa...@ubuntu.com Wed, 04 Nov 2009 18:00:49 -0800
** Changed in: xorg (Ubuntu Karmic)
Status: Fix Committed = Fix Released
--
New gdm does not have the FailsafeXServer config option
https://bugs.launchpad.net/bugs/474806
You received this bug
-dependency for the
same
-- Steve Langasek steve.langa...@ubuntu.com Wed, 04 Nov 2009 18:00:49 -0800
** Changed in: xorg (Ubuntu Karmic)
Status: Fix Committed = Fix Released
** Changed in: xorg (Ubuntu)
Assignee: sayadeejay (rodrigo-orellana) = Bryce Harrington
(bryceharrington
I also had Stellarium crash after upgrading on an IBM T30. The video
card is ATI Radeon Mobility M7 LW (AGP) and I was using the radeon
(not ati) X driver. The error reports in dmesg as segfault in
radeon_dri.so
The crash no longer occurs after downgrading libgl1-mesa-dri from
7.6.0-1 to 7.4.0
[Updating] libpciaccess (0.10.6-2ubuntu1 [Ubuntu] 0.10.9-1 [Debian])
* Trying to add libpciaccess...
- libpciaccess_0.10.9.orig.tar.gz: downloading from
http://ftp.debian.org/debian/
- libpciaccess_0.10.9-1.dsc: downloading from http://ftp.debian.org/debian/
-
Upgraded to Karmic and problem no longer exists.
--
Openoffice and compiz result in a corrupted title bar
https://bugs.launchpad.net/bugs/438495
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
*** This bug is a duplicate of bug 426582 ***
https://bugs.launchpad.net/bugs/426582
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 426582, so it is being marked as such. Please look
Just hit this bug again (huh, had a good run). Is this suitable for
backporting to the karmic kernel?
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
I can confirm that the problem also goes away if all the desktop effects
are removed, i.e. set to none. I only had normal enabled before on my
945GME, and observed the problem, so must be something with that
setting.
--
[i945gme] attaching external monitor: laptop display is black, external
In regards to comment #22, in order to run X -configure, you must not
have X running. The best way in my experience to accomplish this is to
switch to a virtual console with Ctrl-Alt-F1, and stop GDM with sudo
/etc/init.d/gdm stop
--
(32MB) certain windows drawn garbled when XAA is used
** Changed in: gdm (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: xorg (Ubuntu Karmic)
Status: New = In Progress
** Changed in: xorg (Ubuntu Karmic)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: xorg (Ubuntu Karmic)
Importance: Undecided = High
** Changed
Karmic)
Status: Won't Fix = In Progress
** Changed in: gdm (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in: gdm (Ubuntu Karmic)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: gdm (Ubuntu Lucid)
Status: Won't Fix = In Progress
** Changed in: gdm
Unless you're expecting an xorg upload soon, we'll probably be able to
copy these packages from karmic-proposed to lucid once built.
--
New gdm does not have the FailsafeXServer config option
https://bugs.launchpad.net/bugs/474806
You received this bug notification because you are a member of
** Tags added: hw-specific
--
[RS482] low performance due to removal of _tnl_ProgramCacheInit()
https://bugs.launchpad.net/bugs/347569
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
___
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Invalid = Fix Released
--
[i965] Dell Studio 15 White Screen on X startup
https://bugs.launchpad.net/bugs/297245
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
I'm not sure what any of it has to do with the xmodmap ~/.Xmodmap bug I
just reported, but I'm attaching the information you requested, anyway.
Bryce Harrington wrote:
Hi srn-coolheads,
Please attach the output of `lspci -vvnn` and `dmesg`, and attach your
/var/log/Xorg.0.log (and maybe
Public bug reported:
Binary package hint: xorg
Something about my screen possibly the resolution could not be found by
fglrx when running System Test under a new install of Ubuntu 9.10
ProblemType: Bug
Architecture: amd64
CheckboxCommand: resolution_test
CheckboxData: unknown (impossible to
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34732380/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34732381/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34732383/Dependencies.txt
**
Public bug reported:
Binary package hint: xorg
I just installed karmic 9.10.
I have a ~/.Xmodmap file in effect; it has been working fine in Jaunty.
The first time I used it in Karmic, I got the usual prompt about whether
I really wanted to use it, and of course I said yes. After that, it
I did a little more testing so I could tell you exactly how to reproduce
the error. Turns out, emacs has nothing to do with it (sorry, I was
confused). Now I think the problem is actually just another problem
with the new gdm, because the problem occurs when I log out and then log
back in.
Here
to recommend installing virtualbox-ose-guest-x11 to get
the vboxvideo driver?
--
Steve Beattie
sbeat...@ubuntu.com
http://NxNW.org/~steve/
--
No safe fallback on broken xorg.conf or missing driver
https://bugs.launchpad.net/bugs/457443
You received this bug notification because you are a member of Ubuntu
to be fixed
is X's differing behavior around a mildly bogus xorg.conf versus a
non-existent one.
However, it does sound like a good idea anyway. Can you please open a
new jockey bug about this? Please assign it to me, jockey bugs are a
mess right now.
Bug 463464 opened, thanks.
--
Steve Beattie
I've been working around this for myself and others by setting AccelMethod to
EXA.
Can I assume that if this works, it's preferable to setting RenderAccel off?
I'm just guessing that disabling RenderAccel would hurt performace, worse than
switching to EXA?
I could use a little clarification here
Documented at
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes#No%20Xv%20support%20for%20Intel%2082852/855GM%20video%20chips%20with%20KMS:
When using the default kernel-mode-setting (KMS) option in Ubuntu 9.10,
users with Intel 82852/855GM cards will find that they are unable to use
the Xv
Mark,
Is it possible for you to confirm whether plugging the monitor into the
other card does cause the crash with white?
If the currently available fix is only going to correct the problem for
any given user 50% of the time, I think we should wait to be able to
address this fully and fix it via
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34284134/BootDmesg.txt
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/34284135/CoreDump.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34284136/CurrentDmesg.txt
** Attachment
Bryce, sorry, the other virtualbox bug number was tyoped, it should be
bug 457443. In neither of the these bug reports was the virtualbox guest
drivers installed; jockey should probably suggest that.
It'd also be nice to know what's causing xorg.conf to get truncated to
0, even if papering over
Public bug reported:
Binary package hint: xorg
Post jaunty-karmic upgrade, X fails to start (repeatedly, thanks to
gdm). Note that this is subtly different than bug 439551; in that bug, a
zero length xorg.conf was the cause of the failure. Whatever was causing
xorg.conf to get truncated to
** Attachment added: Xorg.0.log from working session after deleting xorg.conf
http://launchpadlibrarian.net/34106011/Xorg.0.log
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34106013/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
Public bug reported:
Binary package hint: xorg
Post jaunty-karmic upgrade, X fails to start (repeatedly, thanks to
gdm). Note that this is subtly different than bug 439551; in that bug, a
zero length xorg.conf was the cause of the failure. Whatever was causing
xorg.conf to get truncated to
** Attachment added: Xorg.0.log from working session after deleting xorg.conf
http://launchpadlibrarian.net/34106207/Xorg.0.log
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34106208/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
Whatever it was that was causing xorg.conf to get truncated to 0 bytes
has been fixed (though I suspect X still doesn't like that); however,
virtualbox guest upgrades from jaunty to karmic without the virtualbox
guest tools/drivers installed are result in an X server that fails,
despite the
Bah, sorry, launchpad returned a proxy 502 error the first time I tried
to file this and I ended up refiling this as bug 457443. Closing this
one out.
--
X fails in virtualbox post jaunty-karmic upgrade
https://bugs.launchpad.net/bugs/457306
You received this bug notification because you are a
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
X fails in virtualbox post jaunty-karmic upgrade
https://bugs.launchpad.net/bugs/457306
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
*** This bug is a duplicate of bug 451725 ***
https://bugs.launchpad.net/bugs/451725
Now I can't log into an XFCE session, either. Sigh.
--
Xorg assert failure: X: ../../../libdrm/intel/intel_bufmgr_fake.c:1370:
drm_intel_fake_bo_exec: Assertion `ret == 0' failed.
This bug is resolved. File a new bug for problems you're seeing, this
bug is unrelated.
** Changed in: eglibc (Ubuntu Karmic)
Status: Confirmed = Fix Released
--
[karmic] Xorg (and anything GLX) crashes on startup
https://bugs.launchpad.net/bugs/429003
You received this bug notification
** Changed in: mesa (Ubuntu)
Status: Incomplete = Invalid
--
[r200] xorg crashes in _mesa_PopAttrib()
https://bugs.launchpad.net/bugs/451514
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
** Changed in: xserver-xorg-video-nv (Ubuntu)
Importance: Undecided = Medium
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Won't Fix = Triaged
--
karmic alpha 4's xorg 'nv' driver does not
)
Importance: Medium = Undecided
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Triaged = Confirmed
** Changed in: xserver-xorg-video-nv (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
karmic alpha 4's xorg 'nv' driver does not handle Nvidia 8200
https
Mario, I'd appreciate if you could test whether this PPA package also
still works on the hardware you've previously tested.
--
karmic alpha 4's xorg 'nv' driver does not handle Nvidia 8200
https://bugs.launchpad.net/bugs/413439
You received this bug notification because you are a member of
** Changed in: xserver-xorg-video-nv (Ubuntu)
Importance: Undecided = Medium
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Confirmed = Triaged
--
karmic alpha 4's xorg 'nv' driver does not handle Nvidia 8200
https://bugs.launchpad.net/bugs/413439
You received this bug
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = Medium
--
Intel/KMS: Missing 1024 x 768 mode (regression from Jaunty)
https://bugs.launchpad.net/bugs/432401
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
Marking 'high' based on the severity of the described problem; given
that it's unreproducible now, however, I'm also marking it 'invalid'.
If you are able to reproduce the problem again, please feel free to
reopen.
Note that a new upstream version of compiz was also uploaded on the
14th, so it's
Well, 2.1.14-2ubuntu3 is definitely the version of the nv driver package
that we had in karmic beta. Can you show the Xorg.0.log from this
successful run with -2ubuntu3 installed? Is it possible that the non-
free nvidia driver is running instead?
--
karmic alpha 4's xorg 'nv' driver does not
14:37 slangasek m3ga: can you please check whether this problem is
reproducible with 'sudo pm-hibernate' instead of 'sudo s2disk'? That will let
us establish whether it should be treated as a driver bug, or if uswsusp is
missing quirk handling that pm-utils knows about
14:38 m3ga ok, i'll
Ok, if ubuntu3 is working for you, then we don't really have a confirmed
bug here at this point. Marking incomplete.
One difference I notice in the old vs. new logs is that there's no
mention of an /etc/X11/xorg.conf in the new log - so maybe the
autodetection doesn't work when you have an
Public bug reported:
Binary package hint: x11-xserver-utils
When the Macbook / Macbook Pro keyboard configuration is selected, I get
a popup error:
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33844143/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33844144/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33844145/Dependencies.txt
**
Public bug reported:
Binary package hint: x11-xserver-utils
System test for cycling through video modes does not switch any video
modes (Macbook 2,1)
ProblemType: Bug
Architecture: i386
CheckboxCommand: xrandr_cycle
CheckboxTest: xrandr_cycle
Date: Tue Oct 13 21:28:28 2009
DistroRelease: Ubuntu
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33631718/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33631719/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33631720/Dependencies.txt
**
X definitely isn't starting before usplash quits in karmic; the usplash
upstart job is defined as:
stop on (starting-dm
or stopped rc RUNLEVEL=[2345]
or starting rcS)
and each of {gdm,kdm,xdm} is configured to emit the 'starting-dm' signal
before it starts - so unless you're
This bug occurs for me too, with the same hardware, and I confirm that
the workaround fixes it too.
--
Tablet stylus right-click not recognized
https://bugs.launchpad.net/bugs/446943
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wacom-tools in
Public bug reported:
Binary package hint: xorg
X segfaulted for me when rapidly switching display output configurations
with a hotkey. The segfault was not trapped by apport; a limited
backtrace is available in the attached Xorg.0.log.old, reproduced here:
Backtrace:
0:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33370697/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33370699/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33370700/Dependencies.txt
**
1001 - 1100 of 1216 matches
Mail list logo
