The other bug mentions using packages from debian sid. You may want to
try those packages as well (or sit tight and see if it is packaged for
Hardy).
Before marking this as a duplicate of the other bug, I would test that
it is a regression from Gutsy. The other bug mentions it worked on
Gutsy
For the virtual desktop you could get away with Virtual 1024 1536
Are you trying to clone the internal monitor or have an extended
desktop?
I have a similar setup to yours (except I have the misfortune of an x1400; what
a pain!) and the following works to get my external monitor working as an
What resolution are the monitors you are using (both the internal LCD
and external monitor)?
The Virtual 2048 2048 line is not meant to be copied verbatim. It is
meant to be the size of your virtual desktop. For instance I have a
1400x1050 LCD on my Thnkpad, and if I connect it to my 1680x1050
I offered a patch upstream that was accepted. What is the proper
procedure to get an ubuntu package made with this patch so that people
may test it? I would build the package myself, but I believe it is bad
practice for people to install random binaries so I would prefer to not
perpetuate this
Try adding the following:
SubSection Display
Depth24
Modes1600x1200 1280x1024 1024x768 800x600
640x480
# ADD A VIRTUAL LINE TO PROVIDE FOR THE LARGEST SCREENS YOU WILL
HOTPLUG
Virtual 2048 2048
If you restore your xorg.conf to its original settings and run xrandr
-q, what output do you get?
--
open source ati driver in hardy can't do external monitor on laptop
https://bugs.launchpad.net/bugs/222905
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You mean like in the attached picture?
I've been playing with it and can't figure out why it is doing it. If
you look, the scrollbar and window decoration are different colors.
I've actually gotten it so that I can have 3 windows, each with a
different color (I only got this once).
As far as I
Forgot to attach
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/13954687/Screenshot.png
--
metacity color doesn't change (after you change the gtk2 engine) until you
logout and log back in
https://bugs.launchpad.net/bugs/192684
You received this bug notification because
*** This bug is a duplicate of bug 192684 ***
https://bugs.launchpad.net/bugs/192684
** This bug has been marked a duplicate of bug 192684
metacity color doesn't change (after you change the gtk2 engine) until you
logout and log back in
--
window decoration colors do not change
I don't think this is a bug. The thinkfinger package is for libpam.
The keyring does not use pam to authenticate.
If you read the known issues on the place to which you linked it say the
same thing.
--
After logging in by thinkfinger, I have to give nm-applet access to keyring by
typing in
Does the iso's MD5 compare to that published on the mirror sites?
--
804-alternate-i386.iso Integrity test failed
https://bugs.launchpad.net/bugs/221908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Are you running any firefox addons? I'm running a fresh install of
firefox on hardy, and it doesn't crash on that page. If you could give
a list of plugins I can see if I can reproduce this error.
--
firefox causes X to crash when openning a large page
https://bugs.launchpad.net/bugs/221906
I think I have a fix for you until something better comes along (Hardy +1/2
maybe?):
See https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/108993
Specifically these comments:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/108993/comments/8
I just checked my iso checksum, and it matches the reported checksum.
If you can download via bittorrent you get some built in checksumming
which makes it easier than downloading from the mirrors several times
(and can be faster if you are able to torrent).
--
804-alternate-i386.iso Integrity
I can confirm this as can some others on my campus.
In my case it fails without any forward slashes in the password.
I don't believe it is an escaping problem as changing the URI for the
printer to match what I see on Gutsy shows the same log message with the
same URI.
I'm also getting
I've narrowed down the issue some more. It appears to be an issue with
deciding which username to use for authenticating.
I did the following on Gutsy and Hardy:
-Installed wireshark
-Scanned for SMB protocol
-Looked at authentication tries
-Noted usernames.
Results:
-Gutsy authenticated once
I believe I have fixed the issue. After playing around I realized that
smbclient would complain that 'client plaintext auth' was disabled (my
campus server needs plaintext for some reasom).
Adding the following to smb.conf and rebooting fixed my problem entirely:
client plaintext auth = yes
17 matches
Mail list logo
