It seems this issue is related to SCIM which is started by Chromium (when it's not started yet?). Removing all the SCIM related packages solved the issue.
I suspect this bug is still present for people that need to use SCIM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1579533 Title: Chromium process doesn't close when closing the last window Status in chromium-browser package in Ubuntu: New Bug description: This is how the problem shows: 1. I start up Chromium 2. I close its window 3. I start it again, Chromium complains it can't open its profile When I run Chromium from a terminal, I see that it doesn't close after I close its window. I have to do an explicit ctrl+c in the terminal (or kill the processes) before I can start Chromium again without having a 'profile in use' warning. There are *no* extensions installed. The check box to stay active if any background app would be enabled is turned *off* as well. Terminal output: $ chromium-browser Using PPAPI flash. Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... Failed to load x11 FrontEnd module. [7859:7859:0508/172606:ERROR:logging.h(813)] Failed to call method: org.freedesktop.DBus.ObjectManager.GetManagedObjects: object_path= /: org.freedesktop.DBus.Error.UnknownMethod: Method "GetManagedObjects" with signature "" on interface "org.freedesktop.DBus.ObjectManager" doesn't exist [7859:7859:0508/172606:ERROR:logging.h(813)] Failed to call method: org.freedesktop.DBus.ObjectManager.GetManagedObjects: object_path= /: org.freedesktop.DBus.Error.UnknownMethod: Method "GetManagedObjects" with signature "" on interface "org.freedesktop.DBus.ObjectManager" doesn't exist When reporting this bug with ubuntu-bug, it suggested that /etc/chromium-browser/default had been changed. I never changed this file myself. When confirming that it could be attached to this bug report, ubuntu-bug crashed. Only choosing to not add this file, allowed me to report this bug. Here is the content of /etc/chromium-browser/default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser # Options to pass to chromium-browser CHROMIUM_FLAGS="" # part for pepperflashplugin-nonfree : begin flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" if [ -f $flashso ] then flashversion=`strings $flashso|grep ^LNX|sed -e "s/^LNX //"|sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" fi # part for pepperflashplugin-nonfree : end ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 49.0.2623.108-0ubuntu0.14.04.1.1113 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 8 17:28:46 2016 Desktop-Session: 'kde-plasma' '/etc/xdg/xdg-kde-plasma:/usr/share/upstart/xdg:/etc/xdg' '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/' Env: 'None' 'None' InstallationDate: Installed on 2011-09-12 (1700 days ago) InstallationMedia: Kubuntu 10.04 Trinity LTS "Lucid Lynx" - Release amd64 (20100427) Load-Avg-1min: 0.12 Load-Processes-Running-Percent: 0.2% MachineType: Paradigit MS-7673 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=999e0fb5-ef5b-44e4-a3a5-0e0f6cad9533 ro quiet splash SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2015-01-02 (491 days ago) dmi.bios.date: 04/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P67A-C43 (MS-7673) dmi.board.vendor: Paradigit dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Paradigit dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd04/14/2011:svnParadigit:pnMS-7673:pvr1.0:rvnParadigit:rnP67A-C43(MS-7673):rvr1.0:cvnParadigit:ct3:cvr1.0: dmi.product.name: MS-7673 dmi.product.version: 1.0 dmi.sys.vendor: Paradigit gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-04T23:18:52.653034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1579533/+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
