From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Scribus is bugged
Date: Mon, 13 Dec 2021 12:12:03 +0100 [thread overview]
Message-ID: <20211213111203.4D0-IfMdQ7w-HrfP0SmKvvjVamteipo8OMQyOS7fUew@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34510@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Closed issue by notthewave on void-packages repository
https://github.com/void-linux/void-packages/issues/34510
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*Void 5.15.7_1 x86_64-musl GenuineIntel uptodate rrDFFFFFFFFFFFFFFFFFF*
* package:
*affected package(s) including the version*: ``scribus-1.5.7_6``
### Expected behavior
- dropdown menus stay within the screen area
- the font menu is displayed normally
### Actual behavior
- dropdown go past the screen edge
- when selecting a font, the menu has graphical glitches
### Steps to reproduce the behavior
- open one of the dropdown menus
- choose a font when editing text
This happens on X as well as in Wayland
Also why ship development releases?
next prev parent reply other threads:[~2021-12-13 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 9:59 [ISSUE] " notthewave
2021-12-13 10:36 ` paper42
2021-12-13 10:43 ` notthewave
2021-12-13 10:43 ` notthewave
2021-12-13 10:43 ` notthewave
2021-12-13 10:47 ` notthewave
2021-12-13 10:52 ` notthewave
2021-12-13 10:53 ` notthewave
2021-12-13 10:53 ` notthewave
2021-12-13 10:53 ` notthewave
2021-12-13 10:55 ` notthewave
2021-12-13 11:00 ` notthewave
2021-12-13 11:01 ` notthewave
2021-12-13 11:12 ` notthewave
2021-12-13 11:12 ` notthewave [this message]
2021-12-13 15:18 ` notthewave
2021-12-13 16:34 ` notthewave
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=20211213111203.4D0-IfMdQ7w-HrfP0SmKvvjVamteipo8OMQyOS7fUew@z \
--to=notthewave@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).