[Touch-packages] [Bug 1473800] [NEW] systemd update causes screen to lock
Public bug reported: When systemd is updated (through the update manager), the screen/session locks when processing the update. I've had this happen twice I think, and the only suspicious packages are the systemd ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 222-1ubuntu3 ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7 Uname: Linux 4.0.0-4-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 09:49:47 2015 InstallationDate: Installed on 2015-01-31 (162 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A88X Extreme4+ 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.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1473800 Title: systemd update causes screen to lock Status in systemd package in Ubuntu: New Bug description: When systemd is updated (through the update manager), the screen/session locks when processing the update. I've had this happen twice I think, and the only suspicious packages are the systemd ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 222-1ubuntu3 ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7 Uname: Linux 4.0.0-4-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 09:49:47 2015 InstallationDate: Installed on 2015-01-31 (162 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A88X Extreme4+ 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.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+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 1412719] Re: wait-for-state restarts whoopsie every 30sec
** Branch linked: lp:~mjblenner/whoopsie/whoopsie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec Status in One Hundred Papercuts: Confirmed Status in Upstart: Confirmed Status in upstart package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Triaged Bug description: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+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 1425024] [NEW] indicator-sound-service crashed with signal 5 in main()
Public bug reported: Crashed in the greeter (lightdm). ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Tue Feb 24 21:50:39 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-01-31 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1425024 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: Crashed in the greeter (lightdm). ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Tue Feb 24 21:50:39 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-01-31 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1425024/+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 1425012] [NEW] webapp-container crashed with SIGSEGV
Public bug reported: youtube webapp crashed on close. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150217.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Feb 24 21:31:56 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=YouTubeyoutubecom --webapp=WW91VHViZQ== --enable-back-forward ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fa5482b6010: mov0x10(%rdi),%rdx PC (0x7fa5482b6010) ok source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webapp-container crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1425012 Title: webapp-container crashed with SIGSEGV Status in webbrowser-app package in Ubuntu: New Bug description: youtube webapp crashed on close. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150217.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Feb 24 21:31:56 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=YouTubeyoutubecom --webapp=WW91VHViZQ== --enable-back-forward ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fa5482b6010:mov0x10(%rdi),%rdx PC (0x7fa5482b6010) ok source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webapp-container crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1425012/+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 1424958] [NEW] ibus-daemon crashed with SIGABRT in g_assertion_message()
Public bug reported: seems to be random. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 19:25:44 2015 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2015-01-31 (23 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus 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 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1424958 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: New Bug description: seems to be random. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 19:25:44 2015 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2015-01-31 (23 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus 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 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1424958/+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 1423855] [NEW] Unity can't show the global menu item for some gnome apps
Public bug reported: Unity can't show the global menu item for some gnome apps. For example, the 'terminal' menu for gnome-terminal, or the 'calculator' menu for gnome-calculator cannot be opened. Other menus can be displayed (file, edit,...) This is a recent regression I think. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 20 21:14:01 2015 InstallationDate: Installed on 2015-01-31 (20 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1423855 Title: Unity can't show the global menu item for some gnome apps Status in unity package in Ubuntu: New Bug description: Unity can't show the global menu item for some gnome apps. For example, the 'terminal' menu for gnome-terminal, or the 'calculator' menu for gnome-calculator cannot be opened. Other menus can be displayed (file, edit,...) This is a recent regression I think. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 20 21:14:01 2015 InstallationDate: Installed on 2015-01-31 (20 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1423855/+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 1419254] [NEW] webapp-container crashed with SIGABRT in __run_exit_handlers()
*** This bug is a duplicate of bug 1416785 *** https://bugs.launchpad.net/bugs/1416785 Public bug reported: Crashed at startup. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150203.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Feb 7 22:03:35 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=Gmailmailgooglecom --webapp=R21haWw= --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 __run_exit_handlers (status=1, listp=0x7ffa111066c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 __GI_exit (status=) at exit.c:104 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() UpgradeStatus: Upgraded to vivid on 2015-01-31 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1419254 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() Status in webbrowser-app package in Ubuntu: New Bug description: Crashed at startup. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150203.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Feb 7 22:03:35 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=Gmailmailgooglecom --webapp=R21haWw= --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 __run_exit_handlers (status=1, listp=0x7ffa111066c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 __GI_exit (status=) at exit.c:104 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() UpgradeStatus: Upgraded to vivid on 2015-01-31 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1419254/+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 1416786] [NEW] webapp-container crashed with SIGSEGV
Public bug reported: Crash while starting web-app containers (googleplus or gmail) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150127-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Feb 1 15:11:14 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=GooglePlusplusgooglecom --webapp=R29vZ2xlUGx1cw== --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8dbfc114a0: mov0x10(%rdi),%rdx PC (0x7f8dbfc114a0) ok source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webapp-container crashed with SIGSEGV UpgradeStatus: Upgraded to vivid on 2015-01-31 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1416786 Title: webapp-container crashed with SIGSEGV Status in webbrowser-app package in Ubuntu: New Bug description: Crash while starting web-app containers (googleplus or gmail) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150127-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Feb 1 15:11:14 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=GooglePlusplusgooglecom --webapp=R29vZ2xlUGx1cw== --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8dbfc114a0:mov0x10(%rdi),%rdx PC (0x7f8dbfc114a0) ok source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webapp-container crashed with SIGSEGV UpgradeStatus: Upgraded to vivid on 2015-01-31 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1416786/+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 1416785] [NEW] webapp-container crashed with SIGABRT in __run_exit_handlers()
Public bug reported: - install googleplus web-app (from firefox) - close firefox - click on googleplus icon - blank window appears for about 5 seconds - crash ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150127-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 1 15:03:27 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=GooglePlusplusgooglecom --webapp=R29vZ2xlUGx1cw== --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 __run_exit_handlers (status=1, listp=0x7ffc58dfe6c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 __GI_exit (status=) at exit.c:104 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() UpgradeStatus: Upgraded to vivid on 2015-01-31 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1416785 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() Status in webbrowser-app package in Ubuntu: New Bug description: - install googleplus web-app (from firefox) - close firefox - click on googleplus icon - blank window appears for about 5 seconds - crash ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150127-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 1 15:03:27 2015 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-01-31 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: webapp-container --app-id=GooglePlusplusgooglecom --webapp=R29vZ2xlUGx1cw== --enable-back-forward --store-session-cookies ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 __run_exit_handlers (status=1, listp=0x7ffc58dfe6c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 __GI_exit (status=) at exit.c:104 Title: webapp-container crashed with SIGABRT in __run_exit_handlers() UpgradeStatus: Upgraded to vivid on 2015-01-31 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1416785/+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 1412719] Re: wait-for-state restarts whoopsie every 30sec
Looking at man 8 init, there is no job state "started", so having WAIT_STATE=started is exactly equal to WAIT_STATE=foobar, since they both don't exit. So you may as well change it to something sensible. Also, the reason that whoopsie exits as soon as it is respawned is that there is already another whoopsie process running, that either was started by something else (apport?), or upstart tost track of it. Either way, fixing the wait-for-state (this patch or fixing whoopsie.conf), fixes the 30sec respawn bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec Status in One Hundred Papercuts: Confirmed Status in Upstart: Confirmed Status in upstart package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Triaged Bug description: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+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 1374721] Re: ibus-daemon uses 100% CPU when using gnome-calculator
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1374721 Title: ibus-daemon uses 100% CPU when using gnome-calculator Status in ibus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721/+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 1377370] Re: ubuntu-desktop should depend on ibus-gtk
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1377370 Title: ubuntu-desktop should depend on ibus-gtk Status in ubuntu-meta package in Ubuntu: New Bug description: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1377370/+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 1412719] [NEW] wait-for-state restarts whoopsie every 30sec
Public bug reported: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec Status in upstart package in Ubuntu: New Bug description: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1412719/+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 1412719] Re: wait-for-state restarts whoopsie every 30sec
This patch changes the defaults for wait-for-state.conf to something sensible for WAIT_STATE. ** Patch added: "Fix for wait-for-state" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1412719/+attachment/4302214/+files/wait_fix.patch ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec Status in upstart package in Ubuntu: New Bug description: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1412719/+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 1375742] Re: ibus-daemon uses 100% CPU after a modifier key is pressed
This is fixed/workedaround by installing ibus-gtk (ibus-gtk3 is in the default install, but ibus-gtk isn't) see LP: #1377370 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1375742 Title: ibus-daemon uses 100% CPU after a modifier key is pressed Status in “ibus” package in Ubuntu: New Bug description: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1375742/+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 1374721] Re: ibus-daemon uses 100% CPU when using gnome-calculator
This is fixed/workedaround by installing ibus-gtk (ibus-gtk3 is in the default install, but ibus-gtk isn't) see LP: #1377370 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1374721 Title: ibus-daemon uses 100% CPU when using gnome-calculator Status in “ibus” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721/+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 1377370] [NEW] ubuntu-desktop should depend on ibus-gtk
Public bug reported: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1377370 Title: ubuntu-desktop should depend on ibus-gtk Status in “ubuntu-meta” package in Ubuntu: New Bug description: Note that ubuntu-desktop depends on ibus-gtk3 already. Looking at /usr/share/im-config/data/21-ibus.rc GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules are present. Otherwise it's set to xim. If GTK_IM_MODULE=xim and ibus is running, then various bugs happen like LP: #1374721 and LP: #1375742. Installing ibus-gtk makes those problems go away. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 4 13:49:55 2014 InstallationDate: Installed on 2014-09-03 (30 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1377370/+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 1375742] [NEW] ibus-daemon uses 100% CPU after a modifier key is pressed
Public bug reported: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1375742 Title: ibus-daemon uses 100% CPU after a modifier key is pressed Status in “ibus” package in Ubuntu: New Bug description: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1375742/+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 1374942] [NEW] compiz crashed with signal 5 in _XReply()
Public bug reported: Unkown cause. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 16:19:49 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-09-03 (25 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1374942 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: Unkown cause. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 16:19:49 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-09-03 (25 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374942/+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 1374721] [NEW] ibus-daemon uses 100% CPU when using gnome-calculator
Public bug reported: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1374721 Title: ibus-daemon uses 100% CPU when using gnome-calculator Status in “ibus” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721/+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 1029289] Re: Need to authorize my google account each time I boot the computer
This isn't fixed for me on utopic, can anyone else confirm? What does fix this for me is the patch I wrote for evolution-data-server over at LP: #1373908 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Status in “account-plugins” source package in Trusty: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Committed Status in “signon-plugin-oauth2” source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1373908] [NEW] UOA integration always creates new evolution-datat-server accounts on login
Public bug reported: (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the "bus-aquired" signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1373908 Title: UOA integration always creates new evolution-datat-server accounts on login Status in “evolution-data-server” package in Ubuntu: New Bug description: (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the "bus-aquired" signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+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 1373908] Re: UOA integration always creates new evolution-datat-server accounts on login
Use g_signal_connect_after() on "bus-acquired" so that EDS can load all the accounts first, before UOA tries to match them to UOA accounts. ** Patch added: "startup-fix.patch" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+attachment/4214809/+files/startup-fix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1373908 Title: UOA integration always creates new evolution-datat-server accounts on login Status in “evolution-data-server” package in Ubuntu: New Bug description: (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the "bus-aquired" signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+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 1365435] [NEW] unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1298654 *** https://bugs.launchpad.net/bugs/1298654 Public bug reported: This happened at the same time as LP:1364285 (except in shotwell, not nautilus) Possibly related to menu items changing? ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Sep 4 20:39:16 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-09-03 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fa78364ae1f: mov(%r12),%rdi PC (0x7fa78364ae1f) ok source "(%r12)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1365435 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() Status in “unity” package in Ubuntu: New Bug description: This happened at the same time as LP:1364285 (except in shotwell, not nautilus) Possibly related to menu items changing? ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Sep 4 20:39:16 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-09-03 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fa78364ae1f:mov(%r12),%rdi PC (0x7fa78364ae1f) ok source "(%r12)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1365435/+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 1360172] [NEW] powerd crashed with SIGABRT in ua_sensors_proximity_new()
*** This bug is a duplicate of bug 1351314 *** https://bugs.launchpad.net/bugs/1351314 Public bug reported: Crash on upgrade (on the desktop) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: powerd 0.16+14.10.20140819-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Fri Aug 22 19:59:36 2014 ExecutablePath: /usr/bin/powerd InstallationDate: Installed on 2013-06-22 (426 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) ProcCmdline: /usr/bin/powerd ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: powerd StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_sensors_proximity_new () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 powerd_sensors_init() () main () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: powerd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1360172 Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() Status in “powerd” package in Ubuntu: New Bug description: Crash on upgrade (on the desktop) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: powerd 0.16+14.10.20140819-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Fri Aug 22 19:59:36 2014 ExecutablePath: /usr/bin/powerd InstallationDate: Installed on 2013-06-22 (426 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) ProcCmdline: /usr/bin/powerd ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: powerd StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_sensors_proximity_new () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 powerd_sensors_init() () main () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1360172/+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
