| 2006-10-24 09:33:46 |
KenSentMe |
bug |
|
|
added bug |
| 2006-10-24 09:48:53 |
Sebastien Bacher |
gnome-system-tools: status |
Unconfirmed |
Needs Info |
|
| 2006-10-24 09:48:53 |
Sebastien Bacher |
gnome-system-tools: importance |
Undecided |
Medium |
|
| 2006-10-24 09:48:53 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
|
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 |
|
| 2006-10-24 09:48:53 |
Sebastien Bacher |
gnome-system-tools: assignee |
|
desktop-bugs |
|
| 2006-10-24 14:15:58 |
Daniel Holbach |
bug |
|
|
assigned to gst (upstream) |
| 2006-10-25 08:35:27 |
Bug Watch Updater |
gst: status |
Unknown |
Rejected |
|
| 2006-12-01 10:58:11 |
Sebastien Bacher |
gnome-system-tools: status |
Needs Info |
Rejected |
|
| 2006-12-01 10:58:11 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
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 |
no update, closing the bug now. Feel free to reopen with the asked details if you you get that problem again |
|
| 2007-01-16 17:12:57 |
KenSentMe |
bug |
|
|
added attachment 'valgrind.log.6229' (Valgrind log) |
| 2007-01-16 17:14:34 |
KenSentMe |
bug |
|
|
added attachment 'gdb-network-admin.txt' (Network-admin gdb backtrace) |
| 2007-01-16 18:48:34 |
KenSentMe |
bug |
|
|
added attachment 'hosts' (My /etc/hosts file) |
| 2007-02-06 17:46:06 |
Sebastien Bacher |
gnome-system-tools: status |
Rejected |
Needs Info |
|
| 2007-02-06 17:46:06 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
no update, closing the bug now. Feel free to reopen with the asked details if you you get that problem again |
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..."? |
|
| 2007-02-12 07:49:23 |
Bug Watch Updater |
gst: status |
Rejected |
Fix Released |
|
| 2007-02-12 09:00:34 |
Sebastien Bacher |
gnome-system-tools: status |
Needs Info |
Fix Committed |
|
| 2007-02-12 09:00:34 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
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..."? |
fixed upstream |
|
| 2007-02-12 17:01:10 |
Sebastien Bacher |
gnome-system-tools: status |
Fix Committed |
Fix Released |
|
| 2007-02-12 17:01:10 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
fixed upstream |
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 avoid GSlice warning
- Improve migration of older parameters in location files to newer format
Shares:
- Check whether there's connection to the bus before requesting data
in the nautilus extension
- call g_thread_init() to avoid GSlice warning
Time:
- updated screenshots for the documentation (Ubuntu: #83006)
Users:
- Mark a few dialogs as transient for another ones
* debian/patches/98_automake.dpatch:
- updated
|
|
| 2007-03-08 15:03:55 |
Sebastien Bacher |
bug |
|
|
added attachment 'gst.debdiff' (change from upstream applied to the edgy version) |
| 2010-09-15 22:46:09 |
Bug Watch Updater |
gst: importance |
Unknown |
Critical |
|
