[Desktop-packages] [Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
I have this error when I try to access an email in Evolution, but at no other time: (evolution:5165): GLib-GObject-CRITICAL **: 09:04:04.308: g_object_ref: assertion 'G_IS_OBJECT (object)' failed I am running Ubuntu 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup Status in gnome-session: New Status in gnome-session package in Ubuntu: Confirmed Bug description: I submitted this question a week but did not receive an answer or advice to solving them. https://answers.launchpad.net/ubuntu/+source /gnome-session/+question/293479 These failures are still plaguing my syslog every time I activate Nautilus. Appreciate help to resolve these failures. Earlier question After a recent updating, I notice these failures in the systemlogs. May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: (zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed May 9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed The last three failures appears whenever I activate nautilus. Nautilus will appear and work as usual. How can I resolve these failure notices? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1582496/+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 1597870] [NEW] [USB-Audio - VX2, playback] Playback problem
Public bug reported: I'm plagued by a usb problem. I have an external soundcard--a Topping VX2--that connects via usb. Under Ubuntu 15.04 and 15.10, the device worked as expected. But under Ubuntu 16.04, it causes severe problems: 1. When plugged in, the device often interferes with boot. Unplug the device, and Ubuntu boots as expected. 2. If left plugged in while booting/rebooting, upon successful login, all desktop icons and other theme-based decoration is reverted to the default Ubuntu settings. 3. If plugged in after successful boot and login, the device seems to nuke Pulseaudio: it wipes out *all* devices in "Sound Settings," giving the impression that there are no sound cards in the machine. Remove the usb cord, and all is well--my devices all return. 4. During a reboot with the device plugged in, Ubuntu seems to hang and gives -110 USB errors. * Thinking I had a defective unit, I returned this device for another one. However, the new device causes the exact same problems. * The VX2 uses Via Technologies VT 1620A USB audio controller. A portion from my kernel log: [Code] kernel: [ 318.180047] usb 3-12: new full-speed USB device number 10 using xhci_hcd Jun 28 13:51:11 Rufus kernel: [ 318.408031] usb 3-12: New USB device found, idVendor=040d, idProduct=3400 Jun 28 13:51:11 Rufus kernel: [ 318.408036] usb 3-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 28 13:51:11 Rufus kernel: [ 318.408039] usb 3-12: Product: VX2 Jun 28 13:51:11 Rufus kernel: [ 318.408041] usb 3-12: Manufacturer: TOPPING Jun 28 13:51:12 Rufus kernel: [ 318.955602] input: TOPPING VX2 as /devices/pci:00/:00:14.0/usb3/3-12/3-12:1.2/0003:040D:3400.000A/input/input23 Jun 28 13:51:12 Rufus kernel: [ 319.008253] hid-generic 0003:040D:3400.000A: input,hidraw7: USB HID v1.00 Device [TOPPING VX2] on usb-:00:14.0-12/input2 Jun 28 13:51:12 Rufus mtp-probe: checking bus 3, device 10: "/sys/devices/pci:00/:00:14.0/usb3/3-12" Jun 28 13:51:12 Rufus mtp-probe: bus: 3, device: 10 was not an MTP device Jun 28 13:51:21 Rufus org.gtk.vfs.Daemon[1944]: ** (gvfsd:1995): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection timed out Jun 28 13:51:21 Rufus org.gtk.vfs.Daemon[1944]: ** (process:2686): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted Jun 28 13:51:22 Rufus kernel: [ 329.060630] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:22 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 1096 events suppressed Jun 28 13:51:22 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:27 Rufus kernel: [ 334.060518] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:23 Rufus pulseaudio[2191]: message repeated 10 times: [ [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally] Jun 28 13:51:27 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 114 events suppressed Jun 28 13:51:27 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:32 Rufus kernel: [ 339.060521] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:28 Rufus pulseaudio[2191]: message repeated 10 times: [ [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally] Jun 28 13:51:32 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 114 events suppressed Jun 28 13:51:32 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:37 Rufus kernel: [ 344.060559] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:33 Rufus pulseaudio[2191]: message repeated 10 times: [ [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally] Jun 28 13:51:37 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 114 events suppressed Jun 28 13:51:37 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:42 Rufus kernel: [ 349.060535] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:38 Rufus pulseaudio[2191]: message repeated 10 times: [ [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally] Jun 28 13:51:42 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 115 events suppressed Jun 28 13:51:42 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:47 Rufus kernel: [ 354.060528] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:43 Rufus pulseaudio[2191]: message repeated 10 times: [ [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally] Jun 28 13:51:47 Rufus pulseaudio[2191]: [alsa-source-USB Audio] ratelimit.c: 115 events suppressed Jun 28 13:51:47 Rufus pulseaudio[2191]: [alsa-source-USB Audio] asyncq.c: q overrun, queuing locally Jun 28 13:51:52 Rufus kernel: [ 359.060519] usb 3-12: 1:1: usb_set_interface failed (-110) Jun 28 13:51:48 Ruf
[Desktop-packages] [Bug 1560181] [NEW] [USB-Audio - VX2, playback] Pulseaudio fails to detect card
Public bug reported: I have an external sound card--A Topping VX2. When plugged in to USB, the device seems to keep Ubuntu from booting properly. It hangs until I remove the USB cord from the device, then Ubuntu boots normally. Once booted, the device can be recognized by Ubuntu, but then seems to nuke PulseAudio, leaving no devices in the Sound Settings. Yes, I have checked this behavior against two Topping VX2 devices, which have identical results. Yes, I have switched out USB cords to test for a bad cord. The VX2 uses Via Technologies VT 1620A USB audio controller. I suspect that this may be the issue. Is this currently supported? Is there a working driver for this? THanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 15:27:54 2016 InstallationDate: Installed on 2016-03-15 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - C-Media USB Audio Device Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2101:bd11/26/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1560181 Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have an external sound card--A Topping VX2. When plugged in to USB, the device seems to keep Ubuntu from booting properly. It hangs until I remove the USB cord from the device, then Ubuntu boots normally. Once booted, the device can be recognized by Ubuntu, but then seems to nuke PulseAudio, leaving no devices in the Sound Settings. Yes, I have checked this behavior against two Topping VX2 devices, which have identical results. Yes, I have switched out USB cords to test for a bad cord. The VX2 uses Via Technologies VT 1620A USB audio controller. I suspect that this may be the issue. Is this currently supported? Is there a working driver for this? THanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 15:27:54 2016 InstallationDate: Installed on 2016-03-15 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - C-Media USB Audio Device Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2101:bd11/26/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net
[Desktop-packages] [Bug 1560181] Re: [USB-Audio - VX2, playback] Pulseaudio fails to detect card
I'm attaching a PulseAudio log here. The device that causes the issue is the Topping VX2. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1560181/+attachment/4618083/+files/pulseverbose.log -- 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/1560181 Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have an external sound card--A Topping VX2. When plugged in to USB, the device seems to keep Ubuntu from booting properly. It hangs until I remove the USB cord from the device, then Ubuntu boots normally. Once booted, the device can be recognized by Ubuntu, but then seems to nuke PulseAudio, leaving no devices in the Sound Settings. Yes, I have checked this behavior against two Topping VX2 devices, which have identical results. Yes, I have switched out USB cords to test for a bad cord. The VX2 uses Via Technologies VT 1620A USB audio controller. I suspect that this may be the issue. Is this currently supported? Is there a working driver for this? THanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 15:27:54 2016 InstallationDate: Installed on 2016-03-15 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - C-Media USB Audio Device Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2101:bd11/26/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1560181/+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 1786607] [NEW] gnome-keyring caches PGP password eternally
Public bug reported: I've been using the program `Pass` to manage my passwords, which uses a PGP key that I created for this purpose. I began noticing that after my first use of the passphrase gnome-keyring would cache the passphrase and no longer request it. This is a security issue as anyone with access to my machine can gain access to all of my passwords. I assumed the settings could be tweaked, so I used `dconf-editor` to edit the `gpg-cache-method` file to use `timeout` instead of the default setting. I also changed the `gpg-cache-ttl` to 1 second from the default, which was 300 I believe. I then restarted the keyring with `$ gnome-keyring-daemon -r`. This successfully reset the keyring and I was prompted for my password. However, it only worked once. After entering the password, gnome-keyring cached my password and this survives logging out or restarting the computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 11 07:38:49 2018 InstallationDate: Installed on 2018-04-26 (106 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic gnome-keyring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1786607 Title: gnome-keyring caches PGP password eternally Status in gnome-keyring package in Ubuntu: New Bug description: I've been using the program `Pass` to manage my passwords, which uses a PGP key that I created for this purpose. I began noticing that after my first use of the passphrase gnome-keyring would cache the passphrase and no longer request it. This is a security issue as anyone with access to my machine can gain access to all of my passwords. I assumed the settings could be tweaked, so I used `dconf-editor` to edit the `gpg-cache-method` file to use `timeout` instead of the default setting. I also changed the `gpg-cache-ttl` to 1 second from the default, which was 300 I believe. I then restarted the keyring with `$ gnome-keyring-daemon -r`. This successfully reset the keyring and I was prompted for my password. However, it only worked once. After entering the password, gnome-keyring cached my password and this survives logging out or restarting the computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 11 07:38:49 2018 InstallationDate: Installed on 2018-04-26 (106 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1786607/+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
