From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: ly-0.5.2
Date: Thu, 06 Aug 2020 04:30:06 +0200 [thread overview]
Message-ID: <20200806023006.vmnYINGpTxfuB2CXItadogdIpHSbDZ2nit2RRXnfPg0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24038@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/24038#issuecomment-669646361
Comment:
@ericonr I didn't think to check my dmesg logs before, but it's segfaulting for me as well. Here's what I believe to be the relevant portion of the logs:
```
[17802.088814] elogind-daemon[1786]: New session 3 of user erebus.
[17802.118293] ly[22191]: segfault at 0 ip 00007f8a457453e1 sp 00007ffc0c1a7248 error 4 in libc-2.30.so[7f8a4560c000+149000]
[17802.118304] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1
[17822.337659] elogind-daemon[1786]: Removed session 3.
```
This means that it's not actually a PAM problem but a full-on crashing problem, right?
next prev parent reply other threads:[~2020-08-06 2:30 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 5:01 [PR PATCH] " cinerea0
2020-08-04 5:25 ` cinerea0
2020-08-04 5:34 ` ericonr
2020-08-04 5:37 ` [PR REVIEW] " ericonr
2020-08-04 5:37 ` ericonr
2020-08-04 5:37 ` ericonr
2020-08-04 5:37 ` ericonr
2020-08-04 5:37 ` ericonr
2020-08-04 5:37 ` ericonr
2020-08-04 13:45 ` ericonr
2020-08-04 13:45 ` ericonr
2020-08-04 13:56 ` [PR REVIEW] " ericonr
2020-08-04 14:30 ` ericonr
2020-08-04 15:36 ` [PR REVIEW] " cinerea0
2020-08-04 15:39 ` cinerea0
2020-08-04 15:40 ` cinerea0
2020-08-04 15:41 ` cinerea0
2020-08-04 15:51 ` ericonr
2020-08-04 15:56 ` cinerea0
2020-08-04 15:59 ` cinerea0
2020-08-04 17:20 ` [PR REVIEW] " ericonr
2020-08-04 17:21 ` ericonr
2020-08-04 17:27 ` ericonr
2020-08-05 0:13 ` [PR REVIEW] " cinerea0
2020-08-05 0:20 ` cinerea0
2020-08-05 0:32 ` cinerea0
2020-08-05 1:33 ` ericonr
2020-08-05 1:34 ` ericonr
2020-08-05 1:42 ` [PR PATCH] [Updated] " cinerea0
2020-08-05 1:53 ` [PR REVIEW] " cinerea0
2020-08-05 1:55 ` cinerea0
2020-08-05 2:44 ` ericonr
2020-08-05 2:46 ` ericonr
2020-08-05 2:47 ` ericonr
2020-08-05 2:48 ` ericonr
2020-08-05 4:08 ` [PR PATCH] [Updated] " cinerea0
2020-08-05 4:10 ` [PR REVIEW] " cinerea0
2020-08-05 4:18 ` ericonr
2020-08-05 4:18 ` ericonr
2020-08-05 4:39 ` cinerea0
2020-08-05 4:40 ` cinerea0
2020-08-05 4:46 ` [PR PATCH] [Updated] " cinerea0
2020-08-05 4:49 ` [PR REVIEW] " cinerea0
2020-08-05 4:52 ` cinerea0
2020-08-05 18:26 ` ericonr
2020-08-06 0:30 ` ericonr
2020-08-06 1:05 ` [PR REVIEW] " ericonr
2020-08-06 2:00 ` [PR PATCH] [Updated] " cinerea0
2020-08-06 2:04 ` [PR REVIEW] " cinerea0
2020-08-06 2:30 ` cinerea0 [this message]
2020-08-06 2:37 ` ericonr
2020-08-06 2:37 ` ericonr
2020-08-06 3:36 ` ericonr
2020-08-06 3:46 ` ericonr
2020-08-06 4:00 ` ericonr
2020-08-06 4:50 ` [PR PATCH] [Updated] " cinerea0
2020-08-06 4:53 ` cinerea0
2020-08-06 5:19 ` ericonr
2020-08-06 13:39 ` cinerea0
2020-08-06 14:37 ` ericonr
2020-08-06 14:49 ` [PR REVIEW] " ericonr
2020-08-06 15:13 ` cinerea0
2020-08-06 15:23 ` ericonr
2020-08-06 19:32 ` [PR PATCH] [Updated] " cinerea0
2020-08-06 19:33 ` [PR REVIEW] " cinerea0
2020-08-06 19:38 ` [WIP] " cinerea0
2020-08-06 19:42 ` ericonr
2020-08-06 20:16 ` cinerea0
2020-08-06 20:34 ` ericonr
2020-08-06 21:18 ` cinerea0
2020-08-06 21:44 ` ericonr
2020-08-06 23:41 ` cinerea0
2020-08-10 19:37 ` cinerea0
2020-08-11 14:45 ` PaperMountainStudio
2020-08-11 19:38 ` cinerea0
2020-08-11 19:41 ` PaperMountainStudio
2020-08-12 1:58 ` [PR PATCH] [Updated] " cinerea0
2020-08-12 2:36 ` cinerea0
2020-08-13 14:41 ` cinerea0
2021-11-06 22:37 ` [PR PATCH] [Closed]: [WIP] " abenson
2021-11-06 22:37 ` abenson
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=20200806023006.vmnYINGpTxfuB2CXItadogdIpHSbDZ2nit2RRXnfPg0@z \
--to=cinerea0@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).