Re: Debian "Bookworm" Installation

[Peter Hillier-Brook]

On 14/04/2022 09:57, Christian Britz wrote:



On 2022-04-14 01:07 UTC+0200, Peter Hillier-Brook wrote:


I've just attempted to Install "Bookworm" to a USB stick and it went
mostly to plan, apart from the fact that it won't boot. However that's
not the issue at hand: I can't find a way to persuade  the installer's
partitioner to use GPT instead of the MS-DOS partitioning scheme.


The installer should choose UEFI or BIOS mode depending on the settings
of your firmware. Do you have previous experiences with a non-usb storage?

Regards,
Christian


Many thanks to all for the useful tips. The problem is now solved.

Peter HB

Re: What happened?

[Dan Ritter]

Stefan Monnier wrote: 
> > My guess is that the upgrade in question was carried out while the VM
> > was running, and when the upgrade tried to unload one or more relevant
> > kernel modules, the kernel refused to let that happen because the module
> > was in use.
> 
> Hmm... I can't remember ever seeing an upgrade remove kernel modules.
> When/why would that happen?

Doing this while running is odd. However --

ZFS is supplied via DKMS, which needs to have the proper version
of kernel headers installed to build it. There are configuration
choices which can be made so that:

- with kernel v1, headers v1 are installed and DKMS builds ZFS

- an apt upgrade occurs, installing kernel v2

- with kernel v2, headers v2 are not installed and DKMS cannot
build ZFS. After reboot, ZFS pools cannot be found.

In which case installing v2 of the headers will allow DKMS to
rebuild ZFS, and pools will either be automatically found or can
be found with 'zfs import'.

-dsr-

Re: What happened?

[The Wanderer]

On 2022-04-17 at 01:26, Stefan Monnier wrote:

>> My guess is that the upgrade in question was carried out while the
>> VM was running, and when the upgrade tried to unload one or more
>> relevant kernel modules, the kernel refused to let that happen
>> because the module was in use.
> 
> Hmm... I can't remember ever seeing an upgrade remove kernel
> modules. When/why would that happen?

I don't remember the specifics in detail, but I know it involves DKMS at
some stage.

I wouldn't necessarily expect it to happen even with the "rebuild module
on package update" model used with DKMS, but as I said, I know I've
*seen* it happen - with VirtualBox, quite some years ago now.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Issues running TigerVNC on Debian WSL-2

[mwoodpatrick]

I installed TigerVNC on my WSL-2 based Debian distro and installed TogerVNC
using:

 

sudo apt-get install tigervnc-standalone-server

 

It installed version TigerVNC 1.11.0 but TigerVNC 1.12.0 has been out since
last November is there a reason the package version has not been updated?

 

In trying to run TigerVNC using:

 

Vncserver :1

 

To display on display 1 (since 0 is Microsoft Wayland) I get:

 

=== tail /home/mwoodpatrick/.vnc/MarkSpectre14.:5901.log
===

_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno =
11
 

_XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix

 

Anyone know why this is failing, is anyone able to run TigerVNC on WSL-2
Debian

 

Any pointers would be most helpful

 

Regards

 

Mark

 

 

 

 

Re: Issues running TigerVNC on Debian WSL-2

[Greg Wooledge]

On Sun, Apr 17, 2022 at 07:20:58AM -0700, mwoodpatr...@gmail.com wrote:
> === tail /home/mwoodpatrick/.vnc/MarkSpectre14.:5901.log
> ===
> 
> _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno =
> 11

errno 11 is EAGAIN, "Try again".  How strange.

I would check the ownership and permissions and fullness of your /tmp
directory.  Make sure everything looks all right.

Also see whether there's a /tmp/.X11-unix directory.  Here's what I have:

unicorn:~$ ls -ld /tmp /tmp/.X11-unix
drwxrwxrwt 29 root root 73728 Apr 17 09:19 /tmp
drwxrwxrwt  2 root root  4096 Mar 26 08:02 /tmp/.X11-unix

Note the world-writability with sticky bits.

RE: Issues running TigerVNC on Debian WSL-2

[mwoodpatrick]

Many thanks for the response. Much appreciated

Permissions look ok

ls -ld /tmp /tmp/.X11-unix
 drwxrwxrwt 2 root root 4096 Apr 17 09:31 /tmp
 lrwxrwxrwx 1 root root   19 Apr 17 09:31 /tmp/.X11-unix ->
/mnt/wslg/.X11-unix

ls -ld /mnt/wslg/.X11-unix
drwxrwxrwx 2 root root 60 Apr 17 09:31 /mnt/wslg/.X11-unix

