[Touch-packages] [Bug 1831299] Re: i cant install driver
What hardware do you want to install a driver for? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831299 Title: i cant install driver Status in Ubuntu: Incomplete Bug description: idk more about this bug , but can you fix it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 06:10:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0724] InstallationDate: Installed on 2019-05-30 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Acer Aspire V5-431 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=c6efd4c5-770f-43f5-babc-e1f4d6123bf6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.05. dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V1.05. dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.05.:bd04/18/2012:svnAcer:pnAspireV5-431:pvrV1.05.:rvnAcer:rnAspireV5-431:rvrV1.05.:cvnAcer:ct9:cvrV1.05.: dmi.product.family: ChiefRiver System dmi.product.name: Aspire V5-431 dmi.product.sku: System SKUNumber dmi.product.version: V1.05. dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1831299/+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 1831339] Re: Backup Unbuntu ERROR undefined
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Backup Unbuntu ERROR undefined + duplicity crashed in with_tempdir ** Package changed: ubuntu => duplicity (Ubuntu) ** Changed in: duplicity (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831339 Title: duplicity crashed in with_tempdir Status in duplicity package in Ubuntu: New Bug description: Backup Unbuntu ERROR undefined ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat Jun 1 14:59:04 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (66 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1831339/+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 1831347] Re: Xorg freeze - update
Could you please describe the problem in a single sentence so we can give this bug a more appropriate title and assign it to the correct package? ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831347 Title: Xorg freeze - update Status in Ubuntu: Incomplete Bug description: Dear Ubuntu, Thank you for taking the time to read this report. My last report stated that nvidia-430 driver was the problem. I have since reinstalled ubuntu 18.4 and carefully followed the EGPU setup provided online using gswitch. I should note that last install I forgot to add "systemctl enable gswitch". I have noticed far fewer issues. Interestingly, I also enabled autologin for my account. This appears to have helped the problem significantly. I did try switching to regular password required at login and the freezing / hanging did occur during some web browsing but it was only for about 5 - 10 seconds. I then immediately switched back to autologins and I have not noticed any freezing or hanging! I believe the problem with regular password req logins is that it causes my internal display (laptop screen) to be enabled first during the login when I enter my password. After I enter my password the internal display turns off and then I use my external display only as I have that confiured in the ubuntu device settings. But with autologin, the computer boots momentarily to internal screen when you see the ubuntu dots sliding to the right and then into gnome. So it appears using autologin is more stable when using an EGPU with external display only! I am using nvidia-430 drivers. So I think gdm3 needs an update or X11 needs an update so that it can honor the external display better? Anyways! I will keep you posted. Thanks for your dedication guys!! Take care, Peter ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.14 Wed May 8 01:10:53 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 16:26:04 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=96ec9aa4-d13a-4223-b15b-4284df054c79 ro quiet splash nouveau.modeset=0 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-
[Touch-packages] [Bug 1831218] Re: xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831218 Title: xorg Status in Ubuntu: Incomplete Bug description: ubuntu 16.04 GF106GL $ sudo ubuntu-drivers autoinstall nvidia-384 $ sudo ubuntu-bug xorg Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 31 12:33:50 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-50-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-50-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF106GL [Quadro 2000] [10de:084a] InstallationDate: Installed on 2019-05-24 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=010c1118-5303-4b15-9fc0-a5cb2c806fb5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-P 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.:bvr1205:bd05/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-P: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.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 31 11:53:0
[Touch-packages] [Bug 1831101] Re: rsync with remote sudo fails over ssh/pki with protocol mismatch error
Thanks Gareth to come back and document the fix for your case! This will certainly help other users finding this bug if they run into the same. ** Changed in: rsync (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1831101 Title: rsync with remote sudo fails over ssh/pki with protocol mismatch error Status in rsync package in Ubuntu: Invalid Bug description: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude --delete --link-dest=../$lastdt /etc $dest/$dt -- The [redacted] output is opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 (20 args) OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xxx [192.168.1.120] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/user/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug1: Authenticating to xxx:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: MAC: compression: none debug1: kex: client->server cipher: MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: xxx Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known hosts. debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa debug1: Server accepts key: xxx debug1: Authentication succeeded (publickey). Authenticated to xxx ([192.168.1.120]:22). debug1: channel 0: new [client-session] debug1: Requesting debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype want_reply 0 debug1: tty_make_modes: no fd or tio debug1: Sending environment. debug1: Sending env LANG = en_GB.UTF-8 debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2] [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2) --- /etc/sudoers contains user ALL= NOPASSWD:/usr/bin/rsync ...which I have tried placing above (as is the default) and below lines beginning %admin and %sudo and the space in "ALL= NOPASSWD..." doesn't seem to make any difference I followed the instructions at https://www.digitalocean.com/community/tutorials/how-to-copy-files- with-rsync-over-ssh https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the- destination-machine ...which worked on 16.04, so I wonder if there may be a bug, although grateful for any other suggestions, as I am unsure how to debug/investigate further To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1831101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
Re: [Touch-packages] [Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...
On Mon, Jun 03, 2019 at 12:09:45AM -, BloodBlight wrote: > I am still seeing this error on Ubuntu 18.04 with netplan.io 0.97: > root@server:/etc/netplan# netplan apply > Traceback (most recent call last): > File "/usr/sbin/netplan", line 23, in > netplan.main() > File "/usr/share/netplan/netplan/cli/core.py", line 50, in main > self.run_command() > File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command > self.func() > File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run > self.run_command() > File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command > self.func() > File "/usr/share/netplan/netplan/cli/commands/apply.py", line 106, in > command_apply > stderr=subprocess.DEVNULL) > File "/usr/lib/python3.6/subprocess.py", line 291, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', > 'net_setup_link', '/sys/class/net/enp1s0f0:0']' returned non-zero exit > status 4. This is a bug report about QETH interfaces, which are an s390x-specific driver. Since you are seeing an issue on amd64, please file a separate bug report for this problem. -- 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/1756322 Title: 'netplan apply' fails when trying to activate another interface on another QETH device ... Status in netplan: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Won't Fix Status in systemd source package in Artful: Invalid Bug description: [Impact] Server users on s390x configuring qeth devices. [Test case] 1) Reconfigure an interface for a QETH device 2) Verify that 'netplan apply' completes successfully, without error. [Regression potential] This change has minimal potential for regression, and it only skip qeth-based devices from "replugging", which "disconnects" them by unbinding and rebinding the driver. Potential issues would be limited to failure to rename interfaces without a reboot, for configurations that depend on this (but it already would not have worked due to netplan apply failing to rebind the device). --- When trying to add another interface for a QETH device on a s390x system netplan apply fails: sudo netplan apply Cannot replug encc003: [Errno 19] No such device Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in command_apply stdout=fd, stderr=fd) File "/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4. It seems like rebinding of qeth devices is not allowed. With qeth devices, I guess one needs to "offline & online" them... Or like unbind a whole group of them, as there are three of them per interface. ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr total 0 drwxr-xr-x 5 root root0 Mar 16 02:06 .. -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent drwxr-xr-x 6 root root0 Mar 16 13:44 . -rw-r--r-- 1 root root 4096 Mar 16 13:44 online lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> ../../../bus/ccwgroup/drivers/qeth drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc --w--- 1 root root 4096 Mar 16 13:44 recover -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2 -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008 lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> .
[Touch-packages] [Bug 1831413] [NEW] alsa has to be reloaded afterlogin or else I don't get any sound
Public bug reported: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: New Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+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 1831393] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid comput
I tried what you suggested: " please go to `pavucontrol` [pulse audio volume control] and in the last Configuration tab, turn off your sound [profile]. Count to 1 (ie. a short delay) then return the profile setting to what it was before (ie. re-enable your sound to your default or favorite profile). Does sound return? (if it does, it'll be for the current session only; this won't be permanent)." and it did not work. I did this after resuming from suspend and no sound. Even after doing this I still had no sound. Only way I have found so far to get sound back is to shut off and then turn on, or to restart. On Sun, Jun 2, 2019 at 8:10 PM Chris Guiver wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > If you wake your system and it has no sound, can you please go to > `pavucontrol` [pulse audio volume control] and in the last Configuration > tab, turn off your sound [profile]. Count to 1 (ie. a short delay) then > return the profile setting to what it was before (ie. re-enable your > sound to your default or favorite profile). > > Does sound return? (if it does, it'll be for the current session only; > this won't be permanent). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831393 > > Title: > [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works > when I turn on the computer and login after the computer is off, but > if i close the lid computer suspends, and upon wakeup from suspend no > sound from built in speakers and built in microphone also does not > work. If shut down and restart then both internal speakers and > microphone will work. I have tried all available settings to fix > this, but as a regular user, I have not been able to fix problem. > Thank you for your help. > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > No sound from internal speakers and internal microphone does not work > upon wake from suspend. No available settings can make sound work, but > if computer is shut down and restarted then sound works until lid is > closed and computer enters suspend. Then upon wake up from suspend, > internal speakers and microphone will not work again until computer is > restarted. Asus E203M, Ubuntu 18.04 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: david 1479 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 2 19:13:57 2019 > InstallationDate: Installed on 2019-05-29 (4 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > PackageArchitecture: all > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gdm1082 F pulseaudio > david 1479 F pulseaudio > Symptom_Type: No sound at all > Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/26/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: E203MAS.302 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: E203MAS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrE203MAS.302:bd06/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook12_ASUSLaptopE203MAS_E203MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE203MAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: VivoBook > dmi.product.name: VivoBook 12_ASUS Laptop E203MAS_E203MA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831393/+subscriptions > -- 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/1831393 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid computer suspends, and upon wakeup from suspend no sound from built in speakers and built in microphone also
[Touch-packages] [Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...
I am still seeing this error on Ubuntu 18.04 with netplan.io 0.97: root@server:/etc/netplan# netplan apply Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 106, in command_apply stderr=subprocess.DEVNULL) File "/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/enp1s0f0:0']' returned non-zero exit status 4. root@MediaServer:/etc/netplan# apt search netplan.io ... netplan.io/bionic-updates,now 0.97-0ubuntu1~18.04.1 amd64 [installed,automatic] YAML network configuration abstraction for various backends ... -- 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/1756322 Title: 'netplan apply' fails when trying to activate another interface on another QETH device ... Status in netplan: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Won't Fix Status in systemd source package in Artful: Invalid Bug description: [Impact] Server users on s390x configuring qeth devices. [Test case] 1) Reconfigure an interface for a QETH device 2) Verify that 'netplan apply' completes successfully, without error. [Regression potential] This change has minimal potential for regression, and it only skip qeth-based devices from "replugging", which "disconnects" them by unbinding and rebinding the driver. Potential issues would be limited to failure to rename interfaces without a reboot, for configurations that depend on this (but it already would not have worked due to netplan apply failing to rebind the device). --- When trying to add another interface for a QETH device on a s390x system netplan apply fails: sudo netplan apply Cannot replug encc003: [Errno 19] No such device Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in command_apply stdout=fd, stderr=fd) File "/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4. It seems like rebinding of qeth devices is not allowed. With qeth devices, I guess one needs to "offline & online" them... Or like unbind a whole group of them, as there are three of them per interface. ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr total 0 drwxr-xr-x 5 root root0 Mar 16 02:06 .. -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent drwxr-xr-x 6 root root0 Mar 16 13:44 . -rw-r--r-- 1 root root 4096 Mar 16 13:44 online lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> ../../../bus/ccwgroup/drivers/qeth drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc --w--- 1 root root 4096 Mar 16 13:44 recover -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2 -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008 lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007 lrwxrwxrwx 1 root root0 Mar 16 13:44 c
[Touch-packages] [Bug 1831393] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid computer s
Thank you for taking the time to report this bug and helping to make Ubuntu better. If you wake your system and it has no sound, can you please go to `pavucontrol` [pulse audio volume control] and in the last Configuration tab, turn off your sound [profile]. Count to 1 (ie. a short delay) then return the profile setting to what it was before (ie. re-enable your sound to your default or favorite profile). Does sound return? (if it does, it'll be for the current session only; this won't be permanent). -- 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/1831393 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid computer suspends, and upon wakeup from suspend no sound from built in speakers and built in microphone also does not work. If shut down and restart then both internal speakers and microphone will work. I have tried all available settings to fix this, but as a regular user, I have not been able to fix problem. Thank you for your help. Status in alsa-driver package in Ubuntu: New Bug description: No sound from internal speakers and internal microphone does not work upon wake from suspend. No available settings can make sound work, but if computer is shut down and restarted then sound works until lid is closed and computer enters suspend. Then upon wake up from suspend, internal speakers and microphone will not work again until computer is restarted. Asus E203M, Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1479 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 19:13:57 2019 InstallationDate: Installed on 2019-05-29 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1082 F pulseaudio david 1479 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E203MAS.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E203MAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE203MAS.302:bd06/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook12_ASUSLaptopE203MAS_E203MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE203MAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 12_ASUS Laptop E203MAS_E203MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831393/+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 1831395] [NEW] Ubuntu doesn't support Wi-Fi on my laptop
Public bug reported: HP 15-bw075ax AMD® A12-9720p radeon r7, 12 compute cores 4c+8g × 4 llvmpipe (LLVM 8.0, 128 bits) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cron 3.0pl1-133ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 23:32:26 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190602) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1831395 Title: Ubuntu doesn't support Wi-Fi on my laptop Status in cron package in Ubuntu: New Bug description: HP 15-bw075ax AMD® A12-9720p radeon r7, 12 compute cores 4c+8g × 4 llvmpipe (LLVM 8.0, 128 bits) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cron 3.0pl1-133ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 23:32:26 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190602) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1831395/+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 1831393] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid computer
Public bug reported: No sound from internal speakers and internal microphone does not work upon wake from suspend. No available settings can make sound work, but if computer is shut down and restarted then sound works until lid is closed and computer enters suspend. Then upon wake up from suspend, internal speakers and microphone will not work again until computer is restarted. Asus E203M, Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1479 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 19:13:57 2019 InstallationDate: Installed on 2019-05-29 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1082 F pulseaudio david 1479 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E203MAS.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E203MAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE203MAS.302:bd06/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook12_ASUSLaptopE203MAS_E203MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE203MAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 12_ASUS Laptop E203MAS_E203MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1831393 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all; sound works when I turn on the computer and login after the computer is off, but if i close the lid computer suspends, and upon wakeup from suspend no sound from built in speakers and built in microphone also does not work. If shut down and restart then both internal speakers and microphone will work. I have tried all available settings to fix this, but as a regular user, I have not been able to fix problem. Thank you for your help. Status in alsa-driver package in Ubuntu: New Bug description: No sound from internal speakers and internal microphone does not work upon wake from suspend. No available settings can make sound work, but if computer is shut down and restarted then sound works until lid is closed and computer enters suspend. Then upon wake up from suspend, internal speakers and microphone will not work again until computer is restarted. Asus E203M, Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1479 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 19:13:57 2019 InstallationDate: Installed on 2019-05-29 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1082 F pulseaudio david 1479 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E203MAS.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E203MAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.a
[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME
** Changed in: base-files (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1598212 Title: /etc/os-release: Please specify VERSION_CODENAME Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in base-files package in Debian: Fix Released Bug description: [ SRU Justification ] UBUNTU_CODENAME was added by the snapd team, then proposed upstream in a more generic way. Upstream settled on VERSION_CODENAME, and we should include that as well, in case third party (or, indeed, future versions of our own) software decide to start looking for it. [ SRU Test Case ] Check diffs of both source package and installed os-release, make sure nothing's changed except VERSION_CODENAME, and that the value is correct. [ Regression Potential ] Nein. [ Original Report ] The os-release specification was updated in systemd > 230 to also include a VERSION_CODENAME parameter: https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8 Please replace the custom UBUNTU_CODENAME parameter by VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os- release to all stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1598212/+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 1537528] Re: byobu-config segfault with screen backend
** Changed in: slang2 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to slang2 in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in slang2 package in Ubuntu: Fix Released Status in slang2 source package in Xenial: Fix Released Status in slang2 package in Debian: Fix Released Bug description: [Impact] * Backport Debian fix for a crash in byobu due to libslang2 [Test Case] * byobu-screen * in there hit F9 or start byobu-config * without the fix this crashes [Regression Potential] * This is changing a libs implementation and $ reverse-depends src:slang2 -r xenial is quite a long list. OTOH this is somewhat ok as the change is in Debian and Ubuntu for more than three releases now and nothing around it seems to have totally broken. Never the less the biggest risk I see is something unexpected in one of the other libslang2 users. [Other Info] * n/a --- When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1537528/+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 1776475] Re: Unlocking existing session often requires several attempts.
## Thanks @vdrok > automatically lock the session - when the screensaver is activated > delay locking after screensaver for - 5 seconds > lock screen when system is going to sleep - checked Hmm, on my system the delay was set to something small (perhaps even 0). ## Thanks @mag3sh > From further investigation, I noticed that chrome-remote-desktop was starting Xsession and this was causing issues. I removed that package and it fixed the issue. I have no such thing as `chrome-remote-desktop` on my machine. ## Workaround (works for me) This workaround was suggested by the fact that logs say everyting is fine. Perhaps the session happens to be locked again before even displaying? * open xfce4-settings-manager, * click icon "power manager", * click tab "security", Set like this : * automatically lock the session - when the screensaver is activated * delay locking after screensaver for - **15** seconds * lock screen when system is going to sleep - checked Thank you for your attention. -- 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/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 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 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1831150] Re: only user.* extended attributes restored upon extraction
** Changed in: tar (Debian) Status: Unknown => New -- 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/1831150 Title: only user.* extended attributes restored upon extraction Status in GNU tar: Unknown Status in tar package in Ubuntu: New Status in tar package in Debian: New Bug description: The tar info page and upstream documentation indicate that when --xattr is used "all names are stored in the archive (or extracted, if using '--extract')", however when using --xattr with extract the security.capability extended attributes are not restored. If one also uses "--xattrs-include=*" then the security.capability extended attributes will be restored. [Test Case] mkdir orig restore touch orig/file_with_capability_and_user_xattr setcap cap_net_raw=p orig/file_with_capability_and_user_xattr (eoan-amd64)root@impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr # file: orig/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" I think tar's extract behavior should be changed to match that of create so that all names are actually extracted. To manage notifications about this bug go to: https://bugs.launchpad.net/tar/+bug/1831150/+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 1831388] [NEW] Wrong Scrolling Direction in Wi-Fi Networks Box
Public bug reported: To reproduce the bug: Natural scrolling is turned on for trackpad scrolling. 1. Go the arrow in the top right corner pointing down 2. Click "Wi-Fi Not Connected" to expand the wifi info 3. Click "Select Network" 4. Scroll in the box titled "Wi-Fi Networks" subtitled "Select a Network" using a trackpad Rather than scrolling up on trackpad causing the list of networks to scroll down it scrolls in the direction of motion on the trackpad, violating the selected natural scrolling setting Expected Behavior: Scroll Track-Pad Up Makes Screen Scroll Down & Scroll Track-Pad Down Makes Screen Scroll Up Current Behavior: Scroll Track-Pad Up Makes Screen Scroll Up & Scroll Track-Pad Down Makes Screen Scroll Down ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 16:49:35 2019 DistUpgraded: 2019-05-04 00:48:40,509 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.0.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-15-generic, x86_64: installed openrazer-driver, 2.5.0, 5.0.0-13-generic, x86_64: installed openrazer-driver, 2.5.0, 5.0.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] InstallationDate: Installed on 2018-12-28 (156 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Razer Blade ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=eca2d1f1-3f0e-4dd4-aa0c-3ae11c838d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-05-04 (29 days ago) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E76 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Dec 28 15:02:58 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.1-3ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1831388 Title: Wrong Scrolling Direction in Wi-Fi Networks Box Status in xorg package in Ubuntu: New Bug description: To reproduce the bug: Natural scrolling is turned on for trackpad scrolling. 1. Go the arrow in the top right corner pointing down 2. Click "Wi-Fi Not Connected" to expand the wifi info 3. Click "Select Network" 4. Scroll in the box titled "Wi-Fi Networks" subtitled "Select a Network" using a trackpad Rather than scrolling up on trackpad causing the list of networks to scroll down it scrolls in the direction of motion on the trackpad, violating the selected natural scrolling setting Expected Behavior: Scroll Track-Pad Up Makes Screen Scroll Down & Scroll Track-Pad Down Makes Screen Scroll Up Current Behavior: Scroll Track-Pad Up Makes Screen Scroll Up & Scroll Track-Pad Down Makes Screen Scroll Down ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignat
[Touch-packages] [Bug 1831339] Re: Backup Unbuntu ERROR undefined
add.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
** Attachment added: "prtscn window error description"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1831339/+attachment/5268408/+files/Captura%20de%20tela%20de%202019-06-02%2014-14-11.png
--
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/1831339
Title:
Backup Unbuntu ERROR undefined
Status in xorg package in Ubuntu:
New
Bug description:
Backup Unbuntu ERROR undefined
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sat Jun 1 14:59:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
InstallationDate: Installed on 2019-03-27 (66 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 24 21:29:22 2019
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1831339/+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 1831378] Re: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1831378 Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: My web pages freezes and then disappears and then it puts the box on my computer screen to enter my password to get back onto my web page. Been doing this for about 3 weeks now and getting frustrated. It also will not load any new updates. Please fix this. Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 2 10:39:20 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-10-23 (221 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831378/+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 1831378] Re: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831378 Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: My web pages freezes and then disappears and then it puts the box on my computer screen to enter my password to get back onto my web page. Been doing this for about 3 weeks now and getting frustrated. It also will not load any new updates. Please fix this. Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 2 10:39:20 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-10-23 (221 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831378/+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 1831378] [NEW] package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: My web pages freezes and then disappears and then it puts the box on my computer screen to enter my password to get back onto my web page. Been doing this for about 3 weeks now and getting frustrated. It also will not load any new updates. Please fix this. Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 2 10:39:20 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-10-23 (221 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1831378 Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: My web pages freezes and then disappears and then it puts the box on my computer screen to enter my password to get back onto my web page. Been doing this for about 3 weeks now and getting frustrated. It also will not load any new updates. Please fix this. Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 2 10:39:20 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-10-23 (221 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-50-generic 4.15.0-50.54~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831378/+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 1786495] Re: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all
I have the same problem on Ubuntu 19.10. The fix of nic30 doesn't work for me. I have a Dell Precision M2800 -- 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/1786495 Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am head no sound from my headphone jack. Laptop speaker work fine. Tried 2 different headphones and still no sound. pavucontrol can see my headphone and I see the sound bar move but no sound comes out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hhernandez 2083 F...m pulseaudio /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio CurrentDesktop: MATE Date: Fri Aug 10 07:59:09 2018 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1786495/+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 1713017] Re: Enable MIDI support
I tried the latest version (5.50) from https://launchpad.net/~bluetooth/+archive/ubuntu/bluez without success. Is bluetooth midi completely disabled on Ubuntu? -- 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/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+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 1831351] Re: Please provide option to continue bug report from different computer
I've added myself to this bug report. I do some QA-testing of Ubuntu (flavors) using various old boxes, some of which have useless/tiny keyboards, plus there are rare occasions where the gui becomes unreadable (the reason for the bug-report) I've learnt to work around it for the most part (eg. https://bugs.launchpad.net/ubuntu/+source/lxqt- panel/+bug/1809205/comments/0) but it'd be nice to not have to. -- 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/1831351 Title: Please provide option to continue bug report from different computer Status in apport package in Ubuntu: Confirmed Bug description: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu-bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831351/+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 1831351] Re: Please provide option to continue bug report from different computer
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/1831351 Title: Please provide option to continue bug report from different computer Status in apport package in Ubuntu: Confirmed Bug description: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu-bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831351/+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 1825963] Re: Abysmal memory leak on tracker-extract
Thanks for providing the 'minimap_area.dds' file. How many other files are there in the same directory? And what is the total size of all of these .dds files? Running `tracker extract` on the given gives the following message: Call to gst_discoverer_discover_uri(file:///.../minimap_area.dds) failed: Internal data stream error. file:///.../minimap_area.dds: No metadata or extractor modules found to handle this file I think this is pretty normal, that GStreamer's type detection code sometimes reports an error when it fails to detect the type of a file. Running with `env GST_DEBUG=2` doesn't show any unexpected messages. Running under `valgrind` doesn't show any dramatic memory leak. It's possible that this code path blows up on some larger files that are in the same directory, though. Could you run `tracker extract *` inside the problematic directory and see what happens? (This will run in the foreground so you should be able to CTRL+c if it starts to eat all your RAM ... which it hopefully will do so we can narrow down the problem :). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
I do not know how priorities in bug handling are set, but I do wonder what may be the reason to not handle this rather common (30 dupes) critical (crash) bug on a 'main' package for the past three years - could someone explain this to me? Thanks in advance. -- 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/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in Apport: New Status in GTK+: Expired Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1552577/+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
