Github messages for voidlinux
 help / color / mirror / Atom feed
From: hervyqa <hervyqa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] obs: segfault (wayland)
Date: Sun, 16 Oct 2022 13:39:53 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39987@inbox.vuxu.org> (raw)

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

New issue by hervyqa on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

`Void 6.0.1_1 x86_64 AuthenticAMD uptodate FFFFFFF`

### Package(s) Affected

`obs-28.0.3_1`

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

-

### Expected behaviour

runs normally before plasma 5.26. after system upgrade obs can't run on wayland. but on x11 it works fine.
I think it needs to be rebuilt.

### Actual behaviour

```
➜  ~ obs
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb.

fish: Job 1, 'obs' terminated by signal SIGABRT (Abort)
```

### Steps to reproduce

- `doas xbps-install -S obs`
- open `obs`

             reply	other threads:[~2022-10-16 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 11:39 hervyqa [this message]
2022-10-16 11:49 ` paper42
2022-10-16 11:58 ` hervyqa
2022-10-16 11:58 ` [ISSUE] [CLOSED] " hervyqa
2022-10-16 12:14 ` paper42

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39987@inbox.vuxu.org \
    --to=hervyqa@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).