** Changed in: libusb
Status: New => Won't Fix
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
This bug was fixed in the package libusb - 2:0.1.12-14ubuntu0.2
---
libusb (2:0.1.12-14ubuntu0.2) lucid-proposed; urgency=low
* 07_altsetting_alloc.patch: Update patch to only clear the current
altsetting record in the loop, not overwrite previously written ones.
Thanks to P
** Tags added: verification-done
** Tags removed: verification-needed
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Ops! Forget my previous comment #43 ... I installed PROPOSED libusb-0.1-4 and
it runs well: IT WORKS FOR ME.
Ciao
Thanks.
CM
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, w
I should be wrong: up to date I'm not able to download the proposed
package. Please, see here below ... what should I change to download and
test the new patched package?
~$ tail -1 /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ lucid-proposed restricted main multiverse
universe
~$
Accepted libusb into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: libusb (Ubuntu Lucid)
As for realloc(). It indeed does not guarantee that it will point out to the
old chunk of memory. However it does guarantee that it will copy the relevant
part of the memory. Reading man realloc:
The contents will be unchanged to the minimum of the old and new sizes;
So that should be just enoug
This bug was fixed in the package libusb - 2:0.1.12-15ubuntu2
---
libusb (2:0.1.12-15ubuntu2) maverick; urgency=low
* 07_altsetting_alloc.patch: Update patch to only clear the current
altsetting record in the loop, not overwrite previously written ones.
Thanks to Pawel Kot!
Updated libusb uploaded to lucid-proposed, awaiting SRU team review.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Indeed the previous patch would overwrite previous altsettings, sorry
that I didn't spot this. When I reviewed this original SRU, I just
looked at the realloc()/memset() sequence, which seems fine at the first
sight. realloc() by no way guarantees you that the reallocated pointer
is still the same
Reopening, since this caused regressions and needs a different patch.
** Changed in: libusb (Ubuntu Maverick)
Status: Fix Released => In Progress
** Changed in: libusb (Ubuntu Lucid)
Status: Fix Released => In Progress
--
usb_find_devices() crashed with SIGSEGV in free()
https://b
The patch in comment #33 that only zeroes the last altsetting works for
me.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
This is the output of lsusb -vvv -d 0421: when gnokii is not working.
** Attachment added: "lsusb 2:0.1.12-14ubuntu0.1 (not working)"
http://launchpadlibrarian.net/51647321/lsusb.2%3A0.1.12-14ubuntu0.1.txt
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/42
With libusb - 2:0.1.12-14ubuntu0.1 and the corresponding -dev package
gnokii doesn't find the FBUS endpoint.
I'm attaching the output of lsusb -vvv for a Nokia phone for 2:0.1.12-14
(working) and for 2:0.1.12-14ubuntu0.1 (not working).
** Attachment added: "lsusb 2:0.1.12-14 (working)"
http:/
The patch applied is actually very wrong. And it breaks for example gnokii.
If you look at the code you find this:
interface->altsetting = realloc(interface->altsetting, sizeof(struct
usb_interface_descriptor) * (interface->num_altsetting + 1));
Which means that the structure is reallocated to ad
Sorry to bother You ... from bug #595650 ...
I noticed that update manager propose libusb 0.1.12-14ubuntu0.1 as
"recommended update" (sorry for my English ... I'm translating from
Italian), but I have experienced that this libusb upgrade is faulty, at
least for HP printers. Therefore I suppose it
The above-mentioned problem was also reported to Ubuntu as bug #595650.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
This update seems to be causing some problems for people using HPLIP and
HP Laserjet printers. After installing libusb-0.1-4 version
2:0.1.12-14ubuntu0.1 yesterday, I could no longer print on my HP
Laserjet 3030 printer and hp-toolbox would report a "Device
communication error 5012". Some googlin
This bug was fixed in the package libusb - 2:0.1.12-14ubuntu0.1
---
libusb (2:0.1.12-14ubuntu0.1) lucid-proposed; urgency=low
* Add 07_altsetting_alloc.patch: Fix crash due to uninitialized memory.
Thanks to Eric Miao for debugging this and the patch! (LP: #427805)
-- Martin Pi
** Tags added: verification-done
** Tags removed: verification-needed
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Thanks Martin, I can confirm this seems to fix the problem for me.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Accepted libusb into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: libusb (Ubuntu Lucid)
** Branch linked: lp:ubuntu/libusb
** Branch linked: lp:ubuntu/lucid-proposed/libusb
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
This bug was fixed in the package libusb - 2:0.1.12-15ubuntu1
---
libusb (2:0.1.12-15ubuntu1) maverick; urgency=low
* Add 07_altsetting_alloc.patch: Fix crash due to uninitialized memory.
Thanks to Eric Miao for debugging this and the patch! (LP: #427805)
-- Martin PittTue,
** Also affects: libusb (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: libusb (Ubuntu Maverick)
Importance: Medium
Assignee: Eric Miao (eric.y.miao)
Status: In Progress
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bug
Seems to have fixed the issue on my MB 5,1 running Lucid as well.
-Barry Flanagan
On 9 June 2010 22:42, Olivier Grisel wrote:
> @Eric: same for me on a MacBook Pro 5,5 running lucid. I can now suspend
> and resume without having libusb segfault in the process. Thanks!
>
> --
> usb_find_devices
@Eric: same for me on a MacBook Pro 5,5 running lucid. I can now suspend
and resume without having libusb segfault in the process. Thanks!
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubu
@Eric: your package worked for me, on a Macbook Pro 5,5 (amd64). I had
the bug, installed it then suspended and it worked (didn't work before).
I think it would be good to get this patch to the official repos.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/42
@Märt, yeah that's something nasty. I tried plug and un-plug my power
several times but didn't managed to get this reproduced. But once it
happens, it seems to last forever. So a possible way to verify is to use
the original libusb package first, and til this issue happens, install
the updated one,
I now installed Your new version. Since the bug does not appear every
time, I cannot report immediately that it works. I will test for a week
and let You know if the bug has reappeared or not.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received
@Märt, finally built with my PPA and uploaded both amd64 and i386
version of the package to http://people.canonical.com/~ycmiao/lp427805.
Please check and report.
@Alex, yeah the patch looks OK. I'll see if we can get this into lucid-
update. Thanks.
--
usb_find_devices() crashed with SIGSEGV in
Also I've attached a patch which I found on the redhat bugzilla (can't
seem to find the original bug report atm) which also addresses a
possible logic error in libusb - Eric can you review and perhaps
incorporate with the existing patch you've just posted?
Cheers?field.comment=Also I've attached a
Thanks Eric, I agree this definitely looks like the potential culprit
for this crash. Am just rebuilding libusb now with your patch so I can
test it and will report back with results. Thanks again for your effort
in debugging this.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs
Try remove config.guess and config.sub before issueing an 'debian/rules
binary', ugly but should work.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Can you build a package for i386?
I tried to do it myself, but "debian/rules binary" fails with errors.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This happens intermittently on my Macbook Pro 5.5, so I debugged into
this for a while. And found there is an incorrect free due to the memory
not being zero-ed during allocation. The attached patch tries to fix
this issue (at least it worked on my side). And I've yet built the
libusb packages at:
So there is absolutely no chance that libusb-0.1 will be fixed or
replaced with libusb-compat which also means that there is absolutely no
support for years now for libusb-0.1 neither from native developers nor
canonical?
By the way this bug is only the top of the iceberg caused by deprecated
libu
@Alex : The packaging of the patch is quite ugly because I struggled
with the autoconf files, and I was happy enough when the source package
finally built. If the fix works, I will try to re-package it better,
even if it means a little bit more testing... Also, the debian/control
file seems to have
** Tags added: patch
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
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.ubun
@Philippe - thanks for that, will test later tonight when I get the
chance - in the meantime I notice your debdiff says this fixes this bug
- unfortunately this bug is against libusb-0.1 which isn't fixed, it
just works around upower triggering this bug. Regardless, thanks again
for generating the
Wow, that was quick. The updated packages are available from ppa
:philippe-gauthier/ppa
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I attached a debdiff that brings the latest fix from Richard Hughes to
the current upower package in Lucid. If you want to test it, you may
apply it or wait until the updated package is built and available in my
PPA.
** Patch added: "Debdiff for using libusb-1.0"
http://launchpadlibrarian.net/4
The ones I manually marked as duplicates all have the same stack-trace
which is pretty much a dead give-away. Unfortunately there seems no good
way to reproduce it - Fedora also have the exact same issue -
https://bugzilla.redhat.com/show_bug.cgi?id=580570 - which is apparently
being looked at by t
There seems to be a bunch of duplicates floating around Launchpad. Can
someone give me a way to reproduce this bug so we can make sure the
other bugs are really duplicates of this one? Thanks in advance!
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
Y
Could someone instuct how to replave libusb-compat with libusb-0.1
Should I just built the libusb-compat package and name it to libusb-0.1 or
should they both be installed?
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notificat
Might be worth replacing libusb-0.1 with libusb-compat since anecdotal
evidence
(https://bugs.launchpad.net/ubuntu/+source/upower/+bug/526895/comments/8)
would appear to suggest it fixes this issue.
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You re
Could it be duplicate to this?:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/551940
Anyway, libusb-0.1 is not supported for a long time now so there is no
chance to get a patch from there.
According to libusb developers libusb-compat-0.1 (version 1.0.3)
provides backwards compatibilit
** Changed in: libusb
Status: Unknown => New
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Bug watch added: www.libusb.org/ #11
http://www.libusb.org/ticket/11
** Also affects: libusb via
http://www.libusb.org/ticket/11
Importance: Unknown
Status: Unknown
--
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bu
49 matches
Mail list logo
