Bug#1010048: fs-uae-launcher: GUI is corrupted.

waxhead

unread,

Apr 23, 2022, 3:40:03 AM4/23/22

to

Package: fs-uae-launcher
Version: 3.0.5+dfsg-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: wax...@dirtcellar.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?

Tried to start fs-uae-launcher, the GUI looks "corrupted" like below...

+------------------------+
|[start] [][][] |
| |
|+---------+ |
|[cfgwindow] |
|| | |
|+---------+ |
+------------------------+

A start button, a config windows and some widgets overlapping [][][].

* What exactly did you do (or not do) that was effective (or
ineffective)?

I tried to resize the window and update all packages.

* What was the outcome of this action?

The GUI is still corrupted... No change.

* What outcome did you expect instead?

Nothing really, was hoping it would "fix" itself by a resize, but it did not.

*** End of the template - remove these template lines ***

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fs-uae-launcher depends on:
ii fs-uae 3.1.66-1
ii python3 3.10.4-1
ii python3-pyqt5 5.15.6+dfsg-1+b2
ii python3-pyqt5.qtopengl 5.15.6+dfsg-1+b2
ii python3-setuptools 59.6.0-1.2

fs-uae-launcher recommends no packages.

fs-uae-launcher suggests no packages.

-- no debconf information

John Paul Adrian Glaubitz

unread,

Apr 24, 2022, 3:50:03 AM4/24/22

to

Control: severity -1 normal

On 4/23/22 09:26, waxhead wrote:
> Tried to start fs-uae-launcher, the GUI looks "corrupted" like below...
>
> +------------------------+
> |[start] [][][] |
> | |
> |+---------+ |
> |[cfgwindow] |
> || | |
> |+---------+ |
> +------------------------+
>
> A start button, a config windows and some widgets overlapping [][][].

> (...)

> -- System Information:
> Debian Release: bookworm/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386

fs-uae-launcher is currently not part of Debian unstable or testing due to insufficient
clarification of the copyright of various files shipped with the source code, see [1].

However, the package is part of the stable distribution and works fine there, just tested
it on a freshly installed system. Thus, you are using the stable package on Debian testing
which may result the bug you described.

But since the package isn't part of testing/unstable anyway, I don't really consider this
to be a valid bug report. Therefore downgrading the severity to normal.

Adrian

> [1] https://github.com/FrodeSolheim/fs-uae-launcher/issues/143

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

waxhead

unread,

Apr 25, 2022, 5:50:02 PM4/25/22

to

Allrighty , that is fair enough. Have to cross our fingers that an
update is near then.

Miguel A. Vallejo

unread,

Nov 20, 2023, 4:20:05 PM11/20/23

to

Hello

I revisited https://github.com/FrodeSolheim/fs-uae-launcher/issues/143
and I noticed user glaubitz is open to make the changes needed to have
this package back in Debian.

Dear maintainer, please explain to GitHub / glaubitz what is needed to
have fs-uae-launcher back in Debian.

Thank you

Miguel A. Vallejo

unread,

Nov 21, 2023, 9:20:07 AM11/21/23

to

What a plot twist! :-)

Do you think there is any possibility to have fs-uae-launcher back in
Debian anytime soon?

Configuring FS-UAE by hand is tedious. we really need fs-uae-launcher
back in Debian

Thank you

Andreas Kohlbach

unread,

Jan 11, 2024, 6:10:06 PM1/11/24

to

Package: fs-uae-launcher
Version: 3.0.5+dfsg-1
Followup-For: Bug #1010048
X-Debbugs-Cc: a...@spamfence.net

Dear Maintainer,

* What led up to the situation?

Just starting the program.

* What exactly did you do (or not do) that was effective (or
ineffective)?

Nothing. Just started the programm resulting in a "strange looking" screen.

* What was the outcome of this action?

The GUI cannot be used.

I took a screeshot at https://bashify.io/i/Za1D75 .

Note: UAE itself works, starting it from the command line. It's the launcher causing the problem.

A (uneducated) guess: It might be a problem with GTK or another framework responsible for displaying. But everything else I run causes no problem with its GUI.

* What outcome did you expect instead?

The GUI to work.

-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fs-uae-launcher depends on:

ii fs-uae 3.1.66-2
ii python3 3.11.2-1+b1
ii python3-pyqt5 5.15.9+dfsg-1
ii python3-pyqt5.qtopengl 5.15.9+dfsg-1
ii python3-setuptools 66.1.1-1