Public bug reported:
Binary package hint: grub2
After a fresh install of Natty on my new PC I noticed that upon booting
the characters of grub and the 'scrolling list of messages' were
completely illegible. Updates were made but it only showed white blocks
where there should be messages. Boot up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797543
Title:
Grub2 and tty characters illegible white blocks
To manage notifications about this bug go to:
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/18771453/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18771454/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/18771455/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: ubuntu-artwork
Hello,
I really like the new dark themes in Ubuntu, however they make working
with GTK1 apps impossible, see the attached screenshot of a window in
GRASS.
This applies to both the Darlooks as well as the DarkRoom themes.
The normal
** Attachment added: Illegible text for GTK1
http://launchpadlibrarian.net/18771693/Screenshot-g.list.png
--
Darkroom and Darklooks make GTK1 apps unreadable
https://bugs.launchpad.net/bugs/287065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can confirm this problem on Ubuntu Hardy. However, the solution
provided by Onno by adding local port 1 solved it instantly. So
maybe it is just a documentation problem? (It took me quite a bit of
digging to find this).
--
no response from target with 0.4.0(1.1) but not with 0.3.3
Hi,
I have the same problem. When opening some (not all) apps they go back
to gtk1 (I think) widgets. Giving the following errors:
~$ bluetooth-properties
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181: Invalid symbolic color
'tooltip_bg_color'
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181:
I can also confirm that changing the fix proposed by Kristian works.
--
Darklooks gtkrc is broken [hardy]
https://bugs.launchpad.net/bugs/215472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This was using
sudo do-release-upgrade
from the command line. I know updated it using
update-manager -d
and that worked ok (no sound and the python2.4 deinstallation gave
errors. Furthermore it was impossible to complete the installation using
only my bluetooth keyboard and mouse as these were
Public bug reported:
Binary package hint: update-manager
On my desktop install I removed all local packages and packages from
other sources than official ubuntu sources.
Still the upgrade fails, I think because of a conflict of
esound/pulsaudio as seen here from the apt.log:
Package
Also added main.log from /var/log/dist-upgrade/
** Attachment added: main.log
http://launchpadlibrarian.net/13352263/main.log
--
Update manager fails [gutsy-hardy]- an unresolvable problem occurred while
calculating the upgrade
https://bugs.launchpad.net/bugs/215554
You received this bug
** Attachment added: apt.log
http://launchpadlibrarian.net/13352257/apt.log
--
Update manager fails [gutsy-hardy]- an unresolvable problem occurred while
calculating the upgrade
https://bugs.launchpad.net/bugs/215554
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: gdal-bin
The new version of gdal as seen here:
http://trac.osgeo.org/gdal/wiki/Release/1.5.0-News
Has been uploaded into debian:
http://packages.qa.debian.org/g/gdal.html
There are many new drivers in this package which are essential to
compete with
I can confirm this on a fresh install of Gutsy as well. Also each time
after it went to screensaver it would have lost the connection.
However, using the suggestion from:
https://help.ubuntu.com/community/BluetoothMouse
More specifically:
1. Edit the file /etc/default/bluetooth: sudo
The same happens here. With a dual screen setup the second monitor is
correctly displayed at 1280x1024, but the first monitor has a virtual
resolution of 1600x1200, causing scrolling.
Every time I run the displayconfig-gtk utility and press OK, it changes
all my xorg.conf settings completely,
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7131280/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7131281/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7131282/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: duplicity
I am trying to get duplicity to backup my files to my (public) http
server on a remote location. However I keep getting this error message.
ProblemType: Crash
Architecture: i386
Date: Tue Apr 3 20:37:52 2007
DistroRelease: Ubuntu 7.04
David,
Since that time I have changed a lot to my xorg.conf (installing beryl,
twinview) and at this moment I can't seem to be able to reproduce it. I
consider it closed.
Good luck with the bug squashing!
Roderik
On 12/4/06, David Farning [EMAIL PROTECTED] wrote:
Roderikk,
Are you still
18 matches
Mail list logo
