Public bug reported:
During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
configure interrupting the upgrade.
dpkg complained that kvm already exist but it is not a system group.
>From what I saw my user was the only member of kvm group
I don't recall installing kvm manually but I
Thanks, removing timidity did help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879054
Title:
No sound after 20.04 update
To manage notifications about this bug go to:
Public bug reported:
After update from 18.04 to 20.04 sound stopped working.
KDE does not display Xonar sound card at all.
$ aplay /usr/share/sounds/alsa/Front_Center.wav
does not make any sound
Alsamixer displays Xonar set at full volume but changing anything there
does not seem to have any
Public bug reported:
Image in topic is draw out of bounds. This did not happen in Thunderbird
from 17.10 (attached: base64Topic.png, HugeEmoteInTopic.png)
I think the relevant part of eml file is:
Subject: =?utf-8?B?8J+RiSBGb3Rva3NpxIXFvGthIDIxIHggMjgganXFvCBvZCAx?=
=?utf-8?B?MzUgesWC?=
** Attachment added: "HugeEmoteInTopic.png"
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1764708/+attachment/5119224/+files/HugeEmoteInTopic.png
** Description changed:
Image in topic is draw out of bounds. This did not happen in Thunderbird
- from 17.10
+ from 17.10
Removing update-manager-kde worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313165
Title:
Unable to upgrade to latest Ubuntu version 14.04
To manage notifications about this bug go
Ok I tested it on pl locale. Looks like in newer version it looks
better, because I got
DEBUG The package 'update-manager-kde' is marked for removal but it's in
the removal blacklist
line in main.log (which previoulsy was not there), but unfortunetlly my
proposed fix for DistUpgradeCache was
Sorry for delay, but I cannot install 1:0.220.3 . I enabled proposed, run
apitude update
but all I see in aptitude versions ubuntu-release-upgrader
is
1:0.205.7saucy-proposed 500
Is 64bit package is in repo already? I selected Ubuntu main repo
I might add that u'xab' appears to be character « according to
http://es.wikipedia.org/wiki/ISO_8859-1 (and my test with python2.7).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310053
Title:
Well I can confirm that line 661 was the one that tried to log error, but
changing
logging.error(Dist-upgrade failed: '%s', e)
to
logging.error(Dist-upgrade failed: '%s', unicode(e))
only results in correctly printing 'Dist-upgrade' failed error to log
file:
2014-04-22 20:06:46,539 DEBUG The
Public bug reported:
Upgrade from 13.10 to 14.04 fails. Last entry in logs before abort is The
package 'update-manager-kde' is marked for removal but it's in the removal
blacklist.
All ppa s were purged before upgrade.
Logs from /var/log/dist-upgrade attached.
ProblemType: Bug
DistroRelease:
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1309723/+attachment/4087969/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In what version was it fixed? I tried again (open qbzr, commit changes
in other window from CLI, press refresh in qbzr) and it crashed just
like in old version. That said I got used to it in the meantime so if no
one cares about it then maybe lets call it a feature and close it ;)
Fontconfig
Public bug reported:
I tried updating Kubuntu 11.10 to 12.04 (beta) with
$ update-manager -d
but I did receive error in console:
authenticate 'precise.tar.gz' against 'precise.tar.gz.gpg'
extracting 'precise.tar.gz'
Traceback (most recent call last):
File
Sure. Here are logs.
** Attachment added: logs from /var/log/dist-upgrade
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/964674/+attachment/2936370/+files/dist_upgrade_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: last apt.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/964674/+attachment/2936371/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964674
** Attachment added: last main.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/964674/+attachment/2936372/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964674
(term.log is empty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964674
Title:
update-manager fails to update to precise beta
To manage notifications about this bug go to:
** Attachment added: apt-clone_system_state.tar.gz
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540828/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540833/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873585
Title:
** Attachment added: apt-term.log.tar.gz
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540837/+files/apt-term.log.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: term.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540834/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873585
Title:
Public bug reported:
Bug occured during update to oneric.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: update-manager (not installed)
ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
Uname: Linux 2.6.38-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion:
** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540832/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873585
** Attachment added: history.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873585/+attachment/2540831/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873585
** Attachment added: apt.log
https://bugs.launchpad.net/bugs/873585/+attachment/2540827/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873585
Title:
bug occured during update to
Public bug reported:
I have usability problem with LightDM. When Ubuntu boots I see LightDM
on primary(left) monitor and black screen on secondary(right) monitor.
Cursor is few pixel on right monitor(and was in previous Ubuntu release
since I remember). In GDM that was not a problem since input
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862146
Title:
LightDM don't reacts on keyboard when cursor is on second
monitor(which is default position)
To manage notifications about this bug go
I've changed mirror to use official one instead of one for my country.
Official had some newer packages and after installing them it seems
fixed. Sorry about report
** Changed in: lightdm (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
Lucid's GDM automatic timed login works only on boot-there is no count
down to log default user again after he logs out making this bug not
reproducible. I wonder if that means that in for example live-cd if user
logs out force him to restart to log in again, but that would be another
issue
**
I think that it is connected to https://bugtrack.alsa-project.org/alsa-
bug/view.php?id=4774 which have addition info (I don't have waiting
for sound system but sound drop is very noticable). If I remember
correctly bug appered first in karmic, and exists in lucid and also
upstream alsa1.021 and
31 matches
Mail list logo
