[Desktop-packages] [Bug 1015794] Re: evolution-calendar-factory crashed with SIGSEGV in book_client_opened_cb()
I to am getting this bug as well. 12.10 32bit. I have reinstalled multiple times. The bug happens at random intervals. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1015794 Title: evolution-calendar-factory crashed with SIGSEGV in book_client_opened_cb() Status in “evolution-data-server” package in Ubuntu: Confirmed Bug description: Out of the blue. Not actively using anything related to evolution. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: evolution-data-server 3.4.3-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic i686 ApportVersion: 2.2.3-0ubuntu6 Architecture: i386 Date: Wed Jun 20 20:50:29 2012 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1) ProcCmdline: /usr/lib/evolution/evolution-calendar-factory ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=en_US:en LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb69aa917:mov0x4(%eax),%eax PC (0xb69aa917) ok source "0x4(%eax)" (0xaaae) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so g_cclosure_marshal_VOID__BOXEDv (closure=closure@entry=0xb290b690, return_value=return_value@entry=0x0, instance=instance@entry=0xb2907020, args=args@entry=0xbf80e47c "", marshal_data=marshal_data@entry=0x0, n_params=n_params@entry=1, param_types=param_types@entry=0xb2906520) at /build/buildd/glib2.0-2.33.2/./gobject/gmarshal.c:1160 _g_closure_invoke_va (closure=0xb290b690, return_value=return_value@entry=0x0, instance=instance@entry=0xb2907020, args=args@entry=0xbf80e47c "", n_params=1, param_types=0xb2906520) at /build/buildd/glib2.0-2.33.2/./gobject/gclosure.c:840 g_signal_emit_valist (instance=instance@entry=0xb2907020, signal_id=signal_id@entry=72, detail=detail@entry=0, var_args=var_args@entry=0xbf80e47c "") at /build/buildd/glib2.0-2.33.2/./gobject/gsignal.c:3207 g_signal_emit (instance=0xb2907020, signal_id=72, detail=0) at /build/buildd/glib2.0-2.33.2/./gobject/gsignal.c:3352 Title: evolution-calendar-factory crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXEDv() UpgradeStatus: Upgraded to quantal on 2012-06-19 (1 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1015794/+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 941463] Re: empathy automatically start on login doesnot work
I can confirm this bug. This has been present since Ubuntu switched to Empathy. This needs to be fixed. -- 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/941463 Title: empathy automatically start on login doesnot work Status in “empathy” package in Ubuntu: Invalid Bug description: i have selected from the preference that auto-start on login but empathy does not start on start on login. ubuntu 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic i686 ApportVersion: 1.93-0ubuntu2 Architecture: i386 Date: Sun Feb 26 19:48:09 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111211) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-01-27 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/941463/+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 841541] Re: "num lock is on" warning remains even after num lock is turned off (thinkpad, numlock status for laptop and external keyboard different)
I can confirm that this bug is real. I have a Lenovo T61. Rebooting and setting from "independent" to "synchronized" in the BIOS under keyboard/mouse settings does remove the message. Would be nice if this was backported to Oneiric... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/841541 Title: "num lock is on" warning remains even after num lock is turned off (thinkpad, numlock status for laptop and external keyboard different) Status in “gnome-screensaver” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “gnome-screensaver” source package in Oneiric: Triaged Status in “gtk+3.0” source package in Oneiric: Triaged Status in “gnome-screensaver” source package in Precise: Fix Released Status in “gtk+3.0” source package in Precise: Fix Released Bug description: Version: 3.1.5-0ubuntu6 Release: 11.10 After fiddling with Num Lock, I noticed that the lock window claimed it was still enabled, and yet it is not. Comments info: "it might be connected with the fact that on (new) Thinkpads there are something like TWO num locks, one is for an external keyboard and the other - for the internal one." Sequence of events: * Turn on Num Lock. * Lock the screen. (On a ThinkPad, I do this by pressing Fn+F2. Whatever option it is that means "lock the screen immediately", I have it turned on.) * Tap a key to bring up the screen-locked/enter-password dialog. * Observe the warning. * Turn off Num Lock. * Observe the warning is still there. * Successfully unlock the screen. * Lock the screen again. * Observe the warning is still there. * [Optional] Unlock the screen. File a bug against gnome-screensaver. Not related to bug #835649, which concerns showing the warning when Num Lock is enabled but not otherwise problematic, e.g. when using a "full-size" (i.e. "has lots of extra keys") keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/841541/+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
