** Visibility changed to: Public
--
desktop icons can be clicked when screensaver has screen locked
https://bugs.launchpad.net/bugs/661987
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs mail
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for reporting this issue, but I can't seem to reproduce it.
Could you please give detailed steps on how to reproduce this issue?
Thanks.
** Visibility changed to: Public
** Package changed: yelp (Ubuntu) => pam (Ubuntu)
** Changed in: pam (Ubuntu)
Status: New => Incomplete
--
L
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Do you mean if you type in your password, don't hit enter, and then
suspend?
** Changed in: gdm (Ubuntu)
Status: New => Incomplete
--
login screen should be reset after resume from suspend
https://bugs.launchpad.net/bugs/669391
You received this bug notification because you are a member
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided => Low
--
desktop icons can be clicked when screensaver has screen locked
https://bugs.launchpad.net/bugs/661987
You received this bug notification because
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
** Changed in: gdm (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gdm (Ubuntu)
Status: Triaged => Confirmed
--
gdm user switcher allows desktop preview w/o passwd
https://bugs.launchpad.net/bugs/618517
You received
This was fixed in Maverick. If you still get this issue, it's a
different bug.
When you're logged in, what process is managing the SSH keyring? To find
out, open a terminal, and type: lsof $SSH_AUTH_SOCK and paste the
results here.
--
gnome-keyring doesn't unlock ssh key
https://bugs.launchpad.n
My apologies, I was sure this was resolved, but I just tested in a fresh
VM, and the problem still exists in an up to date maverick. Please
disregard my comment #22.
--
gnome-keyring doesn't unlock ssh key
https://bugs.launchpad.net/bugs/631980
You received this bug notification because you are a
This was caused by an incorrect patch to attempt to fix gnome bug
#581032, which has since been reverted in evolution trunk and 2.32.
See:
http://git.gnome.org/browse/evolution/commit/?id=723528e407bca6f2aa26461e6f8bcc7de32b056d
** Also affects: evolution (Ubuntu Lucid)
Importance: Undecided
** Changed in: gnome-keyring (Ubuntu Maverick)
Assignee: (unassigned) => Marc Deslauriers (mdeslaur)
--
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 subsc
** Also affects: gnome-keyring (Ubuntu Natty)
Importance: Low
Status: Triaged
** Changed in: gnome-keyring (Ubuntu Natty)
Assignee: (unassigned) => Marc Deslauriers (mdeslaur)
--
gnome-keyring doesn't unlock ssh key
https://bugs.launchpad.net/bugs/631980
You received
** Summary changed:
- gnome-keyring doesn't unlock ssh key
+ [SRU] gnome-keyring doesn't unlock ssh key
--
[SRU] 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
SRU request for Maverick:
Impact: Gnome-keyring contains a regression from lucid that doesn't
allow users to unlock ssh keys upon login.
Bug has been addressed by adding a minimal patch containing two upstream
commits that fix this issue. See included debdiff.
How to test:
1- Create ssh key
2-
@Anquietas: This is the proper procedure to get a package into the
official updates. First a member of the ubuntu-sru team will push it to
the -proposed updates repository. After getting positive feedback in
this bug it will get pushed to the -updates repository and you will see
it appear in Update
I have tested the package in -proposed on maverick, and it works as
expected.
--
[SRU] 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 gnome-keyring in ubuntu.
-
The issue you are having is not the same. Please open a new bug with
backtrace information. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/119693
Title:
xchat-gnome 0.17 crashes on startup
Public bug reported:
gedit in oneiric-proposed breaks the snippets plugin:
Traceback (most recent call last):
File "/usr/lib/gedit/plugins/snippets/__init__.py", line 19, in
from windowactivatable import WindowActivatable
File "/usr/lib/gedit/plugins/snippets/windowactivatable.py", line
** Tags added: regression-proposed
** Also affects: gedit (Ubuntu Oneiric)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/877397
Title:
g
The version is proposed completely breaks the snippets plugin.
See bug 877397
NACK.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bug
Possibly related:
http://git.gnome.org/browse/pygobject/commit/?id=0f1eb9fa0e7aa5e7c22dabc709c0dfb469e404f1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/877397
Title:
gedit in -pr
This is caused by a mistake in the 49_fix_suspend_media_key.patch patch.
The gnome-settings-daemon package currently in -proposed should fix the
issue.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a me
Could someone please try the gnome-settings-daemon package in -proposed
and comment here if it is now fixed?
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
** Visibility changed to: Public
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/879301
Title:
HTML injection in nicknames
To manage notifications
With the pygobject in -proposed, gedit works fine. Marking verification-
done.
** Tags removed: verification-failed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launch
I just testing the update in -proposed, and it fixes the issue with gedit in
-proposed.
Marking verification-done
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to p
Reopening this bug as upstream actually fixed it...
** Changed in: evolution (Ubuntu)
Status: Invalid => Confirmed
** Changed in: evolution (Ubuntu Oneiric)
Status: Invalid => Confirmed
** Bug watch added: GNOME Bug Tracker #660870
https://bugzilla.gnome.org/show_bug.cgi?id=6608
>From upstream bug:
Created commit 7f26baf in eds master (3.3.1+)
Created commit ee4574f in eds gnome-3-2 (3.2.2+)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/846550
Title:
A
Maybe related?
http://git.gnome.org/browse/evolution/commit/?id=d4571114e8b8949922213ac23825075880e59231
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/829351
Title:
Misspelled
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/529696
Title:
[SRU] brasero can't copy audio cd (useless error message)
** Also affects: gtk+2.0 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: gtk+2.0 (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: gtk+2.0 (Ubuntu Lucid)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ub
Debian's gtk+2.0 (2.20.1-2) contains the following patches:
+ 030_gtkscake_redraw.patch: correctly redraw GtkScales.
+ 031_papersize_usletter.patch: update list of countries using US
Letter paper format.
+ 032_offscreenwindow_dnd.patch: fix crasher with offscreen windows.
SRU Request:
Impact: Current lucid users have an issue with the GTK file chooser
selecting the wrong file when the sort order is changed, or when files
get added to the tree. This may lead to the wrong file being selected.
Development fix: This issue affects 2.20, and was resolved in 2.22. Only
L
Caused by this commit:
http://git.gnome.org/browse/gconf/commit/?id=d7917514549f48297bc0032a7e2b54bfb17f7495
The assert probably shouldn't be there...
** Bug watch added: GNOME Bug Tracker #662991
https://bugzilla.gnome.org/show_bug.cgi?id=662991
** Also affects: gconf via
https://bugzill
Please describe how you are suspending the laptop. Is it suspending by
itself? Are you closing the lid? Are you using the indicator to trigger
the suspend? Does the issue occur when you do any of those three, or is
one in particular causing it?
--
You received this bug notification because you ar
Could you also run the following command and attach the resulting file?
Thanks
gsettings list-recursively org.gnome.settings-daemon.plugins.power >
settings.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubun
The regression was fixed in 3.2.3...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/882525
Title:
gconfd-2 crashed with SIGABRT in __kernel_vsyscall()
To manage notifications about
The regression was fixed in 3.2.3. The package in proposed needs to be
updated.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/848198
Title:
Sporadic gconf error messages
To manage
Could you perform the following commands, and paste the results here,
please?
ls -l /etc/shadow
ls -l /sbin/unix_chkpwd
** Changed in: lightdm
Status: New => Invalid
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
gnome-screensaver uses gsettings now, not gconf.
You can change the lock screen settings in gnome-control-center. Is that not
working for you?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.l
@Martin:
Yes, but you also mentioned your laptop doesn't resume at all...so now
I'm confused...do you see this issue when you resume from suspend, or
when you unlock your screen?
Also, could you please provide the settings file I asked for, thanks.
--
You received this bug notification because
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/884764
Title:
gnome-screensaver locks screen even i
Could you please give detailed steps on how to reproduce this issue?
Thanks
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https:
Does this happen if you use Unity?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/880025
Title:
If you use Unity, do you still have this problem?
How about if you use the classic desktop, but without compiz?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
This is actually an issue with how file-roller calls external
applications.
** Package changed: p7zip (Ubuntu) => file-roller (Ubuntu)
** Changed in: file-roller (Ubuntu)
Status: New => Confirmed
** Changed in: file-roller (Ubuntu)
Importance: Undecided => Low
--
You received this bu
Which screensaver are you using?
I'm setting this as gnome-screensaver, please indicate if that's not the
case.
Thanks.
** Visibility changed to: Public
** Visibility changed to: Public
** Package changed: ubuntu => gnome-screensaver (Ubuntu)
** Changed in: gnome-screensaver (Ubuntu)
S
Did you disable gnome-screensaver in any way, including disabling the
lock screen functionality?
** Package changed: shadow (Ubuntu) => gnome-screensaver (Ubuntu)
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a m
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Original reporter apparently wasn't using file-roller. Changed back to
p7zip.
Please add detailed steps on how to reproduce this issue.
** Package changed: file-roller (Ubuntu) => p7zip (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Public bug reported:
Since Ubuntu uses AppArmor by default, the nautilus properties panel
shouldn't show the SELinux context information. This is technical
information that is useless to the user on a default Ubuntu
installation.
We could simply remove selinux from the debian/control file, which
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/886983
Title:
properties panel should not show SELinux context information
To manage notifications about this bug go to:
https://bug
If your desktop environment uses xscreensaver, you should simply not
have the gnome-screensaver package installed. If the gnome-screensaver
package isn't installed, the dbus service file isn't there.
** Package changed: gnome-screensaver (Ubuntu) => lxde-common (Ubuntu)
--
You received this bug
This needs to be fixed upstream. Could you please file a bug against
gnome-screensaver et bugzilla.gnome.org and link the bug here. Thanks.
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided => Low
--
You
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
https://bugs.launchpad.net/bugs/712864
Title:
brasero crashed with SIGSEGV
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.
Public bug reported:
Binary package hint: devhelp
When the devhelp gedit plugin is enabled, it prints a bunch of error
messages on the console when gedit is used:
mdeslaur@mdlinux:~$ gedit
Error in sys.excepthook:
RuntimeError
Original exception was:
RuntimeError
Error in sys.excepthook:
Runtim
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to devhelp in ubuntu.
https://bugs.launchpad.net/bugs/728007
Title:
devhelp gedit plugin prints errors in console
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists
Actually, it would appear other python plugins are printing the errors
also, so reassigning to gedit.
** Package changed: devhelp (Ubuntu) => gedit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in ubuntu.
https://bugs
** Summary changed:
- devhelp gedit plugin prints errors in console
+ python gedit plugins print errors in console
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in ubuntu.
https://bugs.launchpad.net/bugs/728007
Title:
pytho
** Summary changed:
- unlock screen -dialog comes up twice
+ [SRU] unlock screen -dialog comes up twice
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
https://bugs.launchpad.net/bugs/556255
Title:
[SRU
SRU Request:
Impact: On Lucid and Maverick, gnome-screensaver has a race condition
that makes it start twice from time to time, resulting in a poor user
experience.
The bug has been addressed by adding a patch that makes sure gnome-
screensaver can only be run once, and that when spawned as a Dbu
** Patch added: "lucid debdiff for SRU"
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/556255/+attachment/1892883/+files/gnome-screensaver_2.30.0-0ubuntu2.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Patch added: "Maverick debdiff for SRU"
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/556255/+attachment/1892884/+files/gnome-screensaver_2.30.0-1ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion
** Visibility changed t
Thanks for reporting this issue.
This is the way Unix permissions work, and is to be expected. The first
user you have created in both installations have the same User ID (uid).
They are considered the same user permissions-wise.
If you want to prevent one installation from seeing data in the oth
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion
** Visibility changed t
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
I am seeing this with the "postfix" user on a freshly installed natty.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/696038
Title:
system user appears in login list of users
--
desk
Actually, I think it is the 16-capture-before-unmap.patch patch. If I
set the /apps/metacity/general/capture_before_unmap gconf key to false,
I can't seem to reproduce the issue anymore.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/740387
Title:
graphical corruption with multip
This is the problem:
Mar 25 10:24:29 ub3 unix_chkpwd[4005]: check pass; user unknown
What are the permissions on your /etc/shadow file? (Do a ls -l
/etc/shadow)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubu
** Changed in: nautilus (Ubuntu Lucid)
Status: New => Incomplete
** Changed in: nautilus (Ubuntu Lucid)
Status: Incomplete => Confirmed
** Changed in: nautilus (Ubuntu Maverick)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubunt
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/742321
Title:
gnome-screensaver does not unlock,
Does this still happen with version 2.30.0-1ubuntu1.1 that was pushed to
Maverick updates?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
Does this still happen with version 2.30.0-1ubuntu1.1 that was pushed to
Maverick updates?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
Do you happen to have menus open when the screensaver doesn't come up?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bug
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/735172
Title:
gnome-keyring-daem
801 - 900 of 1524 matches
Mail list logo
