steubens: Are you still able to reproduce the bug on demande? Could you
give us precise instructions to reproduce it? Upstream developers would
need more informations to fix the bug.
--
evince crashed with SIGSEGV in clear_job_selection()
https://bugs.launchpad.net/bugs/651931
You received this
Indeed, thanks for these valuable details. When your bug is marked as
duplicate and you think you provided more information than the duplicate
report already has, please post them as a comment!
I've been able to reproduce the crash again, and I've let upstream
developers know how to do so, thus
Thanks for raising this issue, but as I understand it, the only right
way to solve this is to fix bug 104525. As a temporary improvement, we
can simply remove Stratum 1 (and possibly 3) from our list, but how many
servers would be left? We should definitely be using a custom NTP pool
and leave the
OK, thanks, this seems to be a real bug that has been solved upstream in
the master branch. Ryan Lortie pointed me to two commits that are likely
to be backported to 2.26 at some point, and then will possibly enter
Maverick.
These commits are from October 2 and 3, IDs are c84441 and 9211d2b.
**
Sorry, the command should have been 'sudo apt-get install --reinstall
libglib2.0-0'.
Your install media is not likely to be in cause here. More probably, the
fact that you're on PowerPC could trigger a bug elated to endianness. So
reinstalling won't help.
At any rate, the fact that Evince
QAMARDEEN YASIN MUHAMMAD: You don't experience the same problem, this is
not the right place to ask. You have problems with the 'sudo' command,
which you seem to have distrubed with manual changes. Please ask for
help on the forums.
--
users-admin Click to make changes button does nothing
Thanks. So this is weird, because all the needed schemas seem to be
present, and yet it doesn't find them. Could you try reinstalling GLib
by running 'apt-get install --reinstall libglib2.0-0' and see if
something changes?
Are you able to start Evince, the document viewer ('evince' command from
a
Do you get any problems with other programs too? Do you have the file
/usr/share/glib-2.0/schemas/org.gnome.system-tools.gschema.xml installed? What
does the following command say:
grep org.gnome.system-tools.users /usr/share/glib-2.0/schemas/gschemas.compiled
** Summary changed:
- Users and
Please don't assign yourself bugs unless you are currently working on
them. You can click on This bug affects me too at the top of the page
if you want to be counted.
** Changed in: adobe-flashplugin (Ubuntu)
Assignee: milehunter (blow-focus) = (unassigned)
** Changed in: chromium-browser
Hm, indeed, sorry. Next step would be to run the authentication agent
manualy after killing the one that is running, and see if it changes
something. If it doesn't, have a look at the messages it prints to the
console, and also to the messages printed by polkitd, which (IIRC)
should also say it
What you describe feels weird to me, especially the part about the
upgrade breaking things... Please run 'sudo killall
/usr/lib/policykit-1/polkitd sudo /usr/lib/policykit-1/polkitd',
retry to authenticate via users-admin from a local GDM session and a VNC
session, and paste the output here.
Authorization requires authentication but no agent is available.
This means you need to start
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 so that the
authentication dialog can be shown.
But this should be started automatically on login thanks to a desktop
file.Check that it
Maybe the problem come from the allocation, which looks far too wide:
child_allocation = {x = 183, y = 68, width = 160078656, height = 28}
** Visibility changed to: Public
** Changed in: nautilus (Ubuntu)
Status: New = Triaged
--
nautilus crashed with SIGSEGV in
** Description changed:
Binary package hint: gnome-system-tools
This problem appears to be new in Maverick.
Steps:
1. Run users-admin from within a VNC session using my primary user account
that is in the admin group.
2. Click on any button that requires authorization by
Have you tried without VNC, i.e. with a local GDM session?
If the patch doesn't apply, you can still edit by hand
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy
and replace allow_active with allow_any. If that's enough, then
that's a plain duplicate of bug 221363, which
OK, so according to upstream it's not a bug in PolicyKit, but in the
services that specify allow_active instead of allow_any. Of course,
it would be better if ConsoleKit detected remote sessions as active, but
there's no reason anyway why the system-tools-backends shouldn't be
available to
*** This bug is a duplicate of bug 668801 ***
https://bugs.launchpad.net/bugs/668801
** This bug has been marked a duplicate of private bug 668801
--
users-admin crashes due to right mouse click
https://bugs.launchpad.net/bugs/667151
You received this bug notification because you are a
Looks like a bug in the kernel.
** Package changed: gnome-system-tools (Ubuntu) = linux-meta (Ubuntu)
** Changed in: linux-meta (Ubuntu)
Importance: Undecided = Medium
--
SIOCSIFFLAGS: Cannot allocate memory
https://bugs.launchpad.net/bugs/667478
You received this bug notification because
No, using gksu is a deprecated method for a long time, instead programs
are now run as a normal user, and get admin rights using PolicyKit. In
Maverick, this is for example how updates-manager works.
You're not supposed to run 'gksu users-admin', and I really don't see
how you'd think of doing
Thanks for the report. Could you enable Apport and reproduce the crash,
and then attach the debugging information that was found here? Just run
'sudo service apport start force_start=1', reproduce the crash and
follow the instructions.
** Changed in: gnome-system-tools (Ubuntu)
Status: New
Interesting... Indeed, doesn't seem to be a duplicate of bug 659758,
which is only about newly created users (and about which I know the root
cause).
Please follow the instructions at :
https://wiki.ubuntu.com/DebuggingGnomeSystemTools#For%20Users%20[users-admin]
and attach the information here.
Sorry, but we don't support logging in as the root user. This is highly
unsecure and strongly discouraged. I'm not sure what may be happening,
but it's possible something like a D-Bus policy is blocking messages
from being sent to root. You may want to have a look at
/var/log/auth.log for such
Another question: please open two terminals, and:
- in the first one, run 'passwd', type your *old* password, hit RETURN, and let
the terminal in this state
- then, in the second one, try to change your password using 'passwd' the
normal way
Then, please copy/paste the output of the second
And how about my comment #11?
--
changing user password causes hang in users-admin
https://bugs.launchpad.net/bugs/661272
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs mailing list
Fix released before 10.04 at long time ago.
** Changed in: gdm (Ubuntu)
Status: Fix Committed = Fix Released
--
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
I bumped on the same crash, but sadly it doesn't seem to be
reproducible. I'm not sure it has anything to do with the document
itself, maybe with the fact that it was opened from the Web browser, or
something completely random...
--
evince crashed with SIGSEGV in clear_job_selection()
Teej: thanks for the trace, but that's not really what I need since I
know where the problem happens in the code (where it waits for a reply
from the 'passwd' program), but I need to know why it waits. (And BTW,
you'd need to install more debugging symbols packages to get a useful
trace.)
** Visibility changed to: Public
** Bug watch added: GNOME Bug Tracker #632352
https://bugzilla.gnome.org/show_bug.cgi?id=632352
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=632352
Importance: Unknown
Status: Unknown
** Changed in: gnome-keyring
Yes, the password did change that way and was left as the old one
What do you mean? I really don't understand this sentence as its two parts
sound antithetic to me.
My general idea is that users-admin hangs when 'passwd' fails with an
error message we don't handle. Which doesn't seem to be the
This happens when you're using GNOME shell. GKSu doesn't work well with
the Shell because it tries to lock the whole screen. It should use
PolicyKit to authenticate instead. There was a project to do so, but I'm
not sure what's its state today.
** Package changed: gnome-system-tools (Ubuntu) =
You didn't answer my other questions...
--
changing user password causes hang in users-admin
https://bugs.launchpad.net/bugs/661272
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs mailing
If it hung, it's likelly that the change wasn't performed. Could you
please run 'passwd' in a terminal, try to change your password that way,
and copy/paste the full output here? Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in:
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.
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
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:
*** 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:
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
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
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
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
*** 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)
*
*** 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:
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,
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! It was most likely a bug in GTK+/GLib which got fixed in the
development process.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Invalid
--
users-admin crashed with SIGFPE in g_hash_table_lookup()
https://bugs.launchpad.net/bugs/627178
You received this bug
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Triaged
--
[time-admin] Custom NTP servers are not saved when unchecked
https://bugs.launchpad.net/bugs/55582
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Not likely to be a bug in the gnome-system-tools anyway. Somebody trying
to debug this should tell us what /etc/resolv.conf contains before and
after the bug is triggered, and whether running a 'ping' on the address
of the DNS server works.
--
[network-admin] wireless card will not associate if
Problem is, in current Lucid you can't access the interfaces
configuration, since the tab is hidden. So it's hard to check...
--
PPP username/passwords that contain hashes get corrupted
https://bugs.launchpad.net/bugs/14824
You received this bug notification because you are a member of Ubuntu
rusivi1: I don't think it really makes sense to ask people to test
network-admin in Lucid, since (as I said) the Interfaces tab is not
present. Better leave these bugs open until 1) we get that tab back, or
2) we decide to keep it removed, and close all bugs without asking.
Thanks for going over
Yeah, there's no point in renaming a broken group - just get rid of it.
We've not found a valid case where people would like to be actually
members of this group.
--
Only one user gets sound with privilege Use audio devices
https://bugs.launchpad.net/bugs/433654
You received this bug
I've pushed a fix in upstream gnome-system-tools 2.31.92: if you don't
provide a non-empty password, the account will still be disabled and
appear as such, and password-less login won't be enabled. The solution
is a little hacky since there's no explanation of why password-less
login has no
Here's a branch with a fix. Actually, I may sound silly, but I realized
one interest of keeping the group visible, at least for Maverick: people
that have checked the box will need it to get out of the group. Else,
they would need to use the command line.
I've finally chosen Lock audio devices
** Branch linked: lp:~nalimilan/ubuntu/maverick/gnome-system-tools
/gnome-system-tools.fix-433654-2
--
Only one user gets sound with privilege Use audio devices
https://bugs.launchpad.net/bugs/433654
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Project changed: gnome-settings-daemon = gtk
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
desktop-bugs
Actually, that's not a bug in the tool, but in the online documentation:
the program that is described on the page you linked to is now started
using System-Administration-Date and Time. Right-clicking on the date
applet starts a different configuration tool.
I've fixed the online documentation,
** Visibility changed to: Public
** Bug watch added: GNOME Bug Tracker #629345
https://bugzilla.gnome.org/show_bug.cgi?id=629345
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=629345
Importance: Unknown
Status: Unknown
** Changed in: gvfs (Ubuntu)
** Visibility changed to: Public
** Bug watch added: GNOME Bug Tracker #629351
https://bugzilla.gnome.org/show_bug.cgi?id=629351
** Also affects: rhythmbox via
https://bugzilla.gnome.org/show_bug.cgi?id=629351
Importance: Unknown
Status: Unknown
** Changed in: rhythmbox (Ubuntu)
** Visibility changed to: Public
** Bug watch added: GNOME Bug Tracker #629352
https://bugzilla.gnome.org/show_bug.cgi?id=629352
** Also affects: rhythmbox via
https://bugzilla.gnome.org/show_bug.cgi?id=629352
Importance: Unknown
Status: Unknown
** Changed in: rhythmbox (Ubuntu)
Fixed upstream, should be released with next version (current is
0.13.1).
** Bug watch added: GNOME Bug Tracker #627050
https://bugzilla.gnome.org/show_bug.cgi?id=627050
** Changed in: rhythmbox
Remote watch: GNOME Bug Tracker #629351 = GNOME Bug Tracker #627050
--
rhythmbox-metadata
Yes, but that's not the question! ;-)
Please copy/paste this error message, as I need to know it to fix the
GUI.
--
Trying to set a short password in Users Settings shows no error, loops endlessly
https://bugs.launchpad.net/bugs/627385
You received this bug notification because you are a member
Chris: I've been using the workaround for some time with a few
users/machines, and I'm not aware of other issues it would introduce.
Anyway, as you said, Flash is so buggy without it that it could hardly
be worse.
--
Adobe Flash Player does not respond to mouse clicks [READ DESCRIPTION]
** Summary changed:
- user with no password and auto-login actually has an unknown password
+ Disabled accounts are still allowed password-less login via GDM
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnome-system-tools (Ubuntu)
Status:
Thanks for your report. Actually, the problem is not that this user has
an unknown password (you can check in /etc/passwd that it's empty). It's
that password-less login (Don't ask for password on login) takes
precedence over the fact that the account is disabled. And since
password-less login is
Mukesh: please don't reopen such an old bug, but file a new one if
needed.
In your case, though, I think there's no bug: Linux sets the hardware
clock to UTC time disregarding your time zone. Then, the time that is
displayed is adapted depending on the time zone you want. This is
necessary e.g.
** Bug watch added: GNOME Bug Tracker #628612
https://bugzilla.gnome.org/show_bug.cgi?id=628612
** Also affects: epiphany-browser via
https://bugzilla.gnome.org/show_bug.cgi?id=628612
Importance: Unknown
Status: Unknown
--
epiphany-browser assert failure: epiphany-browser:
csotomayor: Please don't change the bug status without reason.
** Changed in: gnome-system-tools (Ubuntu)
Status: Fix Committed = Fix Released
--
gnome-network-admin on UbuntuStudio doesnt allow to configure either wired
networks or wireless
https://bugs.launchpad.net/bugs/570828
You
flm: If you're not using Lubuntu, please file this as a new report. At
any rate, please follow the instructions I've given in all my comments
above, and provide us with this information. Thanks!
--
Polkit authentication fails in Lubuntu
https://bugs.launchpad.net/bugs/599050
You received this
Thanks for your report. I assume the problem happens when changing your
own password? If so, please try to change your password by starting a
terminal, and running the command 'passwd'. Follow instructions, enter
old and new password, and please copy/paste the result here. Note that
depending on
201 - 300 of 1345 matches
Mail list logo
