I just discovered that the error message in question here appeared when
I changed the name of a not yet well functioning (the mainboard)
ethernet connection, but the message did not appear when I changed the
name of the actually well functioning/defined and in use ethernet
connection (a PCI
This was fixed in the last NM upload, but despite triple-checking I seem
to have made a mistake:
This bug was fixed in the package network-manager - 0.9.1.90-0ubuntu1
---
network-manager (0.9.1.90-0ubuntu1) oneiric; urgency=low
* New upstream release. (LP: #855592)
- core:
Jo-Erlend; please file a separate bug. What you're describing doesn't
sound like the same issue at all, and instead looks like it might be
related to bug 855171. Please see that bug report and use the
workaround/fix in its description; and if this doesn't completely fix
your issue, file a new bug
** Changed in: network-manager (Ubuntu Oneiric)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in
Thanks Mathieu. I had the same issue as pointed by Jo-Erlend. I believe
it resulted because of whats mentioned in bug 855171. Will post back if
its resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Mathieu, I confirm the fix mentioned on bug report 855171 indeed
resolves the issue. Thanks again for pointing in right direction.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
** Tags removed: bugpattern-needed
** Tags added: bugpattern-written
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in
I've had big difficulties with my network after yesterdays updates. The
network icon disappear and I'm not able to connect to any networks. They
also don't appear in ifconfig. I did a clean install from oneiric 64bit
from September 20th and now I'm able to connect, but there are still
problems.
Bumping up the importance on this one based on number of folks affected
and duplicate bugs.
** Changed in: network-manager (Ubuntu Oneiric)
Importance: Medium = High
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, I can certainly acknowledge the issue exists, because I was able
to get one crash; but I can't seem to make it crash again in a debugger.
There's a possible patch but so far it's difficult to verify it
correctly fixes the issue, because it's so hard to reproduce.
--
You received this bug
I came across this error when trying to connect to my dorm's Ethernet,
and then switching to wireless when I couldn't get it to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
I got it while renaming my connection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
To manage notifications about
I got this error when I renamed by ethernet connection from Wired
Connection 1 to Wired Connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV
I got this error when I renamed my ethernet connection from Wired
Connection 1 to Ethernet - Auto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in
I did only rename my Wired Connection 1 (Ethernet) to the german word
Kabelnetzwerk - some seconds after that, Network Manager crashed,
shortly after displaying (OSD) that I am connected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
To manage notifications about this
And i was doing nothing and got exactly the same crash report.
NM was NOT really crashing though...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV
I was able to segfault in the same function by simple renaming my
ethernet connection from Wired connection 1 to Local Area Network.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
** Also affects: network-manager (Ubuntu Oneiric)
Importance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: Confirmed
** Changed in: network-manager (Ubuntu Oneiric)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
To manage notifications about this bug
I just had this problem while changing IPV4 to Shared to other computers
on the latest daily build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in
We got plenty of duplicates already, and the last duplicate is against
0.8.9997+git.20110721t045648.36db194-0ubuntu1 which seems to indicate
there's still an issue in the latest upload of NM... perhaps this is
actually a bug in nm-applet though.
Assigning to myself, this should get fixed asap.
22 matches
Mail list logo
