Launchpad has imported 5 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1955800.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2025-03-23T02:34:15+00:00 Intermittent-bug-filer wrote:

**Filed by:** amarc [at] mozilla.com
**Parsed log:** 
https://treeherder.mozilla.org/logviewer?job_id=500488754&repo=mozilla-central
**Full log:** 
https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Wo9dYVitRo-gMSPnbLLZLQ/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2025-03-23T02:31:26.167Z] Building wheels for collected packages: mozlog
[task 2025-03-23T02:31:26.168Z]   Building wheel for mozlog (setup.py): started
[task 2025-03-23T02:31:26.399Z]   Building wheel for mozlog (setup.py): 
finished with status 'done'
[task 2025-03-23T02:31:26.400Z]   Created wheel for mozlog: 
filename=mozlog-8.0.0-py2.py3-none-any.whl size=69608 
sha256=73f30afb9ae230a5abcf0bc00d91f5cf600a03057d8cf66bd40d8abda35430fd
[task 2025-03-23T02:31:26.400Z]   Stored in directory: 
/home/task_174269682053351/.cache/pip/wheels/f3/04/57/02f3d25fa74ca7a408a80e1b4892033a55c233229f7cc0b858
[task 2025-03-23T02:31:26.401Z] Successfully built mozlog
[task 2025-03-23T02:31:26.744Z] Installing collected packages: wcwidth, 
sortedcontainers, urllib3, sniffio, PyYAML, PySocks, Pillow, mozterm, mozfile, 
idna, h11, exceptiongroup, certifi, blessed, attrs, wsproto, outcome, mozlog, 
trio, trio-websocket, selenium
[task 2025-03-23T02:31:27.372Z]   WARNING: The script structlog is installed in 
'/home/task_174269682053351/.local/bin' which is not on PATH.
[task 2025-03-23T02:31:27.372Z]   Consider adding this directory to PATH or, if 
you prefer to suppress this warning, use --no-warn-script-location.
[task 2025-03-23T02:31:28.218Z] Successfully installed Pillow-10.1.0 
PySocks-1.7.1 PyYAML-6.0.1 attrs-23.1.0 blessed-1.20.0 certifi-2023.7.22 
exceptiongroup-1.1.3 h11-0.14.0 idna-3.4 mozfile-3.0.0 mozlog-8.0.0 
mozterm-1.0.0 outcome-1.2.0 selenium-4.12.0 sniffio-1.3.0 
sortedcontainers-2.4.0 trio-0.22.2 trio-websocket-0.10.4 urllib3-2.0.5 
wcwidth-0.2.13 wsproto-1.2.0
[task 2025-03-23T02:31:28.328Z] + export TEST_NO_HEADLESS=1
[task 2025-03-23T02:31:28.328Z] + TEST_NO_HEADLESS=1
[task 2025-03-23T02:31:28.328Z] + '[' -n '' ']'
[task 2025-03-23T02:31:28.328Z] + RECORD_SCREEN_PID=0
[task 2025-03-23T02:31:28.328Z] + '[' '' = true ']'
[task 2025-03-23T02:31:28.328Z] + '[' basic = basic ']'
[task 2025-03-23T02:31:28.328Z] + sed -e s/#RUNTIME_VERSION#/command-chain/#
[task 2025-03-23T02:31:28.330Z] + python3 basic_tests.py 
basic_tests/expectations.json
[task 2025-03-23T02:31:58.595Z] Traceback (most recent call last):
[task 2025-03-23T02:31:58.595Z]   File 
"/task_174269682053351/fetches/basic_tests.py", line 556, in <module>
[task 2025-03-23T02:31:58.595Z]     SnapTests(exp=sys.argv[1])
[task 2025-03-23T02:31:58.595Z]   File 
"/task_174269682053351/fetches/basic_tests.py", line 384, in __init__
[task 2025-03-23T02:31:58.595Z]     super(SnapTests, self).__init__(exp)
[task 2025-03-23T02:31:58.595Z]   File 
"/task_174269682053351/fetches/basic_tests.py", line 87, in __init__
[task 2025-03-23T02:31:58.595Z]     self._driver = 
webdriver.Firefox(service=driver_service, options=options)
[task 2025-03-23T02:31:58.595Z]   File 
"/home/task_174269682053351/.local/lib/python3.10/site-packages/selenium/webdriver/firefox/webdriver.py",
 line 60, in __init__
