Thanks for responding to this. Rather than close the issue, can we
either:
1) Track this as a bug with the fglrx drivers upstream or
2) Catch the error setting the virtual resolution and display a friendly error
message like Your video driver does not support extending your screen between
I'm seeing the same problem with an fglrx package version of
2:8.960-0ubuntu1.1.
Removing fglrx really isn't option, especially on an LTS release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856312
*** This bug is a duplicate of bug 856312 ***
https://bugs.launchpad.net/bugs/856312
Public bug reported:
I have a Dell studio XPS laptop with an external monitor connected to
the VGA port. I want to be able to span my desktop across my laptop
screen and my external monitor. I used to be
*** This bug is a duplicate of bug 856312 ***
https://bugs.launchpad.net/bugs/856312
** This bug has been marked a duplicate of bug 856312
Cant set resolution with two monitors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 856312 ***
https://bugs.launchpad.net/bugs/856312
** This bug has been marked a duplicate of bug 856312
Can't use non-mirrored resolution with two monitors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- Cant set resolution with two monitors
+ Can't use non-mirrored resolution with two monitors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856312
Title:
Can't use non-mirrored
Thanks for the reply. Yes, I wasn't really sure if lightdm was the
source of my /tmp permissions problem (actually, pretty sure it isn't),
but as I had no way of tracking it down, lightdm was the first place I
encountered an issue.
Are there any steps I can follow to work out why this might be
Public bug reported:
Expected: Login via lightdm should successfully create a logged in Ubuntu
session.
What happened: A session is not created and I am returned to lightdm.
When I reboot my laptop, the lightdm greeter allows me to enter my
password, but when I press enter, the screen goes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999526
Title:
Cannot login from lightdm, /tmp is not writable
To manage notifications about this bug go to:
Public bug reported:
Release: Ubuntu 10.04.3 LTS
gnome-panel version: 1:2.30.2-0ubuntu0.2
When I log into a new user session on my laptop, I expect that the indicators
in gnome-panel on the top right are:
1) displayed clearly and without obstruction and
2) displayed in the same position as when
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863258
Title:
Indicators on the top right of the panel are often obscured or out of
place on login
To manage notifications about this bug go to:
Hi, I'm getting this too, while running Karmic through VirtualBox. Will
try the tty redirection.
** Attachment added: Screenshot-1.png
http://launchpadlibrarian.net/32884839/Screenshot-1.png
--
Boot messages show before xsplash kicks in
https://bugs.launchpad.net/bugs/438335
You received
The solution in #13 works well, though in my case a kernel message (I
think relating to the fact I'm running it inside VirtualBox), is still
showing just before xplash loads. Also, on shutdown, I still get a
flicker of messages before usplash takes over.
--
Boot messages show before xsplash
Just retested in Karmic beta, this bug still exists, and gives me the
same resolutions as the Display dialogue did in Jaunty:
1360 x 768
1152 x 864
1024 x 768
800 x 600
640 x 480
However, as noted above, the native resolution of my monitor is 1280 x
1024. Please note that if I add this
** Attachment added: Dmesg output
http://launchpadlibrarian.net/32886133/dmesg
--
[X1800] Incorrect resolutions reported in Display dialog
https://bugs.launchpad.net/bugs/355576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg log
http://launchpadlibrarian.net/32886155/Xorg.0.log
--
[X1800] Incorrect resolutions reported in Display dialog
https://bugs.launchpad.net/bugs/355576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'll try and retest this bug in Karmic beta from the live CD, otherwise
I'm afraid it will have to wait until I can install Karmic proper on my
desktop.
--
[X1800] Incorrect resolutions reported in Display dialog
https://bugs.launchpad.net/bugs/355576
You received this bug notification because
I added your PPA: deb
http://ppa.launchpad.net/bryceharrington/ppa/ubuntu jaunty main, and
did an apt-get update and upgrade, but the only packages offered for
upgrade were intel, mga, and openchrome. I also tried to install
directly from the .deb, but I had a dependancy error with xserver.
When
Public bug reported:
Whenever I click Shut Down in the gnome menu, or type 'sudo shutdown
now' from a terminal, my computer goes through the whole shutdown
process, then reboots.
I used to have the Jaunty beta before upgrading to Jaunty proper, and I
remember carrying out a suspend/resume test
** Attachment added: Syslog
http://launchpadlibrarian.net/26596528/syslog.1.gz
--
Computer restarts/reboots when instructed to shutdown
https://bugs.launchpad.net/bugs/375057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Dmesg
http://launchpadlibrarian.net/26596533/dmesg.1.gz
--
Computer restarts/reboots when instructed to shutdown
https://bugs.launchpad.net/bugs/375057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
No, since I rebooted, I have not since this issue again. Feel free to
close the bug!
--
Rhythmbox fails to load after DBus object creation
https://bugs.launchpad.net/bugs/355602
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Bug watch added: GNOME Bug Tracker #580565
http://bugzilla.gnome.org/show_bug.cgi?id=580565
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=580565
Importance: Unknown
Status: Unknown
--
Very poor performance when extracting audio CDs
Sure thing, I'll do that. Is there a guide on how to link this bug
report to the gnome one?
--
Very poor performance when extracting audio CDs
https://bugs.launchpad.net/bugs/355565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Did a reboot and that seemed to fix it. Do you think it could have been
due to a failed DBus? I looked in my ~/.xsession-errors file and
couldn't see anything pertinent.
Is there anything else I can do to help investigate/reproduce this?
--
Rhythmbox fails to load after DBus object creation
Attached is the output of rhythmbox --debug.
I tried sound juicer, and it seems slightly quicker, ripping the same CD
in about 9m 30s. It seems to affect the speed of my system significantly
as well: audio playing starts stuttering, dragging windows, and even
typing this bug become unresponsive.
As Carasof's reply details, that message is now displayed in the Sharing
Options dialog, and following it's instructions allows you to share the
folder successfully.
However, this is not a very user-friendly way of allowing NTFS drive
sharing, would shipping the default smb.conf with usershare
Public bug reported:
1) Release: Ubuntu Jaunty 9.04 Beta
2) apt-cache policy rhythmbox: 0.12.0-0ubuntu2
3) When extracting audio CDs in other operating systems on the same
computer, the conversion process takes under 5 minutes, and allows me
full use of my computer as the process takes place.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24831397/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/24831398/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/24831399/LsMod.txt
** Attachment added: LsPci.txt
Public bug reported:
Binary package hint: xserver-xorg-video-ati
1) Release: Ubuntu Jaunty 9.04 Beta
2) apt-cache policy xserver-xorg-video-ati: 1:6.12.1-0ubuntu2
3) When installing Ubuntu, I expected the Display dialog in System
Preferences Display to correctly display the native resolution
As Carasof's reply details, that message is now displayed in the Sharing
Options dialog, and following it's instructions allows you to share the
folder successfully.
However, this is not a very user-friendly way of allowing NTFS drive
sharing, would shipping the default smb.conf with usershare
Public bug reported:
Binary package hint: rhythmbox
1) Release: Ubuntu Jaunty 9.04 Beta
2) Rhythmbox 0.12.0
3) Expected: Rhythmbox should load correctly.
4) Actual: After a day of using Rhythmbox on Jaunty, I closed the
program, wanting to report another bug with it's plugin detection
** Attachment added: Debug log for Rhythmbox
http://launchpadlibrarian.net/24832503/rhythmbox-debug.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24832508/Dependencies.txt
--
Rhythmbox fails to load after DBus object creation
I personally don't think an Instant Messaging program would be a correct
fit for messages relating to system updates. Not all users have an IM
running all the time, and if the solution would then be to create a
lightweight message notifier, we are just re-inventing the update-
notifier wheel.
The
I really don't understand how a pop-under window is supposed to notify
the user about anything. A pop-under just isn't obvious at all. If I'm
using Windows, I often find myself annoyed at any window that appears on
my task bar without me specifically launching it.
The current Ibex method seems
I said that if you asked a new Ubuntu user: So, dude, do you think we
should put security=share in your smb.conf?, he'll have no clue what
you're talking about. Hence, it's completely mistaken to say that new
users expect that their smb.conf says security=share. No, they don't.
They expect to
My apologies, I did not realise that setting guest_ok would result in
the same view of the shared folder by windows user. I thought that
perhaps the guest setting in samba would prompt the windows user of a
username and password before accepting a blank. If this is not the case,
then perhaps it
I'm sorry, but I really do see the value of this being kept open. I
realise that this method is inherently insecure, but it seems people are
ignoring the substantial use-case of a Ubuntu newbie who is used to
sharing his files in Windows, and is faced with the near-labyrinthine
configuration of
I'm not at the computer in question at the moment, when I get home I
will boot with the Hardy Heron Live CD, and attempt to share a folder on
my ntfs drive. I'm afraid I can't tell you the name of the application
that shares the folders, just that it launches when I click Share
folder in nautilus'
This really needs to be changed in Hardy. PAM synchronisation of users
sounds like a great idea, and security=user should be enabled by
default, so users do not unwittingly open themselves up to attack.
However, the shared folders tool must provide an obvious option to allow
anonymous access, as
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/10848649/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/10848650/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/10848651/ProcStatus.txt
--
Share
Public bug reported:
Binary package hint: samba
Problem:
When either right-clicking in nautilus or using the Shared Folders application
in the Administration menu, I cannot share a folder on an ntfs-mounted drive.
When I attempt to, an error message pops up saying something like cannot
access
Public bug reported:
Binary package hint: usplash
When booting into Ubuntu, after the bios has initialised, I occasionally
get display corruption. This seems to happen whenever uplash drops into
text-mode (for example, it happened when I entered the wrong settings in
fstab and mounting at boot
43 matches
Mail list logo
