** Changed in: gst
Importance: Unknown => Critical
--
[network-admin] Crash when starting from menu.
https://bugs.launchpad.net/bugs/67936
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@li
Ok, I have made the work around work...lol
and my wifi is dhcp, all i needed to get it working was the wep key.
--
[network-admin] Crash when starting from menu.
https://bugs.launchpad.net/bugs/67936
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a b
Could you try that debdiff? That's the changes from upstream quickly
applied without the connection.c modifications which don't apply
** Attachment added: "change from upstream applied to the edgy version"
http://librarian.launchpad.net/6680008/gst.debdiff
--
[network-admin] Crash when starti
If you have questions on how to do changes the MOTU team is the right
place, the team has already load to do and using comments for questions
doesn't work nicely
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Okay, I got the specified revision. I compared it to the result of
`apt-get source gnome-system-tool` and have applied only the
"relevant?" changes. But, I'm not sure what to do with it now. I
don't know whether to run the configure script, or use the Makefile
that was in the src, or whether to
You can start with the MOTU team: https://wiki.ubuntu.com/MOTU. The
change that fixed the bug upstream: http://svn.gnome.org/viewcvs/gnome-
system-tools?view=rev&revision=3765, testing that change on the edgy
package and confirming it fixes the bug would be useful
--
[network-admin] Crash when st
On 3/7/07, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
> The feisty package is not easy to use on edgy, the patch can be used to
> fix the edgy package though, if somebody want to look at what upstream
> change fixed that exactly and if it works on edgy we might consider a
> stable update
>
> --
>
The feisty package is not easy to use on edgy, the patch can be used to
fix the edgy package though, if somebody want to look at what upstream
change fixed that exactly and if it works on edgy we might consider a
stable update
--
[network-admin] Crash when starting from menu.
https://launchpad.ne
I have found that given enough reboots I can always get my system on my
home (wifi) or work (ethernet with lots of search domains and hosts
entries) networks. I simply have to (usually when I get home from work)
delete all the custom entries from /etc/hosts and reboot. Then network-
admin will la
I have the same problem too, on Ubuntu 6.10, kernel 2.6.17-11.
Today I tried to change th entwork config through system->admin->networking and
puff no way to enter in!
I think that it's not feasible to change everytime it using the sys console...
Unfortunatley I can't solve my bug since the gnome-
I'm sorry to post this here, but this issue is threatening my use of
Linux as a desktop OS. If I cannot make hosts entries I cannot do my
job and my company will revoke my freedom of OS.
So, being new to this I have ask, "can I install
http://packages.ubuntulinux.org/feisty/gnome/gnome-system-too
That upload fixes the problem:
gnome-system-tools (2.17.91-0ubuntu1) feisty; urgency=low
.
* New upstream version:
Network:
- Avoid a critical warning
- Fix invalid memory free() which was causing lots of grief
(Ubuntu: #67936, #70756)
- call g_thread_init() to avoi
fixed upstream
** Changed in: gnome-system-tools (Ubuntu)
Status: Needs Info => Fix Committed
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-b
** Changed in: gst (upstream)
Status: Rejected => Fix Released
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Reopening, that doesn't crash with that host extra lines on my box, the
bug looks like a memory corruption, nothing obvious to the valgrind log
though. Could you try to get an another valgrind log with "G_SLICE
=always-malloc G_DEBUG=gc-friendly valgrind..."?
** Changed in: gnome-system-tools (Ubu
** Attachment added: "My /etc/hosts file"
http://librarian.launchpad.net/5773589/hosts
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
That new crash file looks like
http://bugzilla.gnome.org/show_bug.cgi?id=372697 upstream, the valgrind
log points no error though. What lines did you add to /etc/hosts to
trigger the crash?
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailin
I have to note that i have added 2 lines to /etc/hosts and that since a
short time i even get a crash when i run network-admin with sudo or
gksudo.
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https
** Attachment added: "Network-admin gdb backtrace"
http://librarian.launchpad.net/5773224/gdb-network-admin.txt
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
** Attachment added: "Valgrind log"
http://librarian.launchpad.net/5773214/valgrind.log.6229
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Could anybody having the problem get a debug backtrace and valgrind log
(https://wiki.ubuntu.com/Valgrind) then we can reopen the bug, without
those informations the bug is not that useful
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing
This bug should be reopened - description from montag
(https://launchpad.net/ubuntu/+source/gnome-system-
tools/+bug/67936/comments/11) is correct. After adding entries to
/etc/hosts starting network-admin from menu (or from command line)
results in application crash. You can successfully run netw
getting a backtrace with 0ubuntu2 is fine
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
The problem still occurs. I tried to install gnome-system-tools-dbgsym,
but it wont because it depends on gnome-system-tools (= 2.15.5-0ubuntu2)
but i have the ubuntu4 version installed. Should i fall back to version
ubuntu2 or wait for an update on the dbgsym package?
--
[network-admin] Crash wh
I have found a site claiming to have Razer Tarantula 2.01 drivers.
http://www.razerblueprints.net/index.php?option=com_docman&task=cat_view&gid=60&Itemid=69
I doubt this is legitimate and wanted to know what the deal is, spoof or
virus I dunno.
On 12/24/06, montag <[EMAIL PROTECTED]> wrote:
>
> I'
I've had the same problem.
Network-admin began to crash at the startup after I've added an host. Removing
manually the relative line in /etc/host made network-admin to start again.
Then I've tried to repeat the experiment: adding an host (using network-admin
or editing manually the file) makes ne
could you get one with gnome-system-tools-dbgsym installed?
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I thought i've made a debug backtrace. I've posted it here. What do you
want me to check, because the problem is still there?
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
no update, closing the bug now. Feel free to reopen with the asked
details if you you get that problem again
** Changed in: gnome-system-tools (Ubuntu)
Status: Needs Info => Rejected
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs maili
Well I reinstalled the OS, and have yet to see this issue pop up as of
yet.
On 10/31/06, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
>
> it's probably pointing to the wrong upstream bug. Maybe you could get a
> debug backtrace?
>
> --
> [network-admin] Crash when starting from menu.
> https://laun
it's probably pointing to the wrong upstream bug. Maybe you could get a
debug backtrace?
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I am also having the exact same problem. I traced the Gnome-bugzilla
report, and the power that be claim it is not Gnome related problem. So
what is it?? I cannot connect to wireless devices because it crashes.
running via terminal using gksudo or sudo works, but connection to
wireless is not eve
** Changed in: gst (upstream)
Status: Unknown => Rejected
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Here is all the gdb output i get
[EMAIL PROTECTED]:~$ gdb network-admin
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
** Bug watch added: GNOME Bug Tracker #364625
http://bugzilla.gnome.org/show_bug.cgi?id=364625
** Also affects: gst (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=364625
Importance: Unknown
Status: Unknown
** Bug watch removed: GNOME Bug Tracker #364625
http://bugzill
Here is the bug report made for Gnome-bugzilla
http://bugzilla.gnome.org/show_bug.cgi?id=364625
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I have the same issue when i run it from command line as normal user.
With sudo or gksudo it works without problems (as far as i can see). I
will make a backtrace tonight when i'm on my system again.
--
[network-admin] Crash when starting from menu.
https://launchpad.net/bugs/67936
--
desktop-b
Thanks for your bug. Do you have the same issue if you run it from a command
line? Could you install libglib2.0-0-dbg and get a backtrace with gdb?
- gdb network-admin
(gdb) run
... get the crash
(gdb) thread apply all bt
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medi
38 matches
Mail list logo