[task 2025-03-23T02:31:58.596Z]     self.service.start()
[task 2025-03-23T02:31:58.596Z]   File 
"/home/task_174269682053351/.local/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
 line 116, in start
[task 2025-03-23T02:31:58.596Z]     raise WebDriverException(f"Can not connect 
to the Service {self._path}")
[task 2025-03-23T02:31:58.596Z] selenium.common.exceptions.WebDriverException: 
Message: Can not connect to the Service /snap/bin/firefox.geckodriver
[task 2025-03-23T02:31:58.596Z] 
[taskcluster 2025-03-23T02:31:58.628Z]    Exit Code: 1
[taskcluster 2025-03-23T02:31:58.628Z]    User Time: 9.184071s
[taskcluster 2025-03-23T02:31:58.628Z]  Kernel Time: 2.300034s
[taskcluster 2025-03-23T02:31:58.628Z]    Wall Time: 3m17.577612363s
[taskcluster 2025-03-23T02:31:58.628Z]       Result: FAILED
[taskcluster 2025-03-23T02:31:58.629Z] === Task Finished ===
[taskcluster 2025-03-23T02:31:58.629Z] Task Duration: 3m17.579822758s
[taskcluster 2025-03-23T02:31:58.667Z] Uploading artifact 
public/build/geckodriver.log from file 
/task_174269682053351/builds/worker/artifacts/geckodriver.log with content 
encoding "gzip", mime type "text/plain" and expiry 2025-06-21T02:26:07.298Z
[taskcluster 2025-03-23T02:31:59.051Z] Uploading link artifact 
public/logs/live.log to artifact public/logs/live_backing.log with expiry 
2025-06-21T02:26:07.298Z
[taskcluster:error] exit status 1
```

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2072395/comments/28

------------------------------------------------------------------------
On 2025-03-24T06:11:00+00:00 Lissyx+mozillians wrote:

>From https://firefoxci.taskcluster-artifacts.net/Wo9dYVitRo-
gMSPnbLLZLQ/0/public/build/geckodriver.log

`Content snap command-chain for /snap/firefox/x1/gnome-platform/command-
chain/desktop-launch not found: ensure slot is connected`

Nathan, is this the famous core22 to core24 migration issue?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2072395/comments/29

------------------------------------------------------------------------
On 2025-03-24T06:11:51+00:00 Lissyx+mozillians wrote:

And if so, what is the way to fix it? Locally I could never get anything
to work when it happened until I did a reboot, but on CI it's not going
to be effective.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2072395/comments/30

------------------------------------------------------------------------
On 2025-03-24T06:57:32+00:00 Orangefactor wrote:

## Summary
1 failures in 5035 pushes (0.0 failures/push) were associated with this bug in 
the last 7 days.

## Repository breakdown:
* mozilla-central: 1

## Platform and build breakdown:
* linux64-snap-amd64-2204-stablecore24: 1
  * opt: 1

## Table
| |**no_variant**|
|---|:-:|
|**linux64-snap-amd64-2204-stablecore24--/opt**|1|

## For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1955800&startday=2025-03-17&endday=2025-03-23&tree=all

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2072395/comments/31

------------------------------------------------------------------------
On 2025-03-24T08:37:36+00:00 Nathan Teodosio wrote:

> Nathan, is this the famous core22 to core24 migration issue?

Yes, it's https://launchpad.net/bugs/2072395.

> And if so, what is the way to fix it?

None is known to date, which is why we are holding every snap away from
core24 while Snapd folks fight the bug.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2072395/comments/32


** Changed in: firefox
       Status: Unknown => Confirmed

-- 
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/2072395

Title:
  [snap] Chromium with core24 base won't start: desktop-launch not found

Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  Today I was prompted to update my chromium snap, so I closed it down
  and the auto-refresh happened. When I tried to launch it, it did not
  come up. Running `chromium` from the command line resulted in the
  following error:

  $ chromium
  Content snap command-chain for 
/snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found: 
ensure slot is connected

  
  Browsing the internet, I found people saying that gnome needed to be 
connected. Running `sudo snap connect chromium:gnome-46-2404 
gnome-46-2404:gnome-46-2404` did not fix the problem.

  I'm not sure it matters for a snap, but this is (very recently
  updated) ubuntu 22.04 running KDE on x86_64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2072395/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to