-r3 has been ported to GTK+-2.0, so in order to punt the old GTK+-1.2 version this needs to go stable. You need usbdevfs or lately, usbfs mounted to use it -- "mount -t usbfs usbfs /proc/bus/usb".
sparc stable.
app-admin/usbview-1.0-r3 Emerges OK, no collisions. Runs OK if valid usbdevfs devices file (/proc/bus/usb/devices) is specified. Otherwise, depending on the file, segfaults. running usbview and setting devices file as /etc/DIR_COLORS d'oh! ** (usbview:2859): WARNING **: No interface to put an endpoint at for this device. Segmentation fault
Created attachment 127997 [details] The backtrace
(In reply to comment #2) > app-admin/usbview-1.0-r3 > > Emerges OK, no collisions. > Runs OK if valid usbdevfs devices file (/proc/bus/usb/devices) is specified. > Otherwise, depending on the file, segfaults. Does it happen also with current stable? Or is the breakage caused by Debian provided GTK+-2.0 patch (which is pulled from upstream BitKeeper) which is the change between these versions. It seems like a minor issue and shouldn't, IMO, be stopping it getting stable. The old version needs to die. Greg, could you please release new version of usbview from your bitkeeper and take a look at this backtrace? Thanks.
Current stable aborts with similar issue.. ** WARNING **: No interface to put an endpoint at for this device. *** glibc detected *** usbview: corrupted double-linked list: 0x00000000006222f0 *** ======= Backtrace: ========= /lib/libc.so.6[0x2b3b72be6b1d] /lib/libc.so.6[0x2b3b72be7cfd] /lib/libc.so.6(__libc_free+0x76)[0x2b3b72be8146] usbview(LoadUSBTree+0x245)[0x403d5b] /usr/lib/libgtk-1.2.so.0[0x2b3b7212fa05] /usr/lib/libgtk-1.2.so.0[0x2b3b721309d8] /usr/lib/libgtk-1.2.so.0(gtk_signal_emit+0x1c2)[0x2b3b72130cbc] /usr/lib/libgtk-1.2.so.0[0x2b3b720adb20] /usr/lib/libgtk-1.2.so.0[0x2b3b721308e0] /usr/lib/libgtk-1.2.so.0(gtk_signal_emit+0x1c2)[0x2b3b72130cbc] /usr/lib/libgtk-1.2.so.0[0x2b3b720adf5d] /usr/lib/libgtk-1.2.so.0(gtk_marshal_BOOL__POINTER+0xe)[0x2b3b72106963] /usr/lib/libgtk-1.2.so.0[0x2b3b72130a05] /usr/lib/libgtk-1.2.so.0(gtk_signal_emit+0x1c2)[0x2b3b72130cbc] /usr/lib/libgtk-1.2.so.0(gtk_widget_event+0x2c8)[0x2b3b72160043] /usr/lib/libgtk-1.2.so.0(gtk_propagate_event+0x1ea)[0x2b3b721054e5] /usr/lib/libgtk-1.2.so.0(gtk_main_do_event+0x2d6)[0x2b3b72105f2a] /usr/lib/libgdk-1.2.so.0[0x2b3b722d6a59] /usr/lib/libglib-1.2.so.0[0x2b3b725097d2] /usr/lib/libglib-1.2.so.0[0x2b3b72509f8c] /usr/lib/libglib-1.2.so.0(g_main_run+0x8a)[0x2b3b7250a069] /usr/lib/libgtk-1.2.so.0(gtk_main+0xad)[0x2b3b721062ad] usbview(main+0x3f)[0x402ec7] /lib/libc.so.6(__libc_start_main+0xf4)[0x2b3b72b99374] usbview[0x402df9] ======= Memory map: ======== 00400000-00479000 r-xp 00000000 03:02 59288956 /usr/bin/usbview 00578000-00599000 rw-p 00078000 03:02 59288956 /usr/bin/usbview 00599000-00641000 rw-p 00599000 00:00 0 [heap] 2b3b71f48000-2b3b71f63000 r-xp 00000000 03:02 1026108 /lib64/ld-2.5.so 2b3b71f63000-2b3b71f67000 rw-p 2b3b71f63000 00:00 0 2b3b71f8e000-2b3b71f8f000 rw-p 2b3b71f8e000 00:00 0 2b3b72063000-2b3b72064000 r--p 0001b000 03:02 1026108 /lib64/ld-2.5.so 2b3b72064000-2b3b72065000 rw-p 0001c000 03:02 1026108 /lib64/ld-2.5.so 2b3b72065000-2b3b721ae000 r-xp 00000000 03:02 50916271 /usr/lib64/libgtk-1.2.so.0.9.1 2b3b721ae000-2b3b722ad000 ---p 00149000 03:02 50916271 /usr/lib64/libgtk-1.2.so.0.9.1 2b3b722ad000-2b3b722bd000 rw-p 00148000 03:02 50916271 /usr/lib64/libgtk-1.2.so.0.9.1 2b3b722bd000-2b3b722be000 rw-p 2b3b722bd000 00:00 0 2b3b722be000-2b3b722f4000 r-xp 00000000 03:02 50916222 /usr/lib64/libgdk-1.2.so.0.9.1 2b3b722f4000-2b3b723f4000 ---p 00036000 03:02 50916222 /usr/lib64/libgdk-1.2.so.0.9.1 2b3b723f4000-2b3b723f6000 rw-p 00036000 03:02 50916222 /usr/lib64/libgdk-1.2.so.0.9.1 2b3b723f6000-2b3b723f8000 r-xp 00000000 03:02 51092459 /usr/lib64/libgmodule-1.2.so.0.0.10 2b3b723f8000-2b3b724f7000 ---p 00002000 03:02 51092459 /usr/lib64/libgmodule-1.2.so.0.0.10 2b3b724f7000-2b3b724f8000 rw-p 00001000 03:02 51092459 /usr/lib64/libgmodule-1.2.so.0.0.10 2b3b724f8000-2b3b724f9000 rw-p 2b3b724f8000 00:00 0 2b3b724f9000-2b3b7251d000 r-xp 00000000 03:02 51753801 /usr/lib64/libglib-1.2.so.0.0.10 2b3b7251d000-2b3b7261c000 ---p 00024000 03:02 51753801 /usr/lib64/libglib-1.2.so.0.0.10 2b3b7261c000-2b3b7261e000 rw-p 00023000 03:02 51753801 /usr/lib64/libglib-1.2.so.0.0.10 2b3b7261e000-2b3b72625000 r-xp 00000000 03:02 50442234 /usr/lib64/libXi.so.6.0.0 2b3b72625000-2b3b72725000 ---p 00007000 03:02 50442234 /usr/lib64/libXi.so.6.0.0 2b3b72725000-2b3b72726000 rw-p 00007000 03:02 50442234 /usr/lib64/libXi.so.6.0.0 2b3b72726000-2b3b72734000 r-xp 00000000 03:02 50758038 /usr/lib64/libXext.so.6.4.0 2b3b72734000-2b3b72834000 ---p 0000e000 03:02 50758038 /usr/lib64/libXext.so.6.4.0 2b3b72834000-2b3b72835000 rw-p 0000e000 03:02 50758038 /usr/lib64/libXext.so.6.4.0 2b3b72835000-2Aborted
(In reply to comment #5) > Current stable aborts with similar issue.. Not a regression to current stable then, please proceed..
ppc64 stable
Wow, gtk1->gtk2 move in an ebuild revision. That's a quite big one. Weren't revisions supposed to be limited to ebuild changes and bugfix patches? I think you should wait for upstream release of gtk2 version, but that's just me.
(In reply to comment #8) > Wow, gtk1->gtk2 move in an ebuild revision. That's a quite big one. Weren't > revisions supposed to be limited to ebuild changes and bugfix patches? I could have pulled _pre2007.. from upstream BitKeeper, but seriously, I'm not touching BitKeeper. Someone else from Debian did the dirty job allready, plus I got a nice manpage from them. So, a revision bump instead of _pre but nevertheless, upstream code.
stable on ppc
amd64 stable
Stable on x86
alpha stable, closing, thanks Tobias
