Pedro, I'm sure you are experiencing a bug and that you want to report
it so that it can be fixed. However, in order to do that, please file a
new bug instead of commenting on a bug report for a bug that has already
been fixed.
--
You received this bug notification because you are a member of Ubu
migiel, the login/user photo screen is supposed to be _after_ the "who
are you" screen. It is the loading of that page (which you don't get to
see) which triggers the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Thanks Michael. I have marked bug #933105 and bug #950952 as duplicates
of this bug. Apologies for making the title of this bug report so much
geared towards the developers who could fix the bug that regular users
experiencing it would not recognize that they were affected by it. I
hope the new tit
** Summary changed:
- [Precise] Ubiquity hangs in ubi-webcam.py
+ [Precise] Installation freezes after "Who are you?" (Ubiquity hangs in
ubi-webcam.py)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9
*** This bug is a duplicate of bug 909179 ***
https://bugs.launchpad.net/bugs/909179
** This bug has been marked a duplicate of bug 909179
[Precise] Ubiquity hangs in ubi-webcam.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 909179 ***
https://bugs.launchpad.net/bugs/909179
** This bug is no longer a duplicate of bug 933105
Installer hangs when entering account information
** This bug has been marked a duplicate of bug 909179
[Precise] Ubiquity hangs in ubi-webcam.py
--
Y
** Description changed:
During installation, after entering the user information, the installer
slows down to a crawl and the status bar (which says "Copying files")
stops. Upon switching VT to 2 and back to 7, the window contents is not
- updated. Checking with top, the ubiquity process use
** Summary changed:
- [Precise] Ubiquity uses up all memory and hangs during installation
+ [Precise] Ubiquity hangs in ubi-webcam.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Title:
[Pr
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649231/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9091
apport information
** Attachment added: "UbiquityPartman.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649230/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/90
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649229/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Titl
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649228/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649227/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
I tried again using 'ubiquity --debug --pdb'. Same thing happened, but
now hopefully the apport-collected files will contain more useful
information.
** Description changed:
During installation, after entering the user information, the installer
slows down to a crawl and the status bar (which
apport information
** Attachment added: "Casper.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2649226/+files/Casper.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Title:
[Pre
** Description changed:
- During installation, after entering the user information, the installer slows
down to a crawl and the status bar (which says "Copying files") stops. Upon
switching VT to 2 and back to 7, the window contents is not updated. Checking
with top, the ubiquity process uses 7
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648639/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9091
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648636/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
apport information
** Attachment added: "UbiquityPartman.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648638/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/90
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648637/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Titl
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648635/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Public bug reported:
During installation, after entering the user information, the installer
slows down to a crawl and the status bar (which says "Copying files")
stops. Upon switching VT to 2 and back to 7, the window contents is not
updated. Checking with top, the ubiquity process uses 70-95% CP
apport information
** Attachment added: "Casper.txt"
https://bugs.launchpad.net/bugs/909179/+attachment/2648634/+files/Casper.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909179
Title:
[Pre
The reason that the soname is different in Debian and upstream is
explained in /usr/share/doc/libtiff4/README.Debian:
This version of libtiff is installed with a different shared library
soname from the upstream version. This is because an accidental
change to the library's ABI was introduced som
Phil, this bug report has been closed, and comments on closed bug
reports are not monitored by developers. In order to get someone to
look at this, file a new bug report using the ubuntu-bug command. Use
this bug report as a model and collect the same information that I
have attached here. I don't
This is a master bug report, and no more logs are required despite the
automated message. Besides, the upstream bug report has been closed as
FIXED RESOLVED.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete => Confi
I have tested 0.9.7-1ubuntu1.1, and now my iPhone (with iOS 4.2.1) is
detected. It wasn't before upgrading from 0.9.7-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793616
Title:
lucid and
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605124
Title:
[965gm] "No screens" on startup: "DRM_IOCTL_I91
Note that the upstream 845G bug report has been reopened. It turned out
that the fixes (which are contained in Brian's PPA kernel) are
insufficient to fix the 845G-specific problem completely. The kernel
will probably improve stability on 845G, but I think adding results from
845G to the upstream b
I have previously used the instructions at
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Instead of getting
the vanilla upstream kernel in #2, I would use the drm-intel-next head
from git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git.
Then you would need to apply the patch bef
For completeness, I should add that the upstream fix introduces another
bug which may cause some corruption. This one is fixed in this commit:
commit dc3bfebcf77d943b7e8495d30d0ee3d01b3042a5
Author: Chris Wilson
Date: Thu Dec 30 18:02:21 2010 +
drm/i915: Don't skip ring flushes if only
Note that the new patch upstream fixes the 845G-specific part of this
bug. The 845G also suffers from the same i8xx incoherency that the 855GM
suffers from (LP bug 541511). There is a patch for that as well at
https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281, but this has
not been commited y
There is a (yet another) new kernel patch in the upstream bug report that has
the potential to fix this bug once and for all:
https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281
I don't have the resources (full hard drive and other limitations) to
build a Ubuntu kernel package with this patch
> Why was this closed. Because you hope it's fixed?
> Same issue on Fedora 12:
I do hope it is fixed, but that was not the reason I closed the bug
report.
It is an unfortunate reality that there is not enough people with
enough time to handle ubuntu and specifically xserver-xorg-video-intel
bug r
I agree that it is not worth the trouble putting this through as an SRU.
--
Failsafe X displays variable name instead of file name for debugging tarball
https://bugs.launchpad.net/bugs/596819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
On Mon, Aug 9, 2010 at 1:59 AM, Warren E. Downs wrote:
> Regarding ppa kernel.ubuntu.com/~kernel-ppa/mainline/, I tried adding
> the source but it wasn't recognized. I noticed that there is no 'dists'
> directory under it like apt expects. Is there another source or do I
> have to install the ker
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Triaged
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Low
--
[i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001)
https://bugs.launchpad.net/bugs/611951
You received this bug notification because
I have forwarded this bug the intel developers at
https://bugs.freedesktop.org/show_bug.cgi?id=29345 . Please register at
bugs.freedesktop.org, add yourself to the CC: field of that bug report,
and respond to any requests made by the intel developers. If you need
help with fulfilling any of these r
** Tags added: resume suspend
--
[i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001)
https://bugs.launchpad.net/bugs/611951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Running intel_error_decode on the attached i915_error_state.txt shows
that there is a page table error and that the ringbuffer is completely
empty:
Time: 1280551135 s 109870 us
PCI ID: 0x27a2
EIR: 0x0010
PGTBL_ER: 0x0001
INSTPM: 0x
IPEIR: 0x
IPEHR: 0x
INST
** Tags added: 945gm
--
[i945gm] GPU lockup d0c69edf
https://bugs.launchpad.net/bugs/611951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
** Tags added: 915gm
** Summary changed:
- Dual monitor instability - reverts to low graphics mode
+ [915gm] Dual monitor instability - reverts to low graphics mode
--
[915gm] Dual monitor instability - reverts to low graphics mode
https://bugs.launchpad.net/bugs/608434
You received this bug no
** Summary changed:
- [IGDgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
+ [pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
** Tags added: pineviewgm
--
[pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
https://bugs.launchpad.net/bugs/607207
You received this bug notification becau
** Summary changed:
- [IGDgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
+ [pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
** Tags added: pineviewgm
--
[pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
https://bugs.launchpad.net/bugs/609717
You received this bug notification becau
** Tags added: arrandale dual-head freeze
** Tags removed: freezing monitor syncmaster
--
[arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is
plugged in
https://bugs.launchpad.net/bugs/610387
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Summary changed:
- Lucid - Intel Integrated Graphics freezes when external monitor is plugged in
+ [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor
is plugged in
--
[arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is
plugged in
https://b
To get the drm-intel kernel tree instead of Linus' tree, instead of
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
use
git clone git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel.git
drm-intel-next is the head of that tree (called master in Linus' tree)
The eDP issue should be completely decoupled from this. Howerver,
following the redhat bug report to the upstream bug report mentions
this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=28911,
which is likely to be the same issue. There is an experimental patch at
comment #4 in that bug
Just to confirm: The dell-wmi messages do not show up when the monitor
is plugged in, but only when xrandr is run and the monitor goes black?
If you let it stand for a couple of minutes before hitting Sysrq-REISUB,
does the BUG: Soft lockup line show up eventually, without you
rebooting?
Otherwis
** Description changed:
Binary package hint: xserver-xorg-video-intel
I cannot hook up an external monitor or beamer to my Dell Latitude E6510
using the VGA port. When I open the "monitors" dialogue, the screen goes black
if there is a VGA cable plugged in. Only alt-sysrq-REISUB works to
Great troubleshooting, Corona! I don't know enough kernel stuff to know
if this means that the dell-wmi is the troublemaker or it simply needs
an update to silence an innocent message. Hopefully the kernel people
know that better, so I think it's time that I send this over there. I am
not sure if t
Following upstream and closing this bug report.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
[gm45] system locks up at random intervals, except mouse
https://bugs.launchpad.net/bugs/469820
You received this bug notification because you are a member
> - When I plug in the VGA cable and switch to VT1, the screen goes black,
> even when I don't run `xrandr -q` first, so that doesn't give any
> additional info.
What if you switch to VT1 and then plug in the monitor? Possibly it
will hang when you switch back to X. If that is the case, what if yo
Chris, good to see that this is on your radar. I wasn't aware that you
were also following Ubuntu bug reports. I was simply hoping that the
kernel triagers would know better how to extract some useful information
about the black screen (which takes down the ssh connection) before
forwarding it upst
In addition to bug 596082, there is also bug 599626 which is very similar. In
that case I gave up and moved to the linux package, since I couldn't find a way
to extract relevant logs. That hasn't been touched for the last two weeks,
though, but I'm afraid this may go the same way eventually. Her
** Summary changed:
- VGA port not working on Dell Latitude E6510 (arrandale, Intel Core i5)
+ [arrandale] VGA port not working on Dell Latitude E6510
** Tags added: arrandale dual-head
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
** Changed in: xserver-xorg-
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even m
*** This bug is a duplicate of bug 604885 ***
https://bugs.launchpad.net/bugs/604885
Marking this as a duplicate to bug 604855, since this is troubleshooting
information for that bug report.
** This bug has been marked a duplicate of bug 604885
No main text between the two lateral frames i
** Tags added: grub-gfxpayload
--
BUG: unable to handle kernel NULL pointer dereference at 0008
https://bugs.launchpad.net/bugs/605440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Dmitry, the Ubuntu bug already has status 'Fix Released'. The upstream
task should be updated automatically from the upstream task.
Btw, I don't think it was the commit you mentioned that fixed this
particular bug, since it has also been working in Maverick before that
commit. That commit probably
Corona, most bug reports will never be assigned to anyone. After
screening and finding the most relevant symptoms, we report in to the
upstream developers who then look at and hopefully fix the bug. Then the
fix is pulled into ubuntu, either by a regular driver update or a patch.
This bug report i
Robert, with the upgrade to kernel 2.6.35-8.13, xorg doesn't have problems, but
the kernel oops still happens. Results from testing with 2.6.35-8.13:
vesafb=fubar doesn't seem to change anything (it still get kernel oops
sometimes, but not always)
gfxpayload=text seems to stop the problems. I hav
I thought 2.6.35-6.8 and other -rc3 based kernels were safe, but now I
got a oops from -6.8 too. dmesg is attached. Unlike with 2.6.35-7, xorg
works fine after this one, and I wouldn't have noticed it if I were not
checking dmesg output or see the apport crash indicator.
** Attachment added: "dmes
Thank you, takashi. I have reopened the upstream bug report and copied
your comment and dmesg there. There will probably be more questions in
the upstream bug report. Please answer those there directly.
--
[i945] X Freezes when compiz enabled
https://bugs.launchpad.net/bugs/475429
You received t
Following upstream and closing since patches can't be tested.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Invalid
--
[i945G] Samsung TV not detected on VGA output (no screens)
https://bugs.launchpad.net/bugs/379157
You received this bug notification because you are
Tomas, the question in comment #59 was meant for the original reporter
of the bug, takashi torigoe (sorry for not specifying that). These kind
of bugs may look exactly the same but have totally different underlying
causes, so your freeze may be an unrelated bug.
If you are the experiencing freeze
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/51926646/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/51926647/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/51926648/BootDmesg.txt
** Att
Public bug reported:
This bug may be the underlying problem of bug 605124, which I have
reported upstream as https://bugs.freedesktop.org/show_bug.cgi?id=29048
. I had written some more relevant information here, but I was struck by
bug 553946 for the second time today, and can't remember what it
** Bug watch added: freedesktop.org Bugzilla #29048
http://bugs.freedesktop.org/show_bug.cgi?id=29048
** Also affects: xserver-xorg-video-intel via
http://bugs.freedesktop.org/show_bug.cgi?id=29048
Importance: Unknown
Status: Unknown
--
[965gm] "No screens" on startup: "DRM_IOCTL
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51911990/Dependencies.txt
--
ureadahead conf file format is undocumented
https://bugs.launchpad.net/bugs/605301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: ureadahead
The format and options of
/etc/init/ureadahead.conf
/etc/init/ureadahead-other.conf
are not documented in any file in the ureadahead package.
I suppose the best place to include it is in a common man page for
ureadahead.conf and ureadahead-ot
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51911656/Dependencies.txt
--
ureadahead man page does not include exit status
https://bugs.launchpad.net/bugs/605300
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: ureadahead
The man page for ureadahead does not include exit status. It should be
unnecessary to browse internet forums to find out what exit status 5
means (or 4 for that sake).
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ureadahead 0.100.0-5
** Description changed:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
- out of 5 or 6 times so far) when booting with an external monitor
- attached I get a "no screens" error in the log and get xorg in low-
- graphics mo
I saw the line
Pid: 343, comm: plymouthd Not tainted 2.6.35-7-generic #12-Ubuntu
7764CTO/7764CTO
in the dmesg output, so I tried to remove the kernel options "quiet splash",
but to no avail. dmesg looks the same to me, but is attached.
** Attachment added: "dmesg with drm.debug=0x04 without qui
** Description changed:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
out of 5 or 6 times so far) when booting with an external monitor
attached I get a "no screens" error in the log and get xorg in low-
graphics mo
** Attachment added: "/var/log/gdm/:5.log with problem"
http://launchpadlibrarian.net/51885543/%3A5.log
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notification because you are a me
** Attachment added: "Xorg.5.log without external monitor with problem"
http://launchpadlibrarian.net/51885483/Xorg.5.log
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notification be
** Attachment added: "dmesg with 0x04 with problem and without external monitor"
http://launchpadlibrarian.net/51885206/dmesg-noexternal-bug.txt
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received t
** Attachment added: "/var/log/gdm/:0.log without problem"
http://launchpadlibrarian.net/51884021/%3A0.log
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notification because you are a
** Attachment added: "Xorg.0.log without external monitor and without problem"
http://launchpadlibrarian.net/51883838/Xorg.0.log
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notifica
It turns out that this can happen also without an external monitor
attached, so I will remove that part of the description. I will upload
dmesg and Xorg.0.log, for a bad and fine session.
** Attachment added: "dmesg with 0x04 without problem and without external
monitor"
http://launchpadlibrar
** Attachment added: "Xorg.0.log from when the problem does not occur"
http://launchpadlibrarian.net/51883077/Xorg.0.log.old
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notification
** Attachment added: "dmesg with 0x04 when the problem does not occur"
http://launchpadlibrarian.net/51882987/dmesg-fine.txt
--
[965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor"
https://bugs.launchpad.net/bugs/605124
You received this bug notification
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/51880252/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/51880253/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51880254/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
out of 5 or 6 times so far) when booting with an external monitor
attached I get a "no screens" error in the log and get xorg in low-
graphics mode. I haven't s
The problem is in line 177 of debian/local/Failsafe/failsafeXinit. There
is an \ before the $ in $xorg_backup_file which shouldn't be there.
Since there is an eval_gettext at the beginning, the varable name was
probably supposed to be part of the preceding string. So either remove
the \ or do every
I can now confirm this myself. I have installed a Maverick partition and
got a "no screens" when booting with an external monitor attached and X
in low-graphics mode. Thanks to Glen for already finding out where the
failsafeX-backup-tar went.
** Description changed:
Binary package hint: xor
Thank you for testing Nicolò. I will close the upstream bug report.
--
[gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the
laptop lid)
https://bugs.launchpad.net/bugs/535640
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The patch that fixed (or rather worked around) this problem in Lucid has
not been applied upstream because the developers figure it is not
necessary anymore due to some other fixes. The Maverick kernel has been
without this patch for quite some time now. Could someone that was
affected with this bu
Robert Hooker wrote in comment #3:
> It looks like our friend bug #535640 is back as the patch fixing that is not
> upstream yet.
I suppose we talk about:
SAUCE: drm/i915: don't change DRM configuration when releasing load detect pipe
It looks like that patch is not going to end up upstream. See
According to the upstream bug report, two commits to the kernel should
fix this bug. The commits are included in the current Maverick kernel.
Could you verify that this now works in Maverick?
--
[i945] X Freezes when compiz enabled
https://bugs.launchpad.net/bugs/475429
You received this bug noti
1 - 100 of 2693 matches
Mail list logo
