@Alex: could you provide a rationale for *why* it should ?
** Changed in: likewise-open (Ubuntu)
Status: New => Incomplete
--
gnome-screensaver should allow screen unlock even if account is locked out
https://bugs.launchpad.net/bugs/404321
You received this bug notification because you ar
** Bug watch added: Debian Bug tracker #536757
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536757
** Also affects: gvfs (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536757
Importance: Unknown
Status: Unknown
--
smb: Error while copying file, "Invalid argumen
Well, it's not "totally unusable" since you can still switch to another
user. And there should be other users available if you're under a domain
setup. The whole "account locking" AD feature is buggy, since every
large AD domain user knows they can easily lock out someone else's
account.
I guess i
*** This bug is a duplicate of bug 352921 ***
https://bugs.launchpad.net/bugs/352921
** This bug has been marked a duplicate of bug 352921
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading
response length from authentication socket.
--
ssh-add: "Error reading response
Closing as fix released since original poster confirmed it fixed in
9.04, and Stephen opened a separate bug to track his issue.
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: samba (Ubuntu)
Status: New => Fix Released
--
Nautilus failes connecting t
Fixed in Jaunty (as of 0.11.99.1)
** Changed in: rhythmbox (Ubuntu)
Status: Triaged => Fix Released
--
Rhythmbox can not use smb:// as library location
https://bugs.launchpad.net/bugs/273294
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Tags added: regression-potential
--
ssh-agent stops responding
https://bugs.launchpad.net/bugs/352154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Not an ssh bug, but rather a seahorse or gnome-keyring regression,
opening related tasks and marking regression-potential.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
** Also affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-keyring (
I've been reproducing that as well. I'll try to get you a more complete
backtrace of that SIGABRT.
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from authentication socket.
https://bugs.launchpad.net/bugs/352921
You received this bug notification becaus
I could not making crash using 2.26.0-0ubuntu5 while it was easy to
reproduce with 2.26.0-0ubuntu4. Jamin, Aaron: did you reproduce it with
the -0ubuntu5 version ?
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from authentication socket.
https://bugs.la
Yes, it's normal behavior for mv to overwrite without warning in this case. Use
"mv -i" to prompt on overwrite.
I'd say it's a bug in Nautilus, if any. Probably linked to bug 316653.
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
Renaming a file through Samba
Marking Samba as invalid as smbclient delivers expected behavior, please
reopen if you can point to a specific bug/missingfeature in Samba.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
Renaming a file through Samba overwrites existing one
https://bugs.launchpad.net/bugs/382117
smbclient uses FTP-like commands like ls / put / get
Please see
http://manpages.ubuntu.com/manpages/jaunty/en/man1/smbclient.1.html#toptoc4
--
Renaming a file through Samba overwrites existing one
https://bugs.launchpad.net/bugs/382117
You received this bug notification because you are a member
I agree it doesn't look very good when you log in.
Apparently StartupNotify=true has been there for some time (since
2.14.3-3), and is set explicitely so that a busy cursor is displayed...
What seems new in recent upgrades is that the "Starting Power Manager"
taskbar item remains active for quite
xset -dpms doesn't fix it here.
unsetting "undirect fullscreen windows" fixes it.
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
deskto
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Compiz inhibits screensaver or
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
does not start in intrepid
http
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Gnome-screensaver does not stay on
https://bugs.launchpad.net/bugs/159263
You received this bug notification because you
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
gnome-screensaver never start f
Those who can, please test the compiz packages from:
https://launchpad.net/~tcarrez/+archive
and report success/failure. You no longer should have "Unredirect Fullscreen
Windows" disabled since the purpose of this workaround is to disable it for
gnome-screensaver only. Don't forget to log out/ lo
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
screensavers broken in intrepid with compiz
https://bugs.launchpad.net/bugs/271229
You received this bug notification bec
Proposed fix is to reenable an updated version of the
030_fix_screensaver patch that disables "Unredirect Fullscreen Windows"
for gnome-screensaver only.
I will push this into my PPA so that you can all test this and report if
it fixes it without any dirty side-effect :)
compiz (1:0.7.8-0ubuntu4)
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 271229
screensavers broken in intrepid with compiz
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Screensaver Isn't Work
This might be related or just another bug :
If I select the option "Lock screen while screensaver is on" in
gnome-screensaver, then the screensaver starts up correctly. However when I hit
some keys or move the mouse, the screensaver just restarts... I need to kill it
from SSH to recover my keybo
This is linked to the keyboard choice...
To fix it (on both my workstations) I opened my keyboard preferences,
clicked "+" to select a new layout, selected the SAME layout I used to
have. Then it appears twice on the list. Select the newly-added one as
default and make it the system default. You c
Forget my Lock screen issue (comment 29), it is unrelated (see bug
275957).
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
Ted:
I can confirm the version in your PPA fixes this.
This is a cosmetic fix but definitely one that should make it to release :)
** Changed in: gnome-power-manager (Ubuntu)
Target: None => ubuntu-8.10
--
"Starting Power Manager" shouldn't show up on taskbar during login
https://bugs.lau
Michael:
Confirmed your PPA packages fix the issue for me too. Good job :)
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 275957 ***
https://bugs.launchpad.net/bugs/275957
** This bug has been marked a duplicate of bug 275957
gnome-screensaver-dialog crashed with SIGSEGV in g_type_create_instance()
--
gnome-screensaver segfaults at login screen instead of giving back login
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver idle fails after resume
https://bugs.launchpad.net/bugs/185554
You received this bug notification because you are a member of Ubuntu
Desktop
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver does not reliably allow login after suspend
https://bugs.launchpad.net/bugs/99647
You received this bug notification because you are a member
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver causes my laptop to hang on resume from memory-suspend
https://bugs.launchpad.net/bugs/58963
You received this bug notification because you a
For me it fixes the bug from the description : "the screen starts to
fade, but then immediately returns to the desktop instead of starting
the screensaver".
(Note that I still have just a blank screen rather than a specific
screensaver if running on battery, but this is not what this bug is
about,
** Summary changed:
- gnome-screensaver-dialog crashed with SIGSEGV in g_type_create_instance()
+ Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
--
Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
https://bugs.launchpad.net/bugs/275957
You rece
I can reproduce it on a clean RC install too :
- Install Ubuntu, pick "France - France alternative" as the keyboard.
- When Ubuntu is installed, try "Lock screen" from FUSA
- Try to unlock...
Will see if I can reproduce on a default English install.
** Changed in: gnome-screensaver (Ubuntu)
Im
This seems to be specific to the "France - France alternative" keyboard,
doe snot affect the default US keyboard or the "France - France"
keyboard...
Unfortunately, the "France - France alternative" keyboard is the default for
French users :)
People that are/were affected by this bug: please tell
The strange thing is that adding a "France alternative" layout (and
removing the "France alternative" set by the installer) in the
Preferences > Keyboard > Layouts workarounds the bug...
--
Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
https://bugs.launchpad.net/bugs/2
Should be fixed at the source of the crash (libgnomekbd).
** Also affects: libgnomekbd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libgnomekbd (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
** Changed in: gnome-screensaver (Ubuntu)
Stat
Removing likewise-open: if GDM implementation shows that something also
needs to be done on likewise-open side, please reopen the task.
** Changed in: likewise-open (Ubuntu)
Importance: Wishlist => Undecided
Status: Triaged => Invalid
--
GDM support for domain choice
https://bugs.launc
** Summary changed:
- Rhythmbox can not use samba as library location
+ Rhythmbox can not use smb:// as library location
--
Rhythmbox can not use smb:// as library location
https://bugs.launchpad.net/bugs/273294
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Reproduced on current hardy.
The problem is that the user gets added to the sambashare group, but the
group membership won't be refreshed until the user logs out and back in.
It's not really a samba problem, it's more a problem in the design of
that nautilus "Sharing Options" dialog box. It should
> It should work without re-login, as at windows and mac. If that OS can
do that, also ubuntu should.
It is more a question of security. On windows and mac, all users are
authorized to create shares, unless explicitely denied by their admin in
some group policy (on Windows). We can do that too, we
Ted:
I can confirm the version in your PPA fixes this.
This is a cosmetic fix but definitely one that should make it to release :)
** Changed in: gnome-power-manager (Ubuntu)
Target: None => ubuntu-8.10
--
"Starting Power Manager" shouldn't show up on taskbar during login
https://bugs.lau
Michael:
Confirmed your PPA packages fix the issue for me too. Good job :)
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 275957 ***
https://bugs.launchpad.net/bugs/275957
** This bug has been marked a duplicate of bug 275957
gnome-screensaver-dialog crashed with SIGSEGV in g_type_create_instance()
--
gnome-screensaver segfaults at login screen instead of giving back login
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver idle fails after resume
https://bugs.launchpad.net/bugs/185554
You received this bug notification because you are a member of Ubuntu
Desktop
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver does not reliably allow login after suspend
https://bugs.launchpad.net/bugs/99647
You received this bug notification because you are a member
** This bug is no longer a duplicate of bug 286127
gnome-screensaver segfaults at login screen instead of giving back login
screen
--
gnome-screensaver causes my laptop to hang on resume from memory-suspend
https://bugs.launchpad.net/bugs/58963
You received this bug notification because you a
For me it fixes the bug from the description : "the screen starts to
fade, but then immediately returns to the desktop instead of starting
the screensaver".
(Note that I still have just a blank screen rather than a specific
screensaver if running on battery, but this is not what this bug is
about,
** Summary changed:
- gnome-screensaver-dialog crashed with SIGSEGV in g_type_create_instance()
+ Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
--
Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
https://bugs.launchpad.net/bugs/275957
You rece
I can reproduce it on a clean RC install too :
- Install Ubuntu, pick "France - France alternative" as the keyboard.
- When Ubuntu is installed, try "Lock screen" from FUSA
- Try to unlock...
Will see if I can reproduce on a default English install.
** Changed in: gnome-screensaver (Ubuntu)
Im
This seems to be specific to the "France - France alternative" keyboard,
doe snot affect the default US keyboard or the "France - France"
keyboard...
Unfortunately, the "France - France alternative" keyboard is the default for
French users :)
People that are/were affected by this bug: please tell
The strange thing is that adding a "France alternative" layout (and
removing the "France alternative" set by the installer) in the
Preferences > Keyboard > Layouts workarounds the bug...
--
Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)
https://bugs.launchpad.net/bugs/2
Should be fixed at the source of the crash (libgnomekbd).
** Also affects: libgnomekbd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libgnomekbd (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
** Changed in: gnome-screensaver (Ubuntu)
Stat
Removing likewise-open: if GDM implementation shows that something also
needs to be done on likewise-open side, please reopen the task.
** Changed in: likewise-open (Ubuntu)
Importance: Wishlist => Undecided
Status: Triaged => Invalid
--
GDM support for domain choice
https://bugs.launc
** Summary changed:
- Rhythmbox can not use samba as library location
+ Rhythmbox can not use smb:// as library location
--
Rhythmbox can not use smb:// as library location
https://bugs.launchpad.net/bugs/273294
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I agree it doesn't look very good when you log in.
Apparently StartupNotify=true has been there for some time (since
2.14.3-3), and is set explicitely so that a busy cursor is displayed...
What seems new in recent upgrades is that the "Starting Power Manager"
taskbar item remains active for quite
xset -dpms doesn't fix it here.
unsetting "undirect fullscreen windows" fixes it.
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
deskto
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Compiz inhibits screensaver or
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
does not start in intrepid
http
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Gnome-screensaver does not stay on
https://bugs.launchpad.net/bugs/159263
You received this bug notification because you
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
gnome-screensaver never start f
Those who can, please test the compiz packages from:
https://launchpad.net/~tcarrez/+archive
and report success/failure. You no longer should have "Unredirect Fullscreen
Windows" disabled since the purpose of this workaround is to disable it for
gnome-screensaver only. Don't forget to log out/ lo
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
screensavers broken in intrepid with compiz
https://bugs.launchpad.net/bugs/271229
You received this bug notification bec
Proposed fix is to reenable an updated version of the
030_fix_screensaver patch that disables "Unredirect Fullscreen Windows"
for gnome-screensaver only.
I will push this into my PPA so that you can all test this and report if
it fixes it without any dirty side-effect :)
compiz (1:0.7.8-0ubuntu4)
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 271229
screensavers broken in intrepid with compiz
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Screensaver Isn't Work
This might be related or just another bug :
If I select the option "Lock screen while screensaver is on" in
gnome-screensaver, then the screensaver starts up correctly. However when I hit
some keys or move the mouse, the screensaver just restarts... I need to kill it
from SSH to recover my keybo
This is linked to the keyboard choice...
To fix it (on both my workstations) I opened my keyboard preferences,
clicked "+" to select a new layout, selected the SAME layout I used to
have. Then it appears twice on the list. Select the newly-added one as
default and make it the system default. You c
Forget my Lock screen issue (comment 29), it is unrelated (see bug
275957).
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
Reproduced on current hardy.
The problem is that the user gets added to the sambashare group, but the
group membership won't be refreshed until the user logs out and back in.
It's not really a samba problem, it's more a problem in the design of
that nautilus "Sharing Options" dialog box. It should
> It should work without re-login, as at windows and mac. If that OS can
do that, also ubuntu should.
It is more a question of security. On windows and mac, all users are
authorized to create shares, unless explicitely denied by their admin in
some group policy (on Windows). We can do that too, we
smbclient uses FTP-like commands like ls / put / get
Please see
http://manpages.ubuntu.com/manpages/jaunty/en/man1/smbclient.1.html#toptoc4
--
Renaming a file through Samba overwrites existing one
https://bugs.launchpad.net/bugs/382117
You received this bug notification because you are a member
** Tags added: regression-potential
--
ssh-agent stops responding
https://bugs.launchpad.net/bugs/352154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Not an ssh bug, but rather a seahorse or gnome-keyring regression,
opening related tasks and marking regression-potential.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
** Also affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-keyring (
I've been reproducing that as well. I'll try to get you a more complete
backtrace of that SIGABRT.
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from authentication socket.
https://bugs.launchpad.net/bugs/352921
You received this bug notification becaus
I could not making crash using 2.26.0-0ubuntu5 while it was easy to
reproduce with 2.26.0-0ubuntu4. Jamin, Aaron: did you reproduce it with
the -0ubuntu5 version ?
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from authentication socket.
https://bugs.la
*** This bug is a duplicate of bug 352921 ***
https://bugs.launchpad.net/bugs/352921
** This bug has been marked a duplicate of bug 352921
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading
response length from authentication socket.
--
ssh-add: "Error reading response
Closing as fix released since original poster confirmed it fixed in
9.04, and Stephen opened a separate bug to track his issue.
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: samba (Ubuntu)
Status: New => Fix Released
--
Nautilus failes connecting t
Fixed in Jaunty (as of 0.11.99.1)
** Changed in: rhythmbox (Ubuntu)
Status: Triaged => Fix Released
--
Rhythmbox can not use smb:// as library location
https://bugs.launchpad.net/bugs/273294
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
@Alex: could you provide a rationale for *why* it should ?
** Changed in: likewise-open (Ubuntu)
Status: New => Incomplete
--
gnome-screensaver should allow screen unlock even if account is locked out
https://bugs.launchpad.net/bugs/404321
You received this bug notification because you ar
** Bug watch added: Debian Bug tracker #536757
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536757
** Also affects: gvfs (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536757
Importance: Unknown
Status: Unknown
--
smb: Error while copying file, "Invalid argumen
Well, it's not "totally unusable" since you can still switch to another
user. And there should be other users available if you're under a domain
setup. The whole "account locking" AD feature is buggy, since every
large AD domain user knows they can easily lock out someone else's
account.
I guess i
Yes, it's normal behavior for mv to overwrite without warning in this case. Use
"mv -i" to prompt on overwrite.
I'd say it's a bug in Nautilus, if any. Probably linked to bug 316653.
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
Renaming a file through Samba
Marking Samba as invalid as smbclient delivers expected behavior, please
reopen if you can point to a specific bug/missingfeature in Samba.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
Renaming a file through Samba overwrites existing one
https://bugs.launchpad.net/bugs/382117
Removing likewise-open: if GDM implementation shows that something also
needs to be done on likewise-open side, please reopen the task.
** Changed in: likewise-open (Ubuntu)
Importance: Wishlist => Undecided
Status: Triaged => Invalid
--
GDM support for domain choice
https://bugs.launc
** Summary changed:
- Rhythmbox can not use samba as library location
+ Rhythmbox can not use smb:// as library location
--
Rhythmbox can not use smb:// as library location
https://bugs.launchpad.net/bugs/273294
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I agree it doesn't look very good when you log in.
Apparently StartupNotify=true has been there for some time (since
2.14.3-3), and is set explicitely so that a busy cursor is displayed...
What seems new in recent upgrades is that the "Starting Power Manager"
taskbar item remains active for quite
xset -dpms doesn't fix it here.
unsetting "undirect fullscreen windows" fixes it.
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
deskto
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Compiz inhibits screensaver or
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
does not start in intrepid
http
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Gnome-screensaver does not stay on
https://bugs.launchpad.net/bugs/159263
You received this bug notification because you
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 159263
Gnome-screensaver does not stay on
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
gnome-screensaver never start f
Those who can, please test the compiz packages from:
https://launchpad.net/~tcarrez/+archive
and report success/failure. You no longer should have "Unredirect Fullscreen
Windows" disabled since the purpose of this workaround is to disable it for
gnome-screensaver only. Don't forget to log out/ lo
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
screensavers broken in intrepid with compiz
https://bugs.launchpad.net/bugs/271229
You received this bug notification bec
Proposed fix is to reenable an updated version of the
030_fix_screensaver patch that disables "Unredirect Fullscreen Windows"
for gnome-screensaver only.
I will push this into my PPA so that you can all test this and report if
it fixes it without any dirty side-effect :)
compiz (1:0.7.8-0ubuntu4)
*** This bug is a duplicate of bug 278112 ***
https://bugs.launchpad.net/bugs/278112
** This bug is no longer a duplicate of bug 271229
screensavers broken in intrepid with compiz
** This bug has been marked a duplicate of bug 278112
Screensaver doesn't start
--
Screensaver Isn't Work
This might be related or just another bug :
If I select the option "Lock screen while screensaver is on" in
gnome-screensaver, then the screensaver starts up correctly. However when I hit
some keys or move the mouse, the screensaver just restarts... I need to kill it
from SSH to recover my keybo
This is linked to the keyboard choice...
To fix it (on both my workstations) I opened my keyboard preferences,
clicked "+" to select a new layout, selected the SAME layout I used to
have. Then it appears twice on the list. Select the newly-added one as
default and make it the system default. You c
Forget my Lock screen issue (comment 29), it is unrelated (see bug
275957).
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
Ted:
I can confirm the version in your PPA fixes this.
This is a cosmetic fix but definitely one that should make it to release :)
** Changed in: gnome-power-manager (Ubuntu)
Target: None => ubuntu-8.10
--
"Starting Power Manager" shouldn't show up on taskbar during login
https://bugs.lau
1 - 100 of 259 matches
Mail list logo
