Boxee

D-Link Boxee Remote Crashes Boxee on Linux

Details

  • Labels:
  • Boxee Build Number:
    0.9.22.13692
  • Operating System:
    Ubuntu Maverick
  • Number of attachments:
    3
  • Description:
    Hide
    I just bought the D-Link boxee remote (http://www.amazon.com/gp/product/B00480OSVK/) to use with my Ubuntu 10.10 boxee box. I plugged it in and it worked great in mythtv. But, when I launch boxee and press any button on the remote, boxee segfaults and takes X.org down with it (I am left at the ubuntu login screen). I can reproduce this on several different machines running Ubuntu.

    /var/log/messages shows the following after the segfault:

    Dec 1 20:01:52 desktop kernel: [369619.632822] Boxee[14785]: segfault at 4d0 ip 00dff516 sp bff35280 error 4 in libX11.so.6.3.0[dc8000+119000]

    It is really pretty strange because the remote should work just like any old keyboard and indeed does work fine in mythtv. My keyboard and another IRC based remote work fine as well.

    I'm attaching my boxee log as well, but nothing was written to the log after the crash.
    Show
    I just bought the D-Link boxee remote (http://www.amazon.com/gp/product/B00480OSVK/) to use with my Ubuntu 10.10 boxee box. I plugged it in and it worked great in mythtv. But, when I launch boxee and press any button on the remote, boxee segfaults and takes X.org down with it (I am left at the ubuntu login screen). I can reproduce this on several different machines running Ubuntu. /var/log/messages shows the following after the segfault: Dec 1 20:01:52 desktop kernel: [369619.632822] Boxee[14785]: segfault at 4d0 ip 00dff516 sp bff35280 error 4 in libX11.so.6.3.0[dc8000+119000] It is really pretty strange because the remote should work just like any old keyboard and indeed does work fine in mythtv. My keyboard and another IRC based remote work fine as well. I'm attaching my boxee log as well, but nothing was written to the log after the crash.
  1. jdeslip-boxee.log
    (356 kB)
    Jack Deslippe
    01/Dec/10 11:29 PM
  2. startx-output
    (2 kB)
    Jack Deslippe
    02/Dec/10 11:40 AM
  3. Xorg.0.log
    (24 kB)
    Jack Deslippe
    02/Dec/10 11:40 AM

Activity

Hide
rafael added a comment - 02/Dec/10 4:41 AM
jack, I could not reproduce this crash using Boxee remote and Boxee 0.9.22.13692 on Ubuntu Maverick 64

please try running Boxee using gdb

gdb /opt/boxee/Boxee
run

and when it crashes, write:

thread apply all bt

it will printout a full dump of your threads. add the info to the issue.
Show
rafael added a comment - 02/Dec/10 4:41 AM jack, I could not reproduce this crash using Boxee remote and Boxee 0.9.22.13692 on Ubuntu Maverick 64 please try running Boxee using gdb gdb /opt/boxee/Boxee run and when it crashes, write: thread apply all bt it will printout a full dump of your threads. add the info to the issue.
Hide
Tom Sella added a comment - 02/Dec/10 6:51 AM
From AVNet/Phillips -

The Boxee application shuts down by itself when the last byte of the packet is 0xFF which means battery full.
There is no issue when the last byte is 0 , which means battery low.

Show
Tom Sella added a comment - 02/Dec/10 6:51 AM From AVNet/Phillips - The Boxee application shuts down by itself when the last byte of the packet is 0xFF which means battery full. There is no issue when the last byte is 0 , which means battery low.
Hide
Jack Deslippe added a comment - 02/Dec/10 9:53 AM
@rafael - unfortunately when Boxee segfaults it kills my GNOME/X session. So that after the crash I am brought back to the ubuntu login screen. So, I lose my gdb session.

BTW, I am running 32bit Ubuntu. I don't know if that helps.
Show
Jack Deslippe added a comment - 02/Dec/10 9:53 AM @rafael - unfortunately when Boxee segfaults it kills my GNOME/X session. So that after the crash I am brought back to the ubuntu login screen. So, I lose my gdb session. BTW, I am running 32bit Ubuntu. I don't know if that helps.
Hide
Jack Deslippe added a comment - 02/Dec/10 11:16 AM - edited
So, I tried a bunch more things to see if I could find a fix - unfortunately nothing fixes it. Let me give you all the info I have to help you reproduce this.

- I have reproduced this crash on 3 different machines. All of them have Ubuntu 10.10-32-bit with up to date packages. I have not tried it on 64 bit or older Ubuntu. All of my machines have boxee from boxee-0.9.22.13692.i486.modfied.deb.
- All of them have nvidia video cards. I have tried turning off compiz (desktop effects), disabling the composite extension in xorg.conf and even removing the nvidia driver all together. The crash still happens with the generic nouveau driver (so it does not appear to be related to nvidia driver).
- The crash happens after I press single button on the d-link remote once Boxee has started. The remote works fine in other applications (mythtv and scrolling up and down in Chrome for example).
- The message I posted above from /var/log/messages above is the only line written in any log that I can tell of after the crash.
- I tried deleting my .boxee folder. That also had no affect on this crash.

Finally, in case this is useful to you, when I first put in the dlink usb receiver, the following is appended to dmesg:

[ 590.162690] usb 5-1: new full speed USB device using uhci_hcd and address 3
[ 590.336355] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input17
[ 590.336732] generic-usb 0003:0471:20D9.0007: input,hidraw0: USB HID v1.11 Keyboard [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input0
[ 590.343470] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input18
[ 590.343806] generic-usb 0003:0471:20D9.0008: input,hidraw1: USB HID v1.11 Mouse [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input1
[ 590.352836] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.2/input/input19
[ 590.353658] generic-usb 0003:0471:20D9.0009: input,hiddev96,hidraw2: USB HID v1.11 Device [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input2
[ 590.364012] generic-usb 0003:0471:20D9.000A: hiddev97,hidraw3: USB HID v1.11 Device [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input3
Show
Jack Deslippe added a comment - 02/Dec/10 11:16 AM - edited So, I tried a bunch more things to see if I could find a fix - unfortunately nothing fixes it. Let me give you all the info I have to help you reproduce this. - I have reproduced this crash on 3 different machines. All of them have Ubuntu 10.10-32-bit with up to date packages. I have not tried it on 64 bit or older Ubuntu. All of my machines have boxee from boxee-0.9.22.13692.i486.modfied.deb. - All of them have nvidia video cards. I have tried turning off compiz (desktop effects), disabling the composite extension in xorg.conf and even removing the nvidia driver all together. The crash still happens with the generic nouveau driver (so it does not appear to be related to nvidia driver). - The crash happens after I press single button on the d-link remote once Boxee has started. The remote works fine in other applications (mythtv and scrolling up and down in Chrome for example). - The message I posted above from /var/log/messages above is the only line written in any log that I can tell of after the crash. - I tried deleting my .boxee folder. That also had no affect on this crash. Finally, in case this is useful to you, when I first put in the dlink usb receiver, the following is appended to dmesg: [ 590.162690] usb 5-1: new full speed USB device using uhci_hcd and address 3 [ 590.336355] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input17 [ 590.336732] generic-usb 0003:0471:20D9.0007: input,hidraw0: USB HID v1.11 Keyboard [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input0 [ 590.343470] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input18 [ 590.343806] generic-usb 0003:0471:20D9.0008: input,hidraw1: USB HID v1.11 Mouse [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input1 [ 590.352836] input: NOO_SI002v0.6 DLINK USB HID Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.2/input/input19 [ 590.353658] generic-usb 0003:0471:20D9.0009: input,hiddev96,hidraw2: USB HID v1.11 Device [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input2 [ 590.364012] generic-usb 0003:0471:20D9.000A: hiddev97,hidraw3: USB HID v1.11 Device [NOO_SI002v0.6 DLINK USB HID Receiver] on usb-0000:00:1d.0-1/input3
Hide
Jack Deslippe added a comment - 02/Dec/10 11:40 AM - edited
I booted Ubuntu into init 3 (no X) and then manually ran "startx" - I dumped the output of startx to the file startx-log and the Xorg.0.log from the startx session in which I start X, launch boxee, press a button on the remote and watch Boxee/X segfault.

The backtrace of the segfault is written in both those files which I just attached.
Show
Jack Deslippe added a comment - 02/Dec/10 11:40 AM - edited I booted Ubuntu into init 3 (no X) and then manually ran "startx" - I dumped the output of startx to the file startx-log and the Xorg.0.log from the startx session in which I start X, launch boxee, press a button on the remote and watch Boxee/X segfault. The backtrace of the segfault is written in both those files which I just attached.
Hide
Jack Deslippe added a comment - 02/Dec/10 12:03 PM - edited
Even more info: when I turn on "windowed" mode in Boxee the segfault with the d-link remote goes away. But, as soon as I turn back on the fullscreen (res of my monitor/tv) mode the boxee remote again causes segfault that kills Boxee and X. However, in other programs (e.g. MythTv, Totem, VLC and Banshee) the remote still works fine in fullscreen.
Show
Jack Deslippe added a comment - 02/Dec/10 12:03 PM - edited Even more info: when I turn on "windowed" mode in Boxee the segfault with the d-link remote goes away. But, as soon as I turn back on the fullscreen (res of my monitor/tv) mode the boxee remote again causes segfault that kills Boxee and X. However, in other programs (e.g. MythTv, Totem, VLC and Banshee) the remote still works fine in fullscreen.
Hide
Daniel Becker added a comment - 11/Dec/10 3:23 PM
For what it's worth, the same problem exists in XBMC (SVN:35567, Ubuntu 10.10 on x86_64) as well:

[ 209.426735] xbmc.bin[2701]: segfault at 968 ip 00007f14cecab0bc sp 00007fff1fdc4b50 error 4 in libX11.so.6.3.0[7f14cec6b000+131000]
Show
Daniel Becker added a comment - 11/Dec/10 3:23 PM For what it's worth, the same problem exists in XBMC (SVN:35567, Ubuntu 10.10 on x86_64) as well: [ 209.426735] xbmc.bin[2701]: segfault at 968 ip 00007f14cecab0bc sp 00007fff1fdc4b50 error 4 in libX11.so.6.3.0[7f14cec6b000+131000]
Hide
Daniel Becker added a comment - 12/Dec/10 5:50 PM
Link to relevant bug ticket for XBMC:

http://trac.xbmc.org/ticket/10887
Show
Daniel Becker added a comment - 12/Dec/10 5:50 PM Link to relevant bug ticket for XBMC: http://trac.xbmc.org/ticket/10887
Hide
Daniel Becker added a comment - 08/Jan/11 3:33 PM
Looks like the fix for this will be in Ubuntu Natty:

http://permalink.gmane.org/gmane.linux.debian.devel.x/94624
Show
Daniel Becker added a comment - 08/Jan/11 3:33 PM Looks like the fix for this will be in Ubuntu Natty: http://permalink.gmane.org/gmane.linux.debian.devel.x/94624
Hide
Daniel Becker added a comment - 08/Jan/11 4:57 PM
Actually, looks like the commit i linked to above fixes some other issue, as I still get the exact same crash.
Show
Daniel Becker added a comment - 08/Jan/11 4:57 PM Actually, looks like the commit i linked to above fixes some other issue, as I still get the exact same crash.
Hide
Daniel Becker added a comment - 09/Jan/11 7:15 PM
Possibly related launchpad ticket:

https://bugs.launchpad.net/xorg-server/+bug/597895
Show
Daniel Becker added a comment - 09/Jan/11 7:15 PM Possibly related launchpad ticket: https://bugs.launchpad.net/xorg-server/+bug/597895

People

Dates

  • Created:
    01/Dec/10 11:29 PM
    Updated:
    12/Apr/11 9:06 AM