A further update -- a bit of a hack, but, I liked my "whiteglass"
cursor, and I found that copying its left_ptr and right_ptr files from
/usr/share/icons/whiteglass/cursors overtop of the corresponding ones in
/usr/share/icons/Breeze_Snow/cursors gave me back my whiteglass cursor,
at least for the
I upgraded from 22.04 to 24.04 and could no longer log in. Just
immediately got the sad computer face screen. Can confirm that
installing `breeze` fixed this. I don't really know what's going on but
it seems to provide a functional fallback for when the selected cursor
theme isn't working. Trying
*** This bug is a duplicate of bug 2062377 ***
https://bugs.launchpad.net/bugs/2062377
Hello :-) I don't really know much about what's going on but I just
encountered this exact problem. I wasn't able to log in because Xorg
would immediately display the sad computer screen. I found another
I have emailed pCloud support and they forwarded the problem to Linux tech
developers. They told me when it gets fixed they will email me. After I
found the freezing I completely rebuilt my Ubuntu 22.04 from scratch and
without pCloud installed everything has been normal since then. When I hear
fo
I am almost 99% sure that this error was caused by installing pCloud
Linux software. Today I rebuilt my computer on Ubuntu 22.04 and did NOT
install pCloud Linux and the problem is gone. There fore my assumption
is that Pcloud caused it although I have no proof.
--
You received this bug
Sorry I meant Microsoft Office Home online editing etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers freezes on download and print to pdf
To manage
This bug is affecting both firefox and chrome on 22.04. Any website that
prints, uploads, or downloads. Really made a big mess. I can't edit
using Windows online either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems like nobody is paying attention to this since the fix (which
does not work) was released. Maybe we need to post new bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896482
Title:
Found a fix :
Get into Bios (F2 At boot)
Go to : Power Management -> Wireless Radio Control -> Turn everything OFF
This prevents hardware lock of wifi card when going into suspend and
undocking from Dell dock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*-network
description: Wireless interface
product: Wireless 8265 / 8275
vendor: Intel Corporation
physical id: 0
bus info: pci@:02:00.0
logical name: wlp2s0
version: 78
serial: d4:3b:04:38:28:b3
width: 64 bits
firmware used :
Oct 18 07:53:37 alpha kernel: [2.890212] iwlwifi :02:00.0: Found debug
destination: EXTERNAL_DRAM
Oct 18 07:53:37 alpha kernel: [2.890217] iwlwifi :02:00.0: Found debug
configuration: 0
Oct 18 07:53:37 alpha kernel: [2.890729] iwlwifi :02:00.0: loaded
Note : it might be a problem in the ilwifi driver. I am not sure.
Perhaps rf-kill does the block properly on suspend
But fails to unblock the card because the ilwifi driver does not bring it back
from "hardware lock" to "available" on resume.
So I am not sure of where the problem is, but I tend
Public bug reported:
Dell Latitude 5490
DMI: Dell Inc. Latitude 5490/0FDHF4, BIOS 1.18.0 09/10/2021
When machine goes into sleep, rfkill turns off the wifi card
Then machine goes to sleep.
When resumed, the wifi no longer works, Gnome reports "no wifi card"
Trying to use rfkill to bring the
tried to use rfkill to bring the wifi card back, fails :
after wake from suspend :
gilbert@alpha:~$ sudo rfkill list
1: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
g="wwan-enabled" pid=2153 uid=1000 result="success"
At this point, the Wifi card is dead.
If I try to turn it on in console it says the interface cannot do from DOWN to
UP because RFKILL bit is set :
gilbert@alpha:~$ ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
d
Public bug reported:
It keeps crashing and do not let me install the "Raspberry PI Imager".
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12
Uname: Linux 5.11.0-1007-raspi aarch64
Public bug reported:
Always have an error message on start up
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: firefox 91.0.1+build1-0ubuntu0.21.04.1
ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12
Uname: Linux 5.11.0-1007-raspi aarch64
AddonCompatCheckDisabled: False
I have had this same problem with my Dell Inspiron 5593 since January
2020 when I was on 18.04. Upgrading to 20.04 in June 2020 resulted in
no change of the behavior.
Neither workaround works for me. "rmmod tpm" in grub results in an
error due to the module not being present.
Rebooting
damn, wrong again, the patched kernel has just displayed the bug.
no fixed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896482
Title:
acpi event detection crashes
To manage notifications about
sorry, I retract that. The problem is that ubuntu updated my kernel without my
knowledge,
replacing the correctly patched kernel with the broken one (that both have the
same numbers!)
It would be nice if the patch got incorporated into the distro to save me and
others from this headache!
I
Unfortunately it looks like the bug did not disappear. I have it
starting around 45 minutes after booting in the kernel we thought was
good, 5.4.0-52-generic_5.4.0-52.57. Unless I somehow screwed up and
reinstalled a broken one.
--
You received this bug notification because you are a member of
Public bug reported:
On my new computer, secondary selection with the middle mouse button is not
working. The cursor
does not move when I attempt to drag it while the middle button is pressed. It
may be a motif bug
rather than an nedit bug, since the problem does not occur when I ssh into
I've switched to firefox, that solved the problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898389
Title:
browser frequently crashing with trap int3
To manage notifications about this bug
Version information for python-jmespath in the Ubuntu 20.04 LXC Linux
container:
root@afns1:/# dpkg -l | grep jmespath
ii python3-jmespath 0.9.4-2 all
JSON Matching Expressions (Python 3)
--
You received this bug notification because you are a
Hi, I am also seeing this error when running the following install in a
Ubuntu 20.04 focal fossa on amd64 running in an LXC Linux Container:
The command run is:
COMMAND=/bin/lxc-attach -n nsa -- sudo apt-get -y install bind9 isc-
dhcp-server bind9utils dnsutils openssh-server man awscli sshpass
Using the apt available DKMS does not work
But mounting the 6.1.16 virtual disc with Virtualbox runnable installer
works (VBox_GAs_6.1.16)
After doing :
sudo ./VBox_GAs_6.1.16.run
and rebooting
The display now works again in full screen properly.
Working config is :
-
Upgraded to latest Virtualbox version (which says it supports 5.8 kernel
series). Installed latest available extension pack for VirtualBox.
Then booted the latest kernel avaialble : 5.8.0-34-generic #37
Display is now stuck to 800x600
Latest available DKMS is not compatible with kernel 5.8 :
content of make.log :
DKMS make.log for virtualbox-guest-6.1.10 for kernel 5.8.0-34-generic (x86_64)
jeu. 07 janv. 2021 09:20:12 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic'
CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/VBoxGuest.o
CC [M]
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/virtualbox-guest-dkms.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.10/build/make.log for more
Public bug reported:
kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1
going back to kernel 5.4.0-59 makes full size display working again
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname:
Public bug reported:
Installing on Alienware Laptop. HDD in BIOS set to legasy/ UFEI disabled /
Seure Boot Disabled. First attempt resulted in UNKNOWN CORE ERROR
Second attempt resulted in unrecoverable NVidia Crash then a lockup
Third attempt resulted in error in writing Disk partition
Fourth
Public bug reported:
Trying to install Ubuntu 20.04 over existing partition of Ubuntu 188.04 on a
dual boot iMac computer with OSX. First, the installing program could not
install grub on sda. I decided I would install it manually later. Then the
program crashed and here I am.
I cannot run any
Public bug reported:
I used to be able to have many tabs open with Chromium without problems.
Lately it crashes or gives "aw snap" errors (see kernel messages below)
if I start to keep more than 25 or so open.
Description:Ubuntu 16.04.7 LTS
Release:16.04
chromium-browser:
That's right, I masked them by hand following some advice on the internet for
how to make systemd stop suspending, since it was not responding to settings in
login.conf even after restating logind
service.
Regardless of my motivation, it seems buggy that changing these settings
should lead to
sorry, you can withdraw this bug as I discovered it is a kernel bug, not
systemd.
(I wanted to withdraw it earlier but did not know how to get back to this
report.)
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Right after booting, acpi lid open/close is detected as it should be by
the kernel, but some time later it crashes, so I have to manually
suspend the system. The traceback is here:
Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here
]
Sep 20
Using systemctl status systemd-logind, I see that lid events are no longer
being detected.
This behavior persists even after restarting the service. This is *not* what
is requested in logind.conf, where HandleLidSwitch=suspend and
HandleLidSwitchDocked=suspend.
--
You received this bug
Public bug reported:
in 20.04.01 LTS (release 20.04), suspend on lid closure works for a
while, then one day stops working, with no error message in syslog. The
event is not even registered. The problem seems to start when the
system has been inactive for long enough so that the screen is
by unmasking sleep.target suspend.target hibernate.target hybrid-
sleep.target, and allowing for suspend on lid closure in login.conf, I
was able to make the problem go away, but why should I be forced to
this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
When I close the lid on my laptop, syslog goes crazy with the message
systemd-logind: hibernation is restricted; see man kernel_lockdown.7
repeated ad infinitum, using up all the CPU and GBs of disk space. I am
not even trying to hibernate; everything in
Hi Daniel, yes I was going to resort to that if necessary. Thanks!
One comment though, I found that the setting was not even saved before I
switched to Fvwm.
I had to redo the mouse speed each time I logged into an Ubuntu session.
--
You received this bug notification because you are a member
Public bug reported:
I would like to use gnome control center from Fvwm window manager. But
the mouse speed does not respond at all to what I set unless I am
running it from the default ubuntu window manager. I tried running
gnome control center using different XDG environment variables as
Fabrice: That's probably a different error given that this lp seems to be with
x86 vmx flags.
Check your /var/log/libvirt/qemu/ on the host to see if there's a particular
error shown in the destination qemu after migration.
--
You received this bug notification because you are a member of
Public bug reported:
While upgrading, when calculating it says he cannot complete unless ppa-
purge is done. I did but no progress...
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
Uname:
same seems to happen on Fedora 32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
To manage notifications about this bug go to:
I *think* it's the cf-protection that's adding the endbr32 instructions
that I spotted as being the failing instruction each time; but I don't
understand why they would be CPU type specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That's getting more fun :-)
You could look at whether seabios's config works out hte same in the two
environments, or whether something makes use of new build flags - try looking
at the gcc lines that are invoked in the good/bad cases and see if they're
passing any options that the other
I think the one I was thinking of is 0723cc8a5558c94388db75ae1f4991314914edd3
which is in a 4.2.0 rc
and there was 2605188240f939fa9ae9353f53a0985620b34769 - but that's a
different crash to what you have.
So hmm.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The vmx things make me wonder about a fix Paolo did a while ago for
enabling inidivudal vmx features rather than vmx as a whole; but I
can't remember if that was a kernel or qemu fix.
One thing I notice, that may be a red-herring, all of the machine code
in the errors are 'f3 0f 1e fb' which is
Dnaiel: That's a different problem; 'Bad config data: i=0x10 read: a1
device: 1 cmask: ff wmask: c0 w1cmask:0'; so should probably be a
separate bug.
I'd bet on this being the one fixed by
2bbadb08ce272d65e1f78621002008b07d1e0f03
--
You received this bug notification because you are a member of
#8 from Kai-Heng Feng (kaihengfeng) fixed the issue for me on Lenovo P72
Intel® Core™ i7-8750H running Ubuntu 18.10 kernel 4.18.0-15-generic
#16-Ubuntu SMP. I added the following line to my /etc/default/grub
GRUB_CMDLINE_LINUX="psmouse.elantech_smbus=0"
then ran "sudo update-grub" in the usual
-33 from proposed does boot.
However, while installing that I noticed that the dpkg status on my -32 was
listed as iF (probably from a previous full disk?)
When it installed -33 it regenerated the initramfs for -32 as well and -32 now
works.
Marked invalid.
** Changed in: linux (Ubuntu)
** Attachment added: "screenshot of boot oops"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+attachment/5177502/+files/bootoops-32.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and
earlier) is fine.
(I'll attach the screenshot of the panic in a second)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu
** Patch added: "live-config.patch"
https://bugs.launchpad.net/ubuntu/+source/live-config/+bug/1408135/+attachment/5160429/+files/live-config.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1769053/+subscrip
modalias:
> dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
* ChristianEhrhardt (1769...@bugs.launchpad.net) wrote:
> On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert <dgilb...@redhat.com
> > wrote:
>
> > * ChristianEhrhardt (1769...@bugs.launchpad.net) wrote:
> > > > Interesting; I thought this was supposed to work
assis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dmi.sys.vendor: Dell Inc.
>
Ah right Dan, if you're seeing the 40 bits physical in the guest you
definitely need to try the flags I suggest in comment 6; host-phys-
bits=true should work for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting; I thought this was supposed to work.
I know we (RH) have some downstream patches for >1TB RAM, but the last I'd
heard they weren't supposed to be necessary any more, except for compatibility
with old versions.
It's probably worth checking the guest view fo the CPUs physical address
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729635
Title:
No display after
Workaround #1:
I can confirm that on Lenovo P70 Mobile Workstation running Artful
Aardvark 17.10 an upgrade to kernel 4.13.6 or higher prevented the hang
on "wlp4s0: failed to remove key" (although as mentioned the error still
appears in the shutdown sequence).
Workaround #2
I also found that
/controlC0: gilbert 28962 F pulseaudio
/dev/snd/controlC1: gilbert 28962 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Nov 2 11:44:39 2017
HibernationDevice: RESUME=UUID=909ad59a-dce8-4e98-b3fe-28db48e55878
InstallationDate: Installed on 2017-01-09 (297 days ago)
Install
Re Laszlo's comment #8 - it feels the opposite way around to lp 1715700
- in that I don't think downgrading OVMF helped; so perhaps something
else is going on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After applying the latest update the Software-center now opens but still
has a problem.
For the Launch pad, software center, in Ubuntu 17.10 it reports this error when
trying to open it.
"Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown
Method: No
just tested current head - 1eed33994e28d4a0437ba6e944bbc3ec5e4a29a0 -
seems to work 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/1711602
Title:
--copy-storage-all failing with qemu 2.10
Looks good here, just retested:
here's teh top of my git:
f89f59fad5119f878aaedf711af90802ddcb99c7 nbd-client: avoid spurious
qio_channel_yield() re-entry
cf26039a2b50f078b4ad90b88eea5bb28971c0d8 block: Update open_flags after
->inactivate() callback
8ccc527d84ec9a5052cfae19edbc44abb5ac03ae
I need to recheck with that combo - I'd seen that error but only when
I'd commented out 'if (!blk->dev && !blk_name(blk)[0]) {' when
debugging earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
yes, seems to fix it for me.
Thanks Christian for filing this; we probably wouldn't have spotted it before
the release without it
(which the test Stefan has just added will hopefully cure!).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, yeh that's the same symptom I saw - it's that final failure that
causes bdrv_inactivate_all to return a failure and fail the source
migration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
OK, Stefan posted a patch for that assert (see 'nbd-client: avoid spurious
qui_channel_yield() re-entry) so now I'm running with the following patch and
I'm seeing the bdrv_inactivate return a -1 for
drive-virtio-disk0
Christian: Could you see what your source says with this patch?
diff --git
repeated the assert in #26:
Program received signal SIGABRT, Aborted.
0x7f02163005f7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) where
#0 0x7f02163005f7 in __GI_raise (sig=sig@entry=6)
The difference with the qemu_file_set_error is I'm looking on the source
- because what's happening is the source is erroring so closing the
socket, and so the error you're seeing on the destination is real - the
socket just EOF'd!
--
You received this bug notification because you are a member
(4th try) breakpoint on qemu_file_set_error, it's bdrv_inactivate_all
that's returning the error.
(gdb) list
1155if (inactivate_disks) {
1156/* Inactivate before sending QEMU_VM_EOF so that the
1157 * bdrv_invalidate_cache_all() on the other end won't fail. */
OK, 3rd try and I've hit the same behaviour as Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu 2.10
To manage notifications about this
Hmm i just tried to reproduce this and hit (on the source):
main_channel_client_handle_migrate_connected: client 0x5607d785f610 connected:
0 seamless 0
qemu-system-x86_64: /root/qemu/io/channel.c:303: qio_channel_yield: Assertion
`!ioc->write_coroutine' failed.
2017-08-22 10:50:04.888+:
also, you might want to chase it a bit further down, I think we've got:
qemu-file-channel.c:channel_get_buffer
io/channel-socket.c or io/channel-file.c qio_channel_file_readv
it would be good to know what the readv/readmsg is actually
returning in the case where it's failing.
Dave
OK, so that looks like a real case of the migration stream failing and getting
an IO error; so the question is why:
a) Is the source qemu dieing first and closing the socket?
b) Is libvirt closing the socket for some reason
--
You received this bug notification because you are a member of
oh yeh you want to tell gdb to ignore SIGUSR1, something like:
handle SIGUSR1 nostop noprint pass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with
The 'host doesn't support requested feature' is probably a red-herring in this
case
The fact it's failing with an IO error but nothing else suggests either:
a) it's something closing the socket between the two qemu's
b) The I/O error is from storage/NBD
Assuming it fails on precopy, I'd look
Public bug reported:
Tried to install update.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: gcc-6 6.3.0-19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
Uname: Linux 4.11.0-9-generic i686
ApportVersion: 2.20.5-0ubuntu5
Architecture: i386
Date: Wed Jun 28 08:42:08
Antonio,
Thank you for your report saying the bug was fixed...
I must report I've had a few problems that I have reported.Like "system
setting" wont open from the "gear" in the corner,and I lost the Ubuntu Software
center from the launch pad andothers... However in searching for possible
the 4.2.0 initrd's are pretty sparse, the recent ones seem to have a
full set of modules and firmware (e.g. 18MB of drivers/net)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692208
Title:
initrd
Public bug reported:
My initrd in recent kernels is 4x larger than in slightly older kernels,
making /boot just large enough. It seems unlikely this growth is
intended:
-rw-r--r-- 1 root root 44052519 May 13 12:29 initrd.img-4.10.0-19-generic
-rw-r--r-- 1 root root 44050984 May 13 12:28
Public bug reported:
package: compiz-core 1:0.9.13.1+17.04.20170109-0ubuntu1
problem type: crash
Title: compiz crashed with SIGABRT
...
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux
Public bug reported:
1. Right now from the "gear" in the upper right corner I cannot
open System Settings and About this computer. However Help
Suspend, Lock and Shut Down all seem to work. This problem
started after applying a recent update a few days ago.
2. I have tried to report
Gunnar I had NO choice when opening this bug, it only
showed and accepted ubuntu-docs. I am not happy with
you reply, your action does nothing to improve product
quality. Instead of just closing this bug - a real bug,
maybe you could do something more productive like changing
it to a more
Public bug reported:
Running 17.04 the Software Updated says the SW is up-to-date.
As far as I can tell, the last SW update caused this problem.
Using the "gear icon" in the upper right corner I cannot
open "system settings..." or open About this computer.
I can select help or "shut down..."
Public bug reported:
Updated Ubuntu 16.10 to 17.04 (i386) and initially everything seemed to be ok.
Time only was displayed in title bar after some updates it no longer appears.
The tab in system settings for date/time shows time as selected but it is all
"grayed out" and I cannot change
Public bug reported:
UPGRADING TO 17.04
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-release-upgrader-core 1:17.04.6
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic i686
ApportVersion: 2.20.4-0ubuntu3
Architecture: i386
CrashDB: ubuntu
new at this, sorry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680287
Title:
compiz-core invalid core dump BFD Warning tmp/apport_core_6ywix5b7 is
truncated: expected core file size >= 112926
Public bug reported:
Full backtrace below.
Not seen this one before (machine has been running fine for many years),
so I guess it's Zesty kernel issue. Hit it while running a heavily busy
Firefox.
Apr 2 17:52:16 davros kernel: [17739.294897] [ cut here
]
Apr 2
My issue is now resolved.
I had already run the commands and rebooted and the issue went away. I
was unsure, however, whether or not simply getting into this state was
worthy of having the bug reported.
It had been several months since I had rebooted (even through several
updates, etc.) so I
Public bug reported:
This crash occurred while updating software.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
There seem to be 6 people+ hitting it -> marking confirmed
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643911
Title:
libvirt
** Also affects: libvirt (Ubuntu)
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/1643911
Title:
libvirt randomly crashes on xenial nodes with "*** Error
Any idea if the patched version will make it 16.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615337
Title:
libguestfs uses aug_get to get /files/etc/fstab/X/opt instead
Public bug reported:
Cant install ubuntu 16.04 from usb key .
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
Public bug reported:
Following some advice, I installed this package. It failed, I don't know
why. Anyway, I uninstalled it.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: ipmiutil (not installed)
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic
1 - 100 of 3687 matches
Mail list logo
