[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I just hit this bug with 19.04... The following "/usr/lib/gnome-online-accounts/goa-daemon --replace" did sort of reactivated my accounts accessibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826648] [NEW] cupds crashes with core dump
Public bug reported: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended- up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: New Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1826648] Re: cupds crashes with core dump
Here is the core dump with backtrace: $ gdb -c core /usr/sbin/cupsd Reading symbols from /usr/sbin/cupsd... (No debugging symbols found in /usr/sbin/cupsd) [New LWP 15514] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `cupsd -f -c /etc/cups/cupsd.conf'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type. (gdb) backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7ff44c736535 in __GI_abort () at abort.c:79 #2 0x7ff44c79d726 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff44c8c3952 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x7ff44c7a459a in malloc_printerr (str=str@entry=0x7ff44c8c1a9b "free(): invalid pointer") at malloc.c:5352 #4 0x7ff44c7a63cc in _int_free (av=, p=, have_lock=) at malloc.c:4181 #5 0x7ff44c9a78be in ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 #6 0x7ff44c9a7828 in ippDelete () from /usr/lib/x86_64-linux-gnu/libcups.so.2 #7 0x56032e311964 in ?? () #8 0x56032e34baa7 in ?? () #9 0x56032e309310 in ?? () #10 0x7ff44c737b6b in __libc_start_main (main=0x56032e308940, argc=4, argv=0x7fffb6f84b28, init=, fini=, rtld_fini=, stack_end=0x7fffb6f84b18) at ../csu/libc-start.c:308 #11 0x56032e30a5fa in ?? () (gdb) quit ** Attachment added: "core dumped with manual invocation" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826648/+attachment/5259490/+files/core -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: New Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Same here. Issue still on going with zesty 17.04 and quite painfull to deal with. One other approach is to re-symlink resolv.conf to /run/systemd/resolve/resolv.conf but openconnect then update /run/resolvconf/resolv.conf making this a total mess. I don't get it, this should be fairly trivial... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
>From the man page systemd-resolve can run in 3 mode of operations. 1) Ubuntu 17.10 default - The default is to list the 127.0.0.53 DNS stub (see above) as only DNS server. This file may be symlinked from /etc/resolv.conf in order to connect all local clients that bypass local DNS APIs to systemd-resolved. This mode of operation is recommended. 2) WHAT YOU WANT: systemd-resolved maintains the /run/systemd/resolve/resolv.conf file for compatibility with traditional Linux programs. This file may be symlinked from /etc/resolv.conf and is always kept up-to-date, containing information about all known DNS servers 3) PRE-17.04: Alternatively, /etc/resolv.conf may be managed by other packages, in which case systemd-resolved will read it for DNS configuration data. In this mode of operation systemd-resolved is consumer rather than provider of this configuration file. The fix: root@localhost:~# ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 29 mar 7 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf root@localhost:~# rm -f /etc/resolv.conf root@localhost:~# ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf root@localhost:~# ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 32 mar 8 07:30 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf Finally firefox started working properly along with all my command line tools... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Incomplete Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] Re: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
*** This bug is a duplicate of bug 1482439 *** https://bugs.launchpad.net/bugs/1482439 same as comment #12 for me. disabling wifi caused this bug in my case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Confirmed Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283]
Issue still present using Ubuntu 14.04. While this may be related to a "wrong" behaviour from the server side it works flawlessly using pidgin. Related launchpad bug: https://bugs.launchpad.net/ubuntu/+source /telepathy-gabble/+bug/874283 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283]
And may be related or duplicate of this as well: https://bugs.freedesktop.org/show_bug.cgi?id=39931 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283] Re: Empathy IM Client does not connect to Zimbra via XMPP
Issue still present with 14.04. While this may be related to a "wrong" behaviour from the server side it still does work flawlessly using pidgin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357373] Re: NetworkManager crashed with SIGABRT in g_assertion_message()
aport reported the exact same bug for me. I figure my problem is related where I end-up switching back and forth from one wifi to another possibly due to the networkmanager crashing and crashing... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357373 Title: NetworkManager crashed with SIGABRT in g_assertion_message() Status in “network-manager” package in Ubuntu: Confirmed Bug description: Crash upon login. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-8.13-lowlatency 3.16.0 Uname: Linux 3.16.0-8-lowlatency x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 Date: Fri Aug 15 16:32:32 2014 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-17 (301 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.101.101 dev wlan0 proto static 192.168.101.0/24 dev wlan0 proto kernel scope link src 192.168.101.131 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 ProcCmdline: NetworkManager ProcEnviron: TERM=linux PATH=(custom, no user) LANG=lv_LV.UTF-8 Signal: 6 SourcePackage: network-manager StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_proxy_new_finish () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: NetworkManager crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-01-18T14:14:35.028959 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1357373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
