[Touch-packages] [Bug 1832439] Re: GStreamer installation is missing a plug-in
Please help me to clear this bug. ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/mesa/+question/681353 ** Tags added: gstreamer -- 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/1832439 Title: GStreamer installation is missing a plug-in Status in mesa package in Ubuntu: Invalid Bug description: When i try to play this .mov file using gstreamer i get this following errors, i even tried .avi and .mp4 formats nothing helped. I need to configure this gstreamer plugin correctly to run my matlab code. Please help me on this. #gst-launch-1.0 playbin uri=file:/home/user/file.MOV Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Missing element: H.264 (High Profile) decoder WARNING: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: No decoder available for type 'video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true'. Additional debug info: gsturidecodebin.c(921): unknown_type_cb (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0 ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: Your GStreamer installation is missing a plug-in. Additional debug info: gsturidecodebin.c(988): no_more_pads_full (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: no suitable plugins found: gstdecodebin2.c(4640): gst_decode_bin_expose (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0: no suitable plugins found: Missing decoder: H.264 (High Profile) (video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true) ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... $ gst-launch-1.0 --version gst-launch-1.0 version 1.14.1 GStreamer 1.14.1 https://launchpad.net/distros/ubuntu/+source/gstreamer1.0 Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1832439/+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 1832110] Re: Resource Sharing with multiple sshd services
Robie, There are several options moving forward: 1) We need the /run/sshd file (see Ubuntu's man sshd page) to be configurable. The problem with locating the privilege separation directory in a fixed location, the systemd does not do well in multiple sshd instance assignments. The systemd will delete the processes RuntimeDirectory upon completion of the process. 2) The original OpenSSH 7.6p1 source code assigns the privilege separation directory to /var/empty (see OpenSSH man sshd page). If we assign it to /var/empty, then we get into a philosophical argument about making the /var/empty directory in an Ubuntu system. The frustration I have with both the OpenSSH teams and the Ubuntu teams is neither want to take ownership. I am trying to provide a solution to both teams and I am getting complete rejection. As far as the upstream support, we have 2 options, specifically: 1) Implement a command line option; I propose [-s separation_directory_name]. This would required editing only 1 file (i.e. sshd.c), so upstream modifications would be minimal. 2) Implement a sshd_config option; I propose "PrivSepDir separation_directory_name". This has less of a chance of conflicting with any upstream change. I cannot imagine a conflict but someone always has a better mouse-trap. So how can we come to consensus on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1832110 Title: Resource Sharing with multiple sshd services Status in openssh package in Ubuntu: Won't Fix Bug description: Ubuntu: 18.04.2 LTS OpenSSH: 7.6p1 I am having a problem starting multiple sshd processes. The default location of the sshd privilege separation directory is hard-coded to /run/sshd (see man page). If I want to have 2 sshd services using systemd, I need to write 2 service files, let's call them sshd_wan.service ans sshd_lan.service. Both of these services need to have their own "RuntimeDirectory=sshd_wan" and "RuntimeDirectory=sshd_lan". If you do not have separate RuntimeDirectory definitions for the 2 services, then when one service is killed/faults/restarts/stops/etc. the systemd (or init) process deletes the RuntimeDirectory and causes the other service to crash since a RuntimeDirectory does not exist. The problem is the hard-coding of the sshd Privilege Separation Directory. We need to modify the OpenBSD/OpenSSH sshd code to provision command line assignment of the privilege separation directory. I have attempted to contact the OpenSSH team (i.e. OpenSSH.com) and they say it is a Ubuntu problem. I reported this in Ubuntu bug #1831765 and Ubuntu (e.g. Paride Legovini, June 6, 2019 @ 2:55AM PDT) rejected it because I described the problem using the init.d example. I know how to modify the sshd.c file in OpenSSH 7.6p1, the problem is getting Ubuntu and OpenSSH to admit there is a problem and it needs to be fixed. The problem is still there regardless if you are using Upstart (i.e. init.d) or systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+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 1832439] [NEW] GStreamer installation is missing a plug-in
Public bug reported: When i try to play this .mov file using gstreamer i get this following errors, i even tried .avi and .mp4 formats nothing helped. I need to configure this gstreamer plugin correctly to run my matlab code. Please help me on this. #gst-launch-1.0 playbin uri=file:/home/user/file.MOV Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Missing element: H.264 (High Profile) decoder WARNING: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: No decoder available for type 'video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true'. Additional debug info: gsturidecodebin.c(921): unknown_type_cb (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0 ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: Your GStreamer installation is missing a plug-in. Additional debug info: gsturidecodebin.c(988): no_more_pads_full (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: no suitable plugins found: gstdecodebin2.c(4640): gst_decode_bin_expose (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0: no suitable plugins found: Missing decoder: H.264 (High Profile) (video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true) ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... $ gst-launch-1.0 --version gst-launch-1.0 version 1.14.1 GStreamer 1.14.1 https://launchpad.net/distros/ubuntu/+source/gstreamer1.0 Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Thanks ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1832439 Title: GStreamer installation is missing a plug-in Status in mesa package in Ubuntu: New Bug description: When i try to play this .mov file using gstreamer i get this following errors, i even tried .avi and .mp4 formats nothing helped. I need to configure this gstreamer plugin correctly to run my matlab code. Please help me on this. #gst-launch-1.0 playbin uri=file:/home/user/file.MOV Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Missing element: H.264 (High Profile) decoder WARNING: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: No decoder available for type 'video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true'. Additional debug info: gsturidecodebin.c(921): unknown_type_cb (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0 ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: Your GStreamer installation is missing a plug-in. Additional debug info: gsturidecodebin.c(988): no_more_pads_full (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0: no suitable plugins found: gstdecodebin2.c(4640): gst_decode_bin_expose (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0: no suitable plugins found: Missing decoder: H.264 (High Profile) (video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)5.1, profile=(string)high, codec_data=(buffer)01640033ffe1003627640033ac34c803c0043ec05a808080a07d20001d4c1d0c000727080001c9c3977971a18000e4e1393872ef2e1f0884538001000428ee3830, width=(int)3840, height=(int)2160, framerate=(fraction)3/1001, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true) ERROR: pipeline doesn't want to preroll. Setting
[Touch-packages] [Bug 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
** Attachment added: "IMG_20190612_102743067.jpg" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+attachment/5270262/+files/IMG_20190612_102743067.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Will do, thanks. -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+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 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
hi, I'm getting the same error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset
Launchpad has imported 13 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1282285. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-11-16T02:50:21+00:00 gizmo wrote: Description of problem: When playing audio through the Jabra Evolve 65 UC headset using either the USB cable or the Jabra Link 360 USB dongle, sound is played back too fast, with a 'chipmunk' effect. I don't know if the recording side is affected or not, but people have not commented on it if it is. Version-Release number of selected component (if applicable): Name: pulseaudio Arch: x86_64 Epoch : 0 Version : 6.0 Release : 8.fc22 Size: 3.3 M Repo: @System Name: alsa-plugins-pulseaudio Arch: i686 Epoch : 0 Version : 1.0.29 Release : 1.fc22 Size: 101 k Repo: @System How reproducible: Always Steps to Reproduce: 1. Plug in headset using USB cable. 2. Play audio Actual results: Audio plays fast. Buffered audio streams (like youtube) play without gaps, but realtime streams (like Skype, or Jabber) play with gaps. Expected results: Audio should play back at the normal rate with no gaps. Additional info: My Logitech USB headset plays just fine. When using the Jabra headset in BlueTooth mode, audio playback is normal using either the A2DP audio profile or the HSP/HFP. When connected with the USB cable lsusb reports the Jabra device as: Bus 001 Device 008: ID 0b0e:030b GN Netcom The Jabra device plays just fine on Windows, using the same computer. System is running KDE with Phonon GStreamer and alsa. I honestly don't know if this is a Pulse problem or an ALSA problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/0 On 2016-01-26T20:16:12+00:00 gizmo wrote: This bug has been open now for 2 months with zero movement. Is there anything I can do to help out here? I'm willing to troubleshoot, I just have no idea what to do next. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/1 On 2016-01-29T18:50:29+00:00 wtaymans wrote: I'm pretty sure that this is an alsa problem. The driver probably configures the wrong samplerate or maybe it needs a tweak for this particular hardware. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/2 On 2016-02-15T17:11:38+00:00 joerg.pareigis wrote: Exactly the same here. Trying with newest version of Debian 8 and SuSE 42.1. The headset plays too fast with a short gap every second. Regardless which connection is used. Directly via USB-Cable, or via BT-Dongle. Both with the same result. It plays the correct speed when connected via Bluetooth to Android devices. Connected at Windows PC it pays also without any spot. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/3 On 2016-02-15T19:13:10+00:00 gizmo wrote: (In reply to Wim Taymans from comment #2) > I'm pretty sure that this is an alsa problem. The driver probably configures > the wrong samplerate or maybe it needs a tweak for this particular hardware. Ok, so I've got the same question; what can I do to help troubleshoot this? Guys, I'm willing to be your eyes and hands here, but these eyes and hands need a brain to direct them. :) Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/4 On 2016-03-05T22:15:20+00:00 bs.alex.mail wrote: Hi. I've had the same problem. Here is workaround that helped me: In file /etc/pulse/daemon.conf replace --- ;default-sample-rate = 44100 | v with --- default-sample-rate = 48000 And then reload pulseaudio pulseaudio -k Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/5 On 2016-03-08T03:56:03+00:00 gizmo wrote: Just tried this, and it appears to work here as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/6 On 2016-07-19T20:15:30+00:00 bcotton wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce
[Touch-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2
** Changed in: pulseaudio Status: Unknown => Fix Released -- 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/1806860 Title: Pulseaudio module-jack-source unable to connect to jackd2 Status in PulseAudio: Fix Released Status in jackd2 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604 --- When installing jackd2 in ubuntu 18.04, i am unable to load the module-jack-source. Syslog gives me: Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to server failed< Dec 5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: Failed to load module "module-jack-source" (argument: ""): initialization failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)< Dec 5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)<] Dec 5 11:49:51 nvidio So the path to the shared memory location is not as expected. When jackd2 is running i have: hcw@nvidion:$ cd /dev/shm/ hcw@nvidion:/dev/shm$ ls jack-1000-0 jack_sem.1000_default_1000_0_system jack_sem.1000_default_jack_rack jack_sem.1000_jack_default_1000_0_system jack-1000-1 jack_sem.1000_default_freewheel jack_sem.1000_default_qjackctl jack-shm-registry jack_default_1000_0 jack_sem.1000_default_jack_mixer jack_sem.1000_default_system So it seems module-jack-source / sink are guessing the wrong shared memory paths to the jackd2 server.. Versions: jackd2 1.9.12~dfsg-2 pulseaudio-module-jack 1:11.1-1ubuntu7.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago) UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video wireshark _MarkForUpload: True dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 042NDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7566 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952 mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1806860/+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 1832419] Re: Xorg freeze
Does the freeze only happen when connected to wifi? I can see a couple of errors from the kernel graphics driver suggesting the display might freeze: [ 598.213901] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ... [ 3696.507718] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ... Please try logging into "Ubuntu on Wayland" and tell us if that helps. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + Display freezes ** Summary changed: - Display freezes + Acer Chromebook [banon] display freezes -- 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/1832419 Title: Acer Chromebook [banon] display freezes Status in linux package in Ubuntu: Incomplete Bug description: Freezes when connected to wifi. Running lsof -i and closing some of the processes results in black display, need to restart computer. i can use the computer for very short periods when connected to the internet, frequently the display freezes requiring restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Tue Jun 11 18:39:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: GOOGLE Banon ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-51-generic SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832419/+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 1832369] Re: [Thomson THN14B] Internal speaker does not work
Can you please try booting Ubuntu 19.04 from USB and tell us if that fixes the problem? http://releases.ubuntu.com/19.04/ Please also note that Ubuntu 18.10 will reach end-of-life next month (https://wiki.ubuntu.com/Releases). ** Summary changed: - AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER + [Thomson THN14B] Internal speaker does not work ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- 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/1832369 Title: [Thomson THN14B] Internal speaker does not work Status in linux package in Ubuntu: New Bug description: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago) dmi.bios.date: 01/02/2018 dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: THN14B dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Thomson modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832369/+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 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2
** Bug watch added: PulseAudio #604 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604 Importance: Unknown Status: Unknown -- 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/1806860 Title: Pulseaudio module-jack-source unable to connect to jackd2 Status in PulseAudio: Unknown Status in jackd2 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604 --- When installing jackd2 in ubuntu 18.04, i am unable to load the module-jack-source. Syslog gives me: Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to server failed< Dec 5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: Failed to load module "module-jack-source" (argument: ""): initialization failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)< Dec 5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)<] Dec 5 11:49:51 nvidio So the path to the shared memory location is not as expected. When jackd2 is running i have: hcw@nvidion:$ cd /dev/shm/ hcw@nvidion:/dev/shm$ ls jack-1000-0 jack_sem.1000_default_1000_0_system jack_sem.1000_default_jack_rack jack_sem.1000_jack_default_1000_0_system jack-1000-1 jack_sem.1000_default_freewheel jack_sem.1000_default_qjackctl jack-shm-registry jack_default_1000_0 jack_sem.1000_default_jack_mixer jack_sem.1000_default_system So it seems module-jack-source / sink are guessing the wrong shared memory paths to the jackd2 server.. Versions: jackd2 1.9.12~dfsg-2 pulseaudio-module-jack 1:11.1-1ubuntu7.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago) UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video wireshark _MarkForUpload: True dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 042NDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7566 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952 mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1806860/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Filip, Since you are the original reporter and no longer experience a problem then I would prefer to keep this bug closed. --- Gabriele, If you are experiencing audio problems then please open a new bug by running: ubuntu-bug pulseaudio so that we can review the details of your affected machine. ** Changed in: linux (Ubuntu) Status: Expired => Fix Released ** Changed in: pulseaudio (Ubuntu) Status: Expired => Fix Released -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+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 1832421] [NEW] openssl reboot needed message using incorrect path to X server
Public bug reported: Hello, the openssl library postinst file is using pidof /usr/bin/X, but that doesn't appear to be the path to the X11 server any more: debian/libssl1.1.postinst: # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/bin/X > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi On my 18.04 LTS laptop: $ ps auxw | grep Xorg root 2440 0.5 0.4 495932 78996 tty7 Rsl+ May10 264:45 /usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Jun 11 18:06:51 2019 InstallationDate: Installed on 2012-10-18 (2427 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832421 Title: openssl reboot needed message using incorrect path to X server Status in openssl package in Ubuntu: New Bug description: Hello, the openssl library postinst file is using pidof /usr/bin/X, but that doesn't appear to be the path to the X11 server any more: debian/libssl1.1.postinst: # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/bin/X > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi On my 18.04 LTS laptop: $ ps auxw | grep Xorg root 2440 0.5 0.4 495932 78996 tty7 Rsl+ May10 264:45 /usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Jun 11 18:06:51 2019 InstallationDate: Installed on 2012-10-18 (2427 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832421/+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 1828215] Re: openssl ca -spkac output regressed
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Cosmic: Confirmed Status in openssl source package in Disco: Confirmed Status in openssl source package in Eoan: Fix Committed Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] * OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf -passin stdin -batch -spkac input_file -startdate 190121130654Z Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+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 1018204] Re:
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=835863. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-06-27T10:29:19+00:00 jlieskov wrote: Common Vulnerabilities and Exposures assigned an identifier CVE-2012-2807 to the following vulnerability: Multiple integer overflows in libxml2, as used in Google Chrome before 20.0.1132.43, on 64-bit Linux platforms allow remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors. References: [1] http://code.google.com/p/chromium/issues/detail?id=129930 [2] http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/1 On 2012-06-28T12:08:51+00:00 jlieskov wrote: Relevant Google Chrome patch: [3] http://git.chromium.org/gitweb/?p=chromium/src.git;a=commitdiff;h=f183580d61c054f7f6bb35cfe29e1b342390fbeb Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/4 On 2012-07-18T10:26:45+00:00 veillard wrote: Okay, i finally pushed a patch upstream that I think should backport rather easily http://git.gnome.org/browse/libxml2/commit/?id=459eeb9dc752d5185f57ff6b135027f11981a626 that one http://git.gnome.org/browse/libxml2/commit/?id=4f9fdc709c4861c390cd84e2ed1fd878b3442e28 should also be applied in the errata to avoid similar problem elsewhere. Somehow that's not a complete fix but that's the most immediate and simple way to stop the given problem. I'm still working on a (rather large and intrusive) set of patches for upstream but I would not suggest to push that in RHEL. For fedora I may be tempted to rebase once a new libxml2 version is out Daniel Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/7 On 2012-07-27T07:08:17+00:00 huzaifas wrote: The above patches, described in comment #4 seems to solve the problem here. libxml2 no longer crashes with them. For Red Hat Enterprise Linux use case, we may however require few more patches from upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/8 On 2012-07-27T08:42:59+00:00 huzaifas wrote: Created libxml2 tracking bugs for this issue Affects: fedora-all [bug 843743] Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/9 On 2012-09-04T21:37:12+00:00 teger wrote: This has been reported over 2 months ago with a possible fix coming in a little over a month. Is there any plan of action to fix libxml2 vulnerabilities? Primarily this is a bump to put in back on someones to do list. Thank you Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/10 On 2012-09-18T17:21:34+00:00 errata-xmlrpc wrote: This issue has been addressed in following products: Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Via RHSA-2012:1288 https://rhn.redhat.com/errata/RHSA-2012-1288.html Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/12 On 2012-09-20T02:42:09+00:00 huzaifas wrote: Created mingw32-libxml2 tracking bugs for this issue Affects: epel-5 [bug 858914] Affects: fedora-all [bug 858915] Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/13 On 2013-01-04T10:35:49+00:00 huzaifas wrote: This flaw affects x86_64 version of libxml2 only, however mingw32-libxml2 is only shipped as x86 (32-bit) and therefore it is not affected. Statement: This issue affected the version of libxml2 as shipped with Red Hat Enterprise Linux 5 and 6 has been addressed via RHSA-2012:1288. This issue does not affect the version of mingw32-libxml2 as shipped with Red Hat Enterprise Linux 6. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1018204/comments/17 ** Bug watch added: code.google.com/p/chromium/issues #129930 http://code.google.com/p/chromium/issues/detail?id=129930 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is
[Touch-packages] [Bug 1832397] Re: dbus errors and running older version
Can you please provide the Ubuntu version In a terminal lsb_release -a perhaps even better uname -a attach the appropriate logs? /var/log/syslog or possibly /var/log/messages your dbus conf, everything in /etc/dbus-1/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1832397 Title: dbus errors and running older version Status in dbus package in Ubuntu: Incomplete Bug description: Hello, I am running this older version : Traitement des actions différées (« triggers ») pour dbus (1.12.2-1ubuntu1) ... I have errors as following : Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Thank you in advance to help me debugg dbus then update It, Regards. Dorian ROSSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1832397/+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 1832397] Re: dbus errors and running older version
Where exactly are you seeing that message? Does it work after rebooting? ** Changed in: dbus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1832397 Title: dbus errors and running older version Status in dbus package in Ubuntu: Incomplete Bug description: Hello, I am running this older version : Traitement des actions différées (« triggers ») pour dbus (1.12.2-1ubuntu1) ... I have errors as following : Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Thank you in advance to help me debugg dbus then update It, Regards. Dorian ROSSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1832397/+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 1832417] Re: wrong soundfont path
** Changed in: fluidsynth (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1832417
Title:
wrong soundfont path
Status in fluidsynth package in Ubuntu:
Confirmed
Status in fluidsynth package in Debian:
Confirmed
Bug description:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.
This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1832417/+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 1828215] Re: openssl ca -spkac output regressed
** Patch added: "disco.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270241/+files/disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Cosmic: Confirmed Status in openssl source package in Disco: Confirmed Status in openssl source package in Eoan: Fix Committed Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] * OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf -passin stdin -batch -spkac input_file -startdate 190121130654Z Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+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 1828215] Re: openssl ca -spkac output regressed
** Patch added: "cosmic.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270242/+files/cosmic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Cosmic: Confirmed Status in openssl source package in Disco: Confirmed Status in openssl source package in Eoan: Fix Committed Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] * OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf -passin stdin -batch -spkac input_file -startdate 190121130654Z Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+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 1828215] Re: openssl ca -spkac output regressed
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270243/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Cosmic: Confirmed Status in openssl source package in Disco: Confirmed Status in openssl source package in Eoan: Fix Committed Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] * OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf -passin stdin -batch -spkac input_file -startdate 190121130654Z Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+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 1832417] Re: wrong soundfont path
This bug is a duplicate of Debian #929182. Since this package is
inherited unpatched from Debian, please comment on the bug at this link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929182
** Bug watch added: Debian Bug tracker #929182
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929182
** Also affects: fluidsynth (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929182
Importance: Unknown
Status: Unknown
** Changed in: fluidsynth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1832417
Title:
wrong soundfont path
Status in fluidsynth package in Ubuntu:
Confirmed
Status in fluidsynth package in Debian:
Unknown
Bug description:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.
This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1832417/+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 1800003] Re: evince crashes in FcConfigParseAndLoad
This bug https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71
suggests that substantial improvements have been made to the fontconfig
package against null pointer dereferences after version 2.13.0-5.
https://cgit.freedesktop.org/fontconfig/commit/?id=efac784b0108d3140d7ec51cf22cb8a4453bd566
https://cgit.freedesktop.org/fontconfig/commit/?id=b1762935c3db2bc611750c61ce9cb38b9008db6b
https://cgit.freedesktop.org/fontconfig/commit/?id=b047e299546ac3abb79cf0bac3c67f5c2dfc7fb6
https://cgit.freedesktop.org/fontconfig/commit/?id=f3981a8bcd97a0388bf150ea7c1b4a1015e5e358
Can fontconfig be updated?
** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/issues #71
https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Confirmed
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+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 1832419] [NEW] Xorg freeze
Public bug reported: Freezes when connected to wifi. Running lsof -i and closing some of the processes results in black display, need to restart computer. i can use the computer for very short periods when connected to the internet, frequently the display freezes requiring restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Tue Jun 11 18:39:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: GOOGLE Banon ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-51-generic SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1832419 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Freezes when connected to wifi. Running lsof -i and closing some of the processes results in black display, need to restart computer. i can use the computer for very short periods when connected to the internet, frequently the display freezes requiring restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Tue Jun 11 18:39:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: GOOGLE Banon ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-51-generic SourcePackage: xorg
[Touch-packages] [Bug 1832417] [NEW] wrong soundfont path
Public bug reported:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.
This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.
** Affects: fluidsynth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1832417
Title:
wrong soundfont path
Status in fluidsynth package in Ubuntu:
New
Bug description:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.
This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1832417/+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 1800003] Re: evince crashes in FcConfigParseAndLoad
Please re-open. I have the same bug.
$ /usr/bin/evince
(evince:2751): Gtk-WARNING **: 00:31:32.744: Attempting to read the recently
used resources file at '/home/user/.local/share/recently-used.xbel', but the
parser failed: Failed to open file
“/home/user/.local/share/recently-used.xbel”: Permission denied.
Segmentation fault (core dumped)
$ { echo run; echo thread apply all bt full; quit; } | gdb /usr/bin/evince
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
I can also reproduce the crash with the minimal test program provided in
the bug report (nice catch!). I am on Ubuntu 18.04.2.
** Changed in: fontconfig (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Confirmed
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+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 1825331] Re: apparmor chromium profile blocks yubikeys
I can reproduce this issue with an AppArmor profile in complain mode for both Firefox 67 and Chromium 74 on ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1825331 Title: apparmor chromium profile blocks yubikeys Status in apparmor package in Ubuntu: New Bug description: Hi, some months ago (can't give a precise date) I could use all my pure u2f tokens, as well as Yubikey tokens with mixed apps (yubikey 4, yubikey neo) pretty well with chromium browser as u2f tokens. For some months now and since an update of the chromium-browser in 18.04, it was working with pure u2f tokens (e.g. the blue yubikeys, FIDO u2f token,...), but not with regular yubikeys anymore, although command line tools like u2f-host worked pretty well. I checked the kernel messages and did not find any apparmor deny message or other reasons. Furthermore, the apparmor profile for usr.bin.chromium-browser was in complain mode only. Now I did again some debugging and found that the problem is gone after aa-disable usr.bin.chromium-browser Although the profile was in complain mode and dmesg did not show any forbidden actions, the strace showed some EPERM (Operation not permitted) errors, that's why I tried to disable aa. Interestingly, this problem does not affect regular u2f tokens, just the yubikeys with additional functions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apparmor-profiles 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Apr 18 11:14:22 2019 InstallationDate: Installed on 2018-04-30 (352 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=5dca854b-2558-44a1-918d-c8380934754d ro nosplash SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+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 1832414] [NEW] Removing document files spam from cups
Public bug reported: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: New Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+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 1832407] [NEW] ubuntu-desktop should not hard depend on gnome-shell-extension-*
Public bug reported: I like the Ubuntu themed GNOME desktop but I don't like dash-to-dock. As the preinstalled extensions, especially gnome-shell-extension-ubuntu-dock are not deactivable and not removable atomic (they are hard dependcies of gnome-desktop), the only way to remove them is to rename the extensions folder. This will also restore the dock with every update of the gnome-shell-extension-ubuntu-dock package, as it creates this folder. Therfore, we should remove the hard dependcies. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1832407 Title: ubuntu-desktop should not hard depend on gnome-shell-extension-* Status in ubuntu-meta package in Ubuntu: New Bug description: I like the Ubuntu themed GNOME desktop but I don't like dash-to-dock. As the preinstalled extensions, especially gnome-shell-extension-ubuntu-dock are not deactivable and not removable atomic (they are hard dependcies of gnome-desktop), the only way to remove them is to rename the extensions folder. This will also restore the dock with every update of the gnome-shell-extension-ubuntu-dock package, as it creates this folder. Therfore, we should remove the hard dependcies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1832407/+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 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd
I am cleaning up zookeeper bugs and I believe that this will not be fixed given the release it was reported on. Xenial and newer versions do not appear to be affected by this bug. As such I am marking this incomplete for zookeeper and allowing someone to provide reproduction steps if it still is an issue. Thanks! ** Changed in: zookeeper (Ubuntu) Status: Triaged => Incomplete -- 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/1007433 Title: circular dependency causes zookeeperd to not be running after installation of zookeeperd Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in zookeeper package in Ubuntu: Incomplete Bug description: In a fresh quantal cloud image (i used ubuntu-quantal-daily- amd64-server-20120531), 'apt-get install zookeeperd' does not result in a running zookeeperd. to reproduce: * launch fresh instance * sudo apt-get install --assume-yes zookeeperd * status zookeeper Note, if you have previously installed zookeeper (not zookeeperd) then things will be fine. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: zookeeperd 3.3.5+dfsg1-2 ProcVersionSignature: User Name 3.4.0-3.8-generic 3.4.0 Uname: Linux 3.4.0-3-generic x86_64 ApportVersion: 2.1.1-0ubuntu1 Architecture: amd64 Date: Fri Jun 1 13:44:36 2012 Ec2AMI: ami-00ed Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zookeeper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1007433/+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 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor
** Changed in: evolution-data-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1828124 Title: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Install Evolution 3. Set-up Google account with default settings (this will end with e-mail and calendar) 4. Reboot 5. Open evolution Calendar and/or indicator-datetime 6. Launch `dbus-monitor` Expected results: * Evolution does not show account credentials in plain text in `dbus-monitor` output Actual results: * Evolution shows account credentials in plain text in `dbus-monitor` output: method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate array [ string "password:myrealpassword" string "ssl-trust:" ] method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 serial=366 reply_serial=939 signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" ] signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] - This is huge security flaw. The malicious script can parse `dbus-monitor` output... Not sure about more recent Ubuntu and Evolution versions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution-data-server-common 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 01:40:27 2019 InstallationDate: Installed on 2018-01-04 (488 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+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 1818527] Re: Stub resolver cache is corrupted
** Description changed: [Impact] systemd-resolved fails to resolve A records [Description] When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240. Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd $ git describe --contains 3740146a4cbd v240~839 $ rmadison systemd --arch amd64 systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.21 | xenial-security | source, ... systemd | 229-4ubuntu21.21 | xenial-updates | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.19 | bionic-security | source, ... systemd | 237-3ubuntu10.21 | bionic-updates | source, ... systemd | 237-3ubuntu10.22 | bionic-proposed | source, ... systemd | 239-7ubuntu10| cosmic | source, ... systemd | 239-7ubuntu10.12 | cosmic-security | source, ... systemd | 239-7ubuntu10.13 | cosmic-updates | source, ... systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ... systemd | 240-6ubuntu5 | disco | source, ... systemd | 240-6ubuntu5.1 | disco-proposed | source, ... systemd | 240-6ubuntu9 | eoan| source, ... Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution. [Test Case] Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail: #1 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME + + ;; QUESTION SECTION: + ;github.com. IN CNAME + + ;; Query time: 47 msec + . + $ dig github.com A + + ;; QUESTION SECTION: + ;github.com. IN A + + ;; Query time: 0 msec + + + While in reality, if no non-existent CNAME result query has been made + first: + + $ systemd-resolve --flush-caches + $ dig github.com | grep "IN" | grep "A" + + ; QUESTION SECTION: + ;github.com. IN A + + ;; ANSWER SECTION: + github.com. 59 IN A 192.30.253.112 + + ;; Query time: 51 msec + #2 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A Build a lxd container with Cosmic/Disco/Eoan (systemd-240): $ lxc launch ubuntu:cosmic cosmiclxd $ lxd exec cosmiclxd bash $ dig github.com A + + ;; QUESTION SECTION: + ;github.com. IN A + + ;; Query time: 0 msec + Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver). So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug. [Regression Potential] The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests. [Original Description] It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail. systemd version the issue has been seen with Installed: 237-3ubuntu10.13 Used distribution Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Expected behaviour you didn't see Return A record for a domain when it exists. Unexpected behaviour you saw Resolution failed. Steps to reproduce the problem Whait for 1 minutes (github.com TTL for A record) Try to resolv github.com CNAME record dig CNAME github.com This will return an empty result. Then try to resolve github.com A record dig A github.com. This will now return empty result unless you restart systemd-resolved or wait for cache expiration. At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8. Exemple : Wait for 1 minutes to let cache expire, then run dig CNAME github.com dig A github.com # no result dig A github.com @8.8.8.8 # ;; ANSWER SECTION: # github.com. 59 IN A 192.30.253.113 # github.com. 59 IN A 192.30.253.112 PS: Don't forget to restart systemd-resolve, before trying to post an answer. This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. ** Description changed: [Impact] systemd-resolved fails to resolve A records [Description] When systemd-resolve caches a
[Touch-packages] [Bug 1818527] Re: Stub resolver cache is corrupted
Sponsored in Bionic. * The fix LGTM. - Looking in systemd git upstream repo, I couldn't find anything (revert, known regression introduced by this particular fix or else) - I easily reproduced the bug using systemd without the fix, and I confirm it works for both enumerated scenarios found in [Test Case] just fine[0] with the fix. - This has been extensively tested in both upstream and other Debian/Ubuntu releases. * Very minor modifications: - Slightly modified the DEP3 header (Adding the upstream bug link, ) - Renamed the patch from "lp1818527-resolved-do-not-hit-CNAME-in-NODATA.patch" to "resolved-do-not-hit-CNAME-in-NODATA.patch" to stay consistent with current other "resolved" patch type. Thanks Heitor for your contribution. - Eric [0] - Validation of the fix in Bionic: # systemd-resolve --flush-caches # dig github.com -t CNAME ; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> github.com -t CNAME ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8781 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;github.com.IN CNAME ;; Query time: 22 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Tue Jun 11 15:43:51 EDT 2019 ;; MSG SIZE rcvd: 39 # dig github.com ; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> github.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2811 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;github.com.IN A ;; ANSWER SECTION: github.com. 42 IN A 192.30.253.113 ;; Query time: 13 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Tue Jun 11 15:43:55 EDT 2019 ;; MSG SIZE rcvd: 55 -- 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/1818527 Title: Stub resolver cache is corrupted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Bug description: [Impact] systemd-resolved fails to resolve A records [Description] When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240. Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd $ git describe --contains 3740146a4cbd v240~839 $ rmadison systemd --arch amd64 systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.21 | xenial-security | source, ... systemd | 229-4ubuntu21.21 | xenial-updates | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.19 | bionic-security | source, ... systemd | 237-3ubuntu10.21 | bionic-updates | source, ... systemd | 237-3ubuntu10.22 | bionic-proposed | source, ... systemd | 239-7ubuntu10| cosmic | source, ... systemd | 239-7ubuntu10.12 | cosmic-security | source, ... systemd | 239-7ubuntu10.13 | cosmic-updates | source, ... systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ... systemd | 240-6ubuntu5 | disco | source, ... systemd | 240-6ubuntu5.1 | disco-proposed | source, ... systemd | 240-6ubuntu9 | eoan| source, ... Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution. [Test Case] Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail: #1 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A #2 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A Build a lxd container with Cosmic/Disco/Eoan (systemd-240): $ lxc launch ubuntu:cosmic cosmiclxd $ lxd exec cosmiclxd bash $ dig github.com A Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver). So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug. [Regression Potential] The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests. [Original Description] It seems that when systemd-resolve cache
[Touch-packages] [Bug 1818527] Re: Stub resolver cache is corrupted
** Tags removed: ddstreet-next sts-sponsor-ddstreet -- 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/1818527 Title: Stub resolver cache is corrupted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Bug description: [Impact] systemd-resolved fails to resolve A records [Description] When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240. Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd $ git describe --contains 3740146a4cbd v240~839 $ rmadison systemd --arch amd64 systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.21 | xenial-security | source, ... systemd | 229-4ubuntu21.21 | xenial-updates | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.19 | bionic-security | source, ... systemd | 237-3ubuntu10.21 | bionic-updates | source, ... systemd | 237-3ubuntu10.22 | bionic-proposed | source, ... systemd | 239-7ubuntu10| cosmic | source, ... systemd | 239-7ubuntu10.12 | cosmic-security | source, ... systemd | 239-7ubuntu10.13 | cosmic-updates | source, ... systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ... systemd | 240-6ubuntu5 | disco | source, ... systemd | 240-6ubuntu5.1 | disco-proposed | source, ... systemd | 240-6ubuntu9 | eoan| source, ... Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution. [Test Case] Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail: #1 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A #2 On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A Build a lxd container with Cosmic/Disco/Eoan (systemd-240): $ lxc launch ubuntu:cosmic cosmiclxd $ lxd exec cosmiclxd bash $ dig github.com A Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver). So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug. [Regression Potential] The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests. [Original Description] It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail. systemd version the issue has been seen with Installed: 237-3ubuntu10.13 Used distribution Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Expected behaviour you didn't see Return A record for a domain when it exists. Unexpected behaviour you saw Resolution failed. Steps to reproduce the problem Whait for 1 minutes (github.com TTL for A record) Try to resolv github.com CNAME record dig CNAME github.com This will return an empty result. Then try to resolve github.com A record dig A github.com. This will now return empty result unless you restart systemd-resolved or wait for cache expiration. At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8. Exemple : Wait for 1 minutes to let cache expire, then run dig CNAME github.com dig A github.com # no result dig A github.com @8.8.8.8 # ;; ANSWER SECTION: # github.com. 59 IN A 192.30.253.113 # github.com. 59 IN A 192.30.253.112 PS: Don't forget to restart systemd-resolve, before trying to post an answer. This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527/+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 1832397] [NEW] dbus errors and running older version
Public bug reported: Hello, I am running this older version : Traitement des actions différées (« triggers ») pour dbus (1.12.2-1ubuntu1) ... I have errors as following : Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Thank you in advance to help me debugg dbus then update It, Regards. Dorian ROSSE. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Package changed: clamav (Ubuntu) => dbus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1832397 Title: dbus errors and running older version Status in dbus package in Ubuntu: New Bug description: Hello, I am running this older version : Traitement des actions différées (« triggers ») pour dbus (1.12.2-1ubuntu1) ... I have errors as following : Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Thank you in advance to help me debugg dbus then update It, Regards. Dorian ROSSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1832397/+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 1832397] [NEW] dbus errors and running older version
You have been subscribed to a public bug: Hello, I am running this older version : Traitement des actions différées (« triggers ») pour dbus (1.12.2-1ubuntu1) ... I have errors as following : Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Thank you in advance to help me debugg dbus then update It, Regards. Dorian ROSSE. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- dbus errors and running older version https://bugs.launchpad.net/bugs/1832397 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus 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 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Fixes have been pushed to cosmic-proposed and bionic-proposed. ** Summary changed: - Apply Bash 4.4.20 to fix cpu spinning on built-in wait + [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: In Progress Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1832333] Re: There is no firejail-default profile in Ubuntu
** Summary changed: - There is no firejail-default profile + There is no firejail-default profile in Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1832333 Title: There is no firejail-default profile in Ubuntu Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in firejail package in Ubuntu: New Bug description: Firejail requires the firejail-default apparmor profile in /etc/apparmor.d to work together with apparmor but that doesn't exist in Ubuntu 19.04. After I had added firejail-default to /etc/apparmor.d and firejail-local to /etc/apparmor.d/local everything was OK. Could this be default in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1832333/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Hey, Im not quite sure how I can reopen it, if you could tell me I would do it for you. For me this issue had fixed randomly before I upgraded to 19.04 and was not pressent since then. -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+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 1818527] Re: Stub resolver cache is corrupted
** Description changed: [Impact] systemd-resolved fails to resolve A records [Description] When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240. Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd $ git describe --contains 3740146a4cbd v240~839 $ rmadison systemd --arch amd64 - systemd | 229-4ubuntu4 | xenial | source, ... - systemd | 229-4ubuntu21.21 | xenial-security | source, ... - systemd | 229-4ubuntu21.21 | xenial-updates | source, ... - systemd | 237-3ubuntu10| bionic | source, ... - systemd | 237-3ubuntu10.19 | bionic-security | source, ... - systemd | 237-3ubuntu10.21 | bionic-updates | source, ... - systemd | 237-3ubuntu10.22 | bionic-proposed | source, ... - systemd | 239-7ubuntu10| cosmic | source, ... - systemd | 239-7ubuntu10.12 | cosmic-security | source, ... - systemd | 239-7ubuntu10.13 | cosmic-updates | source, ... - systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ... - systemd | 240-6ubuntu5 | disco | source, ... - systemd | 240-6ubuntu5.1 | disco-proposed | source, ... - systemd | 240-6ubuntu9 | eoan| source, ... + systemd | 229-4ubuntu4 | xenial | source, ... + systemd | 229-4ubuntu21.21 | xenial-security | source, ... + systemd | 229-4ubuntu21.21 | xenial-updates | source, ... + systemd | 237-3ubuntu10| bionic | source, ... + systemd | 237-3ubuntu10.19 | bionic-security | source, ... + systemd | 237-3ubuntu10.21 | bionic-updates | source, ... + systemd | 237-3ubuntu10.22 | bionic-proposed | source, ... + systemd | 239-7ubuntu10| cosmic | source, ... + systemd | 239-7ubuntu10.12 | cosmic-security | source, ... + systemd | 239-7ubuntu10.13 | cosmic-updates | source, ... + systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ... + systemd | 240-6ubuntu5 | disco | source, ... + systemd | 240-6ubuntu5.1 | disco-proposed | source, ... + systemd | 240-6ubuntu9 | eoan| source, ... Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution. [Test Case] Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail: + #1 + On a Bionic host: $ systemd-resolve --flush-caches $ dig github.com CNAME $ dig github.com A + + #2 + On a Bionic host: + $ systemd-resolve --flush-caches + $ dig github.com CNAME + $ dig github.com A + + Build a lxd with Cosmic/Disoo/Eoan and late (systemd-240): + $ lxc launch ubuntu:cosmic cosmiclxd + $ lxd exec cosmiclxd bash + $ dig github.com A + + Despite the fact that Cosmic and late has the proper fix, + Cosmic/Disco/Eoan container can suffer from the bug too if the host is + Bionic (container uses the host as a DNS resolver). + + So you may face the problem inside Cosmic/Disco/Eoan inside a container, + but it's still the same Bionic systemd bug. [Regression Potential] The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests. [Original Description] It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail. systemd version the issue has been seen with Installed: 237-3ubuntu10.13 Used distribution Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Expected behaviour you didn't see Return A record for a domain when it exists. Unexpected behaviour you saw Resolution failed. Steps to reproduce the problem Whait for 1 minutes (github.com TTL for A record) Try to resolv github.com CNAME record dig CNAME github.com This will return an empty result. Then try to resolve github.com A record dig A github.com. This will now return empty result unless you restart systemd-resolved or wait for cache expiration. At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8. Exemple : Wait for 1 minutes to let cache expire, then run dig CNAME github.com dig A github.com # no result dig A github.com @8.8.8.8 # ;; ANSWER SECTION: # github.com. 59 IN A 192.30.253.113 # github.com. 59 IN A 192.30.253.112 PS: Don't forget to restart systemd-resolve, before trying to post an answer. This bug was first reported in github https://github.com/systemd/systemd/issues/11789
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
@Thadeu, here is a new bug report that tracks this issue: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832388 We dont have a system in house with NVme, we will need IBM to verify -proposed with cosmic and report back here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
Hi, Manoj. There is nothing wrong in what you are doing here. This seems to be an unrelated bug. I am looking at any known problems on cpuidle for power9. Can you, please, open a different bug report, and try a different system for regression testing? From the log message, it doesn't seem there is anything related to initramfs changes, but a real kernel bug, also, apparently, unrelated to kdump. Thanks. Cascardo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink
[Touch-packages] [Bug 1831988] Re: msgfmt produces invalid UTF-8 sequences for desktop files
I can reproduce the error in a xenial VM, not in a bionic one. ** Changed in: gettext (Ubuntu) Status: New => Fix Released ** Also affects: gettext (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gettext (Ubuntu Xenial) Status: New => Confirmed ** Changed in: gettext (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1831988 Title: msgfmt produces invalid UTF-8 sequences for desktop files Status in gettext package in Ubuntu: Fix Released Status in gettext source package in Xenial: Confirmed Bug description: VIM has recently added support for validating gnome desktop files and this is reporting errors due to invalid UTF-8 sequences produced by msgfmt. Steps to reproduce: 1. Checkout rev 1253704 from the VIM git repo on GitHub - https://github.com/vim/vim 2. Run ./configure in the repo to set up the build environment. 2. Change to the po directory in the repo - cd src/po 3. Process and validate the gvim desktop file using the Makefile - $ make gvim.desktop msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop rm -f LINGUAS if command -v desktop-file-validate; then desktop-file-validate tmp_gvim.desktop; fi /usr/bin/desktop-file-validate tmp_gvim.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work. [Invalid UTF-8] tmp_gvim.desktop: error: value "\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa0\xe0\xad\x8d\xe0\xac\xaf \xe0\xac\xab\xe0\xac\xbe\xe0\xac\x87\xe0\xac\xb2\xe0\xac\x97\xe0\xad\x81\xe0\xac\xa1\xe0\xac\xbc\xe0\xac\xbf\xe0\xac\x95\xe0\xad\x81 \xe0\xac\xb8\xe0\xac\xae\xe0\xad\x8d\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa6\xe0\xac\xa8 \xe0\xac\x95\xe0\xac\xb0\xe0\xac\xa8\xe0\xad\x8d\xe0\xac\xa4\xe0\xad" for locale string key "Comment[or]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8 Makefile:176: recipe for target 'gvim.desktop' failed make: *** [gvim.desktop] Error 1 The template file has valid UTF-8 sequences so no errors are expected. The error is correct as the generated desktop file has a truncated 3 byte UTF-8 sequence at the end of the line as reported. The problem is msgfmt is emitting an invalid UTF-8 sequence for this one line. This is happening on an up to date 16.04 LTS - $ apt list gettext desktop-file-utils Listing... Done desktop-file-utils/xenial-updates,now 0.22-1ubuntu5.2 i386 [installed] gettext/xenial-updates,xenial-security,now 0.19.7-2ubuntu3.1 i386 [installed] There has been some discussion of this issue on the VIM developers mailing list - https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/i1PNO_46AgAJ A candidate patch for the issue from upstream for the gettext package has been identified - https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/6yAEzO9LAgAJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gettext 0.19.7-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: Unity Date: Fri Jun 7 10:30:31 2019 InstallationDate: Installed on 2019-02-05 (121 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731) SourcePackage: gettext UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1831988/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
This bug was fixed in the package dbus - 1.10.6-1ubuntu3.4 --- dbus (1.10.6-1ubuntu3.4) xenial-security; urgency=medium * SECURITY UPDATE: DBUS_COOKIE_SHA1 implementation flaw - d/p/0001-auth-Reject-DBUS_COOKIE_SHA1-for-users-other-than-th.patch: reject DBUS_COOKIE_SHA1 for users other than the server owner in dbus/dbus-auth.c. - d/p/0002-test-Add-basic-test-coverage-for-DBUS_COOKIE_SHA1.patch: add basic test coverage for DBUS_COOKIE_SHA1 in dbus/dbus-auth-script.c, dbus/dbus-sysdeps-util-unix.c, dbus/dbus-sysdeps-util-win.c, dbus/dbus-sysdeps.h, test/Makefile.am, test/data/auth/cookie-sha1-username.auth-script, test/data/auth/cookie-sha1.auth-script. - CVE-2019-12749 -- Marc Deslauriers Mon, 10 Jun 2019 14:06:01 -0400 ** Changed in: dbus (Ubuntu Xenial) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12749 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Confirmed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in unity-gtk-module source package in Xenial: Fix Committed Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds
** Changed in: initramfs-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832108 Title: unmkinitramfs fails with lz4 compressed initrds Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: In Progress Status in initramfs-tools package in Debian: New Bug description: [Impact] * Cannot unpack initrds compressed with lz4 due to changes in lz4 [Test Case] $ sudo apt install initramfs-tools lz4 file $ mkinitramfs -c lz4 -o foo.img $ lsinitramfs foo.img cpio: premature end of archive [Regression Potential] * New lz4cat is more strict w.r.t. enforcing file name extensions, thus the fix is to feed a stream to lz4cat instead of asking it to open a file. The performance impact should be similar between both methods of reading file contents during ls/unmk-initramfs time. [Other Info] Original bug report: unmkinitramfs fails with lz4 compressed initrds Note: $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832370] Re: Unable to configure or disable TLS 1.3 via openssl.cnf
In my tests, I used NGINX with those TLS related params:
# grep -r ssl_ /etc/nginx/nginx.conf /etc/nginx/conf.d/
/etc/nginx/sites-enabled/
/etc/nginx/nginx.conf: ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3,
ref: POODLE
/etc/nginx/nginx.conf: ssl_prefer_server_ciphers on;
/etc/nginx/conf.d/ssl.conf:ssl_ciphers
TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384;
/etc/nginx/conf.d/ssl.conf:ssl_session_cache shared:SSL:1m;
/etc/nginx/conf.d/ssl.conf:ssl_session_timeout 1d;
/etc/nginx/conf.d/ssl.conf:ssl_session_tickets off;
/etc/nginx/conf.d/ssl.conf:ssl_certificate
/etc/nginx/certs/sdeziel.info/fullchain.pem;
/etc/nginx/conf.d/ssl.conf:ssl_certificate_key
/etc/nginx/certs/sdeziel.info/privkey.pem;
/etc/nginx/conf.d/ssl.conf:ssl_stapling on;
I used many variations of ssl_ciphers and ssl_protocols to no avail. My main
goal is to have TLS 1.3 and 1.2 enabled with this ciphers list from above but
that doesn't work as seen here:
https://dev.ssllabs.com/ssltest/analyze.html?d=sdeziel.info=2001%3a470%3ab1c3%3a7942%3a0%3a0%3a0%3a80=on
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832370
Title:
Unable to configure or disable TLS 1.3 via openssl.cnf
Status in openssl package in Ubuntu:
New
Bug description:
[Description]
Since OpenSSL 1.1.1 was backported to Bionic, some (all?) applications
gained access to TLS 1.3 by default. The applications that were not
rebuilt against OpenSSL 1.1.1 can't tune the TLS 1.3 settings
(protocol, ciphersuites selection, ciphersuites order) like it's
possible with 1.2 and below. As such, one should turn to configuring
/etc/ssl/openssl.cnf to alter TLS 1.3 settings.
Here is how I'd expect to be able to turn off TLS 1.3:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:15:23.805113804 -0400
@@ -12,6 +12,16 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+MaxProtocol = TLSv1.2
+
# Extra OBJECT IDENTIFIER info:
#oid_file= $ENV::HOME/.oid
oid_section = new_oids
This doesn't work as 'openssl s_client -connect
rproxy.sdeziel.info:443' negotiates TLS 1.3 with
TLS_AES_256_GCM_SHA384.
Similarly, trying to change the 'Ciphers' or the 'Ciphersuites' list with:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:37:23.362889367 -0400
@@ -12,6 +12,17 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+Ciphers = TLS_AES_128_GCM_SHA256
+Ciphersuites = TLS_AES_128_GCM_SHA256
+
# Extra OBJECT IDENTIFIER info:
#oid_file= $ENV::HOME/.oid
oid_section = new_oids
Doesn't work as s_client keeps negotiating TLS 1.3 with
TLS_AES_256_GCM_SHA384 (!= 128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssl 1.1.1-1ubuntu2.1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 11:22:47 2019
InstallationDate: Installed on 2018-07-15 (331 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
ProcEnviron:
LANG=en_CA.UTF-8
TERM=xterm-256color
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832370/+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 1832370] Re: Unable to configure or disable TLS 1.3 via openssl.cnf
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832370
Title:
Unable to configure or disable TLS 1.3 via openssl.cnf
Status in openssl package in Ubuntu:
New
Bug description:
[Description]
Since OpenSSL 1.1.1 was backported to Bionic, some (all?) applications
gained access to TLS 1.3 by default. The applications that were not
rebuilt against OpenSSL 1.1.1 can't tune the TLS 1.3 settings
(protocol, ciphersuites selection, ciphersuites order) like it's
possible with 1.2 and below. As such, one should turn to configuring
/etc/ssl/openssl.cnf to alter TLS 1.3 settings.
Here is how I'd expect to be able to turn off TLS 1.3:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:15:23.805113804 -0400
@@ -12,6 +12,16 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+MaxProtocol = TLSv1.2
+
# Extra OBJECT IDENTIFIER info:
#oid_file= $ENV::HOME/.oid
oid_section = new_oids
This doesn't work as 'openssl s_client -connect
rproxy.sdeziel.info:443' negotiates TLS 1.3 with
TLS_AES_256_GCM_SHA384.
Similarly, trying to change the 'Ciphers' or the 'Ciphersuites' list with:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:37:23.362889367 -0400
@@ -12,6 +12,17 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+Ciphers = TLS_AES_128_GCM_SHA256
+Ciphersuites = TLS_AES_128_GCM_SHA256
+
# Extra OBJECT IDENTIFIER info:
#oid_file= $ENV::HOME/.oid
oid_section = new_oids
Doesn't work as s_client keeps negotiating TLS 1.3 with
TLS_AES_256_GCM_SHA384 (!= 128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssl 1.1.1-1ubuntu2.1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 11:22:47 2019
InstallationDate: Installed on 2018-07-15 (331 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
ProcEnviron:
LANG=en_CA.UTF-8
TERM=xterm-256color
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832370/+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 1832370] [NEW] Unable to configure or disable TLS 1.3 via openssl.cnf
Public bug reported:
[Description]
Since OpenSSL 1.1.1 was backported to Bionic, some (all?) applications
gained access to TLS 1.3 by default. The applications that were not
rebuilt against OpenSSL 1.1.1 can't tune the TLS 1.3 settings (protocol,
ciphersuites selection, ciphersuites order) like it's possible with 1.2
and below. As such, one should turn to configuring /etc/ssl/openssl.cnf
to alter TLS 1.3 settings.
Here is how I'd expect to be able to turn off TLS 1.3:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf2019-06-11 11:15:23.805113804 -0400
@@ -12,6 +12,16 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+MaxProtocol = TLSv1.2
+
# Extra OBJECT IDENTIFIER info:
#oid_file = $ENV::HOME/.oid
oid_section= new_oids
This doesn't work as 'openssl s_client -connect rproxy.sdeziel.info:443'
negotiates TLS 1.3 with TLS_AES_256_GCM_SHA384.
Similarly, trying to change the 'Ciphers' or the 'Ciphersuites' list with:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf2019-06-11 11:37:23.362889367 -0400
@@ -12,6 +12,17 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+Ciphers = TLS_AES_128_GCM_SHA256
+Ciphersuites = TLS_AES_128_GCM_SHA256
+
# Extra OBJECT IDENTIFIER info:
#oid_file = $ENV::HOME/.oid
oid_section= new_oids
Doesn't work as s_client keeps negotiating TLS 1.3 with
TLS_AES_256_GCM_SHA384 (!= 128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssl 1.1.1-1ubuntu2.1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 11:22:47 2019
InstallationDate: Installed on 2018-07-15 (331 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
ProcEnviron:
LANG=en_CA.UTF-8
TERM=xterm-256color
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic rls-ee-incoming
** Attachment added: "openssl.cnf trying to disable TLS 1.3"
https://bugs.launchpad.net/bugs/1832370/+attachment/5270156/+files/openssl.cnf
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832370/+attachment/5270158/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832370
Title:
Unable to configure or disable TLS 1.3 via openssl.cnf
Status in openssl package in Ubuntu:
New
Bug description:
[Description]
Since OpenSSL 1.1.1 was backported to Bionic, some (all?) applications
gained access to TLS 1.3 by default. The applications that were not
rebuilt against OpenSSL 1.1.1 can't tune the TLS 1.3 settings
(protocol, ciphersuites selection, ciphersuites order) like it's
possible with 1.2 and below. As such, one should turn to configuring
/etc/ssl/openssl.cnf to alter TLS 1.3 settings.
Here is how I'd expect to be able to turn off TLS 1.3:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:15:23.805113804 -0400
@@ -12,6 +12,16 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+MaxProtocol = TLSv1.2
+
# Extra OBJECT IDENTIFIER info:
#oid_file= $ENV::HOME/.oid
oid_section = new_oids
This doesn't work as 'openssl s_client -connect
rproxy.sdeziel.info:443' negotiates TLS 1.3 with
TLS_AES_256_GCM_SHA384.
Similarly, trying to change the 'Ciphers' or the 'Ciphersuites' list with:
# diff -Naur /etc/ssl/openssl.cnf{.orig,}
--- /etc/ssl/openssl.cnf.orig 2019-06-11 10:33:02.330143086 -0400
+++ /etc/ssl/openssl.cnf 2019-06-11 11:37:23.362889367 -0400
@@ -12,6 +12,17 @@
HOME = .
RANDFILE = $ENV::HOME/.rnd
+ssl_conf = ssl_sect
+
+[ssl_sect]
+
+system_default = system_default_sect
+
+[system_default_sect]
+
+Ciphers = TLS_AES_128_GCM_SHA256
+Ciphersuites = TLS_AES_128_GCM_SHA256
+
# Extra OBJECT IDENTIFIER info:
[Touch-packages] [Bug 1832108] Re: unmkinitramfs fails with lz4 compressed initrds
** Bug watch added: Debian Bug tracker #930366 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930366 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930366 Importance: Unknown Status: Unknown ** Description changed: + [Impact] + + * Cannot unpack initrds compressed with lz4 due to changes in lz4 + + [Test Case] + + $ sudo apt install initramfs-tools lz4 file + $ mkinitramfs -c lz4 -o foo.img + $ lsinitramfs foo.img + cpio: premature end of archive + + [Regression Potential] + + * New lz4cat is more strict w.r.t. enforcing file name extensions, thus + the fix is to feed a stream to lz4cat instead of asking it to open a + file. The performance impact should be similar between both methods of + reading file contents during ls/unmk-initramfs time. + + [Other Info] + + Original bug report: + unmkinitramfs fails with lz4 compressed initrds Note: - $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 - - - And - - $ lsinitramfs /boot/initrd.img - kernel - kernel/x86 - kernel/x86/microcode - kernel/x86/microcode/.enuineIntel.align.0123456789abc - kernel/x86/microcode/GenuineIntel.bin - cpio: premature end of archive ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: initramfs-tools (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832108 Title: unmkinitramfs fails with lz4 compressed initrds Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: In Progress Status in initramfs-tools package in Debian: Unknown Bug description: [Impact] * Cannot unpack initrds compressed with lz4 due to changes in lz4 [Test Case] $ sudo apt install initramfs-tools lz4 file $ mkinitramfs -c lz4 -o foo.img $ lsinitramfs foo.img cpio: premature end of archive [Regression Potential] * New lz4cat is more strict w.r.t. enforcing file name extensions, thus the fix is to feed a stream to lz4cat instead of asking it to open a file. The performance impact should be similar between both methods of reading file contents during ls/unmk-initramfs time. [Other Info] Original bug report: unmkinitramfs fails with lz4 compressed initrds Note: $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832369] [NEW] AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER
Public bug reported: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago) dmi.bios.date: 01/02/2018 dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: THN14B dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Thomson modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- 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/1832369 Title: AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER Status in pulseaudio package in Ubuntu: New Bug description: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu
[Touch-packages] [Bug 1661745] Re: ssh-keyscan does not exit with non-zero return code on error
Upstream commit in 8.0: commit c2c18a39683db382a15b438632afab3f551d50ce Author: d...@openbsd.org Date: Sat Jan 26 22:35:01 2019 + upstream: make ssh-keyscan return a non-zero exit status if it finds no keys. bz#2903 OpenBSD-Commit-ID: 89f1081fb81d950ebb48e6e73d21807b2723d488 https://github.com/openssh/openssh-portable/commit/c2c18a39683db382a15b438632afab3f551d50ce or https://anongit.mindrot.org/openssh.git/commit/?id=c2c18a39683db382a15b438632afab3f551d50ce ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1661745 Title: ssh-keyscan does not exit with non-zero return code on error Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Released Bug description: On xenial, ssh-keyscan returns zero indicating success, when the command fails. root@cp1:~# lsb_release -d Description: Ubuntu 16.04.1 LTS root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@cp1:~# echo $? 0 On trusty, the exit status is non-zero as expected. root@integration-deployer:/home/ubuntu# lsb_release -d Description: Ubuntu 14.04.5 LTS root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@integration-deployer:/home/ubuntu# echo $? 255 This is a incompatibility between Ubuntu 14.04 and 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1661745/+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 1661745] Re: ssh-keyscan does not exit with non-zero return code on error
Note that this has the potential of breaking existing scripts, so it's probably not a good SRU candidate. ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1661745 Title: ssh-keyscan does not exit with non-zero return code on error Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Released Bug description: On xenial, ssh-keyscan returns zero indicating success, when the command fails. root@cp1:~# lsb_release -d Description: Ubuntu 16.04.1 LTS root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@cp1:~# echo $? 0 On trusty, the exit status is non-zero as expected. root@integration-deployer:/home/ubuntu# lsb_release -d Description: Ubuntu 14.04.5 LTS root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@integration-deployer:/home/ubuntu# echo $? 255 This is a incompatibility between Ubuntu 14.04 and 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1661745/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds
This seems to be working on Bionic: root@bb-qemu:~# echo asd | lz4 > asd root@bb-qemu:~# file asd asd: LZ4 compressed data (v1.4+) root@bb-qemu:~# lz4cat -t asd root@bb-qemu:~# echo $? 0 ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Invalid ** Also affects: initramfs-tools (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832108 Title: unmkinitramfs fails with lz4 compressed initrds Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in initramfs-tools source package in Disco: Confirmed Status in initramfs-tools package in Debian: Unknown Bug description: [Impact] * Cannot unpack initrds compressed with lz4 due to changes in lz4 [Test Case] $ sudo apt install initramfs-tools lz4 file $ mkinitramfs -c lz4 -o foo.img $ lsinitramfs foo.img cpio: premature end of archive [Regression Potential] * New lz4cat is more strict w.r.t. enforcing file name extensions, thus the fix is to feed a stream to lz4cat instead of asking it to open a file. The performance impact should be similar between both methods of reading file contents during ls/unmk-initramfs time. [Other Info] Original bug report: unmkinitramfs fails with lz4 compressed initrds Note: $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1831021] Re: Extremely high memory consumption under heavy workload
** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload Status in cups package in Ubuntu: Triaged Bug description: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cupsd killed by OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+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 1832292] Re: reboot reboots system when -h is passed
Also, yes, I get that this is a nit-pick and that there's a history there, this is more a wishlist thing because it's a usability issue. ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- 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/1832292 Title: reboot reboots system when -h is passed Status in systemd package in Ubuntu: New Bug description: -h is a fairly common shortcut for --help. reboot, however, reboots the machine when one issues the command: reboot -h Now looking at the man page, there is an entry for --halt and --help, but NOTHING for -h at all. reboot should return the same as --help when -h is passed, or at the very least it should error out and not reboot the system, instead perhaps dumping a message like "-h unknown argument". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jun 11 00:50:22 2019 InstallationDate: Installed on 2016-02-11 (1215 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832292/+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 1832356] [NEW] Upgrade OpenSSH to 7.9p1-10 or better in stable series
Public bug reported: [Impact] * 18.04 LTS release with a long support time frame * There are two versions of OpenSSL shipped in 18.04: - obsolete 1.0.2 - current long term supported 1.1.1 series * OpenSSH in 18.04 is the only package in main using libcrypto from 1.0.2 * The fact that OpenSSH uses a different libcrypto implementation impacts certification, compliance, and security maintenance. * Furthermore OpenSSH does not benefit from hardware accelerated crypto, as available in 1.1.1 * Thus there is a desire to upgrade OpenSSH in 18.04 from 1:7.6p1-4 to 1:7.9p1-10 and compile against OpenSSL 1.1.1 * 1:7.9p1-10 is currently shipped in Disco/Eoan, and it is likely that 20.04 will ship with 1:8.0p1 or newer. Thus security maintainance burden is slightly increased. However, 1:7.9p1-10 is likely to be shipped in the next stable Debian release, and supported there for a long-ish time including debian-lts efforts. Thus there are some synergies. [Upstream Changelogs] * https://www.openssh.com/txt/release-7.9 * https://www.openssh.com/txt/release-7.8 * https://www.openssh.com/txt/release-7.7 [Test Case] * Install openssh-server and openssh-client, check that they depend on libssl1.1 and do not depend on libssl1.0 * Check that there are no new connectivity issues between old/new servers and clients, at the very least between various Ubuntu releases in the public clouds. [Regression Potential] v7.9 * ssh(1), sshd(8): the setting of the new CASignatureAlgorithms option (see below) bans the use of DSA keys as certificate authorities. DSA keys as certificate authorities are widely banned already. May affect connectivity. * sshd(8): the authentication success/failure log message has changed format slightly. It now includes the certificate fingerprint (previously it included only key ID and CA key fingerprint). This may impact log parsers, i.e. logwatch and similar. Possibly worth a NEWS entry. v7.8 * ssh-keygen(1): write OpenSSH format private keys by default instead of using OpenSSL's PEM format. The OpenSSH format, supported in OpenSSH releases since 2014 and described in the PROTOCOL.key file in the source distribution, offers substantially better protection against offline password guessing and supports key comments in private keys. If necessary, it is possible to write old PEM-style keys by adding "-m PEM" to ssh-keygen's arguments when generating or updating a key. Normally, it shouldn't matter which format newly generated keys use. Existing keys remain unchanged. Systems that automatically generate/parse/store keys may be impacted. The risk here is low. As potential mitigation we can revert the default back to PEM for the SRU into bionic. * sshd(8): remove internal support for S/Key multiple factor authentication. S/Key may still be used via PAM or BSD auth. S/Key is not widely deployed. Most common OTP implementations use PAM stack, and use HOTP, TOTP, Yubikey and similar one time passwords, rather than S/Key. This is deemed low. * ssh(1): remove vestigal support for running ssh(1) as setuid. This used to be required for hostbased authentication and the (long gone) rhosts-style authentication, but has not been necessary for a long time. Attempting to execute ssh as a setuid binary, or with uid != effective uid will now yield a fatal error at runtime. This is security and hardening improvement. We do not ship sshd setuid. * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is potentially a problem. We can add upgrade hooks to warn users about these, or abort the upgrade. This will require user configuration changes, if they set these settings (which might be done by config management systems). These are not widely used options. May affect connectivity. * sshd(8): the precedence of session environment variables has changed. ~/.ssh/environment and environment="..." options in authorized_keys files can no longer override SSH_* variables set implicitly by sshd. This is security and hardening improvement. Thus desirable to ship. Should not affect connectivity. * ssh(1)/sshd(8): the default IPQoS used by ssh/sshd has changed. They will now use DSCP AF21 for interactive traffic and CS1 for bulk. For a detailed rationale, please see the commit message:
[Touch-packages] [Bug 1832110] Re: Resource Sharing with multiple sshd services
> If I upload the sshd.c proposed change, will that be possibility? Please do attach the diff for reference - that is useful for the record. I think it will still be unlikely though. Introducing new configuration options in a distribution delta is particularly painful because if upstream later implement something differently, we'll be stuck supporting an obsolete upgrade path forever. I believe this has already happened to the openssh package in Ubuntu. Just because Ubuntu patches upstream sources for other reasons doesn't automatically qualify doing so again for a new reason. The argument for a new patch will need to be made on its own merits. I suggest that if you want to push this further, you start by identifying exactly what patch it is that upstream won't take, understand exactly why they won't take it, why existing upstream code isn't sufficient for your needs even though upstream believe it is, understand how that applies to Ubuntu's delta if the reasons are different, and present that all here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1832110 Title: Resource Sharing with multiple sshd services Status in openssh package in Ubuntu: Won't Fix Bug description: Ubuntu: 18.04.2 LTS OpenSSH: 7.6p1 I am having a problem starting multiple sshd processes. The default location of the sshd privilege separation directory is hard-coded to /run/sshd (see man page). If I want to have 2 sshd services using systemd, I need to write 2 service files, let's call them sshd_wan.service ans sshd_lan.service. Both of these services need to have their own "RuntimeDirectory=sshd_wan" and "RuntimeDirectory=sshd_lan". If you do not have separate RuntimeDirectory definitions for the 2 services, then when one service is killed/faults/restarts/stops/etc. the systemd (or init) process deletes the RuntimeDirectory and causes the other service to crash since a RuntimeDirectory does not exist. The problem is the hard-coding of the sshd Privilege Separation Directory. We need to modify the OpenBSD/OpenSSH sshd code to provision command line assignment of the privilege separation directory. I have attempted to contact the OpenSSH team (i.e. OpenSSH.com) and they say it is a Ubuntu problem. I reported this in Ubuntu bug #1831765 and Ubuntu (e.g. Paride Legovini, June 6, 2019 @ 2:55AM PDT) rejected it because I described the problem using the init.d example. I know how to modify the sshd.c file in OpenSSH 7.6p1, the problem is getting Ubuntu and OpenSSH to admit there is a problem and it needs to be fixed. The problem is still there regardless if you are using Upstart (i.e. init.d) or systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+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 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor
** Changed in: evolution-data-server Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1828124 Title: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Install Evolution 3. Set-up Google account with default settings (this will end with e-mail and calendar) 4. Reboot 5. Open evolution Calendar and/or indicator-datetime 6. Launch `dbus-monitor` Expected results: * Evolution does not show account credentials in plain text in `dbus-monitor` output Actual results: * Evolution shows account credentials in plain text in `dbus-monitor` output: method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate array [ string "password:myrealpassword" string "ssl-trust:" ] method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 serial=366 reply_serial=939 signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" ] signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] - This is huge security flaw. The malicious script can parse `dbus-monitor` output... Not sure about more recent Ubuntu and Evolution versions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution-data-server-common 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 01:40:27 2019 InstallationDate: Installed on 2018-01-04 (488 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+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 1829557] Re: package file 1:5.25-2ubuntu1 failed to install/upgrade: package file is not ready for configuration cannot configure (current status 'half-installed')
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1829557 Title: package file 1:5.25-2ubuntu1 failed to install/upgrade: package file is not ready for configuration cannot configure (current status 'half-installed') Status in file package in Ubuntu: New Bug description: my system got problem after entering Ctrl + Alt + F2 command Without exit with sudo init 0 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: file: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri May 17 20:52:21 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DpkgTerminalLog: dpkg: error processing package file (--configure): package file is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package file is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2019-05-17 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: file Title: package file 1:5.25-2ubuntu1 failed to install/upgrade: package file is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1829557/+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 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
This bug was fixed in the package sudo - 1.8.16-0ubuntu1.7 --- sudo (1.8.16-0ubuntu1.7) xenial-security; urgency=medium * debian/patches/terminate-with-commands-signal.patch: re-enable patch that got dropped by mistake in previous upload. (LP: #1832257) -- Marc Deslauriers Mon, 10 Jun 2019 15:42:44 -0400 ** Changed in: sudo (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Released Bug description: hey there- it looks like we accidentally removed the patch that fixed this problem when releasing sudo 1.8.16-0ubuntu1.6 - https://git.launchpad.net/ubuntu/+source/sudo/commit/?h=ubuntu/xenial- updates=15345b19b82f587498573b38554e24ec0ab816cb note that `terminate-with-commands-signal.patch` is removed from debian/patches/series in that commit and the behavior described in the original bug (LP 1686803) has returned in xenial. can we get this back into the current sudo package? the fix still exists upstream so it feels like this was an accidental reversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+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 1832337] [NEW] Require password when starting usb-creator
Public bug reported: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. ** Affects: policykit-desktop-privileges (Ubuntu) Importance: Undecided Assignee: Ubuntu Security Team (ubuntu-security) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: New Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+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 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2
The reported commented upstream 'Does not seem to occur with ubuntu 19.04 any longer.', closing the bug ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released ** Changed in: jackd2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1806860 Title: Pulseaudio module-jack-source unable to connect to jackd2 Status in jackd2 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604 --- When installing jackd2 in ubuntu 18.04, i am unable to load the module-jack-source. Syslog gives me: Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to server failed< Dec 5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: Failed to load module "module-jack-source" (argument: ""): initialization failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)< Dec 5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)<] Dec 5 11:49:51 nvidio So the path to the shared memory location is not as expected. When jackd2 is running i have: hcw@nvidion:$ cd /dev/shm/ hcw@nvidion:/dev/shm$ ls jack-1000-0 jack_sem.1000_default_1000_0_system jack_sem.1000_default_jack_rack jack_sem.1000_jack_default_1000_0_system jack-1000-1 jack_sem.1000_default_freewheel jack_sem.1000_default_qjackctl jack-shm-registry jack_default_1000_0 jack_sem.1000_default_jack_mixer jack_sem.1000_default_system So it seems module-jack-source / sink are guessing the wrong shared memory paths to the jackd2 server.. Versions: jackd2 1.9.12~dfsg-2 pulseaudio-module-jack 1:11.1-1ubuntu7.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago) UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video wireshark _MarkForUpload: True dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 042NDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7566 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952 mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1806860/+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 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'
** Tags added: id-5cfe7e5d8c5fcb19686df874 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1832120 Title: i386 - Test fails 'test_get_file_package_uninstalled_multiarch' Status in apport package in Ubuntu: Fix Released Bug description: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. The test 'test_get_file_package_uninstalled_multiarch' now appears to be failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+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 1832333] [NEW] There is no firejail-default profile
Public bug reported: Firejail requires the firejail-default apparmor profile in /etc/apparmor.d to work together with apparmor but that doesn't exist in Ubuntu 19.04. After I had added firejail-default to /etc/apparmor.d and firejail-local to /etc/apparmor.d/local everything was OK. Could this be default in Ubuntu? ** Affects: apparmor Importance: Undecided Status: New ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: firejail (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor Importance: Undecided Status: New ** Also affects: firejail (Ubuntu) Importance: Undecided Status: New ** Description changed: Firejail requires the firejail-default apparmor profile in /etc/apparmor.d to work together with apparmor but that doesn't exist in Ubuntu 19.04. After I had added firejail-default to /etc/apparmor.d and - firejail-local to /etc/apparmor.d/local everything were OK. + firejail-local to /etc/apparmor.d/local everything was OK. Could this be default in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1832333 Title: There is no firejail-default profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in firejail package in Ubuntu: New Bug description: Firejail requires the firejail-default apparmor profile in /etc/apparmor.d to work together with apparmor but that doesn't exist in Ubuntu 19.04. After I had added firejail-default to /etc/apparmor.d and firejail-local to /etc/apparmor.d/local everything was OK. Could this be default in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1832333/+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 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
@peter-shortbus OK, please follow the procedure in the SRU regression policy: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures#Regressions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Released Status in sudo source package in Yakkety: Won't Fix Status in sudo source package in Zesty: Fix Released Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
I can confirm that the same problem affects 19.04 too. -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Hey there, same problem here, audio has strange glitches, maybe we could reopen this issue? Both a collegue and I bought this same laptop and we are both affected by this issue, even on recent kernel builds. -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+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 1615389] Re: Searching for files and folders in AO takes much longer than previously
This bug is nearly 3 years old. Can you say if you think GNOME 3.32 in Ubuntu 19.04 performs adequately now? ** Changed in: ubuntu-gnome Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: tracker (Ubuntu) Status: New => Incomplete ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1615389 Title: Searching for files and folders in AO takes much longer than previously Status in Ubuntu GNOME: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in tracker package in Ubuntu: Incomplete Bug description: I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04 with GNOME 3.20 that searching for files and folders in the Activities Overview takes much much longer when previously (before upgrading) it would find them almost instantly as it currently does with applications. In the preferences for Tracker I have it set up so that it is meant to index content. What is interesting though is that for instance it might take 5 minutes to find my Artwork folder in my Documents directory through the AO. But if I run 'locate Artwork' in Terminal it finds it almost instantly. So that makes me think that perhaps it is an issue with it not properly indexing the content or not being able to retrieve the information or something and being forced to do a real-time search. But it is becoming rather annoying so I thought I would report it so that we can try to figure out what the issue is and hopefully find a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1615389/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
@vorlon has offered to sponsor this for eoan if/when he has time; once that's updated I will upload fixes to the documentation (e.g. man pages) for SRU releases. ** Changed in: sudo (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: sudo (Ubuntu Eoan) Assignee: Ubuntu Security Team (ubuntu-security) => Dan Streetman (ddstreet) ** Also affects: sudo (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu Disco) Status: New => In Progress ** Changed in: sudo (Ubuntu Cosmic) Status: New => In Progress ** Changed in: sudo (Ubuntu Bionic) Status: New => In Progress ** Changed in: sudo (Ubuntu Xenial) Status: New => In Progress ** Changed in: sudo (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sudo (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sudo (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sudo (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sudo (Ubuntu Disco) Importance: Undecided => Low ** Changed in: sudo (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: sudo (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: sudo (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: In Progress Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: In Progress Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. -- Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1830945] Re: DNS settings from interfaces file are ignored
I would still consider it a bug. AFAIK this is the correct way to bind an interface to multiple addresses. It is explictly mentioned in interfaces (5). My "workaround" of removing the second address only works because I no longer have a need for it at this time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1830945 Title: DNS settings from interfaces file are ignored Status in resolvconf package in Ubuntu: Invalid Bug description: Since a recent reboot (00:00 CEST on tuesday to be precise), DNS settings from the interfaces file are no longer present in resolvconf. A file /run/resolvconf/interface/eth0.inet exists but is empty. This is happening on a xenial system. I have since rebooted once more, with the same result. These are the contents of /etc/network/interfaces: iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.200.52 netmask 255.255.255.0 gateway 192.168.200.5 dns-nameserver 192.168.200.5 dns-nameserver 8.8.8.8 # second address iface eth0 inet static address 192.168.200.67 netmask 255.255.255.0 I'm running dnsmasq as a local DNS server on this system, which expects to get the "upstream" dns servers from resolvconf and thus can no longer resolve external addresses. Until this recent reboot, this configuration has worked without issue for many months, I have the etckeeper log to prove it :-). Here are some relevant excerpts from the logs: systemd[1]: Starting Clean up any mess left by 0dns-up... systemd[1]: Reached target Remote File Systems. systemd[1]: Started Clean up any mess left by 0dns-up. systemd[1]: Starting Nameserver information manager... systemd[1]: Started Nameserver information manager. systemd[1]: Reached target Sockets. systemd[1]: Reached target Basic System. systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... systemd[1]: Starting Raise network interfaces... systemd[1]: Started ifup for eth0. systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. ifup[624]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0 systemd[1]: Started Raise network interfaces. systemd[1]: Reached target Network. dnsmasq[583]: dnsmasq: syntax check OK. systemd[1]: Reached target Network is Online. ntpdate[840]: name server cannot be used: Temporary failure in name resolution (-3) dnsmasq[975]: started, version 2.75 cachesize 150 dnsmasq[975]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dnsmasq[975]: DNS service limited to local subnets dnsmasq-dhcp[975]: DHCP, IP range 192.168.200.100 -- 192.168.200.200, lease time 1h dnsmasq[975]: using local addresses only for domain myname.local dnsmasq[975]: no servers found in /var/run/dnsmasq/resolv.conf, will retry dnsmasq[975]: read /etc/hosts - 14 addresses ntpd[1060]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3) systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. systemd[1]: Reached target Host and Network Name Lookups. ntpd[1060]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1830945/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
> If automatic profile switching does not work then it is different problem, not problem "mic not available in A2DP Sink". Yes I think you are right the bug title is incorrect. But it annoys people if we close a bug on a technicality when they are still suffering. Maybe it needs rewording... > You would have to find real issue and provide all needed details when and how automatic profile switching does not work. And ideally send all needed information to pulseaudio mailing list... I can look at it, but without details there is no much which somebody can do. Great! Anyone experiencing this bug still, please tell us what Ubuntu version it is in and also contact the PulseAudio developers. Either by mailing list or by a bug report such as in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1798400]
[Automated Action] NeedInfo-To-Unconfirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1798400]
Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue. Launching impress reports: bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) in the system logs and then the remote app cannot contact the host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1798400]
Thank you for reporting the bug. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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
Re: [Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
On Tuesday 11 June 2019 08:11:07 Daniel van Vugt wrote: > The automatic switching (which is indeed documented in the release of > PulseAudio 10 [1]) doesn't seem to work for all users by the sound of > it. And people are probably justified in complaining if they find > Windows 10 or Android does a better job with the same headset. If automatic profile switching does not work then it is different problem, not problem "mic not available in A2DP Sink". > I am not one of those users but I see enough complaints to believe the > issue is still real. How real, I don't know... we only seem to be > getting complaints about Ubuntu 18.04 (PulseAudio 11.1). But that could > also be related to the general tendency of people to prefer the latest > LTS. You would have to find real issue and provide all needed details when and how automatic profile switching does not work. And ideally send all needed information to pulseaudio mailing list... I can look at it, but without details there is no much which somebody can do. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
Maybe related to the fact that Ubuntu 18.04 is the only "current" release that doesn't have the latest bluez 5.50 ...? But now I am guessing. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
I wish it was that simple. The automatic switching (which is indeed documented in the release of PulseAudio 10 [1]) doesn't seem to work for all users by the sound of it. And people are probably justified in complaining if they find Windows 10 or Android does a better job with the same headset. I am not one of those users but I see enough complaints to believe the issue is still real. How real, I don't know... we only seem to be getting complaints about Ubuntu 18.04 (PulseAudio 11.1). But that could also be related to the general tendency of people to prefer the latest LTS. [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/10.0/ -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1828171] Please test proposed package
Hello Łukasz, or anyone else affected, Accepted gcc-defaults-ports into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc- defaults-ports/1.178ubuntu1.18.10.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 and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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. -- 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/1828171 Title: New toolchain updates need to be rebuilt against -security only Status in binutils package in Ubuntu: New Status in eclipse-titan package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in ggcov package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in eclipse-titan source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Status in ggcov source package in Bionic: Fix Committed Status in binutils source package in Cosmic: Fix Committed Status in eclipse-titan source package in Cosmic: Fix Committed Status in gcc-7 source package in Cosmic: Fix Committed Status in gcc-7-cross source package in Cosmic: Fix Committed Status in gcc-7-cross-ports source package in Cosmic: Fix Committed Status in gcc-8 source package in Cosmic: Fix Committed Status in gcc-8-cross source package in Cosmic: Fix Committed Status in gcc-8-cross-ports source package in Cosmic: Fix Committed Status in gcc-defaults source package in Cosmic: Fix Committed Status in gcc-defaults-ports source package in Cosmic: Fix Committed Status in ggcov source package in Cosmic: Fix Committed Bug description: [Impact] With LP: #1814369, the toolchain packages have been updated in both cosmic and bionic, but due to an error those packages were built in -proposed as any regular SRU. For toolchain updates there exists a policy that those should be always built against -security *only*, and then released to both -security and -updates. Since this is not the case with the current toolchain update, we need to no-change rebuild all of the previously released toolchain packages in a -security enabled devirt PPA, sync them to -proposed with binaries and then release into the archives. [Regression Potential] As these are toolchain packages, there is always some regression potential. These will be no-change rebuilds so in theory the risk should be low, but the current versions of the packages have not been built against -security only before. It is hard to say how any regressions could manifest themselves. [Test Case] Making sure there are no reported regressions in the GCC and binutils test suites. Hopefully this will be sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+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 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad
Further to my previous note, trying to unlock the swap partition yields: # udisksctl unlock -b /dev/sda2 Object /org/freedesktop/UDisks2/block_devices/sda2 is not an encrypted device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad Status in linux package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: Incomplete Bug description: This bug report relates to a machine running 18.04, not the one I am submitting the report from. On 30 May The Software Updater prompted me to update. Included in the update were initramfs components. I now cannot boot the machine. After decrypting the root file system, instead of being prompted for the pass-phrase to decrypt the swap, I get the message "cannot connect to lvmetad: falling back to device scanning". This repeats for a while until I am dropped into a recovery shell of some sort from which I cannot access the root disk. Blocker. My machine is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.48.50 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2433 F pulseaudio raph 8920 F pulseaudio /dev/snd/controlC0: gdm2433 F pulseaudio Date: Fri May 31 12:08:33 2019 HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac InstallationDate: Installed on 2018-02-09 (475 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20CJS0UU00 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+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 1832297] Re: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x
Hmm interesting ... /usr/sbin/ebtables is managed by update alternatives. But iptables continues to surprise. In an sbuild build env of Eoan I get: # which ebtables iptables ip6tables /usr/sbin/ebtables /sbin/iptables /sbin/ip6tables While in an Eoan container I have: # which ebtables iptables ip6tables /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables Let me recycle the container as it might have some old crap. No it stays the same... Both are on 2.0.10.4+snapshot20181205-1ubuntu1 / 1.6.1-2ubuntu3. To make that three a Eoan VM as of today has the same as the container. All of them (sbuild+lxd+vm) have the non usr path in the package itself. dpkg -L iptables | grep 'bin\/iptables$' /sbin/iptables And the /usr/sbin path that exists in the container Hmm, something in the container and the VM brings that /usr/sbin mapping to work which fails in the build environment, maybe because it is "just" a chroot? /var/lib/dpkg/info/iptables.* has no further magic maintscripts that would explain. For now in libvirt lets set the real paths as carried by iptables packages. This will keep us on the safe side. But that also means we are back at my initial assumption that on an iptables 1.8.1 merge one might want to remove that (unless /sbin/iptables is kept as compat, then I can clear it next cycle). ** Changed in: libvirt (Ubuntu) Status: Invalid => Triaged ** Changed in: iptables (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1832297 Title: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x Status in Ubuntu Cloud Archive: New Status in iptables package in Ubuntu: New Status in libvirt package in Ubuntu: Triaged Bug description: Libvirt has now the paths for ip-/ip6-/eb-tables set in d/rules (by Debian) /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables But those paths are changing over time, most liikely due to usermerge activities. Bionic (as common backport target) iptables 1.6.1-2ubuntu2 => /sbin ebtables 2.0.10.4-3.5ubuntu2 => /sbin Eoan iptables 1.6.1-2ubuntu3 => /sbin ebtables 2.0.10.4+snapshot20181205-3 => /usr/sbin Debian iptables 1.8.2-4 => all in /usr/sbin ebtables (bin merged into the above) Due to that while merging libvirt I adapted to the current situation in Eoan for now. But this is only catched in build time tests and even there only listed as skip (binary not found) not as fail. Further at least the autopkgtests won't excercise this path, so once someone is merging the more recent iptables to Eoan this will somewhat silently break. For awareness I opened this bug against libvirt & iptables so that the one merging the latter is aware to drop [1] of the former for a rebuild. [1]: https://git.launchpad.net/~libvirt- maintainers/ubuntu/+source/libvirt/commit/?id=deccb0d6e761ec36a19083f3b4e52e64ac65a6f2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1832297/+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
Re: [Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
On Monday 10 June 2019 17:30:14 Thomas Andrews wrote: > Disappointing that 9 years on this is still an issue. My patches for automatic switching are part of pulseaudio 10. So this problem is fixed. > If I have A2DP Sink selected I have no Mic option This is expected behavior. Your headset in A2DP Sink mode does not support microphone. > and if I use HSP/HFP the audio quality sounds like it's being played down a 14.4K modem And this is expected too. In HSP/HFP mode is used CVSD codec which is sampled at 8 kHz. Same what is used in telephony system. > you might as well not have audio as it's just going to cause your ears to bleed. So what you wrote is expected and correct behavior. Your headset does not support anything else, it is by bluetooth design. === I think you can close this issue with title "ad2p sink profile mic not available". Really by bluetooth design A2DP sink profile does not support microphone and it is intended behavior. The fix which is in pulseaudio 10 is automatic switching between A2DP and HSP/HFP profiles based on fact if some phone application want to access microphone or not. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1830022] Re: DirtyCleanInterval should be 0 by default
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+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 1831021] Re: Extremely high memory consumption under heavy workload
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload Status in cups package in Ubuntu: Triaged Bug description: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cupsd killed by OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+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 1828171] Re: New toolchain updates need to be rebuilt against -security only
Ah, now I see that, thanks Dimitri! Actually I see Colin did mention 'binary versions', but I didn't really read that properly yesterday night. duh. Anyway, will look into that now. -- 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/1828171 Title: New toolchain updates need to be rebuilt against -security only Status in binutils package in Ubuntu: New Status in eclipse-titan package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in ggcov package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in eclipse-titan source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Status in ggcov source package in Bionic: Fix Committed Status in binutils source package in Cosmic: Fix Committed Status in eclipse-titan source package in Cosmic: Fix Committed Status in gcc-7 source package in Cosmic: Fix Committed Status in gcc-7-cross source package in Cosmic: Fix Committed Status in gcc-7-cross-ports source package in Cosmic: Fix Committed Status in gcc-8 source package in Cosmic: Fix Committed Status in gcc-8-cross source package in Cosmic: Fix Committed Status in gcc-8-cross-ports source package in Cosmic: Fix Committed Status in gcc-defaults source package in Cosmic: Fix Committed Status in gcc-defaults-ports source package in Cosmic: Fix Committed Status in ggcov source package in Cosmic: Fix Committed Bug description: [Impact] With LP: #1814369, the toolchain packages have been updated in both cosmic and bionic, but due to an error those packages were built in -proposed as any regular SRU. For toolchain updates there exists a policy that those should be always built against -security *only*, and then released to both -security and -updates. Since this is not the case with the current toolchain update, we need to no-change rebuild all of the previously released toolchain packages in a -security enabled devirt PPA, sync them to -proposed with binaries and then release into the archives. [Regression Potential] As these are toolchain packages, there is always some regression potential. These will be no-change rebuilds so in theory the risk should be low, but the current versions of the packages have not been built against -security only before. It is hard to say how any regressions could manifest themselves. [Test Case] Making sure there are no reported regressions in the GCC and binutils test suites. Hopefully this will be sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+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 1832304] [NEW] SSL socket segfaults during a connect() using a punycode domain containg a umlaut
Public bug reported: Hey, yesterday I stumbled across a segfault which is already fixed upstream. Can you please apply the patch for it? chs@gw-sss-nb8:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial chs@gw-sss-nb8:~$ python3 --version Python 3.5.2 Issue: https://bugs.python.org/issue37217 Fixed by: https://bugs.python.org/issue30594 Thanky you kmille ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1832304 Title: SSL socket segfaults during a connect() using a punycode domain containg a umlaut Status in python3-defaults package in Ubuntu: New Bug description: Hey, yesterday I stumbled across a segfault which is already fixed upstream. Can you please apply the patch for it? chs@gw-sss-nb8:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial chs@gw-sss-nb8:~$ python3 --version Python 3.5.2 Issue: https://bugs.python.org/issue37217 Fixed by: https://bugs.python.org/issue30594 Thanky you kmille To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1832304/+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 1832297] Re: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x
Hmm things seem to have raced in my build envs and containers. Fortunately Eoan is already completed # which ebtables iptables ip6tables /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables Ok then I can make libvirt to use these now, but this is still important to know for backports to Bionic. ** Changed in: libvirt (Ubuntu) Status: New => Invalid ** Changed in: iptables (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1832297 Title: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x Status in Ubuntu Cloud Archive: New Status in iptables package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Invalid Bug description: Libvirt has now the paths for ip-/ip6-/eb-tables set in d/rules (by Debian) /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables But those paths are changing over time, most liikely due to usermerge activities. Bionic (as common backport target) iptables 1.6.1-2ubuntu2 => /sbin ebtables 2.0.10.4-3.5ubuntu2 => /sbin Eoan iptables 1.6.1-2ubuntu3 => /sbin ebtables 2.0.10.4+snapshot20181205-3 => /usr/sbin Debian iptables 1.8.2-4 => all in /usr/sbin ebtables (bin merged into the above) Due to that while merging libvirt I adapted to the current situation in Eoan for now. But this is only catched in build time tests and even there only listed as skip (binary not found) not as fail. Further at least the autopkgtests won't excercise this path, so once someone is merging the more recent iptables to Eoan this will somewhat silently break. For awareness I opened this bug against libvirt & iptables so that the one merging the latter is aware to drop [1] of the former for a rebuild. [1]: https://git.launchpad.net/~libvirt- maintainers/ubuntu/+source/libvirt/commit/?id=deccb0d6e761ec36a19083f3b4e52e64ac65a6f2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1832297/+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 1832297] Re: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x
For further awareness I added a UCA task as back in Bionic the paths are again different. There also ebtables (which means all three binaries) are in /sbin/ That means on backports to Bionic this path needs to be adapted to match. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1832297 Title: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x Status in Ubuntu Cloud Archive: New Status in iptables package in Ubuntu: New Status in libvirt package in Ubuntu: New Bug description: Libvirt has now the paths for ip-/ip6-/eb-tables set in d/rules (by Debian) /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables But those paths are changing over time, most liikely due to usermerge activities. Bionic (as common backport target) iptables 1.6.1-2ubuntu2 => /sbin ebtables 2.0.10.4-3.5ubuntu2 => /sbin Eoan iptables 1.6.1-2ubuntu3 => /sbin ebtables 2.0.10.4+snapshot20181205-3 => /usr/sbin Debian iptables 1.8.2-4 => all in /usr/sbin ebtables (bin merged into the above) Due to that while merging libvirt I adapted to the current situation in Eoan for now. But this is only catched in build time tests and even there only listed as skip (binary not found) not as fail. Further at least the autopkgtests won't excercise this path, so once someone is merging the more recent iptables to Eoan this will somewhat silently break. For awareness I opened this bug against libvirt & iptables so that the one merging the latter is aware to drop [1] of the former for a rebuild. [1]: https://git.launchpad.net/~libvirt- maintainers/ubuntu/+source/libvirt/commit/?id=deccb0d6e761ec36a19083f3b4e52e64ac65a6f2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1832297/+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 1832297] [NEW] usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x
Public bug reported: Libvirt has now the paths for ip-/ip6-/eb-tables set in d/rules (by Debian) /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables But those paths are changing over time, most liikely due to usermerge activities. Bionic (as common backport target) iptables 1.6.1-2ubuntu2 => /sbin ebtables 2.0.10.4-3.5ubuntu2 => /sbin Eoan iptables 1.6.1-2ubuntu3 => /sbin ebtables 2.0.10.4+snapshot20181205-3 => /usr/sbin Debian iptables 1.8.2-4 => all in /usr/sbin ebtables (bin merged into the above) Due to that while merging libvirt I adapted to the current situation in Eoan for now. But this is only catched in build time tests and even there only listed as skip (binary not found) not as fail. Further at least the autopkgtests won't excercise this path, so once someone is merging the more recent iptables to Eoan this will somewhat silently break. For awareness I opened this bug against libvirt & iptables so that the one merging the latter is aware to drop [1] of the former for a rebuild. [1]: https://git.launchpad.net/~libvirt- maintainers/ubuntu/+source/libvirt/commit/?id=deccb0d6e761ec36a19083f3b4e52e64ac65a6f2 ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt-19.10 ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags added: libvirt-19.10 ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1832297 Title: usrmerge changes path of iptables - please update libvirt on a merge of 1.8.1-x Status in Ubuntu Cloud Archive: New Status in iptables package in Ubuntu: New Status in libvirt package in Ubuntu: New Bug description: Libvirt has now the paths for ip-/ip6-/eb-tables set in d/rules (by Debian) /usr/sbin/ebtables /usr/sbin/iptables /usr/sbin/ip6tables But those paths are changing over time, most liikely due to usermerge activities. Bionic (as common backport target) iptables 1.6.1-2ubuntu2 => /sbin ebtables 2.0.10.4-3.5ubuntu2 => /sbin Eoan iptables 1.6.1-2ubuntu3 => /sbin ebtables 2.0.10.4+snapshot20181205-3 => /usr/sbin Debian iptables 1.8.2-4 => all in /usr/sbin ebtables (bin merged into the above) Due to that while merging libvirt I adapted to the current situation in Eoan for now. But this is only catched in build time tests and even there only listed as skip (binary not found) not as fail. Further at least the autopkgtests won't excercise this path, so once someone is merging the more recent iptables to Eoan this will somewhat silently break. For awareness I opened this bug against libvirt & iptables so that the one merging the latter is aware to drop [1] of the former for a rebuild. [1]: https://git.launchpad.net/~libvirt- maintainers/ubuntu/+source/libvirt/commit/?id=deccb0d6e761ec36a19083f3b4e52e64ac65a6f2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1832297/+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
