Steve, why then are all of these bugs linked to this bug as duplicates?
https://bugs.launchpad.net/ubuntu/+source/xsplash/+bug/551196
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/552980
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553656
https://bugs.launchpad.net/ubuntu/+sou
All that has been achieved so far is the logo looks slightly less
terrible when plymouth chooses the worst possible video mode. That
might be acceptable if Lucid is going to ship with this bug still open,
but it does not resolve the bug.
plymouth to display the splash screen in our native resolut
** This bug is no longer a duplicate of bug 551013
ubuntu-logo on VGA fb (as with nvidia or fglrx binary drivers) does not
display crisply
--
plymouth: after installing proprietary nvidia driver, splash screen displays in
low color/low resolution mode
https://bugs.launchpad.net/bugs/553854
Y
This bug is about plymouth being unable to determine the correct native
resolution when using proprietary display drivers.
I removed the reference to bug #551013, which is poor display quality of
the logo in 16colors (now resolved).
--
plymouth: after installing proprietary nvidia driver, splash
Can anyone with ATI hardware, using the proprietary ATI driver please
attempt to reproduce the issue and post the results.
--
plymouth: after installing proprietary nvidia driver, splash screen displays in
low color/low resolution mode
https://bugs.launchpad.net/bugs/553854
You received this bug
Apparently, this workaround is resolving the issue for some users
(linked below). I haven't had time to test this. Perhaps this could be
investigated and used towards developing a solution. (LaunchPad user
idyllic claims to have devised this solution -
https://launchpad.net/~idyllic)
http://new
The Canonical folks believe they have delivered a fix to the title of
this bug. Let's let this one lie.
I corrected the erroneous linking of my bug as a duplicate of this bug.
Now, it is its own bug. If you are affected by plymouth's poor choice
of resolution when using a proprietary display dri
* what testing was done before transitioning to 'plymouth' for lucid was green
lighted for an LTS of all things
* why did Canonical not investigate the true number of users affected
* do we expect this to be resolved for lucid
* if not, what do we need to do to prove there is community interest in
Occurred while changing some settings in the NVIDIA X Server Settings
Administration applet..I believe.
--
gnome-panel crashed with SIGSEGV in ORBit_c_stub_invoke()
https://bugs.launchpad.net/bugs/552965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
opengeek, Tesselode was assisting wavded. He was not insisting that the
solution is not to use proprietary drivers.
I'm pretty sure using nouveau with plymouth and the proprietary driver
under X is not possible. Even if it were, it would still break the
seamless transition, which AFAIK, is the p
Public bug reported:
Binary package hint: compiz
I'm not positive which broke me, but here's what I did:
Installed latest updates.
Configured secondary display (Seperate X Screen/Xinerama).
Logged off and back in for changes to take effect.
After logging in, I have no desktop effects. From Sys
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43489357/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/43489358/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43489359/Dependencies.txt
** A
Further testing: Simply disabling Xinerama restored Compiz.
Any ideas?
--
compiz broken with latest updates and nvidia display config
https://bugs.launchpad.net/bugs/558875
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
If lucid ships with this bug open, perhaps we should consider putting
users on affected drivers on usplash with a comparable logo, and then
roll everyone over to plymouth once the bug is confirmed resolved? Or
is that too drastic of a change post-release?
--
ubuntu-logo on VGA fb (as with nvidia
True, I can suffer with any other multi-mon mode if I must have Compiz,
but I prefer Xinerama. As I said earlier, Compiz has worked with
Xinerama on this hardware as recently as Beta 1 + a few days of updates.
This incident came from the 20100331.2 daily ISO with updates from the
daily firehose.
I'm suspicious since you can reproduce it on your ATI card :)
--
compiz broken with latest updates and nvidia display config
https://bugs.launchpad.net/bugs/558875
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: metacity
Just grabbed a deluge of updates today and noticed right away that I was
unable to click the corner of the window to close it.
This breaks consistency with all previous versions of Ubuntu, and from
my experience, consistency with other operating
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43617833/Dependencies.txt
--
clicking corner of window no longer closes window
https://bugs.launchpad.net/bugs/559726
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
Binary package hint: xorg
Booting to the Ubuntu Alpha 3, Beta 1 and 20100331.2 Live CDs, Ubuntu
hardlocks when plymouth should transition from the bootsplash to the X
session (the bootscreen stays up, appears completed but has stopped
animating, while the disc reads a bit lon
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42861926/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42861928/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42861930/Dependencies.txt
** A
I forgot to mention that when plymouth starts, this error appears in
textmode on my secondary display:
(process:487) GLib-WARNING **: getpwuid_r(); failed due to unknown user
id (0)
Not sure if that's helpful..
--
nouveau: hangs on boot if second monitor is present
https://bugs.launchpad.net/bu
Public bug reported:
Binary package hint: grub
Apologies if I filed this against the wrong package, please reroute as
necessary.
When booting from a Ubuntu Live CD, the rebranded Ubuntu graphic shows
the smaller 'logo' with colors filling in the people forming the circle.
However, whether you se
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42863683/Dependencies.txt
--
gdm logon screen and ubuntu desktop theme color inconsistency
https://bugs.launchpad.net/bugs/553835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
Binary package hint: gdm
The gdm theme uses light gray panels and input boxes. However, the
default Lucid theme is "Ambiance", a very dark theme. Seems very
unprofessional that the panel colors in the logon screen do not match
the panel colors in the "Ambiance" theme. It w
Public bug reported:
Apologies for filing against 'ubuntu-desktop'. I am unsure what package
contains the restricted driver applet. Please redirect as necessary.
After performing a clean installation, Ubuntu notifies me that
"restricted drivers are available". I click the tray icon and am take
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42864463/Dependencies.txt
--
"proprietary driver are in use" when no prop drivers are installed
https://bugs.launchpad.net/bugs/553842
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Public bug reported:
Binary package hint: plymouth
While using the 'nouveau' driver during live CD installation, or after
installation, plymouth displays the very pretty rebranded ubuntu logo at
my native resolution, and supports a clean transition into the gdm logon
screen.
As soon as I install
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42864960/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42864961/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42864962/Dependencies.txt
** A
Public bug reported:
Binary package hint: compiz
On a clean installation of Lucid from 20100331.2 daily Live CD, I
attempted to enable "Extra" visual effects from the Appearance
Preferences window. Ubuntu searched for drivers, and then installed the
nvidia 173 driver, rather than the current ver
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42866264/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42866265/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42866266/Dependencies.txt
** A
Public bug reported:
Binary package hint: htop
htop displays a list of keyboard shortcuts along the bottom of the
screen. 'F10' allegedly closes htop, but this is impossible from
Ubuntu's Terminal window, which captures the F10 key to open the menu.
In testing, I found the F10 key inconsistentl
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42866650/Dependencies.txt
--
'F10' keystroke captured by Terminal window
https://bugs.launchpad.net/bugs/553864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yup, had to install 20100326 plus daily updates. Only then did it
accept the VirtualBox Guest Additions.
--
X Fails to start once VirtualBox Guest Additional Drivers is installed
https://bugs.launchpad.net/bugs/540015
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Still reproduces with 20100326 live CD.
Again, disconnect second display, and I'm able to get into X.
Is anyone looking at this? What further information can I provide?
--
nvidia card: hangs on start gdm if a second monitor on DVI-I is present
https://bugs.launchpad.net/bugs/43710
You received
I'll do that later tonight when I get some free time. If someone beats
me to it, please comment here and drop the Bug# in this thread so I can
folllow.
--
nvidia card: hangs on start gdm if a second monitor on DVI-I is present
https://bugs.launchpad.net/bugs/43710
You received this bug notificat
Reproduced issue on Geforce 9600 GT using Lucid daily live CD
(20100317).
Hangs at the new Ubuntu branded boot screen with second monitor connected.
Disconnected second monitor and successfully completed the installation.
--
nvidia card: hangs on start gdm if a second monitor on DVI-I is present
I can confirm the following:
I can clean install Alpha 3 from ISO, install the Guest Additions and
reboot without repro. I can then apply updates from the daily fire
hose, and hit the issue.
I just reproduced this with Beta 1 -- because it includes all the
updates already, the issue reproduces a
This occurred immediately after setting up my existing Ubuntu One
account from the Me menu on Lucid Beta 1.
--
desktopcouch-service crashed with SIGSEGV
https://bugs.launchpad.net/bugs/524566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Reproduced on Lucid Beta 1.
--
Nautilus crashes when there are multiple XScreens
https://bugs.launchpad.net/bugs/508890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Reproduced on Lucid Beta 1. I told Launchpad that this is the same bug,
so hopefully it linked my trace to this bug for further triage.
--
ubuntuone-login crashed with SIGSEGV in dbus_watch_handle()
https://bugs.launchpad.net/bugs/536758
You received this bug notification because you are a membe
I just received the updated nautilus package and confirmed this resolved
my issue. Thanks for looking into this!
--
Nautilus crashes when there are multiple XScreens
https://bugs.launchpad.net/bugs/508890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I ran into this error after doing an unclean shutdown on my Thinkpad
T400 running ubuntu 9.04. After restarting my machine, I was seeing
errors in evolution and it was unable to load my inbox. The error was:
"Error while opening store spooldir://var/spool/mail -- database disk
image is malformed."
Public bug reported:
jason-1204:~:% lsb_release -rd
Description:Ubuntu precise (development branch)
Release:12.04
--
While applying today's updates, my wallpaper setting (which was simply
set to the time-rotating wallpapers provided with the distribution) was
wiped out and set to a p
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974776
Title:
User-configured wallpaper setting wiped out after today's updates
To manage notifications about this bug go to:
https://bugs.launchpad.net
Grah, I just realized I have a completely new set of wallpapers. I
guess that's why they went missing.
I would hope this would be handled more gracefully, but since the
wallpapers are not going to be moved, removed, updated or replaced after
release, I suppose there isn't much of a bug here.
--
I filed this against gnome-shell, but I just applied today's updates to
a VM with Unity:
After installing the updates, the Unity bar (and dash, when exposed)
turned purple.
After a reboot, the wallpaper was now black.
Would be interesting to see if other user profiles on the same machine
would a
Public bug reported:
I'm running Ubuntu Desktop 12.04 64bit on an HP Elitebook 2760p. This
occurs under Unity and gnome-shell, and I imagine any other DE. I am
not sure what software provides the functionality I am discussing below,
so please assign the bug accordingly.
What is expected: When
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973133
Title:
Finger touch input is not registered correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/973133
This appears to be resolved. Thunderbird is now the default email
client in Ubuntu (since 11.10?) and it works with the notifications as
expected. Shall we close this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
After logging out, the login screen did not respond to touch at all.
After rebooting, the login screen responded to touch as expected, but
reverted to "relative" mode after logging in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Just did today's updates and this appears to be resolved. Can someone
else confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949097
Title:
Serial Wacom Tablet touch not in absolute mode when l
Public bug reported:
from 'lspci':
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
Was using DOSBox earlier and I noticed that vsync was not enabled. I
can also see vsync is not enabled while I type at the termina
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973971
Title:
vsync is not enabled, despite what CCSM tells me
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/9739
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973979
Title:
gnome-shell incorrectly renders desktop viewport
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/g
Public bug reported:
Description:Ubuntu precise (development branch)
Release:12.04
--
Sometimes, gnome-shell incorrectly renders the desktop viewport. This
most recently happened when I moved a terminal window into a new
workspace using the CTRL+ALT+SHIFT+Down keyboard shortcut. (I
So, is libnotify-mozilla the code that will eventually ship with Natty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367175
Title:
thunderbird not using indicator applet
--
ubuntu-bugs mailing li
Would love to see this in GNOME 3.6. How do we apply pressure upstream
from here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969796
Title:
screencast recording does not record sound
To manage n
Just reproduced this on my netbook (an installation of 12.04 current
with today's updates).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973979
Title:
gnome-shell incorrectly renders desktop viewpo
*** This bug is a duplicate of bug 964796 ***
https://bugs.launchpad.net/bugs/964796
Yes, please re-evaluate: This issue does not correct itself after a few
seconds, it lasts the remainder of the user session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
It already appears to be enabled: "Synchronization with vertical
refresh (swap intervals)" is set to "Always synchronize with vertical
refresh, application chooses the minimum swap interval".
I tried setting it to both "Initial swap interval 0/1" settings, but all
three settings gave the same vis
I am on the PPA. I applied updates and I seem to have regained the
power meter.
On 4/6/2013 1:13 PM, Jeremy Bicha wrote:
> Are you using the GNOME3 PPA? Is the power menu still missing after
> installing updates and rebooting?
>
> ** Changed in: gnome-power-manager (Ubuntu)
> Status: Con
Public bug reported:
After installing yesterday's Ubuntu GNOME 13.04 daily image, I had a
power indicator, but somewhere between completing the installation and
now, I've lost it. I have installed a few other applications, but
nothing I would expect to interfere. All extensions have been disable
Public bug reported:
-- lsb_release -rd
Description:Ubuntu precise (development branch)
Release:12.04
--
-- apt-cache policy mdadm
mdadm:
Installed: 3.2.3-2ubuntu1
Candidate: 3.2.3-2ubuntu1
Version table:
*** 3.2.3-2ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ pre
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964052
Title:
mdadm: created as /dev/md0, becomes /dev/md127 after reboot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
'mdadm.conf.txt' shows some manually made changes I was attempting to follow
after reading this thread:
http://ubuntuforums.org/showpost.php?s=b6e090eae70ded837a35d33a855bf21b&p=11623570&postcount=22
However, the alterations have no effect on the end result. mdadm still
reassembles the array as
Reinstalling from the same ISO, I used guided partitioning to completely
wipe the root partition and reinstall the system. At the same time, I
also told it to mount the array.
After installation, my array is mounted and I see this in /etc/fstab:
# /media/raid was on /dev/md0 during installation
I had a question in IRC (#ubuntu+1) about what the untouched mdadm.conf
looked like after building the array but before I altered it. To undo
the changes I made, simply remove the commented and uncommented "DEVICE"
lines.
Again, this change had no visible effect on how the array was
reassembled.
Canonical has no interest in reverting Plymouth, and cannot force Nvidia
or ATI to add the required hooks to their drivers. Nothing else needs
to be said about this, so please give 140 inboxes a rest. If this still
bothers you, go contribute your time to another project, as I did.
--
You receiv
Please stop this endless barrage of "me too" with no real content. We
have enough reports from enough people on enough adapters, I'm sure that
whatever the next one is isn't going to bring us any closer to a
solution.
Every time you "me too" reply, you spam everyone who is subscribed to
the bug.
69 matches
Mail list logo
