From: jchook <jchook@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Skype segfaults when joining a call
Date: Sat, 06 Mar 2021 00:35:48 +0100 [thread overview]
Message-ID: <20210305233548.DRsyhYohJxSH0YwxC3hAs4NhyfZ9BucknFYXKaTEREk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29164@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
New comment by jchook on void-packages repository
https://github.com/void-linux/void-packages/issues/29164#issuecomment-791777893
Comment:
Hm, thanks for trying @mobinmob. I have a hard time reproducing this issue on a fresh VM.
Somehow I got one "general protection fault", similar to this, where the call failed with a loading animation and then dumped me out to the login screen. Now calls to the VM seem to work fine lol. No idea why.
```
2021-03-05T23:00:56.12863 kern.info: [ 226.306155] traps: skypeforlinux[1437] general protection fault ip:7ffa673a0214 sp:7ffa64972ad8 error:0 in slimcore.node[7ffa64ef8000+2e3e000]
```
Here's roughly what I tried...
1. Install void base on a new VM (I used libvirt / virt-manager)
2. Boot VM and login as root
3. Install some software
```sh
xbps-install -Suy
xbps-install -Suy xorg i3 i3status dmenu alacritty void-repo-nonfree void-socklog
xbps-install -S
xbps-install skype
ln -s /etc/sv/socklog-unix /var/services/
ln -s /etc/sv/nanoklogd /var/services/
```
4. Logout and log-in as a non-root user
5. Set-up X11
```sh
echo "i3" > ~/.xinitrc
startx
```
6. Launch skype + login
7. Initiate a voice call from another account + device
I did futz around with `xbps-reconfigure` and installing intel microcode, as well as dbus... perhaps related, but I feel kinda stumped now.
Edit:
Very strangely, if I change my xinitrc (on the problematic host machine) to use `xmonad` instead of `exec xmonad` I no longer get the segfault.
next prev parent reply other threads:[~2021-03-05 23:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:00 [ISSUE] " jchook
2021-03-02 6:41 ` jchook
2021-03-02 6:43 ` jchook
2021-03-02 6:46 ` jchook
2021-03-02 6:48 ` jchook
2021-03-02 6:52 ` jchook
2021-03-02 6:52 ` jchook
2021-03-02 13:46 ` ericonr
2021-03-02 13:59 ` mobinmob
2021-03-02 14:04 ` mobinmob
2021-03-02 14:22 ` mobinmob
2021-03-02 20:00 ` jchook
2021-03-04 20:07 ` mobinmob
2021-03-05 23:07 ` jchook
2021-03-05 23:35 ` jchook [this message]
2021-04-27 23:50 ` ericonr
2021-05-29 14:34 ` mobinmob
2021-05-31 9:52 ` mobinmob
2021-06-06 2:33 ` jchook
2021-06-06 2:33 ` [ISSUE] [CLOSED] " jchook
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=20210305233548.DRsyhYohJxSH0YwxC3hAs4NhyfZ9BucknFYXKaTEREk@z \
--to=jchook@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).