[Desktop-packages] [Bug 1850085] Re: right-click 'Format' removable drive not opening dialog
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1850085 Title: right-click 'Format' removable drive not opening dialog Status in nautilus package in Ubuntu: Expired Bug description: right clicking on removable media in nautilus, the format option does nothing. All other right click options work as expected. Formatting the drive via the disks utility works as expected. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 17:59:20 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' InstallationDate: Installed on 2019-10-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850432] Re: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1850432 Title: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor Status in xorg-server package in Ubuntu: Expired Bug description: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 20:09:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0591] InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0WF4PW dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1850432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857787] [NEW] Bluetooth cannot be turned on once turned off
Public bug reported: Given that Bluetooth is disabled, And I want to enable the bluetooth, When I open the Bluetooth tab in Settings And I press the button, Then the button background turns green but the handle does not move (State 1- Bug 1) Being at State 1, When I move to another tab, And I come back to the "Bluetooth" tab Then the Bluetooth is enabled and I can choose a bluetooth device. (State 2) Being at State 2, When I disable the Bluetooth And I start the process from the beginning Then I cannot re-enable the Bluetooth Ubuntu version: Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-bluetooth 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 29 01:12:53 2019 InstallationDate: Installed on 2019-06-22 (189 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to eoan on 2019-11-01 (57 days ago) ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1857787 Title: Bluetooth cannot be turned on once turned off Status in gnome-bluetooth package in Ubuntu: New Bug description: Given that Bluetooth is disabled, And I want to enable the bluetooth, When I open the Bluetooth tab in Settings And I press the button, Then the button background turns green but the handle does not move (State 1- Bug 1) Being at State 1, When I move to another tab, And I come back to the "Bluetooth" tab Then the Bluetooth is enabled and I can choose a bluetooth device. (State 2) Being at State 2, When I disable the Bluetooth And I start the process from the beginning Then I cannot re-enable the Bluetooth Ubuntu version: Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-bluetooth 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 29 01:12:53 2019 InstallationDate: Installed on 2019-06-22 (189 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to eoan on 2019-11-01 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1857787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Sadly not. I purged, installed, and it failed as before. I had to redo the sed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I can confirm that, in some cases renaming files with ( and ) characters can help to make mtp usable, but... this is not whole story. I have a lot files with parenthesis (or other special characters) in their name. The file operations were hanging only when I tried to do something in a directory which contained photos (.jpg files) - primarily in DCIM/Camera and in a directory where I've copied these photos. There are many files in my mp3 collection with ( ) characters in their name, including some jpegs (album covers) and these directories are usable via mtp. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
If you redid the sed from #25, that caused the problem. You need to reinstall and let it run under Python 2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857736] Re: nautilus crashed with SIGABRT
https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ** Description changed: I do not know, what happened. + + --- + + https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () - () - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () + () + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1324 https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1324 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857736 Title: nautilus crashed with SIGABRT Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: I do not know, what happened. --- https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
It was fixed. My system later updated to version 1531 as above, and this then failed in the same way as before. I had to apply your sed patch to make it work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 656675] Re: Two saned processes and "bind failed: Address already in use"
OK, I think this is not a (huge) bug .. looking at saned code, it tries to bind v6 and v4 sockets separately. If /proc/sys/net/ipv6/bindv6only isn't set, binding v6 will also bind v4, making the later explicit v4 bind fail. The second process is probably the one responsible for avahi advertisements. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/656675 Title: Two saned processes and "bind failed: Address already in use" Status in sane-backends package in Ubuntu: Confirmed Bug description: Ubuntu 10.04 (Lucid Lynx) i386 Whenever saned starts it ends up with two processes running and the following log entries: saned[1470]: bailing out, waiting for children... saned[1470]: bail_out: all children exited saned[4387]: saned (AF-indep+IPv6) from sane-backends 1.0.20 starting up saned[4387]: do_bindings: [0] bind failed: Address already in use saned[4388]: Now daemonized saned[4388]: Dropped privileges to uid 118 gid 122 This occurs with both Inetd and daemon configurations. When it's stopped I can see that no other saned processes are running but when started two always show up along with the error. This is mostly a cosmetic problem as network scanning through saned still functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I've tried it on Ubuntu 18.04.3 with a Galaxy A70, and it was extremely slow in every directory which contained more than 50-100 files. (a simple ls command needed about 2 minutes in a directory with 110 files) But it seems to be a general bug, not OS or distribution dependent, because I've tried it on the latest Fedora with a newer gvfs, but the result was the same: very, very slow... It is possibly an Android bug. (?Is it possible?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I confirm Solution #58 (add `ahci.mobile_lpm_policy=0` to boot options works great). Thanks @prasanth-s-cmi! It fixed freezes and "didn't wake up" problem on Dell Latitute 7390 2018 year manufactured. dev@dev-L-7390:~$ inxi -Fz System:Host: dev-L-7390 Kernel: 5.0.0-37-generic x86_64 bits: 64 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.3 LTS Machine: Device: laptop System: Dell product: Latitude 7390 serial: N/A Mobo: Dell model: 09386V v: A00 serial: N/A UEFI: Dell v: 1.13.1 date: 11/08/2019 BatteryBAT0: charge: 17.8 Wh 30.3% condition: 58.7/60.0 Wh (98%) CPU: Quad core Intel Core i7-8650U (-MT-MCP-) cache: 8192 KB clock speeds: max: 4200 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz Graphics: Card: Intel UHD Graphics 620 Display Server: x11 (X.Org 1.20.4 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) version: 4.5 Mesa 19.0.8 Audio: Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel Sound: ALSA v: k5.0.0-37-generic Network: Card-1: Intel Ethernet Connection (4) I219-LM driver: e1000e IF: enp0s31f6 state: down mac: Card-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp2s0 state: up mac: Drives:HDD Total Size: 512.1GB (4.2% used) ID-1: /dev/sda model: TOSHIBA_KSG60ZMV size: 512.1GB Partition: ID-1: / size: 42G used: 4.8G (13%) fs: ext4 dev: /dev/sda5 ID-2: /home size: 309G used: 956M (1%) fs: ext4 dev: /dev/sda7 ID-3: swap-1 size: 16.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 44.0C mobo: N/A Fan Speeds (in rpm): cpu: 0 Info: Processes: 293 Uptime: 8:54 Memory: 1873.3/15916.4MB Client: Shell (bash) inxi: 2.3.56 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about
[Desktop-packages] [Bug 1857764] [NEW] Brightness conrol
Public bug reported: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.307:bd03/14/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1857764 Title: Brightness conrol Status in xorg package in Ubuntu: New Bug description: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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:
[Desktop-packages] [Bug 1857765] [NEW] Brightness conrol
Public bug reported: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.307:bd03/14/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1857765 Title: Brightness conrol Status in xorg package in Ubuntu: New Bug description: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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:
[Desktop-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash
Another update, Ive seen this have a video/audio running, start a new terminal, type in sudo then tab to autocomlpete, and the audio/video will stop. Now without closing the terminal, when you tab to autocomplete again audio/video keep on playing as expected. Close the terminal, open new terminal and try steps again and audio/video will stop for a second -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1852018 Title: Audio Stops Playing Briefly When Emptying Trash Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am running Ubuntu 19.10 and encountered this issue. I had a podcast playing in the background on Firefox v. 70.0.1 and I was deleting some files. I then proceeded to empty the trash and saw that the audio stops briefly till the "Empty all items from Trash?" prompt shows up. I was able to duplicate this many times and it even occurred with audio on Chrome. The expected way for things to work would be the audio keeps on playing, if I just empty the trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1852018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 656675] Re: Two saned processes and "bind failed: Address already in use"
Still seeing this in 18.04! Gave up, disabled /etc/init.d/saned, and used the systemd socket service - but this doesn't seem to advertise the saned server. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/656675 Title: Two saned processes and "bind failed: Address already in use" Status in sane-backends package in Ubuntu: Confirmed Bug description: Ubuntu 10.04 (Lucid Lynx) i386 Whenever saned starts it ends up with two processes running and the following log entries: saned[1470]: bailing out, waiting for children... saned[1470]: bail_out: all children exited saned[4387]: saned (AF-indep+IPv6) from sane-backends 1.0.20 starting up saned[4387]: do_bindings: [0] bind failed: Address already in use saned[4388]: Now daemonized saned[4388]: Dropped privileges to uid 118 gid 122 This occurs with both Inetd and daemon configurations. When it's stopped I can see that no other saned processes are running but when started two always show up along with the error. This is mostly a cosmetic problem as network scanning through saned still functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Which way does it fail? I thought we had that fixed for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857759] [NEW] network-manager DNS fail after upgrade with openvpn connection
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 09:42:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-23 (158 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) After the upgrade of network-manager with OpenVPN fails to configure DNS settings. - List network-manager versions # apt list -a network-manager network-manager/bionic-updates,now 1.10.6-2ubuntu1.2 amd64 [installed] network-manager/bionic-security 1.10.6-2ubuntu1.1 amd64 network-manager/bionic 1.10.6-2ubuntu1 amd64 - Start the connection # nmcli connection up id VPN Connection successfully activated - Show connection status # systemd-resolved --status Link 20 (tun1) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no No DNS settings! -- - Downgrade network-manager to previous version # apt install network-manager=1.10.6-2ubuntu1.1 - List network-manager versions # apt list -a network-manager network-manager/bionic-updates 1.10.6-2ubuntu1.2 amd64 [upgradable from: 1.10.6-2ubuntu1.1] network-manager/bionic-security,now 1.10.6-2ubuntu1.1 amd64 [installed,upgradable to: 1.10.6-2ubuntu1.2] network-manager/bionic 1.10.6-2ubuntu1 amd64 - Restart network-manager # systemctl restart NetworkManager - Start the connection # nmcli connection up id VPN Connection successfully activated - Show connection status # systemd-resolved --status Link 21 (tun1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.0.0.129 DNS settings OK! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316040/+files/CRDA.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316041/+files/Dependencies.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316042/+files/IpAddr.txt ** Attachment removed: "IpRoute.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316043/+files/IpRoute.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316044/+files/IwConfig.txt ** Attachment removed: "NetDevice.br-47654fac49d5.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316045/+files/NetDevice.br-47654fac49d5.txt ** Attachment removed: "NetDevice.br-51b0cd0cb86a.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316046/+files/NetDevice.br-51b0cd0cb86a.txt ** Attachment removed: "NetDevice.br-6e6e737a82ad.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316047/+files/NetDevice.br-6e6e737a82ad.txt ** Attachment removed: "NetDevice.br-d4a2717d1ce6.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316048/+files/NetDevice.br-d4a2717d1ce6.txt ** Attachment removed: "NetDevice.br-ffd4067857d5.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316049/+files/NetDevice.br-ffd4067857d5.txt ** Attachment removed: "nmcli-dev.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316060/+files/nmcli-dev.txt ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316059/+files/nmcli-con.txt ** Attachment removed: "NetDevice.docker0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316050/+files/NetDevice.docker0.txt ** Attachment removed: "NetDevice.eth0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316051/+files/NetDevice.eth0.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316058/+files/RfKill.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857759/+attachment/5316052/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.wlan0.txt"
[Desktop-packages] [Bug 1789244] Re: Sound driver does not appear to show [Intel HDMI/DP LPE Audio]
Hello, I also have the Thomson NEO10 netbook (Atom-z8350) and struggled to find a Linux where sound would work, after getting everything to work fairly well. I eventually found that sound works in Ubuntu 19.10 with Kernel 5.3, anything lower (19.04, Mint 19.3) had the issue. It seems kernel 5.3 has made some enhancements to sound compatibility. :D With only 2gb ram and running live, Ubuntu would freeze after about 5 minutes though so I ended up using Lubuntu 19.10 instead, which can still freeze if you have too many firefox windows open but is much more manageable. Neither detected my linux-swap partition automatically though so you might want to set that up somehow or make a swapfile either way (or not run the iso live like I'm doing) if you have the 2gb ram version of the NEO10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1789244 Title: Sound driver does not appear to show [Intel HDMI/DP LPE Audio] Status in pulseaudio package in Ubuntu: New Bug description: Using my Thomson Neo 10, which is a French made notebook with a UK qwerty keyboard, however it appears all support for this notebook is that all support is in other languages including french and it is not clear what the actual drivers are in order to attempt to find a way of installing it myself. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Aug 27 17:24:50 2018 InstallationDate: Installed on 2018-08-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: E.C116CM.Thomson.A01 dmi.bios.version: 5.11 dmi.board.asset.tag: WS_reserve dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: WS_reserve dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: UK-NEO10A-2WH32 dmi.product.version: WS_reserve dmi.sys.vendor: Thomson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754321] Re: chromium-browser: please drop dependency on libgnome-keyring
>From source code of Chromium:
components/os_crypt/keyring_util_linux.h:8:// libgnome-keyring has been
deprecated in favor of libsecret.
components/os_crypt/keyring_util_linux.h:18:#include
components/os_crypt/keyring_util_linux.cc:72: void* handle =
dlopen("libgnome-keyring.so.0", RTLD_NOW | RTLD_GLOBAL);
components/os_crypt/keyring_util_linux.cc:77:LOG(WARNING) << "Could not
load libgnome-keyring.so.0: " << dlerror();
components/os_crypt/key_storage_util_linux.cc:40: if (type == "gnome-keyring")
components/os_crypt/features.gni:8: # Whether to use libgnome-keyring
(deprecated by libsecret).
components/os_crypt/key_storage_keyring.cc:58:VLOG(1) << "OSCrypt failed to
use gnome-keyring";
components/os_crypt/key_storage_keyring.cc:75:VLOG(1) << "Failed to store
generated password to gnome-keyring";
components/os_crypt/key_storage_config_linux.h:29: // A runner on the main
thread for gnome-keyring to be called from.
components/os_crypt/BUILD.gn:12: # Gnome-keyring is normally dynamically
loaded. The gnome_keyring config
components/os_crypt/BUILD.gn:15:packages = [ "gnome-keyring-1" ]
components/os_crypt/BUILD.gn:20: # If you want to link gnome-keyring directly
(use only for unit tests)
components/os_crypt/BUILD.gn:22: # bit slow, so prefer not to run it again. In
practice, gnome-keyring's libs
components/os_crypt/BUILD.gn:29:libs = [ "gnome-keyring" ]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1754321
Title:
chromium-browser: please drop dependency on libgnome-keyring
Status in chromium-browser package in Ubuntu:
Confirmed
Status in chromium-browser package in Debian:
Fix Released
Bug description:
Please drop the build-dependency on libgnome-keyring. It looks to me
like it's not used.
The corresponding change was made in Debian last year:
https://anonscm.debian.org/git/pkg-chromium/pkg-chromium.git/commit/?id=6513e334
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754321/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
With the latest update duplicity still fails. Version 0.8.09-0ubuntu0ppa1531-ubuntu19.10.1 (eoan). I had to redo the sed from #25. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754321] Re: chromium-browser: please drop dependency on libgnome-keyring
+1, it would be nice because I don't want to use a snap version of Chromium on Ubuntu 19.10 and 20.04 and try to rebuild Chromium from Bionic in eoan and focal in ppa:mikhailnov/utils, I will try to build libgnome-keyring to avoid changing chromium-browser packaging manually for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1754321 Title: chromium-browser: please drop dependency on libgnome-keyring Status in chromium-browser package in Ubuntu: Confirmed Status in chromium-browser package in Debian: Fix Released Bug description: Please drop the build-dependency on libgnome-keyring. It looks to me like it's not used. The corresponding change was made in Debian last year: https://anonscm.debian.org/git/pkg-chromium/pkg-chromium.git/commit/?id=6513e334 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Release 'eoan-proposed' for 'pulseaudio' was not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857749] Re: HDMI output always selected on reboot
** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+attachment/5315999/+files/default.pa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857749 Title: HDMI output always selected on reboot Status in pulseaudio package in Ubuntu: New Bug description: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock 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.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857749] [NEW] HDMI output always selected on reboot
Public bug reported: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock 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.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857749 Title: HDMI output always selected on reboot Status in pulseaudio package in Ubuntu: New Bug description: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock 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.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
