SOLVED frescobaldi suddenly not opening

pradtf · 2021-12-27 20:06:10

pacman -Suy came through fine though i also did:
pacman -Syu --overwrite /usr/lib/python3.10/site-packages/__pycache__/\*
as suggested on the archlinux homepage.

however, frescobaldi starts up but crashes.
running from the terminal here is the output:

schnell% frescobaldi 

(python:15460): Gtk-WARNING **: 12:01:11.347: Theme parsing error: gtk.css:5:147: Invalid name of pseudo-class

(python:15460): Gtk-WARNING **: 12:01:11.348: Theme parsing error: gtk.css:9:125: Invalid name of pseudo-class
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/panel.py", line 64, in sizeHint
    self.widget()
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/panel.py", line 71, in widget
    w = self.createWidget()
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/docbrowser/__init__.py", line 56, in createWidget
    return browser.Browser(self)
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/docbrowser/browser.py", line 86, in __init__
    self.readSettings()
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/docbrowser/browser.py", line 102, in readSettings
    ws.setFontSize(QWebEngineSettings.DefaultFixedFontSize, fixed.pointSizeF() * 96 / 72)
TypeError: setFontSize(self, QWebEngineSettings.FontSize, int): argument 2 has unexpected type 'float'
zsh: abort (core dumped)  frescobaldi

journal -b gives:

Dec 27 12:04:17 schnell audit[15572]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=15572 comm="frescobaldi" exe="/usr/bin/python3.10" sig=6 res=1
Dec 27 12:04:17 schnell kernel: audit: type=1701 audit(1640635457.162:294): auid=1000 uid=1000 gid=1000 ses=2 pid=15572 comm="frescobaldi" exe="/usr/bin/python3.10" sig=6 res=1
Dec 27 12:04:17 schnell systemd-coredump[15599]: Process 15572 (frescobaldi) of user 1000 dumped core.

the problem seems to be in the python module, but i don't know what to do about it.

Last edited by pradtf (2022-01-06 23:56:42)

V1del · 2021-12-27 20:28:29

That's an upstream bug with python 3.10 as the relevant function got more strict and needs a cast to int/general adjustment. You should report the issue to the frescobaldi devs.

Edit: https://github.com/frescobaldi/frescobaldi/issues/1398

If you have this issue with the repo package, maybe create an Arch bug instead asking for the relevant fixes in that report getting backported.

Last edited by V1del (2021-12-27 20:31:10)

lmn · 2021-12-27 20:30:41

The problem has been fixed by upstream in this commit.
So you have to wait until this makes it downstream. Since the package is build against the release version you can use frescobaldi-git instead.

pradtf · 2022-01-03 08:18:23

lmn wrote:

The problem has been fixed by upstream in this commit.
So you have to wait until this makes it downstream. Since the package is build against the release version you can use frescobaldi-git instead.

frescobaldi still doesn't open, so i guess the python fix hasn't made it downstream yet.

so i took your suggestion and tried it from aur, but got this error regarding dependencies:

==> Making package: frescobaldi-git 3.1.2.r46.gc85376f9-1 (Mon 03 Jan 2022 12:07:06 AM PST)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> qpageview
  -> tango-icon-theme
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

there is no qpageview or tango-icon-theme through pacman, so am i supposed to install the git:
https://aur.archlinux.org/packages/qpageview-git/
https://aur.archlinux.org/packages/tango-icon-theme/

also, if i install something from aur and the regular arch version gets fixed, will it simply update the aur pkg or do i need to delete that and then pacman -S?

Last edited by pradtf (2022-01-03 08:18:47)

Stefan Husmann · 2022-01-03 11:46:57

Yes, you are yourself responsible to do updates or removals, if somthing changes. You could use auracle or auracle-git to get some tool-based help.

ArchChem · 2022-01-05 14:03:01

Hello,

what helped me as a workaround is to replace the bug causing lines in the python source code of the repo version:

1. in /usr/lib/python3.10/site-packages/frescobaldi_app/qpageview/shadow.py change line 43 to:

rect = ev.rect().adjusted(int(-width), int(-width), int(width / 2), int(width / 2))

And 2. in /usr/lib/python3.10/site-packages/frescobaldi_app/docbrowser/browser.py change line 102 to:

ws.setFontSize(QWebEngineSettings.DefaultFixedFontSize, int(fixed.pointSizeF() * 96 / 72))

Hopefully the maintaners will update that soon!

Last edited by ArchChem (2022-01-05 14:03:31)

pradtf · 2022-01-05 18:14:54

ArchChem wrote:

what helped me as a workaround is to replace the bug causing lines in the python source code of the repo version:

i find it amazing how you figured this out!

