initramfs-tools 0.142ubuntu7 has an autopkgtest qemu-net that tests that
the hostname is set to the value provided by the DHCP server.
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343896#131
and mark this bug as Won't Fix.
** Changed in: openssh (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Summary changed:
- Fix CVE-2019-13115 in Focal
+ Fix CVE-2019-13115
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1968334
Title:
Fix CVE-2019-13115
To manage notifications about this
It's fixed in Debian by version 3.121 and therefore fixed in adduser
3.121ubuntu1 in Ubuntu 22.10 (kinetic).
** Changed in: adduser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug
Thanks for reporting this issue. Since you need to be root to create a
new user, this can probably not be used directly as exploit. But I agree
that creating a user "admin" should not create one that is in the admin
group. So either removing this configuration line or create a admin
group by
** Summary changed:
- Incorrect Sudo configuration
+ sudoers: admin group has permissions, but does not exist by default
** Changed in: sudo (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Status: New => Fix Released
** Changed in: apport
Milestone: None => 2.21.0
** Changed in: apport
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Description changed:
We have two cameras connected to Cam Link 4K and using OBS for live-
streaming. Suddenly during the live-stream the video input went to
black. The kernel message shows that the USB disconnect at 2332.127976s
(but we did not unplug anything). Some seconds later the
Public bug reported:
We have two cameras connected to Cam Link 4K and using OBS for live-
streaming. Suddenly during the live-stream the video input went to
black. The kernel message shows that the USB disconnect at 2332.127976s
(but we did not unplug anything). Some seconds later the kernel
Partial review:
* abs-path-revert.patch: Is there a bug report for it? If no, please file one.
If yes, please reference it.
* no-pkg-mangle-deps.patch: plaese forward to Debian. This change does not hurt
Debian.
* Can you adjust verify_deb to support gzip and xzst? Then this part can be
that require access to the Internet.
Closes: #1010881
[ Benjamin Drung ]
* Run all succeeding test cases again.
-- Benjamin Drung Mon, 23 May 2022 14:15:55 +0200
libcloud (3.4.1-3) unstable; urgency=medium
* Team upload.
[ Debian Janitor ]
* Remove constraints unnecessary since
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.21.0
** Changed in: apport
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: apport
Status: In Progress => Fix Committed
** Changed in: apport
Milestone: None => 2.21.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962454
Title:
Oops pages show
Synced iniparser 4.1-6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959346
Title:
Please merge iniparser 4.1-6 from Debian unstable
To manage notifications about this bug go to:
This bug was fixed in the package iniparser - 4.1-6
Sponsored for Dave Jones (waveform)
---
iniparser (4.1-6) unstable; urgency=medium
* debian/watch: Watch for tagged releases on github
-- Salvatore Bonaccorso Thu, 16 Dec 2021 09:43:45
+0100
iniparser (4.1-5) unstable;
cmake-test-clean.patch lacks a patch header. Is this patch forwarded to
upstream? Is that patch forwarded to Debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959346
Title:
Please merge
Public bug reported:
The apport test case test_run_report_bug_kernel_thread fails in my
schroot environment. My schroot environment has only one
/etc/apt/sources.list.d/ubuntu.sources file and no /etc/apt/sources.list
file.
Running following test script as non-root will fail:
!/usr/bin/python3
Please redirect this bug report against gnome-software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893369
Title:
gnome-software installs audacity from snap, which doesn't start
To manage
I had a look into running the test suite of python-invoke. Result:
python-invoke uses pytest-relaxed which is not packaged yet -> ITP for
pytest-relaxed: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1008768 -> pytest-relaxed does not support pytest
5 and 6:
** Bug watch added: Debian Bug tracker #1010360
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010360
** Also affects: openssl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010360
Importance: Unknown
Status: Unknown
--
You received this bug notification
Fix for Debian: https://salsa.debian.org/installer-
team/debootstrap/-/merge_requests/69
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971951
Title:
sh: 48: /usr/share/debootstrap/scripts/gutsy:
Public bug reported:
$ cat test.yaml
---
name: test
mmdebstrap:
suite: jammy
target: root.squashfs
variant: minbase
$ bdebstrap -c test.yaml
I: automatically chosen mode: unshare
I: chroot architecture amd64 is equal to the host's architecture
sh: 48: /usr/share/debootstrap/scripts/gutsy:
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding apport. This problem was most recently seen with version
2.17-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac
contains more
** Description changed:
- On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
+ On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
application
- If you want to uninstall a sottware, tthere is an error message : "no
+ If you want to uninstall a software,
Reproduction Part 2
===
I used divide-by-zero from chaos-marmosets to create a crash file and
deleted parts of CoreDump. Then I used following snippet to test the
modified crash file:
```python
import sys, apport
report = sys.argv[1]
r = apport.Report()
with open(report, 'rb')
** Package changed: apport (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968100
Title:
Reporting firefox bug redirect to general mozilla page
To manage notifications
Let's catch the zlib.error exception the same way as the other
exceptions are caught.
** Patch added: "apport_2.20.11-0ubuntu82.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1947800/+attachment/5580506/+files/apport_2.20.11-0ubuntu82.debdiff
--
You received this bug
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu71.1, the problem page at
https://errors.ubuntu.com/problem/e18a567631253a0239b6097c5b9fb6bc5bacdcaa
*** This bug is a duplicate of bug 1867204 ***
https://bugs.launchpad.net/bugs/1867204
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu27.23, the problem
*** This bug is a duplicate of bug 1867204 ***
https://bugs.launchpad.net/bugs/1867204
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu77, the problem
*** This bug is a duplicate of bug 1947800 ***
https://bugs.launchpad.net/bugs/1947800
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu80, the problem
*** This bug is a duplicate of bug 1947800 ***
https://bugs.launchpad.net/bugs/1947800
** This bug has been marked a duplicate of bug 1947800
*** This bug is a duplicate of bug 1947800 ***
https://bugs.launchpad.net/bugs/1947800
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu80, the problem
Bug analysis
whoopsie-upload-all reads the *.crash files (to upload them):
```
r = apport.Report()
with open(report, 'rb') as f:
r.load(f, binary='compressed')
```
ProblemReport.load reads the encoded data and keeps in compressed:
```python
block = base64.b64decode(line)
if
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947800
Title:
/usr/share/apport/whoopsie-upload-
all:zlib.error:/usr/share/apport/whoopsie-upload-
*** This bug is a duplicate of bug 1947800 ***
https://bugs.launchpad.net/bugs/1947800
** This bug has been marked a duplicate of bug 1947800
I tested your test case on Ubuntu 21.10 (impish) and it works there:
$ ssh-keygen -f fail.rsa -t rsa -N ''
Generating public/private rsa key pair.
Your identification has been saved in fail.rsa
Your public key has been saved in fail.rsa.pub
The key fingerprint is:
Uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968730
Title:
FFe paramiko 2.9.3
To manage notifications about this bug go to:
** Description changed:
paramiko 2.8.1 lacks support for RSA 2 and therefore cannot connect to
Jammy hosts with openssh >= 8.8p1-1 (see bug #1961979). I checked the
upstream changes between 2.8.1 (jammy version) and 2.9.3:
https://github.com/paramiko/paramiko/compare/2.8.1...2.9.3
I filed bug #1968730 as feature freeze exception request to fix this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961979
Title:
Can't connect to Jammy hosts (openssh >= 8.8p1-1)
To manage
Public bug reported:
paramiko 2.8.1 lacks support for RSA 2 and therefore cannot connect to
Jammy hosts with openssh >= 8.8p1-1 (see bug #1961979). I checked the
upstream changes between 2.8.1 (jammy version) and 2.9.3:
https://github.com/paramiko/paramiko/compare/2.8.1...2.9.3
The difference
** Attachment added: "paramiko-2.9.3-changelog.rst"
https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/1968730/+attachment/5579970/+files/paramiko-2.9.3-changelog.rst
** Description changed:
paramiko 2.8.1 lacks support for RSA 2 and therefore cannot connect to
Jammy hosts with
I checked the upstream changes between 2.8.1 (jammy version) and 2.9.3:
https://github.com/paramiko/paramiko/compare/2.8.1...2.9.3
There are only a few commits:
* Weird typos introduced 2 years ago, bah (only change to test cases)
* Longterm TODOs (adds only comments)
* Enhance kex DEBUG logging
** Description changed:
python3-paramiko can't connect to Jammy hosts, likely because of the
stricter signature requirements introduced in openssh 8.8p1-1.
Reproducer:
- 1. Setup a passwordless keypair and add localhost to known_hosts, so
- that:
+ 1. Setup a passwordless keypair and
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu70, the problem page at
https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800
contains
Finished the test cases, successfully tested on Kubuntu and Xubuntu
jammy live images, created merge request:
https://code.launchpad.net/~ubuntu-
installer/ubiquity/+git/ubiquity/+merge/419219
** Merge proposal linked:
I have a working patch for ubiquity that sets the GNOME keyboard there as well.
Next steps (next week):
* finish test cases
* test Kubuntu (KDE)
* then create merge request
I created bug #1968354 for open-vm-tools to make the udev trigger more
precise.
Site notes
==
If you do following
Able to recreate on Ubuntu Desktop amd64 22.04 daily 2022-04-08.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755452
Title:
ubiquity crashed with ValueError in command():
** Bug watch added: Debian Bug tracker #1009194
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009194
** Also affects: open-vm-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009194
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
open-vm-tools 2:11.3.5-1ubuntu4 (on Ubuntu 22.04) calls "udevadm
trigger" in it's postinst script (line 8). Since no options or
devpaths/files/units are specified, udevadm will trigger events for
**all** devices. This will trigger a lot of udev rules and can cause
unwanted
** Summary changed:
- [20.04] Keyboard layout not enabled immediately during installation when
typing username/password
+ [20.04] Keyboard layout changes during installation before typing
username/password
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Problem analysis
* ubiquity installs open-vm-tools.
* open-vm-tools calls "udevadm trigger" in it's postinst script (line 8).
* udevadm triggers all udev rules which includes all input devices.
* gdm-x-session reads /etc/default/keyboard and sets the keyboard layout.
*
The failing line 163 in BaseIO.php was introduced by debian/patches/add-
baseio-types.patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967860
Title:
autopackage tests fail
To manage
** Patch added: "0001-Set-GNOME-keyboard-layout-v2.patch"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/5577712/+files/0001-Set-GNOME-keyboard-layout-v2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I changed ubiquity (see 0001-Set-GNOME-keyboard-layout.patch) to add the
selected keyboard layout to org.gnome.desktop.input-sources sources.
This does not solve this problem, because org.gnome.desktop.input-
sources sources is already changed, but there is a discrepancy between
this setting and
Thanks to Nicolas Mouart and Dag Bjerkeli for analyzing the problem. I
could easily reproduce/simulate the problem:
Bug report
==
Tested on Ubuntu 21.10 with virt-manager. Created a virtual machine and
selected "Ubuntu 21.04" as OS (which uses machine type pc-q35-6.0) and
changed the
** Description changed:
Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as
OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D
acceleration.
- gnome-shell also crashes with 3D
** Description changed:
Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as
OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D
acceleration.
gnome-shell also crashes with 3D
** Description changed:
Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as
OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D
acceleration.
+
+ gnome-shell also crashes with 3D
Public bug reported:
Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as
OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D
acceleration.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
** Description changed:
During a fresh install of Ubuntu 20.04, selecting Norwegian keyboard is
provided and keys are responding correctly at that stage. But later when
entering user information the keyboard setting is wrong.
It looks like it have fallen back to English
I tested in a jammy schroot (with mmdebstrap 0.8.1-1):
$ apt install mmdebstrap qemu-user-static debian-archive-keyring
$ mmdebstrap -v --variant=minbase --mode=unshare --architectures=armel
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg testing example.tar
and that succeeds.
--
You
You might want to get it fixed for impish as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947810
Title:
autopkgtest-satdep.deb unpack fails on Debian images
To manage notifications about
Great. So your fix is included in autopkgtest 5.19 which was synced to
jammy yesterday: https://launchpad.net/ubuntu/+source/autopkgtest/5.19
** Changed in: autopkgtest (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I stumbled upon this bug as well, but I would force using gzip instead
of xz (for performance reasons).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947810
Title:
autopkgtest-satdep.deb unpack
Okay. So I just synced 36.0-2 now.
** Changed in: rdma-core (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/1946895
Title:
Merge rdma-core from Debian
Unsetting LD_PRELOAD only prevents the warning about libgtk3-nocsd.so.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950475
Title:
mmdebstrap fails for foreign architectures: dpkg: error: need
Public bug reported:
After upgrading to Ubuntu 21.10, mmdebstrap fails to build for foreign
architectures:
```
$ mmdebstrap -v --variant=minbase --mode=unshare --architectures=armel bullseye
example.tar
I: armel cannot be executed, falling back to qemu-user
I: automatically chosen format: tar
rdma-core 36.0-2 builds on jammy. How can I test that LTO does not work
and needs to be disabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946895
Title:
Merge rdma-core from Debian unstable
Installed linux 5.4.0-81.91 and verified that it is working.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932367
Installed linux 5.11.0.26.28 and verified that it is working.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
focal-proposed has linux 5.4.0-79.88, but this version does not include
the patch yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932367
Title:
Pixel format change broken for Elgato Cam Link 4K
** Description changed:
+ [Impact]
+
The Elgato Cam Link 4K HDMI video capture card reports to support three
different pixel formats, where the first format depends on the connected
HDMI device.
```
$ v4l2-ctl -d /dev/video0 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
- Type:
Thanks for the pointer. I will follow the process documented there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932367
Title:
Pixel format change broken for Elgato Cam Link 4K
To manage
** Patch removed:
"0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+attachment/5505364/+files/0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch
** Patch added:
Public bug reported:
The Elgato Cam Link 4K HDMI video capture card reports to support three
different pixel formats, where the first format depends on the connected
HDMI device.
```
$ v4l2-ctl -d /dev/video0 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]:
bdebstrap 0.1.2-1 is now in impish.
** Changed in: bdebstrap (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/1929613
Title:
Unblock version 0.1.1-2 from
The proposed package version is linux-kvm 5.4.0-1040.41
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925008
Title:
no memory hot-plugging in cloud-images
To manage notifications about this bug
I tried it as well on my work laptop which has a Intel Core i7-8850H CPU
(Coffee Lake-H) which show the same result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906454
Title:
Firefox does not
Public bug reported:
I use a Sony Alhpa camera attached to Elgato Cam Link 4K as webcam. The
only color format that is working with Cam Link 4K is NV12. Sadly
Firefox does not support NV12 (despite the source code containing
several third party libraries that refer to NV12). Looking at the kernel
Correction: Applying following patch does not solve this assertion
failure:
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 153a9ea..8e2674f 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -879,6 +879,11 @@ private:
if (tzid == nullptr)
return nullptr;
The underlying issue is that
i_cal_timezone_get_builtin_timezone_from_tzid and
i_cal_timezone_get_builtin_timezone included from /usr/include/libical-
glib/i-cal-timezone.h (libical-dev) fail to determine the timezone for
"Etc/Utc" or "Etc/UTC".
** Also affects: libical3 (Ubuntu)
Importance:
Public bug reported:
The site-specific browser (SSB) feature does not work, e.g. running:
firefox --ssb chat.google.com
will just open a new empty Firefox window. "browser.ssb" is set to
"true" in about:config.
Affected version: Firefox 74.0+build3-0ubuntu0.19.10.1 on Ubuntu 19.10
(eoan)
**
Public bug reported:
I tried to convert https://code.launchpad.net/~apport-
hackers/apport/trunk into git (on Ubuntu 19.10 with brz 3.0.1-6):
$ git init
$ bzr fast-export --plain ../apport.bzr | git fast-import
Traceback (most recent call last):
File
Public bug reported:
On Ubuntu 19.10 (amd64), building a Debian chroot with mmdebstrap's
fakechroot mode fails:
$ mmdebstrap -v --mode fakechroot --aptopt='Dir::Etc::Trusted
"/usr/share/keyrings/debian-archive-keyring.gpg"' buster /tmp/buster.tar.xz
[...]
I: extracting archives...
*** stack
Here is the backtrace:
Thread 1 "indicator-datet" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0 0x76eaa3eb in __GI_raise
I am not the only one running into this bug: https://ubuntu-
mate.community/t/clock-indicator-wont-appear-19-10/20424
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After upgrading to Ubuntu 19.10, indicator-datetime
15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:
$ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized
TZID:
The relevant traceback:
Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in
from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in
from ConfigParser import SafeConfigParser
ImportError: No module
This test failure is fixed in salt 2018.3.3+dfsg1-1 and therefore since
Ubuntu 19.04.
** Changed in: salt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since this is a bug in python-pip (not salt), I mark the bug for salt as
invalid.
** Changed in: salt (Ubuntu)
Status: New => Invalid
** Changed in: python-pip (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Upgrading to 2018.3 in Ubuntu 18.04 is not possible, but you could
upgrade to Ubuntu 19.04 instead. Can you please provide more details to
reproduce (and fix) these Jinja errors?
** Changed in: salt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
Can you still reproduce it with salt 2018.3.4~git20180207+dfsg1-1 in
Ubuntu 19.04?
** Bug watch added: Debian Bug tracker #910236
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910236
** Also affects: salt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910236
This is addressed in Ubuntu 19.04 with salt >= 2018.3.3+dfsg1-1.
** Changed in: salt (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/1797895
Title:
Fixed in salt 2018.3.3+dfsg1-1 and therefore in Ubuntu 19.04.
** Changed in: salt (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/1791642
Title:
Python 3.7 is supported since salt 2018.3.3+dfsg1-1 and therefore since
Ubuntu 19.04.
** Changed in: salt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch is part of 2018.3.3 and therefore fixed since
2018.3.3+dfsg1-1 (part of Ubuntu 19.04).
** Changed in: salt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When upgrading from Ubuntu 18.10 to 19.04, the package ebtables fails to
install. The alternatives
/etc/alternatives/ebtables
/etc/alternatives/ebtables-restore
/etc/alternatives/ebtables-save
where empty files instead of symlinks. I removed those files and then
the
** Also affects: unity-tweak-tool (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/1814506
Title:
Use nemo-desktop to draw desktop icons under
I verified that applying commit 223932c786ada7f758a7b7878a6ad2dae0d1e5fb
from https://github.com/systemd/systemd/pull/8728 on top of systemd
237-3ubuntu10.9 solves this bug.
Therefore please include the patch in systemd for Ubuntu 18.04.
** Description changed:
- root cause in systemd bug:
-
301 - 400 of 6961 matches
Mail list logo
