The system is now running 19.04 x64 desktop. The problem has not changed
in any obvious manner, although reporting of battery status for its
external logitech bluetooth mouse is now correct.
Ca anyone suggest how to perform further problem determination, or
perhaps even a circumvention. The 0% bat
Installed Bionic 18.04.2 i386 Desktop iso, (same one used by colin) on
a a Dell PowerEdge R320 and upgraded to the 5.0.0.22. I was able to
successfully boot the host on 5.0.0
ubuntu@ubuntu-PowerEdge-R320:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu
Static hostname: ubuntu-PowerEdge-R320
Icon name: computer-server
Chassis: server
Machine ID: 0f66377cdd544d0285f8c82631d6dff0
Boot ID: d1397f34572f43adbc0e7cee95a9fc3d
Operating System: Ubuntu 18.04.2 LTS
Kernel: Linux 5.0.0-21-generic
Arc
Hi Shrirang,
Your changes look like good candidate for u-boot upstream, you should
submit them upstream first. Once accepted, Eoan will pick them up and
then SRU back to Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
merged for 1
https://github.com/sosreport/sos/commit/9dc6b75f76062315c58196c51ffe9d1319988520#diff-d7d3c9ca39d610cbf8eb4c0bb5719a9f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804600
Title:
apt p
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800566
Title:
Make reset_devices parameter default for kdump and deco
** Package changed: gnome-disk-utility (Debian) => libblockdev (Debian)
** Changed in: libblockdev (Ubuntu)
Importance: Undecided => High
** Changed in: libblockdev (Ubuntu Disco)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837871
Title:
Add retry logic to snap-tool to make downloads more resilient
To m
Same patches were also applied to Disco
---
sysdig (0.24.1-1ubuntu2) disco; urgency=medium
* Add patch to fix build errors on arm64
-- Seth Forshee Thu, 14 Feb 2019 10:05:34
-0600
sysdig (0.24.1-1ubuntu1) disco; urgency=medium
* Add patch to fix build errors with Linux 5.0 caused by ch
Public bug reported:
I have the Settings icon locked to the favorites bar. When I click on
it the wait cursor comes up and the desktop is locked. I cannot
shutdown, except through the power button on my laptop.
Ubuntu 19.04 on Dell XPS15-9560.
** Affects: ubuntu
Importance: Undecided
This bug was fixed in the package kylin-nm - 1.0.0-1ubuntu0.1
---
kylin-nm (1.0.0-1ubuntu0.1) disco-proposed; urgency=medium
* SRU:
- Fix the wrong connection status. (LP: #1823843)
- Fix that unable to close after turned on the network.
(LP: #1823844)
- Implement
** No longer affects: ruby2.3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet agent using 100% CPU, in sched_yield() loop. Looks like an
issue with ruby2.3 which has
** No longer affects: ruby2.3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556783
Title:
ruby2.3 test failures on s390x
To manage notifications about this bug go to:
https://bugs.launchp
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830637
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830
I was mistaken, the TRENDnet TUC-ET2G is actually based on RTL8156 while
the TUC-ET5G is effectively based on Aquantia IC. I made wrong
assumption since Aquantia also has a USB3.0 to ETH 2.5Gbe bridge.
Anyhow, so I tested with RTL8156 driver you linked (which actually is
part of RTL8152 driver) un
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826051
Tit
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Also affects: ruby2.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ruby2.3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556783
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
When you say you cannot shutdown except through power button? Have you
tried [magic] sysrq keys to tell the kernel to safely shutdown? If
you're unfamiliar with them, this may be useful -
https://ubuntuforums.org
If you believe I'm in error (in last comment), please change status back
to New, and just comment a reason why you believe it's valid. Thanks
again for using Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Timo, I think the problem is with xorg-server,
along with mesa, it was present on the latest updates when the crash came up.
When kodi tries to load a video, its window simply closes.
If switch to Wayland, it works.
But everything is very buggy with this server, it's inoperable.
Maybe there are
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: virtualbox-guest-additions-iso (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
** Also affects: virtualbox-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virtualbox (Ubuntu Bionic)
** Also affects: virtualbox (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: virtualbox-hwe (Ubuntu Bionic)
Importance: Undecided
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833671
Title:
bond interfaces stop working after restart of systemd-networkd
To man
Hello quanxian, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Commenting on this old post I found via search because Uli.Heller's
suggestion worked for me to remove the snap core18 from Ubuntu 19.04.
The core18 snap was mounted thusly:
/dev/loop1355808 55808 0 100% /snap/core18/1066
First I disabled it:
snap disable core18
Then I unmo
Running ubuntu-bug on the .crash file in /var/crash gave an internal
error popup.
Trying your instructions on point 2 on this URL:
https://errors.ubuntu.com/user/b3e0d3deed6257fc1b9ae70c24b2a09705d4bb29b1c4e2619a81359775c05b871501564c588e4ed7c7807dfaafe1dd95c6ecb2b3cd1f89744001cf8ffbb9266
shows
Thanks Khurshid and Gunnar.
Hi Khurshid, can you help provide the details per comment #24 to proceed
further?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741027
Title:
[SRU] Screen sharing panel
Yes. Assuming upstream is correct that the problem is in the HP firmware
[1] then the only options are to ask HP for a BIOS fix, or to avoid
using UEFI on this machine.
I half believe it anyway... I also still wonder how Windows is able to
work on the machine and why the BIOS is only broken for Li
Please explain in more detail what problem you are experiencing.
If it is graphics-related then please try removing these kernel
parameters:
vesafb.invalid=1 drm.debug=0xe plymouth:debug
---
Veuillez expliquer plus en détail le problème que vous rencontrez.
S'il s'agit de graphiques, essayez
Can you please provide a `ls -la /var/crash` as the file names
themselves tell us what crashes occurred (inc. when), which is more than
we have currently.
Do the 'times' of the .crash files correspond to when you're likely to
have hit the 'power' button to force-shutdown? or if unsure just respon
Thanks for your reply. Closing.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002573
Title:
Firefox defunct processes
To
401 - 441 of 441 matches
Mail list logo
