Github messages for voidlinux
 help / color / mirror / Atom feed
From: LeamHall <LeamHall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: bug: XFCE PolicyKit Agent
Date: Sun, 23 Jan 2022 16:06:43 +0100	[thread overview]
Message-ID: <20220123150643.ZY1hQur0lx2XYdni4okXJJb76c4oj5jS9hGEjgKlx-8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35198@inbox.vuxu.org>

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

New comment by LeamHall on void-packages repository

https://github.com/void-linux/void-packages/issues/35198#issuecomment-1019503850

Comment:
This is an existing node with XFCE as the primary login window manager. Have been running Void on it daily, for some time. This morning's update broke things, last update was a week ago.  

Oh, here's a funny. I can ctl-alt-f1, run xuname into a file, chmod the file, and then open it with Mousepad. Some applications work, like Mousepad and Firefox. Some don't. Anyway:

Void 5.13.19_1 x86_64 GenuineIntel notuptodate rFF

The "notuptodate" doesn't inspire confidence, since I just did an update. Here's the working part of the script I use for updates.

###
date=`date +%Y%m%d`
logfile="/var/tmp/xbps-install_Suvy_${date}.log"

# Removes old kernels.
vkpurge rm all > $logfile 2>&1

# Updates, and keeps a log.
xbps-install -Suvy >> $logfile 2>&1

# Lets the system quiesce.
sleep 10

# Removes old packages that are no longer needed.
xbps-remove -O >> $logfile 2>&1

# updates the CA certificates
update-ca-certificates >> $logfile 2>&1

# Updates the locate db.
updatedb >> $logfile 2>&1

###





  parent reply	other threads:[~2022-01-23 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 14:20 [ISSUE] " LeamHall
2022-01-23 14:31 ` paper42
2022-01-23 15:06 ` LeamHall [this message]
2022-01-23 15:07 ` LeamHall
2022-01-23 20:55 ` paper42
2022-01-23 20:55 ` [ISSUE] [CLOSED] " 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=20220123150643.ZY1hQur0lx2XYdni4okXJJb76c4oj5jS9hGEjgKlx-8@z \
    --to=leamhall@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).