Hi,
Ken - I think all I said in comment #2 still applies (and likely won't change).
It really is a non-issue warning - and even if you e.g. have a zero-
warning-allowed policy then you can easily avoid that by using a CPU
type that doesn't enable it by default or switch it on/off as needed. In
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832625
Title:
[UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826516
Title:
There are no complains from users, so I assume
erlang-p1-tls_1.0.20-1ubuntu0.1_amd64.deb fixed problem.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832933
Title:
upgrade to
Please test this kernel:
https://people.canonical.com/~khfeng/lp1832988/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832988
Title:
Intel 8260 Bluetooth not working
To manage notifications about
Public bug reported:
This is a new test for overlayfs:
<<>>
tag=fanotify06 stime=1560747299
cmdline="fanotify06"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1833028
and then change the status of the bug to 'Confirmed'.
If, due to the
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832101
Title:
systemd-networkd: Lost carrier e1000
To
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.6
---
ubuntu-release-upgrader (1:19.10.6) eoan; urgency=medium
* DistUpgradeQuirks.py: modify string regarding refreshing and installing
snaps so that it is translatable. (LP: #1824005)
-- Brian Murray Fri,
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1504445
Title:
FocalTech touchpad stops working after suspend
To manage
[Expired for acpi-support (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed-hwe (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed-hwe (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-meta (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ubuntu-meta (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1752613
[Expired for linux-signed-hwe (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed-hwe-edge (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe-edge (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for elogind (Ubuntu) because there has been no activity for 60
days.]
** Changed in: elogind (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for dovecot (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dovecot (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for virtualbox (Ubuntu) because there has been no activity for
60 days.]
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1824953
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> This is also described here: https://askubuntu.com/a/1041631/326601
That describes an unrelated issue.
** Description changed:
When I rebooted my system after an update, `/etc/resolv.conf` was
symlinked to `/run/resolvconf/resolv.conf`. That file did not have my
local domain name in
Does kernel parameter "nopti" help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833018
Title:
After Installing Updates, system fails to boot on first try
To manage notifications about this bug
> When I rebooted my system after an update, `/etc/resolv.conf` was
> symlinked to `/run/resolvconf/resolv.conf`
That is as expected, if you have the resolvconf package installed.
> That file did not have my local domain name in the search even though
> it is supplied by the dhcp server. The
Public bug reported:
Almost every boot attempt drops to initramfs prompt, requiring me to
type echo /dev/sdb >/sys/fs/bcache/register. Logs showing that attempt
to register caching device via udev rules was made, but failed with code
== 1.
Looks like an regression were introduced in upstream
In particular, note that /lib/systemd/system/resolvconf-pull-
resolved.{service,path} are meant to populate /run/resolvconf/interface
/systemd-resolved using the contents of /run/systemd/resolve/stub-
resolv.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu8
---
gnome-software (3.30.6-2ubuntu8) eoan; urgency=medium
* debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
-- Robert Ancell
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
** Tags removed: 5.0.0
** Tags added: 5.0 ubuntu-kvm-unit-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821394
Title:
vmx tests fail in kvm_unit_tests
To manage notifications about this bug
These tests have passed on node amaura, not naunamm.
Need to check if this is hw-specific.
** Tags added: 5.0 disco oem-osp1 ubuntu-ltp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830316
Title:
The attached RfKill.txt seems to suggest that Bluetooth is only turned
off in software. So maybe this is just a gnome-shell GUI bug, or gnome-
bluetooth.
To confirm this, please try turning it on by running this command in a
terminal:
rfkill unblock 0
** Also affects: gnome-shell (Ubuntu)
If the above command doesn't work then I would next focus on a possible
kernel problem in:
[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
** Summary changed:
- Bluetooth not working
+ Intel 8260 Bluetooth
This is affecting OEM-OSP1 (5.0.0-1009.10-oem-osp1) as well, we might
need to rebase this fix to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829812
Title:
Regression for
Pat,
Re comment #19, your crash (hang) reports there seem to show the gnome-
shell process behaving normally (in poll) and not stuck at all. That
doesn't tell us much but it would support the theory in comment #31.
** Summary changed:
- Login screen never appears on vmwgfx but installing kernel
On 6/16/19 6:51 PM, Eduardo Alcober wrote:
> Just eliminate the first command. just
>
> sudo grub-install
> sudo update-grub
>
> from your normal user.
>
> Sorry, Thanks.
>
The grub-install required a device name. I specified:
sudo grub-install /dev/sda
It said it was successful, and the "sudo
Hello!
Installed erlang-p1-tls_1.0.20-1ubuntu0.1_amd64.deb from ppa you
mentioned.
Now I can connect my psi to my ejabberd.
Thank you!
It's early morning here, I need to wait when most users will try to use
ejabberd.
I'll report in next several hours.
--
You received this bug notification
Interesting one of the commits mentioned above:
37efe80ce85f drm/vmwgfx: use monotonic event timestamps
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f)
is related to what I changed in the latest update to mutter:
Indeed there was a kernel update to 18.04 around the same time as the
mutter update which I thought was causing this bug.
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Bionic)
** No longer affects: mutter (Ubuntu Eoan)
** Also affects: linux (Ubuntu Eoan)
** Tags added: cursor hidpi
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- Wrong cursor size after screensaver
+ [hidpi] Cursor is too small after screensaver
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received
@Drew, have you tried user_id_attribute=uid as well in addition to
user_name_attribute=uid ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832766
Title:
LDAP group_members_are_ids = false fails in
Can you please reword that? I don't understand (and can't see in the
video) what the problem is here.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It sounds like you're trying to describe general frame skipping and
performance degradation as more apps are opened. Can you please put the
problem into words so we can be sure what the problem is you are
reporting?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Tags
*** This bug is a duplicate of bug 1800196 ***
https://bugs.launchpad.net/bugs/1800196
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1800196, so it is being marked as such. Please
It appears this crash is in:
/home/gjm/.local/share/gnome-
shell/extensions/wsmat...@martin.zurowietz.de
which is not part of Ubuntu, so we can't handle it here. Sorry.
I suggest you uninstall that extension to avoid the crash.
** Summary changed:
- Gnome-shell crashes frequently
+
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832869
Title:
gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
meta_display_list_windows →
Thanks. Since gnome-shell provides all the graphics (even the lock
screen), this bug is now assigned to gnome-shell only.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** No longer affects: gdm3 (Ubuntu)
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (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/1832869
Title:
I find a good way to solve this problem in ubuntu18.04: use dde file
manager create by deepin
sudo add-apt-repository ppa:leaeasy/dde
sudo apt install dde dde-file-manager
I think dde-file-manager is better than nautilus.
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows
meta_workspace_list_windows
+ gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV →
ffi_call()
--
You received this
Unfortunately we can't backport a fix which we don't know the location
of. And I don't see any links to a patch here. Also, we generally don't
support/patch gnome-shell on Ubuntu releases older than 18.04.
Anyway, this bug is closed and we can't be sure you are experiencing the
exact same issue.
This bug is closed. If you have any issues at all then please open a new
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759008
Title:
Revert automatic suspend by default for bionic?
To manage
** Tags removed: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746656
Title:
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError() from xwl_log_handler() from
I'm not sure monitors.xml is any more useful than the xrandr output we
already get... unless xrandr output is missing from crash bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722886
Title:
Ran into this problem on 18.04 server as well.
Removing the overriding line in /etc/default/grub.d/50-curtin-
settings.cfg works around it for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Hi,
Have you tried reinstalling grub? It's recommended after a big upgrade.
The sequence of commands is as follows:
su -
sudo grub-install
sudo update-grub
After this the machine should boot normally. Keep in touch.
Greetings,
EAC.
--
You received this bug notification because you are a
Just eliminate the first command. just
sudo grub-install
sudo update-grub
from your normal user.
Sorry, Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833018
Title:
After Installing
When I boot, but specify the other partition (also Lubuntu 18.04.2) -
the one that originally started having the boot problems - it boots
successfully.
When I boot, but specify the originally-installed kernel (linux-
image-4.15.0-20-generic), it also boots successfully.
Sometimes, on the boots
This change was made by a bot.
** Changed in: linux (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/1833018
Title:
After Installing Updates, system fails to
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833017
Title:
[needs-packaging] nativefier
To manage notifications about this bug go to:
Public bug reported:
I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After
installation, it rebooted with no problems.
I installed all updates, and on rebooting it failed to boot. The screen
had unreadable graphics in the top third of it.
On rebooting again, it booted okay,
Changed kernel parameter on Dell D620 and Dell 530s - both booting
properly first time since upgrade from kernel 47. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot
Public bug reported:
I would like to request that nativefier be packaged for Ubuntu. It can
already be installed via npm (npm install -g nativefier), but I prefer
to manage all of my global system packages in one place. I see that many
node packages are already packaged for Ubuntu.
Nativefier
Still affecting 18.04. Also note that upstream does not have an issue
tracker anymore, losing the linked issue above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780310
Title:
Option
Public bug reported:
GPT partitioned harddrive using UEFI.
Trying to do a dual-boot using an UEFI installer.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
On brainwash's suggestion (IRC #xubuntu-devel) I disabled UPower's Lid
handling with /etc/UPower/UPower.conf:
IgnoreLid=true
After six suspend-resume cycles this does seem to have prevented the issue.
*However* I then noticed that in the x-p-m dialog, General tab, the
options to control the
Ah, looks like this is a fault with apt-get for not detecting a non-
interactive install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833013
Title:
Interactive prompt during non-interactive
Public bug reported:
`apt-get install -y -qq ansible` runs `whiptail --backtitle Package
configuration --title Configuring libssl1.1:amd64 --output-fd 11
--defaultno --yesno -- There are services installed on your system which
need to be restarted when certain libraries, such as libpam, libc,
*** Bug 408759 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ktorrent in Ubuntu.
https://bugs.launchpad.net/bugs/1762167
Title:
ktorrent always crashes on exit
To manage notifications
I can confirm this behaviour. Although it's not Erlang PPA but rather
erlang-solutions repository:
https://packages.erlang-solutions.com/ubuntu bionic contrib
I also found similar bug in APT
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810622). And tried to run
synaptic with different
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: synaptic (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/1831185
Title:
I agree, it took me a long time to figure out the meanings of the
buttons as well. I would have found it easier to understand if there
was a red X for the muted state and picture of sound waves for unmuted
state, like the top two in this image here:
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Public bug reported:
Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pavucontrol (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/1807221
Title:
A change in xfwm4 made it so that the minimize button is now visible.
https://git.xfce.org/xfce/xfwm4/commit/?id=bd6481d170cebb56b33a38806e021a5781d82c6c
** Package changed: xfce4-settings (Ubuntu) => xfwm4 (Ubuntu)
** Changed in: xfwm4 (Ubuntu)
Status: Confirmed => Fix Released
--
You
A workaround is not a proper fix. Would it not make more sense to revert
the GTK commit which broke the menu behavior?
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Update: Disabling x-p-m Security > Lock screen when system is going to
sleep causes the LCD to be blank resume for the 1st cycle.
This definitely feels like some weird interaction with x-p-m, light-
locker, and logind.
--
You received this bug notification because you are a member of Ubuntu
And it gets weirder... with supend-lock disabled AND leaving x-p-m
dialog box on screen whilst suspending the LCD always gets enabled on
resume!
I tried leaving other application windows open but those don't have the
same effect.
--
You received this bug notification because you are a member of
I've done some more tests with another clean install of 19.04; The only
user setting I changed was on x-p-m for Laptop Lid Closed, On Battery =
suspend.
1st suspend=resume cycle is fine; user session re-appears after
unlocking with password
*BUT*
2nd suspend-resume cycle turns the LCD panel off
ethtool reports "highdma: on [fixed]", and won't let me switch it off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832101
Title:
systemd-networkd: Lost carrier e1000
To manage notifications
I have same issue here in 2019.
01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B
Mini PCI Adapter (rev 04)
M3N notebook
4.15.0-51-generic
Ubuntu 18.04.2 LTS
a lot of:
[11414.173675] ipw2100: Fatal interrupt. Scheduling firmware restart.
[12674.408121] ipw2100: Fatal
Hello Hui,
Sadly the kernel 5.2-rc4 dont run correctly on my Laptop.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832961
** Changed in: iperf (Debian)
Status: Confirmed => 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/1832401
Title:
iperf server will not exit
To manage notifications about this
1 - 100 of 132 matches
Mail list logo
