Ungoogled-chromium doesn't launch with linux 6.2

  • Done
  • quality assurance status badge
Details
4 participants
  • Josselin Poiret
  • Jack Hill
  • Maxim Cournoyer
  • Nicolas Graves
Owner
unassigned
Submitted by
Nicolas Graves
Severity
normal
N
N
Nicolas Graves wrote on 16 Mar 2023 09:08
(address . bug-guix@gnu.org)
87mt4ddspl.fsf@ngraves.fr
Hi!

I've updated linux to version 6.2.2 (the nonfree version), and since
then I can't launch ungoogled-chromium-wayland.

Nyxt or Firefox-like browsers work fine.

Here's what I tried :

guix shell gdb -- gdb /gnu/store/1jmlqw987ifnb3abr0s2hvihcg1n2xmx-ungoogled-chromium-wayland-109.0.5414.119-1/bin/chromium

yields

"/gnu/store/1jmlqw987ifnb3abr0s2hvihcg1n2xmx-ungoogled-chromium-wayland-109.0.5414.119-1/bin/chromium": not in executable format: file format not recognized

Thanks if you can fix this quickly.

--
Best regards,
Nicolas Graves
J
J
Josselin Poiret wrote on 16 Mar 2023 10:36
87sfe5ghri.fsf@jpoiret.xyz
Hi Nicolas,

Nicolas Graves via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (5 lines)
> Hi!
>
> I've updated linux to version 6.2.2 (the nonfree version), and since
> then I can't launch ungoogled-chromium-wayland.

Can you reproduce in linux-libre? A `guix system vm` should be enough
to test this.

Best,
--
Josselin Poiret
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCAAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmQS4xEQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5FhcaikZDC/0baqSH8Y2FYScfuCLb5c3m7bkG68dYOIe1
Kws04c9o3drAyIBLqH3QMR/GHN83AuR/z69Oi9adbF+9OqdcZedFZs8EFBO5ZLGp
T8xKe8pStevwQ5ndPXfPQ5dDJAR2ykwGMffzfkhTq1HF/pCkc7BIvtwq2hJ/biPP
SOcyjljQ7c7D6iRxuhE735W+OjllX0KGkvNv3v+Qwl9oyJJ0mY9H9FcoALafK5XA
BQ4K1mDbwAK94xaMNXCsEVU8LpYqd6MI578ECaI9CmtZcB1ShfEtJSbMixugzkwb
5TFCanVHd5dCf14h7+BKnNpWZ6OOzuRqtNh5azjAMxkv/NaquKWZyKiNv/Z0f2xr
cDT7OPRiCn4HCCVxLGFs3UttkrPfChneHDXFeylRUwdh6nIG5kQCeOwYJTnlBOgp
j8WC4eDTQocoU8o/sY+j68nC4j44r4OyPO8q9v+pECKBgnN8Mr52y69T74+t8MuN
i2UIFYvDYLlR+k/KldMPI12ceXSTlqM=
=972B
-----END PGP SIGNATURE-----

J
J
Jack Hill wrote on 16 Mar 2023 15:58
(name . Nicolas Graves)(address . ngraves@ngraves.fr)(address . 62217@debbugs.gnu.org)
alpine.DEB.2.21.2303161055290.15296@marsh.hcoop.net
On Thu, 16 Mar 2023, Nicolas Graves via Bug reports for GNU Guix wrote:

Toggle quote (2 lines)
> "/gnu/store/1jmlqw987ifnb3abr0s2hvihcg1n2xmx-ungoogled-chromium-wayland-109.0.5414.119-1/bin/chromium": not in executable format: file format not recognized

I've run into this message in the past when my store got corrupted (in my
case it was a full disk on a computer that has other evil spirits living
in it as well). Can you check with `guix gc --verify=contents`? If it
reports anything, you might be able to repair it with `sudo guix gc
--verify=contents,repair`.

For what it's worth ungoogled-chromium works for me with Guix commit
5312d798ac36a72d8a977325a7c6ff7647be670a.

Best,
Jack
M
M
Maxim Cournoyer wrote on 17 Mar 2023 18:49
(name . Jack Hill)(address . jackhill@jackhill.us)
87y1nv469x.fsf@gmail.com
Hi,

Jack Hill <jackhill@jackhill.us> writes:

Toggle quote (11 lines)
> On Thu, 16 Mar 2023, Nicolas Graves via Bug reports for GNU Guix wrote:
>
>> "/gnu/store/1jmlqw987ifnb3abr0s2hvihcg1n2xmx-ungoogled-chromium-wayland-109.0.5414.119-1/bin/chromium":
>> not in executable format: file format not recognized
>
> I've run into this message in the past when my store got corrupted (in
> my case it was a full disk on a computer that has other evil spirits
> living in it as well). Can you check with `guix gc --verify=contents`?
> If it reports anything, you might be able to repair it with `sudo guix
> gc --verify=contents,repair`.

I believe the error is because chromium is a shell script wrapper and
not an ELF binary.

I used the following script for those:

Toggle snippet (12 lines)
$ cat ~/.local/bin/run-gdb
#!/usr/bin/env bash

(
wrapper=$(cat $(which $1))
shift
. <(echo "$wrapper" | grep ^export)
binary=$(echo "$wrapper" | grep ^exec | grep -o -E '/gnu/store[^"]*')
gdb --args "$binary" "$@"
)

Then you can do:

Toggle snippet (3 lines)
run-gdb chromium

Hope that helps,

--
Thanks,
Maxim
N
N
Nicolas Graves wrote on 10 May 11:45 +0200
(address . 62217@debbugs.gnu.org)
87pltuf19p.fsf@ngraves.fr
I don't experience the issue anymore, closing it.

On 2023-03-17 13:49, Maxim Cournoyer wrote:

Toggle quote (41 lines)
> Hi,
>
> Jack Hill <jackhill@jackhill.us> writes:
>
>> On Thu, 16 Mar 2023, Nicolas Graves via Bug reports for GNU Guix wrote:
>>
>>> "/gnu/store/1jmlqw987ifnb3abr0s2hvihcg1n2xmx-ungoogled-chromium-wayland-109.0.5414.119-1/bin/chromium":
>>> not in executable format: file format not recognized
>>
>> I've run into this message in the past when my store got corrupted (in
>> my case it was a full disk on a computer that has other evil spirits
>> living in it as well). Can you check with `guix gc --verify=contents`?
>> If it reports anything, you might be able to repair it with `sudo guix
>> gc --verify=contents,repair`.
>
> I believe the error is because chromium is a shell script wrapper and
> not an ELF binary.
>
> I used the following script for those:
>
> --8<---------------cut here---------------start------------->8---
> $ cat ~/.local/bin/run-gdb
> #!/usr/bin/env bash
>
> (
> wrapper=$(cat $(which $1))
> shift
> . <(echo "$wrapper" | grep ^export)
> binary=$(echo "$wrapper" | grep ^exec | grep -o -E '/gnu/store[^"]*')
> gdb --args "$binary" "$@"
> )
> --8<---------------cut here---------------end--------------->8---
>
> Then you can do:
>
> --8<---------------cut here---------------start------------->8---
> run-gdb chromium
> --8<---------------cut here---------------end--------------->8---
>
> Hope that helps,

--
Best regards,
Nicolas Graves
N
N
Nicolas Graves wrote on 10 May 11:46 +0200
control message for bug #62217
(address . control@debbugs.gnu.org)
87msoyf19b.fsf@ngraves.fr
close 62217
quit


--
Best regards,
Nicolas Graves
?
Your comment

This issue is archived.

To comment on this conversation send an email to 62217@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 62217
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch