** This bug is no longer a duplicate of bug 573387
gnome-keyring-daemon fails to start
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Ah, that was what I feared: your bug is different from the password-less
issue. So let's say the latter is bug 525642, and deal with your problem
here. What does 'ps x|grep keyring' return, with and without autologin
enabled? What errors do you get in /var/log/auth.log in both cases?
(The logs
ntpdate is not supposed to be run all the time AFAIK, it's mainly here
to allow synchronizing the clock manually (what the Sync Now button is
time-admin does), and creating scripts to do that. On my box, syslog
doesn't contain anything related to ntpdate... Can't you think of any
package you may
Is that without autologin and without password-less enabled?! That seems
very similar to what we get when it's on.
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
But that's not a problem with time-admin, which is not supposed to
control ntpdate at all. It's just that ntpdate shouldn't run by ifup
when interfaces are enabled. Else, there's no point in optionally
installing the ntp daemon.
I suspect ntpdate is not run when your connections are managed using
Is this still buggy in Lucid?
Anyway, I think fixing bug 583994 by replacing ntpdate with ntpd would
solve this the right way.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member
Upstream has committed a fix which should be made available with gnome-
keyring 2.30.2.
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Maybe you should remove the .service file you added manually. Bug 525642
is fixed now, and manual tweaks like that can lead to problems. It's
possible that gnome-keyring is started via D-Bus before the PAM module
loads it, so it lacks the --login option that automatically unlocks the
keyring. But
That's because Samba and NFS no longer use SysV boot script, but Upstart
jobs. Thus, they are not detected even if they are installed. We need a
temporary fix in Lucid for that, possibly a ugly hack.
In the long term, though, that's going to be a problem: we need minimal
support for Upstart jobs,
** Branch linked: lp:~nalimilan/ubuntu/lucid/gnome-system-tools/shares-
services
--
shares-admin doesn't see NFS and SMB installed (no support for Upstart jobs)
https://bugs.launchpad.net/bugs/574046
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Yeah, I know, normally the --login option should be present in your case, but
for some reason it's not. I don't really see why it should work differently on
your system than on mine (say). Do you have a personal config starting g-k?
e.g. check with:
ls ~/.config/autostart/*keyring*
Else, you
g-k-d should be started by it's PAM module. If it's not started on login
before any app tries to use it, then it's the problem. What does
/etc/pam.d/gdm contains?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a
Yeah, the problem is that the menu is shared with the groups, so fixing
this would require splitting it from there. It may be easier to remove
completely this menu, since it's mainly redundant. But definitely not a
very serious issue...
Don't bother reporting this upstream, I manage the bugs here
** Package changed: gnome-system-tools (Ubuntu) = gnome-control-center
(Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = Low
--
Proxy auto-config (PAC) not usable by some applications
https://bugs.launchpad.net/bugs/587097
You received this bug notification
use_md5 parameters has been removed in 2.10, we now use chpasswd to set
the password, and don't play with encryption methods.
** Changed in: system-tools-backends (Ubuntu)
Status: New = Fix Released
--
including a file leads to confusion about whether md5 is being used
That would be a different bug then. Could you paste here the line from
/etc/passwd which was the problem? National characters shouldn't be an
issue as long as they are in UTF-8; if they aren't, then some strange
tool must have gone wrong when writing to it.
Closing the bug since in Lucid we no
** Changed in: gdm (Ubuntu)
Status: Confirmed = Triaged
--
Unable to change options on passwordless login
https://bugs.launchpad.net/bugs/508552
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
HP: and what does 'ps x | grep keyring' returns on your box after
booting without your script?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
Seems to be the same issue then. Are you using autologin or password-
less login?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
Yes, but that doesn't change the problem. Bug 583428 is about g-k-d
hanging when started without a password, whether it actually needs one
or not. ;-) BTW, let's comment this on that report rather than here,
which may not be the same issue.
--
gnome-keyring-daemon fails to start
Thanks for the report. Do you mean you were removing two accounts by
selecting them both at the same time, and clicking Delete once? Did the
crash happen before or after the confirmation dialog asking whether to
remove user files?
** Changed in: gnome-system-tools (Ubuntu)
Status: New =
Here's a trace with --sync, up-to-date Maverick as of today.
The crash occurs when window manager changes (or restarts), which
triggers terminal_window_composited_changed_cb() and
terminal_util_x11_set_net_wm_desktop().
Breakpoint 1, gdk_x_error (display=0x9cd5d90, error=0xbff3a2ac) at
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug is no longer a duplicate of bug 624255
gnome-terminal crashed with signal 5 in gdk_x_error()
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
*** This bug is a duplicate of bug 633303 ***
https://bugs.launchpad.net/bugs/633303
** This bug has been marked a duplicate of bug 633303
gnome-terminal crashed with signal 5 in _XError()
* You can subscribe to bug 633303 by following this link:
Seems also to occur very often when Unity crashes, obviously for the
same reason (mutter dies).
** Changed in: gnome-terminal (Ubuntu)
Importance: Medium = High
** Summary changed:
- gnome-terminal crashed with signal 5 in _XError()
+ gnome-terminal crashes when Mutter is restarted
**
Thanks for your report, but the version you're using is quite old (9.04
is reaching its end of life), and debugging this kind of error is quite
hard since we have no way to reproduce them. So I'm going to close this
bug, anyway newer versions don't seem to suffer from this crash. (For
the record,
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 633349
gnome-power-manager crashed with SIGSEGV in g_str_hash()
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 633349
gnome-power-manager crashed with SIGSEGV in g_str_hash()
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 633349
gnome-power-manager crashed with SIGSEGV in g_str_hash()
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following this link:
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
The same crash happens in gnome-settings-daemon, the culprit is
libappindicator or GTK+.
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of bug 627236
gnome-power-manager crashed with SIGSEGV
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following this link:
A few reports against gnome-power-manager show the very same backtrace,
which confirms the bug is in libappindicator using GtkStatusIcon
(whichever the culprit), not in gnome-settings-daemon. See bug 63334,
and upstream report for explanations.
--
gnome-settings-daemon crashed with SIGSEGV
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following this link:
The same crash happens in gnome-settings-daemon, the culprit is
libappindicator or GTK+.
--
gnome-power-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/552276
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I was going to mark this bug as duplicate of bug 551809, but for some
reason Launchpad fails to do it (maybe there are too many duplicates).
So I'm going to close this report, if you are interested in its
resolution, please subscribe manually to the other one. Sorry...
** Changed in:
*** This bug is a duplicate of bug 574046 ***
https://bugs.launchpad.net/bugs/574046
Yes, that's because it doesn't detect NFS and Samba. See bug 574046.
** This bug has been marked a duplicate of bug 574046
shares-admin doesn't see NFS and SMB installed (no support for Upstart
jobs)
*
Thanks for your report. Are you able to reproduce this crash? Could you
explain precisely what you did to trigger it?
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
** This bug is no longer flagged as a security vulnerability
--
time-admin crashed with SIGSEGV in
Installing today's upgrades, I reproduced the crash of gnome-power-
manager again. I'm attaching the relevant part of /var/log/dpkg.log, in
the hope we'll be able to find what's the kind of package that causes
the crash. So, if you trigger the bug after running upgrades, please
also attach your
Indeed, thanks for reporting. Not sure we want to keep this icon, even
if fixed. I could as well remove it, since it's really not useful.
I'll push a fix shortly, for 2.32.1.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
--
time-admin icon stock_timezone missed
Wow, we make me worry for a few minutes... ;-) I thought you meant
package ntp wasn't detected even when it was installed, which was fixed
a few releases ago.
ntpdate is absolutely not taken into account, because it doesn't keep your cock
in sync with network servers: it only synchronizes it
Guram: I'm not sure the solution is to change the login screen's
behavior. Since you can't guess that the user is going to click on an
account with password-less login, you would have to see the options all
the time. This means you cannot know what language and keyboard layout
are the default for
*** This bug is a duplicate of bug 574046 ***
https://bugs.launchpad.net/bugs/574046
** This bug has been marked a duplicate of bug 574046
shares-admin doesn't see NFS and SMB installed (no support for Upstart
jobs)
* You can subscribe to bug 574046 by following this link:
Both packages have this bug fixed in Maverick (2.32).
** Changed in: gst
Importance: Undecided = Unknown
** Changed in: gst
Status: Fix Committed = Unknown
** Changed in: gst
Remote watch: None = GNOME Bug Tracker #619354
** Changed in: gnome-control-center (Ubuntu)
Status:
Reopening as per recent comments.
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Released = Triaged
--
gnome-keyring doesn't unlock ssh key
https://bugs.launchpad.net/bugs/631980
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Are you sure the timezone change actually took effect? That is, does
restarting time-admin show the timezone you selected? If that's the
case, then the bug would be in the XFCE panel, which could update the
timezone.
OTOH, I'm not sure that's a real bug, because you may want to change the
Confirmed. It seems we're using MAX_GUINT32 as the GID for the user when
trying to change its home dir, which always fails. This value isn't
supposed to be used after the user has been created, it just means
default GID and should be updated to a real value imediately after the
user's creation.
Sure, but you don't need feedback when the operation takes one second
instead of 20.
--
users-admin has significantly delayed response after clicking OK
https://bugs.launchpad.net/bugs/546873
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Hmm. You reported the bug against the gnome-system-tools, so I thought
that was a bug in users-admin - actually, you first experienced it with
gnome-about-me, which is in gnome-control-center. But I can confirm it
happens with users-admin, which partly uses the same code.
OTOH you say you've been
I don't think we can close the bug because it was confirmed on the
upstream report to be still present in 2.28.0. No code changes have been
made since then, so the bug is still here. Sure, network-admin is no
longer shipped by default, so that's less of a problem, but from the POV
of this tool,
Ah, thanks for the clarification!
So:
- have you ever experienced this bug with users-admin?
- have you ever been able to change your password successfully using
gnome-about-me?
- have you installed special password or PAM packages such as pam-cracklib?
- is the fact that you change the password
What version are you using? Since 2.29, users-admin simply runs 'adduser
$LOGIN --disabled-password', so everything that happens after that is a
problem with adduser and adduser.conf. Profiles are a different matter,
and by default only add membership to special groups like video, admin,
etc.
**
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
Thanks for your report. I strongly suspect your problem is the same as
bug 533870. Are you using a 64 bits version of Ubuntu? If so, then
please try the package from comment #30 on that report, and tell me
** Summary changed:
- Changing the long name in users-admin to the same name results in an error
+ Crash in SelfConfig on amd64
--
Crash in SelfConfig on amd64
https://bugs.launchpad.net/bugs/533870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Let's close the Intrepid task, nobody is going to backport the fix
there...
** Changed in: system-tools-backends (Ubuntu Intrepid)
Status: Triaged = Won't Fix
--
package system-tools-backends 2.6.0-1ubuntu1.1 failed to install/upgrade:
subprocess post-installation script returned error
*** This bug is a duplicate of bug 475974 ***
https://bugs.launchpad.net/bugs/475974
Actually, I think that's a duplicate of bug 475974. What happens is that
the first time you open the group settings dialog, the GID is set to 0,
and group creation fails. Just close and launch the dialog
Thanks for you report. I think you should read more about how to write a
useful report before we go on trying to fix your problems. First, you
should never report several unrelated bugs at the same time. For each
bug, we need a precise procedure about how to reproduce it, and many
details, which
** Package changed: gnome-system-tools (Ubuntu) = gnome-panel (Ubuntu)
--
date and time applet mix up and turns unreadable
https://bugs.launchpad.net/bugs/544084
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
--
*** This bug is a duplicate of bug 470743 ***
https://bugs.launchpad.net/bugs/470743
Thanks for your report. This bug has already been reported as bug #
470743. You may want to go and comment there to propose your solution.
Please continue testing Lucid and reporting bugs!
** This bug has
Moving to nautilus, as PolicyKit itself provides a way to know whether
authentication was canceled or whether it failed. See POLKIT_ERROR_CANCELLED,
which is the GError returned by polkit_authority_check_authorization_finish(),
at
That's fixed in Lucid. Since 2.29.92 we automatically add the user to
the group named after its login if it already exists. That's not really
optimal since it may not be what you want, though - that will be
improved in the next cycle.
** Changed in: gnome-system-tools (Ubuntu)
Status:
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Triaged
--
Alt+C access key does not work in time-admin
https://bugs.launchpad.net/bugs/287262
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in
Martin: I guess you can simply run 'sudo killall polkitd', and it will
forget your authentication.
One would have to check whether gvfs actually redirects
POLKIT_ERROR_CANCELLED to G_IO_ERROR_CANCELLED, and if so, then add it
to the ignore case in Nautilus. Or simply add that condition in
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
--
system-tools-backends assert failure: *** glibc detected ***
** Attachment added: Stacktrace.txt
http://launchpadlibrarian.net/42383966/Stacktrace.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this
** Attachment added: ThreadStacktrace.txt
http://launchpadlibrarian.net/42383968/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/42318890/CoreDump.gz
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided = Medium
--
** Attachment added: StacktraceSource.txt
http://launchpadlibrarian.net/42383967/StacktraceSource.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You
Woops! For some reason, apport-retrace removed the core dump even if it
failed to retrace...
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42384531/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk():
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
--
system-tools-backends assert failure: *** glibc detected ***
** Attachment added: Stacktrace.txt
http://launchpadlibrarian.net/42384662/Stacktrace.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this
** Attachment added: StacktraceSource.txt
http://launchpadlibrarian.net/42384665/StacktraceSource.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You
** Attachment added: ThreadStacktrace.txt
http://launchpadlibrarian.net/42384669/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/42384531/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends:
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42385283/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this bug
*** This bug is a duplicate of bug 534154 ***
https://bugs.launchpad.net/bugs/534154
Ah, I've finally managed to retrace the core dump on my box - I wanted
to be sure I could check that crash before releasing 2.10.0 tonight.
Hopefully, it seems to be a duplicate of bug 534154, which has a fix
Are you in a hurry? I said in about 10 days, and I'm going to release
it tonight, so that will make 15 days, which is the same from the POV of
Lucid inclusion. The only requirement is to be here for GNOME 2.30,
which is released this week, and it's better to wait for testers to
report bugs instead
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/515803
You received this
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/514816
You received this
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/516601
You received this
Thanks for your report and sorry for waiting so long before responding.
Could any of the reporters confirm the crash is still present in up-to-
date Lucid? I'm not able to reproduce it here. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
time-admin crashed
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42508621/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42508622/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42508623/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42509350/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42509351/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42509352/Disassembly.txt
** Attachment
Yeah, I noticed that yesterday too. Shouldn't be too hard to fix.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Summary changed:
- value of Configuration doesn't change on initial switch to Keep
synchronized with Internet servers
+ [time-admin] Value of
601 - 700 of 1655 matches
Mail list logo
