I hadn't tried using vinagre for some time, but I updated with the
latest updates yesterday and tried connecting again (using the same
computers that had not worked before); remote desktop is working great,
and I was able to see and manipulate everything I tried.
--
vinagre connects but appears
Confirmed on two computers with Jaunty, using the nvidia 180 driver.
Didn't see this behavior on the first computer in Intrepid, only after a
new install of Jaunty. Occurs when using Cedega OR wine.
--
gnome panel displayed running wine apps full screen with desktop effects enabled
https://bugs.
Same behavior here, also have nvidia-180 driver.
--
vinagre connects but appears that I cannot start anything on remote desktop
https://bugs.launchpad.net/bugs/350327
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I don't think this should be closed, I just upgraded one of my computers
from Hardy to Intrepid and had this happen. It's very disconcerting,
and I had not changed any settings. There appears to be something
broken in the upgrade process. I'm glad the fix is easy, but it would
be nice if nautilu
Fresh install of Beta from 2 days ago... USB keyboard works fine, USB
mouse does not. In /var/log/messages I see my USB wheel mouse being
detected and set to /class/input/input6. Restarting Gnome
(/etc/init.d/gdm restart) did not resolve the problem, and I did a full
apt-get update/upgrade/dist-u
The xorg file fix worked for me - but even better news, I ran all the
updates today and with a clean xorg file (i.e. no entries for any input
devices), my mouse and keyboard now work perfectly! I love seeing bugs
disappear so quickly...
--
[intrepid] mouse and keyboard stop working under gdm and
Update - in Intrepid Ibex (beta), after applying the restricted NVidia
driver through the built-in Ubuntu mechanism, my screen resolution is
working beautifully - I didn't have to do any messing with the xorg file
this time. Before using the restricted driver, however, it was still
only allowing 8
I also had the same problem using the nvidia driver through the
Restricted Drivers Manager - I could get 800x600 resolution through nv
(hardly great, but that's a different issue), but once I loaded the
nvidia driver through the Manager, I could only get 640x480.
Did these three steps this weekend
Public bug reported:
Binary package hint: xserver-xorg
Running the latest Hardy beta on a desktop with CRT monitor (model
Gateway EV910, edid "name" gwy232a) with NVidia card. Used Restricted
Driver Manager to install the nvidia driver and as far as I can tell
it's being used.
Only 320x240 and
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/13079401/xorg.conf
--
[hardy] Screen resolution only 640x480
https://bugs.launchpad.net/bugs/211098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Attachment added: "ddcprobe output"
http://launchpadlibrarian.net/13079404/ddcprobe.txt
--
[hardy] Screen resolution only 640x480
https://bugs.launchpad.net/bugs/211098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/13079409/Xorg.0.log
--
[hardy] Screen resolution only 640x480
https://bugs.launchpad.net/bugs/211098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "output of get-edid | parse-edid"
http://launchpadlibrarian.net/13079429/edid.txt
--
[hardy] Screen resolution only 640x480
https://bugs.launchpad.net/bugs/211098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Ignore the 1024x768 entry in the xrandr output; I added that myself, but
it won't let me enable it, either through xrandr --output default --mode
[EMAIL PROTECTED], or through the Ubuntu Screen Resolution tool. The screen
just flickers once, no new entries are added to the Xorg.0.log
** Attachmen
The output from running xresprobe leads me to believe this is not a bug
with the nvidia driver? It seems to think it can support 1024x768 just
fine on this monitor...
** Attachment added: "xresprobe nvidia"
http://launchpadlibrarian.net/13079503/xresprobeOutput.txt
--
[hardy] Screen resoluti
I started up a separate bug for my particular monitor/video card combo, and
attached all the information to it. Seemed cleaner than merging it into this
bug--however, if anyone is still monitoring this bug, here's a link to the one
I created:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/
Great--glad to hear the information was useful. I went ahead and copied
over my old xorg.conf file from Gutsy to use for now, and that gets me
up and running with a decent resolution. I'm attaching the file in case
someone else stumbles across this same bug and doesn't have a working
xorg.conf fi
Upgraded from Karmic to Lucid today and am also having the "symbol
'grub_puts' not found" error described by illbashu; I have the Ubuntu
install on a different drive from sda, so I had to reinstall grub2 for
Karmic also. I haven't rebooted yet after reinstalling grub2, but I
assume I'll run into t
18 matches
Mail list logo
