Yes, fine to close. It is no longer reproducible in 8.10. Thanks!
--
Timestep and speed in Rotate cube in Compiz settings can not be set
https://bugs.launchpad.net/bugs/154098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi, just tested it out on the docking station finally, and it looks like
it is related to multiple monitors. When I am just on the laptop monitor
I can cycle through all the available screensavers and not trigger a
crash. When I am hooked up to a second external monitor, just cycling
through
Verified on my Gentoo install too.
On 10/31/07, Merton [EMAIL PROTECTED] wrote:
So if it is a BIOS setting, is any other distro of linux affected by
this bug?
Or does it mainly have to do with Ubuntu's way of managing drive power
on battery?
Concerning 59695:
Will enabling package
Hi Pedro,
You're right, that fixes it. Ticking the setting
use_screensaver_settings will now lock the screen when I close the lid.
Thanks,
Marko
--
Screen is not locked when laptop lid is closed
https://bugs.launchpad.net/bugs/156226
You received this bug notification because you are a member
Public bug reported:
Binary package hint: gnome-screensaver
When I open System - Preferences - Screensaver and try to select a few
of the first screensavers, X crashes. At times the gnome-settings-daemon
dies as well. It does not always happen on the same screensaver, but it
is enough to go
Sorry, forgot to mention, this is on Gutsy, which was just upgraded to
from Feisty the other day. This worked fine in Feisty.
--
Changing screensaver crashes X
https://bugs.launchpad.net/bugs/156212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
On Gutsy, just recently upgraded from Feisty, I have the screensaver set
to lock screen in System - Preferences - Screensaver.
When I close the laptop lid the screen is blanked, however when opened
again it is not locked. It does lock when the screensaver time is
reached
Public bug reported:
Small typo on the page:
https://launchpad.net/codeofconduct/1.0.1/+sign
Step 3 says to sign the downloaded code of conduct text using the command:
gpg --clearsign UbuntuCodeOfConduct-1.0.1.txt
The file that was offered for download in the previous screen was
Hi Pedro,
Very strange... it looks like it is linked to whether I am on a docking
station or not (ie. multi monitors). I can not replicate this at home
when not docked, whether I am using my xorg.conf or auto-detect.
I will have to come back to this on Friday when I'm back in the office.
In the
** Attachment added: Xorg log when using my xorg.conf
http://launchpadlibrarian.net/10145826/Xorg.0.log
--
Changing screensaver crashes X
https://bugs.launchpad.net/bugs/156212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: Xorg.log when using auto-detect
http://launchpadlibrarian.net/10145833/Xorg.0.log
--
Changing screensaver crashes X
https://bugs.launchpad.net/bugs/156212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: net-tools
When running the netstat command, the first title line that is output says
routeing... surely it should be routing:
# netstat -rn
Kernel IP routeing table
Destination Gateway Genmask Flags MSS Window irtt Iface
What's
Hi Basilio,
Yeah, you're right, it seems it's an en_GB problem, C prints it just
fine:
$ locale
LANG=en_GB.UTF-8
LC_CTYPE=en_GB.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_COLLATE=en_GB.UTF-8
LC_MONETARY=en_GB.UTF-8
LC_MESSAGES=en_GB.UTF-8
LC_PAPER=en_GB.UTF-8
LC_NAME=en_GB.UTF-8
Yes, I've seen this as well in the Gutsy final release I just upgraded
to last night. vmware-server 1.0.3 will not run in Gutsy because of the
kernel modules mismatch.
Workaround:
1. Back up your license file found in: /etc/vmware/license.vs.1.0-00 or at
least save the serial contained in that
I've got the same issue, with this card:
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS
110M/GeForce Go 7300] (rev a1)
I've just done an upgrade to Gutsy. The composite worked fine in Feisty.
Same thing, I get the message The Composite extension is not available
when
Sorry, I should have been more thorough... even though composite was
working fine in Feisty I had it turned off in xorg.con. Upgrading to
Gutsy does not reset this. So just turning it back on in xorg.conf
worked.
However, the dialog box is what is borked, it should allow you to click
OK to close
Public bug reported:
Binary package hint: compizconfig-settings-manager
Under the Rotate Cube plugin, the General settings:
- Speed
- Timestep
seem to be inconsistent in remembering that they were set.
For example, I would change the numeric setting timestep from 1. to
20.. I click
Ok thanks, I will try reopening the one with Gnome.
No reason why it can't be disabled on our build though?
--
Disable ctrl-t as default for moving to trash
https://bugs.launchpad.net/bugs/137638
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
That's a valid point.
Anyway, I've filed a bug with GNOME too. Here's the link for the record:
http://bugzilla.gnome.org/show_bug.cgi?id=474222
--
Disable ctrl-t as default for moving to trash
https://bugs.launchpad.net/bugs/137638
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: nautilus
Hi,
Would it be possible to disable ctrl-t as a keyboard shortcut for moving
to trash?
1) There's already the del key which achieves exactly that, so no need for two
shortcuts (and del is far more intuitive).
2) It clashes with the very often
Close it for now, it looks like I've got a few more complexities with a
combo of mod_rewrite, path_info and other configs. I'll need to go back
to a clean install, debug more to narrow down the issue better and
reopen if necessary.
Thanks
** Changed in: php5 (Ubuntu)
Status: Incomplete =
Public bug reported:
Binary package hint: php5
Running Feisty with the standard PHP 5.2.1 and Apache 2.2.3.
If in the file /etc/php5/apache2/php.ini the error_reporting value is set as
follows:
error_reporting = E_ALL ~E_STRICT
Then no PATH_INFO will be provided to the PHP scripts. It is
Public bug reported:
Binary package hint: openoffice.org
I have msttcorefonts and Openoffice.org 2.2.0 installed.
If I carry out the following steps:
- Open up Openoffice.org writer and start a new doc
- Open Styles and Formatting (F11)
- Select any header style, eg. Header 1 and try to modify
** Attachment added: screenshot with one document open
http://launchpadlibrarian.net/8215371/onedoc.png
--
Openoffice.org shows inconsistent fonts in styles
https://bugs.launchpad.net/bugs/122541
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
This shows how the font list should look, but I had to open first an
unused second document in the background. Notice how now there are more
fonts and not just the three fonts AR, Baekmuk and Kochi like in the
first screenshot.
** Attachment added: screenshot with two documents open
25 matches
Mail list logo
