** Changed in: anjuta (Ubuntu)
Sourcepackagename: None => anjuta
--
anjuta can not be installed
https://bugs.launchpad.net/bugs/157563
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively" [WWW]
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
This bug report is being closed due to your last comment regarding this
being solved. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug statu
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
- Do you have crossfader activated in Rhythmbox (Edit -> Preferences ->
Playback)?
- If crossfader was active, can you disable crossfader and try to play the m4a
files again?
Pleas
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Please run the command
$cat /etc/timezone
and add the output to this bug report
* Please run the command
$sudo zdump -v /etc/localtime | grep 2007
and add the output to th
Thanks for the reply VLK. That output looks good. Can you please confirm if
your clock is still wrong? If so, can you please add the full output of the
command: date and the correct time to the bug report?
If the clock is now correct, did you change any settings?
--
Ubuntu did not set the Wint
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Please include the following additional information, if you have not already
done so (pay attention to lspci's addition
Thanks for the reply zach. Can you please confirm if you restarted
Rhythmbox after you disabled crossfader? If you didn't, can you please
restart rhythmbox and try again?
--
M4a sound like a skipping cd
https://bugs.launchpad.net/bugs/157946
You received this bug notification because you are a me
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer this question:
* How many rows and columns do you have for the workspaces applet? (right click
on the workspace applet, then choose preferences)
* If you set columns to 4 and rows to 1, does that giv
** Summary changed:
- "Sélecteur d'espaces de travail" est devenu très petit
+ Workspace Switcher has become very small
** Description changed:
+ English translation of below original report:
+ I have 4 workspaces, but the Workspace Switcher (next to the trash bin) does
not take more then half
@Lieven:
Yes, ntp is working. I use it as well, and for me it did change the clock back
from summer to winter time, as my syslog shows:
Oct 28 11:17:44 ubuntu ntpdate[4086]: step time server 193.79.237.14 offset
-3599.771174 sec
- When you switched on your PC, did you have an active Internet co
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* please run the command
$ uname -a
and paste the result in this bug report
* please run the command
$ dpkg -l linux* > image.txt
(where l is the lowercase L, not the dig
Thanks for your reply. Unfortunately, I cannot reproduce this problem.
Can you please remove the workspace switcher from the bottom panel (right click
on the workspace switcher, then remove from panel)
Then add the workspace switcher again to the panel (right click on the bottom
panel, then add t
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete => Confirmed
--
Resume from suspend fails on 2.6.22-14-generic
https://bugs.launchpad.net/bugs/158050
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Thanks Camille, good to hear it's working now.
Since your problem has been solved and we both don't know how to reproduce the
problem, I will close this bug report. Thank you again for taking the time to
report this bug and helping to make Ubuntu better. Feel free to submit any
future bugs you m
@Max: your syslog shows the ntp server you selected is not valid anymore:
Oct 29 13:56:38 localhost ntpd_initres[20088]: host name not found:
ntp.landau.ac.ru
Please select another ntp server to solve your problem (e.g. the one you used
for ntpdate should be ok).
@Laco: in your case the ntp serv
*** This bug is a duplicate of bug 156778 ***
https://bugs.launchpad.net/bugs/156778
Benson,
the last two lines in your sources.list are not correct:
deb http://archive.ubuntu.com/ubuntu/ restricted main multiverse universe
deb-src http://archive.ubuntu.com/ubuntu/ restricted main multiverse
Thanks for the reply richard.
The kernel you are currently using does not support dual core / multi
processors. For dual core you need an SMP kernel, which in Ubutu has a name
ending in -generic (instead of -386 you have now). The list you attached shows
you do have a generic kernel for Gutsy in
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Do you use dhcp to get an IP address for your network connection?
* Can you please attach the file /var/log/syslog? Please make sure the syslog
includes a reboot.
This will help u
I just experience (an hour ago) the same problem during the installation
of xubuntu-7.10-alternate-i386.iso (release date: 09-Oct-2007 21:36), on
my ibm r50e laptop with Intel 855GM video chipset. The trick is to wait
for the hard drive & cd-rom drive activity to stop and just press
enter.
--
Al
*** This bug is a duplicate of bug 152256 ***
https://bugs.launchpad.net/bugs/152256
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This particular bug has already been reported and is a duplicate of bug
152256, so it is being marked as such. Please look
Thank you for taking the time to report this bug and helping to make Ubuntu
better. It looks like your problem may be related to bug 145012, which was
solved recently. Could you please try to do the installation using the Release
Candidate CD an report if that works correctly?
Many thanks in adv
*** This bug is a duplicate of bug 152185 ***
https://bugs.launchpad.net/bugs/152185
** This bug has been marked a duplicate of bug 152185
K3B refuses to close
--
K3B refuses to close
https://bugs.launchpad.net/bugs/152186
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 129910, so it is being marked as such. Please look at
existing
libsensors configurations
* Add postinst script with warning that the applet needs reinstalling
in the panels for the change to take effect
-- Albert Damen <[EMAIL PROTECTED]> Wed, 10 Oct 2007 21:36:35 +0200
** Changed in: sensors-applet (Ubuntu)
Status: Fix Committed
Thanks for your response. I will mark this bug as fixed released for now.
Please feel free to re-open it (set status to new) in case you might find the
problem was not solved after all.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Fix Released
--
Kunbuntu 7.10 Beta ubiquity ins
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs
This seems to be a duplicate of bug 144956. That problem was fixed shortly
after the release of Gutsy Beta.
Could you please test again with the Release Candidate version?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
** Changed in: xorg (Ubuntu)
Status
It looks like fsck wants to check another partition, but fails to do so.
Can you please list the partitions you have on your system and what is
on it (i.e. windows or other linux versions). If you know, please add
the filesystem (i.e. ntfs, fat, linux) type to the list.
Secondly, can you please tr
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
I had the same problem. I fixed it by editing the script
/etc/init.d/vboxdrv and commenting out a line in the stop function:
stop()
{
log_daemon_msg "Stopping VirtualBox kernel module" "$MODNAME";
- killall -q VBoxSVC
+ #killall -q VBoxSVC
if running; then
Apparently the script failed becaus
*** This bug is a duplicate of bug 49613 ***
https://bugs.launchpad.net/bugs/49613
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 49613, so it is being marked as such. Please look at
th
*** This bug is a duplicate of bug 152376 ***
https://bugs.launchpad.net/bugs/152376
dAniel, this is happening when version 6 gets installed. This is
complete log:
/var/cache/apt/archives/virtualbox-ose-modules-2.6.22-14-generic_6_amd64.deb:
subprocess new pre-removal script returned error e
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
The problem you see seems to be the standard Linux implementation for packets
send to the local system, see
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.1/2205.html.
Can you please test to send the packet t
Fixed in Gutsy (3.2.3-2ubuntu3)
valgrind (1:3.2.3-2) unstable; urgency=low
* debian/patches/03_valgrind-libc6-2.6.dpatch:
- Patch based on Gentoo's to make valgrind compiles under glibc 2.6.
Thanks to [EMAIL PROTECTED] (Closes: #433899)
** Changed in: valgrind (Ubuntu)
Status
I have got confirmation from
https://answers.launchpad.net/ubuntu/+question/15207 that the -proposed
package solves the DST issue for Brazil.
--
Brazilian DST date change needs upgrade to 2007h
https://bugs.launchpad.net/bugs/152113
You received this bug notification because you are a member of U
zeddock, you may want to read this: https://wiki.ubuntu.com/Bugs/Status
Triaged is actually a better status then confirmed, so you shouldn't change a
status back from triaged to confirmed.
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bu
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Can you please run the command:
cat /etc/udev/rules.d/70-persistent-net.rules > udev.rules
and attach the file udev.rules as attachment to this bug report?
** Changed in: ubuntu
Status: New => Incomplete
*** This bug is a duplicate of bug 147070 ***
https://bugs.launchpad.net/bugs/147070
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This particular bug has already been reported and is a duplicate of bug
147070, so it is being marked as such. Please look
There already is a package called packaging-guide:
The Ubuntu Packaging Guide
This package holds the official Ubuntu Packaging Guide. The guide can
be viewed using an html browser.
Alternatively you can find a pdf at
https://help.ubuntu.com/6.06/pdf/ubuntu/C/packagingguide.pdf
Does that solve t
dennda, this sounds much like bug 129910, although that only mentions the black
screen in the consoles, not the stripes.
Could you check from gnome terminal if the tty's are active (i.e. with ps ax |
grep -i tty)?
Also, you can try to login on tty1 blindly. Then ps ax would show if you are
logge
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
No problem dennda, and thanks for the confirmation!
--
tty1-6 don't work in gutsy
https://bugs.launchpad.net/bugs/148746
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Thank you for taking the time to report this bug and helping to make Ubuntu
better. However, I am closing it because the bug has been already been fixed.
You should already be able to upgrade to pidgin 2.2.1.
Today I received version 2.2.1-1ubuntu3
** Changed in: pidgin (Ubuntu)
Status: N
Bryce, I don't have this problem myself, I just did triage.
--
resolution out of sync with version 2:1.3.0.0.dfsg-12ubuntu8
https://bugs.launchpad.net/bugs/147846
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
That sounds like a valid wishlist item.
Please note there recently has been some discussion about the packaging guide
in https://lists.ubuntu.com/archives/ubuntu-motu/2007-September/thread.html
** Changed in: ubuntu
Status: Incomplete => Confirmed
** Summary changed:
- provide a download
With kernel 2.6.22-13 I can get the tty's working again with:
sudo modprobe fbcon
sudo modprobe vga16fb
You may need to press enter to see the tty is really working again.
(Intel GM965, AMD64)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received
** Changed in: ubuntu-docs (Ubuntu)
Sourcepackagename: None => ubuntu-docs
--
provide a link to the downloads of the packaging guide
https://bugs.launchpad.net/bugs/148714
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
I did a fresh install of Gutsy today, using the daily CD 20071006.2 This still
gave the wrong unit A instead of C. After changing the applet settings in
gconf-editor, setting the sensor type to 2 instead of 0, and restarting gdm
this problem was solved. The attached picture shows the settings a
urho: the problem with m4a and crossfader is bug 138728 (m4a files
playback choppy with crossfading on) and has been reported to and
confirmed by upstream.
Антон Иванов: can you please advise if you have crossfading enabled
(Edit -> Preferences -> Playback)? From the trace you attached it looks
li
In Gutsy Beta, daily updated, I can reproduce the crash only when compiz
is enabled and gstreamer is configured to use xv output. Without compiz
or with compiz / non-xv output, visualization works fine. I also have an
Intel x3100 (GM965). As the x3100 has been blacklisted for compiz, this
bug shoul
I think Gutsy already has a good working alternative: computertemp. That
worked fine out-of-the-box and, in my opinion, has nicer icons.
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.net/bugs/147188
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 147943 ***
https://bugs.launchpad.net/bugs/147943
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 147943, so it is being marked as such. Please look at
I could reproduce this problem with ekiga 2.0.9. The problem is solved in ekiga
2.0.11, but the upgrade to 2.0.11 has been "hanging" in update-manager for more
then a week. It turned out there is a dependency problem: libopal-2.2.0 was
installed on my system, but the new ekiga depends on libopal
I guess this may be the same problem with libopal versions found in bug
150168.
--
package ekiga 2.0.11-1ubuntu1 failed to install/upgrade: subprocess
post-installation script returned error exit status 134
https://bugs.launchpad.net/bugs/147933
You received this bug notification because you are
I think this report is indeed outdated. apt-get source ekiga today
downloaded ekiga 2.0.11, which built fine in pbuilder.
--
autopkgtest gutsy ekiga: erroneous package!
https://bugs.launchpad.net/bugs/144496
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Can you please confirm if you filed a bug at Debian for this, so we can
add a tracker here? I think it may be http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=444825 Is that right?
--
Upgrade busybox
https://bugs.launchpad.net/bugs/145484
You received this bug notification because you are a mem
** Also affects: busybox (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444825
Importance: Unknown
Status: Unknown
--
Upgrade busybox
https://bugs.launchpad.net/bugs/145484
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
*** This bug is a duplicate of bug 147943 ***
https://bugs.launchpad.net/bugs/147943
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 147943, so it is being marked as such. Please look at
Same problem here. Unpacking the update-notifier 0.60 package shows the problem:
in usr/share/gconf/schemas/update-notifier.schemas line 7 reads:
false/default>
So the end tag on line 7 is not correct.
** Changed in: update-notifier (Ubuntu)
Status: New => Confirmed
--
package update-not
*** This bug is a duplicate of bug 150680 ***
https://bugs.launchpad.net/bugs/150680
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported. Feel free
to continue to report any other bugs you may find.
** This bug has
TEMP_SENSOR ? TRUE :
FALSE);
icon = get_sensor_icon(type);
Would that be a correct patch to your knowledge?
If it is correct, I will upload the debdiff and ask to get this bug fixed.
Regards,
Albert
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.
Soren, can you please advise which CD exactly you used? i.e which Ubuntu type,
i386 or amd64 and which day? We know the problem was not fixed in beta yet, so
I am assuming you used one of the daily CD's.
Secondly, can you confirm your graphics card is an 855GM? Can you see from your
logs which v
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
It looks like your problem may consist of two separate problems:
1. The colored blocks during installation
2. The problems after reboot.
The first problem was a known problem which was solved shortly after the bet
After discussion on #ubuntu-motu, I backported the solution for this bug from
the current Debian unstable version, 1.8.1+dfsg-1
Attached is the debdiff. Hopefully this can still be fixed before Gutsy is
released.
** Attachment added: "debdiff"
http://launchpadlibrarian.net/9899702/debdiff
--
This is the corrected debdiff, now made using cdbs-edit-patch.
** Attachment added: "debdiff with cdbs"
http://launchpadlibrarian.net/9927405/debdiff_cdbs
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.net/bugs/147188
You received this bug notification because y
-applet (Ubuntu)
Assignee: albert (albrt) => (unassigned)
Status: Incomplete => Confirmed
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.net/bugs/147188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Can you please answer the following questions:
- which cd version did you use, Desktop or Alternative?
- did you get a message about failed check for security updates during the
installation?
- can you please atta
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 129910, so it is being marked as such. Please look at
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
Confirming after installing Gutsy final in vmware, without Internet connection.
After the installation completed, lines in sources.list are commented out and
another comment says it was done by the installer, i.e.:
# Line commented out by installer because it failed to verify:
# deb http://securi
As discussed on irc #ubuntu-bugs, please verify if the CD is error free.
If the CD is error free, please try and get details of your hardware,
for example using an older live-CD. If an older live-CD boots correctly,
please run the command lspci -v > lspci.txt and attach the file lspci.tt
to this bu
*** This bug is a duplicate of bug 154095 ***
https://bugs.launchpad.net/bugs/154095
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has also been reported in the final
release of Gutsy and therefore is marked as a duplicate of bug 154095
Public bug reported:
Binary package hint: update-manager
Error messages:
Failed to fetch
http://medibuntu.sos-sts.com/repo/dists/feisty/free/binary-i386/Packages.gz 302
Found
Failed to fetch
http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/binary-i386/Packages.gz
302 Found
** Affect
Have tried to upgrade every 3 hours over a 24 hour period. Medibuntu
servers appear to be up, but upgrade fails to find the packages.
--
Ubuntu 7.04 to 7.10 upgrade fails on Medibuntu
https://bugs.launchpad.net/bugs/155135
You received this bug notification because you are a member of Ubuntu
Bugs
The documents opens fine in Gutsy AMD64, with 4 GB RAM. It just uses a lot of
memory (580 MB virt when it is open, more during opening the document).
However, on Gutsy i386 in vmware with 512 MB ram it seems to open, but crashes
after a while, while the hard disk is busy swapping. According to t
*** This bug is a duplicate of bug 138343 ***
https://bugs.launchpad.net/bugs/138343
Sorry, forget the line about plenty swap: swap actually goes down to 0 during
the process.
The document opens in 512 MB ram if nothing else is running (still giving the
cairo NULL pointer message), it breaks
*** This bug is a duplicate of bug 138343 ***
https://bugs.launchpad.net/bugs/138343
This turns out to be a duplicate of bug 138343, which is already known
upstream.
** This bug has been marked a duplicate of bug 138343
evince consumes a lot of memory (1.5 GB VM)
--
maybe mem leak
https:
http://www.tfh-
berlin.de/~rudolph/signale/skripte/SuS_SS06/Shannon_Limit.pdf (from dup
bug 154526) is another example taking a lot of memory. It can crash a
512 MB system, without doing anything special.
--
evince consumes a lot of memory (1.5 GB VM)
https://bugs.launchpad.net/bugs/138343
You re
The medibuntu repositories have been moved. See
https://help.ubuntu.com/community/Medibuntu#head-7486ed038a9becc1dff10a24cc07a38a00d70e9f
Can you please try again with the location mentioned there and report if that
works?
** Changed in: update-manager (Ubuntu)
Status: New => Incomplete
As Gutsy has been released now with the new version of ekiga, I will
close this bug as fix released. New installations will get the new ekiga
with the correct libopal version. For those who have been using
development versions of gutsy, they may need to update ekiga and libopal
through Synaptic, us
*** This bug is a duplicate of bug 154885 ***
https://bugs.launchpad.net/bugs/154885
** This bug has been marked a duplicate of bug 154885
Update-manager failed to install or upgrade
--
Update-manager failed to install or upgrade
https://bugs.launchpad.net/bugs/154886
You received this bu
Work-around:
1. System -> Administration -> Software Sources
2. Under Third-Party Sources, untick Medibuntu
3. Now do upgrade to 7.10
--
Ubuntu 7.04 to 7.10 upgrade fails on Medibuntu
https://bugs.launchpad.net/bugs/155135
You received this bug notification because you are a member of Ubuntu
Bug
I can only reproduce this when compiz is active. With desktop-effects switched
off, the problem does not occur.
As metacity is not active when desktop-effects are on, I think this would
actually be a bug in either compiz or gtk-window-decorator.
Joachim, can you please try what happens for you if
Contact on #ubuntu-bugs showed Joachim is using Feisty, with Metacity 2.18.2
I am using Gutsy, with Metacity version 2.20.0. I did a second test in a
virtual machine with Gutsy, which also did not show the problem. As this
problem is solved in the development version, I will mark this as fix rele
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
It looks like this bug may be a duplicate of bug 129910. Can you please run the
command:
ps ax | grep tty
and verify the virtual consoles are active?
Secondly, please try the command:
sudo modprobe fbcon
and afte
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
*** This bug is a duplicate of bug 146513 ***
https://bugs.launchpad.net/bugs/146513
This was fixed earlier today. You should soon be able to download the
correct package.
** This bug has been marked a duplicate of bug 146513
package volumeid 113-0ubuntu13 failed to install/upgrade:
--
p
*** This bug is a duplicate of bug 146513 ***
https://bugs.launchpad.net/bugs/146513
This was fixed earlier today. You should soon be able to download the
correct package.
** This bug has been marked a duplicate of bug 146513
package volumeid 113-0ubuntu13 failed to install/upgrade:
--
v
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
- please paste the result of the command uname -a
- please advise the version of udev on your system (output of dpkg -s udev |
grep Version)
** Changed in: udev (Ubuntu)
Stat
Juergen, that confirms what I noticed. However, Gutsy has only 2.6.22 kernels,
so I wanted to double check. With a non-standard kernel this is not a bug in
Gutsy and I will mark it as invalid.
For information, Gutsy with 2.6.22 still has /dev/bus/usb/
** Changed in: udev (Ubuntu)
Status:
*** This bug is a duplicate of bug 140833 ***
https://bugs.launchpad.net/bugs/140833
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 140833, so it is being marked as such. Please look at
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
BuGabundo, that problem during installation is bug 127008, which has
just been fixed.
--
framebuffer doesn't work on gutsy kernel
https://bugs.launchpad.net/bugs/141221
You received this bug notification bec
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This particular bug probably has already been reported as bug 138348.
Can you please take a look at the screenshots in that bug and report if you
have the same error messages?
NB: that bug is on IFL91 as well
**
I can confirm this as well, when Compiz is active. With desktop-effects
disabled I don't have the problem.
gnome-panel version 2.20.0.1-0ubuntu4
** Changed in: gnome-panel (Ubuntu)
Status: New => Confirmed
--
bottom panel not visible when desktop starts
https://bugs.launchpad.net/bugs/14
This issue has been fixed in the development version of Ubuntu - the Gutsy
Gibbon. Therefore I will close this bug.
pci.ids now contains a daily snapshot of Mon 2007-09-17
pciutils (1:2.2.4-1ubuntu2) gutsy; urgency=low
* Updated pci.ids
-- Tim Gardner <[EMAIL PROTECTED]> Mon, 17 Sep 2007 21:1
An update to xresprobe was published yesterday which may be related to this bug.
Previously xresprobe would not use ddcprobe in this configuration, but after
yesterday's update ddcprobe will be used.
** Also affects: xresprobe (Ubuntu)
Importance: Undecided
Status: New
--
Xorg 1:7.2-5
101 - 200 of 2817 matches
Mail list logo
