** Tags removed: need-duplicate-check
--
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/1220073
Title:
[sandybridge-m-gt2] GPU lockup IPEHR: 0x79050005 IPEHR: 0x0b140001
To ma
Public bug reported:
I tried to suspend the laptop, but nothing happened. The fan was working
at maximum. I had to turn it off by the power button.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1197405
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1171666
Public bug reported:
Bug appeared after recent uptade (~ 30 Aug). Display coonnects to APU,
discrette GPU also exists, but not used in this system.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.2.901-2ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-
** Summary changed:
- [radeon] Graphic glitches and screen corruption since the latest update
+ [radeon] Graphic glitches and screen corruption (vertical lines)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.
Interesting the workaround would not work, because it looks like bypass
mode has the wrong pixel format. But I'm also glad bypass isn't broken
too. Please double-check that the workaround really does not help. Also
remember to reboot.
Secondly, please try this (or something like it):
1. sudo apt
Public bug reported:
Trackpad on Lenovo IdeaPad P500 does not work properly. This problem was
originally in my Ubuntu partition, but now my Windows 8 partition also
has some noticeable issues with clicking (perhaps because of my
debugging attempts). I did accidentally spill a small amount of water
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
I have the same behavior -- ie. when I leave my computer at night the
monitor eventually goes into suspend mode. Then in the morning I come in
and touch the keyboard nothing happens. If I log in remotely I can see
that X has died and I see the same "fallen off the bus" kernel messages.
I put the su
Please execute the following command, as it will
automatically gather debugging information, in a terminal:
`apport-collect BUGNUMBER` <-- in this case 'apport-collect 01'
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can
Can you tell me what you were doing when the crash happened? Did you
have loads of Chromium browser windows open? What Chromium browser
settings were you using?
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because yo
If possible could you attempt to shut-down the system and then provide
your 'dmesg', 'syslog' or 'xorg' logs that were written during that
shut-down? There's usually more specific information there.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Incomplete
--
You rece
These logs are stored in your '/var/logs/' folder if you use Nautilus
you can navigate there and then change to list view and then sort by
"modified date" to find which logs were most recently written to.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Incomplete
--
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/1185782
Title:
Unity crashes after inst
I filed a bug report on AMD's bug tracker. I don't know what else to do
about this as it's hard to describe what is happening.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
Title:
Low
Also, one more thing, could you try removing the Nvidia drivers from the
"additional drivers" dialog and testing to see if this happens again
with the open source 'nouveau' driver?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-d
According the the www.nvidia.com/driver selection tool, for Linux x64
drivers only series 319 and 325 support the Titan line of graphics cards
or are currently recommended to use with them:
- Linux x64 (AMD64/EM64T) Display Driver - BETA
Version: 325.08 - Release Date: Mon Jul 01, 2013
- Linux x6
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
`apport-collect 1185782`
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and t
Is this somehow related to the following bug fixed in the 319.49 driver release:
http://www.nvidia.com/object/linux-display-amd64-319.49-driver
* Fixed a bug that resulted in corrupt texels when a previously empty
texture image was specified with glXBindTexImageEXT. In GNOME 3, this
caused gnome-s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
http
rsoika, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal (Applications->
+Timo, my tone was one of excitement and not really a rant, so I
apologize if I came off as sounding impatient and I can understand the
long hours everyone here puts into this and I really do appreciate this
and am very grateful.
However, I'm looking at this from a "customer expectations" point of
*** This bug is a duplicate of bug 1145689 ***
https://bugs.launchpad.net/bugs/1145689
Mint15
removing ~/.config/monitors.xml didn't work for me
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs
Sorry for the bad photo, I'll try to get a better one with a better
camera tomorrow. This is how it looks in LightDM.
The workaround you mentioned didn't work for me.
** Attachment added: "Error as seen directly after booting (LightDM)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+b
Same problem with Dell xps13 - 3.8.0-29-generic 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/1183942
Title:
Cannot adjust screen brightness in DELL XPS 13
To manage notifications abou
First of all, there is no 'nvidia-updates' package and never will. We
use nvidia-VER names now, as you know, also 'nvidia-current' is just a
transitional package in saucy (new versions backported to precise might
still use old names, dunno).
Also, people do tend to take vacation from time to time,
Could you please provide us with some more information?
* Information about your hardware setup such as Nvidia card type and model.
* Please indicate which version of Ubuntu you are using and Kernel version:
just do 'uname -a' at the terminal.
* The driver version and how you installed it.
Thank
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* What exactly were you doing when the error occured?
This will help us to find and resolve
** Description changed:
The official Nvidia long-lived-branch stable driver is now 319.49. That
means that the recommended official driver is 319.49 and should be used
by all Nvidia users except those using old legacy devices. There are
important fixes that are in this driver and the pre
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
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 #1033533, so is being marked as such.
Things have changed just a bit between the Alpha 2 images and the first
of the Beta 1 testing images. I now no longer freeze while the progress
bar is showing, but I still boot to a blank screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
** Project changed: nvidia-drivers-ubuntu => nvidia-graphics-
drivers-319-updates (Ubuntu)
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: AG Restringere (ag-restringere) => (unassigned)
** Changed in: nvidia
Assignee: (unassigned) => AG Restringere (ag-restringere)
** Ch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubun
** Package changed: nvidia-graphics-drivers (Ubuntu) => nvidia-graphics-
drivers-304 (Ubuntu)
--
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/1219908
Title:
All nvidia-curr
*** This bug is a duplicate of bug 1194114 ***
https://bugs.launchpad.net/bugs/1194114
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 #1194114, so is being marked as such.
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
Is is possible to keep this as a separate official PPA that just has
nvidia-drivers, nvidia-vpdau and nvidia-settings and keep this in
mirror-lock-step with the upstream releases?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-dr
Public bug reported:
The official Nvidia long-lived-branch stable driver is now 319.49. That
means that the recommended official driver is 319.49 and should be used
by all Nvidia users except those using old legacy devices. There are
important fixes that are in this driver and the previous 319.1
Update comment:
The official Nvidia long-lived-branch stable driver is now 319.49. That
means that the recommended official driver is 319.49 and should be used by
all Nvidia users except those using old legacy devices. There are important
fixes that are in this driver and the previous 319.17 that
Comment:
The official Nvidia long-lived-branch stable driver is now 319.49. That
means that the recommended official driver is 319.49 and should be used by
all Nvidia users except those using old legacy devices. There are important
fixes that are in this driver and the previous 319.17 that affect
Jussi Pakkanen, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/c
/etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf is an alternative
the images have restricted driver pvr-omap4 which provides that alternative
instead of mesa
but pvr-omap4 does not include libwayland so it can't be used
breakage
--
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
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 #1033533, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Confirmed
--
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/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-319 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.lau
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
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/1219869
Title:
ld.so.conf incorrect on arm
To manage notifications about this bug go to
Public bug reported:
The ld.so.conf.d file points to the wrong directory on ARM for egl
/etc/ld.so.conf.d/armhf-linux-gnu_EGL.conf
contains /usr/lib/pvr-omap4-egl
when the libraries are in
/usr/lib/armhf-linux-gnu/mesa-egl
using daily image from 20130902
this stops kwin from running on
I had no lock up since about a year.
--
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/936159
Title:
Xorg freeze, radeon gpu lockup with softreset
To manage notifications about t
Medya, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
OK, so attached is the result of a two-reboot cycle.
Initially (first reboot) I didn't have the monitor attached at all.
Then I ran your diagnostic scripts (output in post-reboot-unattached).
Then I attached the monitor.
Then I ran your diagnostic scripts (output in post-reboot-attached-
after
Hi there!
So, I'm having a hard time with the same bug as well. I've tried several
linux versions with no success. Here's the list:
- Mint 10, 12, 13 (amd64);
- Ubuntu 10.04 , 11.04, 11.10, 12.04 (x86 & amd64), 12.10;
- Kubuntu 12.04 (x86 & amd64);
- Lubuntu 12.04 (x86 & amd64) - this particul
Thanks for your reply, Chris.
I think you meant...
echo 6 | sudo tee /sys/module/drm/parameters/debug
...and I will attach the sequential xrandr outputs, X l.ogs and Dmesg
for all three cases.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
The bug appears to be syncing to vblank, I get multiples of 30 fps for all
tests.
Running glmark2 --off-screen gets the expected fps, so I do not think this is a
critical performance bug. There is a bug in the way measurements are performed
though, but I don't think the actual performance change
** Changed in: xorg (Ubuntu)
Status: Incomplete => In Progress
--
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/1214066
Title:
phoronix benchmarks on nouveau is 4 times slower today than it
Is this perhaps a kernel bug and should this report therefore be
reassigned to the kernel team?
--
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/1219753
Title:
Dell XPS 12
In fact my bug report is based on kernel v3.11-rc7-saucy with 13.10.
Everything in my XPS 12 2013 seems to work fine with current Saucy
development and kernel 3.11rc, *except* the trackpad. Strange that my
Synaptic did work in 3.8 and not anymore since 3.10 and 3.11rc.
--
You received this bug no
Runtime power management support (to be able to dynamically turn on/off
secondary GPUs) is coming in the upstream 3.12 kernel.
--
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/98740
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
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/1212
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mousetweaks (Ubuntu)
Status: New => Confirmed
--
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/1212
Another combination you could try is 13.10 with 3.11rc? That would
probably work better because 3.11rc would be closer to Saucy's 3.10 than
Raring's 3.8...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
ht
** Changed in: libxrandr (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: libxrandr (Ubuntu Precise)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxrandr in Ubuntu.
https://bu
Is there a bug regarding this dual head problem on Ubuntu 13.04? If not,
it could be useful to file a new bug so that Ubuntu developers (and
hopefully also AMD's ones) are correctly informed about this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
** Attachment added: "Output of xinput --list"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799037/+files/xinput
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
** Attachment added: "Output of Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799038/+files/Xorg.0.log
** Attachment removed: "XorgConf.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+a
** Attachment added: "Output of /proc/bus/input/devices"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799036/+files/devices
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input
Public bug reported:
First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8.
Trackpad was functioning correctly (e.g. two-finger scrolling worked)
and was recognized as Synaptics device in /proc/bus/input/devices.
Due to very new Intel wireless 7260 hardware that did not work in ker
** Changed in: nouveau
Status: Confirmed => Invalid
--
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/1196049
Title:
Laptop with Nvidia GPU is hot while using xserver-x
(In reply to comment #3)
> Do you really understand that Nvidia-based 1500-3000$ laptop may be really
> killed by overheat with pretty non-binary / no-blob / GPL-friendly
> opensource driver? Are you kidding? :)
I really understand. But no amount of understanding will make it a good
idea to file b
This is not the appropriate forum to track "power management not
supported" issues. This is something that's being worked on, when it's
supported, should it not work, feel free to file bugs then.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
Do you really understand that Nvidia-based 1500-3000$ laptop may be
really killed by overheat with pretty non-binary / no-blob / GPL-
friendly opensource driver? Are you kidding? :)
It seems Linus Torvalds was right about Nvidia and their (Optimus)
hardware.
OK, Ilia. Where do yo recommend to po
(In reply to comment #3)
> Do you really understand that Nvidia-based 1500-3000$ laptop may be really
> killed by overheat with pretty non-binary / no-blob / GPL-friendly
> opensource driver? Are you kidding? :)
>
The temperatures you've mentioned will not kill your laptop.
> OK, Ilia. Where do y
I can confirm that this is an issue on the MacBook Air 4,2 Mid 2011.
Also seems to be an issue with any trackpad that supports multitouch and
has no click buttons, but a click pad. This is the reason I still don't
use ubuntu on my Mac. Please take this into consideration and add thumb
support and m
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219708/+attachment/3798892/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu
** Attachment added: "Cat from /proc/bus/input/devices"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219708/+attachment/3798889/+files/devices
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-
Public bug reported:
Bug occurred during a fresh install of Ubuntu-13.04. Attempted to fix by
attempting another fresh install as well as reverting to the previous
12.04 version and switching interfaces such as installing Kubuntu. The
mouse responds perfectly fine yet the touch pad is not even det
** Patch added: "proposed patch for precise"
https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/985202/+attachment/3798885/+files/lp985202-precise.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxrandr in Ubuntu.
https://bugs
The originally reported "[TTM] Failed to expire sync object before buffer
eviction"
smell like a kernel issue too, and probably one that's fixed in upstream kernel.
They don't show up when I boot into today's kernel.org's 3.11.0-rc7 (commit
a8787645e14ce),
and are probably fixed by recent drm/nov
** Patch removed: "proposed patch for precise"
https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/985202/+attachment/3498064/+files/nx.debdiff
** Patch added: "proposed patch for saucy"
https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/985202/+attachment/3798878/+files/lp98520
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
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/968295
Title:
No HDMI either sound or activity on the connedted TV
To manage notif
82 matches
Mail list logo
