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.
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
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
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
** 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
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.
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
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
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:
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
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
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
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
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
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.
@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
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.
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
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 bug
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)
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
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
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
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
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
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
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:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This is not a bug, but rather expected behavior:
https://wiki.ubuntu.com/SecurityTeam/FAQ#gnome-keyring
Please feel free to report any other bugs you may find.
** Visibility changed to: Public
** This bug is no
I am running the oneiric-proposed package right now. Contacts list is
appearing fine, with no apparent regressions.
** Tags removed: verification-needed
** Tags added: verification-complete
** Tags removed: verification-complete
** Tags added: verification-done
--
You received this bug
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
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
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
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
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
This is a design flaw in GTK. This needs to be fixed upstream.
--
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/49579
Title:
screen doesn't lock when panel menu is open
This is a limitation in how X handles keyboard grabbing. Essentially,
when GTK opens a menu, it needs to grab keyboard and mouse. When that
happens, gnome-screensaver cannot exclusively grab the keyboard.
There are two ways to fix this: 1- Redesign how X handles keyboard
grabbing, and probably
** Changed in: libimobiledevice (Ubuntu)
Assignee: Josh Williams (ijoshmobile) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/793616
Title:
lucid and
** Attachment added: Screenshot at 2011-12-11 22:22:21.png
https://bugs.launchpad.net/bugs/903025/+attachment/2628891/+files/Screenshot%20at%202011-12-11%2022%3A22%3A21.png
** Changed in: xchat-gnome (Ubuntu)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
--
You received this bug
-gnome (Ubuntu)
Importance: Undecided
Assignee: Marc Deslauriers (mdeslaur)
Status: New
** Tags: amd64 apport-bug oneiric running-unity
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https
** Bug watch added: GNOME Bug Tracker #666056
https://bugzilla.gnome.org/show_bug.cgi?id=666056
** Also affects: xchat-gnome via
https://bugzilla.gnome.org/show_bug.cgi?id=666056
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 848340 ***
https://bugs.launchpad.net/bugs/848340
** This bug has been marked a duplicate of bug 848340
Brasero can't select DVD drive to burn image
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 848340 ***
https://bugs.launchpad.net/bugs/848340
** This bug has been marked a duplicate of bug 848340
Brasero can't select DVD drive to burn image
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 848340 ***
https://bugs.launchpad.net/bugs/848340
** This bug has been marked a duplicate of bug 848340
Brasero can't select DVD drive to burn image
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 848340 ***
https://bugs.launchpad.net/bugs/848340
** This bug has been marked a duplicate of bug 848340
Brasero can't select DVD drive to burn image
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 848340 ***
https://bugs.launchpad.net/bugs/848340
** This bug has been marked a duplicate of bug 848340
Brasero can't select DVD drive to burn image
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Did you restart your session after updating? In any case, please open a
new bug, as it is working fine for me so this bug is closed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
*** This bug is a duplicate of bug 872701 ***
https://bugs.launchpad.net/bugs/872701
** This bug has been marked a duplicate of bug 872701
Keyboard layout doesn't change
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/959874
Title:
gnome-settings-daemon crashed with SIGSEGV in
This could be a compiz layering issue
--
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/958353
Title:
Locked screen reveals far too much information about the user and his
@dfoxpro: which screensaver are you using that isn't working?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/55575
Title:
Lock Screen/Switch User can't use
To manage notifications about this bug
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** 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
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** 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
** This bug is no longer flagged as a security vulnerability
** 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-control-center in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This is not a bug, but rather expected behavior:
https://wiki.ubuntu.com/SecurityTeam/FAQ#Rescue_Mode
Please feel free to report any other bugs you may find.
** Visibility changed to: Public
** This bug is no
We should change the default sysrq to something like debian did in their
2.6.32-9 kernel:
* Restrict access to sensitive SysRq keys by default.
Reassigning to kernel.
** Visibility changed to: Public
** Package changed: gnome-screensaver (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
*** This bug is a duplicate of bug 831020 ***
https://bugs.launchpad.net/bugs/831020
** This bug is no longer a duplicate of bug 940936
nautilus crashed with SIGSEGV in nautilus_file_invalidate_attributes()
** This bug has been marked a duplicate of bug 831020
nautilus crashes with http
*** This bug is a duplicate of bug 831020 ***
https://bugs.launchpad.net/bugs/831020
** This bug has been marked a duplicate of bug 831020
nautilus crashes with http protocol
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This still happens in 12.04.
--
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/831020
Title:
nautilus crashes with http protocol
To manage notifications about this bug go to:
Thanks for reporting this issue.
Please describe the exact steps necessary to reproduce your 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
Those settings look okay.
When the screensaver doesn't come up, is the gnome-screensaver process
still running? Can you start it by hitting Ctrl-Alt-L?
When this happens, do you have a context menu open, or an application
such as VNC or Virtualbox?
** Changed in: gnome-screensaver (Ubuntu)
What do you mean by the content of the virtual console changed?
--
the screen saver never starts
https://bugs.launchpad.net/bugs/516094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
Could you please try killing gnome-screensaver and running:
gnome-screensaver --debug ~/gss-debug.txt 21
Wait 10 minutes withough moving keyboard or mouse and attach the log
file here.
Thanks.
--
the screen saver never starts
https://bugs.launchpad.net/bugs/516094
You received this bug
I am getting this also in an up-to-date amd64 lucid in a kvm VM.
Attached is my xtrace log.
** Attachment added: xtrace log
http://launchpadlibrarian.net/40255454/xtrace-mdeslaur.log
** Changed in: gnome-screensaver (Ubuntu)
Status: Invalid = Confirmed
--
gnome-screensaver crashed
Oh! That's really cool!
--
Please ignore this report :)
https://bugs.launchpad.net/bugs/533561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
@Chris: I can reproduce this at will in a kvm. Lucid's gnome-screensaver
doesn't work _at all_ in kvm, but previous released worked fine.
Attached is the result of running gnome-screensaver --debug --no-daemon
and running gnome-screensaver-command -a in a second terminal.
--
gnome-screensaver
** Attachment added: Result of gnome-screensaver --debug
http://launchpadlibrarian.net/40392016/gss-debug.txt
--
gnome-screensaver crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/503961
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Robert: As I expected, adding the xorg.conf you specified didn't change
anything as it was already being detected as cirrus.
I tried using the vmvga driver instead of the cirrus driver, and that
made gnome-screensaver work properly. It would appear that the crash is
related to some capability of
oops...I attached the wrong log file, here's the right one.
** Attachment added: gnome-screensaver --debug log
http://launchpadlibrarian.net/40392592/gss-log.txt
--
gnome-screensaver crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/503961
You received this bug notification
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
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
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
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
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
nautilus mounts partitions without authentication
https://bugs.launchpad.net/bugs/534837
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
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
Bryce, what's the contents of your ~/.config/user-dirs.dirs file?
--
Pictures folder: --location requires absolute path
https://bugs.launchpad.net/bugs/393727
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
You can also use --location=$HOME/Pictures as a workaround, but I'm
curious why your pictures directory isn't picked up automatically.
** Changed in: gnome-screensaver (Ubuntu Lucid)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
** Changed in: gnome-screensaver (Ubuntu Lucid
So, you actually have three issues?
1- Default pictures directory as set by XDG_PICTURES_DIR isn't being used by
the screensaver
2- screensaver's --location should accept ~/Pictures
3- screensaver doesn't work with pictures directory specified on an NFS mount
point
--
Pictures folder:
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
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
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
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
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
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
*** This bug is a duplicate of bug 31979 ***
https://bugs.launchpad.net/bugs/31979
** This bug has been marked a duplicate of bug 31979
Screensaver should allow selective random
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Justin: could you please file a new bug for that particular issue. This
bug, along with the original issue, has been closed.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
Thanks for reporting this issue.
What desktop environment are you using?
Could you please do a ps aux | grep screensaver when you manage to have two
running, and paste the result here?
Thanks.
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Incomplete
--
You received this bug
Also, what is the result of which gnome-screensaver-command, and does
running gnome-screensaver-commend --lock lock your screen?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
After you restart your session, do you have two gnome-screensaver
processes running?
When you do have two screensavers, what is the output of ps aux | grep
dbus-daemon | grep -v grep
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Debdiff looks good, thanks!
SRU request:
Evince crashes when clicking on the blank document area during the short
interval between Evince's window opening, and before the document has
been loaded.
Steps to reproduce:
1. Find a PDF file (the larger the better, so that there's a greater time
801 - 900 of 1519 matches
Mail list logo