from what i see, you are taking the 'float' out of the picture by changing it to 'int',
since the problem lay with the float strictness as per post by V1del.

anyway, frescobaldi opens, but i can't engrave. getting this

 File "/usr/lib/python3.10/site-packages/frescobaldi_app/progress.py", line 73, in jobStarted
    self.showProgress(document)
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/progress.py", line 59, in showProgress
    self._bar.start(buildtime, j.elapsed_time())
  File "/usr/lib/python3.10/site-packages/frescobaldi_app/widgets/progressbar.py", line 74, in start
    self._timeline.setDuration(total * 1000)
TypeError: setDuration(self, int): argument 1 has unexpected type 'float'

thx for the help though!

Last edited by pradtf (2022-01-05 18:17:45)

V1del · 2022-01-05 18:39:11

you basically need to repeat this process for every file that is mentioned failing in that way. See this reply and the referenced changes for the relevant fixes: https://github.com/frescobaldi/frescoba … 1004766411

If you want this fixed you should open a bug on bugs.archlinux.org and post the above github for reference at the minimum, or even better provide a patched PKGBUILD cherry picking these.

pradtf · 2022-01-05 18:54:33

V1del wrote:

If you want this fixed you should open a bug on bugs.archlinux.org and post the above github for reference at the minimum, or even better provide a patched PKGBUILD cherry picking these.

that's what you suggested earlier, but i thought from Imn's post that the matter was fixed and we just had to wait.

i don't know how to do the things you suggested, but now is a good time to learn this stuff!
so i'll follow your link and see what i can figure out.

i see searching on bugs.archlinux.org there is nothing for frescobaldi yet.

thx v1del!

Last edited by pradtf (2022-01-05 18:56:20)

V1del · 2022-01-05 19:18:07

Well yeah you can also just wait, but I'm not sure how far out an official release is and I'd presume the Arch packagers have a vested interest in applying fixes to currently broken software due to the release model of the distribution.

pradtf · 2022-01-05 22:14:59

V1del wrote:

Well yeah you can also just wait, but I'm not sure how far out an official release is and I'd presume the Arch packagers have a vested interest in applying fixes to currently broken software due to the release model of the distribution.

right!

well i've submitted a bug report after reading:
https://wiki.archlinux.org/title/Bug_re … guidelines

here it is:
https://bugs.archlinux.org/task/73270

and hopefully i've done it properly.

i don't understand the "provide a patched PKGBUILD cherry picking these" you mentioned since i don't really know how this bug mechanism works, but i've linked to the github item you provided as well as my journalctl and console output.

thx again for getting me to learn how to do this stuff!

Last edited by pradtf (2022-01-05 22:15:50)

pradtf · 2022-01-06 23:55:54

V1del wrote:

I'm not sure how far out an official release is .

the problem has been fixed and things work nicely after you update the package!

thx again v1del for encouraging me to submit the bug report!
now that i know what i'm doing, i can hardly wait to do the next one!

it was fixed by Caleb Maclennan (alerque) who wrote:

----------
I've cherry picked some patches from master that were Python 3.10 related (ignoring the MacOS stuff and other bug fixes). This seems to get it functional again, but the real solution is to convince upstream to cut another release sooner rather than later. I commented on the relevant issue.
----------

so the "cut another release" must be what you meant when you talked about the "official release".

as i'm understanding the landscape, upstream produces releases which work for the dependencies they were using at the time. when some of these dependencies change, such as python's, they need to make changes to the official release. however, till they do that, our archlinux folks can compensate and get things working again the way caleb did.

Arch Linux

#1 2021-12-27 20:06:10

SOLVED frescobaldi suddenly not opening

#2 2021-12-27 20:28:29

Re: SOLVED frescobaldi suddenly not opening

#3 2021-12-27 20:30:41

Re: SOLVED frescobaldi suddenly not opening

#4 2022-01-03 08:18:23

Re: SOLVED frescobaldi suddenly not opening

#5 2022-01-03 11:46:57

Re: SOLVED frescobaldi suddenly not opening

#6 2022-01-05 14:03:01

Re: SOLVED frescobaldi suddenly not opening

#7 2022-01-05 18:14:54

Re: SOLVED frescobaldi suddenly not opening

#8 2022-01-05 18:39:11

Re: SOLVED frescobaldi suddenly not opening

#9 2022-01-05 18:54:33

Re: SOLVED frescobaldi suddenly not opening

#10 2022-01-05 19:18:07

Re: SOLVED frescobaldi suddenly not opening

#11 2022-01-05 22:14:59

Re: SOLVED frescobaldi suddenly not opening

#12 2022-01-06 23:55:54

Re: SOLVED frescobaldi suddenly not opening

Board footer