I have write access to both locations

Regards

Mark

-Original Message-
From: Greg Wooledge  
Sent: Sunday, April 17, 2022 7:47 AM
To: debian-user@lists.debian.org
Subject: Re: Issues running TigerVNC on Debian WSL-2

On Sun, Apr 17, 2022 at 07:20:58AM -0700, mwoodpatr...@gmail.com wrote:
> === tail 
> /home/mwoodpatrick/.vnc/MarkSpectre14.:5901.log
> ===
> 
> _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, 
> errno =
> 11

errno 11 is EAGAIN, "Try again".  How strange.

I would check the ownership and permissions and fullness of your /tmp
directory.  Make sure everything looks all right.

Also see whether there's a /tmp/.X11-unix directory.  Here's what I have:

unicorn:~$ ls -ld /tmp /tmp/.X11-unix
drwxrwxrwt 29 root root 73728 Apr 17 09:19 /tmp drwxrwxrwt  2 root root
4096 Mar 26 08:02 /tmp/.X11-unix

Note the world-writability with sticky bits.

Re: Issues running TigerVNC on Debian WSL-2

[Greg Wooledge]

On Sun, Apr 17, 2022 at 10:59:44AM -0700, mwoodpatr...@gmail.com wrote:
> Many thanks for the response. Much appreciated
> 
> Permissions look ok
> 
> ls -ld /tmp /tmp/.X11-unix
>  drwxrwxrwt 2 root root 4096 Apr 17 09:31 /tmp
>  lrwxrwxrwx 1 root root   19 Apr 17 09:31 /tmp/.X11-unix ->
> /mnt/wslg/.X11-unix
> 
> ls -ld /mnt/wslg/.X11-unix
> drwxrwxrwx 2 root root 60 Apr 17 09:31 /mnt/wslg/.X11-unix
> 
> I have write access to both locations

That looks incredibly not OK.  You're doing something unusual, and
you are going to have to deal with the consequences of that.  This
may include running afoul of various things like AppArmor that are
restricting access to specific directory trees, which you are no longer
in.

I can't imagine what benefit you think you're deriving from this
convoluted setup, but whatever it is, I hope it's worth the pain you're
going to experience, trying to track down all of the things you've
broken.

