** 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/881725
Title:
"xset: unable to open display" while do-release-upgrade v
** Description changed:
Binary package hint: xserver-xorg-video-intel
- After some time X randomly crashes. This time it crashes when I middle-
+ After some time X randomly crashes. This time it crashed when I middle-
clicked a link in chromium.
Backtrace:
[ 9958.320] 0: /usr/bin/X
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After some time X randomly crashes. This time it crashed when I middle-
clicked a link in chromium.
Backtrace:
[ 9958.320] 0: /usr/bin/X (xorg_backtrace+0x26) [0x4a2626]
[ 9958.320] 1: /usr/bin/X (0x40+0x6219a) [0x46219a]
[
*** This bug is a duplicate of bug 539477 ***
https://bugs.launchpad.net/bugs/539477
** This bug has been marked a duplicate of bug 539477
Video out hot key sends super + p + return on many upcoming Dell & HP systems
--
Fn+switch screen key (F8) doesn't work on DELL e4300
https://bugs.lau
This is fixed in 2.6.32-19.
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in ubuntu.
_
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/41263483/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/41263484/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41263485/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
Although the touchpad on the Dell Latitude E6400 has physical buttons, a
tap on the top right corner of the touchpad simulates a middle click and
a tap on the bottom right corner simulates a right click. As the scroll
area is
This is fixed in Karmic and Lucid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
[g45] (Needs kernel 2.6.31-rc1) Xorg freeze after resume (UXA bug) (KMS bug)
https://bugs.launchpad.net/bugs/382159
You received this bug notification because you are a member of Ubuntu-
I didn't encounter this problem anymore in karmic.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
[gm45] task xorg/i915 blocked after resume
https://bugs.launchpad.net/bugs/421032
You received this bug notification because you are a member of Ubuntu-
** Attachment added: "dmesg"
http://launchpadlibrarian.net/39105467/dmesg
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/39105480/Xorg.0.log
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is su
Using xorg-edgers (libdrm 2.4.17+git20100210.4f0f8717-0ubuntu0sarvatt,
which contains commit 4f0f871730b76730ca58209181d16725b0c40184) seems to
at least partially "fix" it:
- log in to gnome with compiz enabled
- close lid -> backlight turns off
- open lid -> backlight stays off
- switch vts: vt7
Nicolò, removing the plymouth package unfortunately doesn't solve it for
me. It's still crashing every time I close the lid.
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you
The kernel without that commit had no problems with either compiz or
metacity. Closing the display lid disabled the backlight, opening the
lid turned the backlight on again. No error messages from the kernel,
everything worked just fine :)
--
[gm45] "*ERROR* Execbuf while wedged" when closing lap
Okay, bisecting ended with:
11ed50ec2a316928c2bacc1149bded86c6a96068 is the first bad commit
commit 11ed50ec2a316928c2bacc1149bded86c6a96068
Author: Ben Gamari
Date: Mon Sep 14 17:48:45 2009 -0400
drm/i915: Implement GPU reset on i965
This patch puts in place the machinery to atte
No, I didn't, just this one.
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
__
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xser
I tried it several times more, sometimes the vt-switching workaround was
working, sometimes it wasn't. I tried opening the lid immediately after closing
it, waiting a bit before opening it and even tried running glxgears while I was
closing it, I couldn't find a pattern.
I even got 2.9.1-1ubuntu
I was testing the 2.6.33 kernel from the mainline kernel-ppa yesterday,
but have since reverted back to 2.6.32. The funny thing is that I was
also testing xorg-edgers yesterday and IIRC I also tried vt-switching to
enable my display again, which didn't work.
I have no idea why it is working today,
Alright, crashing with 2.9.1-1ubuntu1 as usual, recoverable with
2.10.0+git20100108.4902f546-0ubuntu0sarvatt by switching VTs.
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because yo
xserver-xorg-video-intel 2.10.0+git20100108.4902f546-0ubuntu0sarvatt
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/37714949/Xorg.0.log
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is su
** Attachment added: "dmesg"
http://launchpadlibrarian.net/37714889/dmesg
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
It's recoverable with xorg-edgers (either that, or the update to kernel
2.6.32-10)! The display is still blank (backlight off) after opening the lid
again, but vt-switching makes the display usable again, with compiz and
everything.
Attaching dmesg output and Xorg.0.log.
--
[gm45] "*ERROR* Exe
I followed the instructions on https://wiki.ubuntu.com/X/Troubleshooting/Freeze
on how to get a batchbuffer dump, unfortunately i915_batchbuffers is empty.
I inserted "export INTEL_DEBUG=batch into /etc/init/gdm.conf, right before
"exec gdm-binary $CONFIG_FILE", does this suffice?
** Attachment
This may be a duplicate of https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/+bug/503255, but since I can't reproduce this
by running xrandr, I filed a new bug.
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Steps to reproduce:
1. Log in and have compiz activated in your user session
2. Close the laptop lid (gnome-power-manager is configured to blank the display
on lid close)
3. Open the laptop lid again
Expected result:
Display tur
dmesg after opening the lid again
** Attachment added: "dmesg"
http://launchpadlibrarian.net/37657686/dmesg
--
[gm45] "*ERROR* Execbuf while wedged" when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/37657619/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/37657620/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37657621/Dependencies.txt
** A
I have also seen this, the monitor blanks for a split second during
normal use and then returns to normal. It occured only on DVI1, I never
saw it happen on LVDS1. Could this be bug #275152 again? I had/have
frequent monitor blanks on Jaunty. On Karmic, I saw it maybe five times
since alpha 2.
Sam
Running "torcs" caused it to reappear, attaching the requested
information.
** Attachment added: "dri_debug.tgz"
http://launchpadlibrarian.net/30985243/dri_debug.tgz
--
[GM45] task xorg/i915 blocked after resume
https://bugs.launchpad.net/bugs/421032
You received this bug notification because
Just tried 9 suspend/resume cycles without any blocking, I don't know
how to trigger this.
--
[GM45] task xorg/i915 blocked after resume
https://bugs.launchpad.net/bugs/421032
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
** Attachment added: "kern.log with blocked xorg/i915"
http://launchpadlibrarian.net/30964794/kern.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/30964795/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/30964796/CurrentDmesg.tx
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After resume I just saw the wallpaper and mouse pointer, couldn't switch
ttys. Login via ssh was very slow, but managed to reboot remotely.
Snippet from kern.log (see attached file for complete log):
[6.692263] INFO: task Xo
No, the problem still remains.
KMS detects and sets the "preferred" resolutions for each device correctly
(1600x1200 on DVI1, 1440x900 on LVDS1). When X starts up, the resolutions set
by KMS IMHO should be kept, but aren't. X sets both displays to the highest
common resolution, which is 1152x86
Just noticed the following:
LVDS1 is disabled by GNOME according to the display settings set there.
VT-switching enables LVDS1 and shows the console. If I switch back to X, I
first have to manually enable LVDS1 (xrandr --output LVDS1 --auto) before I can
turn it off again (xrandr --output LVDS1 --o
Using xserver-xorg-video-intel 2:2.8.0-0ubuntu1 and linux-
image-2.6.31-4-generic 2.6.31-4.23, this appears to be fixed.
$ time xrandr -q
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected (normal left
** Attachment added: "Kernel messages while docked"
http://launchpadlibrarian.net/29660967/dmesg_docked_closed
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu-X,
which
** Attachment added: "Output of xrandr while docked"
http://launchpadlibrarian.net/29660946/xrandr_docked
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu-X,
which is s
Sorry that it took so long for me to respond.
I tested it with xserver-xorg-video-intel 2:2.8.0-0ubuntu1 and
linux-image-2.6.31-4-generic 2.6.31-4.23 and observed the following behaviour:
Booting docked with DVI1 attached, lid closed/open (doesn't make a difference):
- If lid is closed, only DVI1
** Attachment added: "Output of xrandr while undocked"
http://launchpadlibrarian.net/29661005/xrandr_undocked
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu-X,
which
** Attachment added: "Kernel messages while undocked"
http://launchpadlibrarian.net/29661008/dmesg_undocked
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "Xorg.0.log_undocked"
http://launchpadlibrarian.net/29661032/Xorg.0.log_undocked
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Invalid => New
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You rec
** Attachment added: "Xorg.0.log_docked"
http://launchpadlibrarian.net/29660980/Xorg.0.log_docked
--
[g45] Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
This appears to be only the case if something is attached to the DVI1
port:
$ time xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 303mm
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27889881/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27889882/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27889883/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Calling xrandr takes nearly 3 seconds with KMS, during which X is not
usable (mouse pointer not movable, static image).
This probably causes the login process (gnome) to delay considerably (as AFAIK
during gnome startup the reso
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27889146/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27889147/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27889148/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I have an internal laptop display and an external display attached via
DVI. Both displays are enabled during boot.
1. Disable laptop display (System -> Settings -> Display), leaving the external
display the only one being enable
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27576651/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27576652/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27576653/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
On a GM45, X freezes as soon as DPMS kicks in and turns off the monitor
on HDMI-1 and has to be killed via sysrq-k.
Xorg.0.log.old states:
(WW) intel(0): ESR is 0x0011, page table error
(WW) intel(0): PGTBL_ER is 0x0010,
X is also crashing here after login. The compiz update to
0.8.2-0ubuntu12 changed the behavior somewhat. Before the update, X
crashed as soon as I had entered my password. After the update, I can
see at least gnome-panel loading, then it crashes.
Note that X only crashes if I enable KMS. Without K
Switching to fullscreen mode in totem/mplayer/firefox also triggers a
crash.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
x server dies with a SIGSEGV when gnome screen saver blanks the display
https://bugs.launchpad.net/bugs/383129
You received this bug notification because y
*** This bug is a duplicate of bug 383129 ***
https://bugs.launchpad.net/bugs/383129
** This bug has been marked a duplicate of bug 383129
x server dies with a SIGSEGV when gnome screen saver blanks the display
--
[GM45] Switching apps to fullscreen mode causes X to crash (UXA)
https://bu
** Attachment added: "gdb-Xorg.txt"
http://launchpadlibrarian.net/27459982/gdb-Xorg.txt
--
[GM45] Switching apps to fullscreen mode causes X to crash (UXA)
https://bugs.launchpad.net/bugs/383172
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27455873/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27455874/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27455875/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Switching to fullscreen mode in mplayer/totem/firefox reliably causes X
to crash on a X4500MHD (Dell Latitude E6400) since UXA was enabled by
default.
ProblemType: Bug
Architecture: amd64
Date: Wed Jun 3 15:55:02 2009
DistroRele
** Attachment added: "kern.log after failed resume while X is still running,
but not responding any more"
http://launchpadlibrarian.net/27332335/kern.log.kms
--
[KMS] [GM45]: Xorg freeze after resume
https://bugs.launchpad.net/bugs/382159
You received this bug notification because you are a
** Attachment added: "Xorg.0.log after failed resume while X is still running,
but not responding any more"
http://launchpadlibrarian.net/27332248/Xorg.0.log.kms
--
[KMS] [GM45]: Xorg freeze after resume
https://bugs.launchpad.net/bugs/382159
You received this bug notification because you ar
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27332207/Dependencies.txt
--
[KMS] [GM45]: Xorg freeze after resume
https://bugs.launchpad.net/bugs/382159
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Public bug reported:
Binary package hint: xorg
I tested KMS + UXA on a Dell Latitude E6400 with an Intel X4500MHD
according to https://wiki.ubuntu.com/X/KernelModeSetting.
If I am logged in and initiate suspend by pressing Fn+F1, the screen is locked
and then the machine suspends successfully.
61 matches
Mail list logo
