** Summary changed:
- Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation
unit too large for Clang to process.
+ Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation
unit too large for Clang to process.
--
You received this bug notification
** Attachment added: "cpp code that crashes clang-11"
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451542/+files/qs_adr-d57687.cpp
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to llvm-toolchain-11 in
** Attachment added: "shell script generated by clang"
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451541/+files/qs_adr-d57687.sh
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to llvm-toolchain-11 in
Public bug reported:
clang11 provided by ubuntu on 20.10 crashes on some C++ code with the
message:
sorry, this include generates a translation unit too large for Clang to
process.
Installing clang-11 from llvm fixes the issue.
This issue occur only on 20.10
** Affects: llvm-toolchain-11
Public bug reported:
Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et
reste figé sur les points sous le logo Ubuntu
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux
Public bug reported:
trying desperately to install ubuntu on a new Kingston SSD drive...
allways a bug bitchin' around :-\
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux
Well… Switching to another window manager doesn't solve the “any 3D/GLX
app would crash” issue…
In my case I would have preferred to use the nouveau driver from the
beginning, except that for ancient cards like the 6150SE it makes the
whole system freeze after only a few minutes…
Finally, I was
FYI, after a kernel upgrade the NVIDIA driver was unusable again. This
time was because of the DKMS mechanism which, for whatever reason I
didn't investigate yet (could it be because of the apt-pinning??),
didn't success to build and install the nvidia_304.ko module for the new
kernel.
If that
Sorry for the typos and long-lines… Can't find a way to edit back my
posts… :-/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after
In my case I have a GeForce 6150SE so I really need this 304.131 and
can't higher version like 340.xx.
For people needing to downgrade, this is one (among others) correct way to do
so with Ubuntu 16.04:
- first create a file named /etc/apt/preferences.d/local-nvidia-quirks
with the following
Since this problem greatly affects usability (no graphic login anymore),
may be it's worth (in the users' point of view) creating a “fake
version” security-upgrade like "304.132-0ubuntu0.16.04.2+really304.131"
to fill the gap while waiting for Nvidia to provide a fix for 304.132,
IMHO.
--
You
** Bug watch added: Debian Bug tracker #840342
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342
** Also affects: nvidia-graphics-drivers-legacy-304xx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342
Importance: Unknown
Status: Unknown
--
You received
A debdiff between the packages shows the difference is mainly a version
upgrade from 304.131 to 304.132.
And it seems a lot of people are experiencing problems with version
304.132, cf
https://devtalk.nvidia.com/search/more/sitecommentsearch/304.132/
A specific thread retained my attention:
FYI, downgrade “solved” the problem for me too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to nvidia 304.132
To manage
Philippe, I am not really sure what you want to do with those
commands...
--
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/1590590
Title:
Touchpad not recognized on Dell
Another thing I just noticed : with or without the patch, the only thing
that works with two screen is the extended mode. When I try to go from
two screen extended to two screen clone mode, both screens switch off
and cannot be switched back on.
--
You received this bug notification because you
In the next comment, you will findthe output of xrandr --verbose, when both
monitors are enabled, with the original (non patched) drivers.
I must say that the patch you posted in comment #47 works perfectly when it
comes to wake the monitor after some time of sleep. Only the problem of black
** Attachment added: "Xrandr output"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4702793/+files/xrandr
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: "20160706_120743.jpg"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696357/+files/20160706_120743.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
** Attachment added: "black_screen.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696354/+files/black_screen.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
** Attachment added: "before_black_screen.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696355/+files/before_black_screen.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I must add that without the patch, after the black screen and the ctrl-alt-F1
then ctrl-alt-F7, I had a dialog box saying : "Impossible de restaurer la
configuration de l'affichage
could not set the configuration for CRTC 80".
--
You received this bug notification because you are a member of
Same problem with this patch. Well in fact, it's even worse as I got a
kernel panic when trying to switch from 2 screens to only one (see
picture attached).
I attached the output of xrandr before and after the black screen (but
before the complete crash).
The black screen when changing between
Michel, this patch seems to work quite well, but still showing some strange
behaviour. To sum up, with the new patch :
- with one or two screens used, when the screens goes off after some time of
inactivity, they can be woken up by moving the mouse.
- when two screens are used, from time to
It's a DELL Dimension E520. Is that the full computer model ?
--
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/1577170
Title:
screen cannot be turned back on after being switched off after some
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695158/+files/XorgLog.txt
--
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/1577170
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695162/+files/xdpyinfo.txt
--
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/1577170
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695157/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695155/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695153/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695159/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695152/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695160/+files/Xrandr.txt
--
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/1577170
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695147/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695146/+files/DpkgLog.txt
--
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/1577170
apport information
** Tags added: apport-collected compiz-0.9 ubuntu
** Description changed:
I did a fresh install of ubuntu 16.04 on my old dell computer in which
there is an ati radeon X1300 graphics card.
Whenever the screen turns off due to inactivity, it cannot be woken up
by
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695148/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "drirc.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695161/+files/drirc.txt
--
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/1577170
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695145/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695156/+files/UdevDb.txt
--
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/1577170
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695150/+files/Lsusb.txt
--
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/1577170
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695144/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695151/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695149/+files/Lspci.txt
--
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/1577170
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1577170/+attachment/4695154/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- [solved] screen cannot be turned back on after being switched off after some
time of inactivity
+ screen cannot be turned back on after being switched off after some time of
inactivity
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "gdb output with "new" patch and 1 screen on"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4676222/+files/gdb_new_patch_1_screen.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "gdb output with "old" patch and 2 screens on"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4676221/+files/gdb_old_patch_2_screens.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I just attached the two gdb backtraces from when it hangs. I must add
that during the "make" process of the newly patched radeon driver, I get
this warning :
radeon_drm_queue.c: In function ‘radeon_drm_queue_alloc’:
radeon_drm_queue.c:95:9: warning: return makes integer from pointer without a
What I have noticed is that when two screens are plugged in the graphic card,
and the desktop appears on both screen, and when I then choose to only use the
dvi-connected screen via the "display" menu in ubuntu, the vga-connected screen
goes off, and the dvi-connected screen only show the mouse
Thank you Michel for this new fix. Unfortunately, this one does not work
on my computer at all.
With the previous patch, the problem seemed to have been fixed, but
wasn't completely fixed as my computer couldn't be woken up when two
screens were used on my radeon card (it works so far with only
Strange, as with the patched driver, the problem reappeared today.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1577170
Title:
[solved] screen cannot be turned back on after
Thanks to the guys in the #radeon channel on irc, I found a way to solve the
problem.
You have to apply this patch to the source of the video driver
(xfree86-video-ati-7.7.0) : https://paste.debian.net/plain/682956
and compile then install it (using --prefix=/usr for the configure process).
** Description changed:
I did a fresh install of ubuntu 16.04 on my old dell computer in which
there is an ati radeon X1300 graphics card.
Whenever the screen turns off due to inactivity, it cannot be woken up
by moving the mouse or by hitting a key.
- The same ubuntu 16.04
** Package changed: unity (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1577170
Title:
screen cannot be turned back on after being
EDIT : I just found that letting the screen be turned off when not
logged at all (when I boot the computer and don't log in for example)
causes no problem. The screen goes black and can be woken up by moving
the mouse or by hitting a key. The problem only appear when logged in,
whatever the user.
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1577170
Title:
screen cannot be
New information : typing "xset -display :0.0 dpms force off" in the
terminal makes my screen to turn off. Then I can wake it up just by
moving the mouse. So the problem seems related to the "screen saver" of
ubuntu rather than Xorg.
** Package changed: xorg (Ubuntu) => gnome-screensaver (Ubuntu)
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+attachment/4654716/+files/Xorg.0.log
--
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/1577170
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577170/+attachment/4654715/+files/dmesg
--
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/1577170
Title:
The problem is not solved with the latest 4.6 kernel.
--
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/1577170
Title:
screen cannot be turned back on after being switched off after some
time of
Is it something I could do to find out a fix ?
--
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/1577170
Title:
screen cannot be turned back on after being switched off after some
time of
Hello,
i was able to install, but unable to run the apk on android 4.2.2
C.O.
Le 17/06/2015 13:14, Rolf Leggewie a écrit :
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: fglrx-installer (Ubuntu
Hey,
I have just found a workaround by chance: purging xserver-xorg-video-
nouveau (without replacing it by a Nvidia driver) from the system
removes the freezing issue during shutdown!
That's very strange because the driver is loaded with initrd during the
boot, meaning rebooting after the
A trace has recently shown up during a failed shutdown; the following is
the OCR translation obtained from a picture (available as attachment),
meaning some decoding errors may be still there, especially in the
Modules linked in section that I have not checked:
wait-for-state stop/waiting
*
Public bug reported:
I know someone who solved this issue by installing a Nvidia driver.
Do you test your Nouveau driver on MSI computers and computers with Nvidia
graphics card before rolling out new releases?
This is not the first time I'm experiencing a significant flaw with this driver.
This is fixed upstream: http://cgit.freedesktop.org/xkeyboard-
config/commit/?id=ec875f6f9b7c4028e11d32b071989c682e6502bd
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/802589
Title:
Public bug reported:
I was running glmark2 when my screen turned black.
Matching syslog lines:
[drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
[drm] capturing error event; look for more information in
/sys/kernel/debug/dri/0/i915_error_state
[drm:i915_set_reset_status] *ERROR* render
Here's the glmark output from a second run.
(...)
[ideas] speed=duration:intel_do_flush_locked failed: Input/output error
** Attachment added: glmark.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1235280/+attachment/3859537/+files/glmark.log
--
You received
It is working now so it can be closed
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1075158
This bug affects me as well. When starting my computer with the tablet
plugged in, the led on the tablet doesn't light up, lsusb doesn't list
it, and lsmod doesn't list the wacom module. The tablet just does not
react. A workaround is to unplug it and plug it again: the tablet gets
recognised and
Public bug reported:
It seems that bug #966744 has been fixed but I have still the issue
I have a Laptop Fujitsu s761
Kubuntu 12.10 64 bit
I am using a i915 card from intel
** Affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Attachment added:
** Package changed: ubuntu = libx11 (Ubuntu)
** Changed in: libx11 (Ubuntu)
Assignee: (unassigned) = Christophe (kriss-tofephon)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1023414
Ter Info
I just found the problem by me.
Crashes occured due to I/0 dropout on asus MB P6X58-E WS.
This happened about one time each hour. Pc worked fine during 9 months and
sudden it's start freezing. It was not a real freeze. As I still had graphical
screen and every program and service
Since a week now after latest upgrade ubuntu 12.04 also always crashes
after a certain amount of time.
system asus mb P6X58-E WS,Intel core i7 990x, corsair vengeance 3 x 4GB
ddr3 1600mhz.
drives 2 sdd corsair crucial 512 GB 2 WD 2002FAEX 2TB.
Crash seems to be related with sata. When running
This problem seems to occur one many modern system's.
it's not graphical related. But eigther I/0 related.
I think that a change somewhere into D-bus must be the cause
All graphic drivers are making a lot of use of hdd and so ..
--
You received this bug notification because you are a
I have the same problem.
I use a freshly installed Ubuntu 12.04, and when I log under unity (3d)
the GUI freezes after some time randomly. It can be when I surf the web
with firefox or when I read a pdf file in evince. The mouse still moves
on the screen, but nothing happens when I click
I have the same problem.
I use a freshly installed Ubuntu 12.04 64 bits, and when I log under
unity (3d) the GUI freezes after some time randomly. It can be when I
surf the web with firefox or when I read a pdf file in evince. The mouse
still moves on the screen, but nothing happens when I click
I think this could help. The bug just appeared again as I was within a
gnome classic (WITH effects) session with my ubuntu 12.04 64 bits.
So it looks like it's really a issue of compiz and not really a bug in
unity.
--
You received this bug notification because you are a member of Ubuntu-X,
I think this could help. The bug just appeared again as I was within a
gnome classic (WITH effects) with my ubuntu 12.04 64 bits.
So it looks like it's really a issue of compiz and not really a bug in
unity.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Hi Axel,
This is not completely true. In Natty, it was possible to activate twinview on
2 external monitors if DFP-0 is disabled.
This was done via nvidia-settings.
However now, the nvidia-settings seems to crash when the same setup is applied.
Like Radu, I also experience this problem. I have
Small focus on what I see as suspect in X11.logs files:
Wladimir Mutel log:
[ 393.193] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
mine:
[12.757] (WW) Hotplugging is on, devices
Public bug reported:
All inputs plugged at booting are not detected by xorg (need magic keys
alt+impr_ecr+r to release keyboard and go tty)
note: I use nvidia pilots and it makes an autoconfig.
here the logs... I have no usb keyboard at home, this bug turn my laptop
nearly unusable. (still tty
** Attachment added: Xorg log file
https://bugs.launchpad.net/bugs/808478/+attachment/2201253/+files/Xorg.0.log
--
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/808478
Title:
Input detection
I have downgraded the compiz packages and I haven't had a freeze since
then.
--
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/799085
Title:
Xorg freeze
To manage notifications
Public bug reported:
Binary package hint: xorg
after an upgrade on 2011-06-12(compiz) xorg started to freeze after some time
of usage.
The freeze are not always fatal, sometimes going to the console and going back
allows to continue working However this works only once.
typically what happens
--
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/799085
Title:
Xorg freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/799085/+subscriptions
On the ubuntu french forum, the nvidia driver 173 solve the problem of
some personnes, but not all of them.
The white blank windows desepear for all of them, but new bugs appear
for some, as a nearly completely black screen (with a little normal zone
at the top of the screen).
--
You received
Similar issue here. Often, applications freeze and I have to kill them
(qtcreator for example). Sometimes, it is even worse and the whole
system freezes and I need to reboot.
After a system freeze, I tried to use CTRL+ALT+Fx then check dmesg and
Xorg log but there was nothing strange in those.
Public bug reported:
failed during upgrade to 1010... upgrade interrupted!
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
NonfreeKernelModules: fglrx
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
https://bugs.launchpad.net/bugs/720763
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to upgrade to 1010:
ErrorMessage: le sous-processus script post-removal
Same here, I confirm that the GPU hang can also happen with desktop
effects disabled (although way less often).
--
[GM45] GPU Hang when enabling KDE desktop effects
https://bugs.launchpad.net/bugs/644740
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Here is the debug output you requested.
** Attachment added: debug output
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/644740/+attachment/1669561/+files/i915_debug.log.gz
--
[GM45] GPU Hang when enabling KDE desktop effects
https://bugs.launchpad.net/bugs/644740
Note that I have the exact same issue on a E4310. This is not specific
to E6410.
Also, it was working fine a few days ago and was broken by a recent
package update in Maverick (I don't know which one exactly).
--
erratic mouse behaviour after resume
https://bugs.launchpad.net/bugs/641091
You
This is a kernel issue. The last kernel to work is:
2.6.35-20-generic
The breakage was introduced in v2.6.35-21-generic. I hope this helps.
** Package changed: xserver-xorg-input-mouse (Ubuntu) = linux (Ubuntu)
--
erratic mouse behaviour after resume
https://bugs.launchpad.net/bugs/641091
You
Architecture: amd64
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
MachineType: LENOVO 9461DXG
Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5
PackageArchitecture: amd64
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine:
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51563989/Dependencies.txt
--
DPI of monitor incorrectly set
https://bugs.launchpad.net/bugs/580985
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: DkmsStatus.txt
http://launchpadlibrarian.net/51563990/DkmsStatus.txt
--
DPI of monitor incorrectly set
https://bugs.launchpad.net/bugs/580985
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51563987/BootDmesg.txt
--
DPI of monitor incorrectly set
https://bugs.launchpad.net/bugs/580985
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/51563988/CurrentDmesg.txt
--
DPI of monitor incorrectly set
https://bugs.launchpad.net/bugs/580985
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
1 - 100 of 131 matches
Mail list logo
