It's a little late to fix this for Karmic, it should have been done
months ago. For now, best answer is upgrade to Lucid, since it's a
LTS.
The fix wouldn't be very complex. We should close the user settings
dialog when user clicks on the Change password button. I can post a
patch, if a core dev
That one is fixed upstream with 2.9.10, which should be in Lucid soon.
** Changed in: system-tools-backends
Status: Fix Committed = Fix Released
--
system-tools-backends crashed with SIGSEGV in dbus_message_iter_append_basic()
https://bugs.launchpad.net/bugs/534154
You received this bug
Hugh - not 2.9.10, but the system-tools-backends 2.10.0.
--
system-tools-backends crashed with SIGSEGV in dbus_message_iter_append_basic()
https://bugs.launchpad.net/bugs/534154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
Thanks for your report. This bug is already known and fixed upstream, it
should be made available for Lucid at some point.
In the future, note that the best method to report bugs is to run
'ubuntu-bug
*** This bug is a duplicate of bug 544867 ***
https://bugs.launchpad.net/bugs/544867
Thanks for your report, but this bug is already fixed in current Lucid.
In the future, please check that you've updated all your packages before
reporting a bug, that will save developers' and triagers' time!
OK, that was fixed a few weeks ago.
** Changed in: system-tools-backends (Ubuntu)
Status: Triaged = Fix Released
--
users-admin crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/512112
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The trace is really poor. All I can see is that libgnome-keyring has a
failing assertion leading to abort. The assertion is ((int) res !=
INCOMPLETE).
One would have to check whether the bug is in desktopcouch or gnome-
keyring... Anyway, if you think there's not enough information to debug
this,
** Summary changed:
- desktopcouch-service crashed with SIGABRT in __kernel_vsyscall()
+ desktopcouch-service aborted from libgnome-keyring: ((int) res != INCOMPLETE)
--
desktopcouch-service aborted from libgnome-keyring: ((int) res != INCOMPLETE)
https://bugs.launchpad.net/bugs/556310
You
** Visibility changed to: Public
--
firefox-bin crashed with SIGSEGV in gdk_window_get_frame_extents()
https://bugs.launchpad.net/bugs/557631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sorry, but this is not a duplicate. As I explained in the description, renaming
the top directory is enough to fix the problem, and it's in valid UTF-8. I've
been using UTF-8 for ages, and all the files in this folder are correctly named:
$ python utf8-filename-check.py
You don't have any
Though, it's true that something is going wrong with encoding here:
2010-04-06 10:51:50,172 - ubuntuone-preferences - ERROR - [Failure instance:
Traceback (failure with no frames): class 'dbus.exceptions.DBusException':
org.freedesktop.DBus.Python.KeyError: Traceback (most recent call last):
No worries, if i made it public myself, it's because I know there aren't
any sensitive data in Empathy (only IRC chat).
** Visibility changed to: Public
--
empathy crashed with SIGSEGV
https://bugs.launchpad.net/bugs/554708
You received this bug notification because you are a member of Ubuntu
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43335768/Dependencies.txt
** Attachment added: UbuntuOneClientPackages.txt
http://launchpadlibrarian.net/43335769/UbuntuOneClientPackages.txt
** Attachment added: UbuntuOneOAuthLoginLog.txt
Public bug reported:
Binary package hint: ubuntuone-client
It seems that Ubuntu One fails to share directories with non-ASCII
Unicode chars, in my case accentuated French chars ('é'). Choosing
Synchronize with Ubuntu One from Nautilus doesn't work, while it's
fine if I rename the folder to
I disagree. We wont change this because hiding system groups would make
the groups dialog completely useless. Users have nice ways of tweaking
privileges, but those who go to the groups dialog must know what they
are doing.
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed =
** Summary changed:
- [users-admin] Changing password many times in the same session hangs and
corrupts it
+ [users-admin] Changing password to something similar hangs
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Confirmed
** Also
Thanks for your report. I can confirm the bug, but it has nothing to do
with users-admin. Just removing an user via 'deluser' triggers the bug.
What is interesting is that new users appear on the fly in the menu,
while they are not removed when deleted. This makes me think something
very trivial
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=13931
Importance: Unknown
Status: Unknown
--
Acer Aspire 5720 hangs on second resume from suspend, i.e. suspends only once
https://bugs.launchpad.net/bugs/160763
You received this bug notification because you are
Yeah, you're right, that could well be the same bug. But since we don't
really know what leads to one or another trace... Could it be different
hardware? In this case we could consider the traces as the same.
--
[i915] Crash after suspending (NULL pointer dereference in intel_crt_detect())
** Changed in: user-setup (Ubuntu)
Status: New = Triaged
** Changed in: user-setup (Ubuntu)
Importance: Low = Medium
--
Missing default groups for user created on install
https://bugs.launchpad.net/bugs/339164
You received this bug notification because you are a member of Ubuntu
Bugs,
That's just like the other bug. I consider this as Fix Released because
everything from the software has been uploaded to Lucid, but we need
translations to be imported to Launchpad, and a new language pack to be
made available. Please leave this as Fix Released, as no action is
required to get it
The reason why we can't fix that in the application itself is that
button boxes don't allow buttons to have different widths. So we would
have to use a terrible hack, of fix GTK. IMO it's better to improve the
button itself.
--
PolkitLockButton too wide, and shouldn't change size when unlocked
Yeah, I've reported this long time ago upstream, so far no reply. The
message should really be made shorter (using French here). But one of
the solutions is to get rid of these buttons, just like users-admin in
Lucid. ;-)
** Package changed: gnome-system-tools (Ubuntu) = policykit-1-gnome
OK, thanks for reporting that. I've closed the upstream report too,
nothing has happened there for a long time.
--
[network-admin] Need option for wireless-key 'restricted'
https://bugs.launchpad.net/bugs/27896
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** Summary changed:
- BUG: unable to handle kernel NULL pointer dereference at 0108
+ [GM965] NULL pointer dereference in intel_tv_detect()
--
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
*** This bug is a duplicate of bug 525801 ***
https://bugs.launchpad.net/bugs/525801
** This bug is no longer a duplicate of bug 553176
[i915] Crash after suspending (NULL pointer dereference in
intel_crt_detect())
** This bug has been marked a duplicate of bug 525801
[GM965] NULL
I don't think these are all duplicates. I've kept all the duplicates
where the oops happens in intel_crt_detect(), and created bug 525801 for
the ones in intel_tv_detect(). It seems Apport only considers the NULL
pointer dereference as the common part, but I fail to see how this can
ensure the
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
** Changed in: linux (Ubuntu)
Importance: Low = High
--
[GM965] NULL pointer dereference in intel_tv_detect()
https://bugs.launchpad.net/bugs/525801
You received this bug notification because you are a member of Ubuntu
Bugs,
I've separated these reports from bug 553176 because they don't happen
in the same function. We'll see whether they are related or not.
** Summary changed:
- [GM965] NULL pointer dereference in intel_tv_detect()
+ [i915] NULL pointer dereference in intel_tv_detect()
** Tags added: metabug
**
Yes, I'll have to fix that string, but that will be for Lucid+1.
We can't really remove these checks because when changing password for a
user different than the current one, PAM doesn't check the password,
which is set using 'chpasswd'. The current situation is pretty lame, but
we'd have to
I think upstream were talking about the X trace, not the Oops, which is
the only way to get the real cause of the X crash.
--
[i915] Crash after suspending (NULL pointer dereference in intel_crt_detect())
https://bugs.launchpad.net/bugs/553176
You received this bug notification because you are a
** Changed in: gst
Status: In Progress = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
binary users-admin hints using if not installed ecryptfs-utils
https://bugs.launchpad.net/bugs/544867
You received this bug notification because you
Works for us, please reopen if it still doesn't on your system.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
users-admin Help button doesn't do anything in Lucid
https://bugs.launchpad.net/bugs/529790
You received this bug notification because you are a
Fixed with 2.30.
** Changed in: ubuntu-translations
Status: Fix Committed = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Fix Committed = Fix Released
--
Information message from users-admin shows untranslated, albeit it's translated
Fixed with 2.30.
** Changed in: gst
Status: Fix Committed = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
Change... buttons on users-admin dialog untranslated and untranslatable
https://bugs.launchpad.net/bugs/543664
You received this
Closing, I think it's been fixed since then.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/513233
You received this bug notification because you are a member of Ubuntu
Bugs,
Fixed with 2.30.
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
** Changed in: gst
Status: Fix Committed = Fix Released
--
users-admin and about-me hang when new password value only differs in case
https://bugs.launchpad.net/bugs/512315
You received
I've been able to reproduce the same crash after/while upgrading. So I
confirm my own bug (bad, bad!).
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Medium = High
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Triaged
--
gnome-settings-daemon crashed with
** Bug watch added: GNOME Bug Tracker #614800
https://bugzilla.gnome.org/show_bug.cgi?id=614800
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=614800
Importance: Unknown
Status: Unknown
--
gnome-settings-daemon crashed with SIGSEGV
http://www.google.com/search?q=Matthias+Clasen%27s+accounts-dialog
--
[enhancement] Password strength meter in user creation
https://bugs.launchpad.net/bugs/155308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thanks for investigating the code, but I don't think the line you cite
is the source of the bug. This line is only run when changing your own
password, which is a completely different case. Furthermore, enabling an
account works for me following the same procedure as you.
So I rather suspect that
And in a more recent version like 9.10 or 10.04? Sorry, but many
warnings like that have been fixed since 9.04, and you really can't
expect a fix being backported there.
--
[network-admin] Gtk-WARNING **: Unknown property: GtkComboBox.items
https://bugs.launchpad.net/bugs/206291
You received
*Please* you two stop discussing your private issues here. This is a bug
report, if you want to talk about you like and existential questions,
use your mail or find a place to meet. You're really not furthering the
case of buttons on the right side with all this noise.
--
[Master] Window Control
Hmm, I wouldn't like to hijack your report. If other people can confirm
the new kernel fixed their crash here, we should just mark it as fixed
and continue with other reports. Seems the error message is very
generic, and may come from different bugs in the kernel. So, sorry, I'm
closing again.
Glad to know I'm not alone then! ;-) Marking as Triaged.
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Bug watch added: freedesktop.org Bugzilla #26974
http://bugs.freedesktop.org/show_bug.cgi?id=26974
** Also
*** This bug is a duplicate of bug 553176 ***
https://bugs.launchpad.net/bugs/553176
Doesn't seem to be a duplicate of bug 447159. The X crash is the same,
but the cause in the kernel is different, since some people say their
bug is fixed there, while this one isn't. See bug 553176 for kernel
Sure, if you want to implement it. But I'm not sure I'll work on that,
given Matthias Clasen's accounts-dialog already has this feature, we may
as well switch to it.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Yeah, you were also able to set the phone number, and tweak membership
to every kind of obscure privilege, plus changing home directory. But
how many people need that? If you really need a specific UID, just
create the user and change UID after, that doesn't hurt, and makes most
people not scared
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42967540/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42967541/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42967542/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42988297/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42988298/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42988299/Disassembly.txt
** Attachment
dicka: Personally, I've opened bug 553176 as I said above, since I'm
tracking this bug for quite a long time now. You may have a look there
and see whether that seems to be the same bug, but the best would be to
get Apport upload necessary information to a new report, and explain
there why you
Glad to know some people are actually using that feature! ;-)
I think that's fixed in the system-tools-backends 2.10.0, which I hope
will be uploaded soon to Lucid.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Changed in: gnome-system-tools (Ubuntu)
Importance:
So let's reopen it for now, waiting for more informations from
developers...
** Changed in: xserver-xorg-video-intel (Ubuntu Lucid)
Status: Fix Released = Triaged
--
[i945gm] Xorg assert failure: X: ../../src/i830_batchbuffer.h:79:
intel_batch_emit_dword: Assertion `pI830-batch_ptr !=
OK, thanks for the reply. So you suffer from this bug because you were
an early tester. You can either continue using gnome-volume-control-
applet, or add the indicator applet to your panel.
** Changed in: gnome-media (Ubuntu)
Status: Incomplete = Invalid
--
volume icon is missing
*** This bug is a duplicate of bug 546874 ***
https://bugs.launchpad.net/bugs/546874
That's simply a bug that should be fixed before the release. See
informations on the other report.
** This bug has been marked a duplicate of bug 546874
passwd - can't login, change password (pam_winbind
Public bug reported:
This happens about one hour after returning from suspend, and makes X
crash. I'm posting a link to the X report where I put the informations
and the link to upstream report.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/42769261/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/42769262/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/42769263/ArecordDevices.txt
See bug 553174 for X.org side of the crash.
--
[i915] Crash after suspending (unable to handle kernel NULL pointer dereference
at 0108)
https://bugs.launchpad.net/bugs/553176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
See bug 553176 for the kernel oops that likely caused the X crash.
Especially: http://launchpadlibrarian.net/42769271/OopsText.txt
** Visibility changed to: Public
** Bug watch added: freedesktop.org Bugzilla #26974
http://bugs.freedesktop.org/show_bug.cgi?id=26974
** Also affects:
Robert: I've been able to reproduce the same kind of crash with the new
kernel 2.6.32-19. See bugs 553174 and 553176 - now I'm not sure that's
the very same bug. Should I keep them separate and meave this one as
fixed?
--
[i945gm] Xorg assert failure: X: ../../src/i830_batchbuffer.h:79:
** Description changed:
This happens about one hour after returning from suspend, and makes X
- crash. I'm posting a link to the X report where I put the informations
- and the link to upstream report.
+ crash. See bug 553174 for the X crash report, where I have put the
+ informations and the
** Bug watch added: freedesktop.org Bugzilla #27411
http://bugs.freedesktop.org/show_bug.cgi?id=27411
** Also affects: policykit via
http://bugs.freedesktop.org/show_bug.cgi?id=27411
Importance: Unknown
Status: Unknown
** Changed in: policykit-1 (Ubuntu)
Status: New =
*** This bug is a duplicate of bug 546874 ***
https://bugs.launchpad.net/bugs/546874
benohb: Are you joking? You already reported the same bug with the very
same description as #552026, and I said you that was a duplicate of bug
546874. You're generating extra work for triagers and developers
I can confirm it still happens in Lucid:
- with Metacity, OO steals focus when the main window has finished loading
- with Compiz, all applications steal focus, so can't test
- with Mutter/GNOME Shell, OO steals focus as with Metacity
Upstream said a year ago, after the bug was fixed:
a) it was
I reported a new issue because I couldn't reopen bug myself, and the
original report is form 2003, code is likely to have changed in that
regard.
** Bug watch added: OpenOffice.org Issue Tracker #110545
http://qa.openoffice.org/issues/show_bug.cgi?id=110545
** Changed in: openoffice
No news on that bug? If you can't provide the required information,
please say so, we'll have close the bug. Thanks!
--
OpenOffice.org Writer window exhibits strange maximizing behavior upon startup.
https://bugs.launchpad.net/bugs/442506
You received this bug notification because you are a
This one seems to have been fixed upstream with 3.2 (ooo32gsl09).
** Changed in: openoffice.org (Ubuntu)
Status: Triaged = Fix Released
--
[upstream] [3.2] Apostrophes are not printed when using font 'Gentium'
https://bugs.launchpad.net/bugs/376953
You received this bug notification
Bug 376953, which is very similar, should be fixed in Lucid. Could you
check whether that's the case? Thanks!
** Changed in: openoffice.org (Ubuntu)
Status: Triaged = Incomplete
--
[ooo-build] OOo printed documents miss some cyrillic alphabet letters
9.10 only has OpenOffice.org 3.1, while Lucid has 3.2, where the bug
seems to be fixed. Could you confirm that's the case? Thanks!
** Changed in: openoffice.org (Ubuntu)
Status: Triaged = Incomplete
--
OpenOffice.org does not print capital Й with msttcorefonts
nhasian: you need to add the notification applet, which is different
from the notification area.
--
volume icon is missing
https://bugs.launchpad.net/bugs/552221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
Thanks for the report. Have you checked that you're actually able to
change user passwords? Just create a test user, then run 'sudo passwd
$USER_LOGIN'. If you get a System Error message even when passwords
are long enough, then you're experiencing bug 546874 (which as a
workaround).
** Changed
Well, pasting a link, expecting triagers will go through the whole
thread to understand your problem is hardly a nice practice. I see there
that your problem is solved, and you don't provide any detail about the
problem. Did you upgrade from Karmic? Was the applet present in the
list, only
Actually, in Ubuntu, you need to add the notification applet to the
panel (not the notification area). It provides the messaging and the
volume icon, that's why gnome-volume-control-applet is disabled (not
sure how, though). The bug is in the fact that upgraders are not
suggested to add it, but
When exactly did you upgrade from Karmic? Normally, since beta1, the
indicator-applet is added to the panel automatically. If you upgraded
before that, then you may have missed that feature.
--
volume icon is missing
https://bugs.launchpad.net/bugs/552221
You received this bug notification
Looks like the icon name is not filled correctly:
theme_dir_get_icon_suffix (dir=value optimized out, icon_name=0x1 Address
0x1 out of bounds, has_icon_file=0x0)
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551809
You received this bug notification because you
You know, I've reproduced it with the Intel development branch of 2.6.33
too, so it's clearly not gone...
--
[i945gm] Xorg assert failure: X: ../../src/i830_batchbuffer.h:79:
intel_batch_emit_dword: Assertion `pI830-batch_ptr != ((void *)0)' failed.
https://bugs.launchpad.net/bugs/447159
You
*** 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/516601
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
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
Same here. Using 'chpasswd' I get the same error, with a little more details:
chpasswd: (user test) pam_chauthtok() failed, error:
System Error
** Changed in: shadow (Ubuntu)
Status: Confirmed = Triaged
** Changed in: shadow (Ubuntu)
Importance: Undecided = High
--
[Lucid] passwd
** 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
That's a very annoying bug I've been tracking for some time. I had
already reported it separately some time ago, and provided upstream with
some additional debugging information there. I really hope they are
going to investigate this further.
** Bug watch added: freedesktop.org Bugzilla #26974
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
701 - 800 of 1774 matches
Mail list logo
