Re: [Ubuntu-x-swat] [Bug 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
Confirmed fixed here on my end as well, prior to that I had the package versions locked in synaptic. On Tue, Sep 15, 2009 at 10:42 AM, Eric Casteleijn < eric.castele...@canonical.com> wrote: > Brian: > > No icons, no taskbars, desktop background is there. When I click > somewhere the taskbars seem to appear very briefly and then disappear > again, so I guess something's crashing. Will investigate more, and file > a new bug, if it's not already there. > > -- > [karmic] Xorg (and anything GLX) crashes on startup > https://bugs.launchpad.net/bugs/429003 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “eglibc” package in Ubuntu: Fix Released > Status in “nvidia-graphics-drivers-180” package in Ubuntu: Invalid > Status in eglibc in Ubuntu Karmic: Fix Released > Status in nvidia-graphics-drivers-180 in Ubuntu Karmic: Invalid > > Bug description: > As of after updates at 2009-09-13 ca. 16:00, Xorg and anything using GLX > (eg. glxinfo) crashes on startup. > The only thing that seems to have been changed then is the upgrade of libc6 > to 2.10.1-0ubuntu11. > > Log of crashing Xorg run is attached. The corresponding gdb backtrace is: > $ gdb /usr/bin/Xorg CoreDump > ... > (gdb) bt > #0 0x278da3c0 in ?? () > #1 0x00289d8d in *__GI___backtrace (array=0xbfdab960, size=32) at > ../sysdeps/i386/backtrace.c:121 > #2 0x08133d1b in xorg_backtrace () at ../../os/backtrace.c:39 > #3 0x080c7b95 in xf86SigHandler (signo=11) at > ../../../../hw/xfree86/common/xf86Events.c:387 > #4 > #5 *__GI_strtol_l_internal (nptr=0xbfdac02d "001 GLX", > endptr=0xbfdac028, base=10, group=0, loc=0x0) at strtol_l.c:246 > #6 0x001d6667 in *__GI_strtol (nptr=0xbfdac02d "001 GLX", > endptr=0xbfdac028, base=10) at strtol.c:110 > #7 0x0807355e in RegisterExtensionNames (extEntry=0x8387690) at > ../../dix/registry.c:168 > #8 0x0809e33a in AddExtension (name=0x635ebc "GLX", NumEvents=17, > NumErrors=12, MainProc=0x6135f0, SwappedMainProc=0, CloseDownProc=0x613430, >MinorOpcodeProc=0x809da10 ) at > ../../dix/extension.c:145 > #9 0x006132f5 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so > #10 0x00635ebc in ?? () from /usr/lib/xorg/modules/extensions//libglx.so > #11 0x0011 in ?? () > #12 0x000c in ?? () > #13 0x006135f0 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so > #14 0x00613560 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so > #15 0x00613430 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so > #16 0x0809da10 in ?? () at ../../dix/extension.c:219 > #17 0x080ec7c5 in InitExtensions (argc=4, argv=0xbfdac2d4) at > ../../../../mi/miinitext.c:551 > #18 0x080722b8 in main (argc=4, argv=0xbfdac2d4, envp=0xbfdac2e8) at > ../../dix/main.c:319 > > Glxinfo backtrace looks like this: > $ unset DISPLAY > $ gdb glxinfo > ... > (gdb) run > Starting program: /usr/bin/glxinfo > > Program received signal SIGSEGV, Segmentation fault. > *__GI_strtol_l_internal (nptr=0xb57a "\t26782\n", endptr=0x0, > base=0, group=0, loc=0x0) at strtol_l.c:246 > 246 strtol_l.c: No such file or directory. >in strtol_l.c > (gdb) bt > #0 *__GI_strtol_l_internal (nptr=0xb57a "\t26828\n", endptr=0x0, > base=0, group=0, loc=0x0) at strtol_l.c:246 > #1 0x0045b6b6 in *__GI___strtol_internal (nptr=0xb57a "\t26828\n", > endptr=0x0, base=0, group=0) at strtol.c:99 > #2 0x006bac15 in ?? () from /usr/lib/libGL.so.1 > #3 0xb57a in ?? () > #4 0x in ?? () > > Note that it crashes at a very early stage, not probably even contacting X > server yet (since DISPLAY is unset). > > Packages: > > ii libc6 2.10.1-0ubuntu11 > GNU C Library: Shared libraries > ii libc6-dbg 2.10.1-0ubuntu11 > GNU C Library: detached debugging symbols > ii libc6-dev 2.10.1-0ubuntu11 > GNU C Library: Development Libraries and Hea > ii libc6-i6862.10.1-0ubuntu11 > GNU C Library: Shared libraries [i686 optimi > ii libgl1-mesa-glx > 7.6.0~git20090817.7c422387-0ubuntu3A free implementation of the > OpenGL API -- G > ii mesa-utils > 7.6.0~git20090817.7c422387-0ubuntu3Miscellaneous Mesa GL utilities > ii mesa-utils-dbgsym > 7.6.0~git20090817.7c422387-0ubuntu3debug symbols for package > mesa-utils > ii nvidia-185-kernel-source 185.18.36-0ubuntu2 > NVIDIA binary kernel module source > ii nvidia-185-libvdpau 185.18.36-0ubuntu2 > Video Decode and Presentation API for Unix > ii nvidia-glx-185185.18.36-0ubuntu2 > NVIDIA binary Xorg driver > ii nvidia-settings 180.25-0ubuntu1 > Tool of configuring the NVIDIA graphics driv > ii rss-glx
[Ubuntu-x-swat] [Bug 430537] Re: keyboard/mouse doesn't respond under X
Alright... got my linux working just a moment ago. Not sure if it was one of the few updates (one of which being hal), or if it was upstart not being updated, but I do have full kb/mouse again. Apparently upstart and some init-scripts packages were being kept back. Doing an apt-get -f install upstart fixed it, after that running update again installed the rest. Here's what Xorg gave me: ==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. If anyone else is having these problems I'd suggest making sure as of "right now" all packaged are updated, and that upstart isn't being kept back. I noticed this to be an issue with update apps other than synaptic. Synaptic usually resolves problems and fixes them on it's own. I will provide any other information I can if asked. -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 430537] Re: keyboard/mouse doesn't respond under X
I am currently in the same situation. I ran an update yesterday (Sept. 15th), and then switched to windows to do a few things. This morning when I woke up, I tried to reboot back into linux to find that the minute I got to the login screen, my mouse and keyboard were frozen. I am going to connect my laptop directly to my router and boot it to console with net support. Maybe there's an update for this. Also, I checked my kern and xorg logs, nothing out of the ordinary. I will try checking .xsession-errors next boot. -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 430537] Re: keyboard/mouse doesn't respond under X
Well, at this point, it seems as tho X isn't getting the mouse/keyboard info from udev. I'd love to post some logs, but since I can't seem to get into kde to do so, there is not much I can provide. On a more amusing note, everytime I go from recovery mode to normal boot, fsck throws a fit over time miss-matches, believing it to be "In the future". So everytime I try to fix something or run more diagnostics, I have to sit through a manual fsck. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
@Conn, If this is the case.. grab my custom fdi file from the previous post and follow the instructions, if everything works as it should you should have tap-clicking and vertical scrolling re-enabled, I also left the 2 finger scrolling active in case anyone wanted both but you can easily tweak out the file to change the values to false/0/whatever. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
Conn, I could not find your full Xorg log, you seem to have only posted your grep via "mouse". Could you run the following commands that Andreas had suggested to me previously? grep -c Synaptics /var/log/Xorg.0.log lshal | grep -c input.touchpad If the 2 commands produce a number higher than 1, can you then post the information from the following commands? cat /var/log/Xorg.0.log | grep Synaptics lshal | grep input.touchpad PS: Sorry if we hijacked your bug report, I was under the assumption that you did what I did.. which was assume synaptics would be listed as a "mouse" and therefore be displayed on a grep. Realizing I had no tap- click or scroll, I decided to run a search for it and found this bug report, ran the same command you did, which produced the same results and never even looked at my whole Xorg.0.log file. If you do not have the synaptics driver at all, perhaps myself or some others can help you out. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
If I have time later I may pop in my Jaunty live CD, I am unsure of what changed between then and now as far as default configurations are concerned.. however.. after poking around in /etc/hal/fdi/policy/ as well as /usr/share/hal/fdi/policy/20thirdpolicy (some sites suggest the default file is in "10osvendor"), I managed to come up with a custom FDI file that restored all my synaptics functions back to the way they were. Andreas will probably slap me for this, as I probably should have checked these earlier, and did not. However, the fdi system is fairly new to some people (myself included), so I am going to attach my custom file in the hopes it will help someone else out and prevent them from also being slapped. As I stated though, it is unclear to me whether this change was intended or not. In the case where it was accidental, I suppose it'd still be considered a bug. If it was intended, I am certain this bug report will eventually be closed. At any rate, the attached file is my fdi policy. The quick instructions are; Download to .. wherever. sudo cp 99-x11-synaptics.fdi /etc/hal/fdi/policy/ reboot I added some comments in the file as to what things are, most are fairly self explanatory. Any questions about it can be emailed to me directly through my profile and I can try to help you out. ** Attachment added: "My Custom synaptics FDI profile" http://launchpadlibrarian.net/27621327/99-x11-synaptics.fdi -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
There is no reason to be rude here. I was not vague at all, i merely made the assumption that you read the file you suggested other people read in regards to re-enabling tap-clicking, which I stated did not work for me. No, I was not aware that it defaults to mac touchpad behavior, but considering I am not using a mac touch pad, I am rather displeased that it's behavior is being forced on me by default. Yes, I am aware that there is no way to detect a "painted scrollbar" on my touchpad, however, all laptops I've owned have had this painted scrollbar, and up until now that area on the touchpad has worked as a scroller. Granted, mentioning it was not very useful in any respect, but it was first thing in the morning and I decided to mention it, though I did so in parenthesis to suggest it was a personal note. Considering no "official" has stepped in to decide whether or not this is a bug, or just new behavior we are supposed to accept as the new standard, I am going to continue treating it like a bug. If there is a way to restore behavior, perhaps you could have mentioned it rather that berate me after I pasted the corresponding information you asked me for? I would think that more people are eventually going to notice this behavior and wish to restore it, so sharing that information would be a nice thing to do, especially for those of us, myself included, who weren't aware that the behavior was completely "changed". -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
$ grep -c Synaptics /var/log/Xorg.0.log
15
$ lshal | grep -c input.touchpad
1
This is rather odd.. it seems to actually find my touchpad (which is
good in some respects)..
$ cat /var/log/Xorg.0.log | grep Synaptics
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) Synaptics touchpad driver version 1.1.0
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type:
TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) filter chain progression: 2.00
(**) SynPS/2 Synaptics TouchPad: (accel) filter stage 0: 20.00 ms
(**) SynPS/2 Synaptics TouchPad: (accel) set acceleration profile 0
(--) SynPS/2 Synaptics TouchPad: touchpad found
$ lshal | grep input.touchpad
info.capabilities = {'input', 'input.touchpad'} (string list)
$ sudo tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.
... however, as I stated previously.. using those options found in the
news file didn't allow touch clicking, and my scroll is broken too
(there's a designated area on the right of the touchpad for it). It
seems to me, that while it is detecting it, it's not applying the proper
driver for it. Strange thing is, I've never had this issue in any
previous distro of Kubuntu.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
To: Andreas Henriksson Unfortunately in my case (and probably others), the synaptics driver doesn't actually seem to be loading. Typing the options listed in that news file doesn't seem to effect the mouse at all. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
Can confirm same issue on the HP Pavilion dv9610us. No tap-click, no scroll: ~$ cat /var/log/Xorg.0.log | grep -i mouse (==) NVIDIA(0): Silken mouse enabled (II) config/hal: Adding input device Macintosh mouse button emulation (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: "/dev/input/event4" (II) Macintosh mouse button emulation: Found 3 mouse buttons (II) Macintosh mouse button emulation: Found x and y relative axes (II) Macintosh mouse button emulation: Configuring as mouse (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE) (**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1 (**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00 (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms (**) Macintosh mouse button emulation: (accel) set acceleration profile 0 -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
