Public bug reported:
Steps to reproduce:
1) Run the command unity-control-center color in a terminal, to open the
Color profile management dialog
2) Click Add profile
3) Select Other profile... from the drop down list
4) Select the ICC color profile attached to this bug report
5) Click Add
Public bug reported:
When installing Ubuntu 14.04 on my machine, the installation fails at
the step where GRUB is installed onto the disk. I got a message saying
something like:
Installation of GRUB to disk /dev/sdd failed. This is a fatal error.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
By the way, I think this is the relevant part of the log:
Apr 9 14:38:09 ubuntu grub-installer: info: Installing grub on
'/dev/sdd'
Apr 9 14:38:09 ubuntu grub-installer: info: grub-install does not
support --no-floppy
Apr 9 14:38:09 ubuntu grub-installer: info:
I was able to fix this issue the following way.
Apparently, my motherboard (ASUS M5A97 EVO R2.0) can boot a USB drive in
two ways:
1) using UEFI
2) using the standard way (BIOS?)
I originally booted the Ubuntu 14.04 USB installation drive using UEFI
(I didn't realize there would be a
Here are some relevant lines from syslog:
Aug 27 14:27:23 rune-desktop kernel: [1.943848] md: bindsdb1
Aug 27 14:27:23 rune-desktop kernel: [1.958267] md: bindsdc1
Aug 27 14:27:23 rune-desktop kernel: [2.036123] md: bindsdd1
Aug 27 14:27:23 rune-desktop kernel: [
Public bug reported:
For some reason, a functioning RAID1 array that contains a RAID0 array
as a member does not properly assemble after rebooting.
Before rebooting, when everything is running fine, this is what
/proc/mdstat looks like:
rune@rune-desktop:~$ cat /proc/mdstat
Public bug reported:
I create an armhf container using the following command:
sudo lxc-create -n armhf01 -t ubuntu — -a armhf -r precise
I then start it like so:
sudo lxc-start -n armhf01
It boots up, shows a lot of
process name main process terminated with status num
messages
** Attachment added: Debug output file from running the command sudo
lxc-start -n armhf01 -l debug -o output
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1183429/+attachment/3684945/+files/outout
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
I create an armhf container using the following command:
sudo lxc-create -n armhf01 -t ubuntu — -a armhf -r precise
I then start it like so:
sudo lxc-start -n armhf01
It boots up, shows a lot of
process name main process terminated with status num
messages
** Attachment added: Debug output file from running the command sudo
lxc-start -n armhf01 -l debug -o output
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1183429/+attachment/3684945/+files/outout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can't reproduce this bug on Raring either, using either ppa:deluge-
team/ppa or ppa:gnome3-team/gnome3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789859
Title:
add-apt-repository adds invalid
Bitcoin 0.8 is available in the following PPA, although not for Raring.
I'm not completely sure how the process of pulling in updated packages
works for Ubuntu. If Bitcoin 0.8 for Raring is added to the following
PPA, is it simply a matter of pulling it in from there, or is there more
work
Public bug reported:
I'm currently experiencing a bug in strace 4.5.20 running on an armhf
system: https://bugs.launchpad.net/chromebook-arm/+bug/1098163
This bug is fixed in strace version 4.7. Please pull in version 4.7 of
strace for Raring.
4.5.20 was released in April 2010, so it's almost
Public bug reported:
Upon startup of the system I notice the CPU usage is very high, and
top reveals that it is evolution-calendar-factory that is using 100%
CPU. Attaching to the process via gdb causes it to exit, producing the
following output (though I'm not sure how relevant it is, since
Upon further research, it appears that the applet in question loads
x86-specific binaries for execution.
The file DanID_Applet.jar contains an x86 ELF file disguised as a GIF
file:
error.gif: ELF 32-bit LSB shared object, Intel
80386, version 1 (SYSV), dynamically linked,
Upon further research, it appears that the applet in question loads
x86-specific binaries for execution.
The file DanID_Applet.jar contains an x86 ELF file disguised as a GIF
file:
error.gif: ELF 32-bit LSB shared object, Intel
80386, version 1 (SYSV), dynamically linked,
** Bug watch added: Iced Tea Bugzilla #1248
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1248
** Also affects: icedtea via
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1248
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Public bug reported:
When going to the site https://www.portalbank.dk/6610/ the plugin on the
site fails to load. I'm attaching the terminal output from firefox to
the report.
Other plugins, like the Java test applet
http://www.java.com/en/download/testjava.jsp works fine on the system.
** Description changed:
When going to the site https://www.portalbank.dk/6610/ the plugin on the
site fails to load. I'm attaching the terminal output from firefox to
the report.
Other plugins, like the Java test applet
http://www.java.com/en/download/testjava.jsp works fine on the
** Description changed:
STEPS TO REPRODUCE:
1. Add the PPA, that contains a slash, with add-apt-repository:
sudo add-apt-repository ppa:deluge-team/ppa
- 2. Removing the PPA with ppa-purge
+ 2. Removing the PPA with ppa-purge:
sudo ppa-purge ppa:deluge-team/ppa
- 3. Again, add the PPA
My problem was that Ubuntu kept trying to connect to WLANs that I didn't
have the key for, but I was unable to change the Connect automatically
option for these WLANs. I resolved this by deleting all the WLANs that I
didn't have the key for, so that only one WLAN - for which I have the
key -
This is, seemingly, caused by a corrupt database journal file:
https://bitcointalk.org/index.php?topic=1993.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812275
Title:
bitcoind fatal error on
No, not as far as I have experienced. The presence of the ain line is
the only thing that is causing the issue, removing it fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789859
Public bug reported:
As it is now, when using nautilus to copy files from a directory
residing on an NTFS partition to another directory residing on an NTFS
partition, file attributes (like 'hidden', 'system') are lost. This can
be fixed by using ntfscp (from the ntfsprogs package) to copy files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829408
Title:
Nautilus should preserve NTFS file attributes when copying from NTFS
to NTFS file system
To manage notifications about this bug go to:
I have started to experience this in Natty as well. Normally only from a
cold boot though; upon restarting, the issue is gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/441653
Title:
radeon
It turns out we don't have to install anything, in order to reproduce
this bug. Simply:
1. Adding the PPA with add-apt-repository
2. Removing the PPA with ppa-purge
3. Again, adding the PPA with add-apt-repository
reproduces this error.
I'm attaching a terminal log that shows how the third step
*** This bug is a duplicate of bug 789859 ***
https://bugs.launchpad.net/bugs/789859
** This bug has been marked a duplicate of bug 789859
if PPA contains a forward slash, when adding an already added, but disabled
PPA, add-apt-repository adds invalid deb line to sources file
--
You
*** This bug is a duplicate of bug 789859 ***
https://bugs.launchpad.net/bugs/789859
** This bug has been marked a duplicate of bug 789859
if PPA contains a forward slash, when adding an already added, but disabled
PPA, add-apt-repository adds invalid deb line to sources file
--
You
*** This bug is a duplicate of bug 789859 ***
https://bugs.launchpad.net/bugs/789859
** This bug has been marked a duplicate of bug 789859
if PPA contains a forward slash, when adding an already added, but disabled
PPA, add-apt-repository adds invalid deb line to sources file
--
You
** Description changed:
+ STEPS TO REPRODUCE:
- STEPS TO REPRODUCE:
- Long way:
- 1. Install oibaf's mesa PPA using add-apt-repository:
- sudo add-apt-repository ppa:oibaf/graphics-drivers
- sudo apt-get update
- sudo apt-get dist-upgrade
- 2. Remove this PPA with ppa-purge:
- sudo ppa-purge
I tried to test this on a Oneiric live CD, but I was unable to get to a GNOME
session to test it.
If someone knows how to achieve this, please provide some instructions.
I tried the Classic Guest session option (from the Power(button) menu),
this seemed to have no effect. Logging out of the
Public bug reported:
STEPS TO REPRODUCE:
Long way:
1. Install oibaf's mesa PPA using add-apt-repository:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get dist-upgrade
2. Remove this PPA with ppa-purge:
sudo ppa-purge ppa:oibaf/graphics-drivers
3. Add the PPA
** Attachment added: sources.list.d.tar.gz
https://bugs.launchpad.net/bugs/789859/+attachment/2146771/+files/sources.list.d.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789859
Title:
Note, this behavior is also described in Bug #640784, but this was
allegedly fixed and the bug was closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789859
Title:
add-apt-repository adds
I am unable to test this because of bug #36563 in mesa:
https://bugs.freedesktop.org/show_bug.cgi?id=36563. Perhaps they're related?
I will test this again when the mesa bug is fixed.
** Bug watch added: freedesktop.org Bugzilla #36563
http://bugs.freedesktop.org/show_bug.cgi?id=36563
--
Note. The link to launchpad bug number 36563 in the previous comment has
nothing to do with this. It's bug number 36563 on freedesktop's bug
tracker (in mesa).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I experience the same issue, but for me it doesn't happen on every boot, only
occasionally.
I'm attaching my /var/log/boot.log which claims there are several problems,
both with the swap disk (which seems to work fine) and with a disk that is a
RAID array (which is present when I get to a
I agree with Franco in #24; this is solved by using the version of
telepahy and empathy in the Telepathy PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/631428
Title:
Empathy doesn't apply
** Bug watch added: Iced Tea Bugzilla #663
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=663
** Also affects: openjdk via
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=663
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
Steps to reproduce:
Go to the site www.borger.dk. Click the Log ind link in the upper right
corner. Click the Log på med Digital Signatur tab on the page that appears.
What happens:
The applet that is supposed to appear, to enable log in via digital signature,
is a grey
** Attachment added: Output of running 'firefox log.txt 21' in terminal
https://bugs.launchpad.net/bugs/728602/+attachment/1883405/+files/log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could people experiencing this bug please specify which of these three
error messages you receive when you try to open your file (from gedit-
io-error-message-area.c):
gedit has not been able to detect the character encoding.
Please check that you are not trying to open a binary file.
Select a
Public bug reported:
Binary package hint: gedit
1. Steps to reproduce:
sudo apt-get build-dep gedit
apt-get source gedit
cd gedit-2.30.3/
./configure
make
2. What happens:
make fails with the following error:
./.libs/libgedit.a(gedit-window.o): In function `create_menu_bar_and_toolbar':
** Attachment added: Log from issuing steps to reproduce
https://bugs.launchpad.net/bugs/722555/+attachment/1863868/+files/gedit-build.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722555
Thank you for that information, I was not aware of that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722555
Title:
fails to build from source with error: undefined reference to
The bug is gone after upgrading to bzr1505. Also, I have upgraded to Maverick
since, not sure if this has had any influence.
Thanks!
** Changed in: awn-extras
Status: Incomplete = Fix Released
** Changed in: awn-extras (Ubuntu)
Status: New = Fix Released
--
You received this bug
Public bug reported:
Using AWN from the AWN testing PPA:
rune@runescomp:~$ apt-cache policy awn-applets-python-core-trunk
awn-applets-python-core-trunk:
Installed: 0.4.1~bzr1504+201101250003~lucid1
Candidate: 0.4.1~bzr1504+201101250003~lucid1
Version table:
***
I have put up a package in my PPA with Wine 1.3 with the most recent WinePulse
patches (as of 2010-01-25) if there are people interested in testing:
https://launchpad.net/~runeks/+archive/winepulse/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: wine
I posted this in the questions-department, and was asked to report a
bug, so I'm moving my request here.
After experiencing a sound issue with a game running Wine from the
Ubuntu Wine PPA, I tried compiling the latest Wine from the Ubuntu Wine
PPA
I think I gave found out why this is the case. The output of the command
wodim -prcap dev=/dev/scd1 says, amongst other things, the following:
Maximum read speed: 8450 kB/s (CD 48x, DVD 6x)
Current read speed: 178 kB/s (CD 1x, DVD 0x)
Maximum write speed: 8450 kB/s (CD 48x, DVD
Public bug reported:
Binary package hint: brasero
When I try to burn a CD with brasero, be it an audio CD or an image, the
only speeds I can select are maximum and 47.9x (which is practically
maximum).
I remember being able to burn at lower speeds a couple of years ago, so
I'm not sure what has
--
Only available recording speeds are maximum and 47.9x
https://bugs.launchpad.net/bugs/668330
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
Hi Jools
Thanks for updating the package for Lucid. I have installed it without any
issues. I attach a log of the output of dpkg.
** Attachment added: Output of sudo dpkg -i mdadm_3.1.4-1_i386.deb
Other components are now available to provide support for SMART status.
I'm marking this as invalid.
** Changed in: ubuntu
Status: New = Invalid
--
[needs-packaging] gnome-disk-health
https://bugs.launchpad.net/bugs/405291
You received this bug notification because you are a member of
Other components are now available to provide support for SMART status.
I'm marking this as invalid.
** Changed in: ubuntu
Status: New = Invalid
--
[needs-packaging] gnome-disk-health-service
https://bugs.launchpad.net/bugs/405285
You received this bug notification because you are a
This is no longer an issue for me either, using the kernel from the
Ubuntu Kernel PPA:
r...@runescomp:~$ uname -a
Linux runescomp 2.6.35-19-generic #25~lucid1-Ubuntu SMP Wed Aug 25 04:24:28
UTC 2010 i686 GNU/Linux
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Fix
I have another bit of information to add to this bug report.
I just tried booting the presumably faulty USB stick on a third computer
with the same results. So all signs point to the USB stick as the cause
for this. I also tried booting another USB stick, to which the the same
ISO file has been
I just experienced this error, and it seems to be caused by a faulty USB
stick.
I downloaded a daily build of Maverick, and confirmed that the md5 sums
matched. This image was written to a USB stick using the Startup Disk Creator.
I first booted this USB stick on a laptop and got the error, then
Public bug reported:
Binary package hint: plymouth
If the default display resolution and refresh rate that the kernel should use,
is specified with the video kernel option/parameter, plymouth does not use
this resolution for the boot splash screen.
The virtual terminals use this resolution and
** Attachment added: Content of the file /etc/default/grub
https://bugs.launchpad.net/bugs/622824/+attachment/1513272/+files/grub
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/622824/+attachment/1513273/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
If one wishes to increase the likelihood of this bug being fixed, it's
possible to vote for this bug, by visiting Wine's bug tracker at the
URL below, clicking the vote link under Importance, and following
the instructions on the page that appears. A registration is required
though (but it takes,
62 matches
Mail list logo
