I have encountered this issue trying a fresh install of Kubuntu 20.04.1.
The entire reason that I tried a fresh install is that trying to upgrade
my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the
upgrade finishing with errors and leaving my system in an unusable state
(fortunately,
** Attachment added: "The attachment for my comment above does not seem to have
taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04
installation"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog
--
You received this bug notificat
Public bug reported:
Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2
Most of the subcommands for /sbin/ip are documented in a manpage with a name of
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at
"ip-address(8)".
However, ip tuntap seems to be
As an update to my comment above, while the release upgrader hung and
did not finish the upgrade, it *did* disable all my ppa's and switch
over to the Xenial repositories, which ended up leaving my system broken
next time I tried pulling in updates (thinking the upgrade had failed
completely and th
I'm running into the same thing trying to upgrade from 14.04 to 16.04.
After Googling around about the issue, this link at first looked like a
promising lead, as I'm running into this on Haswell hardware and I have
Core2 hardware that was unaffected:
https://groups.google.com/forum/#!topic/mechan
Is there any chance of this being fixed in Precise?
Looking at https://wiki.ubuntu.com/StableReleaseUpdates#When , it's not
really a severe regression (2nd bullet point), but I believe it
qualifies for "Obviously safe patch" and "Affects an application" (4th
bullet point).
--
You received this b
I've recently run into this problem. From my own experience, and looking
around on the net, the cause seems to be that something in the handling
of chainloading or drive mapping has changed since grub-legacy, and
Windows 95/98/ME thinks that it was booted from the MBR of a drive with
grub on it in
Oops. Just realized that the problem was do to the inclusion of
"loop,user,noauto" rather than "user,noauto" in my fstab entries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919736
Title:
Mounting
I can reproduce this bug in Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726283
Title:
umount segfaults with inconsistent entry in /etc/fstab
To manage notifications about this bug go to:
h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919736
Title:
Mounting a loop device causes the wrong loop device to be mounted.
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Public bug reported:
Ubuntu 10.04.3 LTS
util-linux 2.17.2-0ubuntu1.10.04.2
There may be other packages involved in this bug than util-linux: This
bug has only affected me for a few days, whereas Synaptic reports the
last update to util-linux / mount to have been about a year ago (January
20th 201
OK, yeah, I recently installed a fingerprint reader package (from this
PPA: https://launchpad.net/~fingerprint/+archive/fingerprint-gui) , and
I recall that a PAM module was involved. And /var/log/syslog records a
segfault in a *.so associated with that package.
--
You received this bug notificat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913029
Title:
su segfaults when Ctrl-D is entered as the first charachter in
response to the password prompt
To manage notifications about this bug go
Public bug reported:
64 bit Ubuntu 10.04.3 LTS
login version 1:4.1.4.2-1ubuntu2.2
Steps to reproduce:
1. Invoke su. (What options and username are given, if any, doesn't seem to
matter).
2. When prompted for a password, hit Ctrl-D without typing any other characters
first.
Expected results:
@ Tal Liron
>In their rush to hate on Unity, people are forgetting how keyboard-centric
>Unity is.
Not me. For me, the fact that that keyboard centrism comes at the cost
of huge regressions in mouse-centric usability is what kills it for me
(that and some configurability issues, but many of thos
@Mark Shuttleworth:
>Nonsense, again. Ubuntu has *always* aimed for usability, always gone
>the extra mile to make it easy to install and easy to embrace and easy
>to share Linux. I don't think it's cool to be too cool for that mission,
>but if you are in fact too cool for that mission, please d
** Attachment added: "The corrupted file."
https://bugs.launchpad.net/bugs/84/+attachment/2364026/+files/I.S.Bach-BWV578.ogg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/84
Title:
Rhyth
Public bug reported:
In my ~/Music folder I have a corrupted copy of
http://en.wikipedia.org/wiki/File:I.S.Bach-BWV578.ogg
Naturally, Rhythmbox will often stop playing this file when in reaches
the corrupt data (though exactly where it stops and if it stops is
inconsistent). The problem is that t
The thing is, this probably isn't actually a bug, but rather a
misfeature, and the "it's not a bug, it's a feature" mentality is
probably responsible for the fact that it has gone unfixed so long. I
see no evidence that the behavior gedit exhibits here wasn't intended.
If it *were* a bug, it would
19 matches
Mail list logo
