> So it was the mkinitcpio update. When running etc-update, I missed the
> resume hook in the mkinitcpio.conf file. Now systems goes to
> hibernation and resumes a normally.
You can now put your custom HOOKS in /etc/mkinitcpio.conf.d/my-hooks.conf
--
damjan
> I am trying to run X from within a systemd-nspawn container - this is
> something I had set up and was running successfully about three years ago,
> but something seems to have changed in the meantime and I am not able to
> recreate this.
>
> I created the container and installed X related
> > > Be Carefull i now have a totally Trashed system thanks to dbus-broker
> > > and i am not happy need to remove it and get back to dbus but it has
> > > it locked wn tight
> > Define "trashed system"?
> >
> > Take care,
>
> complete list 2 screens full of dbus failures that were NOT there
> The only thing I wonder about is that dbus-broker-units replaced
>
> /usr/lib/systemd{system,user}/dbus.service with the corresponding
> dbus-broker.service, why was /usr/lib/systemd{system,user}/dbus.socket
> left as being owned by dbus?
it's the same unit file for both services, and the dbus
> I've put some work into making it easy to install Arch Linux inside
> OSTree. I have started creating a guide at
> https://wiki.archlinux.org/title/Install_Arch_Linux_inside_OSTree with
> the intention of that being just another installation method like LUKS
> or LVM.
>
> Unfortunately, the page
> > According to
> > https://archlinux.org/packages/extra/any/python-pyrate-limiter/ the
> > current version should be 3.1.1 rather than 3.1.0 so it seems your
> > system is not up to date? Or maybe you do have the latest version but
> > some part of your system thinks you still have the previous
On Thu, 3 Aug 2023 at 12:24, David C. Rankin wrote:
>
> Arch devs,
>
>I read that systemd 254 will enable a soft-reboot similar to how windows
> does fast-boot does it. (The Register:
> https://go.reg.cx/tdml/dfd67/64f3cc7f/8aaa3ef6/49jh)
That's a huge miss-representation. Please don't read
On Sun, 23 Apr 2023 at 07:53, Ralf Mardorf wrote:
>
> Hi,
>
> assuming you can't get rid of the cause of messages flooding the log
> file, could you prevent writing with a filter? After all, only filtering
> when reading would not prevent the unnecessary growth of log files.
you didn't say which
> I saw the LD proccess consumed almost all of the machine free
> memory. And also a lot of swap. Which happend right at the LD operation,
> not before. It is only a desktop, Only 4G RAM.
I'm surprised you could've ever compiled a kernel with only 4GB Ram
People are talking here about
> > Now, I simply installed all the packages mentioned on the arch wiki
> > pipewire page
>
> The fact that you have to go to a wiki page to get your audio working
> the way you want it speaks volumes (no pun intended).
What are you talking about?
This is Arch linux, you have to go to the wiki
> Problem:
> This package is available in community, but pacman cannot find it -
> which breaks pipewire-audio due to missing soname depends.
> pacman only finds 1.3.1-1 which is missing the needed provides.
>
> Cause:
> The reason appears to be that while the package is available, it was not
>
On Mon, 16 Jan 2023 at 15:45, Markus Schaaf wrote:
> for a long time now, I'm seeing unclean shutdowns of SATA drives
> on different machines running Arch. There is a nice write-up
> about the problem here:
> https://lore.kernel.org/lkml/20170410232118.ga4...@khazad-dum.debian.net/
> If you are
> Today I encountered an error response in my browser when attempting to
> use my locally-installed Trac projects. Notice that Trac, as it is
> installed on my system, uses Python 2.x.
there's no longer python2 in ArchLinux
https://archlinux.org/news/removing-python2-from-the-repositories/
--
> here are the commands used:
>
> # ip tuntap add tap0 mode tap user me
> # ip addr add 192.168.11.254/24 dev tap0
> # ip link set tap0 down
> # echo 11 tap0 >> /etc/iproute2/rt_tables
> # ip rule add from 192.168.11.254 lookup tap0
you probably want `from 192.168.11.0/24` here
(iif tap0 should
> I doubt that it's related to the kernel. I suspect a systemd related
> race condition, but I might be completely mistaken.
Based on what?
I don't think systemd (by itself) does anything to PCI devices or
their irq workers at all.
--
damjan
On Sat, 1 Oct 2022 at 22:12, wrote:
>
> $ ldd /usr/sbin/remmina | grep libsoup
> libsoup-2.4.so.1 => /usr/lib/libsoup-2.4.so.1 (0x7fae45bde000)
you should really use readelf -d /usr/sbin/remmina | grep 'Shared
library:' instead of ldd
but in this case it does confirm the
> on the other hand, when it runs on my Lenovo ThinkPad X1 Carbon, Chromium
> has problems with the sound
Check the Arch wiki for the requirements of the exact model and
generation of X1.
a wild guess would be, you need to install `sof-firmware` but it's
hard to say without more data
--
Currently it's quite complicated to make the reference from an
installed kernel package(s) to it's files (the kernel image and
modules),
except by either invoking `pacman -Qlq linux | grep vmlinuz$` or some
heuristics like what mkinitcpio does.
So the proposal is that every kernel package should
On Tue, 16 Nov 2021 at 05:05, Paul M. Foster wrote:
>
> On 11/15/21 9:18 PM, Damjan Georgievski wrote:
> >> Well, I created this USB stick with dd. I used the basic ISO available
> >> on the Arch download mirrors. I'm assuming from what you say that a
> >> sti
> Well, I created this USB stick with dd. I used the basic ISO available
> on the Arch download mirrors. I'm assuming from what you say that a
> stick built from dd wouldn't satisfy what you're saying. If that's the
> case, how do you prepare a USB stick as a UEFI device, and then how
> would you
On Sat, 12 Jun 2021 at 13:59, Maykel Franco via arch-general
wrote:
>
> Hi, I try configure the rule in udev for when I connect specific usb
> device, launch script backup.
>
> I have this rule:
>
> /etc/udev/rules.d/10.autobackup.rules
>
> SUBSYSTEM=="block", ACTION=="add",
> But, there is no added rule in /etc/udev/rules.d/. Just showing the usual two.
Udev rules from packages are installed in /usr/lib/udev/rules.d/
(and they don't appear or disappear when the device is plugged in)
--
damjan
On Wed, 24 Mar 2021 at 02:10, riveravaldez via arch-general
wrote:
>
> Hi, I was using Wicd until a couple of weeks without problems,
> but because it's been out of repos for a while and generally not
> maintained/developed anymore I decided to make the switch and
> start using systemd-networkd.
> Em fevereiro 22, 2021 10:23 JustKidding via arch-general escreveu:
> > Do I have to wait for kernel 5.11 in order to use zstd?
> >
>
> No, zstd is supported since kernel 5.9.
The unfortunate consequence of this is that currently Arch only has
5.10 kernels available, and a mkinitcpio that by
24 matches
Mail list logo
