The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: modemmanager (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: modemmanager (Ubuntu Quantal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Branch linked: lp:~modemmanager/modemmanager/ubuntu.raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_remove()
To manage notifica
** Branch linked: lp:ubuntu/modemmanager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_remove()
To manage notifications about this bug
This bug was fixed in the package modemmanager - 0.6.0.0.really-0ubuntu4
---
modemmanager (0.6.0.0.really-0ubuntu4) raring; urgency=low
* debian/patches/git_cdma_double_free_05a4226.patch: cdma: avoid double free
of GError (LP: #1083659)
* debian/patches/git_ignore_arduino_aa8
Great, we'll just backport the same patch to precise if possible.
Targetting for SRU for Quantal/Precise.
** Also affects: modemmanager (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: modemmanager (Ubuntu Quantal)
Importance: Undecided
Status: New
** Chan
The commit can avoid valgrind errors in precise as well.
** Attachment added:
"precise_valgrind_with_05a42261795f27c4ecd0cd6503114322c8b8.out"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3458921/+files/precise_valgrind_with_05a42261795f27c4ecd0cd650
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_remove()
To manage notifications about this bug go to:
https://bug
The commit in MM_0.6 can avoid valgrind errors in quantal.
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=MM_06&id=05a42261795f27c4ecd0cd6503114322c8b8
** Attachment added:
"quantal_valgrind_with_05a42261795f27c4ecd0cd6503114322c8b8.out"
https://bugs.launchpad.net/ubu
** Tags added: precise
** Changed in: modemmanager (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in
** Attachment added: "quantal_valgrind.out"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3457977/+files/quantal_valgrind.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
reproducible on quantal as well.
** Attachment added: "quantal_usr_sbin_modem-manager.0.crash"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3457976/+files/quantal_usr_sbin_modem-manager.0.crash
--
You received this bug notification because you are a member
** Attachment added: "precise_valgrind.out"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3457952/+files/precise_valgrind.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "precise_usr_sbin_modem-manager.0.crash"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3457951/+files/precise_usr_sbin_modem-manager.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I can reproduce a crash in precise.
Note: I used a manually patched package for Bug #1071492, because it's not
SRUed yet.
https://launchpadlibrarian.net/125443163/modemmanager_0.5.2.0-0ubuntu2_0.5.2.0-0ubuntu2ppa1.diff.gz
I will attach stacktrace and valgrind log.
--
You received this bug notif
I can confirm the crash is no longer reproducible with daily-build from
upstream 0.6.0.0.really+git201212040418.1200-0~pkg164~raring1.
> Do you know if Ubuntu Quantal and Precise have the same problem?
I'm not sure. I will check that too.
--
You received this bug notification because you are a
** Changed in: modemmanager
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_remove()
To manage notific
Nobuto, please test again when this patch goes into the PPA tomorrow. Do
you know if Ubuntu Quantal and Precise have the same problem?
** Description changed:
modem-manager crashed with SIGSEGV in g_source_remove()
How to reproduce:
1. attach au/huawei DATA07 USB modem.
2. click "Ena
A fix for the memory errors was pushed to MM_06 upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_remove()
To manage notification
** Changed in: modemmanager
Status: Unknown => New
** Changed in: modemmanager
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager cra
Attached valgrind logs were without -dbg packages, sorry.
I have re-uploaded those.
** Attachment removed: "valgrind_with_debug.out"
https://bugs.launchpad.net/modemmanager/+bug/1083659/+attachment/3446965/+files/valgrind_with_debug.out
** Attachment added: "valgrind_with_debug.out"
https
** Attachment removed: "valgrind_without_debug.out"
https://bugs.launchpad.net/modemmanager/+bug/1083659/+attachment/3446966/+files/valgrind_without_debug.out
** Attachment added: "valgrind_without_debug.out"
https://bugs.launchpad.net/modemmanager/+bug/1083659/+attachment/3446981/+files/v
** Bug watch added: GNOME Bug Tracker #689289
https://bugzilla.gnome.org/show_bug.cgi?id=689289
** Changed in: modemmanager
Importance: Undecided => Unknown
** Changed in: modemmanager
Status: New => Unknown
** Changed in: modemmanager
Remote watch: None => GNOME Bug Tracker #68928
** Attachment added: "valgrind_without_debug.out"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3446966/+files/valgrind_without_debug.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
@Aleksander
I will attach valgrind logs.
valgrind_with_debug.out:
G_SLICE=always-malloc valgrind --log-file=valgrind.out
/usr/sbin/modem-manager --debug
valgrind_without_debug.out:
G_SLICE=always-malloc valgrind --log-file=valgrind.out
/usr/sbin/modem-manager
modemmanager:
Inst
Nobuto:
Please run it under valgrind like this:
$> G_SLICE=always-malloc valgrind --log-file=valgrind.out /usr/sbin
/modem-manager --debug
And send us back the valgrind.out log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Since you have verified that the problem is not solved upstream, could
you please report an upstream bug report at:
https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
Mark component=ModemManager.
** Also affects: modemmanager
Importance: Undecided
Status: New
** Changed i
Adding --log-level=DEBUG to modem-manager can avoid segfault and keep
modem-manager running. But still no luck to connect au(KDDI). That might
be a another bug that I should file next later.
** Attachment added: "debug.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+a
** Attachment added: "gdb.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3446669/+files/gdb.log
** Changed in: modemmanager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tried a new daily build 0.6.0.0.really+git201211281825.1195-0~pkg164~raring1.
And I can reproduce a crash with segfault.
** Attachment added: "crash.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3446668/+files/crash.log
--
You received this bug notifi
Probably:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1071492/comments/19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashed with SIGSEGV in g_source_
I faced a problem with PPA version.
==
Nov 28 13:23:16 ubuntu modem-manager[2760]: Couldn't probe for
capabilities, probably not a GSM or CDMA modem
==
It was resolved in Bug #1071492. But PPA version might not have the
patch for my device.
--
You received this bug notificatio
Looks good. I wonder if this problem has been solved in the latest
upstream version. Would you be able to test this PPA, containing the
latest code?:
https://launchpad.net/~network-
manager/+archive/trunk?field.series_filter=raring
** Changed in: modemmanager (Ubuntu)
Status: New => Incomp
Thanks, I have attached the updated .crash file with apport-retrace. It
contains full stacktrace now.
** Attachment added: "_usr_sbin_modem-manager.0.crash"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3445883/+files/_usr_sbin_modem-manager.0.crash
** Change
Ah ok, I think you need to install the package "apport-retrace" to get
the options to investigate the crash locally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Title:
modem-manager crashe
** Attachment added: "nm.log.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3445278/+files/nm.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083659
Ti
** Attachment added: "modem.log.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3445277/+files/modem.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10836
In my environment, apport-cli exits silently.
I will attach debug logs of modem-manager and network-manager for now,
and I will try to get full stacktrace.
=
ubuntu@ubuntu:/var/crash$ sudo apport-cli _usr_sbin_modem-
manager.0.crash
*** Send problem report to the developers?
After the prob
Japp, the crash might have been reported. But the stacktrace in the txt
file is incomplete. Could you please run "apport-cli
name_of_.crash_file" and select to have stacktrace filled out by
installing debug symbols.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "_usr_sbin_modem-manager.0.crash"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3445251/+files/_usr_sbin_modem-manager.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Sorry, I failed to attach a .crash file (it might be due to bug #1071092).
I will manually attach the file.
** Attachment added: "apport_information.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659/+attachment/3445250/+files/apport_information.txt
--
You received thi
Could you please try to get a full stacktrace of the crash, e.g. by
running modemmanager through gdb, or maybe these instructions ensures
it:
https://wiki.ubuntu.com/DebuggingModemmanager
** Changed in: modemmanager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
42 matches
Mail list logo
