** Description changed:
- After allowing an Ubuntu Impish system to update, and rebooting for a
- new kernel it gets stuck after loading kernel and ramdisk, no further
- output on 5.13.0-36
+ After allowing an Ubuntu Impish system running under Parallels Desktop
+ on M1 Mac (aarch64) to update,
Public bug reported:
After allowing an Ubuntu Impish system to update, and rebooting for a
new kernel it gets stuck after loading kernel and ramdisk, no further
output on 5.13.0-36
Reverting to 5.13.0-20 by selecting it at the grub screen allows the
system to boot as normal.
ProblemType: Bug
Running sleep fails with:
sleep: cannot read realtime clock: Invalid argument
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868854
Title:
package libc6:amd64 2.31-0ubuntu6 failed to
I believe this is a change in libc6 2.31 now making an unsupported call
in WSL which causes "sleep" to break:
https://github.com/microsoft/WSL/issues/4898
As a workaround I edited /var/lib/dpkg/info/libc6:arm64.postinst (as I
was on arm64) and removed the "sleep 1" which was causing package
And of course anything else on an affected system calling sleep be they
scripts or packages will be similarly affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868854
Title:
package
Public bug reported:
In a recently juju deployed 13.2.4 ceph cluster (as part of an OpenStack
Rocky deploy) we experienced a none clearing HEALTH_WARN event that
appeared to be associated with a short planned network outage, but did
not clear without human intervention:
health: HEALTH_WARN
Public bug reported:
running conjure-up from snap with snapped lxd on amd64 bionic with a
previously lxd init'd lxd allows to deploy spells to localhost with lxd.
On arm64 it appears the localhost/lxd provider doesn't detect lxd
whether package or snap derived despite it being there and useable
Public bug reported:
With python3-googleapi 1.5.5-1 installed on ubuntu 18.04 bionic system
we get several tracebacks on connect/discovery related to
discovery_cache and module load:
Traceback (most recent call last):
File
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059593/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059596/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059594/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IfupdownConfig.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059591/+files/IfupdownConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059597/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059592/+files/IpAddr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
Title:
apport information
** Tags added: apport-collected
** Description changed:
Firefox on Ubuntu 16.04 crashes when launched on armhf.
ii firefox
58.0.2+build1-0ubuntu0.16.04.1 armhfSafe and easy
web browser from Mozilla
Description: Ubuntu 16.04.3 LTS
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059599/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059589/+files/CurrentDmesg.txt
--
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/1750444/+attachment/5059595/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059598/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059590/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1750444/+attachment/5059588/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
Title:
Public bug reported:
Firefox on Ubuntu 16.04 crashes when launched on armhf.
ii firefox
58.0.2+build1-0ubuntu0.16.04.1 armhfSafe and easy
web browser from Mozilla
Description:Ubuntu 16.04.3 LTS
Release:16.04
gareth@localhost:~$ firefox
Note while I submitted this from a Linux chroot env on an Android device
it also fails in the same way on a RPi3 running Ubuntu-Mate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750444
Title:
Fix seems to be to remove "MenuBar=Disabled" from ~/.config/quasselrc
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
https://bugs.launchpad.net/bugs/1736732
Title:
quassel-client lacks menus on artful
To manage
Public bug reported:
After upgrading from Xenial to Artful (via Zesty), quassel-client
appears to have no menus, eg File, etc.
It is otherwise functional/usable connecting to an existing core, aside
from being unable to configure the client.
** Affects: quassel (Ubuntu)
Importance:
moon127@moon127-UX305CA:~$ dpkg -l | grep quassel
ii quassel-client 1:0.12.4-2ubuntu2
amd64distributed IRC client - client component
ii quassel-data 1:0.12.4-2ubuntu2
Public bug reported:
IS have a number of bootstrap nodes with small <10GB disks, particularly
in AWS where root disk is often only 8GB with our current sizing.
Periodically we get disk space alerts and find that there is little we
can clean up on the instance, with juju's mongodb using the vast
Public bug reported:
Until a few weeks ago suspend worked perfectly on my 2012 11" MacBook
Air. Since that time however it has become very unreliable.
If I close the lid to suspend and reopen within a short period of time
it resumes and all is fine. If left longer eg overnight then on opening
Kernel bisecting:
We know it's fixed in 4.3.0-040300-201511020949
Stepping up through kernels:
Current wily kernel (with displayport issue):
4.2.0-17.21 Ubuntu-4.2.0-17.21 4.2.3
dist-upgrade gets us to:
4.2.0-18.22 Ubuntu-4.2.0-18.22 4.2.3 - same displayport issue
v4.2.6-wily
Tested mainline and the Mini-DP to VGA adaptor behaved correctly
allowing me 1920x1200 on my external display.
uname -a
Linux moon127-MacBookAir 4.3.0-040300-generic #201511020949 SMP Mon Nov 2
14:50:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
sudo dmidecode -s bios-version && sudo dmidecode -s
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512851/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512849/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
In Vivid on connection of external display using displayport to VGA
adaptor all resolutions upto max of my monitor were supported.
Since upgrade to Wily while my internal display operates correctly the
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512839/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512840/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512843/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512842/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512844/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512847/+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/1510021
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512857/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512856/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512858/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512853/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512852/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Run as requested (with the MiniDP to VGA) adaptor connected.
Interestingly I tried this with a colleagues generic el cheapo MiniDP to
{VGA,HDMI,DVI} adaptor and successfully got my monitors native
resolution.
So for me at least it appears that the limited resolution issue only
occurs with an
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512859/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512845/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512854/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512855/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512850/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512846/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512841/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512848/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
Public bug reported:
In Vivid quassel-client used to detect disconnect from core after
network interruption or laptop suspend.
In Wily it does not, and appears still connected when resumed but with
stale state.
Description:Ubuntu 15.10
Release:15.10
ii quassel-client
Public bug reported:
In Vivid on connection of external display using displayport to VGA
adaptor all resolutions upto max of my monitor were supported.
Since upgrade to Wily while my internal display operates correctly the
external display only shows resolutions up to 1024x768 as available, eg:
Public bug reported:
After ~3 days uptime the upstart process on my system begins to exhibit
excessive CPU/RAM usage and affects the system responsiveness to the
point I have to restart the system due to slow window redraw and
generally slow task switching in the UI:
08:25:31 up 3 days, 23:01,
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1273261/+attachment/4228103/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
I'm seeing this error and a failure to boot on a previously working
Trusty environment upgraded to Utopic.
As a workaround if I drop to text mode with ESC or boot in recovery I
can see the error /scripts/local-top/cryptroot: line 1: can't open
/dev/mapper/ubuntu--vg-root: no such file but can
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1273261/+attachment/4228102/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
InstallationDate: Installed on 2014-03-31 (190 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64+mac (20140326)
Package: cryptsetup 2:1.6.1-1ubuntu3
PackageArchitecture: amd64
apport information
** Attachment added: fstab.txt
https://bugs.launchpad.net/bugs/1273261/+attachment/4228104/+files/fstab.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Also seeing this on the desktop, as james-fsck machine grinds to a halt
in swap after a few days.
I was forced to hard reset as I couldn't afford the time to try and get
back into the system, if this happens again at a less critical time I'll
try and collecty output per above.
--
You received
Disregard above, I only killed compiz and manually started unity to get
the existing desktop back long enough to save some work so gathered the
requested.
** Attachment added: 1257880-debug.txt
Strace log
** Attachment added: session-init-strace.log
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1257880/+attachment/4185319/+files/session-init-strace.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307437
Title:
Ubuntu removed boot from cd, boot from usb etc.
To manage notifications
I've had a number of lockups in the last 2 days since upgrading to
Trusty and trying to run a VM under kvm which look to match this issue.
System appears to become unresponsive/hang with what looks like some
kind of I/O lockup, cannot ls in a terminal etc before eventually
display freezes.
I've had a number of lockups in the last 2 days since upgrading to
Trusty and trying to run a VM under kvm which look to match this issue.
System appears to become unresponsive/hang with what looks like some
kind of I/O lockup, cannot ls in a terminal etc before eventually
display freezes.
67 matches
Mail list logo
