A quick look at the code showed that the 2.6.28.10 stable tree from
which patches were pulled, contains a broken commit for the bas_gigaset
file. The hunk of code that allocates memory is at a different place
than in the upstream patch. This causes a pointer to be accessed at the
wrong time. I created a patch and some test kernels which can be found
at http://people.canonical.com/~smb/bug417732. Could you try this and
report back whether that fixes your problem? Thanks
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
connecting gigaset USB device causes null pointer error
https://bugs.launchpad.net/bugs/417732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