(You've also forgotten the sticky bit on your mounted directory.)

Re: Issues running TigerVNC on Debian WSL-2

[Mark Wood-Patrick]

I need to run on Debian under WSL-2 and want to be able to use Microsoft
Wayland as display 0 and want to have VNC access to the system.

Can you elaborate on exactly what your concerns are and how you would
resolve them and on your comment about the sticky bit, any links on these
issues would be appreciated

Regards

Mark

On Sun, Apr 17, 2022 at 11:07 AM Greg Wooledge  wrote:

> On Sun, Apr 17, 2022 at 10:59:44AM -0700, mwoodpatr...@gmail.com wrote:
> > Many thanks for the response. Much appreciated
> >
> > Permissions look ok
> >
> > ls -ld /tmp /tmp/.X11-unix
> >  drwxrwxrwt 2 root root 4096 Apr 17 09:31 /tmp
> >  lrwxrwxrwx 1 root root   19 Apr 17 09:31 /tmp/.X11-unix ->
> > /mnt/wslg/.X11-unix
> >
> > ls -ld /mnt/wslg/.X11-unix
> > drwxrwxrwx 2 root root 60 Apr 17 09:31 /mnt/wslg/.X11-unix
> >
> > I have write access to both locations
>
> That looks incredibly not OK.  You're doing something unusual, and
> you are going to have to deal with the consequences of that.  This
> may include running afoul of various things like AppArmor that are
> restricting access to specific directory trees, which you are no longer
> in.
>
> I can't imagine what benefit you think you're deriving from this
> convoluted setup, but whatever it is, I hope it's worth the pain you're
> going to experience, trying to track down all of the things you've
> broken.
>
> (You've also forgotten the sticky bit on your mounted directory.)
>
>

-- 
Mark Wood-Patrick

Re: slrn broke after power failure

[Charlie Gibbs]

On Sat, 16 Apr 2022 05:40:02 +0200 songbird 
wrote:

["Server read failed." when trying to enter a newsgroup]

>  i have four thoughts.
>
>  first one would be to do a fsck on that file system (after
> unmounting it).

No joy

>  second one is to restore from backup or redownload articles
> after running the expire process.

I've tried the "c" (catchup) command, but that didn't help.

>  third one would be to start over with a clean spool and
> then just grab the most recent few hundred articles for
> each newsgroup you want to read.
>
>  and the last is maybe the least intrusive would be to test
> something out by deleting an empty file.  will you be able
> to redownload it?  try it and see what happens for one article
> and if you can then perhaps you can write a script that would
> get rid of all the zero length files and then be able to redownload
> them or expire them or something.

The zero-length files were easy enough to find, and few enough
that I just deleted them by hand.  No luck.  I've even tried
deleting the entire contents of a group, e.g.:

rm /var/spool/slrnpull/news/linux/debian/user/*

Still no luck.  The group header window still shows the number
of messages that were available; the "c" command resets this to
zero, but I still get "Server read failed." when trying to enter
the group.

Oddly enough, there are one or two groups which are still
working properly.

>  i'm not at all familiar with slrn's spooling or structure since
> i've been using leafnode ever since i started usenet.  leafnode
> has a process that goes through and checks consistency and will
> rebuild an overview file for a group but i've never had a problem
> with it truncating contents to zero.

I was hoping that there was an slrn guru who could explain all this.

Oh well, I've been meaning to upgrade my laptop to Bullseye -
maybe it's time to nuke slrn and re-install it from scratch.

--
cgi...@surfnaked.ca (Charlie Gibbs)

Re: Issues running TigerVNC on Debian WSL-2

[The Wanderer]

On 2022-04-17 at 14:07, Greg Wooledge wrote:

> On Sun, Apr 17, 2022 at 10:59:44AM -0700, mwoodpatr...@gmail.com wrote:
>
>> Many thanks for the response. Much appreciated
>> 
>> Permissions look ok
>> 
>> ls -ld /tmp /tmp/.X11-unix
>>  drwxrwxrwt 2 root root 4096 Apr 17 09:31 /tmp
>>  lrwxrwxrwx 1 root root   19 Apr 17 09:31 /tmp/.X11-unix ->
>> /mnt/wslg/.X11-unix
>> 
>> ls -ld /mnt/wslg/.X11-unix
>> drwxrwxrwx 2 root root 60 Apr 17 09:31 /mnt/wslg/.X11-unix
>> 
>> I have write access to both locations
> 
> That looks incredibly not OK.  You're doing something unusual, and
> you are going to have to deal with the consequences of that.  This
> may include running afoul of various things like AppArmor that are
> restricting access to specific directory trees, which you are no longer
> in.
> 
> I can't imagine what benefit you think you're deriving from this
> convoluted setup, but whatever it is, I hope it's worth the pain you're
> going to experience, trying to track down all of the things you've
> broken.

I don't think this is something he broke himself; from the little I've
found, this appears to be something that's recommended or even required
for WSLg (the Windows Subsystem for Linux GUI) to work. See e.g.
https://github.com/microsoft/wslg/issues/193#issuecomment-841341256 for
one indication that that may be the case.

It is, of course, always possible that other software might not be
compatible with doing this - and, honestly, if I were trying to debug
this I'd probably start by getting the source of TigerVNC and
experimenting with changing things around there.

> (You've also forgotten the sticky bit on your mounted directory.)

While that's certainly not ideal, I can't see how it could cause the
exhibited behavior in this case; from what I can find reading up on the
sticky bit to refresh my memory, having it unset should just result in
being able to do *more* things with/inside the directory than would be
the case if it were set.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: What happened?

[Charles Curley]

On Sun, 17 Apr 2022 07:06:44 -0400
Dan Ritter  wrote:

> Doing this while running is odd. However --
> 
> ZFS is supplied via DKMS, which needs to have the proper version
> of kernel headers installed to build it. There are configuration
> choices which can be made so that:
> 
> - with kernel v1, headers v1 are installed and DKMS builds ZFS
> 
> - an apt upgrade occurs, installing kernel v2
> 
> - with kernel v2, headers v2 are not installed and DKMS cannot
> build ZFS. After reboot, ZFS pools cannot be found.
> 
> In which case installing v2 of the headers will allow DKMS to
> rebuild ZFS, and pools will either be automatically found or can
> be found with 'zfs import'.

Hmmm. Would installing linux-image-amd64 (or arch as appropriate) solve
that by bringing in the new headers at the same time it brought in a new
kernel?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Issues running TigerVNC on Debian WSL-2

[Greg Wooledge]

On Sun, Apr 17, 2022 at 03:44:33PM -0400, The Wanderer wrote:
> I don't think this is something he broke himself; from the little I've
> found, this appears to be something that's recommended or even required
> for WSLg (the Windows Subsystem for Linux GUI) to work.

*shudder*

> > (You've also forgotten the sticky bit on your mounted directory.)
> 
> While that's certainly not ideal, I can't see how it could cause the
> exhibited behavior in this case; from what I can find reading up on the
> sticky bit to refresh my memory, having it unset should just result in
> being able to do *more* things with/inside the directory than would be
> the case if it were set.

Well, some applications may check the permissions on the directory,
see that they are set wrong, and refuse to operate.  I have no idea
whether their VNC server is one of them, but there's certainly
precedent.

But as soon as I saw they had made a symlink from a standard location
to a nonstandard location, I *immediately* thought of AppArmor, because
that has been an issue so many times in the past with so many apps.

I don't know precisely why the EAGAIN errno is happening, but it isn't
EACCES so it's not a direct refusal by file system permissions, and it's
not EPERM so it's not a direct refusal for not being superuser.  It's also
not ENOSPC (disk full), so I don't think it's due to a full file system,
but it doesn't take much effort to check that, so I would check anyway.

Re: What happened?

[Dan Ritter]

Charles Curley wrote: 
> On Sun, 17 Apr 2022 07:06:44 -0400
> Dan Ritter  wrote:
> 
> > Doing this while running is odd. However --
> > 
> > ZFS is supplied via DKMS, which needs to have the proper version
> > of kernel headers installed to build it. There are configuration
> > choices which can be made so that:
> > 
> > - with kernel v1, headers v1 are installed and DKMS builds ZFS
> > 
> > - an apt upgrade occurs, installing kernel v2
> > 
> > - with kernel v2, headers v2 are not installed and DKMS cannot
> > build ZFS. After reboot, ZFS pools cannot be found.
> > 
> > In which case installing v2 of the headers will allow DKMS to
> > rebuild ZFS, and pools will either be automatically found or can
> > be found with 'zfs import'.
> 
> Hmmm. Would installing linux-image-amd64 (or arch as appropriate) solve
> that by bringing in the new headers at the same time it brought in a new
> kernel?

No, you need linux-image-amd64 and linux-headers-amd64

If you've specified versions of these instead, the headers don't
follow along automatically.

-dsr-

Re: Issues running TigerVNC on Debian WSL-2

[The Wanderer]

On 2022-04-17 at 18:16, Greg Wooledge wrote:

> On Sun, Apr 17, 2022 at 03:44:33PM -0400, The Wanderer wrote:

[that in an earlier message, Greg Wooledge wrote:]

>>> (You've also forgotten the sticky bit on your mounted
>>> directory.)
>> 
>> While that's certainly not ideal, I can't see how it could cause
>> the exhibited behavior in this case; from what I can find reading
>> up on the sticky bit to refresh my memory, having it unset should
>> just result in being able to do *more* things with/inside the
>> directory than would be the case if it were set.
> 
> Well, some applications may check the permissions on the directory,
> see that they are set wrong, and refuse to operate.  I have no idea
> whether their VNC server is one of them, but there's certainly 
> precedent.

Given the error messages being displayed, I don't think it likely that
this is the result of a failed permissions check; it looks as if the
program called mkdir() on the specified path, and is just dealing with
the error code returned by that function call.

I initially thought this was the C library's mkdir() (see 'man 2 mkdir')
- but since that appears to require a second argument to specify the
mode, and there's only one argument presented here, I'm not so sure of
that anymore. This might even be some higher-level language that's
layered over top of the C mkdir(), which would make it even messier to
try to understand.

> But as soon as I saw they had made a symlink from a standard
> location to a nonstandard location, I *immediately* thought of
> AppArmor, because that has been an issue so many times in the past
> with so many apps.

I would be surprised if the WSL2 version of Debian was using AppArmor
enabled by default, but I suppose it's hard to rule anything out,
especially when it comes to Microsoft.

> I don't know precisely why the EAGAIN errno is happening, but it
> isn't EACCES so it's not a direct refusal by file system permissions,
> and it's not EPERM so it's not a direct refusal for not being
> superuser.  It's also not ENOSPC (disk full), so I don't think it's
> due to a full file system, but it doesn't take much effort to check
> that, so I would check anyway.

Assuming this *is coming from the mkdir() C library function, it gets
weirder. On my own (non-WSL-based) Debian system, the man page does not
list EAGAIN for that function.

(I'll note that multiple man pages say that errno 11 may legally be,
and/or specifically is, used for both EAGAIN and EWOULDBLOCK. I can't
see why the latter would make any more sense here than the former,
though.)

I think this almost has to be a WSL2-specific detail - probably
something about how it layers *nix semantics over top of filesystems
which are not compatible with those semantics. (I think it does at least
part of it via having actual virtual-hard-disk files, but that can't be
everything, and in this specific case it's pointing to a mounted
filesystem which is very probably on the host machine and therefore not
in such a contained filesystem.)

From what I gather, WSLg is explicitly in an experimental / pre-release
sort of mode, so it's not surprising that there'd be incompatibilities
and other bugs. I rather think the OP has just hit one of those bugs: a
case where some existing *nix applications are doing things that are
legitimate in their original environment but don't (currently) work
under WSLg, or in other words, a case where WSLg isn't sufficiently
compatible yet.

It might even be worth filing a report about this on the WSLg GitHub
issue tracker; they might decide to declare it not their problem and
close the issue, but they might also consider it legitimate and track it
down and try to get this working.

(If the solution winds up involving not using that symlink, though, I
think - based on what I've seen from existing issue discussions - that
that's going to be a nonstarter.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: slrn broke after power failure

[songbird]

Charlie Gibbs wrote:
...
> The zero-length files were easy enough to find, and few enough
> that I just deleted them by hand.  No luck.  I've even tried
> deleting the entire contents of a group, e.g.:
>
> rm /var/spool/slrnpull/news/linux/debian/user/*
>
> Still no luck.  The group header window still shows the number
> of messages that were available; the "c" command resets this to
> zero, but I still get "Server read failed." when trying to enter
> the group.
>
> Oddly enough, there are one or two groups which are still
> working properly.

  if you have a file which keeps track of what you have already
read like .jnewsrc there are lines in there for groups you've
subscribed to which keep track of which articles you've read.
after you delete the files from your spool then you would also
need to change the lines back so that you could read them
again.

here's an example of two lines in my .jnewsrc file that show an
example:

rec.food.cooking: 1-253560
rec.food.cuisine.jewish!

the first line says what articles i've seen and the second is
an example of a group i've not read any messages from at all.
so if you change the lines of groups you'd like to reread back
to ! marks then you should be able to redownload them.  you
may need to resubscribe to them.


> >  i'm not at all familiar with slrn's spooling or structure since
> > i've been using leafnode ever since i started usenet.  leafnode
> > has a process that goes through and checks consistency and will
> > rebuild an overview file for a group but i've never had a problem
> > with it truncating contents to zero.
>
> I was hoping that there was an slrn guru who could explain all this.
>
> Oh well, I've been meaning to upgrade my laptop to Bullseye -
> maybe it's time to nuke slrn and re-install it from scratch.

  you can uninstall it but that may not clear up the spool for
the groups, so you'd need to see if that actually works or not.


  songbird

Trying to Narrow Down Package Causing gnome-control-center to Hang

[Jaycee Santos]

Hi all.
In unstable, gnome-control-center hangs when opening the Applications submenu. 
Considering that some application information (settings, icon, etc.) may be 
causing gnome-control-center to become unresponsive, I noticed it was due to 
kwrite being installed. Removing the kwrite package allowed 
gnome-control-center to load the Applications submenu smoothly.

But I'm not sure if this is a bug in gnome-control-center, GTK, or something 
else.

If anyone else can check if the problem is reproducible, please let me know (if 
running GNOME on unstable, try installing kwrite then opening up the 
Applications submenu in GNOME Settings).

gnome-control-center 1:42.0-3
libgtk-4-1 4.6.2+ds-1
kwrite 4:21.12.3-1


Jaycee

moving dir with lots of files

[Adriel Peng]

Hello

I plan to move a dir which has about 0.4 million files to a new location.
This new location is a network storage.

I will run the command:

nohup mv dir /mnt/disk/newdir

I guess this will take a lot of hours to finish.

My question is, if the process gets an unexpected interruption, what will
happen and how can I recover it?

Thanks.

Re: moving dir with lots of files

[Bijan Soleymani]

On 2022-04-18 00:16, Adriel Peng wrote:

Hello

I plan to move a dir which has about 0.4 million files to a new 
location. This new location is a network storage.


I will run the command:

nohup mv dir /mnt/disk/newdir

I guess this will take a lot of hours to finish.

My question is, if the process gets an unexpected interruption, what 
will happen and how can I recover it?


Thanks.



If you can afford not to do a move but a copy and then a delete, then I 
would recommend using rsync


rsync will transfer what is missing if interrupted

If there is nothing missing it will finish pretty quickly.

I sync 130GB in 1.4 million files over the internet regularly and if 
there are no changes it take about 20 seconds to finish (the disks are 
fast on both ends).


If there are changes it transfers about as fast as the network can go.

Bijan