@Mathieu, the issue described here was fixed, it's probably best to open
a new bug (& upstream as well if possible) with a full journal log and
description of your issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is the issue still present if the all packages are up to date?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843873
Title:
Sound distored on Hades Canyon NUC
To manage notifications about this
Public bug reported:
Please sync libgdiplus 6.0.4+dfsg-1 (universe) from Debian sid (main)
Changelog entries since current focal version 4.2-2:
libgdiplus (6.0.4+dfsg-1) unstable; urgency=medium
* [1d0918c] New upstream version 6.0.4
* [c8e4ab1] Forcibly skip tests
* [a0213b8] Pango is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849060
Title:
eoan/linux-gcp: 5.3.0-1006.6
After reading this:
* I know, one could as well call that a "feature", but it really is a
performance bug fix more than anything else. Also the SRU policy allows
exploitation/toleration of new HW especially for LTS releases.
Therefore I think this is fine as SRU.
I'm okay with that
Exits with the correct error code now:
bionic-arhhf$ stress-ng --rmap 10 -t 5
stress-ng: info: [7937] dispatching hogs: 10 rmap
stress-ng: info: [7937] cache allocate: using built-in defaults as unable to
determine cache details
stress-ng: fail: [7939] stress-ng-rmap: fallocate failed,
I think this comes from [1] which is in since 5.3.
This will be generated into s390x-linux-gnu/asm/unistd_64.h and such.
on x86-64 it was 220 all along, no change there.
/usr/include/x86_64-linux-gnu/asm/unistd_64.h:#define __NR_semtimedop 220
** Changed in: cargo (Ubuntu Xenial)
Status: New => In Progress
** Changed in: cargo (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cargo (Ubuntu Disco)
Status: New => In Progress
** Changed in: cargo (Ubuntu Eoan)
Status: New => In Progress
--
You
the updated the fwupd 1.2.10 ppa. It need the libxmlb that already in proposed
channel.
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and test newer mainline kernels
https://kernel.ubuntu.com/~kernel-ppa/mainline/
try 5.4-rc4 and if it doesn't work, drm-tip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847980
Title:
Lightdm is
I had the same bug. What I did:
sudo systemctl stop e2scrub_reap.service
(I had to run it in Xterm, because the gnome-terminal didn't launch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846499
I've upgraded to disco 19-04 and that does not change anything, always
the same problem.
But, today, I'm lucky there's a crash log in /var/crash, I join it.
** Attachment added: "_usr_bin_mate-settings-daemon.1000.crash"
** Bug watch added: Debian Bug tracker #942614
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942614
** Also affects: valgrind via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942614
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Agreed on Frank's last comment.
commit a32295c612c57990d17fb0f41e7134394b2f35f6
Author: Alexey Kardashevskiy
Date: Wed Dec 13 00:31:31 2017
vfio-pci: Allow mapping MSIX BAR
By default VFIO disables mapping of MSIX BAR to the userspace as
the userspace may program it in a way
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849733
Title:
resolved incorrectly limits TCP reply to edns0 payload
To manage notifications about this bug go to:
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846265
Title:
shiftfs: rework how shiftfs opens files
To manage
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846272
Title:
overlayfs: allow with shiftfs as underlay
To manage
Verified bug is now fixed:
bionic-arhhf$ cat /proc/cpuinfo | grep model | head -1
model name : ARMv7 Processor rev 1 (v7l)
bionic-arhhf$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847744
Title:
The issue remains the unchanged with 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
No way to encrypt at partition level (dual boot)
To manage notifications about this bug go
Test cases can always be adjusted - no doubt about it (and also the
reason why this is marred with Importance low).
But the case here is that the "de-facto" standard is that a short version or an
argument is usually introduced by one dash:
lsmem -v
and the long version by two dashes:
lsmem
Verified in version 1:11.1-1ubuntu7.4 best I can tell due to no
crashes...
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Jakob, or anyone else affected,
Accepted keystone into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/keystone/2:13.0.2-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've uploaded the transitional fwupdate to the queue, and rejected the
old fwupd upload because it was based on 1.2.5 and AIUI the desire is to
get 1.2.10 in bionic, ycheng promised to prepare that soon.
** Also affects: fwupdate (Ubuntu)
Importance: Undecided
Status: New
** Changed
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374714
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849658
Title:
resolved fallback
Workaround:
- unmount zfs volume 'sudo /var/snapd'
- uninstall package 'sudo apt purge snapd'
is error-free
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849515
Title:
package snapd (not
Thanks for following up, here's the log from dmesg.
I've removed some audit logs that are non-applicable.
** Attachment added: "Kernel log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823655/+attachment/5299986/+files/dmesg.txt
--
You received this bug notification because
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849058
Title:
eoan/linux-azure: 5.3.0-1005.5
The difference is in the includes:
Good:
grep -Hrn __NR_semtimedop *
asm-generic/unistd.h:539:#define __NR_semtimedop 192
asm-generic/unistd.h:540:__SC_COMP(__NR_semtimedop, sys_semtimedop,
compat_sys_semtimedop)
s390x-linux-gnu/bits/syscall.h:1782:#ifdef __NR_semtimedop
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374715
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849608
Title:
systemd resolv
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
include/seccomp.h
#define __PNR_semtimedop-204
#ifndef __NR_semtimedop
#define __NR_semtimedop __PNR_semtimedop
#endif /* __NR_semtime */
So if __NR_semtimedop is 392 then it would not set -204 and we'd get
this result.
Turns out that all but SCMP_SYS(semop) have changed on this
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
I run a short test :
root@m3545034:~# lsmem --v
lsmem from util-linux 2.34
root@m3545034:~# lsmem -V
lsmem from util-linux 2.34
root@m3545034:~# lsmem -v
lsmem: invalid option -- 'v'
Try 'lsmem --help' for more information.
Can the testcase be changed to --v ?
or is there a need for an upstream
Completed testing (regression) on disco on z13 LPAR according to test
case above - no issues found - updating tag.
** Attachment added: "regression_test_disco.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847590/+attachment/5299982/+files/regression_test_disco.txt
** Tags
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Completed testing (regression) on eoan on z13 LPAR according to test
case above - no issues found - updating tag.
** Attachment added: "regression_test_eoan.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847590/+attachment/5299985/+files/regression_test_eoan.txt
** Tags removed:
Completed testing (regression) on bionic on z13 LPAR according to test
case above - no issues found - updating tag.
** Attachment added: "regression_test_bionic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847590/+attachment/5299983/+files/regression_test_bionic.txt
** Tags
Note: it became a PIE executable in Eoan, but haven't we had pie as
default much longer?
The difference is in:
rc = seccomp_rule_add(ctx, SCMP_ACT_ALLOW, SCMP_SYS(semtimedop), 0);
In the bad case it returns -14
Good:
Breakpoint 2, seccomp_rule_add (ctx=0x2aa00049260, action=2147418112,
Can you please post a complete kernel log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823655
Title:
Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work
To manage notifications about
please test mesa 19.2.1 from ppa:ubuntu-x-swat/updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To manage notifications
https://lists.ubuntu.com/archives/kernel-team/2019-October/105034.html
** Changed in: linux-firmware (Ubuntu Bionic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Disco)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
**
This is non stripped and only 112 lines of C
./36-sim-ipc_syscalls: ELF 64-bit MSB pie executable, IBM S/390, version
1 (SYSV), dynamically linked, interpreter /lib/ld64.so.1,
BuildID[sha1]=15c4946540be396acecc4273529e252eceff398f, for GNU/Linux
3.2.0, with debug_info, not stripped
wc -l
Hello Seth, or anyone else affected,
Accepted rtl8812au into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/rtl8812au/4.3.8.12175.20140902
+dfsg-0ubuntu12~ubuntu18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by
The error is benign, meaning that the kernel simply tries to load a
driver for a device that is already managed by a different driver and
thus logs an error. I don't believe that this is the cause of the issue
you're seeing.
--
You received this bug notification because you are a member of
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299959/+files/Snap.Info.chromium.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/1849693/+attachment/5299953/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299952/+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/1849693
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299956/+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/1849693
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299949/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299950/+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/1849693
Title:
Note: the debug needs nothing very special
$ apt build-dep libseccomp
$ pull-lp-source libseccomp
$ cd libseccomp-2.4.1/
$ ./debian/rules build
Is enough to trigger the failing build.
To then afterwards re-iterate on the failing code run:
$ cd tests
$ ./36-sim-ipc_syscalls
Good: some output and
Can you please test this kernel:
https://people.canonical.com/~khfeng/lp1849721/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849721
Title:
Raydium Touchscreen on ThinkPad L390 does not work
To
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299951/+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/1849693
Title:
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299961/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299962/+files/Snap.Info.gtk-common-themes.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/1849693/+attachment/5299963/+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/1849693
Title:
Probably not a regression after all (as far as the snap is concerned),
the corresponding code in chrome/browser/platform_util_linux.cc hasn't
changed recently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299958/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299954/+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/1849693
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299960/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299957/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299955/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will the transfer of the .config/chromium files start again when
removing the snap/chromium files? So I could test if it works with a
second try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849693
apport information
** Tags added: apport-collected eoan snap
** Description changed:
I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser
for the first time, it should have imported all former
Hello Olivier,
No, I don't think that chromium was installed as snap before. I have
never installed snap things myself, only maybe such packages that were
installed by the system, AFAIK.
I did the apport-collect and attached the history.log
Regards
Gert
** Attachment added: "history.log"
Public bug reported:
running 14.04 to 16.04 upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu13.5
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset
Confirmed. I think this is a regression. I'm seeing this in the log:
LaunchProcess: failed to execvp:
xdg-email
snapd assumes that the application would call out to xdg-open, not xdg-
email.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in:
I wanted to have a good case for comparison, so I also spawned Disco and there
the same passes.
The subtests are reporting "SUCCESS" and overall it is skipped for non native.
Test 36-sim-ipc_syscalls%%023-1 result: SUCCESS
...
Test 36-sim-ipc_syscalls%%025-1 result: SKIPPED (only
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1798364
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ping, will the test case be improved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726068
Title:
debconf socket closes if aptdaemon/PK client exits
To manage notifications about this bug go to:
OpenCubicPlayer next version depends on this getting fixed
** Also affects: ocp (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/1839038
Title:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: linux (Ubuntu)
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/1840889
Title:
Black Screen on 18.04 + Intel Graphics with Kernel > 4.15.0-47
Hello Colin, or anyone else affected,
Accepted stress-ng into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/stress-
ng/0.09.25-1ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Colin, or anyone else affected,
Accepted stress-ng into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/stress-
ng/0.09.25-1ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Interestingly this is already FTBFS in Eoan.
I have created LXD environments doing rebuilds of the same source and they fail
the same way in Eoan and Focal.
The last successful build in Launchpad if from 4th of May, so something
else going into Eoan already broke this.
** Summary changed:
-
** Tags removed: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798364
Title:
Lubuntu 18.10 - screenfetch wrongly says LXDE (not LXQt)
To manage notifications about this bug go to:
Hello @juergh
I believe this issue is also affecting me, I reported this earlier this
year: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1823655
How are you progressing getting a fix into the kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Thanks for interests. I tried connect to monitor via windows 10 and
works properly but Ubuntu 19.10 did not recognize and give PKCS#7 error
(also many different solution tries and errors). After that reinstall
Ubuntu 18.04 with disabled secure boot and update drivers, Ubuntu
finally recognize HDMI
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849787
Title:
The dock is shown in front of full screen window (in my case X2Go
session) since 19.10
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (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/1847980
Title:
This issue has been fixed in the linux-generic 4.15.0-66.75 and linux-
generic-hwe-18.04 5.0.0-32.34~18.04.2 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840889
Title:
Black Screen on
** Tags added: oem-priority originate-from-1844304 presidio
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Disco)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Please run `apport-collect 1849183` to collect more logs to help
debugging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849183
Title:
Bluetooth devices doesn't get listed while turn off and then
Public bug reported:
See attached screenshot
** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot from 2019-10-25 09-28-27.png"
** Also affects: cargo (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: cargo (Ubuntu)
Status: New => In Progress
** Changed in: rustc (Ubuntu)
Status: New => Fix Released
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (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/1847980
Title:
it's not X to blame, but the one that starts it so moving to gdm3 hoping
that someone would have a clue
** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Due to the python 3.8 transition in focal this was rebuilt but fails atm.
=>
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz
The simulations fail in this case:
batch name: 36-sim-ipc_syscalls
test
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849675
Title:
Touch pad not working at all
To manage
Hi Brian,
from your log:
mysqld will log errors to /var/log/mysql/error.log
2019-10-24T14:30:52.608720Z 0 [ERROR] [MY-010946] [Server] Failed to start
mysqld daemon. Check mysqld error log.
Warning: Unable to start the server.
Job for mysql.service failed because the control process exited with
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
Yes.
Ian Johnson <1849...@bugs.launchpad.net> schrieb am Mi., 23. Okt. 2019,
22:49:
> >From the dpkg terminal log I see this:
>
> ```
> rm: das Entfernen von '/var/snap' ist nicht möglich: Das Gerät oder die
> Ressource ist belegt
> ```
>
> which google translate tells me means:
>
> ```
> rm:
** Description changed:
href="mailto:xyz; links don't work in the chromium snap package anymore
to open an external email client.
It used to work fine in the non-snap Chromium deb package, before Ubuntu
19.10.
In settings, if enabling "Allow sites to ask to become default handlers
Please test linux kernel 5.0.0-32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849697
Title:
~/devices
To manage notifications about this bug go to:
401 - 500 of 551 matches
Mail list logo
