Thanks, closing the bug.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Incomplete => Fix Released
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I haven't seen this bug for a while, and yes, I am testing on Lucid
right now. Everything's a-okay; you can close this.
On 9 April 2010 09:34, Timo Aaltonen wrote:
> Can you still reproduce it on lucid?
>
> ** Package changed: wacom-tools (Ubuntu) => xf86-input-wacom (Ubuntu)
>
> --
> x11 won't
Can you still reproduce it on lucid?
** Package changed: wacom-tools (Ubuntu) => xf86-input-wacom (Ubuntu)
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: jaunty
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
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/ma
I've been seeing the same problem, and have managed to get a backtrace
(I used DEB_BUILD_OPTIONS=nostrip for dpkg-buildpackage)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb799e6d0 (LWP 3953)]
xf86WcmDevOpen (pWcm=0xb159428) at ../../../src/xdrv/xf86Wacom.c:794
794
Hmm, actually I'm not spotting a place where the null dev pointer is
getting dereferenced. It seems the crash is occurring somewhere within
the wacom driver. So we would definitely need a backtrace with the
wacom-tools dbg symbols installed. It's sort of a shame that the crash
went away after in
Thanks for the more complete backtrace. Looks like it's a regular old
null pointer deref.
dev == 0x0
ret = (*dev->deviceProc) (dev, DEVICE_INIT);
** Changed in: xorg-server (Ubuntu)
Importance: Medium => High
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
S
** Description changed:
Binary package hint: xorg
Last week I upgraded from intrepid to jaunty. After the reboot, X11
failed to start. It looks like it tried a few times before giving up.
That is, after the splash logo and boot progress bar, it alternated
several times between a black
Hi, I probably can confirm this.
I am using an Asus eeePC 701.
Since kernel 2.6.28-7 I just see the splash logo and afterwards the screen is
black. strg-alt-F* just makes the screen background blink once.
2.6.28-6 works fine.
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.ne
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: xorg => xorg-server
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
I built and installed an unstripped version of the xserver-xorg-input-
wacom package, and the segfault went away. X launched just fine with the
wacom entries in xorg.conf. Ugh.
Attaching a new Xorg.0.log from the run with the self-built wacom driver
and the xorg.conf_20090204 above. It doesn't try
Attaching the xorg.conf that caused the crash. At some point, the three
wacom entries were added; removing them and the references from the
ServerLayout section avoids the crash. My system has no
/dev/input/wacom.
** Attachment added: "xorg.conf_20090204"
http://launchpadlibrarian.net/21994205/
The crash is in the wacom driver. I didn't find a debug package for it,
so I don't know where exactly. It prints several errors about not being
able!
After removing the wacom sections from my xorg.conf, gdm started
normally and I was able to log in again. So yay, workaround! I've never
had a wacom
Hi Bryce, thanks for taking a look.
The crash still happens with xorg 1:7.4~5ubuntu12. Xorg.0.log shows some
different addresses, but otherwise the startup and backtrace are the
same. Trying to run it in the debugger now.
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs
** Attachment added: "crash file from the original segfault"
http://launchpadlibrarian.net/21993248/_usr_bin_Xorg.0.crash
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "Output of lspci -vvnn"
http://launchpadlibrarian.net/21993105/lspci-vvnn.txt
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
See http://wiki.ubuntu.com/X/Backtracing for directions on how to
collect a full backtrace on X crashes. You can also check to see if a
*.crash file was produced in your /var/crash directory - if so please
just attach it to this bug report.
Also please attach the output of `lspci -vvnn`
** Chang
** Changed in: xorg (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Bryce (bryce)
** Changed in: xorg (Ubuntu)
Assignee: Bryce (bryce) => Bryce Harrington (bryceharrington)
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You recei
** Attachment added: "Xorg.log from the failed start"
http://launchpadlibrarian.net/21963572/Xorg.0.log
--
x11 won't start after upgrade to jaunty
https://bugs.launchpad.net/bugs/325101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
