From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] The current i3-4.19.1_1 package appears to be a development version with coredumps enabled
Date: Sun, 07 Feb 2021 17:21:00 +0100 [thread overview]
Message-ID: <20210207162100.C2xXiB-VrP63I9n0BQfMlINbR_IQaePISqO9Ie4hNeo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28545@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Closed issue by paoloschi on void-packages repository
https://github.com/void-linux/void-packages/issues/28545
Description:
Although I have not set the -d option for debugging, after the recent update i3 generates a 25Mb dump file named 'i3-log-NNN' that starts as follows:
```
/dev/shm $ head i3-log-833
u�*��06/02/2021 09:59:06 - CORE DUMPS: You are running a development version of i3, so coredumps were automatically enabled (ulimit -c unlimited).
06/02/2021 09:59:06 - CORE DUMPS: Your current working directory is "/dev/shm".
06/02/2021 09:59:06 - CORE DUMPS: Your core_pattern is: core
06/02/2021 09:59:06 - i3 4.19.1-non-git starting
06/02/2021 09:59:06 - ../libi3/dpi.c:init_dpi:42 - Resource Xft.dpi not specified, skipping.
06/02/2021 09:59:06 - ../libi3/dpi.c:init_dpi:65 - Using fallback for calculating DPI.
06/02/2021 09:59:06 - ../libi3/dpi.c:init_dpi:67 - Using dpi = 96
06/02/2021 09:59:06 - ../src/main.c:main:604 - root_depth = 32, visual_id = 0x00000079.
06/02/2021 09:59:06 - ../src/main.c:main:605 - root_screen->height_in_pixels = 1200, root_screen->height_in_millimeters = 317
06/02/2021 09:59:06 - ../src/main.c:main:607 - One logical pixel corresponds to 1 physical pixels on this display.
```
prev parent reply other threads:[~2021-02-07 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 9:52 [ISSUE] " paoloschi
2021-02-07 16:21 ` sgn [this message]
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=20210207162100.C2xXiB-VrP63I9n0BQfMlINbR_IQaePISqO9Ie4hNeo@z \
--to=sgn@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).