Thanks. I think I uploaded it into saucy anyway, sorry about that. I
guess it will be able to get back in sync.
libxdamage (1:1.1.4-1ubuntu1) saucy; urgency=low
* Mark libxdamage-dev as Multi-Arch: same.
-- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Fri, 11 Oct 2013 17:47:45
+0100
Public bug reported:
As per title.
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
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/1246013
Title:
Whould be nice for
** Tags added: multiarch
--
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/1246013
Title:
Whould be nice for libgl1-mesa-dev to be multiarched
To manage notifications about this bug go to:
Public bug reported:
I often compile stuff for the host (amd64) and target (i386)
architectures using multilib compiler. Unfortunately I need libxdamage-
dev and at the moment I constantly have to re-install it. It would be
great is libxdamage-dev was converted to multiarch:saem.
ProblemType:
*** This bug is a duplicate of bug 1207890 ***
https://bugs.launchpad.net/bugs/1207890
This is actually ubiquity-panel bug, part of ubiquity. Not an xorg bug.
** This bug has been marked a duplicate of bug 1207890
too many panels displayed during install (see screenshot)
--
You received
Public bug reported:
Similar to bug 11588934, I get acpi_video0 intel_backlight, or
(ideapad intel_backlight) depending on the osi_* kernel cmd line
settings. The one that is preferred / used (acpi_video0 / ideapad) do
not work. Whereas intel_backlight is the one that does work. I have
Lenovo
** Attachment added: dmidecode.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1227188/+attachment/3827396/+files/dmidecode.txt
** Summary changed:
- brightness doesn't work
+ brightness doesn't work on Lenovo IdeaPad Yoga 13
--
You received this bug notification because you are a
What is the output of:
$ ubuntu-drivers list
?
We use Modaliases stanza on the package to figure out if your hardware needs it.
Could you also do:
$ lspci
And then lookup modalias for your card in:
$ cat /sys/devices/pci*/*$(DEVICE)/modalias
** Also affects: nvidia-graphics-drivers (Ubuntu)
It looks like drivers were installed:
Jul 8 03:59:55 ubuntu ubiquity: Building dependency tree...
Jul 8 03:59:55 ubuntu ubiquity:
Jul 8 03:59:55 ubuntu ubiquity: Reading state information...
Jul 8 03:59:55 ubuntu ubiquity: The following extra packages will be installed:
Jul 8 03:59:55 ubuntu
Ubiquity bugs are only tracked in Ubuntu ubiquity package.
This issue will not be fixed, in later releases webcam step has been
altogether removed, due to being buggy, creepy and not providing
significant benefit to the users. We may push a change in ubiquity to
also remove the webcam step in
The required changes are too risky for stable releases, and fall out of
scope from both Stable Release Updates [1] and Backports [2] process. I
am against from making such updates available in the Ubuntu Archive. It
will be a support nightmare.
Installing nvidia-current on e.g. intel machine
libx11 is in precise unapproved queue. Unsubscribing ubuntu-sponsors for
now. If more uploads needed, please re-subscribe the team, when ready.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
** Changed in: pyopencl (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AMD graphics
** Changed in: pycuda (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AMD graphics
ogra_21 xnox, ogra@chromebook:~/xf86-video-omap-0.4.0$ grep 24 src/*
ogra_ src/omap_driver.c: default_depth = 24; /* TODO: get from kernel
*/
Changing that to 32, recompiling, in-place replacing allows me to boot
and be presented with the you are running in a low graphics mode and
On 4 March 2013 11:32, reddot 763...@bugs.launchpad.net wrote:
Dmitrijs, currently I've downloaded python-pyopencl packages from raring
and build package locally with no modifications under quantal. After
that package was installed and working find on my quantal box. But
anyway it's tricky way
As per bug status above neither fglrx-installer nor nvidia-common
provided the opencl-icd package, while pyopencl which depends on a such
package got uploaded into quantal. If you want to install pyopencl in
quantal _now_, please use equivs to create a dummy package named
opencl-icd.
--
You
(or whatever other packages are missing)
This change in pyopencl has been reverted in raring, so in raring
python-pyopencl should be installable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
in ubiquity-dm installer, we pre-empt lightdm. Then execute plymouth
deactivate followed by plymouth quit if plymouth does not have an
active-vt. Then we start Xorg straight away, if Xorg fails to start, we
retry with modified 'fallback' configs using fbdev and finally vesa. I
guess in ubiquity-dm
Public bug reported:
in kvm in ubiquity-dm boot.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
** Also affects: pyopencl (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: pyopencl (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
** Changed in: pyopencl (Ubuntu Raring)
Status: Confirmed = Fix Released
** Changed in: pyopencl (Ubuntu
** Changed in: nvidia-graphics-drivers (Ubuntu Quantal)
Status: Confirmed = Won't Fix
** Changed in: nvidia-common (Ubuntu Quantal)
Status: Confirmed = Won't Fix
** Changed in: fglrx-installer (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) = (unassigned)
--
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/1096943
Title:
Ubiquity
** Description changed:
- After installing the latest fglrx-updates package on Ubuntu 12.10
- (fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
- present before AMD fixed switchable graphics on PowerXpress 4.0 cards
- (such as my HD 6470M coupled with the intel HD Graphics 3000
@ Everyone
This is quite a large bug report. Ubuntu Sponsors team is subscribed to this
bug report hence it appears at
http://reqorts.qa.ubuntu.com/reports/sponsoring/ .
Are there any debdiffs / patches ready that need sponsoring?
If yes: which onces?
If no: ubuntu-sponsors team should be
** Package changed: ubuntu = ubiquity (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/1078226
Title:
raring daily: background lightdm look as if they are in 8bit
greyscale mode
To
** Summary changed:
- fails to load background picture in raring daily
+ raring daily: background lightdm look as if they are in 8bit greyscale mode
** Attachment added: lightdm-grey-boxes.png
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Status: New = Invalid
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
cannot login into my session, nor into unity3d nor into gnome
with/without effects.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
Uname: Linux 3.6.0-030600rc4-generic x86_64
ApportVersion: 2.6.2-0ubuntu2
Architecture: amd64
CompizPlugins:
Thank you all.
--
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/1076787
Title:
GLX error: Can not get required symbols
To manage notifications about this bug go to:
I uploaded pyopencl to not pull in fglrx by default.
** Also affects: pyopencl (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pyopencl (Ubuntu Raring)
Status: New = Fix Released
** Changed in: pyopencl (Ubuntu Raring)
Importance: Undecided = High
--
You received
@nouveau folks look at the spam in UbiquitySyslog.txt
** Also affects: xserver-xorg-video-nouveau (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-nouveau in Ubuntu.
You are using an old image, please use a more recent one. There were a few
related bugs fixed. Please file a new bug if a newer image is also failing. The
most current image has 20121014 timestamp.
LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
You can use zsync with zsync
This is not ubiquity bug. But kernel / driver / X. Please do not assign
this back to ubiquity.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status:
@ M. van der Heide sure you assign it to ubiquity (the graphical)
install _until_ somebody triages to be a problem in another package.
There are hundreds of software packages that get you the graphical
installer, and we do need to start narrowing it down. Usually we start
with ubiquity and then
I am hitting this bug. Can somebody please explain how to check if I am
using UXA or SNA and how to switch between the two? If SNA helps, and I
am using UXA I'd like to try SNA.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Cannot switch to TTY, cannot move mouse, everything is stuck including
performance indicators clock.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
Uname: Linux 3.6.0-030600-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.6.1-0ubuntu1
--
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/1061441
Title:
graphical desktop locksup and becomes non-responsive
To manage notifications about this bug go to:
Nevermind the kernel version. Happens with both ubuntu's stock / latest
3.5 kernel as well as the mainline kernel ppa 3.6-final.
--
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/1061441
Title:
Preferably don't add this dependency. This should be seeded as part of
ubuntu-desktop, and weston itself should fall back to
$something_sensible if the path isn't set.
from the spec
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
If $XDG_RUNTIME_DIR is not set
I am not sure what good fallback location is.
** Changed in: weston (Ubuntu)
Assignee: Logan Rosen (logan) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to weston in Ubuntu.
https://bugs.launchpad.net/bugs/1058211
Title:
** Also affects: nvidia-common (Ubuntu Quantal)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: Confirmed
** Also affects: pyopencl (Ubuntu Quantal)
Importance: High
Assignee: Dmitrijs Ledkovs (xnox)
Status: Fix Released
--
You received this bug
well, because we do not keep debug symbols for all package releases
it will be sometimes have a scew. Which is a blueprint type of work
aimed to be fixed sometime.
** Changed in: mesa (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member
Same in Virt Manager with graphics selected as vmvga
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
** Changed in: ubiquity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification
= Medium
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided = Medium
** Changed in: pyopencl (Ubuntu)
Assignee: (unassigned) = Dmitrijs Ledkovs (dmitrij.ledkov)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone
This bug was fixed in the package pyopencl - 2012.1-1
---
pyopencl (2012.1-1) unstable; urgency=low
* New upstream release.
* Depend on free ocl-icd-libopencl1 instead of non-free libraries.
* Add NEWS entry describing OpenCL library dependencies.
* Change my email.
* Move
All done now! Thank you everyone for quick responses and patches!
--
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/1013171
Title:
Many package hooks not ported to python3
To manage
It would help a lot to keep the python hooks both python2.7 (precise)
and python3 (quantal+) for the upgrade case where your hook maybe run
with either pythons.
https://wiki.ubuntu.com/Python/3
Most of the time it's easy to accomplish with:
from __future__ import print_function
Which is valid
I will look into mdadm hook
** Changed in: mdadm (Ubuntu Quantal)
Assignee: (unassigned) = Dmitrijs Ledkovs (dmitrij.ledkov)
--
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/1013171
apport information
** Tags added: apport-collected natty ubuntu
** Description changed:
Binary package hint: xorg
I have early 2006 Macbook (1.1) changing the LCD brightness using the
keyboard keys previously resulted in smooth brightness changes (from 0%
- 100%). I've upgraded to
apport information
** Attachment added: DRM.card0.SVIDEO.1.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864738/+files/DRM.card0.SVIDEO.1.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864737/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: peripherals.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864755/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Yeap, still a problem in natty. Same steps to reproduce as in the
original description.
--
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/619726
Title:
[regression since lucid]
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864756/+files/xdpyinfo.txt
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864754/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864745/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864746/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864747/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864748/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864739/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864740/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: GdmLog.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864741/+files/GdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: GdmLog1.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864742/+files/GdmLog1.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: GdmLog2.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864743/+files/GdmLog2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864749/+files/UdevDb.txt
** Summary changed:
- [regression, maverick] LCD backlight brightness steps are inconsistent
+ [regression since lucid] LCD backlight brightness steps are
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864744/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864751/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864752/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864753/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/619726/+attachment/1864750/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Right investigating further:
On my machine /sys/class/backlight/mbp_backlight is a symlink to
/sys/devices/virtual/backlight/mbp_backlight
In there the max brightness value is 15. And the lowest value
(experimental) is 0.
echo 0..15 into the brightness file in the above mentioned folder
changes
Dear Ubuntu X team, thank you very much for all of your hard work! You get
loads of bug reports and from my point of view you are handling it really well.
The latest ping from your bot to check this bug out, prompted me to check the
freedesktop bugzilla and search for similar brightness key
For me the crash happens after I enter the password to unlock my
keyring. I can wait it will continue to work normally, but as soon as
I hit enter to submit password to unlock the keyring the crash
happens.
ps. I'm using auto-login.
--
gdm restarts on initial login
Public bug reported:
Binary package hint: xorg
I have early 2006 Macbook (1.1) changing the LCD brightness using the
keyboard keys previously resulted in smooth brightness changes (from 0%
- 100%). I've upgraded to maverick yesterday and the minus
brightness key when going from 100% results in
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/619726/+attachment/1497457/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/619726/+attachment/1497458/+files/CurrentDmesg.txt
** Attachment added:
*** This bug is a duplicate of bug 584477 ***
https://bugs.launchpad.net/bugs/584477
** This bug has been marked a duplicate of bug 584477
glxinfo is messed up
--
[Lucid Beta 1] Case ID: xpr-006 failed, glxinfo segmentation fault
https://bugs.launchpad.net/bugs/553435
You received this
** Summary changed:
- glxinfo is messed up
+ mesa dbg packages are still have CRC mismatch in lucid
** Summary changed:
- mesa dbg packages are still have CRC mismatch in lucid
+ mesa dbg packages still have CRC mismatch in lucid
--
mesa dbg packages still have CRC mismatch in lucid
Public bug reported:
I am not sure if this bug is reported. I've reinstalled lucid from
scratch updated it.
Here is how to reproduce this:
$ glxinfo
name of display: :0.0
Segmentation fault
dmit...@surgut:~$ gdb glxinfo
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48958017/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48958018/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48958019/Dependencies.txt
**
** Tags added: patch-accepted
** Tags removed: patch
--
Does not support current Lucid kernel (2.6.32) or xserver (1.7)
https://bugs.launchpad.net/bugs/494699
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
With upgrade from ppa the system is still stable but when I use chromium
I get freeze shortly afterwards.
** Attachment added: xserver-xorg-video-intel.2010-03-05_13:36:52.509175.crash
http://launchpadlibrarian.net/40248553/xserver-xorg-video-intel.2010-03-05_13%3A36%3A52.509175.crash
--
desktop-couch crashes slightly after xorg (time of crash report)
** Attachment added: _usr_lib_desktopcouch_desktopcouch-service.1000.crash
http://launchpadlibrarian.net/40248925/_usr_lib_desktopcouch_desktopcouch-service.1000.crash
--
Xorg freeze Chromium Black screen of not death
Public bug reported:
Binary package hint: xorg
Attaching apport crash see Bug #522937
Basicly x crashes when using chromium. It produced a few other crashes
as well i will upload them to launchpad soon.
ProblemType: Bug
Architecture: i386
Date: Sat Feb 27 14:17:23 2010
DistroRelease: Ubuntu
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/39855389/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/39855390/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39855391/Dependencies.txt
**
See Bug #529006 does that now have more info you require? Apport did it
for me
I have found desktop-couch, chromium and gwibber crashes as well which
happened less than one minute after the xorg one. maybe they are all
related
--
Black Screen of not death
I think this is standard xorg freezes class bug.
# When did you first notice it? Did you change any settings (Desktop Effects?)
or update your system prior to first noticing it?
After upgrading to Lucid
# What frequency does it occur? Just once? Hourly? Daily?
5-10minutes after using Chromium
** Attachment added: lspci.txt
http://launchpadlibrarian.net/39693426/lspci.txt
** Tags removed: needs-lspci-vvnn
--
Black Screen of not death
https://bugs.launchpad.net/bugs/522937
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
LinkedIn
Bug,
I'd like to add you to my professional network on LinkedIn.
- Dmitrijs Ledkovs
Dmitrijs Ledkovs
Student at The University of Hull
United Kingdom
Confirm that you know Dmitrijs Ledkovs
https://www.linkedin.com/e/isd/1067430355/atgqGcaI/
--
(c) 2010
Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич
--
MASTER: Poor graphics performance on Intel
https://bugs.launchpad.net/bugs/252094
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel
90 matches
Mail list logo
