Actually, it appears that a patch has been submitted for this problem
(see https://bugzilla.gnome.org/show_bug.cgi?id=556932#c10). I don't
know how long it will take for this to filter through to Ubuntu. Maybe
it will be fixed in Lucid.
Mal
--
Gnome-sudoku timings all wrong
https://bugs.launch
I have also found that Sudoku in Karmic always reports game times of
about 58 seconds.
After having a bit of a look around the source, it seems that the
problem relates to the autosave function. Autosave is triggered ever 60
seconds (or the time set by gconf /apps/gnome-
sudoku/auto_save_interval
Further to my earlier note about getting a blue screen with intel i810
video, I have worked around my problem by reverting to my original hardy
mythbuntu diskless image for the frontend. This is now served by my
Jaunty backend / server machine and is working well.
Mal
--
[ubuntu jaunty] Blue Sc
I have a similar problem with my Mythtv frontend. This is a Compaq
Deskpro Pentium III system with on-board Intel i810 video with reference
number 8086:1132.
When I try to watch TV with Mythtv, I just get a blue screen. Sound
works correctly and it responds keypresses, so I can back out of TV mo
I have now managed to get this working on my Intrepid system. The trick
was to install Coherence 5.8 from the "Cheeseshop" as well as installing
the SVN version of the Rhythmbox plugin.
Mal
--
Rhythmbox Coherence UPnP doesn't work.
https://bugs.launchpad.net/bugs/278790
You received this bug no
Unfortunately, I have not been able to duplicate John's success on my
Intrepid system. I followed the instructions above and after I fix the
"import louie" line and run Rhythmbox, I get no messages about Coherence
and no sign of any shared music. This was using the python-coherence
package from t
Actually, I think this bug is related to problem with mount.nfs trying
to mount an export on a non-existent server. See
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/234480.
This problem has appeared in Ubuntu Hardy but not in Gutsy.
By the way, I don't see why a design flaw couldn't
Sorry - please ignore my previous comment. It was meant for a different
bug (234480).
Mal
--
nfs-client
https://bugs.launchpad.net/bugs/232325
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I really don't understand why this issue has not received more attention
from other users. This bug seriously degrades the usefulness of autofs
on Hardy. Maybe not many people use autofs?
To make sure I didn't have some particular problem with the computer I
found the problem with, I installed H
Public bug reported:
Binary package hint: nfs-common
When using autofs in Hardy to automount nfs shares, lengthy hangs occur
if the target server is not available. This causes nautilus (and the
desktop) to hang at login and when opening. The problem seems to
originate with changed behaviour of
I am seeing this problem with the updated nfs-common package in Hardy.
As shown below, I get about a 38 second hang when attempting to mount an
export from an off-line server. The same thing on Gutsy produces a "No
route to host" message and returns in about 3 seconds.
[EMAIL PROTECTED]:~$ cat /e
*** This bug is a duplicate of bug 132939 ***
https://bugs.launchpad.net/bugs/132939
Output from:
$ grep gdm /var/log/syslog
after failed suspend from gdm greeter is included as an attachment.
Mal
** Attachment added: "syslog-gdm"
http://launchpadlibrarian.net/10793650/syslog-gdm
--
w
I have the same problem with 2 different desktop computers. The
following error message appears in /var/log/syslog after an unsuccessful
attempt to suspend from the gdm login screen:
"... gdm[6792]: WARNING: Request for configuration key
daemon/SuspendCommand=, but not type STRING"
The SuspendCo
13 matches
Mail list logo
