Chromium process doesn't close when closing the last window
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
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:
[7859:7859:
When reporting this bug with ubuntu-bug, it suggested that /etc/chromium-
# Default settings for chromium-browser. This file is sourced by /bin/sh from
# /usr/bin/
# Options to pass to chromium-browser
CHROMIUM_FLAGS=""
# part for pepperflashplug
flashso=
if [ -f $flashso ]
then
fi
# part for pepperflashplug
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 49.0.2623.
ProcVersionSign
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: KDE
Date: Sun May 8 17:28:46 2016
Desktop-Session:
'kde-plasma'
'/etc/
'/usr/
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-
MachineType: Paradigit MS-7673
ProcKernelCmdLine: BOOT_IMAGE=
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.
dmi.board.name: P67A-C43 (MS-7673)
dmi.board.vendor: Paradigit
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Paradigit
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7673
dmi.product.
dmi.sys.vendor: Paradigit
gconf-keys: /desktop/
modified.
modified.
mtime.conffile.
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.