It happens in ArchLinux as well, so I am sure it has nothing to do with the
Ubuntu version...
WARNING: Not able to provide 1 puzzles in levels ['hard']
WARNING: Generate more puzzles if you really need this many puzzles!
WARNING: Repeating puzzle for difficulty hard -- generate more puzzles to avo
I have the bug too.. Here is a crash report...
** Attachment added: "_usr_bin_abiword.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/993543/+attachment/3159571/+files/_usr_bin_abiword.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs
Workaround installing the latest driver from Nvidia 285.05.09 -- works fine!
I found a .deb here https://launchpad.net/~ubuntu-x-swat...ates/+packages
(The Nvidia package won't install as is)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The problem only exists if I start the program from the primary X Screen
e.g. using an xterm and something like " DISPLAY=:0.1 xterm &"
starting on the secondary screen using the icewm menu is OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That is everything works fine other than keyboard focus remains in the primary
screen.
11.04
Using nvidia Linux-x86_64
NVIDIA Driver Version: 270.41.06
seperate X screens
no Xinerama
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Same problem with 11.04 running icewm!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774941
Title:
No keyboard focus on second screen with Duel Head after upgrade to
11.04
--
ubuntu-bugs mailing
I solved or worked around the problem using this link:
https://wiki.ubuntu.com/UbuntuOne/Bugs
this section:
ROOT_MISMATCH in syncdaemon.log - This normally indicates that there may
be two Ubuntu One accounts, one in the local cache and another setup in
the keyring. This happens if the user insta
Same problem in Italy:
http://forum.ubuntu-it.org/index.php?topic=430439.0
An interesting solution, he removed nautilus and now his system works
I forgot to say above that I am running 64 bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same problem here (actually in an openbox desktop)
If I first run ubuntuone-launch the nautilus, I get the following:
j...@jeff:~$ nautilus --no-desktop
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
** Message: Initializing gksu extension...
sys:1: Warning: inv
** Attachment added: "xorg log"
http://launchpadlibrarian.net/41482145/Xorg.0.log
** Changed in: xorg (Ubuntu)
Status: Invalid => Confirmed
--
Ice listener
https://bugs.launchpad.net/bugs/516331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
and other ouput:
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/41482066/lspci.txt
--
Ice listener
https://bugs.launchpad.net/bugs/516331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same problem in lucid lynx Beta
** Attachment added: "Dmesg output"
http://launchpadlibrarian.net/41482029/dmesg.txt
--
Ice listener
https://bugs.launchpad.net/bugs/516331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35778707/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/35778708/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/35778709/ArecordDevices.t
Public bug reported:
Binary package hint: pulseaudio
This was the last line in kern.log
python[2532] general protection ip:7fb20ed55235 sp:7fff00640ff0 error:0 in
libpulse.so.0.12.0[7fb20ed43000+3e000]
mail me if you want me to collect/report any other info
ProblemType: Bug
Architecture: amd64
Is it only me who is still crashing?
--
NetworkManager assert failure: ERROR:nm-device.c:2754:dispose: assertion
failed: (s_ip4)
https://bugs.launchpad.net/bugs/436654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
still crashing ... 64 bit xfce - well managed - older dual core - nice
owner - good luck!
--
NetworkManager assert failure: ERROR:nm-device.c:2754:dispose: assertion
failed: (s_ip4)
https://bugs.launchpad.net/bugs/436654
You received this bug notification because you are a member of Ubuntu
Bug
Still happens on a recently updated (a couple of hours back) 64 bit
Gnome desktop, doesn't really bother me because the process - I guess -
restarts automatically, so I don't even notice a break in
communications, I keep sending duplicates so that you know it's not
fixed yet... Good Luck!
--
Netw
** Attachment added: ".home.jeff..cache.ubuntuone.log.oauth.login.log.txt"
http://launchpadlibrarian.net/33201007/.home.jeff..cache.ubuntuone.log.oauth.login.log.txt
** Attachment added:
".home.jeff..cache.ubuntuone.log.syncdaemon.exceptions.log.gz"
http://launchpadlibrarian.net/33201008
Public bug reported:
Binary package hint: ubuntuone-client
after clicking connect disconnect a number of times, maybe in quick
succession
ProblemType: Bug
Architecture: amd64
Date: Wed Oct 7 07:17:37 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 0.96.0-0
*** This bug is a duplicate of bug 436654 ***
https://bugs.launchpad.net/bugs/436654
** This bug has been marked a duplicate of bug 436654
NetworkManager assert failure: ERROR:nm-device.c:2754:dispose: assertion
failed: (s_ip4)
--
NetworkManager assert failure: ERROR:nm-device.c:2754:dis
I have the same behaviour on three gutsy installations on different
hardware and one hardy, so much so that NetworkManager is unusable. I
use the interfaces file or Wicd if I want to roam. It would be a sad day
to see Hardy released like this.
--
nm-applet: requests keyring password, doesn't use
I think it's a bit of an overkill removing the standard Linux runlevel
behavior in Ubuntu. It's not "Noobs" that get to fiddle the runlevel,
rather people with more experience in Linux. Since this has no effect on
the "Noob" user interface, why not leave it as it was in good old Linux?
It is a usef
22 matches
Mail list logo
