[Touch-packages] [Bug 1791783] Re: cupsd denied
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/1791783 Title: cupsd denied Status in apparmor package in Ubuntu: Confirmed Bug description: Sep 10 12:15:44 server1 kernel: [ 645.335635] audit: type=1400 audit(1536603344.350:58): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12 capname="net_admin" Sep 10 12:15:44 server1 kernel: [ 645.338733] audit: type=1400 audit(1536603344.354:59): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12 capname="net_admin" Sep 10 12:15:44 server1 kernel: [ 645.339664] audit: type=1400 audit(1536603344.354:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12 capname="net_admin" apparmor-2.12-4ubuntu5, ubuntu 18.04.1 sudo aa-complain /usr/sbin/cupsd allows me to print. Sep 10 12:19:04 server1 kernel: [ 845.532951] audit: type=1400 audit(1536603544.545:61): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=16673 comm="apparmor_parser" Sep 10 12:19:04 server1 kernel: [ 845.533182] audit: type=1400 audit(1536603544.545:62): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=16673 comm="apparmor_parser" Sep 10 12:19:04 server1 kernel: [ 845.546603] audit: type=1400 audit(1536603544.561:63): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=16673 comm="apparmor_parser" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1791783/+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 1801551] [NEW] ubuntu does not load the image from swap after hibernation
You have been subscribed to a public bug: after upgrading from 16.04 to 18.04 the upgrade messes up the boot process and hibernatation does not work. I hibernate by systemctl hibernate it asks for a password and it seemingly saves the image and shuts down. when I start the computer it does not load the saved image but opens a blank session losing the saved workspace. very inconvenient to start from scratch every time. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Incomplete -- ubuntu does not load the image from swap after hibernation https://bugs.launchpad.net/bugs/1801551 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801564] [NEW] Can't connect second monitor on NVidia over adapter DVI->VGA
Public bug reported: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835] MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: STRIX B250F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Sun Nov 4 07:41:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1801564 Title: Can't connect second monitor on NVidia over adapter DVI->VGA Status in xorg package in Ubuntu: New Bug description: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00
[Touch-packages] [Bug 1801551] Re: ubuntu does not load the image from swap after hibernation
This would certainly not be a bug in grub, which has nothing to do with hibernate/resume handling. What disk is the target for your hibernation? What are the contents of the RESUME setting in your initramfs? (unmkinitramfs /boot/initrd.img /tmp/initrd; cat /tmp/initrd/main/conf/conf.d/zz-auto-resume) Resume from hibernation only works if you resume into the same kernel after hibernation that you were running before hibernation. Is it possible that you were rebooting into a different kernel version due to kernel security updates having been applied? ** Package changed: grub (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/1801551 Title: ubuntu does not load the image from swap after hibernation Status in initramfs-tools package in Ubuntu: Incomplete Bug description: after upgrading from 16.04 to 18.04 the upgrade messes up the boot process and hibernatation does not work. I hibernate by systemctl hibernate it asks for a password and it seemingly saves the image and shuts down. when I start the computer it does not load the saved image but opens a blank session losing the saved workspace. very inconvenient to start from scratch every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801551/+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 1772578] Re: [Nvidia HDA] audio crackling
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
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/1772578
Title:
[Nvidia HDA] audio crackling
Status in gnome-shell package in Ubuntu:
Expired
Status in pulseaudio package in Ubuntu:
Expired
Bug description:
Hello,
on Ubuntu this bug regularly appearing: audio suddenly crackling for all
softwares.
If I restart pulseaudio, it changes nothing.
But if I restart gnome-shell ("alt+F2", type "r"), the audio no more
crackling.
I had this bug for Ubuntu 17.10 and perhaps 17.04 too.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
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/pcmC0D7p: romain 3648 F...m pulseaudio
/dev/snd/controlC0: romain 3648 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 22 07:56:34 2018
InstallationDate: Installed on 2012-07-07 (2144 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
dmi.bios.date: 09/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G45 (MS-7752)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7752
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1772578] Re: [Nvidia HDA] audio crackling
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
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/1772578
Title:
[Nvidia HDA] audio crackling
Status in gnome-shell package in Ubuntu:
Expired
Status in pulseaudio package in Ubuntu:
Expired
Bug description:
Hello,
on Ubuntu this bug regularly appearing: audio suddenly crackling for all
softwares.
If I restart pulseaudio, it changes nothing.
But if I restart gnome-shell ("alt+F2", type "r"), the audio no more
crackling.
I had this bug for Ubuntu 17.10 and perhaps 17.04 too.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
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/pcmC0D7p: romain 3648 F...m pulseaudio
/dev/snd/controlC0: romain 3648 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 22 07:56:34 2018
InstallationDate: Installed on 2012-07-07 (2144 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
dmi.bios.date: 09/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G45 (MS-7752)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7752
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Changed in: openssh (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
** Tags added: regression-release -- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1781597] Re: [SRU] WoWLAN settings are not supported
** Changed in: network-manager (Ubuntu) Importance: Undecided => Wishlist -- 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/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Confirmed Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packages over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
** Tags added: xenial
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => Wishlist
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771783
Title:
iproute2: frr route protocols are not converted to string on xenial
Status in iproute2 package in Ubuntu:
New
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile
** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => High -- 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/1750947 Title: pulseaudio print lots of error when selecting unavailable profile Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Confirmed Bug description: SRU Document: [Impact] A HDMI audio device usually has several output ports, each port represents a profile in pulseaudio, without this patch, the puseaudio always choose the first profile no matter it is active or not. [Test Case] connect each port of HDMI device, and check if the profile of that port is active or not. [Regression Potential] The patch will check all ports under each profile, if a profile only contains unavailable ports, this profile will be set to unavailable as well. Without this patch, all profiles are always available, then if a profile includes a unusable hdmi-output, and pulseaudio select this profile to be active (since its priority is the highest), the kernel audio driver will crash. I think this patch will not introduce regression: 1) It is a correct logic to set a profile to be unavailable if it only contains unavailable ports. 2) pulseaudio-artful and pulseaudio-bionic already include this patch, they work very well 3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop and 1 dell desktop, all worked well as before 4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C without analogue audio) which have unusable hdmi-output profile on them, the kernel driver did not crash anymore and audio function worked very well. [Other Info] Only pulseaudio-xenial has this problem. we need to backport this commit to pulseaudio-xenial. https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4 After printing out the error logs, the kernel crashes and system hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9
** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => High -- 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/1767784 Title: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9 Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Bug description: SRU Document: [Impact] The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even there is no internal speaker and nothing plugged in the audio jack, the profile is still set available, then the active profile is analog- stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to unavailable, and the active profile is off, after users plug sth in the audio jack, the active profile will not switch automatically, need users to switch manually, this change is unfriendly to users. [Test Case] On the machines without internal speaker, open sound-setting and check if there is some output devices in the UI, and play sound from the UI. Under 1:8.0-0ubuntu3.9 there is no output device, and can't play sound; under 1:8.0-0ubuntu3.8 there is output device, and can play sound. [Regression Potential] This is a revert, after reverting, the content of pulseaudio is exactly same as 1:8.0-0ubuntu3.8 [Other Info] none Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not showing anymore my soundcard. https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9 The command "pacmd list-sinks" only shows a dummy output When running on a fresh install of ubuntu 16.04, the sound is ok. When updating the install with locking the following files to version 1:8.0-0ubuntu3 the sound keeps working: libpulse0:amd64 libpulse-mainloop-glib0:amd64 libpulse-dev:amd64 pulseaudio-module-x11:amd64 pulseaudio-module-bluetooth:amd64 pulseaudio-utils:amd64 When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output". I tried running the following versions of Ubuntu (live usb), and get the same issue (no need to update to get the problem) 17.04 17.10 18.04 I attached the result of command "pactl list" I have also generated logs during the boot but I don't know how to attach multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1059541] Re: Change default behavoir to boot degraded RAID
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1059541 Title: Change default behavoir to boot degraded RAID Status in initramfs-tools package in Ubuntu: Confirmed Bug description: A degraded RAID should be started and boot should be attempted *by default*, since jumping into busybox in case one is degraded, gives the admin very few possible actions than "exit" and debug the problem from Linux instead. Not booting degraded arrays is also a problem for new administrators, since jumping into busybox blanks the screen and in pratice stops the information flow from the system. Can you please change this in future versions? roy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1059541/+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 1196693] Re: Cannot boot degraded RAID1 array with LUKS partition
Ubuntu 18.04 is still affected with a blank test installation.
Please update the bugtracker entry to reflect this.
I would be really happy if this could be fixed, it's been 5 years and
this breaks using RAID with dm-crypt :(
Steps to reproduce:
- Install via network installer, create the following partition layout manually:
{sda1, sdb1} -> md RAID1 -> btrs -> /boot
{sda2, sdb2} -> md RAID1 -> dm-crypt -> btrfs -> /
- After the system is installed and confirmed as working, shutdown and
remove sdb
- Boot will now hang at "Begin: Waiting for encrypted source device
...". That will timeout eventually and drop to an initramfs shell,
complaining that the disk doesn't exist.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1196693
Title:
Cannot boot degraded RAID1 array with LUKS partition
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in initramfs-tools-ubuntu-core package in Ubuntu:
Invalid
Bug description:
When pulling out a disk on my 12.04.2 RAID1 setup, which contains a
LUKS container inside an md device, my system won't boot. Plugging the
second disk back in worked, but I wanted to replace my disks, and if a
disk is broken you don't have that option...
Debugging the initramfs boot sequence seems to indicate that the
crypto handling is done before degraded array handing, rendering the
BOOTDEGRADED flag ineffective.
I've looked at other bugs (#1077650 #1003309 #728435 #106215) but I
think it's a different problem.
Situation
I've got a LVM-in-LUKS-in-RAID1 setup, with a separate, RAID'ed
bootpartition.
# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md126 : active raid1 sda2[0] sdb2[2]
523968 blocks super 1.2 [2/2] [UU]
md127 : active raid1 sda1[0] sdb1[2]
976106048 blocks super 1.2 [2/2] [UU]
unused devices:
md127 contains a LUKS container, called ugh2_lvm.
ugh2_lvm contains an LVM with a volume group called ugh2_vg.
ugh2_vg contains LV's called "root" (the root filesystem) and "swap".
# mount | grep /dev/m
/dev/mapper/ugh2_vg-root on / type ext4 (rw,relatime)
/dev/md126 on /boot type ext4 (rw)
# cat crypttab
ugh2_lvm UUID=69ade3d3-817d-42ee-991b-ebf86e9fe685 none luks
# grep 'DEGRADED=' /etc/initramfs-tools/conf.d/mdadm
BOOT_DEGRADED=true
Symptoms
Booting seems to hang with a message "evms_activate is not available".
I'm not using EVMS so the message is not really indicative of the
problem. Perhaps you get dropped to a shell after a lot of time (3
minutes? I saw a time-out of 180 seconds in the scripts somewhere) but
that took too long for me.
Diagnosis
Interrupting the boot process with break=premount let me take a look
at the situation. Turns out the degraded arrays assembled, but
inactive; the BOOT_DEGRADED handling activates the degraded arrays
(scripts/local-premount/mdadm). However, it does not get the chance to
do so before the scripts try to open the LUKS device with the
configured UUID, since this is done by scripts/local-top/cryptroot.
"*-top" scripts are run before "*-premount" scripts.
Workaround / solution
I made it work again by linking /usr/share/initramfs-tools/scripts
/local-premount/mdadm -> /etc/initramfs-tools/scripts/local-
top/mdadm, then rebuilding my initramfs (update-initramfs -u).
It seems to work well. Not sure if it's the best or even a clean
approach.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1196693/+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 1380702] Re: No keyboards shortcuts in QT apps
** Changed in: qtbase-opensource-src (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** Changed in: canonical-devices-system-image Status: In Progress => Fix Released ** Changed in: appmenu-qt5 Status: In Progress => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => Medium ** Changed in: qtbase-opensource-src (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: qtbase-opensource-src (Ubuntu Yakkety) Importance: Undecided => Medium ** Project changed: sni-qt => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: Fix Released Status in Canonical System Image: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Yakkety: Won't Fix Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1801540] Re: Microphone distorted sound on ALC892
Uhm yes I know that, but apport-collect is just not working as I already said... -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** No longer affects: snapd (Ubuntu) ** No longer affects: snapd (Ubuntu Xenial) ** Project changed: snappy => ubuntu-translations ** No longer affects: ubuntu-translations ** Project changed: qt => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in libappindicator source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Xenial: Confirmed Status in sni-qt source package in Xenial: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1600136/+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 1801540] Re: Microphone distorted sound on ALC892
https://help.ubuntu.com/community/ReportingBugs -- Cristian Aravena Romero (caravena) ** Changed in: linux (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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Yes, that is it! systemctl stop timidity.service systemctl disable timidity.service solves the problem. On Sat, Nov 3, 2018 at 9:30 PM Cristian Aravena Romero wrote: > > *** This bug is a duplicate of bug 210472 *** > https://bugs.launchpad.net/bugs/210472 > > ** This bug has been marked a duplicate of bug 210472 >Timidity daemon doesn't play nice with pulse audio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1801538 > > Title: > no sound after upgrading to ubuntu 18.10 from 18.04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+subscriptions -- Thomas -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
** Changed in: xdg-utils (Ubuntu Bionic) Importance: Undecided => High ** No longer affects: perl (Ubuntu) ** No longer affects: perl (Ubuntu Bionic) ** No longer affects: perl (Ubuntu Cosmic) -- 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/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in xdg-utils package in Ubuntu: Fix Released Status in xdg-utils source package in Bionic: Fix Committed Status in xdg-utils source package in Cosmic: Fix Released Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1743216/+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 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1799202 Title: SRU: update Python 3.7 to the 3.7.1 release Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Committed Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: New Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.1 release. 3.7.1 is the first maintenance release, update both 18.04 LTS and 18.10 to the release. For 18.10 it's just one bug fix compared to the release candidate 2. python3-stdlib-extensions also updates the modules to the 3.6.7 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 ** This bug has been marked a duplicate of bug 210472 Timidity daemon doesn't play nice with pulse audio -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801540] Re: Microphone distorted sound on ALC892
I tried running it, I don't know honestly if that worked because when I clicked on that link a browser page just appeared showing nothing relevant ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1164016] Re: restore type-ahead find
One more vote for a type-ahead navigation rather than a search. The search is stupid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1801540] Re: Microphone distorted sound on ALC892
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1801540 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1801541] Re: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1801541 Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: failed to upload proprietary packages during installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.9 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Nov 3 11:17:28 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-01 (1067 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1801541/+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 1801541] [NEW] package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: failed to upload proprietary packages during installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.9 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Nov 3 11:17:28 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-01 (1067 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-11-03 (0 days ago) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1801541 Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: failed to upload proprietary packages during installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.9 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Nov 3 11:17:28 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-01 (1067 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1801541/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
I found solution with command: "sudo apt purge timidity-daemon", and then reboot. After this, sound works like sharm. Source: https://askubuntu.com/questions/1085174/no-sound-after-upgrade- to-18-10-only-a-dummy-device-is-shown/1085992#1085992 -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801540] [NEW] Microphone distorted sound on ALC892
Public bug reported: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info" https://bugs.launchpad.net/bugs/1801540/+attachment/5208845/+files/alsa-info ** Package changed: alsa-lib (Ubuntu) => alsa-driver (Ubuntu) -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
I have this problem too, how can I fix it? I have Acer Aspire V Nitro II. -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1776200] Re: package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1776200 Title: package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: Confirmed Bug description: How to solve this problem? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.9-0ubuntu7 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 Architecture: amd64 CrashReports: 600:0:117:212493:2018-06-11 16:03:27.512198209 +0530:2018-06-11 16:03:28.512198209 +0530:/var/crash/python3-apport.0.crash Date: Mon Jun 11 16:03:28 2018 DuplicateSignature: package:python3-apport:2.20.9-0ubuntu7 Setting up python2.7 (2.7.15~rc1-1) ... dpkg: error processing package python3-apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: apport Title: package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1776200/+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 1801538] [NEW] no sound after upgrading to ubuntu 18.10 from 18.04
Public bug reported: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801533] Re: lightdm does not start
This schouldn't happen. lightdm should only be started about 10 times, then disabled. BTW: no errors are readable on screen. Logs only show lightdm restarted by systemd after terminatating. Errors can be seen by disabling lightdm, then starting it from commandline. But this isn't helpful either: "Could not initialize screen. Terminating." -- 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/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start
This bug exists since 16.10 – we are at 18.10 now it is now two years with this monitor killing bug. -- 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/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start
Same problem: it does not matter if upgraded from 18.04 or installed new with 18.10. lightdm might not allways be capable initializing graphics leeding to some loop together with systemd turning on backlight, turning it off again, then restarting. Backlight is turned on, then off about twice a second. After some time backlight electronics break down, killing the monitor. -- 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/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] [NEW] lightdm does not start
Public bug reported: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf
checking for !s->userdata seems to fix it -- 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf
the line in question is, I think: if (!s->userdata->client || avahi_client_get_state(s->userdata->client) != AVAHI_CLIENT_S_RUNNING) return; something here is null, probably because there's a restart happening? -- 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening To manage notifications about
[Touch-packages] [Bug 1801532] [NEW] pulseaudio crashing when publishing sound devices to zeroconf
Public bug reported: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I had the same problem after upgrading to 18.10. Uncommenting "WaylandEnable=false" worked. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
Happens with me too -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Same issue here with 18.10 The bug is here and ignoring it for 2 years is just ridiculous -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
In 18.04 I can get the modem working by: sudo usb_modeswitch -v 0x03f0 -p 0x9d1d -u3 -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1801338] Re: apt fails to properly handle server-side connection closure
** Tags added: id-5bdb63ea912f3607fa876c2d -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+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 1747711] Re: file mis-identifies modern executables as application/x-sharedlib
Electron applications using Electron 4.0.0 beta/nightly are effected by
this bug making it impossible for developers to create Linux
applications and have it easily work using that version, doesn't effect
applications developed Electron 3.0.6 latest but this is a seriously
annoying bugs that will cause issues with Linux users and needs to be
patched.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1747711
Title:
file mis-identifies modern executables as application/x-sharedlib
Status in file package in Ubuntu:
Confirmed
Bug description:
file doesn't recognize modern PIE (Position Independent Executable)
x86 executables as such, reporting them as “application/x-sharedlib”.
Consequently, only non-PIE executables can be opened in graphical file
managers such as nautilus. This may cause a minor (?) security risk if
a commonly-published workaround is attempted.
Expected behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-executable
Actual behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-sharedlib
Workaround (unsafe?):
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo-nopie foo.c -no-pie
$ file foo-nopie
foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
$ file --mime-type foo-nopie
foo-nopie: application/x-executable
gcc now defaults to building with PIE enabled for security reasons.
Also affects: nautilus (and likely other graphical file managers like
those on Lubuntu) - because nautilus uses mime-type to determine if a
file is executable, double-click to run a program no longer works.
Also noted on: Gnome Bugs -
https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
became the default build option.
This may be an upstream issue. This may not affect architectures
outside x86.*
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: file 1:5.32-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb 6 11:21:20 2018
InstallationDate: Installed on 2017-05-11 (270 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: file
UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1747711/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
Daniel, the audio card id string seems to be the same, so I suspect it might be the same issue. Anyway, I have found the culprit. Sound card was intercepted by another process (timidity), so Pulseaudio was unable to use it. I have discovered the offending process via the `sudo fuser /dev/snd/*` command. Uninstalling timidity has solved the issue. -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 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 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1796900] Re: Inconsistency in the man page regarding created archive file
** Tags added: bitesize manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1796900 Title: Inconsistency in the man page regarding created archive file Status in tar package in Ubuntu: New Bug description: This is just a minor mistake, but still worth correcting, I think. In the man page for tar_1.29b-2_amd64 and also tar_1.30+dfsg-2_amd64, the first command demonstrating the option styles is tar cfv a.tar /etc which creates the archive a.tar. In the text, however, it is said to create the file etc.tar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1796900/+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
