Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ReText won't open after install
Date: Tue, 11 Apr 2023 22:18:25 +0200	[thread overview]
Message-ID: <20230411201825.qqxXyWW45fhebfbOE0tEyK08JRJMe7y1XQ-b7x-2Hmk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43323@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Closed issue by matthew-yates on void-packages repository

https://github.com/void-linux/void-packages/issues/43323

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.21_1 x86_64 GenuineIntel uptodate rrFFF

### Package(s) Affected

ReText-7.2.1_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

ReText window should open.

### Actual behaviour

Starting retext from the command line reveals an error in:

/usr/lib/python3.11/site-packages/ReText/window.py

It states an integer is expected in line 89, but a float is there instead.  I edited line 89 from:

self.splitter.setSizes([self.width() / 5, self.width() * 4 / 5])

to:

self.splitter.setSizes([int(self.width() / 5), int(self.width() * 4 / 5)])

Not sure if that is the correct bug fix, but ReText opens as expected now after making that edit.

### Steps to reproduce

1. xbps-install ReText
2. Try to open ReText from a graphical menu and nothing happens.

      parent reply	other threads:[~2023-04-11 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 15:25 [ISSUE] " matthew-yates
2023-04-08 12:23 ` mhmdanas
2023-04-11 20:18 ` classabbyamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230411201825.qqxXyWW45fhebfbOE0tEyK08JRJMe7y1XQ-b7x-2Hmk@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).