Ok, I also noticed a coredump file was created in my home directory
yesterday in an attempt to enable coredumps. The attached backtrace was
generated using the instructions on
https://wiki.debian.org/XStrikeForce/XserverDebugging
--
Mvg, Sander Devrieze.
Op di 27 apr. 2021 om 13:25 schreef
.uploaded
-rw-r- 1 sander whoopsie 25M apr 26 17:22
_usr_bin_gnome-shell.1027.crash
-rw-rw-r-- 1 sander whoopsie0 apr 26 17:22
_usr_bin_gnome-shell.1027.upload
-rw--- 1 whoopsie whoopsie0 apr 26 17:22
_usr_bin_gnome-shell.1027.uploaded
-rw-r- 1 gdm whoopsie 4,9M apr 26 16
Public bug reported:
The X Server consistently crashes when my Wacom Intuos Pro Medium tablet
is attached to my Dell XPS 13 laptop whilst I have a second screen
connected using the HDMI port on the Dell DA300 hub. The crash does not
immediately happens when the Wacom devices is attached, but
Updates:
1) The workaround is only temporarily working. After some time of
handling both the mouse and the Wacom tabled, Xorg consistently keeps
crashing. Obviously, this is making using the tablet under Ubuntu
unworkable.
2) I tried using the tablet in a Wayland session and that seems to solve
Public bug reported:
When touching an unmapped tablet button, Xorg crashes. This happens
immediately when working in Gimp and might need a few presses when Gimp
is not open.
This bug is very consistent and I can repeat it always, even after a
reboot.
Workaround: I configured all unmapped
ere for the last 3 to 4
years accept
for an endless stream of duplicates being appended.
--
Sander
--
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/1140716
Title:
[regression] 3.5.0-26-ge
ere for the last 3 to 4
years accept
for an endless stream of duplicates being appended.
--
Sander
--
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/1041790
Title:
[snb] GPU lockup
** Summary changed:
- fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices
(Radeon HD 2400, 3300, 3470, 4570, 4650)
+ fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices
(Radeon HD 2400, 3300, 3470, 4570, 4650, 4670)
--
You received this bug notification
Cannot reproduce this crash anymore.
Only a couple of packages are different since then:
@ -7 +7 @@
-dbus 1.6.12-0ubuntu7
+dbus 1.6.12-0ubuntu10
@@ -15 +15 @@
-gcc-4.8-base 4.8.1-10ubuntu6
+gcc-4.8-base 4.8.1-10ubuntu9
@@ -17,2 +17,2 @@
-initramfs-tools 0.103ubuntu1
-initramfs-tools-bin
I have tried disabling fglrx with: aptitide purge fglrx
So I could instead use the xserver-xorg-video-ati driver.
But I was unable to get the free driver up and running.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in
Public bug reported:
Everything looks to work with my grafic card, movie playback with
acceleration and sound. But im getting theese weird error messages all
the time displaying: We have discovered a problem with your system..
And it asks me 5 times if I want to report it.
How can I get theese
Could be related to bug #939858
Could you please have a look at /var/log/Xorg.*.log and look for lines
starting with (EE) fglrx?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/879092
This also happens on the same hardware running natty:
[347395.593] (II) fglrx(0): Kernel Module Version Information:
[347395.593] (II) fglrx(0): Name: fglrx
[347395.593] (II) fglrx(0): Version: 8.85.6
[347395.593] (II) fglrx(0): Date: Apr 19 2011
[347395.593] (II) fglrx(0): Desc:
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/939858
Title:
Switch user does not work
To
According to http://forums.gentoo.org/viewtopic-t-888290-start-0.html
this could be a conflict with the framebuffer device.
I will try and compile a kernel without builtin fbdev and see if this
solves this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which
I cannot believe that this is really a memory issue.
Yesterday I exchanged the hardware from a single monitor with 128MB
nVidia graphics card to a dual monitor setup with a 256MB ATI
Technologies Inc RV730 [FirePro V5700].
The user switching was working flawlessly with the nVidia proprietary
I removed the fglrx package and configured X to use the radeon driver
with the two monitors.
With the radeon X11 driver I am able to switch users.
I still think this is an fglrx issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
With 3.2.0-10 I can boot normally without adding iommu=off.
(But it was necessary to reinstall the nvidia drivers, before that I couldn't
boot)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I just tried 3.2.0.9 and it still does not work..
Has anyone had any luck with newer kernels than 3.2rc4?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu
I have this problem too.
My videocard is Nvidia Quadro FX 3800.
Adding intel_iommu=off to grub parameters indeed solves this problem
temporarily...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I tried classic desktop (no effects) (at login) and the fglrx driver,
but I still have flashes a few times per minute.
Is this going to be solved with the real Natty release, or is there a
workaround, or should I just stay with Ubuntu 10.x (which shows no
flashes)?
--
You received this bug
I've the same problem with Ubuntu 11.04 daily build (april 9) on my ATI
(!) based system.
I will try “drm_kms_helper.poll=0” as a kernel boot parameter
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
I tried the “drm_kms_helper.poll=0” as a kernel boot parameter, but the
screen still flashes.
sander@athlon64:~$ dmesg | grep helper
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8
-generic-pae root=UUID=9adcf26d-4b8c-48e2-9f9f-528963628734 ro quiet
splash
I had the same bug without twinview. The following workaround solved
this problem for me: edit /etc/X11/xorg.conf and add the line:
Option RenderAccel 0
to the device section. I suppose this workaround is nonoptimal as it
may reduce video acceleration, but it does allow using subpizel font
will re-test this
using Kubuntu, to see if it works there.
On Mon, Oct 4, 2010 at 8:01 PM, Dave Gilbert ubu...@treblig.org wrote:
Hi Sander,
My understanding is the Intel 945 chips have a 2048 horizontal maximum
pixel limit; it can push 4096 pixels with a load of things disabled, but
that's
Dave,
I'm away from the problematic laptop at the moment, but reading the
description my issue is the exact same one. The description of the bug is
precisely what I see. I think you can label my bug as a duplicate. I will,
however, take a look in my Xorg.0.log tomorrow and let you know the
** Attachment added: Monitor preferences screenshot
https://bugs.launchpad.net/bugs/654515/+attachment/1671203/+files/Screenshot-Monitor%20Preferences.png
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/654515/+attachment/1671204/+files/BootDmesg.txt
** Attachment
Public bug reported:
Binary package hint: xorg
TRying to setup a dual-head setup, with a laptop and a flat-panel TFT.
Using the Monitor Preferences panel, I enable the TFT panel and place it
to the right of the laptop screen. If I hit apply, the screen on the
laptop shows the correct image, but
Hi,
I reported bug #484387 back in November. To trace the issue I also tried the
open source nv driver for X, but it also crashed:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/484387/comments/4
--
synaptic assert failure: synaptic: ../../src/xcb_io.c:385:
I just experienced another crash using the nv driver.
This often happens when a second user is active. The session of the
first user crashes. I suspect my IM client (kopete) and its
notifications, but that's not reproducible.
** Attachment added: Xorg.0.log.old
old xorg logfile
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/44275632/Xorg.0.log.old
--
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion
`ret != inval_id' failed.
https://bugs.launchpad.net/bugs/507062
You received this bug notification
Sorry: problems occurs in Lucid Beta 1, about 3 minutes after boot, and
the goes away after one or two minutes...
--
Lucid Lynx Alpha 3: Synaptics Touchpad does not work during first few minutes
after boot
https://bugs.launchpad.net/bugs/542063
You received this bug notification because you are
Now running Lucid Beta1, and the Synaptics Touchpad is working right
from the boot.
Problem gone!
--
Lucid Lynx Alpha 3: Synaptics Touchpad does not work during first few minutes
after boot
https://bugs.launchpad.net/bugs/542063
You received this bug notification because you are a member of
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41309487/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41309488/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41309489/Dependencies.txt
**
Public bug reported:
Binary package hint: xorg
Lucid Lynx Alpha 3: Synaptics Touchpad does not work during first few
minutes after boot
The touchpad is seen by dmesg:
ubu...@ubuntu:~$ dmesg | grep -i touch
[ 70.889343] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps:
It just happened again:
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
2: [0x32e400]
3: /usr/lib/libpixman-1.so.0(pixman_blt+0xfa) [0x73155a]
4: /usr/lib/xorg/modules//libfb.so(fbCopyNtoN+0x1aa) [0x9e672a]
5:
This is the backtrace from /var/log/Xorg.0.log.old
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
2: [0x662400]
3: /usr/lib/libpixman-1.so.0(pixman_fill+0x5c) [0x34e2ec]
4: /usr/lib/xorg/modules//libfb.so(fbFill+0x23d) [0x2d3c4d]
5:
After crashing happened with the proprietary nvidia driver I switched to
the open source nv X driver.
Now my session crashed again. It seems not to be related with the
proprietary nvidia driver.
--
kopete crashes a parallel Xsession
https://bugs.launchpad.net/bugs/484387
You received this bug
I'm now on a live-boot of Karmic Alpha 5 on my all-Intel laptop, and ... no
echoes and no flashes!
Problem solved? I hope so ...
--
karmic alpha 3 flashing and echoing screen
https://bugs.launchpad.net/bugs/404528
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: sudo-lspci-vvnn.txt
http://launchpadlibrarian.net/30484751/sudo-lspci-vvnn.txt
--
karmic alpha 3 flashing and echoing screen
https://bugs.launchpad.net/bugs/404528
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: var-log-Xorg.0.log
http://launchpadlibrarian.net/30484775/var-log-Xorg.0.log
--
karmic alpha 3 flashing and echoing screen
https://bugs.launchpad.net/bugs/404528
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: var-log-Xorg.0.log.old
http://launchpadlibrarian.net/30484776/var-log-Xorg.0.log.old
--
karmic alpha 3 flashing and echoing screen
https://bugs.launchpad.net/bugs/404528
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I am now running Karmic Alpha 4 from the live CD on the same laptop, and
still get the flashes and echo's. Very annoying. It makes Karmic Alpha 3
and 4 unusable.
--
karmic alpha 3 flashing and echoing screen
https://bugs.launchpad.net/bugs/404528
You received this bug notification because you
43 matches
Mail list logo
