desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #147696
[Bug 1249047] Re: Chromium profile get corrupted when logged in Google cloud print service
I am also Creating new profile and i also got the same error here
http://www.bestessayhelp.co.uk
--
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/1249047
Title:
Chromium profile get corrupted when logged in Google cloud print
service
Status in Chromium Browser:
Unknown
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
Step to reproduce :
-install chromium-browser package
-launch chromium and log in with your google account
-have the hangout extension installed : get it from here https://chrome.google.com/webstore/detail/hangouts/nckgahadagoaajjgafhacjanaoiihapd in chromium
-be sure you have the option "Continue running background apps when Google Chrome is closed" checked in params
-in params, connect to google cloud print and add printer (you need to have a printer connected to your pc)
-when all of these is done, close chromium and restart your pc
-log in and chromium should start the hangout extension and show up your contact list, the chromium icon sould also be displayed in the systray
-when chromium is loaded, start id by clicking the chromium icon in the startup menu, or by taping "chromium-browser" into a console
You should get a message notifying you that your chromium profile is corrupted.
If you start chromium by clicking the menu in system tray (on about menu option by example), you won't get this message.
If you start chromium with the profile corrupted, you have to kill all
your chromium instances to get it work back properly.
If google cloud print is disconnected, everything is working
perfectly.
I tried to reproduce this bug in chrome (not chromium) under windows
7, I wasn't able to do so.
I am running Kubuntu 13.10 and chromium version
30.0.1599.114-0ubuntu0.13.10.2
Did you see the same behaviour ?
Did you reproduce this problem ?
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1249047/+subscriptions