[Touch-packages] [Bug 1906091] [NEW] libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Public bug reported:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in both
libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc location=videoplayback.mp4
! decodebin ! videoconvert ! x264enc byte-stream=true
threads=1 tune=zerolatency
bitrate=400 key-int-max=50 option-
string="force-cfr=1" ! video/x-h264,profile=baseline,stream-
format="byte-stream" ! h264parse ! mpegtsmux !
hlssink location="/tmp/data%06d.ts" max-
files=100 playlist-length=10 playlist-
location="/tmp/kek" target-duration=10
playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
** Affects: x264 (Ubuntu)
Importance: Undecided
Status: New
** Tags: gst gstreamer h264 libx264 opencv
** Summary changed:
- libx264-148 libx264-152 conflict segmentation failt SIGSEGV
+ libx264-148 libx264-152 conflict segmentation fault SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Status in x264 package in Ubuntu:
New
Bug description:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
both libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc
location=videoplayback.mp4 ! decodebin !
[Touch-packages] [Bug 1905768] Re: ld: DWARF error: could not find variable specification at offset
** Changed in: binutils (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1905768 Title: ld: DWARF error: could not find variable specification at offset Status in binutils package in Ubuntu: Fix Released Status in binutils package in Debian: New Bug description: Fixed upstream. Please update (I still get the error in 2.35.1-1ubuntu1 on groovy). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1905768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906086] [NEW] DIsplay is limited to top half of the screen
Public bug reported: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO dmi.product.sku: T6T88PA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906086 Title: DIsplay is limited to top half of the screen Status in xorg package in Ubuntu: New Bug description: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO dmi.product.sku: T6T88PA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Touch-packages] [Bug 1905510] Re: utils-linux 2.36.1 breaks user mounts (cifs)
** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Committed Status in util-linux package in Debian: Unknown Bug description: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent
** Description changed: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": - renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie - renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie - renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie - renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie - new file: systemd/system/multi-user.target.wants/whoopsie.service + renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie + renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie + renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie + renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie + new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... - My /etc/ does a "whoopsie" file (/etc/whoopsie) which doesn't seem to be - present in clean installations of Ubuntu and which there is the + My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem + to be present in clean installations of Ubuntu and which there is the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. ** Description changed: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem - to be present in clean installations of Ubuntu and which there is the + to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I
[Touch-packages] [Bug 1906078] [NEW] Whoopsie sends bug reports automatically without consent
Public bug reported: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1906078 Title: Whoopsie sends bug reports automatically without consent Status in whoopsie package in Ubuntu: New Bug description: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. To manage notifications about this bug go to:
[Touch-packages] [Bug 1906074] Re: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1906074 Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 Status in tzdata package in Ubuntu: New Bug description: Attempted to uninstall AisleRiot Solitaire which was preinstalled with Ubuntu 20.04. Received an error that the process was locked by aptd, rebooted, retried, crashed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020d-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 18:25:55 2020 DuplicateSignature: package:tzdata:2020d-0ubuntu0.20.04 Setting up tzdata (2020d-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1906074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906074] [NEW] package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
Public bug reported: Attempted to uninstall AisleRiot Solitaire which was preinstalled with Ubuntu 20.04. Received an error that the process was locked by aptd, rebooted, retried, crashed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020d-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 18:25:55 2020 DuplicateSignature: package:tzdata:2020d-0ubuntu0.20.04 Setting up tzdata (2020d-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1906074 Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 Status in tzdata package in Ubuntu: New Bug description: Attempted to uninstall AisleRiot Solitaire which was preinstalled with Ubuntu 20.04. Received an error that the process was locked by aptd, rebooted, retried, crashed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020d-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 18:25:55 2020 DuplicateSignature: package:tzdata:2020d-0ubuntu0.20.04 Setting up tzdata (2020d-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1906074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Problems appear with changs on drivers for/and screen resolution -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine:
[Touch-packages] [Bug 1891953] Re: CVE-2019-8936
@alexmurray - The debdiff for Groovy is identical to the one from Focal (same source package version). Let me know if you need a distinct debdiff with the release pocket (groovy-security) identified. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Bionic: Fix Released Status in ntp source package in Focal: Confirmed Status in ntp source package in Groovy: Confirmed Status in ntp package in Debian: Fix Released Bug description: It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer dereference into NTP. An attacker could use this vulnerability to cause a denial of service (crash). https://people.canonical.com/~ubuntu- security/cve/2019/CVE-2019-8936.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891953] Re: CVE-2019-8936
Patch for Focal ** Patch added: "Patch for Focal" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+attachment/5438836/+files/1-ntp_4.2.8p12+dfsg-3ubuntu5.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Bionic: Fix Released Status in ntp source package in Focal: Confirmed Status in ntp source package in Groovy: Confirmed Status in ntp package in Debian: Fix Released Bug description: It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer dereference into NTP. An attacker could use this vulnerability to cause a denial of service (crash). https://people.canonical.com/~ubuntu- security/cve/2019/CVE-2019-8936.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
systemctl --user status pulseaudio.service ** Attachment added: "systemctl --user status pulseaudio.service" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5438826/+files/systemctl_--user_status_pulseaudio.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906061] [NEW] vim package links against libcanberra
Public bug reported: vim 8.1 and newer has decided to link against libcanberra for "sound support", which pulls in several other reasonably unnecessary packages (libasound2, libvorbis to name a couple) for server environments. Presumably the --disable-canberra flag should be applied on configure. Focal+, as far as I can tell. See also https://bugs.archlinux.org/task/63073 ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1906061 Title: vim package links against libcanberra Status in vim package in Ubuntu: New Bug description: vim 8.1 and newer has decided to link against libcanberra for "sound support", which pulls in several other reasonably unnecessary packages (libasound2, libvorbis to name a couple) for server environments. Presumably the --disable-canberra flag should be applied on configure. Focal+, as far as I can tell. See also https://bugs.archlinux.org/task/63073 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1906061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl
** Summary changed: - htop shows 100% usage of systemd-udevd + htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl -- 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/1905167 Title: htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765141] Re: [amdgpu][radeon][regression] Full screen white flash from time to time (Wayland and X11)
I am on Ubuntu 20.04 and never observed that problem. -- 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/1765141 Title: [amdgpu][radeon][regression] Full screen white flash from time to time (Wayland and X11) Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I am using Ubuntu 18.04 with gnome shell on Wayland. From time to time, maybe every one or two hours, the desktop becomes white for a fraction of second. I guess it is just one frame (1/60 of second). It looks like a full filled rectangle of white color but it is so fast I cannot verify to be sure (the only solution I'm thinking of would be to have a fast recording camera pointed to my display). I did not experience that problem on Ubuntu 17.10 with Wayland. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 19:26:15 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-07 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
failed install, tried in both ubuntu 20.04.1 and 20.10. It works fine when I install ubuntu last time, for somewhat reason I nuke my LTS install and wanted to try 20.10 then get redirected into this page, then tried to get back to 20.04.1 install with another usb get redirected to this page as well. both same option with "Install third party software - enabled". system : intel i7-9700KF and nVidia gtx1660, -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
IMO it is a bug in systemd-timesyncd (see LP: #1880839) that it adjusts time backward automatically and thus this won't become a real issue until 2036. -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905655] Re: PulseAudio release 14.0
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:14.0-1ubuntu1 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905655 Title: PulseAudio release 14.0 Status in pulseaudio package in Ubuntu: Fix Committed Bug description: PulseAudio release 14.0 is now out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
Hello Alex, or anyone else affected, Accepted whoopsie into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.72.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: whoopsie (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: New Status in whoopsie source package in Focal: New Status in whoopsie source package in Groovy: Fix Committed Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. [Test Case] We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified. [Regression Potential] Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker. Original Description Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905969] [NEW] Asus Zephyrus G14 microphone not works
Public bug reported: I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA GeForce GTX 1650. I am use 5.9.8-050908-generic kernel from (kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/) dmamchyts@ga401ih:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" I have some problem with notebook microphone. When I use headphones via 3.5 jack - all works fine. But without headphones - system doesn't see any microphone device in settings. I am using KDE dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Also, I try to report issue into kernel team (they help me to fix issue with speakers), you can find some into it: https://bugzilla.kernel.org/show_bug.cgi?id=210359 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 Uname: Linux 5.9.8-050908-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 17:13:59 2020 InstallationDate: Installed on 2020-11-10 (17 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905969 Title: Asus Zephyrus G14 microphone not works Status in pulseaudio package in Ubuntu: New Bug description: I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA GeForce GTX 1650. I am use 5.9.8-050908-generic kernel from (kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/) dmamchyts@ga401ih:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" I have some problem with notebook microphone. When I use headphones via 3.5 jack - all works fine. But without headphones - system doesn't see any microphone device in settings. I am using KDE dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Also, I try to report issue into kernel team (they help me to fix issue with speakers), you can find some into it: https://bugzilla.kernel.org/show_bug.cgi?id=210359 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 Uname: Linux 5.9.8-050908-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 17:13:59 2020 InstallationDate: Installed on 2020-11-10 (17 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No
[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Description changed:
+ [Impact]
+
+ * Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
+ * The option is available on grub and will let you with a broken system,
partially cloned.
+
+ [Test Case]
+
+ * Boot on a system, using ZFS and ZSys.
+ * In grub, select "History" entry
+ * Select one of the "Revert" option: the system should boot after being
reverted with an older version.
+
+
+ [Where problems could occur]
+ * The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
+ * We replace dd with another way (more robust and simple) for generating
this ID.
+
+
+ -
+
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which
[Touch-packages] [Bug 1905953] Re: Xorg crash
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905953 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: hangs on when shutdown dell inspiron 3443 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:08:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Nov 27 17:57:31 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-54-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0656] Subsystem: Dell GM108M [GeForce 840M] [1028:0656] InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Inspiron 3443 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=UUID=c01998b1-8f09-4926-82c8-91624db2b067 ro intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09H9GH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3443:pvrA07:rvnDellInc.:rn09H9GH:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3443 dmi.product.sku: 0656 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905953] [NEW] Xorg crash
You have been subscribed to a public bug: hangs on when shutdown dell inspiron 3443 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:08:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Nov 27 17:57:31 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-54-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0656] Subsystem: Dell GM108M [GeForce 840M] [1028:0656] InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Inspiron 3443 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=UUID=c01998b1-8f09-4926-82c8-91624db2b067 ro intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09H9GH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3443:pvrA07:rvnDellInc.:rn09H9GH:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3443 dmi.product.sku: 0656 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 crash ubuntu -- Xorg crash https://bugs.launchpad.net/bugs/1905953 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
We don have this net/pmtu test in bionic 4.15 and this has already landed on 5.4, therefore I will close this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Invalid ** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Won't Fix -- 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/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: Fix Released Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Invalid Status in linux source package in Bionic: Won't Fix Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905560] Re: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Thanks a lot. You are absolutely right. After removing the old stuff from /usr/local/lib und rebuilding ld.so.cache there is no problem any longer. Xserver runs fine with version: 2.34.2-0ubuntu2~20.04.1 now. Sorry for your inconvenience and again, many thanks. Klaus p.s. will close this bug ** Changed in: at-spi2-atk (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used Status in at-spi2-atk package in Ubuntu: Invalid Bug description: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
I confirm that the version 0.62.0-2ubuntu2.12 fixes the 0.62.0-2ubuntu2.11 bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output Status in poppler package in Ubuntu: Invalid Status in poppler source package in Xenial: Fix Released Status in poppler source package in Bionic: Fix Released Bug description: The security updates 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 break the Splash output rendering, for example if using the xpdf utility that relies on Poppler splash output, or as used by the GDAL library (the issue was detected due to breakage in GDAL continuous integration tests) I've traced the root cause to those security updates enabling in 'rules' CMYK (--enable-cmyk for 0.41.0-0ubuntu1.15 and -DSPLASH_CMYK=ON for 0.62.0-2ubuntu2.11) Building without CMYK restore poppler in a working state. It should be noted that even on the upstream 0.41.0 version, enabling CMYK result in a non-functional build, so it is not related to the patches applied on top of it, but really on enabling CMYK The issue can be verified with "xpdf test_ogc_bp.pdf" with the attached test_ogc_bp.pdf file. With the new packages, xpdf crashes, whereas with older ones it displays a 20x20 greyscale image. Or with "gdal_translate test_ogc_bp.pdf out.png -of PNG" when installing the "gdal-bin" package, that currently errors out with a message like "ERROR 1: Bitmap decoded size (18623872x0) doesn't match raster size (20x20)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905704] Re: xpdf segmentation fault
*** This bug is a duplicate of bug 1905741 *** https://bugs.launchpad.net/bugs/1905741 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 1905729, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: poppler (Ubuntu) Importance: Undecided => High ** Changed in: poppler (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault Status in poppler package in Ubuntu: Fix Released Bug description: When I installed the latest updates this morning, xpdf started crashing with all pdf files. xpdf uses libpoppler73:amd64 and this library was updated from version 0.62.0-2ubuntu2.10 to 0.62.0-2ubuntu2.11. xpdf itself was not updated. $ xpdf foo.pdf Segmentation fault (core dumped) (gdb) run Starting program: /usr/bin/xpdf.real [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x55569173 in ?? () (gdb) bt #0 0x55569173 in ?? () #1 0x55565123 in ?? () #2 0x5556521c in ?? () #3 0x55561616 in ?? () #4 0x7737ddb9 in Gfx::go(bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #5 0x7737de8b in Gfx::display(Object*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #6 0x773c9e31 in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #7 0x55563af6 in ?? () #8 0x55566aa0 in ?? () #9 0x5556ca31 in ?? () #10 0x555619c6 in ?? () #11 0x55572e57 in ?? () #12 0x779b7a78 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #13 0x779ee9e1 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #14 0x779eef65 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #15 0x779c0bd3 in _XmDispatchGadgetInput () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #16 0x77a6dae2 in _XmGadgetActivate () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #17 0x77050a0d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #18 0x77051937 in _XtTranslateEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #19 0x77029e52 in XtDispatchEventToWidget () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #20 0x7702a83d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #21 0x7702a919 in XtDispatchEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #22 0x770365cf in XtAppProcessEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #23 0x7702ad2d in XtAppMainLoop () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #24 0x55561115 in ?? () #25 0x76140bf7 in __libc_start_main (main=0x55560b30, argc=1, argv=0x7fffde78, init=, fini=, rtld_fini=, stack_end=0x7fffde68) at ../csu/libc-start.c:310 #26 0x5556146a in ?? () $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ dpkg -l|grep xpdf ii xpdf 3.04-7 amd64Portable Document Format (PDF) reader ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpoppler73:amd64 0.62.0-2ubuntu2.11 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Thu Nov 26 11:57:55 2020 SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905704] Re: xpdf segmentation fault
*** This bug is a duplicate of bug 1905741 *** https://bugs.launchpad.net/bugs/1905741 bug #1905741 rather ** This bug has been marked a duplicate of bug 1905741 poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault Status in poppler package in Ubuntu: Fix Released Bug description: When I installed the latest updates this morning, xpdf started crashing with all pdf files. xpdf uses libpoppler73:amd64 and this library was updated from version 0.62.0-2ubuntu2.10 to 0.62.0-2ubuntu2.11. xpdf itself was not updated. $ xpdf foo.pdf Segmentation fault (core dumped) (gdb) run Starting program: /usr/bin/xpdf.real [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x55569173 in ?? () (gdb) bt #0 0x55569173 in ?? () #1 0x55565123 in ?? () #2 0x5556521c in ?? () #3 0x55561616 in ?? () #4 0x7737ddb9 in Gfx::go(bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #5 0x7737de8b in Gfx::display(Object*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #6 0x773c9e31 in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #7 0x55563af6 in ?? () #8 0x55566aa0 in ?? () #9 0x5556ca31 in ?? () #10 0x555619c6 in ?? () #11 0x55572e57 in ?? () #12 0x779b7a78 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #13 0x779ee9e1 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #14 0x779eef65 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #15 0x779c0bd3 in _XmDispatchGadgetInput () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #16 0x77a6dae2 in _XmGadgetActivate () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #17 0x77050a0d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #18 0x77051937 in _XtTranslateEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #19 0x77029e52 in XtDispatchEventToWidget () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #20 0x7702a83d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #21 0x7702a919 in XtDispatchEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #22 0x770365cf in XtAppProcessEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #23 0x7702ad2d in XtAppMainLoop () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #24 0x55561115 in ?? () #25 0x76140bf7 in __libc_start_main (main=0x55560b30, argc=1, argv=0x7fffde78, init=, fini=, rtld_fini=, stack_end=0x7fffde68) at ../csu/libc-start.c:310 #26 0x5556146a in ?? () $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ dpkg -l|grep xpdf ii xpdf 3.04-7 amd64Portable Document Format (PDF) reader ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpoppler73:amd64 0.62.0-2ubuntu2.11 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Thu Nov 26 11:57:55 2020 SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 I have an Epson TM BA Thermal network printer, configured in CUPS After today's unattended upgrade it stopped working Logs found on server [540009.389033] pdftoraster[63919]: segfault at d0400 ip 557a50f569a8 sp 7ffd5ca826d8 error 6 in pdftoraster[557a50f52000+8000] Thu Nov 26 14:14:19 2020: apport: report /var/crash/_usr_lib_cups_filter_pdftoraster.7.crash already exists and unseen, doing nothing to avoid disk usage DoS # dpkg -S /usr/lib/cups/filter/pdftoraster cups-filters-core-drivers: /usr/lib/cups/filter/pdftoraster Start-Date: 2019-11-25 17:01:06 Install cups-filters-core-drivers:amd64 # dpkg -l|grep cups-filters-core-drivers ii cups-filters-core-drivers 1.20.2-0ubuntu3.1 I checked what was updated with unattended upgrade Start-Date: 2020-11-24 06:20:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpulse0:amd64 (1:11.1-1ubuntu7.10, 1:11.1-1ubuntu7.11) End-Date: 2020-11-24 06:20:10 and I rolled back # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/poppler-utils_0.62.0-2ubuntu2.10_amd64.deb # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/libpoppler73_0.62.0-2ubuntu2.10_amd64.deb # ls apt/ libpoppler73_0.62.0-2ubuntu2.10_amd64.deb poppler-utils_0.62.0-2ubuntu2.10_amd64.deb #dpkg -R --install apt/ and started to work again and of course apt-mark hold libpoppler73 poppler-utils # apt-cache policy poppler-utils libpoppler73 poppler-utils: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libpoppler73: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output Status in poppler package in Ubuntu: Invalid Status in poppler source package in Xenial: Fix Released Status in poppler source package in Bionic: Fix Released Bug description: The security updates 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 break the Splash output rendering, for example if using the xpdf utility that relies on Poppler splash output, or as used by the GDAL library (the issue was detected due to breakage in GDAL continuous integration tests) I've traced the root cause to those security updates enabling in 'rules' CMYK (--enable-cmyk for 0.41.0-0ubuntu1.15 and -DSPLASH_CMYK=ON for 0.62.0-2ubuntu2.11) Building without CMYK restore poppler in a working state. It should be noted that even on the upstream 0.41.0 version, enabling CMYK result in a non-functional build, so it is not related to the patches applied on top of it, but really on enabling CMYK The issue can be verified with "xpdf test_ogc_bp.pdf" with the attached test_ogc_bp.pdf file. With the new packages, xpdf crashes, whereas with older ones it displays a 20x20 greyscale image. Or with "gdal_translate test_ogc_bp.pdf out.png -of PNG" when installing the "gdal-bin" package, that currently errors out with a message like "ERROR 1: Bitmap decoded size (18623872x0) doesn't match raster size (20x20)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905793] Re: latest poppler xenial update breaks xpdf
*** This bug is a duplicate of bug 1905741 *** https://bugs.launchpad.net/bugs/1905741 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 1905741, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: poppler (Ubuntu) Importance: Undecided => High ** Changed in: poppler (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 1905741 poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905793 Title: latest poppler xenial update breaks xpdf Status in poppler package in Ubuntu: Fix Released Bug description: There were three updates over the last two days. with poppler (0.41.0-0ubuntu1.16) I find xpdf (3.04-1-ubuntu1.1) crashes on startup, on any file, every time. The version 0.41.0-0ubuntu1.13 worked correctly. I'm not sure about the ones in between. Perhaps this is a classic bug, back again. See, e.g., https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/669211 Description: Ubuntu 16.04.7 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905560] Re: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
> # ldd -r /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 | grep atk > libatk-1.0.so.0 => /usr/local/lib/libatk-1.0.so.0 (0x7f29f0ee9000) That's your issue, /usr/local is a directory not used by Ubuntu but meant for local installations to take over the distribution, it seems like you installed an older version that the Ubuntu one in there and that's it's loaded instead of the official one and creating the issue. Cleaning the /usr/local/lib content should make things better if you could try -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used Status in at-spi2-atk package in Ubuntu: Incomplete Bug description: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902244] Autopkgtest regression report (mesa/20.2.1-1~ubuntu0.20.04.1)
All autopkgtests for the newly accepted mesa (20.2.1-1~ubuntu0.20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: wlroots/0.10.0-2 (s390x, arm64, armhf, amd64) konsole/unknown (armhf) clutter-1.0/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905817] Re: Thumbnail
> it doesn't display the thumbnail Preview of the file Please clarify which program "it" is. Can you attach a screenshot of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905817 Title: Thumbnail Status in Ubuntu: Incomplete Bug description: Sorry. I am using xubuntu 16.04 linux. I tried installing themes, icons and others, because I thought it didn't look good, so I used it. But the problem I want to report is that after I apply it, the photo, video or so on, it doesn't display the thumbnail Preview of the file. I tried to restore the original settings but still, is this a bug? Then when I enter the file manager using sudo thunar / nautilus, the thumbnail is shown here? On the other hand, if you don't use it with sudo access, it won't show up. Please help, I've installed ffmpegthumbnailer and one other thing, but still. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-123.126~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-123-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 27 10:59:43 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9853] (rev 40) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mullins [Radeon R2 Graphics] [1043:1360] InstallationDate: Installed on 2020-10-03 (54 days ago) InstallationMedia: Xubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) MachineType: ASUSTeK COMPUTER INC. X540YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-123-generic root=UUID=14f9398a-5d01-4368-b455-954d3cdc98bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540YA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540YA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540YA.311:bd11/25/2016:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X540YA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Nov 27 10:08:12 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905817] Re: Thumbnail
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905817 Title: Thumbnail Status in Ubuntu: Incomplete Bug description: Sorry. I am using xubuntu 16.04 linux. I tried installing themes, icons and others, because I thought it didn't look good, so I used it. But the problem I want to report is that after I apply it, the photo, video or so on, it doesn't display the thumbnail Preview of the file. I tried to restore the original settings but still, is this a bug? Then when I enter the file manager using sudo thunar / nautilus, the thumbnail is shown here? On the other hand, if you don't use it with sudo access, it won't show up. Please help, I've installed ffmpegthumbnailer and one other thing, but still. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-123.126~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-123-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 27 10:59:43 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9853] (rev 40) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mullins [Radeon R2 Graphics] [1043:1360] InstallationDate: Installed on 2020-10-03 (54 days ago) InstallationMedia: Xubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) MachineType: ASUSTeK COMPUTER INC. X540YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-123-generic root=UUID=14f9398a-5d01-4368-b455-954d3cdc98bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540YA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540YA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540YA.311:bd11/25/2016:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X540YA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Nov 27 10:08:12 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905817] [NEW] Thumbnail
You have been subscribed to a public bug: Sorry. I am using xubuntu 16.04 linux. I tried installing themes, icons and others, because I thought it didn't look good, so I used it. But the problem I want to report is that after I apply it, the photo, video or so on, it doesn't display the thumbnail Preview of the file. I tried to restore the original settings but still, is this a bug? Then when I enter the file manager using sudo thunar / nautilus, the thumbnail is shown here? On the other hand, if you don't use it with sudo access, it won't show up. Please help, I've installed ffmpegthumbnailer and one other thing, but still. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-123.126~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-123-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 27 10:59:43 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9853] (rev 40) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mullins [Radeon R2 Graphics] [1043:1360] InstallationDate: Installed on 2020-10-03 (54 days ago) InstallationMedia: Xubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) MachineType: ASUSTeK COMPUTER INC. X540YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-123-generic root=UUID=14f9398a-5d01-4368-b455-954d3cdc98bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540YA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540YA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540YA.311:bd11/25/2016:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X540YA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Nov 27 10:08:12 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- Thumbnail https://bugs.launchpad.net/bugs/1905817 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
