Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New issue 17219 by chris.frostnet.net: Making chrome the default browser, when config files are not owned by the user, freezes chrome http://code.google.com/p/chromium/issues/detail?id=17219 Chrome Version : 3.0.194.3-r20926 OS + version : v CPU architecture (32-bit / 64-bit): 32-bit (pentium-m) window manager : kwin URLs (if applicable) : n/a Behavior in Firefox 3.x (if applicable): untested Behavior in Chrome for Windows (optional): untested What steps will reproduce the problem? 1. Set the owner of $HOME/.kde/share/config/profilerc or $HOME/.local/share/applications/defaults.list to someone other than $USER (in my case, and very oddly, it was root). 2. Open the Options dialog box and click on "Make Google Chrome my default browser". What is the expected result? The Chrome UI continues to be responsive and Chrome becomes the default browser. What happens instead? Chrome freezes and on the terminal that started chrome, mv asks the user the questsion: "mv: try to overwrite `<CONFIG_FILE>', overriding mode 0644 (rw-r--r--)? " where <CONFIG_FILE> is one of the above two files owned by another user. Please provide any additional information below. Attach a screenshot and backtrace if possible. The mv program (/bin/mv) sees that it has a terminal and so asks the user whether they are sure they want to perform this action, which is somewhat odd for unix security to allow. I would not expect most users to have config files in their home directories that are owned by another user, but I also do not know how mine came to be owned by root. It seems more desirable for the operation to proceed without asking the user from the terminal. Thanks to Mike Mammarella for helping track down the root cause. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
