Sorry for double post. I don't believe this is a bug and can safely be
closed. I do recommend however that the default config have matching
pan/duration as it will then behave as a normal user expects.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I'll add my 2c as I decided to do a strace on the config.
For KDE the configuration file is: -
~/.kde/share/config/glslideshowrc
Simply updating it to have matching pan/duration fixes the "issue". No
need to install xscreensaver.
--
You received this bug notification because you are a member
I too had this same error, but I found a workaround. Set the environment
variable 'LIBGL_ALWAYS_INDIRECT=yes' and then try running the program.
Example: -
administra...@artemis:~$ glxinfo
name of display: localhost:11.0
Error: couldn't find RGB GLX visual or fbconfig
administra...@artemi
Sorry, should also mention that I've tried the usual tricks I would try under
Windows. That is, sometimes under Windows you get the behaviour where the OS
gets confused and doesn't recognize a key-release on something like the shift
key, and thus when you type it capitalises everything. You get
I can confirm this behaviour and yes it is a BUG.
I'm running Hardy Heron, English on a Sony VAIO TX notebook.
Currently the Caps Lock light is on, but I'm typing as if it is off. If
I turn it off then everything comes up in capitals.
The only thing I can think they may have caused it was that I
I can confirm the same problem.
Hardy Heron 8.04 amd64. Nvidia Proprietary driver with Compiz enabled.
Something to do with loose bindings upstream.
--
Evolution cursor creates a track.
https://bugs.launchpad.net/bugs/237002
You received this bug notification because you are a member of Ubuntu
This is NOT fixed yet (Hardy 8.04). Excuse my very rushed comment.
First, a typo
- if [ ${IPOPTS} == "dhcp"] && [ -n "$DHCPPORT" ]; then
+ if [ ${IPOPTS} == "dhcp" ] && [ -n "$DHCPPORT" ]; then
(Note the space)
Second. I'm still unsure if $IPOPTS should be in ipconfig long format as
described
Public bug reported:
My first bug report.
Gutsy 7.10 Host. Gutsy 7.10 LTSP Client Chroot.
When booting an LTSP client, using NBD and squashfs (Default in LTSP
5+), I kept getting an error where the squashfs volume would just
disappear.
Traced it down to the script:
/etc/init.d/ltsp-client-setu
