[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader
The issue of these speech-dispatcher processes spawning for some unknown reason and distorting sound (as mentioned above a few users) is still present in 22.04 for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+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 1726124] Re: DNS domain search paths not updated when VPN started
I hope something can be worked out before this lands in the next LTS- release. This breaks one of the most common uses of a VPN (remote work). Right now a workaround is using this script after connecting to a VPN- server: https://github.com/jonathanio/update-systemd-resolved It calls systemd-resolved via DBus to add the proper settings after the OpenVPN connection is established. Of course this means abandoning NetworkManager for use with OpenVPN, because there is also no way to specify --up and --down parameters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Desktop-packages] [Bug 975749] Re: writer mail merge cannot select address book
*** This bug is a duplicate of bug 986205 *** https://bugs.launchpad.net/bugs/986205 This is still an issue with Ubuntu 16.04. Without the full LibreOffice package Writer will crash without any message when you try to add a database for a mail merge. Can someone remove the duplicate tag? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/975749 Title: writer mail merge cannot select address book Status in libreoffice package in Ubuntu: Confirmed Bug description: When starting the Mail Merge Wizard in LibreOffice Writer. I get to stage 3 (select address list). When I click the Select Address List button I presented with the following error: Loading Component Library Failed: file:///usr/lib/libreoffice/program/.../program/libdbalo.so I was hoping to be able t oselect an address list, but it never happened. Version Details: LibreOffice 3.5.1.2 Build ID: 350m1(Build:102) OS: Ubuntu 12.04 beta 2 x64 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 18:20:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-04-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/975749/+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 1504792] Re: nm applet displays inaccurate notification when user disconnects from VPN
I am seeing this behaviour since the 'Disconnect from VPN' menu entry was removed. Was that removal intentionally? It used to be possible to click that (which disconnected the VPN connection without this 'Connection Failed' message). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1504792 Title: nm applet displays inaccurate notification when user disconnects from VPN Status in network-manager-applet package in Ubuntu: Confirmed Bug description: When the user voluntarily disconnects from a vpn connection, network manager displays the error message "VPN Connection Failed." See the attached screenshot. However, since a disconnection in this case is a success, not a failure, something more neutral like "Successfully disconnected" would be more appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1504792/+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 1631095] Re: pushed dns servers not being used
This issue is now present in 16.04 as well. As Matthew mentions, the first time you connect to a VPN with OpenVPN DNS works, the second time it doesn't. In case anyone stumbles upon this issue, this workaround (restarting dnsmasq) makes name resolution work again for a single VPN session: sudo pkill dnsmasq You can execute it either before or after the VPN connection is made. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1631095 Title: pushed dns servers not being used Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: After the upgrade from yenial to yakkety, the internal DNS servers (pushed by the openvpn server) are not being used by dnsmasq. Symptom: I connect via openvpn (called from network manager), the connection is established successfully but INTERNAL hostnames cannot be resolved. The system itself is using dnsmasq. I then have to kill the running dnsmasq instance. After it's been (automagically) restarted, internal DNS names can be resolved. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager-openvpn 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Oct 6 20:06:33 2016 InstallationDate: Installed on 2014-02-07 (972 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to yakkety on 2016-10-01 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1631095/+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 1625790] [NEW] Cannot enter character via shift-ctrl-u shortcut
Public bug reported: In most Gnome applications I can use shift-ctrl-u to directly enter a character via its Unicode codepoint. So, for example, to enter the character € via this method, one does: shift-ctrl-u 2 0 A C enter This works in gedit and gnome-terminal today. I use this often in gucharmap when dealing with a character I don't recognize, and can't easily directly copy from the source. Since updating to Ubuntu 16.04, the gucharmap version shipped with Ubuntu has started to ignore the shift-ctrl-u shortcut in the search text field. Upstream reports that this appears to be a Ubuntu specific issue: https://bugzilla.gnome.org/show_bug.cgi?id=769327 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gucharmap 1:3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 20 21:55:13 2016 InstallationDate: Installed on 2014-09-16 (735 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gucharmap UpgradeStatus: Upgraded to xenial on 2016-05-26 (117 days ago) ** Affects: gucharmap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1625790 Title: Cannot enter character via shift-ctrl-u shortcut Status in gucharmap package in Ubuntu: New Bug description: In most Gnome applications I can use shift-ctrl-u to directly enter a character via its Unicode codepoint. So, for example, to enter the character € via this method, one does: shift-ctrl-u 2 0 A C enter This works in gedit and gnome-terminal today. I use this often in gucharmap when dealing with a character I don't recognize, and can't easily directly copy from the source. Since updating to Ubuntu 16.04, the gucharmap version shipped with Ubuntu has started to ignore the shift-ctrl-u shortcut in the search text field. Upstream reports that this appears to be a Ubuntu specific issue: https://bugzilla.gnome.org/show_bug.cgi?id=769327 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gucharmap 1:3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 20 21:55:13 2016 InstallationDate: Installed on 2014-09-16 (735 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gucharmap UpgradeStatus: Upgraded to xenial on 2016-05-26 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1625790/+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 572628] Re: "Liyama" spelling error
The patch I sent was ultimately accepted upstream. 'Liyama' should now be spelled as 'Iiyama' on system's using this database. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/572628 Title: "Liyama" spelling error Status in gnome-desktop: Invalid Status in gnome-desktop3 package in Ubuntu: Invalid Status in hwdata package in Ubuntu: New Bug description: Binary package hint: gnome-control-center Lucid final release amd64 alternate install CD iiyama ProLite H511S LCD monitor gnome-control-center1:2.30.0-0ubuntu4 Preferences -> Monitors brings up a green box containing the text "Liyama North America 20". It should be iiyama, not Liyama. (And FWIW the monitor was purchased in England.) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/572628/+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 1168582] Re: Google talk Requires Authorization after suspend/resume
This problem persists in 14.04 for me as well. One of the two Google accounts I add will fail even during the same session with the authorisation required error. I have stopped using Empathy and the Online Accounts configurator completely due to this bug, although I give it a go whenever I move to a newer version of Ubuntu to see if the bug persists. Oddly enough, other messaging applications seem fine with my Google accounts, and no authorisation of any kind is needed beyond my credentials. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk Requires Authorization after suspend/resume Status in “empathy” package in Ubuntu: Confirmed Bug description: Fresh install of raring with all updates. After suspend/resuming my laptop, the google talk account refuses to reconnect, and emparthy says it requires authorization, if I click the button next to requires authorzation it just brings me to UOA and nothing happens. toggling the gtalk account on and off doesn't help, it just requires authorization again. only way to get it back is to reboot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 12 20:14:00 2013 InstallationDate: Installed on 2013-04-12 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130411) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+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 1168582] Re: Google talk Requires Authorization after suspend/resume
I have two Google accounts as well, could that be a relevant factor? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk Requires Authorization after suspend/resume Status in “empathy” package in Ubuntu: Confirmed Bug description: Fresh install of raring with all updates. After suspend/resuming my laptop, the google talk account refuses to reconnect, and emparthy says it requires authorization, if I click the button next to requires authorzation it just brings me to UOA and nothing happens. toggling the gtalk account on and off doesn't help, it just requires authorization again. only way to get it back is to reboot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 12 20:14:00 2013 InstallationDate: Installed on 2013-04-12 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130411) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+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 572628] Re: Liyama spelling error
In 2011 I sent a patch fixing this to the then-maintainer of hwdata. That patch apparently never made it through, possibly because of a maintainer change. Today I've sent the patch again to the developer who last made commits to the project. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/572628 Title: Liyama spelling error Status in GNOME Desktop Common Files: Invalid Status in “gnome-desktop3” package in Ubuntu: Invalid Status in “hwdata” package in Ubuntu: New Bug description: Binary package hint: gnome-control-center Lucid final release amd64 alternate install CD iiyama ProLite H511S LCD monitor gnome-control-center1:2.30.0-0ubuntu4 Preferences - Monitors brings up a green box containing the text Liyama North America 20. It should be iiyama, not Liyama. (And FWIW the monitor was purchased in England.) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/572628/+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 1174936] Re: online-accounts-preferences crashes immediately when opened
I'm not using two-factor authentication and I get the same issue. After going offline and removing my two Google accounts the crashing stops, but I still get this message: credentials-cc-panel-Message: cc-credentials-account-applications- model.vala:156: No valid plugin found for application 'shotwell' with account '7' Before removing the previous two account it was '6'. In seahorse the two accounts I have added are now represented by these four entries: Ubuntu Web Account: id 10-1 Ubuntu Web Account: id 10-3 Ubuntu Web Account: id 11-1 Ubuntu Web Account: id 11-3 There is something really strange going on with authentication. The Google accounts fail to connect half the time. Removing and readding them works, but that is not much of a workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1174936 Title: online-accounts-preferences crashes immediately when opened Status in Online Accounts: GNOME Control Center: New Status in “empathy” package in Ubuntu: Confirmed Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: `online-accounts-preferences` crashes immediately when opened. It crashes when you launch it by first opening System Settings via the launcher then choosing Online Accounts as well as when you open it directly by choosing Online Accounts from the launcher. It also crashes immediately when opened by running the `online-accounts- preferences` command on the command line. Here's the output it gives: % online-accounts-preferences credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'shotwell' with account '1' credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'unity-scope-gdrive' with account '1' credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'unity-lens-photos' with account '1' ** ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec != NULL) Aborted ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 30 14:03:48 2013 InstallationDate: Installed on 2012-10-18 (194 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center-signon UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center-signon/+bug/1174936/+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
