Thanks for your report. Are you able to reproduce this problem? I'd
really like to fix that if we can get enough information.
At least I'm sure that in Lucid users won't be affected, and groups
won't be removed. Only group membership will be affected, which is still
a problem though.
** Changed
This is fixed upstream with 2.29.2. Should be in Lucid soon.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Also affects: gst
Importance: Undecided
Status: New
** Changed in:
Hey, thanks for the patch, but we needed a little more than that to make
the file translated: Makefile.am had to be changed too, that was a
little tricky. See http://git.gnome.org/browse/gnome-system-
tools/commit/?id=4b3806048a0e0913b78615c85db6c43853151d1f.
Feel free to suggest other patches in
Thanks for the report, but in 2.29.2 (in Lucid) we don't allow selecting
any other setting than Real name and login when creating and user. You
can only change the main group after that. So that bug is obsolete.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Invalid
--
This is fixed with 2.29.2.
--
[users-admin]cannot create user when the /home directory already exist
https://bugs.launchpad.net/bugs/190815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Since 2.29.1 in Lucid we no longer use the unlock button, so that's
obsolete.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
--
users-admin doesn't fully update UI after unlock
No news on that bug?
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
Cannot unlock user priveledges.
https://bugs.launchpad.net/bugs/282065
You received this bug notification because you
Since Karmic we show all system groups by default, regardless of system
users being hidden.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Fix Released
--
users-admin should have a 'show all groups'
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Triaged
--
in users-admin the name 'root' is checked instead of uid 0
https://bugs.launchpad.net/bugs/255980
You received this bug notification
In 2.29.2 we hide root, and don't allow the last admin to be removed. If
user is about to lose its own admin rights, we warn him. For home
directory, there will be more improvements to come, like making user the
owner of the dir.
** Also affects: gst
Importance: Undecided
Status: New
** Summary changed:
- Unexpected display of /etc/group nfs entry in the user setting interface.
+ [users-admin] Unexpected display of /etc/group NIS entry
--
[users-admin] Unexpected display of /etc/group NIS entry
https://bugs.launchpad.net/bugs/107422
You received this bug notification
Confirmed for the power menu part. But you can choose language (Alt+L)
and log in right after, just type the password and hit Return.
** Summary changed:
- karmic gnome login requires mouse
+ Can't access GDM's power menu with keyboard
** Package changed: gnome-system-tools (Ubuntu) = gdm
Good catch indeed! That's the button used to change password when the
selected user is the current one. Does the bug appear only with that
user? In other cases, it should be hidden.
Anyway, this hack should go away in the next release, with a more
generic dialog from upstream.
--
Users-admin
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m U$
This is a bad copy/paste: U$ can't work, obviously, that should be UsersConfig.
/usr/sbin/system-tools-backends
Should be /usr/bin/system-tools-backends in 8.04.
Anyway, you don't need to run those to perform the test I
Chris, you said you were able to reproduce the problem too? So that
wouldn't be specific to the reporter's configuration... I'm absolutely
not able to see this, maybe I'll have to get the package form Lucid.
--
Users-admin password-password confirm requires 2 Tab keys
OK, sorry for the delay Roger. So if I understand correctly, the only
way to reproduce this problem is to create a new user when the users
list appears empty? That would be logical, since we commit the data we
have, which would be empty if it could not be loaded.
But do you mean that the second
This Debian bug is not related at all.
** Changed in: debian
Importance: Unknown = Undecided
** Changed in: debian
Status: Fix Released = New
** Changed in: debian
Remote watch: Debian Bug tracker #470123 = None
** Changed in: debian
Status: New = Invalid
** Also affects:
What I asked Xande to test should be interesting for you too:
One interesting test (for both of you) would be to start the scripts before
starting users-admin, and to compare the startup times: start users-admin once,
run it again and see the time it needs, then wait for 5 minutes so that the
Sure, that's really a trivial workaround on a desktop box...
$ sudo apt-get remove dbus
[...]
0 upgraded, 0 newly installed, 361 to remove and 2 not upgraded.
After this operation, 1173MB disk space will be freed.
Are you sure you're using Ubuntu? :D
--
[jaunty] Xephyr fails with D-Bus
No, Sugar is not at fault for the precise problem of this report. It's
just that comments above also had errors from Sugar that could indicate
another bug.
This report is strictly about a problem with D-Bus policy that doesn't
allow org.x.config.displayXX to be owned by users because only a few
Thanks for your report. Actually, you're not using network-admin from
the gnome-network-admin package, but network-manager. Reassigning.
I think you should tell us what kind of encryption is using your
network: WEP or WPA? And what type of password authentication too.
** Package changed:
If you are willing to help debugging this, then please run 'sudo ntpd
-q' and report its output, and whether that fixes the problem. Is your
clock highly different from the real hour, i.e. by hours as the title of
the bug says?
--
[jaunty] Synchronizing with a time server does not work when time
Good news, I've just finished a future patch that allows us to stop
creating the main group ourselves. When creating an user, the backends
can now omit the --gid option, and we let adduser (and equivalents) do
the work. This is simpler for everyone. Should be in the next release.
Now I need to
** Changed in: gst
Status: Fix Committed = Fix Released
--
[network-admin] Modem connection types not listed
https://bugs.launchpad.net/bugs/485641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If you are willing to help debugging this, then please run 'sudo ntpd
-q' and report its output, and whether that fixes the problem. Is your
clock highly different from the real hour, i.e. by hours as the title of
the bug says?
--
[jaunty] Synchronizing with a time server does not work when time
ceciliavergara: Please don't open new tasks against upstream projects
without any explanation. Why do you think this bug is still valid? I've
just tried to reproduce it, and it seems be fixed.
** Changed in: gst
Status: New = Invalid
--
[network-admin] Gtk-WARNING **: Unknown property:
So by first time you mean first time from fresh boot; there's no
package installation involved then. I think you're slightly wrong about
memory usage, because the fact that every SystemToolsBackends perl
process uses 10MB doesn't mean you can sum up those values to get the
total: there's shared
No, I had strong reasons to think we had actually fixed that in Jaunty.
** Changed in: gnunet (Ubuntu)
Status: Incomplete = Invalid
--
package gnunet-server 0.8.0a-1ubuntu3 failed to install/upgrade: subprocess
post-installation script killed by signal (Interrupt)
In Karmic, I can confirm that the -m Platform script does not die after
3 minutes, consuming 10MB until reboot. I'll give a look at this
problem.
Though, you mention in the description that there's a 90MB usage on
first launch. I guess this comes from the package installation, isn't
it? If that
Pjotr12345: please report your problem separately against the package
'passwd', this has nothing to do with the present bug. BTW, when
changing your own password, you should use 'passwd' instead of 'sudo
passwd'. The latter won't update your eCryptfs Private dir and your main
keyring password.
It's not unlikely that users-admin itself has introduced those broken
settings, but we can't really be sure. I'd need a list of all programs
that may change this file (maybe there aren't at all). But that doesn't
mean there isn't something broken here. I've checked our code, and
everything seems
*** This bug is a duplicate of bug 210710 ***
https://bugs.launchpad.net/bugs/210710
Hmm, seems a duplicate of bug 210710. Please follow the instructions I
gave in my latest comment there, and I'll have a look. So far, your
/etc/passwd file looks right to me. And AFAICT the root account is
You could just try changing in /etc/login.defs
UID_MAX 6
I think that should do the trick. Then it would mean the bug is in the
program that set this value...
--
System Admin Users and Groups: only root available
https://bugs.launchpad.net/bugs/210710
You received this bug notification
Could you follow the procedure at
https://wiki.ubuntu.com/DebuggingGnomeSystemTools#For%20Users%20[users-
admin] to provide more information? This way we would be able to find
out what's going on. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Confirmed
** Changed
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
[hardy] Unlock button not in dialog
https://bugs.launchpad.net/bugs/245809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thanks for your report. This was indeed a silly detail that I've just
fixed. It will be available in the next minor release.
Please continue to report bugs about the gnome-system-tools, especially
the next version that should land in Lucid in a month or so. Not many
people do this, which makes
If it's just for reviewing purposes, the only changes I added are in:
about_me_path = g_find_program_in_path (gnome-about-me);
show_passwd = (user != oobs_self_config_get_user
(OOBS_SELF_CONFIG
(GST_USERS_TOOL
The rationale behind this feature vs. the standard nullok_secure way is
that *you actually have a password*. This means users can be admins,
type their password to use sudo, PolicyKit or lock their screen, but
they are not asked to type it on login. They can additionally connect
over local SSH for
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, I've found the problem. It's not related to ConsoleKit directly, I
was actually misled by a warning shown for some reporters, but not all.
It seems that the messagebus user and groups don't match after an
Reopening. Duplicate 475503 has several reporters confirming that this
still happens when upgrading to Karmic. We should find out whether this
comes from the d-bus package of from another part of the system that
recreates the group with a wrong GID. Seems really strange.
** Changed in: dbus
jxparo: are you sure you are in Manual mode? I've reinstalled the gnome-
system-tools and I can still see this button in this mode. And I don't
see the patch that used to hide it in Ubuntu.
--
time-admin does not update time
https://bugs.launchpad.net/bugs/400130
You received this bug
I've no personal problem with that, but if we don't respect what we
write on the Wiki, we may as well change it instead of using
inconsistent statuses. Don't worry about the wrong upstream status for
that, I always go over all bugs registered in the GNOME System Tools
Launchpad project (i.e. for
That's tightly related to bug 484559. If you don't mind losing the
improvement brought by fixing bug 307019, I think you can commit the
debdiff that is available on the former. Anyway the goal is to get rid
of this hack and do all the work right by ourselves, i.e. without
dependencies.
--
This is not committed in Ubuntu. It's committed upstream, waiting for a
release upstream (2.29.2) to be committed on Ubuntu's Baazar repository,
and then released in Lucid. See https://wiki.ubuntu.com/Bugs/Status.
Thanks for helping, though! ;-)
** Changed in: gnome-system-tools (Ubuntu)
The polkitd part does not work because the daemon was already running. Could
you try
sudo killall /usr/lib/policykit-1/polkitd
sudo /usr/lib/policykit-1/polkitd
--
D-BUS activation fails to start console-kit-daemon with error: Success
https://bugs.launchpad.net/bugs/475503
You received this bug
Le dimanche 13 décembre 2009 à 11:01 +, José Luis Ricón a écrit :
I agree with considering chromium (or even a canonical remix of it) as
a default browser. The only thing firefox has over it are extensions,
but in a few months, the most useful extensions will be probably
ported.
I think
I think we could add this option to the new Advanced Settings dialog,
but we won't move home dir and other things: just rename the user in
/etc/passwd. Not sure our architecture allows for this easily.
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Triaged
--
Can not
Any trace of this bug in Karmic (or at least Jaunty)? I really can't
afford going through our code in Hardy to check where this was coming
from, we have already enough bugs to tackle in recent versions. The
trace upstream is too old, I'll have to close the report there without
more information.
Sorry, it's been a long time since you reported this bug. Sadly, we need
more information to work on it. The chances are low we can actually do
anything about it, since it's kind of late to get the details... :-(
First, did it happen after you had changed user settings via
Development version upstream has a GConf option to show root, which
means its hidden by default.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Fix Committed
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Triaged
Thanks for your report. Could you report each problem separately?
There's absolutely no chance that a developer will try to fix all those
bugs at once, you're discouraging people from reading your report. And
feature requests such as please write a GUI for XXX are completely
useless: we know this
Thanks for your report. I'm not able to reproduce your problem. Can you
confirm it still exists in Karmic? Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
[users-admin] adding new
That's a problem with the installer that does not add the user to all
the privilege groups used in Ubuntu. Have a look at /etc/gnome-system-
tools/profiles for a list of them.
** Package changed: gnome-system-tools (Ubuntu) = user-setup (Ubuntu)
** Changed in: user-setup (Ubuntu)
Importance:
Fixed in Karmic AFAICS.
** Package changed: gnome-system-tools (Ubuntu) = language-selector
(Ubuntu)
** Changed in: language-selector (Ubuntu)
Importance: Undecided = Low
** Changed in: language-selector (Ubuntu)
Status: New = Fix Released
--
[intrepid][gnome-language-support]
** Package changed: gnome-system-tools (Ubuntu) = network-manager
(Ubuntu)
--
Network manager deletes eth1 default gw when eth0 has Static IP
https://bugs.launchpad.net/bugs/223575
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for your report. I think the problem you describe is an intended
feature: developers upstream have considered this option was not useful
for enough users, and it makes our control center more complex for
everyone.
Though, you can start 'gconf-editor' and tune the key
** Package changed: gnome-system-tools (Ubuntu) = human-theme (Ubuntu)
--
Bug in human-theme_0.18_all.deb prevents upgrade
https://bugs.launchpad.net/bugs/222330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Oh, sorry, your problem wasn't clear to me. I'm not very familiar with
gnome-network-properties, since it's not actually part of the gnome-
system-tools, as you originally reported it (I know, it's confusing...).
So the issue is that you are using different proxies for various
protocols, the
I'd avise you to report that upstream before you start working on it.
It's possible that the problem is known, maybe even already fixed.
Unfortunately, bugzilla.gnome.org is down for the week-end... Maybe it
would be worth waiting monday - that's up to you. Else, sure, you can
attach the patch
Thanks for your report. I don't think the problem you describe is a bug,
rather an intended feature. There's no Cancel button: you can't close it
without applying the changes you've performed, because they are applied
on the go. I don't see how this behavior could hurt anybody: you can
always
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
David: what's your problem exactly? You can set up a password for root
in Karmic too, it's just that PolicyKit won't allow you to enter the
root password to authenticate. I fail to see how upgrading from
Yeah, the certificate was also in the same dir. That can hardly affect
importing of settings, though.
I don't think bgo#484315 is really related since I'm able to connect to
my VPN when I enter the settings manually into nm-connection-editor.
(And, sorry, I could have reported it upstream myself
Development version 2.29.1 contains the fix for the GID is 0 on start
problem, and also prevents you from choosing already used GIDs when
creating/editing groups.
** Changed in: gst
Status: Fix Committed = Fix Released
--
[users-admin] Group Properties dialog sets GID to 0 on first
Hm, silly: the latter is actually not in 2.29.1, but will be in the next
release. Anyway, that's for Lucid.
--
[users-admin] Group Properties dialog sets GID to 0 on first launch
https://bugs.launchpad.net/bugs/475974
You received this bug notification because you are a member of Ubuntu
Bugs,
This is now fixed upstream. Since deluser does not remove active users,
we simply refuse to delete them, showing a dialog: John Doe is
currently using this computer. Please ensure the user has logged out
before deleting this account.
Feel free to suggest a better formulation if you find one...
This is now fixed upstream, will be included in 2.29.2.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Fix Committed
--
users-admin fakes adding groups with existing gid
https://bugs.launchpad.net/bugs/491434
You received this bug
Public bug reported:
Binary package hint: ecryptfs-utils
This occurs when I try mounting manually my Private dir, maybe because the
passphrase is wrong:
$ keyctl clear @u
$ mount.ecryptfs ~/.Private/ /mnt/
Unable to find a list of options to parse, defaulting to interactive mount
Passphrase:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36618868/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/36618869/XsessionErrors.txt
--
mount.ecryptfs fails with error [-22] Invalid argument
https://bugs.launchpad.net/bugs/494404
I'm seeing the same kind of error in my dmesg here, with ecryptfs-utils
81-0ubuntu3 in Karmic. If you need debugging, please just ask.
** Changed in: ecryptfs-utils (Ubuntu)
Status: New = Confirmed
** Summary changed:
- Weird mount behvaiour giving Input/output error
+ Weird mount
Public bug reported:
Binary package hint: ecryptfs-utils
Another stupid use case: if you insert a key in the keyring using the
signature from ~/.ecryptfs/Private.sig as description, and something
wrong as the passprase, you don't get a meaningful message saying that
the passphrase is not the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36619063/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/36619064/XsessionErrors.txt
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided = Low
--
mount.ecryptfs_private
The version mismatch does not come from the kernel 2.6.32, I've just
reproduce it with the official 2.6.31-15-generic.
** Description changed:
Binary package hint: ecryptfs-utils
Another stupid use case: if you insert a key in the keyring using the
signature from ~/.ecryptfs/Private.sig
That won't happen, as explained by Chris in the previous comment. It's
far too late now, that will be for Lucid.
--
System Administration Services (services-admin) missing (Karmic)
https://bugs.launchpad.net/bugs/437905
You received this bug notification because you are a member of Ubuntu
Bugs,
Are people actually watching liboobs development?! ;-)
I've tried using before, but I was getting strange results because when
converting the constant value to signed int, something was going wrong and I
was getting -GMAX_INT32. I've tried again with your solution, and that does not
work
*** This bug is a duplicate of bug 490093 ***
https://bugs.launchpad.net/bugs/490093
Yeah, that was a little hard to find, but that's actually bug 490093,
which was spotted recently. The problem is that we're starting another
tool (about-me) to change the password, and that when you have
** Changed in: system-tools-backends (Ubuntu)
Status: Confirmed = Triaged
--
ecryptfs Private directory not mounted after changing password in users-admin
https://bugs.launchpad.net/bugs/307019
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hmm... Charlie, I did not notice your step:
3. enter sudo passwd expiry USER1
Is there a specific reason why you didn't use the standard 'passwd' command?
Could you post the log when using it? Don't even use 'sudo passwd', as it
doesn't work the same way. Does it work then?
Anyway, the
That doesn't work because you're passing the '-e' option, which means:
mark the password for expiration to force the user changing it on next
login. That operation requires admin rights. BUT please simply use
'passwd', without anything else.
(This is the best way of changing passwords in the
That's not a workaround, that's the normal procedure. Why would you use
'passwd -e' in the first place, if you want ot change your own password?
The only bug I can see here is that PolicyKit should allow users to
authenticate even if their password is marked for expiration until they
log change
** Bug watch added: freedesktop.org Bugzilla #25461
https://bugs.freedesktop.org/show_bug.cgi?id=25461
** Also affects: policykit via
https://bugs.freedesktop.org/show_bug.cgi?id=25461
Importance: Unknown
Status: Unknown
--
Changing your password does not allow admin
OK, I've just committed a fix that allows IDs to be handled correctly as
long as they don't go beyond G_MAXINT32 when the system supports it,
which means on Ubuntu you can go up to 2,147,483,647. I guess that's
enough for most people, but I'll see if we can guarantee we support the
full range for
Please don't bother installing Jaunty - if that's failing in Karmic,
that's enough for me. So to sum up, it seems that both PolicyKit and
gksu authentications fail. Does a simple sudo echo test works? I guess
not, but I'd like to be sure. A log that you could also post here is
/var/log/auth.log
I think the wrong behavior on failure was fixed, but the real support
for authentication has still not be committed. That's another bug
report, I guess it will go into Lucid.
** Bug watch added: GNOME Bug Tracker #553690
https://bugzilla.gnome.org/show_bug.cgi?id=553690
** Changed in: gtk
** Bug watch added: GNOME Bug Tracker #602110
https://bugzilla.gnome.org/show_bug.cgi?id=602110
** Also affects: gst via
https://bugzilla.gnome.org/show_bug.cgi?id=602110
Importance: Unknown
Status: Unknown
--
No easy way to make passwordless account
Thanks for the report, I agree the present situation is not optimal. But
don' t believe we wan't to fix this because password-less accounts are
unsecure, and we don't want to encourage users to work as in Windows. If
you want to perform administrative tasks, having a password is
essential.
OTOH,
** Changed in: gdm (Ubuntu)
Status: Confirmed = Triaged
--
Update PAM policy to allow password-less logins set up via users-admin
https://bugs.launchpad.net/bugs/393854
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
So thanks for providing the details now. This bug was not Triaged, it
was merely Confirmed. Sure, you had in mind the details, but nobody else
did. So, what was not mentioned in the report or the comments is:
changing your password does not allow you to authenticate via sudo.
You're really not
** This bug is no longer a duplicate of bug 315002
Changing your password does not take effect before session is restarted
--
Administer the system for new user requires reboot
https://bugs.launchpad.net/bugs/418337
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry, it was not clear to me whether your report was a duplicate or
not, partly because I didn't have much information about the other
report. So yours is about the fact that new administrator users cannot
authenticate until the computer is rebooted. That may well come from the
same problem as
Do you have any idea of were this problem comes from? Are you able to
reproduce it in Karmic? I'm not able to reproduce the problem here, so
I'd need somebody to answer these questions. In particular, whether this
also happens when changing password using 'passwd', rather than using
users-admin.
Again... Tricky issue. Considering the precise bug you found, it comes
from the fact that the max [GU]ID was statically defined as 65,535. I'll
fix that easily, but I lack a generic way of detecting the actual system
maximum for gid_t. I guess I've found a hack that will work, though.
That will be
That's a bug in OpenOffice, there's a fix committed upstream.
** Bug watch added: OpenOffice.org Issue Tracker #106833
http://qa.openoffice.org/issues/show_bug.cgi?id=106833
** Changed in: openoffice
Status: Invalid = Unknown
** Changed in: openoffice
Remote watch: OpenOffice.org
Yeah, that's bug 484559. But does changing your password from the
console using 'passwd' bring the same bug as the present report
describes? If that's the case, that's a bug in PAM or sudo, and we
should move it if we want it to be fixed some day.
--
Changing your password does not take effect
I think the wrong behavior on failure was fixed, but the real support
for authentication has still not be committed. That's another bug
report, I guess it will go into Lucid.
** Bug watch added: GNOME Bug Tracker #553690
https://bugzilla.gnome.org/show_bug.cgi?id=553690
** Changed in: gtk
If you are both experiencing this problem, we can resume debugging then. Could
you post the output of
sudo /usr/sbin/console-kit-daemon
here?
** Changed in: consolekit (Ubuntu)
Importance: Undecided = Medium
** Changed in: consolekit (Ubuntu)
Status: Invalid = Incomplete
--
D-BUS
I guess you'd need to kill the existing daemon if it exists:
sudo killall /usr/sbin/console-kit-daemon
But if it's already present, D-Bus wouldn't need to start it...
--
D-BUS activation fails to start console-kit-daemon with error: Success
https://bugs.launchpad.net/bugs/475503
You received
Mmm... Those warnings are really different from those of the original
report. Why do you think you're experiencing the same problem? It's
always good to avoid dealing with different issues on the same report.
And BTW, I've skipped your question form the previous comment: running
via SSH or VNC
Sadly gdb doesn't seem to find the source file, which does not allow us
to get details about the crash. From what I see in the code, we could
crash if libhal returns an array without telling us its real size. We
could check that the code in libhal is not buggy in that regard, but
anyway HAL is now
OK, I've finally found http://bugs.gentoo.org/278760 which explains that
libhal returns NULL when no devices are found, not even setting the
number of devices to 0. So we should check that before trying to add
them to our internal list.
I don't know why shares-admin needs the list of network
Here's a patch that you can apply against the liboobs package if you
want to check that it works. It seems to work here, but I never get the
crash, even if the error was set.
** Package changed: gnome-system-tools (Ubuntu) = liboobs (Ubuntu)
** Changed in: liboobs (Ubuntu)
Status: Triaged
1101 - 1200 of 1774 matches
Mail list logo
