Public bug reported:
I was using chrome
deluge was running in the background
I got 3 quick error messages that other apps were shutting down but I
didn't get the names
Then, all applications disappeared from screen
running desktop UI but NO apps
All running apps just stopped.
No error
Launchpad has imported 19 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=204237.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: Linux Kernel Bug Tracker #204237
https://bugzilla.kernel.org/show_bug.cgi?id=204237
** Changed in: linux
Importance: Medium => Unknown
** Changed in: linux
Status: Invalid => Unknown
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #205083 => Linux
** Summary changed:
- Upgrade to Python 2.7.9 (backporting features from PEP 466)
+ Upgrade to Python 2.7.17 (backporting features from PEP 466)
** Tags removed: precise trusty utopic
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Touch
autosynced for 20.04 LTS
** Changed in: v4l-utils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1844992
Title:
Update to
Thanks for report. ubuntu-docs is for bugs in the desktop documentation,
though, and this is apparently not about that. Changing affected
package.
The window on my 19.10 (attached) does not look exactly as the one in
your screenshot. I have a "Connect" button at the top right which
probably would
You have been subscribed to a public bug:
I am trying to add an online account, nextcloud
three fields show, server, username and password.
There is no Apply or OK button.
I cannot add the account.
Resizing the window does not help. Fields just get longer, still no
buttons.
Ubuntu 19.10
**
Still happens on 237-3ubuntu10.31
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1813400
Title:
systemctl doesn't respect --dry-run
Status in systemd package in Ubuntu:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Kodi devs-team were very conservative they would not help and asked me
to wait Ubuntu fix the bug.
Kodi is a reference to a bug that affects every graphical software
installed.
I'm observing every new mesa and kernels upgrades, I'll keep informing.
--
You received this bug notification because
bueno pero en conclusión que se puede hacer con ese error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1647638
Title:
W: APT had planned for dpkg to do more than it
No, Kodi does not crash anymore with x-swat and since official mesa
19.0.8-0ubuntu0~18.04.2
But it's followed by another problem, it's not 100% solved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: audit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
This is not unreasonable given that I have not been able to find a
simple way to reproduce the first failure. I will focus on the long
list of easily repeatable problems with this port.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
change the term "blank screen" to "unresponsive blank screen" in the
above. Sorry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1849886
Title:
lightdm does
Public bug reported:
if you follow the directions on https://wiki.ubuntu.com/ARM/RaspberryPi
sudo apt-get install xubuntu-desktop
about 20% thru the installation it will ask which window manager you want
(using dpkg-reconfigure).
if you select lightdm, you will only get a blank greeter screen
This is a duplicate of bug 204237.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1846539
Title:
[broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
*** This bug has been marked as a duplicate of bug 204237 ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1846539
Title:
[broadwell-rt286, playback] Since Linux
** Changed in: linux
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1846539
Title:
[broadwell-rt286, playback] Since Linux 5.2rc2
This bug was fixed in the package unattended-upgrades - 1.15
---
unattended-upgrades (1.15) unstable; urgency=medium
[ Tobias Bannert ]
* update german translation.
Improved some formulations and punctuation.
[ Maarten ]
* Update Dutch translation (Closes: #941672)
[
This bug was fixed in the package unattended-upgrades - 1.15
---
unattended-upgrades (1.15) unstable; urgency=medium
[ Tobias Bannert ]
* update german translation.
Improved some formulations and punctuation.
[ Maarten ]
* Update Dutch translation (Closes: #941672)
[
This bug is about kodi crashing, so does it crash with 19.2.1 or not?
If you have other issues, test with 19.10 and then file them upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
as for testing more AMD hw, (accelerated) media decoding is not within
the scope of hw enablement as required by the OEM's (on any GPU)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman
wrote:
> I looked at this for a few minutes, and it seems strange that it works
> at all (at boot) since networkd sets the ipv6 mtu before bringing the
> link up, but the kernel resets the ipv6 mtu to the device mtu on link
> up. I must be missing
Filed https://gitlab.gnome.org/GNOME/gtk/issues/2221 in case it's an upstream
bug.
I'll probably regret that.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2221
https://gitlab.gnome.org/GNOME/gtk/issues/2221
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
This problem occurs when accessing the systems "setting" menu only after
you try to select "devices" such as printers. The display goes haywire
and refuses to respond to users selections. The only way to recover is
to right-click the gnome menu icon on the left side of
That was really fast response, or I think a bugfix independent of my bug
report. Anyway, in the recently zsynced new daily iso file
add-apt-repository
works in Lubuntu focal :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I looked at this for a few minutes, and it seems strange that it works
at all (at boot) since networkd sets the ipv6 mtu before bringing the
link up, but the kernel resets the ipv6 mtu to the device mtu on link
up. I must be missing something.
--
You received this bug notification because you
Public bug reported:
I try to make the connection with an NSA that lives on the same network
of my Ubuntu 1804 server, however performing authentication via SSH
hangs in Debu1: SSH2_MSG_KEXINIT sent. Tracked error: Conection closed
** Affects: openssh (Ubuntu)
Importance: Undecided
The are no packages for Ubuntu 19.10 (Eoan) in that PPA. I'll contact
someone who can update the wiki page, but I'm setting this bug to
Invalid.
** Changed in: software-properties (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
Thanks. Let's put both tasks as Triaged again then, since it's obviously
not fixed in disco and bionic.
I don't think this qualifies as a regression though, since the feature
was never available before. It's just not finished since the systemd
side of this isn't complete.
** Changed in: systemd
I tried it on the live session USB 3.0, Ubuntu 19.10 (I checked the disk
for defects: no errors found). I still had to manually enable the sound
over HDMI for the TV.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
Public bug reported:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c &&
gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
All autopkgtests for the newly accepted python3-stdlib-extensions
(3.7.5-1~19.04) for disco have finished running.
The following regressions have been reported in tests triggered by the package:
thonny/3.1.1-1 (s390x)
python3.8/3.8.0~a3-2 (amd64, arm64, s390x, i386, armhf, ppc64el)
Just tested your ppa with mesa 19.2.1-1ubuntu1~18.04.1~ppa2, thank you
Since mesa 19.0.8-0ubuntu0~18.04.2 the image produced by Ubuntu with all
media players and browsers is very dark, like the contrast and black
levels were adjusted at a very low value. It became worse than before,
including
Also tried with the iproute2 in bionic-backports - same result
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1849856
Title:
ip commands error with mellanox devices in
Public bug reported:
Kernel: using 5.0.0-23-generic from hwe-edge
Configuring a mellanox connectx device with configured VF's into
switchdev (rather than legacy) mode result in the ip cli tool erroring
when trying to query the interface state:
$ sudo ip link
Error: Buffer too small for object.
** Description changed:
[impact]
glibc's getaddrinfo() uses EDNS0 to talk to resolved, and it sets its
payload limit to 1200. When the response is larger than 1200, resolved
will limit the response and set the truncate flag. This causes
getaddrinfo() to switch to TCP and request
I reinstalled this morning and got a lot further, but it still does not
work.
The script now works but it does not find the repo
oot@ubuntu:/home/ubuntu# apt-get update
Hit:1 http://ports.ubuntu.com/ubuntu-ports eoan InRelease
Ign:2 http://ppa.launchpad.net/ubuntu-raspi2/ppa/ubuntu eoan
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/1849835
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The video works with kernel 5.4-rc4 form https://kernel.ubuntu.com
/~kernel-ppa/mainline/.
Thank you for your patience.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Tested unattended-upgrades/1.10ubuntu5.2 on Disco:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-disco/disco/amd64/u/unattended-
upgrades/20191025_130642_9d5e1@/log.gz
...
E: Failed to fetch
Public bug reported:
I tested to use a ppa because I wanted to test if mkusb will work in
focal. But
add-apt-repository
does not work.
---
lubuntu@lubuntu:~$ sudo add-apt-repository ppa:mkusb/ppa # existing ppa
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107,
** Also affects: glib2.0 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu Eoan)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Iain Lane
Thanks Łukasz and Christian. I find the block-proposed-* tags idea
interesting if that's not too much work on your side.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Changed in: libseccomp
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
network-manager/1.10.6-2ubuntu1.2 (amd64, arm64, i386, ppc64el)
systemd/237-3ubuntu10.31 (i386, ppc64el)
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
network-manager/1.10.6-2ubuntu1.2 (amd64, arm64, i386, ppc64el)
systemd/237-3ubuntu10.31 (i386, ppc64el)
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
network-manager/1.10.6-2ubuntu1.2 (amd64, arm64, i386, ppc64el)
systemd/237-3ubuntu10.31 (i386, ppc64el)
Please ignore confusing comment about HP. It should have read my old HP
Printer had no issues :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1849824
Title:
Cup over usb
Public bug reported:
I've tried everything I can find on the internet and on Ubuntu. Nothing
works: changing parameters as per instructions, no go. cat text
>/dev/usb/lp0 does not work either. Using cups the printer remains
steadfastly inactive. "Catting" wakes up the printer to indicate data is
TODO:
a) wait for 2.4.2 and 2.5.0 to be released and pick those
b) if urgent pick and backport [1]
[1]:
https://github.com/seccomp/libseccomp/pull/176/commits/e4d38dcfd44743a55728b336d008ec8e37c1b344
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Subscribing ubuntu-security to monitor this together with us as often enough
they do libseccomp.
IMHO We don't have any urgency to go ahead of upstream, unless a fast re-build
is needed.
** Changed in: libseccomp (Ubuntu)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu
Bug still exists on Ubuntu 16.04.6 LTS, Kernel 4.14.140. Found when
looking for what was causing xrandr to reset screens to full brightness
and gamma. Even if `colord` isn't culprit, life is easier with less spam
in journalctl.
Ignore extra `s` in `fails` below (line wrap off) for bug report:
$
And as usual once you know what you search:
=> https://github.com/seccomp/libseccomp/issues/166
** Bug watch added: github.com/seccomp/libseccomp/issues #166
https://github.com/seccomp/libseccomp/issues/166
** Also affects: libseccomp via
https://github.com/seccomp/libseccomp/issues/166
Well this change made the ID 392 "known" to all architectures (in a try
to sync numbers across everywhere) but it fails on those it isn't
implemented (32bit, ppc, s390x + sparc which we don't have).
The path registering these calls goes
seccomp_rule_add
-> seccomp_rule_add_array
->
Upstream/master branch still is on 4.15-rc7 AND still uses __PNR_* for the
definitions.
I'll open an issue to further discuss it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Hello Dan, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello dwmw2, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello bugproxy, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Tested 1.14ubuntu1.1 on Eoan:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan/eoan/amd64/u/unattended-
upgrades/20191016_223206_2d8a4@/log.gz
...
autopkgtest [22:31:56]: summary
run-testsPASS
Dropping block-proposed-eoan tag, since releasing to release pocket is
now to be approved by the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1848354
Tested 1.1ubuntu1.18.04.7~16.04.4 on Xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unattended-upgrades/20191024_220650_7dfdf@/log.gz
...
The URI
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849658
Title:
resolved fallback to TCP
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849608
Title:
systemd resolv should
Tested 1.1ubuntu1.18.04.12 on Bionic:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20191024_213859_e45c8@/log.gz
...
Allowed origins are: origin=Debian,codename=sid,label=Debian,
the kernel driver seems perfectly happy though.. could you change to
tty1 and copy /var/log/Xorg.0.log somewhere and then attach here
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
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
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849733
Title:
resolved incorrectly limits TCP reply to edns0 payload
Status in systemd package in
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
Touch seeded packages, which is subscribed to e2fsprogs in 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
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849658
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
Touch seeded packages, which is subscribed to pulseaudio in
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
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
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849608
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,
please test mesa 19.2.1 from ppa:ubuntu-x-swat/updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
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
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
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
ping, will the test case be improved?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1726068
Title:
debconf socket closes if aptdaemon/PK client exits
Status in apper
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:
-
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
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
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
Touch seeded packages, which is subscribed to lightdm in 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
19.10 shipped with mesa 19.2.1
** Project changed: mesa => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
You have been subscribed to a public bug:
Description:
Mesa Vulkan VK_INTEL_performance_query extension
Adds support to Mesa and kernel for a new Vulkan extension called
“VK_INTEL_performance_query” enabling exposure of Intel based GPU metric
collection. Enable support for query based metrics
** Changed in: ibus (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1835541
Title:
ibus only provides non-standard UK keyboard layouts
using 'nomodeset' disables the intel gpu completely, so vulkan not
working is the least of your problems ;)
you could try installing newer mainline kernels from
kernel.ubuntu.com/~kernel-ppa/mainline/
maybe start from v5.4-rc and if it doesn't work, try drm-tip. Install
the amd64 version of
92 matches
Mail list logo
