We were using aliased interfaces (lo:1) on other OSs (cent/debian/etc)
as well as ubuntu to avoid overwriting the default lo interface
configuration files . We've tested cloud-init with lo and no mac
matching on ubuntu and non ubuntu OSs and it works, so we'll just change
our base CI data to work
Mantic with 0.106.1 correctly configures the loopback interface so it
seems other package updates on the system aren't affected by the
permanent mac address changeset. I suspect it is something with systemd
but I haven't found anything definitive yet. The netplan file from
cloudinit and the
I was able to confirm that https://github.com/canonical/netplan/pull/278
is the breaking commit with git bisect. I tried to bisect forward to
0.107.1 to see if I could find the behavior change back to working but I
think my test setup is flawed or there's another factor at play here. I
did spin up
Ignore the github comment, I was looking at the
https://github.com/canonical/netplan.io repo which I incorrectly assumed
was the repo the package was being built from, I didn't even check the
code there when I didn't see any versioning tags (facepalm).
--
You received this bug notification
I can see the need for skipping most of, if not all non loopback,
virtual devices. lo would seem to be a special case imho. I'd like to
avoid differing cloudinit nocloud data between the various distros.
As an aside it also doesn't seem to handle subinterfaces (e.g. lo:1)
like other distributions
Also, why is previous behavior allowed to change in an LTS release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055333
Title:
netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional
If that is the case then why does it work on the newer version that is
present in mantic? Is there any source for this package besides github?
I can't find any tags, branching, release notes that would make it easy
to find/generate a changeset/changelog between specific versions or even
find which
*** This bug is a duplicate of bug 2043073 ***
https://bugs.launchpad.net/bugs/2043073
I have the same symptoms as described in the initial post. I haven't
seen any ACPI BIOS errors though. I'm not sure what logs might be
helpful in debugging this but I'm happy to upload anything that might
I applied the patch and ran `update-initramfs -u` with
`/lib/libc6-prof/x86_64-linux-gnu` at the front of my dynamic linker
search path and it seemed to work. Even installed a new kernel update
with the patch in place and the system rebooted into the new kernel.
That's better than before, where
Public bug reported:
Attempting to add additional loopback addresses to 22.04 jammy fails
with the latest netplan.io package. Previous versions (.104) work
correctly as well as newer versions (0.107) in 23.10 mantic. Behavior
does not change if default loopback addresses are or are not present
Public bug reported:
I am not very computer literate. I was attempting an upgrade from Ubuntu
16.04 to 18. During the cleaning up phase, a pop-up occurred stating
"Error during commit" A problem occurred during the clean-up. Please see
the below message for information. installArchives() failed
Public bug reported:
After issuing a software reboot, the machine hangs at a black screen
after the grub prompt, before the kernel boots. This lasts at least five
minutes, with the processor fans spun all the way up. If I remove quiet
and nosplash there is no text, the screen is completely black.
Perhaps @Rolf meant this bug?
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1164016
Title:
restore type-ahead find
To manage
Hello.
I have this bug too.
[ 944.504716] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
When I had 5.4.0-74 core this bug was unconditional, i.e. it was when even no
one usb devices was plugged.
Know I have 5.8.0-55 and this bug occurs only when second usb monitor is
plugged (it
Judging by the 100% cpu utilization and entries in /var/log/dist-
upgrade/apt.log... as an outside observer black box guess: is this thing
loading the parsing the entire package dependency graph repeatedly once
per potential package?
88% complete after 30 minutes of CPU time...
--
You received
Public bug reported:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was caused by:
* Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem,
please try again later.
If none of this applies, then please
** Summary changed:
- Samsung SSD 750 EVO doesn't support queued TRIM command
+ Samsung SSD 750/850/860/870 EVO/QVO doesn't support queued TRIM command
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this with my 870 EVO on 20.04 kernel 5.4.0-65-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809972
Title:
Samsung SSD 750 EVO doesn't support queued TRIM command
To manage
This also happens on the brand new Samsung 870 EVO.
And based on https://bugzilla.kernel.org/show_bug.cgi?id=203475 and
https://bugzilla.kernel.org/show_bug.cgi?id=201693 a variety of other
Samsung 8* devices on a wide variety of SATA controllers (it doesn't
seem controller related).
At the very
Just as a status update,
we are waiting on
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
to be merged right now. Perhaps people wouldn't mind doing a thumbs up to bump
that PR?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can't edit my previous post, but I've attached a screenshot of what
Nautilus looks like as well.
** Attachment added: "Screenshot from 2020-12-08 16-25-16.png"
@paelzer I'm here because I'm running into the same issue. Server and
client are running Samba version 4.11.6-Ubuntu.
smbstatus shows SMB3 for the protocol.
Ubuntu client mounts Ubuntu server share via SMB via fstab. Kodi client
returns the following errors:
2020-12-08 12:56:45.868
Currently, you can track the status of the MR for Nautilus for the fix
of this regression:
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573
The change in the gnome shell that was causing all this has already been
reverted / altered here:
Bug exists in 20.10 too, I just triggered it. It happened after screen
lock/unlock cycle.
Like other restart got rid of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824874
Title:
Public bug reported:
The prompt said something wasn't configured...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Public bug reported:
Continued issue getting high download speed (only getting 6MB/s) on a
5.8GHz wifi dongle. Even utilizing the 6MB/s internet video streaming is
intermittent at best. File download fluctuate and at times drop all
together and would have to be restarted to get the complete file.
Public bug reported:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad
Public bug reported:
I am merely responding to a generated crash query. I have no expertise
in bugs of the electronic kind
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libencode-perl:amd64 3.02-1
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic
My particular problem stemmed from reconfiguring python3 to point to
python3.7 instead of python3.6 via update-alternatives. Logging into
terminal-only mode (Ctrl + F3), setting update-alternatives to use the
system version of python3.6 again, and rebooting solved the issue.
--
You received this
Public bug reported:
Xubuntu 20.04
Hollywood Version 1.20-1 is in the repos.
Hollywood Version 1.20-1 does not play the theme song.
** Affects: hollywood (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: initramfs-tools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's
Public bug reported:
This isn't a bug just in the Ubuntu kernel, as it happened on Debian
too, and I wouldn't rule out any hardware issue either, but I wanted to
share this here to see if I could get any help. I dual boot Windows and
Linux and I think my WiFi card might be failing, but it could
Public bug reported:
Errors were encountered while processing:
google-android-platform-23-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up google-android-platform-23-installer (23+r03+nmu3) ...
make: Entering directory
Just a note that Andrew's comment#1
https://bugs.launchpad.net/ubuntu/+source/nss-
mdns/+bug/369008/comments/1 is still useful as the fix.
On Ubuntu 18.04 /etc/nsswitch.conf is still defaulting to mdns4_minimal
and mdns4. Rather than the much more useful mdns_minimal and mdns which
don't cripple
Affects me too on a T480 running Manjaro
** Also affects: thermald (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815214
Title:
Lenovo
When Windows became unbearable some years ago I moved to Ubuntu 14 and have
been very happy with it
and later issues since. I have kept clear of software details but used
Terminal when necessary to delete obsolete software from the base sector.
Technical explanations of my problems may not be
Public bug reported:
The upgrade was said to be from Ubuntu 18 to Ubuntu 20.
During the Upgrade the screensaver changed and I assumed that all was
well. Today I was prompted to backup and found that my normal automatic
back up was not working and needed to be changed from disk to Google
cloud.
I just diagnosed that openntpd on my 18.04.2 server to be broken
(failing to run, the process died after the apparmor denials, no time
adjustments ever happening) until I manually applied the changes
mentioned in #34.
Neither flags=(attach_disconnected) or "/run/systemd/journal/dev-log w,"
had
(Sadly the bug tracker won't let me change the status from "Won't Fix"
to "Confirmed")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727202
Title:
[17.10 regression] AppArmor ntp denial: Failed
Hi, same problem here, keyboard backlight and some Fn don't work:
- F5 (fan overboost, that's ok if it doesn't work)
- F6 (don't know what it is)
- F7 (screen brightness down)
- F8 (screen brightness up)
- F10 (disable touchpad)
- F11 (screen sleep)
- F12 (airplane mode)
- keyboard arrow up
Regarding #17 and the bug (issue) report at Seahorse Gitlab, the latest
comment is that Seahorse 3.20.0 which is the latest available on Ubuntu
18.04, is "an ancient version". Can 18.04 receive a newer version such
that upstream can be brought into the issue if it persists with that?
--
You
Wish I had the ability to edit a post...
Scratch most of my last post. There is a problem with vdagent~, but I just
refuted my previous post. I do have the error, but I am 99.9% certain that it
does not cause the problems that I am experiencing which brought me to this bug
report. Apologies if
I am wondering if a JVM can be used to more reliably trigger the bug and
thus help isolate it? Hopefully someone else reading this has an
opinion...
Below is my experience and the reason why I am considering this idea:
I have had what I first believed were random black screens, restarts
Public bug reported:
GNU Global supports building with sqlite3 support if configure script is
called with --with-sqlite3 switch. But is disabled in package build.
This is necessary for example to support Go language tags using gogtags
https://github.com/juntaki/gogtags
** Affects: global
I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.
Successfully got a GUI logon prompt and was able to log in to the
desktop.
--
You received this bug notification because you
Uninstalled xorgxrdp, no change:
/var/log/apport.log:
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: called for pid 2790, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR:
apport is enabled.
>From /var/log/apport.log.1:
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: called for pid 2699, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport
I went back to the 4.18 kernel but am not running VirtualBox (running
bare metal).
Also seeing issues with libglib. gnome-shell won't run due to a trap in
libglib-2.0.so:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025
--
You received this bug notification because you are a
No files in /var/crash
No recent issues at
https://errors.ubuntu.com/user/fb9e5fb71e92d21ebe2afac92a428d6eea824f5589e0f6ce0091c409672afddf8eae235d2f465417f7a38369af1cf550eef2e8774386815dad2fad787da75334
Rebooted to reproduce gnome-crash
>From /var/log/syslog:
Apr 24 08:55:18 mizuno
Public bug reported:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
Public bug reported:
greg@mizuno:/var/crash$ cat /proc/version_signature
Ubuntu 4.18.0-13.14-generic 4.18.17
greg@mizuno:/var/crash$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04
Happened during upgrade from 18.10 to 19.04.
ProblemType: Package
DistroRelease: Ubuntu 19.04
Not a bug in Ubuntu 14.04 at least (I can't speak for earlier versions).
The package works fine, but usage is not obvious. The include paths and
library order should be retrieved using pkgconfig. On an x86_64 system,
the pkgconfig file itself will be in /usr/lib/x86_64-linux-
We too are working around this bug with a sleep. Agreed, a solution
would be welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288196
Title:
MAC address of bonding interface is randomly
Having reported the problem I wonder how to proceed. Could I:-
1. Simple delete the later, 4.15.0-39 & -42 versions, leaving me space on the
/boot partition and perhaps try reloading one of them ?
2. Is there a method for getting one of these to boot leaving the
present 4.15.0-18 free to be
Public bug reported:
I was trying to clear space on /boot by removing linux-image-4.15.0-38. This
would have left wo later versions.
sudo apt auto-remove --purge usually works but did not this time.
I reverted to sudo apt-get remove linux-image-4.15.0-38.
This produced a screen telling me that I
Is there a patch for this bug yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769396
Title:
package cairo-dock-core 3.4.1-0ubuntu1 failed to install/upgrade:
trying to overwrite
In our experience, Trusty appears to be fine - it is just Xenial that is
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786910
Title:
Latest patch breaks command line 'restart all'
To
I believe I have found the culprit. Not happy to say that it looks like
it was a configuration change I made to try to fix the ubiquitous
screen-tearing and frame synch problems that some applications have. I
*believed* I had reverted all the changes I made when I saw they hadn't
fixed the issue,
For #41 and #43; tried rebooting into the previous kernel 4.0.15.22.
Both with "nomodeset" and without it.
With "nomodeset" the GDM login presents and I can log in! But it doesn't
appear to be using the actual nvidia driver... Only resolution available
is 1027x768 (not the native resolution of
For #42, the contents of 10-nvidia.conf:
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
EndSection
--
You received this bug notification because you
Just did a locate for all xorg.conf:
sudo locate -i xorg.conf
/usr/share/X11/xorg.conf.d
/usr/share/X11/xorg.conf.d/10-amdgpu.conf
/usr/share/X11/xorg.conf.d/10-nvidia.conf
/usr/share/X11/xorg.conf.d/10-quirks.conf
/usr/share/X11/xorg.conf.d/10-radeon.conf
For 2 from #34.
** Attachment added: "dpkgl.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154436/+files/dpkgl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For 1 from #34.
** Attachment added: "gdms.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154435/+files/gdms.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The machine in question has a single monitor with a resolution of
1920x1080.
And newjournal.txt for 4 from #34.
** Attachment added: "newjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154437/+files/newjournal.txt
--
You received this bug notification
As per #32:
1 Purged all nvidia packages.
2 apt autoremoved, autocleaned.
3 Removed ppa:graphics-drivers (added for a previous attempt to fix this bug)
4 Apt update
5 Apt Installed nvidia-driver-390
6 Rebooted machine
Still no graphical login. ALso, strangely, no new or updated files in
In reference to #29. Attached is the contents of /var/crash.
** Attachment added: "var_crash.tar"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154143/+files/var_crash.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In reference to #29 regarding whoopsie:
The ID is:
19b6b20813c4f5b05681f9895a0eea0b33c549b42c2877003a447f1dc2e2d71a1c819b59ac63fb1977d412a9b4c0adbc72585129337191e89a05d246c7bf0bb0
The links are:
https://errors.ubuntu.com/oops/d69e209a-70f2-11e8-b67b-fa163ef911dc
Added nomodeset to the lines specified in #26. Ran "update-grub".
Rebooted. Unfortunately, still no GDM login screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777378
Title:
[nvidia] GDM no
Answer to #24- make.log is attached.
/proc/cmdline is -
BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root
ro quiet splash vt.handoff=1
** Attachment added: "nvidia_390_67_make_log.txt"
There seems to be several places to look. I will have to continue later
as I have run out of time for now. But maybe the attached file will help
narrow down the location of any useful files related to dkms.
** Attachment added: "locate_i_dkms.txt"
The output of "lspci -k" is attached.
Unfortunately, there doesn't appear to be anything related to dkms in
/var/log .
** Attachment added: "lspci_k_001.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5153859/+files/lspci_k_001.txt
--
You received this bug
Noticed previously that the status of my working Gnome (Ubuntu 16.04)
desktop's GDM3 service is a bit different than the bugged machine.
Attached is a series of systemctl status updates before and after
stopping and starting the GDM3 service. Note that I did not run any
other systemctl command
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1777378/+attachment/5153857/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1777378/+attachment/5153856/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Manually installed files specified in #12. There was one missing
package, "libglib2.0-dev". Installed it, then ran "dpkg -i *.deb" again.
Rebooted. No apparent change on first reboot. No apparent change after
second reboot.
Note: The debug, or ddeb files, were not installed.
** Description
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1777378/+attachment/5153855/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the history.log for #13
** Attachment added: "apt_history.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5153835/+files/apt_history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1777378/+attachment/5153833/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1777378/+attachment/5153834/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Tags added: apport-collected
** Description changed:
Background:
Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used nVidia
proprietary drivers from Ubuntu repo. Worked quite well for over two
weeks. When booting up on Friday 15th June, 2018 no
Daniel, I am not sure what to do with apport-collect 1777378 from #3,
since it is waiting in vein for a web-browser to open. This won't happen
since I have no GUI desktop at present.
I did try the fix from #5 two different ways:
1> Commented out "WaylandEnable=true" with a leading #.
-This
Daniel here is the output of journalctl.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5153831/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Daniel, here is the output of dmesg:
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5153830/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Background:
Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used nVidia
proprietary drivers from Ubuntu repo. Worked quite well for over two
weeks. When booting up on Friday 15th June, 2018 no longer had a GUI
login screen. There was just a few lines in tty1.
Also having a this problem. Why is this marked fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
To manage notifications about this bug
I have what seems to be a similar problem. Have a machine with stock
Ubuntu 18.04 clean install. Ran fine with latest recommended proprietary
driver for over 2 weeks. Then Friday the 15th June, 2018 it refuses to
use the proprietary drivers. The latest Kernel version will not even
show the login
Public bug reported:
This happens almost every time my computer starts up. I still can use it
bit I sometimes lose the bottom bar in LKDE.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214
I think it is wrong that you won't tell me what's wrong with MY computer
just because someone with wheel bits set found the problem first.
--
You received this bug notification because you are a member of
Can confirm #5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773383
Title:
iotop crashes on launch
To manage notifications about this bug go to:
Public bug reported:
default optimizations cause issues with this kind of operation:
dingus.rip += doodle();
where the call to doodle() mutates dingus.rip
The produced assembly will use stale data and simply overwrite the
mutation with the original value. the resulting code simplifies to this
Public bug reported:
I'm trying to set up a network bridge for KVM but I keep getting a the
error,"Error in network definition //etc/netplan/50-cloud-init.yaml line
5 column 0: unknown key bridges." The funny thing is line 5 column 0 is
network, not bridges, so I'm not sure why it is saying
It is 2018 year. A ridiculous bug with NumLock is still present in a fresh
installation of 14.04 LTS.
4 years no one can fix the bug, is it for real?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also affects Xubuntu 16.04
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730560
Title:
package apt-config-auto-update (not installed) failed to
install/upgrade: trying to
Public bug reported:
Keeps crashing, all attempts to upgrade have failed.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-extra-4.10.0-26-generic 4.10.0-26.30
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion:
Public bug reported:
Firefox always crashes when launched after the 55.0.1 update on an
Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
even in safe mode.
I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM
single-board computer) on a similar board
Public bug reported:
No details
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-extra-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Ubuntu 16.04 LTS ("Xenial Xerus") here, and I too have no notifications
for new e-mails... "Pulling" to refresh does not seem to work, and
closing then re-opening usually doesn't work either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Patch (#4) works for mysql-workbench 6.3 on xenial. Thanks, ehoover!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Title:
python-paramiko 1.16.0-1 incompatible with python-crypto
** Also affects: mysql-workbench
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Title:
python-paramiko 1.16.0-1 incompatible with python-crypto
Public bug reported:
install of postfix
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: postfix 3.1.0-3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
postfix: Purge
sensible-mda: Purge
NULL:
1 - 100 of 1144 matches
Mail list logo
