[Touch-packages] [Bug 1813701] Re: the screen flickers. Ubuntu 18 + AMD RX580
** Summary changed: - the screen flickers + the screen flickers. Ubuntu 18 + AMD RX580 -- 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/1813701 Title: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, мерцание исчезнет, пока дисплей не выключится. После включения мерцание возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не видна. Подробнее в видео https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Пакет: xorg 1: 7.7 + 19ubuntu8 ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Архитектура : amd64 BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: Нет CurrentDesktop: ubuntu: GNOME Дата: Вт 29 января 13:13:19 2019 DistUpgraded: Свежая установка DistroCodename: космический Вариант: Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X / 580 / 580X] [1043: 0519] InstallationDate: Установлен в 2019-01-22 (6 дней назад). InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 (20181017.3) Тип машины : MSI MS-7693 ProcEnviron: TERM = xterm- 256color PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_RU.UTF-8 SHELL = / bin / bash ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash vt.handoff = 1 SourcePackage: xorg Симптом: отображение UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) dmi.bios.date: 08.08.2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios . версия: V10.6 dmi.board. asset.tag: Заполняется OEM dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis. asset.tag: Заполняется OEM dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis. версия: 3.0 dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: cvnMSI: ct3: cvr3. 0: dmi.product.family: заполняется OEM dmi.product.name: MS-7693 dmi.product.sku: заполняется OEM dmi.product. версия: 3.0 dmi.sys.vendor: MSI version.compiz: compiz Н / Д version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ oibaf ~ c версия. libgl1- mesa-glx: libgl1-mesa-glx N / A версия. xserver-xorg-core: xserver-xorg-core 2: версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- evdev N / A версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 18.1.0-1 . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + git20171229 -1ubuntu1 версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)
** Summary changed: - the screen flickers. Ubuntu 18 + AMD RX580 + [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10) ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1813701 Title: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, мерцание исчезнет, пока дисплей не выключится. После включения мерцание возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не видна. Подробнее в видео https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Пакет: xorg 1: 7.7 + 19ubuntu8 ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Архитектура : amd64 BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: Нет CurrentDesktop: ubuntu: GNOME Дата: Вт 29 января 13:13:19 2019 DistUpgraded: Свежая установка DistroCodename: космический Вариант: Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X / 580 / 580X] [1043: 0519] InstallationDate: Установлен в 2019-01-22 (6 дней назад). InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 (20181017.3) Тип машины : MSI MS-7693 ProcEnviron: TERM = xterm- 256color PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_RU.UTF-8 SHELL = / bin / bash ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash vt.handoff = 1 SourcePackage: xorg Симптом: отображение UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) dmi.bios.date: 08.08.2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios . версия: V10.6 dmi.board. asset.tag: Заполняется OEM dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis. asset.tag: Заполняется OEM dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis. версия: 3.0 dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: cvnMSI: ct3: cvr3. 0: dmi.product.family: заполняется OEM dmi.product.name: MS-7693 dmi.product.sku: заполняется OEM dmi.product. версия: 3.0 dmi.sys.vendor: MSI version.compiz: compiz Н / Д version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ oibaf ~ c версия. libgl1- mesa-glx: libgl1-mesa-glx N / A версия. xserver-xorg-core: xserver-xorg-core 2: версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- evdev N / A версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 18.1.0-1 . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + git20171229 -1ubuntu1 версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
First, sorry for my english, I was scary, but there is no problem. I have reboot the PC and after one upgarde has repaired the problem. Thanks Le 28/01/2019 à 19:46, Robie Basak a écrit : > Thank you for taking the time to report this bug and helping to make Ubuntu > better. > > Since it seems likely to me that this is a local configuration problem, > rather than a bug in Ubuntu, I'm marking this bug as Incomplete. > > If indeed this is a local configuration problem, you can find pointers > to get help for this sort of problem here: > http://www.ubuntu.com/support/community > > Or if you believe that this is really a bug, then you may find it > helpful to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem, > explain why you believe this is a bug in Ubuntu rather than a problem > specific to your system, and then change the bug status back to New. > > > ** Changed in: cyrus-sasl2 (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Incomplete Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+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 1813701] [NEW] the screen flickers
Public bug reported: the screen flickers always at a frequency of 75 GHz. At frequencies of 60 and 50 GHz, if you change to any other except 75, the flicker disappears until the display is turned off. After switching on, flicker returns. on kernel 4.18.0-10, the problem is not seen. more in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption cosmic third-party-packages ubuntu wayland-session ** Attachment added: "IMG_20190129_131458.jpg" https://bugs.launchpad.net/bugs/1813701/+attachment/5233377/+files/IMG_20190129_131458.jpg ** Description changed: - the screen flickers always at a frequency of 75 GHz. At frequencies of 60 and 60 GHz, if you change to any other, the flicker disappears until the display is turned off. After switching on, flicker returns. more in the video + the screen flickers always at a frequency of 75 GHz. At frequencies of 60 and 50 GHz, if you change to any other except 75, the flicker disappears until the display is turned off. After switching on, flicker returns. on kernel 4.18.0-10, the problem is not seen. more in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= +
[Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server
I just wanted to chime in here as I was having the exact same problem. Turned out to be because of some configuration changes I made to ntp.conf in an attempt to prevent ntpd from listening on any of my network interfaces (security paranoid): interface ignore wildcard interface listen 127.0.0.1 Apparently ntpd also uses these settings for outgoing connection attempts too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: New Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+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 1805635] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1805635 Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Expired Bug description: I wasn't doing anything. Bug was there when I returned to screen first thing in the morning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Nov 28 06:21:09 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-04-14 (227 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1805635/+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 1803316] Re: VPN connection is stopped
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1803316 Title: VPN connection is stopped Status in network-manager package in Ubuntu: Expired Bug description: From a few days I cannot connect via VPN, It worked from a few months *sudo apt policy network-manager* network-manager: Installed: 1.2.6-0ubuntu0.16.04.3 Candidate: 1.2.6-0ubuntu0.16.04.3 Versions: *** 1.2.6-0ubuntu0.16.04.3 500 500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages */var/sys/log* Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8520] audit: op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS VPN" pid=13561 uid=1000 result="success" Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8706] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Started the VPN service, PID 2396 Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8815] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw the service appear; activating connection Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.9989] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN connection: (ConnectInteractive) reply received Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405 Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0148] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: starting (3) Nov 14 10:46:08 hs pppd[2405]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0226] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47) Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0 Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0 Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0391] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0392] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated. Nov 14 10:46:39 hs pppd[2405]: Connection terminated. Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with PID 2405. Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0566] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: failed: connect-failed (1) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0577] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopping (5) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0579] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopped (6) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0680] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state change reason: unknown (0) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0802] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN service disappeared Nov 14 10:46:39 hs
[Touch-packages] [Bug 1805953] Re: perl is not installed correctly ubuntu-18.10-server-amd64.iso
[Expired for perl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: perl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1805953 Title: perl is not installed correctly ubuntu-18.10-server-amd64.iso Status in perl package in Ubuntu: Expired Bug description: perl is not installed correctly in ubuntu-18.10-server-amd64.iso. It can be fixed when reinstall perl with command "apt install perl" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1805953/+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 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
[Expired for kerneloops (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kerneloops (Ubuntu) Status: Incomplete => Expired -- 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/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: Expired Status in kerneloops package in Ubuntu: Expired Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+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 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: Expired Status in kerneloops package in Ubuntu: Expired Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+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 1308261] Re: ICE provoked by a lambda using the sizeof a captured stack-allocated array
Launchpad has imported 3 comments from the remote bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.
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 2014-04-15T21:33:20+00:00 Brady Garvin wrote:
Created attachment 32611
Preprocessed source
$ cat gcc-bug.cpp
int main() {
unsigned count = 5;
bool array[count];
[] () {
array[0] = sizeof(array) > 5;
}();
return 0;
}
$ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp
gcc-bug.cpp: In lambda function:
gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this function
[-Wuninitialized]
}();
^
gcc-bug.cpp:3:21: note: ‘’ was declared here
bool array[count];
^
gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at expr.c:9363
}();
^
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to
your bugreport.
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.8 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
$ # Closest I could find by searching is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56699.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1308261/comments/0
On 2014-04-15T22:53:28+00:00 Brady Garvin wrote:
Also ICEs in 4.9.0:
/usr/lib/gcc-snapshot/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/usr/lib/gcc-snapshot/bin/g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc-snapshot/libexec/gcc/x86_64-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
20130917-1ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-snapshot/README.Bugs
--enable-languages=c,ada,c++,java,go,fortran,objc,obj-c++
--prefix=/usr/lib/gcc-snapshot --enable-shared --enable-linker-build-id
--disable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-snap-amd64/jre
--enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-snap-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-snap-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic
--enable-checking=yes --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.0 20130917 (experimental) [trunk revision 202647] (Ubuntu
20130917-1ubuntu1)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1308261/comments/2
On 2014-04-16T08:24:07+00:00 Rguenth wrote:
Confirmed. We trap on
9446 /* Variables inherited from containing functions should have
9447 been lowered by this point. */
9448 context = decl_function_context (exp);
9449 gcc_assert (SCOPE_FILE_SCOPE_P (context)
9450 || context == current_function_decl
9451 || TREE_STATIC (exp)
9452 || DECL_EXTERNAL (exp)
9453 /* ??? C++ creates functions that are not
[Touch-packages] [Bug 1813376] Re: i dont know what that is
** Package changed: xorg (Ubuntu) => unity (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/1813376 Title: i dont know what that is Status in unity package in Ubuntu: Incomplete Bug description: Please help me since I am new to linux and My wifi also got question mark all the time after 15-20 mins ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 25 17:45:45 2019 DistUpgraded: 2018-08-24 14:16:14,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-133-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Seymour [Radeon HD 6400M/7400M Series] [106b:00e1] InstallationDate: Installed on 2015-02-26 (1429 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Apple Inc. MacBookPro8,2 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=754616c8-84b9-4619-95cf-b7420df47da7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-24 (154 days ago) dmi.bios.date: 10/20/16 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B2D.1610201938 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2D.1610201938:bd10/20/16:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Aug 23 23:14:20 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1813376/+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 1813020] Re: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all
You say "there is no voice in headphone". Does that mean only the microphone stopped working? Can you still hear sound in the headphones? ** Summary changed: - [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all + [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813020 Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone Status in alsa-driver package in Ubuntu: Incomplete Bug description: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813020/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1813075 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813433] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: amdgpu
** Summary changed:
- Xorg freeze
+ [amdgpu] Xorg freeze
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
--
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/1813433
Title:
[amdgpu] Xorg freeze
Status in xorg-server package in Ubuntu:
New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
New
Bug description:
Hello,
Thanks for looking forward to fix problems.
I re-installed ubuntu 18.04LTS & 18.10 4 times and every time it's just get
worse! So this time I did my best, And I didn't re-install ubuntu I just
changed gdm to lightdm < after looking for the problem > I notice that Ubuntu +
Ubuntu On WayLand is not working at all, So I logged into GNOME and It's
working perfectly.
--
Problems are:
1- Freezing for the whole system, Even music Freeze Ex. Before
Freezing:Lalala | After: l
2- Black Screen With A lot of [OK] { I guess that ubuntu-desktop couldn't
boot up }
--
That's it
Best Wishes,
Just4you.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Jan 27 02:11:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: I don't know
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920]
InstallationDate: Installed on 2019-01-24 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
Lsusb:
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:07dc Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite L50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=220449dc-de23-41d3-9305-079db3268b33 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 2.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSatelliteL50-B:pvrPSKTNV-02Y01DAR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: INVALID
dmi.product.name: Satellite L50-B
dmi.product.version: PSKTNV-02Y01DAR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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/xorg-server/+bug/1813433/+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 1813431] Re: Problem with gnome panel system menu
Also, if this is a Gnome Shell bug then there is still some information missing. Please run this command to send it: apport-collect 1813431 ** Summary changed: - Problem with start menu and menu bar + Problem with gnome panel system menu ** Package changed: xorg (Ubuntu) => gnome-shell (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/1813431 Title: Problem with gnome panel system menu Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I clicked on the start menu in the top right corner, that little window jumped out, and. when I wanted to lock my account, nothing happened, but when I clicked on that panel again, it was like... vibrating... It was moving up and down about 10px (If I remember well). When I left it be and came back later (I have automatic lock after 5 min) There was that menu on the left (I don't know the name :D) After I logged in, I noticed, that when I move my mouse on it, it becomes wider and icons go slightly further apart(When I'm on desktop). When I have Firefox window opened, same happens, but when I aim on Firefox icon, the icons go to normal distance, but bar is still wider. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 23:29:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:805d] InstallationDate: Installed on 2019-01-11 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:760a Microdia Bus 001 Device 002: ID 0458:0188 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProDesk 600 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4d46de66-f485-47e9-905c-9d172082c94d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.16 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC6448GH4 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.16:bd08/18/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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/gnome-shell/+bug/1813431/+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 1432302] Re: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while
Boomer, is the problem just with speakers (bug 1654857), or just with headphones (bug 1603696)? ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1432302 Title: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Boot to ubuntu. 2. Change volume up and down using Fn volume keys several times. 3. Sound start shuttering and only reboot helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: boomer 2115 F pulseaudio /dev/snd/controlC0: boomer 2115 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 15 12:24:42 2015 InstallationDate: Installed on 2015-02-12 (30 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN24WW(V1.06) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN24WW(V1.06):bd07/09/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1432302/+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 1603696] Re: [K501UX, Conexant CX20751/2, Black Headphone Out, Right] Not able to get sound out of my headphones
** Summary changed: - [K501UX, Conexant CX20751/2, Black Headphone Out, Right] No sound at all + [K501UX, Conexant CX20751/2, Black Headphone Out, Right] Not able to get sound out of my headphones ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1603696 Title: [K501UX, Conexant CX20751/2, Black Headphone Out, Right] Not able to get sound out of my headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: Not Able to get sound out of my headphones from ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1580 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 16 15:22:01 2016 InstallationDate: Installed on 2016-05-28 (49 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1580 F pulseaudio daniel30828 F alsamixer Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [K501UX, Conexant CX20751/2, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K501UX.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K501UX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501UX.209:bd01/20/2016:svnASUSTeKCOMPUTERINC.:pnK501UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K501UX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-16T14:24:41.418524 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1603696/+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 1654857] Re: [80SM, Conexant CX20751/2, Speaker, Internal] No sound from speakers, but headphones work
** Summary changed: - [80SM, Conexant CX20751/2, Speaker, Internal] No sound at all + [80SM, Conexant CX20751/2, Speaker, Internal] No sound from speakers, but headphones work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654857 Title: [80SM, Conexant CX20751/2, Speaker, Internal] No sound from speakers, but headphones work Status in alsa-driver package in Ubuntu: New Bug description: No sound at all, but on my headphones work correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dejan 2719 F...m pulseaudio /dev/snd/controlC0: dejan 2719 F pulseaudio CurrentDesktop: Unity Date: Sun Jan 8 15:36:09 2017 InstallationDate: Installed on 2016-12-23 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dejan 2719 F...m pulseaudio /dev/snd/controlC0: dejan 2719 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [80SM, Conexant CX20751/2, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 5A2 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN23WW:bd03/21/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK: dmi.product.name: 80SM dmi.product.version: Lenovo ideapad 310-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654857/+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 1813557] Re: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] I can play sound without headphone but when i connect headphone sound can not play at all.
*** This bug is a duplicate of bug 1603696 *** https://bugs.launchpad.net/bugs/1603696 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1603696, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all + [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] I can play sound without headphone but when i connect headphone sound can not play at all. ** This bug has been marked a duplicate of bug 1603696 [K501UX, Conexant CX20751/2, Black Headphone Out, Right] Not able to get sound out of my headphones -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813557 Title: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] I can play sound without headphone but when i connect headphone sound can not play at all. Status in alsa-driver package in Ubuntu: New Bug description: i can play sound without headphone but when i connect headphone sound can not play at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masoud 3192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 14:31:19 2019 InstallationDate: Installed on 2019-01-15 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2111 F pulseaudio masoud 3192 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X756UWK.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X756UWK 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.:bvrX756UWK.307:bd03/08/2017:svnASUSTeKCOMPUTERINC.:pnX756UWK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX756UWK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X756UWK 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/alsa-driver/+bug/1813557/+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 1812014] Re: keyboard not responding after suspend after some time
Please also run: dpkg -l > dpkgl.txt and send us the resulting file 'dpkgl.txt'. ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812014] Re: keyboard not responding after suspend after some time
Thanks, those photos are very helpful. One shows 'upower' using 100% CPU and another shows 'kworker/6:0-events' using 100%. I wonder if that second one is related to Nvidia (like bug 1808108)... Can you please run: dmesg > dmesg.txt and send us the resulting file 'dmesg.txt'? ** Also affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1813227] Re: lvm2-pvscan services fails to start on S390X DPM
** Attachment added: "lsblk output" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233345/+files/lsblk.log -- 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/1813227 Title: lvm2-pvscan services fails to start on S390X DPM Status in lvm2 package in Ubuntu: New Bug description: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Autoactivation reading from disk instead of lvmetad. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm4" now active zkvm4: autoactivation failed. Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm1" now active zkvm1: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed. Cannot activate LVs in VG
[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM
The MAAS ephemeral environment does not have the multipath kernel module nor multipath-tools. To get this log I had to install both. ** Attachment added: "multipath.log" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233346/+files/multipath.log -- 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/1813227 Title: lvm2-pvscan services fails to start on S390X DPM Status in lvm2 package in Ubuntu: New Bug description: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Autoactivation reading from disk instead of lvmetad. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm4" now active zkvm4: autoactivation failed. Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm1" now active zkvm1: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. 0 logical volume(s)
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1768261] Re: Videos are getting stuck randomly at frames
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => Confirmed ** Tags added: radeon ** Summary changed: - Videos are getting stuck randomly at frames + [radeon] Videos are getting stuck randomly at frames -- 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/1768261 Title: [radeon] Videos are getting stuck randomly at frames Status in compiz package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos, on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The video seek time also gets stuck at that frame, and then suddenly the video skips ahead. Audio has no issues. I am assuming it's a problem with the video drivers. I have dual graphics cards, one integrated and one dedicated(AMD Radeon HD 8670M). I guess my problem is similar to https://askubuntu.com/questions/1029205/video-playback-performance- issue-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 1 19:40:21 2018 DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea] InstallationDate: Installed on 2016-01-21 (830 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 04NGGW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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/compiz/+bug/1768261/+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 582585] Re: getaddrinfo() returns duplicate addresses under AI_ADDRCONFIG
Launchpad has imported 2 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=14969.
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-12-17T17:08:20+00:00 Psimerda wrote:
getaddrinfo() with AI_ADDRCONFIG replaces all ::1 with 127.0.0.1 on
hosts without non-loopback IPv6 addresses. See the following test
result:
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether f0:de:f1:b8:6a:ee brd ff:ff:ff:ff:ff:ff
inet 84.246.161.88/28 brd 84.246.161.95 scope global eth0
getaddrinfo host="None" hints.ai_flags=AI_ADDRCONFIG:
::1
127.0.0.1
getaddrinfo host="localhost" hints.ai_flags=AI_ADDRCONFIG:
127.0.0.1
127.0.0.1
getaddrinfo host="127.0.0.1" hints.ai_flags=AI_ADDRCONFIG:
127.0.0.1
getaddrinfo host="localhost4" hints.ai_flags=AI_ADDRCONFIG:
127.0.0.1
getaddrinfo host="::1" hints.ai_flags=AI_ADDRCONFIG:
::1
getaddrinfo host="localhost6" hints.ai_flags=AI_ADDRCONFIG:
127.0.0.1
getaddrinfo host="195.47.235.3" hints.ai_flags=AI_ADDRCONFIG:
195.47.235.3
getaddrinfo host="2a02:38::1001" hints.ai_flags=AI_ADDRCONFIG:
2a02:38::1001
getaddrinfo host="info.nix.cz" hints.ai_flags=AI_ADDRCONFIG:
195.47.235.3
getaddrinfo host="www.google.com" hints.ai_flags=AI_ADDRCONFIG:
173.194.39.81
173.194.39.82
173.194.39.80
173.194.39.84
173.194.39.83
Especially notable are:
getaddrinfo(localhost) -> 127.0.0.1, 127.0.0.1 (duplicate)
getaddrinfo(localhost6) -> 127.0.0.1 (wrong)
Contents of /etc/hosts:
127.0.0.1 localhost localhost4
::1 localhost localhost6
Looks like some sort of black magic someone was trying to solve
something.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/582585/comments/2
On 2012-12-17T17:09:23+00:00 Psimerda wrote:
Testing script:
#!/usr/bin/python3
import sys
from socket import *
hosts = [
None,
"localhost",
"127.0.0.1",
"localhost4",
"::1",
"localhost6",
"195.47.235.3",
"2a02:38::1001",
"info.nix.cz",
"www.google.com",
]
for host in hosts:
print("getaddrinfo host=\"{}\" hints.ai_flags=AI_ADDRCONFIG:".format(host))
try:
for item in getaddrinfo(host, "http", AF_UNSPEC, SOCK_STREAM, SOL_TCP,
AI_ADDRCONFIG):
print(" {}".format(item[4][0]))
except gaierror as error:
print(" !! {} !!".format(error))
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/582585/comments/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/582585
Title:
getaddrinfo() returns duplicate addresses under AI_ADDRCONFIG
Status in eglibc:
Confirmed
Status in eglibc package in Ubuntu:
Confirmed
Bug description:
Presume I have a computer that has no global IPv6 addresses, but a few
IPv4 addresses.
Applications using getaddrinfo() with hints.ai_flags = AI_ADDRCONFIG
set will properly omit IPv6 addresses, HOWEVER they will return
duplicate IPv4 addresses.
Demonstration code attached.
Without IPv6 addresses:
# show setup
$ grep -w localhost /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
$ ip a s | grep inet
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
inet 192.168.0.4/24 brd 192.168.0.255 scope global eth0
inet6 fe80::226:::/64 scope link # masked for privacy
# compile test case
$ gcc -Wall -Wextra -pedantic -O -o libcbug-demo libcbug-demo.c
# run test case
$ ./libcbug-demo localhost echo
Address 1: 127.0.0.1
Address 2: 127.0.0.1
(127.0.0.1 should be listed only once, Solaris 10 for instance
achieves that)
Now configure a fake IPv6 address (don't do this on hosts with real
IPv6 connectivity, it suffices to use your real IPv6 address) and re-
run the application:
$ ip a a 2001::2001 dev eth0 # set up IPv6
$ ./libcbug-demo localhost echo
Address 1: ::1
Address 2: 127.0.0.1
$ ip a d 2001::2001 dev eth0 # deconfigure bogus address
(This is fine)
Practical consequence: excessive connection retries by applications
that possibly take a long time.
This isn't Ubuntu specific.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libc6 2.11.1-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed
[Touch-packages] [Bug 1805077] Re: the audio pause and repeat for a very short of time randomly
** Changed in: pulseaudio (Ubuntu) Status: Expired => New -- 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/1805077 Title: the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: New Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805077/+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 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
root@improved-kodiak:~# systemctl restart systemd-resolved
Jan 29 00:11:52 improved-kodiak systemd[1]: Bus private-bus-connection:
changing state UNSET → OPENING
Jan 29 00:11:52 improved-kodiak systemd[1]: Bus private-bus-connection:
changing state OPENING → AUTHENTICATING
Jan 29 00:11:52 improved-kodiak systemd[1]: Accepted new private connection.
Jan 29 00:11:52 improved-kodiak systemd[1]: Bus private-bus-connection:
changing state AUTHENTICATING → RUNNING
Jan 29 00:11:52 improved-kodiak systemd[1]: Got message type=method_call
sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=RestartUnit cookie=1
reply_cookie=0 signature=ss error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service: Trying to
enqueue job systemd-resolved.service/restart/replace
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service: Installed
new job systemd-resolved.service/restart as 1358
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service: Enqueued
job systemd-resolved.service/restart as 1358
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dresolved_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dresolved_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=2
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal sender=n/a
destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dresolved_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=6343
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal sender=n/a
destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dresolved_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=6344
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=3
reply_cookie=0 signature=uos error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=signal sender=n/a
destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=6345
reply_cookie=0 signature=uos error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: Sent message type=method_return
sender=org.freedesktop.systemd1 destination=n/a path=n/a interface=n/a
member=n/a cookie=4 reply_cookie=1 signature=o error-name=n/a error-message=n/a
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service: Job 1358
systemd-resolved.service/restart finished, result=done
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service:
Converting job systemd-resolved.service/restart ->
systemd-resolved.service/start
Jan 29 00:11:52 improved-kodiak systemd[1]: systemd-resolved.service: Failed to
reset devices.allow/devices.deny: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service: Operation not permitted
Jan 29 00:11:52 improved-kodiak systemd[1]: Failed to set devices.allow on
/system.slice/systemd-resolved.service:
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
Hmmm, but it should be fine if one gets EPERM or like EACCES. Hmmm.. -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813622/+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 1813679] [NEW] vim-gtk can no longer save to GVFS STFP mounts in 18.04
Public bug reported: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (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 vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS STFP mounts in 18.04 Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1813679/+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 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
Jan 28 23:50:06 ottawa audit[10278]: AVC apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-improved-kodiak_" name="/run/systemd/unit-root/home/" pid=10278 comm="(networkd)" flags="ro, nosuid, nodev, remount, bind" Jan 28 23:50:06 ottawa kernel: audit: type=1400 audit(1548719406.237:332): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-improved-kodiak_" name="/run/systemd/unit-root/home/" pid=10278 comm="(networkd)" flags="ro, nosuid, nodev, remount, bind" Jan 28 23:50:06 ottawa audit[10310]: AVC apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-improved-kodiak_" name="/run/systemd/unit-root/home/" pid=10310 comm="(networkd)" flags="ro, nosuid, nodev, remount, bind" Jan 28 23:50:06 ottawa kernel: audit: type=1400 audit(1548719406.273:333): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-improved-kodiak_" name="/run/systemd/unit-root/home/" pid=10310 comm="(networkd)" flags="ro, nosuid, nodev, remount, bind" So systemd v240 tries to setup mount namespace to further contain execution, and it appears that this is no longer possible inside the lxd container, due to apparmor denies. I'm not sure if this is a bug/feature of systemd | snapd | lxd | apparmor, as all of these are involved. ** Summary changed: - systemd-resolved fails to start in a container + systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813622/+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 1442775] Re: apt-get --ignore-missing doesn't ignore missing packages
Yes this affects me as well. Still true as of apt 1.6.6 (Ubuntu 18.04) -- 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/1442775 Title: apt-get --ignore-missing doesn't ignore missing packages Status in apt package in Ubuntu: Confirmed Bug description: The man page for apt-get states: -m, --ignore-missing, --fix-missing Ignore missing packages; if packages cannot be retrieved or fail the integrity check after retrieval (corrupted package files), hold back those packages and handle the result. Use of this option together with -f may produce an error in some situations. If a package is selected for installation (particularly if it is mentioned on the command line) and it could not be downloaded then it will be silently held back. Configuration Item: APT::Get::Fix-Missing. However, when removing or purging packages, it does /not/ actually ignore missing packages: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo apt-get purge -y --ignore-missing zimbra-openssl-lib Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package zimbra-openssl-lib build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 100 This causes some pain when using apt-get in a Makefile and wanting to ensure custom packages have been removed. dpkg handles this correctly: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo dpkg --purge zimbra-openssl-lib dpkg: warning: ignoring request to remove zimbra-openssl-lib which isn't installed build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 0 however you then lose dependency tracking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1442775/+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 1442775] Re: apt-get --ignore-missing doesn't ignore missing packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1442775 Title: apt-get --ignore-missing doesn't ignore missing packages Status in apt package in Ubuntu: Confirmed Bug description: The man page for apt-get states: -m, --ignore-missing, --fix-missing Ignore missing packages; if packages cannot be retrieved or fail the integrity check after retrieval (corrupted package files), hold back those packages and handle the result. Use of this option together with -f may produce an error in some situations. If a package is selected for installation (particularly if it is mentioned on the command line) and it could not be downloaded then it will be silently held back. Configuration Item: APT::Get::Fix-Missing. However, when removing or purging packages, it does /not/ actually ignore missing packages: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo apt-get purge -y --ignore-missing zimbra-openssl-lib Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package zimbra-openssl-lib build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 100 This causes some pain when using apt-get in a Makefile and wanting to ensure custom packages have been removed. dpkg handles this correctly: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo dpkg --purge zimbra-openssl-lib dpkg: warning: ignoring request to remove zimbra-openssl-lib which isn't installed build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 0 however you then lose dependency tracking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1442775/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Btw I made an alias to update my laptop taking care of some of the annoying stuff regarding this issue. Modify to fit your needs (: alias distup='apt -y --fix-broken install && apt update && apt upgrade && apt -y autoremove && dpkg --ignore-depends libcurl3 -i ~/viber.deb' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1804887] Re: software-properties-qt should not run as root
** Branch linked: lp:~silhusk/software-properties/lp1804887-qt-dbus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1804887 Title: software-properties-qt should not run as root Status in software-properties package in Ubuntu: New Bug description: s-p-qt should not be run as root (with sudo or pkexec), instead it should use the DBus backend like s-p-gtk does. This way the UI runs as unprivileged user, and the user is asked for credentials when making changes. Motivation: * Running the UI with sudo is bad. * It doesn't work in Wayland. (https://bugs.kde.org/show_bug.cgi?id=391965) * The DBus backend already exists and is used by s-p-gtk. RFC: The attached patch changes s-p-qt to use the DBus service for the settings in the first tab (enable/disable components, change server). Any comment on how it works or should work? Known issues with the patch: * When a change fails to be applied the UI doesn't notice and is out of sync with system state. That's because the DBus service never returns a value (except for DBus error). Solution is to reload the config after every change attempt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1804887/+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 1644996] Re: logrotate config uses syslog group
** Tags added: rls-bb-notfixing rls-cc-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1644996] Re: logrotate config uses syslog group
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1813648] [NEW] error reports
Public bug reported: Failed to start Process error reports when automatic reporting is enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Jan 28 21:34:51 2019 InstallationDate: Installed on 2019-01-08 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Dell System Inspiron N4110 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05TM8C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System Inspiron N4110 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1813648 Title: error reports Status in systemd package in Ubuntu: New Bug description: Failed to start Process error reports when automatic reporting is enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Jan 28 21:34:51 2019 InstallationDate: Installed on 2019-01-08 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Dell System Inspiron N4110 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05TM8C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System Inspiron N4110 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813648/+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 1766542] Re: Installation blocks when the machine is behind a proxy server
I don't believe that any special fix is need for ubiquity given that the bug and fix were in apt, so I'm setting this task to Invalid. ** Changed in: ubiquity (Ubuntu Bionic) Status: New => Invalid ** Tags removed: rls-bb-incoming -- 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/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Fix Released Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Bug description: [Impact] APT takes a long time to notice when certain connections time out [Test case] * Change the default route to not route stuff successfully (wrong gateway, for example) * Make your sources.list look like this: deb http://archive.ubuntu.com/ubuntu bionic main restricted deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted * Run apt update You should see that it fails with a long verbose error message for the first entry, with all possible IP addresses listed in it; while for the second one it fails with just "Unable to connect to archive.ubuntu.com:http:" as it recognizes it has been blacklisted. [Regression potential] APT will not attempt to retry the host given that it could not connect to it for previous entries. If your network recovered in the meantime, it might update less than previously. [Original bug report] When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1773859] Re: upgrades to 18.04 fail
The upload of systemd that was purported to fix this bug report was superseded by a security update of systemd so the fix is no longer available. ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Triaged -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Triaged Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
** Tags removed: rls-bb-incoming -- 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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1813622] Re: systemd-resolved fails to start in a container
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1813622 Title: systemd-resolved fails to start in a container Status in systemd package in Ubuntu: Confirmed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/+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 1813622] Re: systemd-resolved fails to start in a container
Robie: Confirmed with a Bionic host as well using the same LXD snap and environment, and the same reproduction steps. (Marking as "Confirmed") -- 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/1813622 Title: systemd-resolved fails to start in a container Status in systemd package in Ubuntu: Confirmed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change
This bug was fixed in the package linux - 4.15.0-44.47
---
linux (4.15.0-44.47) bionic; urgency=medium
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make many functions static
- net: hns: make hns_dsaf_roce_reset non static
- net: hisilicon: hns: Replace mdelay() with msleep()
- net: hns3: fix return value error while hclge_cmd_csq_clean failed
- net: hns: remove redundant variables 'max_frm' and 'tmp_mac_key'
- net: hns: Mark expected switch fall-through
- net: hns3: Mark expected switch fall-through
- net: hns3: Remove tx ring BD len register in hns3_enet
- net: hns: modify variable type in hns_nic_reuse_page
- net: hns: use eth_get_headlen interface instead of hns_nic_get_headlen
- net: hns3: modify variable type in hns3_nic_reuse_page
- net: hns3: Fix for vf vlan delete failed problem
- net: hns3: Fix for multicast failure
- net: hns3: Fix error of checking used vlan id
- net: hns3: Implement shutdown ops in hns3 pci driver
- net: hns3: Fix for loopback selftest failed problem
- net: hns3: Fix ping exited problem when doing lp selftest
- net: hns3: Preserve vlan 0 in hardware table
- net: hns3: Only update mac configuation when necessary
- net: hns3: Change the dst mac addr of loopback packet
- net: hns3: Remove redundant codes of query
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This bug was fixed in the package linux - 4.15.0-44.47
---
linux (4.15.0-44.47) bionic; urgency=medium
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make many functions static
- net: hns: make hns_dsaf_roce_reset non static
- net: hisilicon: hns: Replace mdelay() with msleep()
- net: hns3: fix return value error while hclge_cmd_csq_clean failed
- net: hns: remove redundant variables 'max_frm' and 'tmp_mac_key'
- net: hns: Mark expected switch fall-through
- net: hns3: Mark expected switch fall-through
- net: hns3: Remove tx ring BD len register in hns3_enet
- net: hns: modify variable type in hns_nic_reuse_page
- net: hns: use eth_get_headlen interface instead of hns_nic_get_headlen
- net: hns3: modify variable type in hns3_nic_reuse_page
- net: hns3: Fix for vf vlan delete failed problem
- net: hns3: Fix for multicast failure
- net: hns3: Fix error of checking used vlan id
- net: hns3: Implement shutdown ops in hns3 pci driver
- net: hns3: Fix for loopback selftest failed problem
- net: hns3: Fix ping exited problem when doing lp selftest
- net: hns3: Preserve vlan 0 in hardware table
- net: hns3: Only update mac configuation when necessary
- net: hns3: Change the dst mac addr of loopback packet
- net: hns3: Remove redundant codes of query
[Touch-packages] [Bug 1813623] Re: Failed to start LightDM on disco
https://prnt.sc/mdcy64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1813623 Title: Failed to start LightDM on disco Status in lightdm package in Ubuntu: New Bug description: I installed Ubuntu 19.04 in VirtualBox using the net install ISO. I then installed a minimal XFCE4 desktop and LightDM using apt: sudo apt install xfce4 --no-install-recommends sudo apt install lightdm --no-install-recommends After rebooting, it hangs on the loading screen. I pressed CTRL + ALT + G and saw that systemd had tried to start LightDM several times but failed at every one. The boot process hangs on "A start job is running for Hold until boot process finishes up". The only way to solve this is by either reinstalling Ubuntu or chrooting into the installation from a live CD and removing the lightdm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1813623/+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 1813623] [NEW] Failed to start LightDM on disco
Public bug reported: I installed Ubuntu 19.04 in VirtualBox using the net install ISO. I then installed a minimal XFCE4 desktop and LightDM using apt: sudo apt install xfce4 --no-install-recommends sudo apt install lightdm --no-install-recommends After rebooting, it hangs on the loading screen. I pressed CTRL + ALT + G and saw that systemd had tried to start LightDM several times but failed at every one. The boot process hangs on "A start job is running for Hold until boot process finishes up". The only way to solve this is by either reinstalling Ubuntu or chrooting into the installation from a live CD and removing the lightdm package. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1813623 Title: Failed to start LightDM on disco Status in lightdm package in Ubuntu: New Bug description: I installed Ubuntu 19.04 in VirtualBox using the net install ISO. I then installed a minimal XFCE4 desktop and LightDM using apt: sudo apt install xfce4 --no-install-recommends sudo apt install lightdm --no-install-recommends After rebooting, it hangs on the loading screen. I pressed CTRL + ALT + G and saw that systemd had tried to start LightDM several times but failed at every one. The boot process hangs on "A start job is running for Hold until boot process finishes up". The only way to solve this is by either reinstalling Ubuntu or chrooting into the installation from a live CD and removing the lightdm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1813623/+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 1813622] Re: systemd-resolved fails to start in a container
If it matters, my host is running Disco, upgraded nightly but last rebooted 59 days ago. lxd is from the snap: installed: 3.9 (9919) 54MB - -- 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/1813622 Title: systemd-resolved fails to start in a container Status in systemd package in Ubuntu: New Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Tags removed: rls-bb-incoming rls-cc-incoming -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1813622] [NEW] systemd-resolved fails to start in a container
Public bug reported: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). ** Affects: systemd (Ubuntu) Importance: Critical Status: New ** Tags: block-proposed -- 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/1813622 Title: systemd-resolved fails to start in a container Status in systemd package in Ubuntu: New Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
** Also affects: gnupg (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnupg2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Status in apt-setup source package in Bionic: New Status in gnupg source package in Bionic: New Status in gnupg2 source package in Bionic: New Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1787460] Please test proposed package
Hello Dean, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.8 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop:
[Touch-packages] [Bug 1787460] Please test proposed package
Hello Dean, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.2 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop:
[Touch-packages] [Bug 1811120] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.8 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+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 1811120] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.2 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+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 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
>From log: Paramétrage de sasl2-bin (2.1.27+dfsg-1) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: erreur de traitement du paquet sasl2-bin (--configure) : installed sasl2-bin package post-installation script subprocess returned error exit status 1 Additionally it looks like /etc/default/saslauthd has a local modification. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Incomplete Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+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 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Incomplete Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+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 1813616] [NEW] man: can't open /usr/share/man/man8/init.8: No such file or directory
Public bug reported: I run Ubuntu 16.04.5 LTS and the value of `LANG` is `en_US.UTF-8`. After quitting the `man upstart` page I see the following message in terminal: ``` man: can't open /usr/share/man/man8/init.8: No such file or directory ``` And `locate init.8` confirms that there is no such file. The `apt-file find init.8` command shows that `init.8.gz` is present in `manpages-es-extra`, `manpages-hu` and similar packages for other languages (but not for English). This is the output of `gunzip -c /usr/share/man/man7/upstart.7.gz`: ``` .so man8/init.8 ``` (So, it looks like this is an incorrect redirection.) I believe, `upstart.7.gz` should be fixed. Information about release and package version: $ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 $ apt-cache policy upstart upstart: Installed: 1.13.2-0ubuntu21.1 Candidate: 1.13.2-0ubuntu21.1 Version table: *** 1.13.2-0ubuntu21.1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.13.2-0ubuntu21 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages This might be a related bug: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/252413 ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1813616 Title: man: can't open /usr/share/man/man8/init.8: No such file or directory Status in upstart package in Ubuntu: New Bug description: I run Ubuntu 16.04.5 LTS and the value of `LANG` is `en_US.UTF-8`. After quitting the `man upstart` page I see the following message in terminal: ``` man: can't open /usr/share/man/man8/init.8: No such file or directory ``` And `locate init.8` confirms that there is no such file. The `apt-file find init.8` command shows that `init.8.gz` is present in `manpages-es-extra`, `manpages-hu` and similar packages for other languages (but not for English). This is the output of `gunzip -c /usr/share/man/man7/upstart.7.gz`: ``` .so man8/init.8 ``` (So, it looks like this is an incorrect redirection.) I believe, `upstart.7.gz` should be fixed. Information about release and package version: $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy upstart upstart: Installed: 1.13.2-0ubuntu21.1 Candidate: 1.13.2-0ubuntu21.1 Version table: *** 1.13.2-0ubuntu21.1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.13.2-0ubuntu21 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages This might be a related bug: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/252413 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1813616/+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 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
** Tags added: server-triage-discuss -- 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/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+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 1813428] Re: "sorry, you are not running GNOME or KDE" while running GNOME
These guided questions come from apport-symptoms and apport presents them to the user, regardless this is likely an issue with apport- symptoms. ** Package changed: apport (Ubuntu) => apport-symptoms (Ubuntu) -- 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/1813428 Title: "sorry, you are not running GNOME or KDE" while running GNOME Status in apport-symptoms package in Ubuntu: New Bug description: 1) run ubuntu-bug with no arguments 2) "What kind of problem do you want to report?" choose "External or internal storage devices(e.g. USB sticks)" 3) OK 4) choose "Removable storage device is not mounted automatically" 5) when ubuntu-bug says "please remove it ..." physically remove USB thumb drive from computer. 6) when ubuntu-bug says "please plug it back in..." physically plug USB thumb back in computer. result: "sorry, you are not running GNOME or KDE automounting needs to be provided by your desktop environment" oddly enough if you leave it in, instead of unplugging, it proceeds to report the bug as usual usb thumb drive device: /dev/sdg Bus 001 Device 016: ID 10d6:1101 Actions Semiconductor Co., Ltd D-Wave 2GB MP4 Player / AK1025 MP3/MP4 Player gnome: 3.28.2 OS type: 64 bit ubuntu: bionic 18.04 apport: Installed: 2.20.9-0ubuntu7.5 Candidate: 2.20.9-0ubuntu7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport-symptoms/+bug/1813428/+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 1812348] Re: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927
I got the same issue. My hardware is MSI X470 Gaming Plus AMD Ryzen 5 2600 XFX RX580 GTS Black Edition Log: gernot@pcname:~$ journalctl -b -p err -- Logs begin at Sun 2018-10-07 04:01:03 CEST, end at Mon 2019-01-28 15:51:03 CET. -- Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800e Jän 28 14:25:00 pcname kernel: MODSIGN: Couldn't get UEFI db list Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800e Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800e Jän 28 14:25:00 pcname kernel: amdgpu :1d:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] Assuming drive cache: write through Jän 28 14:25:05 pcname spice-vdagent[1727]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:25:10 pcname colord-sane[1833]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Jän 28 14:27:09 pcname spice-vdagent[2694]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:33 pcname pulseaudio[2597]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote app Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1812348 Title: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927 Status in libdrm package in Ubuntu: Confirmed Bug description: Each time I boot my laptop (and time to time after), the log show this crash : [ 47.202056] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927 [ 47.202109] WARNING: CPU: 5 PID: 868 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:254 generic_reg_wait+0xe4/0x160 [amdgpu] [ 47.202110] Modules linked in: ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter snd_hrtimer bnep nfnetlink_log nfnetlink zram binfmt_misc nls_iso8859_1 arc4 dell_smm_hwmon cdc_ether usbnet joydev r8152 mii dell_rbtn intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_usb_audio snd_usbmidi_lib razerkbd(OE) aesni_intel aes_x86_64
[Touch-packages] [Bug 1812348] Re: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdrm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1812348 Title: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927 Status in libdrm package in Ubuntu: Confirmed Bug description: Each time I boot my laptop (and time to time after), the log show this crash : [ 47.202056] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927 [ 47.202109] WARNING: CPU: 5 PID: 868 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:254 generic_reg_wait+0xe4/0x160 [amdgpu] [ 47.202110] Modules linked in: ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter snd_hrtimer bnep nfnetlink_log nfnetlink zram binfmt_misc nls_iso8859_1 arc4 dell_smm_hwmon cdc_ether usbnet joydev r8152 mii dell_rbtn intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_usb_audio snd_usbmidi_lib razerkbd(OE) aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf iwlmvm dell_laptop mac80211 snd_hda_codec_realtek snd_hda_codec_generic input_leds serio_raw snd_hda_codec_hdmi [ 47.202131] dell_wmi dell_smbios dcdbas iwlwifi snd_hda_intel snd_hda_codec btusb dell_wmi_descriptor btrtl uvcvideo btbcm snd_hda_core btintel snd_hwdep bluetooth videobuf2_vmalloc ecdh_generic snd_seq_midi videobuf2_memops intel_wmi_thunderbolt wmi_bmof snd_seq_midi_event snd_pcm videobuf2_v4l2 videobuf2_common videodev media cfg80211 snd_rawmidi rtsx_pci_ms memstick snd_seq snd_seq_device snd_timer hid_multitouch mei_me idma64 mei virt_dma snd processor_thermal_device ucsi_acpi soundcore typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic amdkfd [ 47.202150] amd_iommu_v2 amdgpu rtsx_pci_sdmmc chash gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops i2c_i801 thunderbolt nvme drm i2c_hid rtsx_pci ahci intel_lpss_pci nvme_core libahci intel_lpss hid wmi pinctrl_cannonlake video pinctrl_intel [ 47.202161] CPU: 5 PID: 868 Comm: kworker/5:4 Tainted: GW OE 4.18.0-13-generic #14-Ubuntu [ 47.202161] Hardware name: Dell Inc. Precision 7530/0425K7, BIOS 1.5.2 11/01/2018 [ 47.202170] Workqueue: events drm_mode_rmfb_work_fn [drm] [ 47.202195] RIP: 0010:generic_reg_wait+0xe4/0x160 [amdgpu] [ 47.202195] Code: a9 44 8b 45 20 48 8b 4d 18 89 de 44 89 4d d4 8b 55 10 48 c7 c7 10 74 74 c0 e8 48 47 d4 ff 41 83 7c 24 20 01 44 8b 4d d4 74 02 <0f> 0b 48 83 c4 18 44 89 c8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 41 0f [ 47.202210] RSP: 0018:b7df44a9f948 EFLAGS: 00010297 [ 47.202211] RAX: RBX: 000a RCX: [ 47.202211] RDX: RSI: 8c801bd564b8 RDI: 8c801bd564b8 [ 47.202212] RBP: b7df44a9f988 R08: 00031548 R09: 00010200 [ 47.202212] R10: 0004 R11: a2f8480d R12: 8c7feb1b7300 [ 47.202213] R13: 0bb9 R14: 0001 R15: [ 47.202214] FS: () GS:8c801bd4() knlGS: [ 47.202214] CS: 0010 DS: ES: CR0: 80050033 [ 47.202215] CR2: 7f72dc02d3c8 CR3: 00058040a002 CR4: 003606e0 [ 47.202216] DR0: DR1: DR2: [ 47.202216] DR3: DR6: fffe0ff0 DR7: 0400 [ 47.202216] Call Trace: [ 47.202245] dce110_stream_encoder_dp_blank+0x12f/0x1a0 [amdgpu] [ 47.202269] dce110_blank_stream+0x57/0x90 [amdgpu] [ 47.202293] core_link_disable_stream+0x57/0x220 [amdgpu] [ 47.202317] dce110_reset_hw_ctx_wrap+0xcd/0x1e0 [amdgpu] [ 47.202340] dce110_apply_ctx_to_hw+0x52/0xa30 [amdgpu] [ 47.202364] ? dce110_apply_ctx_for_surface+0x1f2/0x270 [amdgpu] [ 47.202387] dc_commit_state+0x306/0x5b0 [amdgpu] [ 47.202392] ? drm_atomic_helper_setup_commit+0x31e/0x420 [drm_kms_helper] [ 47.202418] amdgpu_dm_atomic_commit_tail+0x37f/0xe40 [amdgpu] [ 47.202421] ? _cond_resched+0x19/0x30 [ 47.202422] ? wait_for_completion_timeout+0x38/0x140 [
[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
Could someone report hat one upstream? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1738676/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
** Changed in: freetype (Ubuntu) Status: Confirmed => Invalid ** Changed in: freetype (Ubuntu Bionic) Status: New => Invalid ** Changed in: freetype (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Invalid Status in openjdk-lts package in Ubuntu: Fix Released Status in freetype source package in Bionic: Invalid Status in openjdk-lts source package in Bionic: New Status in freetype source package in Cosmic: Invalid Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1813376] Re: i dont know what that is
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813376 Title: i dont know what that is Status in xorg package in Ubuntu: Incomplete Bug description: Please help me since I am new to linux and My wifi also got question mark all the time after 15-20 mins ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 25 17:45:45 2019 DistUpgraded: 2018-08-24 14:16:14,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-133-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Seymour [Radeon HD 6400M/7400M Series] [106b:00e1] InstallationDate: Installed on 2015-02-26 (1429 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Apple Inc. MacBookPro8,2 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=754616c8-84b9-4619-95cf-b7420df47da7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-24 (154 days ago) dmi.bios.date: 10/20/16 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B2D.1610201938 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2D.1610201938:bd10/20/16:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Aug 23 23:14:20 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813376/+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 1813431] Re: Problem with start menu and menu bar
Thank you for your bug report, what desktop session do you use? Could you make a screenshot or screencast showing the issue since it's a bit complicated to understand from the description? Could you also add the journalctl log from a session having the problem? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813431 Title: Problem with start menu and menu bar Status in xorg package in Ubuntu: Incomplete Bug description: When I clicked on the start menu in the top right corner, that little window jumped out, and. when I wanted to lock my account, nothing happened, but when I clicked on that panel again, it was like... vibrating... It was moving up and down about 10px (If I remember well). When I left it be and came back later (I have automatic lock after 5 min) There was that menu on the left (I don't know the name :D) After I logged in, I noticed, that when I move my mouse on it, it becomes wider and icons go slightly further apart(When I'm on desktop). When I have Firefox window opened, same happens, but when I aim on Firefox icon, the icons go to normal distance, but bar is still wider. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 23:29:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:805d] InstallationDate: Installed on 2019-01-11 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:760a Microdia Bus 001 Device 002: ID 0458:0188 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProDesk 600 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4d46de66-f485-47e9-905c-9d172082c94d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.16 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC6448GH4 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.16:bd08/18/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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/xorg/+bug/1813431/+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 1792978] Re: initscript avahi-daemon, action "start" failed
Subscribed to field-high as this is causing a lot of failures lately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+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 1813593] [NEW] Please merge 2:3.41-1 into disco
Public bug reported: tracking bug ** Affects: nss (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1813593 Title: Please merge 2:3.41-1 into disco Status in nss package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1813593/+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 1813591] [NEW] pygobject ftbfs in 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 ** Affects: pygobject (Ubuntu) Importance: High Status: New ** Affects: pygobject (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: pygobject (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pygobject (Ubuntu) Importance: Undecided => High ** Changed in: pygobject (Ubuntu Bionic) Importance: Undecided => High ** Tags added: ftbfs rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: New Status in pygobject source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+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 1813587] [NEW] libunistring ftbfs on 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) ** Affects: libunistring (Ubuntu) Importance: High Status: New ** Affects: libunistring (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: libunistring (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libunistring (Ubuntu) Importance: Undecided => High ** Changed in: libunistring (Ubuntu Bionic) Importance: Undecided => High ** Tags added: ftbfs rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: New Status in libunistring source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+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 1813584] [NEW] libidn ftbfs in 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 ** Affects: libidn (Ubuntu) Importance: High Status: New ** Affects: libidn (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: libidn (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libidn (Ubuntu) Importance: Undecided => High ** Changed in: libidn (Ubuntu Bionic) Importance: Undecided => High ** Tags added: ftbfs rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: New Status in libidn source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+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 1813586] [NEW] libnih ftbfs in 18.04 LTS (arm64 only)
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libnih ftbfs on arm64. make check-TESTS make[4]: Entering directory '/<>/nih-dbus' make[5]: Entering directory '/<>/nih-dbus' PASS: test_dbus_error 1 - nih_dbus_error_raise PASS: test_dbus_error 2 - nih_dbus_error_raise_printf make[5]: *** Deleting file 'test_dbus_connection.log' Makefile:1239: recipe for target 'test_dbus_connection.log' failed make[5]: *** [test_dbus_connection.log] Terminated E: Caught signal ‘Terminated’: terminating immediately debian/rules:31: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Terminated make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[2]: *** wait: No child processes. Stop. Makefile:1211: recipe for target 'check-TESTS' failed make[4]: *** [check-TESTS] Terminated Makefile:1326: recipe for target 'check-am' failed make[3]: *** [check-am] Terminated debian/rules:6: recipe for target 'build-arch' failed make: *** [build-arch] Terminated Build killed with signal TERM after 150 minutes of inactivity ** Affects: libnih (Ubuntu) Importance: High Status: New ** Affects: libnih (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: libnih (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libnih (Ubuntu) Importance: Undecided => High ** Changed in: libnih (Ubuntu Bionic) Importance: Undecided => High ** Tags added: ftbfs rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1813586 Title: libnih ftbfs in 18.04 LTS (arm64 only) Status in libnih package in Ubuntu: New Status in libnih source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libnih ftbfs on arm64. make check-TESTS make[4]: Entering directory '/<>/nih-dbus' make[5]: Entering directory '/<>/nih-dbus' PASS: test_dbus_error 1 - nih_dbus_error_raise PASS: test_dbus_error 2 - nih_dbus_error_raise_printf make[5]: *** Deleting file 'test_dbus_connection.log' Makefile:1239: recipe for target 'test_dbus_connection.log' failed make[5]: *** [test_dbus_connection.log] Terminated E: Caught signal ‘Terminated’: terminating immediately debian/rules:31: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Terminated make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[2]: *** wait: No child processes. Stop. Makefile:1211: recipe for target 'check-TESTS' failed make[4]: *** [check-TESTS] Terminated Makefile:1326: recipe for target 'check-am' failed make[3]: *** [check-am] Terminated debian/rules:6: recipe for target 'build-arch' failed make: *** [build-arch] Terminated Build killed with signal TERM after 150 minutes of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1813586/+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 1813580] [NEW] findutils ftbfs in 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html findutils ftbfs. ../build-aux/test-driver: line 107: 20659 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 ** Affects: findutils (Ubuntu) Importance: High Status: New ** Affects: findutils (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: findutils (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: findutils (Ubuntu) Importance: Undecided => High ** Changed in: findutils (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1813580 Title: findutils ftbfs in 18.04 LTS Status in findutils package in Ubuntu: New Status in findutils source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html findutils ftbfs. ../build-aux/test-driver: line 107: 20659 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1813580/+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 1813581] [NEW] gpgme1.0 ftbfs in 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo ** Affects: gpgme1.0 (Ubuntu) Importance: High Status: New ** Affects: gpgme1.0 (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: gpgme1.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gpgme1.0 (Ubuntu) Importance: Undecided => High ** Changed in: gpgme1.0 (Ubuntu Bionic) Importance: Undecided => High ** Tags added: ftbfs rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: New Status in gpgme1.0 source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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 1813568] [NEW] coreutils ftbfs in 18.04 LTS
Public bug reported: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html coreutils ftbfs. ../build-aux/test-driver: line 107: 31009 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 ** Affects: coreutils (Ubuntu) Importance: High Status: New ** Affects: coreutils (Ubuntu Bionic) Importance: High Status: New ** Tags: ftbfs rls-bb-incoming ** Also affects: coreutils (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: coreutils (Ubuntu Bionic) Importance: Undecided => High ** Changed in: coreutils (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1813568 Title: coreutils ftbfs in 18.04 LTS Status in coreutils package in Ubuntu: New Status in coreutils source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html coreutils ftbfs. ../build-aux/test-driver: line 107: 31009 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813568/+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 1813557] [NEW] [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all
Public bug reported: i can play sound without headphone but when i connect headphone sound can not play at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masoud 3192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 14:31:19 2019 InstallationDate: Installed on 2019-01-15 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2111 F pulseaudio masoud 3192 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X756UWK.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X756UWK 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.:bvrX756UWK.307:bd03/08/2017:svnASUSTeKCOMPUTERINC.:pnX756UWK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX756UWK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X756UWK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813557 Title: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: i can play sound without headphone but when i connect headphone sound can not play at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masoud 3192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 14:31:19 2019 InstallationDate: Installed on 2019-01-15 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2111 F pulseaudio masoud 3192 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X756UWK, Conexant CX20751/2, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X756UWK.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X756UWK 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.:bvrX756UWK.307:bd03/08/2017:svnASUSTeKCOMPUTERINC.:pnX756UWK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX756UWK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X756UWK 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/alsa-driver/+bug/1813557/+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 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
** Tags removed: amd64 ** Tags added: cosmic rls-bb-incoming -- 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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811447/+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 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
** Package changed: xorg (Ubuntu) => xserver-xorg-video-modesetting (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/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in xserver-xorg-video-modesetting package in Ubuntu: New Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-modesetting/+bug/1813423/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
Hello Nathaniel, or anyone else affected, Accepted xorg-server into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.20.3-0ubuntu0.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. ** Changed in: xorg-server (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Fix Committed Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on
[Touch-packages] [Bug 1377600] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Status in ufw source package in Disco: Fix Released Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+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 1204579] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1204579 Title: ufw doesn't support concurrent updates Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw prior to 0.36 did not support locking or use xtables locking which can lead to problems when using ufw as a dynamic firewall. [Test Case] $ sudo apt-get install python-minimal # for the test script $ sudo ./test_ufw_threads.py # this runs for many seconds A patched ufw will complete with no errors. With an unpatched ufw, there will be many errors like: $ sudo ./test_ufw_threads.py ... ERROR: initcaps [Errno 2] iptables: Chain already exists. ERROR: initcaps [Errno 2] iptables: Chain already exists. [Regression Potential] ufw 0.36 implements a global exclusive lock before doing any kernel or file writes. Risk of regression includes the lock file not being released due to coding error. The locking is done via fcntl.lockf and ufw releases it in a finally clause that is careful to always release it. [Other Info] This locking code has been in production in the ufw snap for years and is known to work is static environments as well as in dynamic environments (IPS/fail2ban/etc). = Original description = On a server under Ubuntu 12.04 I automatically update firewall rules and I unfortunately noticed that if 2 rules are processed at the same time it leads to an inconsistent result between iptables and ufw status. In fact it can be reproduced using the python script in attachment. Before executing this script I didn't have any rules matching the ip 192.168.254.1 on my computer. After a launch iptables takes into acount 464 rules. sudo iptables -L -n | grep 192.168.254.1 | wc -l 464 It should be 500 rules but the script stressed a lot my system and all rules can't be processed by iptables sudo ./test_ufw_threads.py iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. [...] Anyway, ufw stores only the last updates (in /lib/ufw/user.rules): sudo ufw status État : actif Vers Action Depuis -- -- 192.168.254.1 1234/tcp ALLOW 192.168.46.9 192.168.254.1 1234/tcp ALLOW 192.168.22.10 192.168.254.1 1234/tcp ALLOW 192.168.32.10 192.168.254.1 1234/tcp ALLOW 192.168.5.10 192.168.254.1 1234/tcp ALLOW 192.168.43.9 192.168.254.1 1234/tcp ALLOW 192.168.40.10 192.168.254.1 1234/tcp ALLOW 192.168.46.10 192.168.254.1 1234/tcp ALLOW 192.168.48.10 192.168.254.1 1234/tcp ALLOW 192.168.42.10 192.168.254.1 1234/tcp ALLOW 192.168.43.10 So I can't delete other rules using ufw, I had to directly use iptables. In this case I can only delete 10 rules using ufw. Could you please handle some kind of lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1204579/+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 1509725] Proposed package upload rejected
*** This bug is a duplicate of bug 1664133 *** https://bugs.launchpad.net/bugs/1664133 An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1509725 Title: Some ICMPv6 packets rejected due to rule ordering Status in ufw package in Ubuntu: Fix Released Bug description: In the default before6.rules file, the following lines: # drop INVALID packets (logs these in loglevel medium and higher) -A ufw6-before-input -m conntrack --ctstate INVALID -j ufw6-logging-deny -A ufw6-before-input -m conntrack --ctstate INVALID -j DROP are present before the ICMPv6 rules. The problem is that this also captures echo replies (but, somehow, allows echo requests) and some IPv6 routing announcements. If I try to ping ff02::1 to ping all devices on the local network, I only get a response from my own device. Moving those three lines towards the end of the file (after all ICMP rules and before the COMMIT) fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ufw 0.34-2 Uname: Linux 4.3.0-rc5arcot x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 24 18:07:40 2015 InstallationDate: Installed on 2012-10-19 (1099 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to wily on 2015-02-28 (238 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2015-08-08T23:49:55.322401 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1509725/+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 1368411] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw's 'insert' command is designed to work with 'ufw status numbered' to insert rules in specific places in the ruleset. This makes it more difficult than it should be for using ufw as part of an IPS/dynamic firewall (eg, fail2ban) since if the firewall already has an IPv4 rule then the user/IPS must calculate the position of an IPv6-only rule before inserting it. From the git commit: " add 'prepend' command Introduce 'prepend' command to add rules to the top of the IPv4 and/or IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg, fail2ban). Unlike 'insert', 'prepend' does not require knowledge about the IPv6 rule number so integration into IPS is much easier. " [Test Case] $ sudo ufw allow 22/tcp $ sudo ufw allow from 1.2.3.4 $ sudo ufw allow from 2001:db8::/32 $ sudo ufw enable $ sudo ufw status numbered ... [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 # unchanged from 0.35 $ sudo ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 ERROR: Invalid position '1' # new in 0.36 $ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1 $ sudo ufw prepend deny from 6.7.8.9 $ sudo ufw status numbered ... [ 1] Anywhere DENY IN 6.7.8.9 [ 2] 22/tcp ALLOW INAnywhere [ 3] Anywhere ALLOW IN1.2.3.4 [ 4] Anywhere (v6) DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1 [ 5] 22/tcp (v6)ALLOW INAnywhere (v6) [ 6] Anywhere (v6) ALLOW IN2001:db8::/32 [Regression Potential] ufw has a clean methodology for adding new commands so while frontend.py necessarily has some logic changes to calculate where to insert the rule (ie, if IPv4 at the top, if IPv6 before other IPv6 rules and if both, both), the changes were minimal and only are used if 'prepend' is specified (so people only using the previous command set should be fine). [Other Info] The ufw prepend command is new in 0.36 and thus only available in Debian, Ubuntu disco and the ufw snap for a few weeks. The snap is known to work with fail2ban and the prepend command in production environments since it was available. = Original description = I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 1602834] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1602834 Title: obsolete conffiles not cleaned up on upgrade Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Status in ufw source package in Disco: Fix Released Bug description: Hi, the following conffile is marked as obsolete in my dpkg status db /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete Ufw now ships /usr/share/bash-completion/completions/ufw, so the conffile should be removed on upgrades. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 13 22:19:52 2016 InstallationDate: Installed on 2011-11-10 (1706 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1602834/+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 1664133] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1664133 Title: ipv6 multicast pings don't return Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Bug description: [Impact] ping6 replies to multicast addresses are mistakenly blocked. ufw used to have correct ordering for these replies, but 0.34 reorganized the icmp rules and reintroduced LP: #720605 (this bug). multicast ping replies are part of the ok icmp codes for INPUT (rfc4890, 4.4.1 and 4.4.2) but don't have an associated connection and are marked INVALID, so move this rule above the INVALID rules. [Test Case] On an IPv6 enabled system, perform a multicast ping like so: $ sudo ufw enable $ sudo ping6 ff02::1%wlp58s0 # where 'wlp58s0' is your network iface PING ff02::1%wlp58s0(ff02::1%wlp58s0) 56 data bytes 64 bytes from ...addr1...: icmp_seq=1 ttl=64 time=0.081 ms 64 bytes from ...addr2...: icmp_seq=2 ttl=64 time=0.155 ms ^C $ Without this fix, only see responses from the ff80 address of the specified interface (ie, the 'wlp58s0' interface in the above example). With the fix, there should be a response from other IPv6 enabled hosts on the network. [Regression Potential] The regression potential is extremely low since we are simply moving a single rule above another rule. The worst that could happen is that the ping6 would continue to not work. = Original description = Hi, I have the default settings from Linux Mint 18 for ufw. When I "ping6 ff02::1%wlp3s0", I get only an answer from my own ip. Duplicates from other devices on the net get filtered. It works fine after "sudo ufw disable". ufw --version ufw 0.35 Copyright 2008-2015 Canonical Ltd. I've attached the output of ip6tables-save. There is a similar old and long fixed bug: https://bugs.launchpad.net/ufw/+bug/720605 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1664133/+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 1775043] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1775043 Title: bash completion not working: uses deprecated have() Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Bug description: [Impact] Tab completion is currently broken. [Test Case] $ ufw allow delete --dry-run --help loggingreset status appdeny enable insert reject route version defaultdisable--forcelimit reload show With an unpatched ufw, tab completion only shows the files in the current directory, which is meaningless for ufw. [Regression Potential] Risk of regression is considered very low since tab completion is totally broken and correct functionality is easily tested. = Original description = bash completion, defined in /usr/share/bash- completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1775043/+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 1719211] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1719211 Title: Bad interface name Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Bug description: [Impact] ufw's interface name's or both too strict (this bug) and too loose (iptables has its own limits). Adjust the interface name checks to match those of the kernel. [Test Case] $ sudo ufw --dry-run allow in on i-1|grep i-1 ### tuple ### allow any any 0.0.0.0/0 any 0.0.0.0/0 in_i-1 -A ufw-user-input -i i-1 -j ACCEPT ### tuple ### allow any any ::/0 any ::/0 in_i-1 -A ufw6-user-input -i i-1 -j ACCEPT With an unpatched ufw, the above results in: $ sudo ufw --dry-run allow in on i-1|grep i-1 ERROR: Bad interface name [Regression Potential] Risk of regression is considered low since the updated allow more than what is currently allowed, but not more than what iptables allows. See: https://git.launchpad.net/ufw/tree/src/common.py?h=release/0.36#n295 = Original description = Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+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 1811129] Proposed package upload rejected
An upload of ufw to cosmic-proposed has been rejected from the upload queue for the following reason: "All bugs mentioned in the .changes file (so therefore also in the new debian/changelog entries) need to comply with SRU standards (test-case, regression potential). Please re-upload after filling out the required info or modify changelog to exclude irrelevant bug numbers.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1811129 Title: update ufw to 0.36 Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: In Progress Status in ufw source package in Cosmic: In Progress Status in ufw source package in Disco: Fix Released Bug description: [Impact] This bug is the master bug for a one time SRU of ufw to the new 0.36 release. Typically patches would be individually backported like normal, but the new 'prepend' command feature is the impetus for this SRU and it contains most of the code changes. Other bugs fixes in the upstream release are either already included in the Ubuntu/Debian packaging or small enough to not pose a significant regression risk. 0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading 18.04 to 0.36 will make maintaining ufw a bit easier for the duration of this LTS. [Test Case] In addition to the in-build tests, there is an extensive testsuite for running under root on the live system. The QRT tests for ufw (scripts /test-ufw.py) run these tests (and more). [Regression Potential] In terms of code changes, I've attached code-changes-bionic-to- disco.diff which is a diff of the source code in bionic's 0.35-5 with patches applied and disco's 0.36-1 with its patches applied. This shows that: * only comment changes to conf/sysctl.conf * only comment changes to conf/ufw.defaults * doc/systemd.example is updated (but unused in our packaging) * various man page updates * ufw.pot is refreshed * various Makefile updates related to snap packaging and coverage (the debian packaging only uses the 'clean' target) * src/applications.py has only whitespace and comment changes The remaining code changes in src/ are quite small and address the SRU bugs and the regression potential for these changes will be discussed in those bugs. [Other Info] Note that the 0.36 code base has been the basis for the snap for many months with the majority of the non-'prepend' changes in production during this time. 0.36-1 was uploaded to Debian last month (and it migrated automatically to disco shortly after) with no new bug reports in either. The snappy packaging, which is included upstream, underwent a lot of changes, but should not be considered as part of this SRU since it doesn't affect the deb builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1811129/+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 1644996] Re: logrotate config uses syslog group
** Also affects: logrotate (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: logrotate (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1806532] Re: The line-out on the Dell Dock station can't work
...ignore me, I see the alsa-lib part has been already released for cosmic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in alsa-lib source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1806532] Re: The line-out on the Dell Dock station can't work
This bug was fixed in the package alsa-lib - 1.1.3-5ubuntu0.2 --- alsa-lib (1.1.3-5ubuntu0.2) bionic; urgency=medium * d/p/0014-conf-ucm-Add-a-UCM-profile-for-Dell-WD15-Dock-USB-au.patch * d/p/0015-conf-ucm-Dell-WD15-Dock-Fix-incorrect-device-names.patch * d/p/0016-conf-USB-Audio-Add-Dell-WD19-Dock-in-the-IEC958-blac.patch * d/p/0017-configure-Fix-forgotten-ucm-entry.patch - enable line-out on the Dell WD Dock stations (LP: #1806532) -- Hui Wang Wed, 19 Dec 2018 12:25:25 +0800 ** Changed in: alsa-lib (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in alsa-lib source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1644996] Re: logrotate config uses syslog group
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1644996] Re: logrotate config uses syslog group
Dimitri John Ledkov, thanks for fixing, it would be nice if fix appear in LTS releases too, at least in Ubuntu 18.04 "Bionic" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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
