Issue metadata
Sign in to add a comment
|
remote "new tab" closes browser.
Reported by
rew-goog...@bitwizard.nl,
Apr 8 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/56.0.2924.76 Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: 1. Open browser with lotsa tabs. 2. switch to an other virtual desktop. 3. run "chromium-browser --new-tab-page-1 http://www.gocomics.com/adamathome/" (I do this from CRON). What is the expected behavior? Just as when you leave out "step 2" above, the mentioned website opens in a new tab. What went wrong? The browser crashes with "invalid channel message". The call to chromium-browser (from CRON) then opens a new browser that holds the requested site and "chromium didn't shut down properly, restore tabs?", but cannot do any audio. Crashed report ID: nope. How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes About a month ago. Chrome version: 56.0.2924.76 Channel: n/a OS Version: Ubuntu 16.04 Flash Version: Shockwave Flash 25.0 r0 The behaviour of "chromium-browser --new-tab-page-1" is inconsistent: It returns to the shell after opening a new tab, but does not return when there is no browser running.
,
Apr 17 2017
Unable to reproduce the issue on Linux Ubuntu 16.04 using chrome reported version-56.0.2924.76 & stable-57.0.2987.133 as per the below steps: 1.Check 'enable Workspaces' option in settings>appearence 2.Opened chrome browser with lots of tabs in workspace 1. 3.Open workspace 2 4.Open terminal 5.Execute "chromium-browser --new-tab-page-1 http://www.gocomics.com/adamathome/" command in terminal & hit enter 6.Observed chromium browser opened seccuessfully without any crash & site "http://www.gocomics.com/adamathome" opened in new tab Please check the issue by updating chrome browser with latest stable version & update the thread accordingly. Thank you!!
,
Apr 17 2017
I have "workspace 2" for webbrowsing, workspace 1 for mail. I was looking at the mail message with your comment when I realized: my workspace1 was open when I came to the computer this morning and my comics had opened just fine.... I have the impression that today is the first time I've noticed it working normally again. Options: * You're pulling my leg by quickly fixing it and then blaming me for the inaccurate report. :-) * Ubuntu fixed the regression. (It may have only been in their version). * It depends on more than I thought it did -> It'll happen again on short notice. My suggestion: * Leave this open. No further action from chromium team. I'll try to report back in a week or so. Otherwise remind me by posting the comment: "and?" if you see this after april 24 2017.
,
Apr 17 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 24 2017
Hi, I've been going about my business since then, and partly because I hate it when this bug triggers and partly because I apparently often leave my computer with the web-browsing workspace active... it hasn't happened again.. Until yesterday. So. For me on 16.04 the problem has NOT been fixed. I use "sawfish" as the window manager. Is that something that may make a difference? On my systems, installing sawfish and then trying to login with sawfish as the window manager will return you to the login screen on short notice. The issue is a missing file that comes with the sawfish source distribution that needs to be included in the .deb....
,
Apr 24 2017
,
Jul 31 2017
There is no valid updates happened in the last few months, closing the issue. Feel free to reopen if needed.
,
Aug 1 2017
I still suspect that it has NOT been fixed. But I found a good workaround. My start-tabs script now asks the windowmanager to switch to the browser-workspace before starting the tabs. This works-for-me, but does not fix the bug. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nyerramilli@google.com
, Apr 12 2017