Thanks for answers, all back to normal this morning after the usually
updates and reboot (exception of the debian grub in place of ubuntu but
different matter ;).
Then after reboot the resolution was ok for authentication, and after
login in ubuntu standard session changing resolution settings w
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu Oneiric)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs
OK, I am good with that...except I could use help on the "easily enabled" part:
I checked in "System Settings"-->"Mouse and Touchpad" and there is no option to
turn on the right button or the middle button. Is there a more obvious place to
look?
Also, you haven't mentioned that the middle button
This is something that requires some physical testing to ensure it gets
done right. Unfortunately, my Macbook 5,1 laptop won't resume from
suspend, so I can't really develop a fix for this. I'm unassigning
myself.
A workaround is to unload and reload the bcm5974 kernel module:
$ sudo rmmod bcm597
Hi Mason,
While I understand your sentiment, clickpad support is fully available
in 12.04. The right button area is not enabled by default, but it can be
easily enabled by users who want it.
There's a lot to clickpad functionality beyond just emitting the correct
button click when tapping or clic
No this problem has been resolved. On my laptop I have not had this
issue in a long time. It looks like it inadvertently was fixed at some
point. Thank you for checking up on this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
*** This bug is a duplicate of bug 938658 ***
https://bugs.launchpad.net/bugs/938658
** This bug has been marked a duplicate of bug 938658
[nvidia] Clicking minimized applications from launcher presents blank window
--
You received this bug notification because you are a member of Ubuntu-
11.10: still same old problem
12.04 Beta 2: touchpad working fine
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/859474
Title:
Dragging with touchpad unusable
To manage
I just did update and problem still occurs :/ (lenovo x200t hardware)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/949097
Title:
Serial Wacom Tablet touch not in absolute mode when
This affects me as well. MacBookPro 5,2.
The mouse cursor is still visible, and I can right-click and get a
context menu, but I am unable to move the mouse cursor around my screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-inp
*** This bug is a duplicate of bug 576648 ***
https://bugs.launchpad.net/bugs/576648
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 576648, so it is being marked as such. Please look at
*** This bug is a duplicate of bug 943880 ***
https://bugs.launchpad.net/bugs/943880
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #943880, so is being marked as such. Ple
There have been many changes to -synaptics this cycle, since the last
comment. Is anyone on this bug still seeing this misbehavior?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubunt
Are you still experiencing this problem? There've been a bunch of
changes to synaptics in precise since the last comment of this bug
report.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ub
Are you still experiencing this problem? There've been a bunch of
changes to synaptics in precise since the last comment of this bug
report.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 938039 ***
https://bugs.launchpad.net/bugs/938039
** This bug has been marked a duplicate of bug 938039
Touchpad stops working after using keyboard in textfields & function keys
--
You received this bug notification because you are a member of Ubuntu-X,
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/950036
Title:
Touchpad does not tri
Did you turn them on in the Mouse and Touchpad config applet?
I've verified once I flip them on in that, they work on my mini 10v.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X
Hi Andreas, has it always behaved like this, or did this behavior just
begin recently?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-syna
*** This bug is a duplicate of bug 968845 ***
https://bugs.launchpad.net/bugs/968845
Betting this has the same root cause as bug 968845
** This bug has been marked a duplicate of bug 968845
bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
--
You received this bug notification beca
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/939804
Title:
Touchpad scrolling f
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => High
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
You
*** This bug is a duplicate of bug 968845 ***
https://bugs.launchpad.net/bugs/968845
** This bug has been marked a duplicate of bug 968845
bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
** Summary changed:
- trackpad fails to work on resume
+ trackpad fails to work on resume on Micro-Star PR420
** Summary changed:
- trackpad fails to work on resume on Micro-Star PR420
+ trackpad fails to work on resume if disabled with Fn+F3 on Micro-Star PR420
** Changed in: xserver-xorg-inpu
*** This bug is a duplicate of bug 968845 ***
https://bugs.launchpad.net/bugs/968845
** Summary changed:
- Touchpad configuration reset after suspend/resume
+ Touchpad configuration reset after suspend/resume on MacBookAir4,2
--
You received this bug notification because you are a member of
** Summary changed:
- bcm5974 touchpad doesn't work after S3
+ bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/968845
*** This bug is a duplicate of bug 968845 ***
https://bugs.launchpad.net/bugs/968845
** Summary changed:
- Touchpad stops working when coming out of suspend
+ Touchpad stops working when coming out of suspend on MacBookPro5,2
** This bug has been marked a duplicate of bug 968845
bcm5974 t
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => Triaged
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-sy
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/957699
Title:
[bcm5974] Right-cli
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => Triaged
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => High
** Summary changed:
- Mouse pointer stops responding
+ Mouse pointer stops responding without known trigger
--
You rec
Just did today's updates and this appears to be resolved. Can someone
else confirm?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/949097
Title:
Serial Wacom Tablet touch not in abs
** Attachment added: "kern.log"
https://bugs.launchpad.net/bugs/973893/+attachment/3006529/+files/kern.log
--
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.
https://bugs.launchpad.net/bugs/973893
Title
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/973893/+attachment/3006530/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in Ubu
Public bug reported:
Hi Devs,
I'm using 12.04 (beta2) and I get a kernel panic (flashing Caps + Scroll lock)
after about 20mins of use if I activate the fancy non-open source nVidia driver.
lspci reports that I have:
02:00.0 VGA compatible controller: NVIDIA Corporation G71GL [Quadro FX 3500]
(r
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Let me know if you require anything else.
** Attachment added: "Backtrace"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+attachment/3006457/+files/gdb-Xorg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hi,
the description of features for Ubuntu 12.04 (at
https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview/Beta2) lists Clickpad
support as a feature of 12.04, but this bug is now marked as "Won't fix"--with
this bug still present, Clickpad support is only partial--and Ubuntu really
needs a
While this is Precise xrandr --verbose
As you can see, they look similar except in Lucid there a few lines
more where there are the right resolutions.
As read-edid, they's quite small so I copy/paste them here.
PRECISE:
===
sudo get-edid | parse-edid
par
Here's Lucid xrandr --verbose
** Attachment added: "LUCIDxrandr_verbose.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/973163/+attachment/3006291/+files/LUCIDxrandr_verbose.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg i
Here's Lucid Xorg.0.Log
** Attachment added: "LUCID_Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/973163/+attachment/3006290/+files/LUCID_Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bu
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=48311.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
--
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/973866
Title:
VGA and second monitor on ATI HD 6670 (Dell XPS 8300) is broken
To manage notifications about this bug go to:
https://bugs.launchpad.
Public bug reported:
Hello,
I reported this problem for kubuntu but I was asked to rereport it using
ubuntu. The kubuntu bug (with screenshot) is
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/969758
Just after grub, VGA output just show a flicking color with a barelly
visible top bar (abou
This bug was fixed in the package xorg-server - 2:1.11.4-0ubuntu10
---
xorg-server (2:1.11.4-0ubuntu10) precise; urgency=low
* Fix touchscreen pointer emulation (LP: #949791)
- Add temporary patch 506_touchscreen_pointer_emulation_checks.patch
-- Chase DouglasWed, 04 Apr 20
(I'm changing this to "confirmed" though one should not confirm one's
own bugs, because this is a very well known bug which seems to get
attention everywhere except here.)
IT GOT WORSE TODAY: now it has started to affect also videos streaming
online, for example videos on YouTube.
For god's sake,
** Bug watch added: freedesktop.org Bugzilla #48311
https://bugs.freedesktop.org/show_bug.cgi?id=48311
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=48311
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 972727 ***
https://bugs.launchpad.net/bugs/972727
** This bug has been marked a duplicate of bug 972727
Synaptics Clickpad functionalities incomplete: Right button area, two-tap
disabling
--
You received this bug notification because you are a member of
I do plan to enable it in 12.10. I suggest following Robert's approach
for 12.04.
** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise)
Importance: Wishlist
Status: Triaged
** Also affects: xserver-xorg-input-synaptics (Ubuntu Q-series)
Importance: Undecided
Status: N
@Craig, if you're still seeing it with current 12.04, can you file a new
bug? The logs and data on this report are out of date with precise, so
I'm going to remove the tag.
Also, please reproduce using the stock ubuntu rather than kubuntu; some
input handling is done in desktop services - this be
Guy,
-synaptics received a lot of development work this cycle, including
after you filed this bug report; can you re-test to see if current
precise has these same performance issues?
** Summary changed:
- Elantech Touchpad become unusable in precise
+ Elantech Touchpad has severe delay and sensi
** Summary changed:
- "Cando" Touchscreen buggy since Precise
+ "Cando" Touchscreen buggy since Precise - After the first few successful
"clicks" on the touchscreen, new "clicks" are not registered anymore.
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
** Summary changed:
- Problems with the touchpad on the HP Probook 4730s
+ Cannot enable/disable the touchpad when I double tapped in the upper left
corner on the HP Probook 4730s
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => New
--
You received this bug not
Hi Dave, any updates you can share about this bug? A lot has changed
with -synaptics this cycle.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg
There was concern of possible side effects / regressions that could
affect other devices. I think Chase plans on bringing the feature back
in 12.10. I don't know if he has any plans to host a PPA with the
patched version we were experimenting with, but you can still obtain the
old .debs that had
This bug was fixed in the package xserver-xorg-input-synaptics -
1.5.99.902-0ubuntu3
---
xserver-xorg-input-synaptics (1.5.99.902-0ubuntu3) precise; urgency=low
* Fix bad default for two touch tap as middle button click (LP: #973783)
- Fixed 104_always_enable_tapping.patch
-
Public bug reported:
This usually isn't seen because gnome-settings-daemon overwrites the
setting once logged in. However, if g-s-d isn't used or isn't running,
the user will be left with the wrong setting.
This is due to a bad change in distro patch
104_always_enable_tapping.patch:
-/* Enab
Some more info on what was going on:
Nautilus, the file manager, is in charge of the desktop. This is how
files on your desktop are managed. When it sees button press event, it
grabs the device. When the button release event is seen, it ungrabs the
device.
GTK is only selecting for events on mast
This made it work properly for me on a fujitsu T4410 with wacom serial
touch screen:
gsettings set org.gnome.settings-daemon.plugins.gsdwacom active false
Without that, I get relative tracking behavior as described in bug
973133.
--
You received this bug notification because you are a member of
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/949097
Title:
Serial Wacom Tablet touch not
This is caused by bad input event mask checking and handling in the X
server for touchscreen pointer emulation. The following patches fix the
issue:
http://lists.x.org/archives/xorg-devel/2012-April/030265.html
http://lists.x.org/archives/xorg-devel/2012-April/030267.html
http://lists.x.org/archiv
*** This bug is a duplicate of bug 949097 ***
https://bugs.launchpad.net/bugs/949097
After talking to timo, guessing this is the same as bug #949097. As he
points out, it could well be a bug in g-s-d.
** This bug has been marked a duplicate of bug 949097
Serial Wacom Tablet touch not in a
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/969603
Title:
xdiagnose crashed with GError in constructor(): Couldn't recognize the
image file format for
Was fixed in 2.2
** Changed in: xdiagnose (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/914038
Title:
Can't use keyboard on "What would you
*** This bug is a duplicate of bug 966649 ***
https://bugs.launchpad.net/bugs/966649
Guessing this might be a dupe of #966649. If not feel free to reopen
with further details.
** This bug has been marked a duplicate of bug 966649
apport-gpu-error-intel.py is not executable
--
You receiv
This is the one bit that stands out as improper:
plymouth:debug=1=1
I can see if this reproduces symptoms such as you reported.
** Visibility changed to: Public
** Changed in: xdiagnose (Ubuntu)
Importance: Undecided => High
** Changed in: xdiagnose (Ubuntu)
Status: Incomplete => Tri
You have been subscribed to a public bug:
I have a Viewsonic Viewpad 10 (Atom based) tablet running Precise 32
Bit. If I use Unity-2D the Touchscreen works as expected.
If I run Unity-3D I can tap once or twice. From that point I can just move the
mouse pointer, but I can't click on anything.
--
** Changed in: xdiagnose (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/966649
Title:
apport-gpu-error-intel.py is not executable
To manage not
X shouldn't crash even if the media player is doing something wrong.
Please run 'apport-collect 942821' to attach the X logs and so on.
Also collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Ah - thanks for the tip! It seems this came from the xorg-edgers PPA which I
installed based on suggestions at
http://bernaerts.dyndns.org/linux/202-ubuntu-acer-ao722 on installing this
machine - which seem to now be outdated.
Once I did a ppa-purge I can confirm that fglrx works correctly on t
Verified here as well with mesa in proposed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/966399
Title:
Mesa related GPU h
** Summary changed:
- Xorg freeze
+ Xorg freeze playing video in firefox
** Package changed: xorg (Ubuntu) => fglrx-installer (Ubuntu)
--
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/972907
Title
What was the error message that it threw?
It doesn't seem to be recorded in any of the attached information.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://b
I'm able to reproduce this issue on a fujitsu T4410, which also has a
serial wacom touch screen.
** Package changed: xorg (Ubuntu) => xf86-input-wacom (Ubuntu)
** Changed in: xf86-input-wacom (Ubuntu)
Importance: Undecided => High
** Changed in: xf86-input-wacom (Ubuntu)
Status: Incom
Looking at your Xorg.0.log, X is not receiving any EDID information from
the TV. So it's defaulting to the VESA modes, maxing out at 1024x768.
Check an Xorg.0.log from booting a Lucid LiveCD to see if it did receive
correct EDID information in that case. If so, post a copy of the
Xorg.0.log and
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
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/973297
Title:
Xorg recognizes Logitech Headset USB dongle as input device then
s
We'll need a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Changed in: xorg (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchp
Hmm, the Xorg.0.log indicates no EDID is being received from the
monitor. Presumably it was auto-detecting previously because it was
getting the EDID.
I've never heard of wine game modechanges causing corruption to the EDID
itself (it's usually firmware, although some monitors have writable
EDID;
Is that an issue for you in Ubuntu 12.04 beta 2?
** Changed in: unity
Status: New => Incomplete
** Changed in: unity (Ubuntu)
Status: New => Incomplete
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because yo
** Description changed:
When booting 12.04 (with all updates installed), X loads but only covers
the upper half of the screen. On the bottom half the console output of
the boot process is still visible.
This blog post (not by me) contains a screenshot and a simple workaround
http:/
** Tags added: bugpattern-needed
--
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/933504
Title:
Xorg crashed with SIGABRT in __libc_message "double free or corruption
(out)" from DeleteIn
*** This bug is a duplicate of bug 933504 ***
https://bugs.launchpad.net/bugs/933504
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #933504, so is being marked as such. Ple
I can confirm this fixes the issue on a number of Ivy Bridge systems we
have tested, with no regressions observed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/966399
Title:
Mesa related GPU h
Let us know if purging and reinstalling nvidia solves it.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Incomplete
--
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.
Well, here's the problem, you have ancient nvidia bits installed. 285
is incompatible with the Ubuntu Precise xserver.
DkmsStatus:
nvidia-current, 285.05.09, 3.0.0-12-generic, x86_64: installedError! Could not
locate dkms.conf file.
File: does not exist.
nvidia-current-updates, 280.13, 3.0.0
** Package changed: nvidia-graphics-drivers (Ubuntu) => gnome-power-
manager (Ubuntu)
--
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/972055
Title:
Screen brightness stuck at m
Please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Incomplete
--
You received this bug notif
Interesting, I notice the nvidia driver version being reported here is
the same as it was on the other bug:
NVRM version: NVIDIA UNIX x86 Kernel Module 285.05.33 Thu Jan 19
15:24:04 PST 2012
and that's quite old. I wonder if your installation got corrupted?
Anyway, this is the cause of your p
Similar to 877438 (8xxx cards), 940742 (6xxx cards), 943643 (9800),
958251 (8600), 962191 (7100).
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers (Ubuntu)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers (Ubuntu)
*** This bug is a duplicate of bug 973506 ***
https://bugs.launchpad.net/bugs/973506
** This bug has been marked a duplicate of bug 973506
Huge processor's loading by Xorg process when nvidia proprietary drivers
installed
--
You received this bug notification because you are a member of
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete => New
** Changed in: nvidia-graphics-drivers (Ubuntu Oneiric)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in
@Alberto, this looks worth raising with nvidia
** Summary changed:
- [8400] Xorg freeze
+ [8400] Xorg freeze with 3D - regression since 295.20
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => T
Often with these 100% X cpu bugs, the problem is caused by a client
application, which is stuck in a loop making X requests. In such cases,
the debugging procedure is to examine your process table (e.g. `ps aux`)
and start killing processes one by one until the system unfreezes.
However, the fact
I would like to "reopen" this bug because it does seem that it is not a
question of UMS support for dri on r200 or r300.
I'm on PP beta 2 on i386, I've compiled and installed mesa 7.11 and
7.10 and the problem remains. Didn t notice before as I didn t need to
disable modesetting. I'm investigatin
** Also affects: nouveau
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/888373
Title:
Ubuntu 11.10 won't boot with nvidia driver
Public bug reported:
Running the current Ubuntu 12.04 LTS Beta2 as a live test from dvd (x64)
- default boot settings, nothing changed, I encountered the following
graphics problem:
In X-Window-Mode on the Unity Desktop my screen starts to flicker
continuous at intervals of about 10 seconds!
The
You appear to be running a non-stock xserver:
xorg-server
2:1.12.0+git20120308+server-1.12-branch.b1be72c5-0ubuntu0ricotz
Likely fglrx simply hasn't been compiled to work against this version of
X. Bring your system back towards a stock configuration and then
install fglrx. If you still spot pr
To reproduce the problem you can use a AMD Graphics Card (Not sure if
it's the APU series only or not) install the graphics driver as you
normally would, restart the computer. If you are lucky you will get into
Ubuntu, or in some cases it will get stuck at "Checking Battery State".
If you did get i
More discussion at http://www.linlap.com/wiki/acer+aspire+one+722 -
seems that jiggling the network devices is a common theme.
** Summary changed:
- Ubuntu freezes with AMD APU C-60 and Radeon HD 6290
+ Ubuntu freezes on boot with Acer ao 722-C62kk (AMD APU C-60 and Radeon HD
6290) - wireless de
1 - 100 of 179 matches
Mail list logo
