Re: grub-pc error when upgrading from buster to bullseye

[John Boxall]

On 2024-02-12 15:14, Greg Wooledge wrote:


According to

it uses debconf's database.  That page includes instructions for viewing
the device and changing it.



I had just started looking into the grub-pc package before I saw this. 
I'll be able to test this out sometime tomorrow.



I can't verify this on my machine, because mine uses UEFI.



Will advise. Thank you Greg!

--
Regards,

John Boxall

Re: grub-pc error when upgrading from buster to bullseye

[Greg Wooledge]

On Mon, Feb 12, 2024 at 09:04:01PM +0100, Thomas Schmitt wrote:
> Hi,
> 
> John Boxall wrote:
> > I am aware that the label and uuid (drive and partition) are replicated on
> > the cloned drive, but I can't find the model number (in text format) stored
> > anywhere on the drive.
> 
> Maybe the grub-pc package takes its configuration from a different drive
> which is attached to the system ?

According to

it uses debconf's database.  That page includes instructions for viewing
the device and changing it.

I can't verify this on my machine, because mine uses UEFI.

Re: grub-pc error when upgrading from buster to bullseye

[Thomas Schmitt]

Hi,

John Boxall wrote:
> I am aware that the label and uuid (drive and partition) are replicated on
> the cloned drive, but I can't find the model number (in text format) stored
> anywhere on the drive.

Maybe the grub-pc package takes its configuration from a different drive
which is attached to the system ?

Somewhat wayward idea:
Does the initrd contain the inappropirate address ?
(I don't see much connection between initrd and grub-pc. But initrd is a
classic hideout for obsolete paths after modification of boot procedures.)


Have a nice day :)

Thomas

Re: grub-pc error when upgrading from buster to bullseye

[John Boxall]

On 2024-02-12 09:34, Thomas Schmitt wrote:


The disk/by-id file names are made up from hardware properties.
I believe to see in the name at least: Manufacturer, Model, Serial Number.

So you will have to find the configuration file which knows that
/dev/disk/by-id address and change it either to the new hardware id or
to a /dev/disk/by-uuid address, which refers to the cloned disk content.


Have a nice day :)

Thomas



Thank you Thomas. That is what I am trying to find as I have searched 
for both the SSD drive model number and the WWN on the cloned HDD but 
can't find anything.


I am aware that the label and uuid (drive and partition) are replicated 
on the cloned drive, but I can't find the model number (in text format) 
stored anywhere on the drive.


I will keep looking.

--
Regards,

John Boxall

Re: grub-pc error when upgrading from buster to bullseye

[Thomas Schmitt]

Hi,

John Boxall wrote:
>   Setting up grub-pc (2.06-3~deb11u6) ...
>   /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not
> exist, so cannot grub-install to it!
> What is confusing to me is that the error indicates the source SDD even
> though I have updated the boot images and installed grub on the cloned HDD.

The disk/by-id file names are made up from hardware properties.
I believe to see in the name at least: Manufacturer, Model, Serial Number.

So you will have to find the configuration file which knows that
/dev/disk/by-id address and change it either to the new hardware id or
to a /dev/disk/by-uuid address, which refers to the cloned disk content.


Have a nice day :)

Thomas

grub-pc error when upgrading from buster to bullseye

[John Boxall]

I am attempting to upgrade my laptop (Thinkpad X230) from buster to 
bullseye and have run into the error below. In order to ensure that all 
goes well and not to lose all of the tweaks I have added over time, I am 
performing the upgrade first on a cloned HDD (via "dd") of the working SDD.


apt-get -y upgrade --without-new-pkgs

Setting up grub-pc (2.06-3~deb11u6) ...
/dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not
  exist, so cannot grub-install to it!
You must correct your GRUB install devices before proceeding:

DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg --configure -a
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess
 returned error exit status 1


All of the latest updates for buster have been applied before starting 
the process (below).


apt-get update;apt-get -y upgrade;apt-get -y dist-upgrade;

#shutdown, boot Debian live

#clone working SSD drive to an HDD  

#boot cloned drive

#login and open terminal session

#su to root

update-initramfs -u -k all

grub-install --recheck /dev/sda

apt-get update;apt-get -y upgrade;apt-get -y dist-upgrade;

#modify /etc/apt/source.list to point to bullseye
#modify all /etc/apt/source.list.d/* files to point to bullseye

apt-get update;apt-get -y upgrade --without-new-pkgs;

Running the recommended dpkg commands brings up the dialog to install 
grub and does complete successfully so that I can then run

"apt-get -y dist-upgrade", which also runs successfully.

What is confusing to me is that the error indicates the source SDD even 
though I have updated the boot images and installed grub on the cloned HDD.


Is there some other configuration file that needs to be updated/removed 
so that the grub-pc install works without intervention?


Source system info:

user:~$ uname -a
Linux laptop 4.19.0-26-amd64 #1 SMP Debian 4.19.304-1 (2024-01-09) 
x86_64 GNU/Linux


user:~$ cat /etc/debian_version
10.13

user:~$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   36 bits physical, 48 bits virtual
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   58
Model name:  Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Stepping:9
CPU MHz: 1202.696
CPU max MHz: 3600.
CPU min MHz: 1200.
BogoMIPS:5786.44
Virtualization:  VT-x
L1d cache:   32K
L1i cache:   32K
L2 cache:256K
L3 cache:4096K
NUMA node0 CPU(s):   0-3
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor 
ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault 
epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid 
fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d



--
Regards,

John Boxall

Re: Issues after upgrading 11 -> 12

[Charlie Gibbs]

On Tue, 30 Jan 2024 21:50:01 +0100
Michael =?utf-8?B?S2rDtnJsaW5n?= <2695bd53d...@ewoof.net> wrote:

> On 30 Jan 2024 10:14 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
>
>> VirtualBox, which I use heavily, has disappeard, so I'm going to
>> have to re-install some packages anyway.
>
> I'm pretty sure VirtualBox has not been shipped by Debian for quite a
> while because of its licensing status, so I guess you're relying on a
> third party package for that? (Probably Oracle's.) That's another
> thing that can easily cause complications during an upgrade, which is
> why the release notes recommend to disable third-party repositories
> before upgrading between releases and holding off on upgrading those
> packages until after the main system has been upgraded successfully;
> another detail that doesn't seem to be mentioned on the wiki page.

No worries, I'm used to installing VirtualBox afterwards.

> Semi-unrelated, but you might want to consider switching to KVM
> virtualization instead; it's supported by the stock kernel, making
> things easier. AQEMU is a fairly VirtualBox-like GUI front-end for it,
> and VMs can be converted (though especially if you're virtualizing
> Windows, I'm not sure how it takes to the changes in virtualized
> hardware). I switched from VirtualBox to KVM a while ago and haven't
> looked back.

I did some reading on KVM vs. VirtualBox.  For my application,
there didn't seem to be enough benefit to KVM to justify climbing
yet another learning curve.  As it turns out, re-installing
VirtualBox is now just a matter of going to Oracle's web site,
which contains one line you can add to /etc/apt/sources.list.
At this point you can just type
sudo apt install VirtualBox-7.0 (new version!)
Since its .vdi files (etc.) were already in $HOME, it came right up.
I told it to load guest extensions, and my Windows XP VM was up and
running again, complete with network and USB bridges.

>> Once I get this mess sorted out, I have one more machine to
>> upgrade.  I'll follow the release notes to the letter then,
>> and see whether I have better luck.
>
> For what it's worth, back when I upgraded my system from Bullseye to
> Bookworm (I think around the time 12.1 came out) closely following the
> release notes, the process was smooth, including Xfce and X11.

To be honest, most of my upgrades have gone smoothly too.  Maybe
I was becoming complacent and got careless - and if things go wrong,
they can go _very_ wrong.

For now, though, my laptop is happily running 12.4.  It occurs to
me that a full install from scratch isn't really that big a thing
if /home is intact.  I'll be occasionally finding a package that
isn't installed, but that's a matter of 30 seconds to install it;
it'll find its old configuration files in $HOME and all will be well.

Thanks, everyone, for your help.  Hopefully I'll remember some lessons
I can take to my next upgrade.

--
/~\  Charlie Gibbs  |  They don't understand Microsoft
\ /|  has stolen their car and parked
 X   I'm really at ac.dekanfrus |  a taxi in their driveway.
/ \  if you read it the right way.  |-- Mayayana

Re: Issues after upgrading 11 -> 12; was: Is 12.4 safe, or should I wait for 12.5?

[Max Nikulin]

On 31/01/2024 01:14, Charlie Gibbs wrote:

[Sorry about the broken threads; I read this group on Usenet.]


I use a NNTP gateway as well.


That seems the obvious conclusion.  I was pretty gobsmacked, though,
when my system came up in a totally different graphical environment.


May it happen that you have GNOME and GDM3 installed before despite you 
usual session was xfce? Do you have xfce as an alternative to GNOME? You 
should still have dpkg and apt logs, so you may try to figure out what 
happened during upgrade.



The takeaway (for me, anyway) is that upgrading a system is a
complicated and hazardous process which requires a lot of study
before attempting it.


Do release notes fall into your "a lot" category? Skimming through 
package lists presented by apt may be tedious to some degree, but it 
allows to spot something unexpected.

Re: Issues after upgrading 11 -> 12

[Michael Kjörling]

On 30 Jan 2024 10:14 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
> [Sorry about the broken threads; I read this group on Usenet.]

At least you kept the Subject line intact and provided solid quotes,
making manual linking of threads manageable.


> VirtualBox, which I use heavily, has disappeard, so I'm going to
> have to re-install some packages anyway.

I'm pretty sure VirtualBox has not been shipped by Debian for quite a
while because of its licensing status, so I guess you're relying on a
third party package for that? (Probably Oracle's.) That's another
thing that can easily cause complications during an upgrade, which is
why the release notes recommend to disable third-party repositories
before upgrading between releases and holding off on upgrading those
packages until after the main system has been upgraded successfully;
another detail that doesn't seem to be mentioned on the wiki page.

Semi-unrelated, but you might want to consider switching to KVM
virtualization instead; it's supported by the stock kernel, making
things easier. AQEMU is a fairly VirtualBox-like GUI front-end for it,
and VMs can be converted (though especially if you're virtualizing
Windows, I'm not sure how it takes to the changes in virtualized
hardware). I switched from VirtualBox to KVM a while ago and haven't
looked back.


> The takeaway (for me, anyway) is that upgrading a system is a
> complicated and hazardous process which requires a lot of study
> before attempting it.  Often it goes smoothly, but when it
> doesn't I"m in for a world of hurt.  So it goes.

I don't think I would go that far. My experience is that generally
Debian upgrades are very smooth; what can cause complications is if
you're not running a pure Debian system, especially if you have
out-of-tree packages installed which integrate into the kernel
(graphics drivers, virtualization, file system support, ...). Not
closely following the upgrade instructions in the release notes is
then likely to further compound any issues.


> Once I get this mess sorted out, I have one more machine to
> upgrade.  I'll follow the release notes to the letter then,
> and see whether I have better luck.

For what it's worth, back when I upgraded my system from Bullseye to
Bookworm (I think around the time 12.1 came out) closely following the
release notes, the process was smooth, including Xfce and X11.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Issues after upgrading 11 -> 12; was: Is 12.4 safe, or should I wait for 12.5?

[Charlie Gibbs]

[Sorry about the broken threads; I read this group on Usenet.]

On Tue, 30 Jan 2024 08:50:01 +0100
Michael =?utf-8?B?S2rDtnJsaW5n?= <2695bd53d...@ewoof.net> wrote:

> On 29 Jan 2024 19:54 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
>
>> Today I took a thorough backup of my laptop and dove in, using the
>> instructions at https://wiki.debian.org/DebianUpgrade as a guide.
>
> Did you actually follow _that_ page, or did you read and follow the
> _release notes_ as it says near the top of that page?

Mea culpa.  I used the wiki.

> As a rule the release notes for a release should be considered the
> authoritative truth about upgrading to any given release from the
> immediately preceding release. (Skipping releases is not supported and
> strongly discouraged.) There are also meaningful differences in system
> setup between 11 and 12, not least non-free-firmware (which, were it
> just that, would be easy enough to add after the fact).

Noted.  Hopefully I'll remember to go there first the next time I do
an upgrade, rather than following the first page that comes up in my
search engine.

> A plain Debian release upgrade should not switch your desktop
> environment on its own, and last I looked Xfce wasn't yet compatible
> with Wayland, so although I haven't looked in detail, it seems likely
> that your issues are related to something which you did or did not do
> during the upgrade process.

That seems the obvious conclusion.  I was pretty gobsmacked, though,
when my system came up in a totally different graphical environment.
Even though I've had strange things happen in other upgrades, this one
takes it to a whole new level.  I'm obviously playing with dynamite.

> Do you have a "script" transcript of the upgrade session (as the
> release notes also strongly recommend [1] in case there are problems)?
>
> [1]: 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session


Alas, no.  Again, something to remember for next time.

Although just about everything seems to be there, I feel uneasy
enough about the whole thing that I think I'll just re-format the
root partition (while leaving the separate /home partition intact)
and install Bookworm from scratch.  VirtualBox, which I use heavily,
has disappeard, so I'm going to have to re-install some packages
anyway.  This isn't the first time I've had to do this; when
I tried to upgrade this same laptop from (IIRC) Stretch to Buster,
I was left with an unbootable machine.

The takeaway (for me, anyway) is that upgrading a system is a
complicated and hazardous process which requires a lot of study
before attempting it.  Often it goes smoothly, but when it
doesn't I"m in for a world of hurt.  So it goes.

Once I get this mess sorted out, I have one more machine to
upgrade.  I'll follow the release notes to the letter then,
and see whether I have better luck.

--
/~\  Charlie Gibbs  |  Life is perverse.
\ /|  It can be beautiful -
 X   I'm really at ac.dekanfrus |  but it won't.
/ \  if you read it the right way.  |-- Lily Tomlin

Re: Issues after upgrading 11 -> 12; was: Is 12.4 safe, or should I wait for 12.5?

[Michael Kjörling]

On 29 Jan 2024 19:54 -0800, from cgi...@surfnaked.ca (Charlie Gibbs):
> Today I took a thorough backup of my laptop and dove in, using the
> instructions at https://wiki.debian.org/DebianUpgrade as a guide.

Did you actually follow _that_ page, or did you read and follow the
_release notes_ as it says near the top of that page?

As a rule the release notes for a release should be considered the
authoritative truth about upgrading to any given release from the
immediately preceding release. (Skipping releases is not supported and
strongly discouraged.) There are also meaningful differences in system
setup between 11 and 12, not least non-free-firmware (which, were it
just that, would be easy enough to add after the fact).

A plain Debian release upgrade should not switch your desktop
environment on its own, and last I looked Xfce wasn't yet compatible
with Wayland, so although I haven't looked in detail, it seems likely
that your issues are related to something which you did or did not do
during the upgrade process.

Do you have a "script" transcript of the upgrade session (as the
release notes also strongly recommend [1] in case there are problems)?


 [1]: 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session
 
-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Problem with php after upgrading to Bookworm

[Charles Curley]

On Thu, 14 Dec 2023 23:26:47 +0200
Alexis Grigoriou  wrote:

> On Thu, 2023-12-14 at 12:28 -0700, Charles Curley wrote:
>  [...]  
>  [...]  
>  [...]  
> 
>  [...]  
> 
> root@bfs# dpkg-query --show 'php*'
> php-amqp  
> php-apcu  
…
> php-yaml  
> php-zmq   
> php5.6-common 
> php5.6-json   
> php7.0-common 
> php7.0-curl   
> php7.1-common 
> php7.2-common 
> php7.2-sodium 
> php7.3-common 
> php7.4-calendar   
> php7.4-cgi7.4.33-1+deb11u4
> php7.4-cli7.4.33-1+deb11u4
> php7.4-common 7.4.33-1+deb11u4
> php7.4-ctype  
> php7.4-exif   
> php7.4-ffi
> php7.4-fileinfo   
> php7.4-ftp
> php7.4-gd 7.4.33-1+deb11u4
> php7.4-gettext
> php7.4-iconv  
> php7.4-json   7.4.33-1+deb11u4
> php7.4-mysql  7.4.33-1+deb11u4
> php7.4-mysqli 
> php7.4-mysqlnd
> php7.4-opcache7.4.33-1+deb11u4
> php7.4-pdo
> php7.4-pdo-mysql  
> php7.4-phar   
> php7.4-posix  
> php7.4-readline   7.4.33-1+deb11u4
> php7.4-shmop  
> php7.4-sockets
> php7.4-sysvmsg
> php7.4-sysvsem
> php7.4-sysvshm
> php7.4-tokenizer  
> php8.0-common 
> php8.1-common 
> phpapi-20190902   
> root@invader:/etc/php/7.4# apt update

I see a lot of php 7.4 but no php 8.2. I think you need more 8.2. But
that should have been installed as part of the upgrade. I'd try running
"apt install php".

Also, don't purge any of the 7.4 or older stuff until you are well
satisfied that 8.2 is working correctly.


> > Also, to make things easier down the road, install the generic
> > equivalent of a php package. E.g. php-imagick rather than
> > php8.2-imagick.
> 
> I also installed php-imagick along with it's dependencies but I still
> get the same result.

Unless you need it, I'd purge it. I intended that as an example, not
something to actually do.

> 
> 

-- 
Does anybody read signatures any more?

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

Re: Problem with php after upgrading to Bookworm

[Alexis Grigoriou]

On Thu, 2023-12-14 at 12:28 -0700, Charles Curley wrote:
> On Thu, 14 Dec 2023 19:24:19 +0200
> Alexis Grigoriou  wrote:
> 
> > All
> > I see is probably the php code. If I remember correctly, before the
> > upgrade php 7.4 was installed in my Bulleye installation. There is
> > a
> > directory in /etc/php/7.4, although 8.2 is the default in Bookworm,
> > but there is no /etc/php/8.2 directory.
> 
> Do you know for a fact that you have php 8.2 installed? The
> /etc/php/8.2 directory should be there. What do you get when you run:
> 
> dpkg-query --show 'php*'

> Please run that in a terminal window, and copy and paste the results,
> including the command prompt and the trailing prompt, into your reply
> email.

root@bfs# dpkg-query --show 'php*'
php-amqp
php-apcu
php-ast 
php-calendar
php-cgi 
php-cli 
php-common  2:93
php-crypt-gpg   
php-ctype   
php-ds  
php-exif
php-facedetect  
php-ffi 
php-fileinfo
php-ftp 
php-gd  
php-gearman 
php-gmagick 
php-gnupg   
php-iconv   
php-igbinary
php-imagick 
php-json
php-libvirt-php 
php-lua 
php-mailparse   
php-memcache
php-memcached   
php-mongodb 
php-msgpack 
php-mysqli  
php-mysqlnd 
php-mysqlnd-ms  
php-oauth   
php-opcache 
php-pcov
php-pdo 
php-pdo-mysql   
php-pear
php-pecl-http   
php-phar
php-posix   
php-ps  
php-psr 
php-radius  
php-raphf   
php-readline
php-redis   
php-rrd 
php-shmop   
php-smbclient   
php-sockets 
php-ssh2
php-stomp   
php-sysvmsg 
php-sysvsem 
php-sysvshm 
php-tideways
php-tokenizer   
php-uopz
php-uploadprogress  
php-uuid
php-xdebug  
php-xmlrpc  
php-yac 
php-yaml
php-zmq 
php5.6-common   
php5.6-json 
php7.0-common   
php7.0-curl 
php7.1-common   
php7.2-common   
php7.2-sodium   
php7.3-common   
php7.4-calendar 
php7.4-cgi  7.4.33-1+deb11u4
php7.4-cli  7.4.33-1+deb11u4
php7.4-common   7.4.33-1+deb11u4
php7.4-ctype
php7.4-exif 
php7.4-ffi  
php7.4-fileinfo 
php7.4-ftp  
php7.4-gd   7.4.33-1+deb11u4
php7.4-gettext  
php7.4-iconv
php7.4-json 7.4.33-1+deb11u4
php7.4-mysql7.4.33-1+deb11u4
php7.4-mysqli   
php7.4-mysqlnd  
php7.4-opcache  7.4.33-1+deb11u4
php7.4-pdo  
php7.4-pdo-mysql
php7.4-phar 
php7.4-posix
php7.4-readline 7.4.33-1+deb11u4
php7.4-shmop
php7.4-sockets  
php7.4-sysvmsg  
php7.4-sysvsem  
php7.4-sysvshm  
php7.4-tokenizer
php8.0-common   
php8.1-common   
phpapi-20190902 
root@invader:/etc/php/7.4# apt update

> Even if php8.2 itself is installed, you will likely need other php8.2
> packages.
> 
> Also, to make things easier down the road, install the generic
> equivalent of a php package. E.g. php-imagick rather than
> php8.2-imagick.
> 

I also installed php-imagick along with it's dependencies but I still
get the same result.

Re: Problem with php after upgrading to Bookworm

[Alexis Grigoriou]

On Thu, 2023-12-14 at 18:07 +, Michael Kjörling wrote:
> On 14 Dec 2023 19:24 +0200, from ale...@nanoid.net (Alexis
> Grigoriou):
> >  As the subject states pages using php won't disply in the browser.
> > All
> > I see is probably the php code.
> 
> Well, first things first. What web server are you using to try to
> serve those pages?
> 

I am using apache
root@bfs:apt show apache2
Package: apache2
Version: 2.4.57-2

Re: Problem with php after upgrading to Bookworm

[Charles Curley]

On Thu, 14 Dec 2023 19:24:19 +0200
Alexis Grigoriou  wrote:

> All
> I see is probably the php code. If I remember correctly, before the
> upgrade php 7.4 was installed in my Bulleye installation. There is a
> directory in /etc/php/7.4, although 8.2 is the default in Bookworm,
> but there is no /etc/php/8.2 directory.

Do you know for a fact that you have php 8.2 installed? The
/etc/php/8.2 directory should be there. What do you get when you run:

dpkg-query --show 'php*'

Please run that in a terminal window, and copy and paste the results,
including the command prompt and the trailing prompt, into your reply
email.

Even if php8.2 itself is installed, you will likely need other php8.2
packages.

Also, to make things easier down the road, install the generic
equivalent of a php package. E.g. php-imagick rather than
php8.2-imagick.

-- 
Does anybody read signatures any more?

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

Re: Problem with php after upgrading to Bookworm

[Michael Kjörling]

On 14 Dec 2023 19:24 +0200, from ale...@nanoid.net (Alexis Grigoriou):
>  As the subject states pages using php won't disply in the browser. All
> I see is probably the php code.

Well, first things first. What web server are you using to try to
serve those pages?

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Problem with php after upgrading to Bookworm

[Alexis Grigoriou]

Greetings,

 As the subject states pages using php won't disply in the browser. All
I see is probably the php code. If I remember correctly, before the
upgrade php 7.4 was installed in my Bulleye installation. There is a
directory in /etc/php/7.4, although 8.2 is the default in Bookworm, but
there is no /etc/php/8.2 directory.

 I don't code/script, so I am completely lost here. Any help would be
appreciated. Any more info need to help out will be available.

TIA

Re: USB2 not working after upgrading to bookworm

[Rafa]

Hi,

Thank you for your quick reply, Michael.

On Sun, Nov 12, 2023 at 09:05:19PM +, Michael Kjörling wrote:
>
> What kernel, systemd and udev versions are installed and running in
> the Bookworm install?

kernel version 6.1 and systemd and udev version 252:

$ uname -a
Linux  6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 
(2023-09-29) x86_64 GNU/Linux

$ LANG=C dpkg-query --list systemd
[...]
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd252.17-1~deb12u1 amd64system and service manager

$ LANG=C dpkg-query --list udev
[...]
||/ Name   Version  Architecture Description
+++-==---===
ii  udev   252.17-1~deb12u1 amd64/dev/ and hotplug management 
daemon

> Just how _did_ you "upgrade" the system while retaining the ability to
> boot the older install? [...]

I followed chapter 4 "Upgrades from Debian 11 (bullseye)" from the "Release
Notes for Debian 12 (bookworm), 64-bit PC" manual.

With regard to the ability to boot the older install, I keep two systems
installed on the machine, on different file system partitions (I will
call one of them the "TEST" system and the other one the "PROD" system).
Normally, both of them are Debian stable systems.

The grub menu contains entries to boot either system.

When I am ready to upgrade to a new version, first I upgrade the "TEST"
system and I verify that everything is working fine. If it is not, I try
to solve any problem I have before upgrading the "PROD" system.

Currently I have upgraded the "TEST" system to bookworm, while the
"PROD" system is still at bullseye.

This is how I am able to boot to either system.

> [...] please
> specify more exactly what you mean by "boot bullseye" and "boot
> bookworm".

In the current configuration, "boot bullseye" means boot the "PROD"
system and "boot bookworm" means boot the "TEST" system.

> Do you see any difference if you hook up a USB 2 device to a port
> which is physically USB 2 or USB 3?

When using a USB2 port I get error messages in dmesg, and cannot use the
device. When using a USB3 port, instead, messages in dmesg seem to be ok
and I can mount the device and work with it normally.

--

# dmesg -w

(plug a USB2 device into a USB2 port)

[  918.226025] usb 7-1: new full-speed USB device number 53 using ohci-pci
[  918.386029] usb 7-1: device descriptor read/64, error -32
[  918.654039] usb 7-1: device descriptor read/64, error -32
[  918.946053] usb 7-1: new full-speed USB device number 54 using ohci-pci
[  919.106056] usb 7-1: device descriptor read/64, error -32
[  919.374063] usb 7-1: device descriptor read/64, error -32
[  919.482114] usb usb7-port1: attempt power cycle
[  919.718072] usb 2-1: new high-speed USB device number 80 using ehci-pci
[  919.846076] usb 2-1: device descriptor read/64, error -32
[  920.086086] usb 2-1: device descriptor read/64, error -32
[  920.322096] usb 2-1: new high-speed USB device number 81 using ehci-pci
[  920.450099] usb 2-1: device descriptor read/64, error -32
[  920.686105] usb 2-1: device descriptor read/64, error -32
[  920.794138] usb usb2-port1: attempt power cycle
[  920.998137] usb 2-1: new high-speed USB device number 82 using ehci-pci
[  921.414135] usb 2-1: device not accepting address 82, error -32
[  921.542137] usb 2-1: new high-speed USB device number 83 using ehci-pci
[  921.958185] usb 2-1: device not accepting address 83, error -32
[  921.958233] usb usb2-port1: unable to enumerate USB device
[  922.342175] usb 7-1: new full-speed USB device number 56 using ohci-pci
[  922.502170] usb 7-1: device descriptor read/64, error -32
[  922.770180] usb 7-1: device descriptor read/64, error -32
[  923.062191] usb 7-1: new full-speed USB device number 57 using ohci-pci
[  923.222194] usb 7-1: device descriptor read/64, error -32
[  923.490206] usb 7-1: device descriptor read/64, error -32
[  923.598258] usb usb7-port1: attempt power cycle
[  923.834214] usb 2-1: new high-speed USB device number 84 using ehci-pci
[  923.962255] usb 2-1: device descriptor read/64, error -32
[  924.198226] usb 2-1: device descriptor read/64, error -32
[  924.434235] usb 2-1: new high-speed USB device number 85 using ehci-pci
[  924.562241] usb 2-1: device descriptor read/64, error -32
[  924.798250] usb 2-1: device descriptor read/64, error -32
[  924.906283] usb usb2-port1: attempt power cycle
[  925.110259] usb 2-1: new high-speed USB device number 86 using ehci-pci
[  925.526270] usb 2-1: device not accepting address 86, error -32
[  925.654276] usb 2-1: new high-speed USB device number 87 using ehci-pci
[  926.070290] usb 2-1: device not accepting address 8

Re: USB2 not working after upgrading to bookworm

[Michael Kjörling]

On 12 Nov 2023 19:25 +, from r...@rptv.info (Rafa):
> I have an issue regarding USB2 after upgrading a desktop machine from
> Debian 11 (bullseye) to Debian 12 (bookworm).
> 
> USB3 ports work fine, but USB2 ports do not.
> 
> I still have bullseye installed in the machine and when I boot bullseye
> I can use both USB2 and USB3. But when I boot bookworm I can only use
> USB3.

What kernel, systemd and udev versions are installed and running in
the Bookworm install?

Just how _did_ you "upgrade" the system while retaining the ability to
boot the older install? I take it that this would mean that you didn't
do the normal in-place upgrade but rather something else, and exactly
what that something else is might provide clues. Alternatively, please
specify more exactly what you mean by "boot bullseye" and "boot
bookworm".

Do you see any difference if you hook up a USB 2 device to a port
which is physically USB 2 or USB 3?

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

USB2 not working after upgrading to bookworm

[Rafa]

Hi,

I have an issue regarding USB2 after upgrading a desktop machine from
Debian 11 (bullseye) to Debian 12 (bookworm).

USB3 ports work fine, but USB2 ports do not.

I still have bullseye installed in the machine and when I boot bullseye
I can use both USB2 and USB3. But when I boot bookworm I can only use
USB3.

I have compared the output from the "lspci" and "lsusb" commands
obtained with bullseye and with bookworm, but they seem quite similar to
me.

In bookworm, command "dmesg -w" writes out several error messages like
the following when I plug a USB device in a USB2 port:

  usb 4-1: device descriptor read/64, error -32

  usb 4-1: device not accepting address 4, error -32



$ lspci -nnk
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 
Host Bridge [1002:5a14] (rev 02)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host 
Bridge [1002:5a14]
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) [1002:5a16]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI 
to PCI bridge (PCI Express GFX port 0) [1002:5a14]
Kernel driver in use: pcieport
00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) [1002:5a18]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI 
to PCI bridge (PCI Express GPP Port 0) [1002:5a14]
Kernel driver in use: pcieport
00:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 4) [1002:5a1c]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI 
to PCI bridge (PCI Express GPP Port 4) [1002:5a14]
Kernel driver in use: pcieport
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390] (rev 40)
Subsystem: Gigabyte Technology Co., Ltd GA-MA770-DS3rev2.0 Motherboard 
[1458:b002]
Kernel driver in use: ahci
Kernel modules: ahci
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-series motherboard 
[1458:5004]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-series motherboard 
[1458:5004]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-series motherboard 
[1458:5004]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-series motherboard 
[1458:5004]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus 
Controller [1002:4385] (rev 42)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus 
Controller [1002:4385]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] (rev 40)
Subsystem: Gigabyte Technology Co., Ltd GA-MA78GM-S2H motherboard 
[1458:5002]
Kernel driver in use: pata_atiixp
Kernel modules: pata_atiixp, ata_generic
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383] (rev 40)
Subsystem: Gigabyte Technology Co., Ltd SBx00 Azalia (Intel HDA) 
[1458:a002]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC 
host controller [1002:439d]
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to 
PCI Bridge [1002:4384] (rev 40)
00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-series motherboard 
[1458:5004]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:16.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: Gigabyte Technology Co., Ltd GA-78/880-

Re: a couple of problems after upgrading to bookworm

[John Covici]

hmm, I thought I had this correct, but I will recheck and try again.
Thanks for the hint.

On Sun, 23 Jul 2023 09:35:44 -0400,
Greg Wooledge wrote:
> 
> On Sun, Jul 23, 2023 at 09:27:18AM -0400, John Covici wrote:
> > i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
> > failed with error -2 ...:  4 Time(s)
> > 
> > Where can I find this firmware -- isn't it in the firmware-linux-free
> > package?
> 
> unicorn:~$ dpkg -S /lib/firmware/i915/skl_dmc_ver1_27.bin
> firmware-misc-nonfree: /lib/firmware/i915/skl_dmc_ver1_27.bin
> 
> Remember, in bookworm, the non-free firmware has moved to a newly
> created section in the repositories.  Make sure your sources.list
> has been updated appropriately.
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: a couple of problems after upgrading to bookworm

[Greg Wooledge]

On Sun, Jul 23, 2023 at 09:27:18AM -0400, John Covici wrote:
> i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
> failed with error -2 ...:  4 Time(s)
> 
> Where can I find this firmware -- isn't it in the firmware-linux-free
> package?

unicorn:~$ dpkg -S /lib/firmware/i915/skl_dmc_ver1_27.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_dmc_ver1_27.bin

Remember, in bookworm, the non-free firmware has moved to a newly
created section in the repositories.  Make sure your sources.list
has been updated appropriately.

a couple of problems after upgrading to bookworm

[John Covici]

Hi.  I upgraded to bookworm and it went pretty well, but I have some
strange errors (what's a not strange error).

I use logwatch and I am getting apache2 level error and then a number
of times, but I cannot find what its complaining about.  I did not get
these under bullseye.  I am running with kernel 6.1.0-10.

Also, I am getting the following:

i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
failed with error -2 ...:  4 Time(s)

Where can I find this firmware -- isn't it in the firmware-linux-free
package?


Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: Printer not working after upgrading

[Brian]

On Tue 22 Nov 2022 at 09:25:40 -0600, David Wright wrote:

[...]

> $ driverless
> ipp://Brother%20HL-L2390DW._ipp._tcp.local/
> $ 
> 
> # lpadmin -p brother -v ipp://Brother%20HL-L2390DW._ipp._tcp.local/ -E -m 
> driverless:ipp://Brother%20HL-L2390DW._ipp._tcp.local/
> # 

Splendid advice for those wishing to have complete control of setting
up a print queue for a Modern printer. Unfortunately, the device in
question is a Legacy one from around 2010 requiring a vendor driver.

-- 
Brian.

Re: Printer not working after upgrading

[Brian]

On Tue 22 Nov 2022 at 09:42:34 +, Rodolfo Medina wrote:

> I noticed the problem just after upgrading to bullseye from previous stable
> Debian version; then I upgraded to Unstable in the hope of solving it but the
> problem remains, with error:
> 
>  stopped "Filter failed"
> 
> I also tried to remove and re-add the printer with no success.  I'm stuck,
> please help, thanks in advance.

I have not read ths thread in its entirety:

 https://lists.debian.org/debian-user/2017/03/msg00100.html

There will be a PPD for the printer in /etc/cups/ppd. As root,
execute

 cupsfilter -p /etc/cups/ppd/YOUR_PPD -m printer/foo -e /etc/nsswitch > out.dat 
2>log

and post log.

-- 
Brian.

Re: Printer not working after upgrading

[David Wright]

On Tue 22 Nov 2022 at 09:42:34 (+), Rodolfo Medina wrote:
> I noticed the problem just after upgrading to bullseye from previous stable
> Debian version; then I upgraded to Unstable in the hope of solving it but the
> problem remains, with error:
> 
>  stopped "Filter failed"
> 
> I also tried to remove and re-add the printer with no success.  I'm stuck,
> please help, thanks in advance.

So your configuration is likely two releases out of date (at least).
I just moved everything out of the way and started from scratch.
Because the printer was reasonably recent, it came down to:

$ driverless
ipp://Brother%20HL-L2390DW._ipp._tcp.local/
$ 

# lpadmin -p brother -v ipp://Brother%20HL-L2390DW._ipp._tcp.local/ -E -m 
driverless:ipp://Brother%20HL-L2390DW._ipp._tcp.local/
# 

(This is in the absence of being in group lpadmin.)

$ lp -d brother file
request id is PDF-1234 (1 file(s))
$ 

but I did leave this file:

$ cat .cups/lpoptions 
Default PDF resume=true
$ 

The key was moving everything out of the way and starting from scratch.

Cheers,
David.

Re: Printer not working after upgrading

[mick.crane]

On 2022-11-22 12:39, Rodolfo Medina wrote:

Rodolfo Medina  writes:

I noticed the problem just after upgrading to bullseye from previous 
stable
Debian version; then I upgraded to Unstable in the hope of solving it 
but the

problem remains, with error:

 stopped "Filter failed"

I also tried to remove and re-add the printer with no success.  I'm 
stuck,

please help, thanks in advance.



Peter von Kaehne  writes:

To help I think people need more than you have given. Printer model, 
software

in use, version, printer driver, logs.



Brad Rogers  writes:


Hello Rodolfo,

Same sort of thing Celejar said about your gv issues;  What printer,
what driver, what were the exact commands and error messages...



Thanks, sorry: the printer is the Samsung ML-191x 252x Series, the 
software I'm
using to manage it is the Debian package cups and `aptitude show' says 
it's
installed in my Sid box at the version 2.4.2-1+b2.  The driver I think 
is the

file called ML-191xspl2.ppd.  I do:

 $ lp -P 1 ing.pdf

and the output:

 request id is Samsung_ML-191x_252x_Series-694 (1 file(s))

and nothing happens.  In the "Jobs" section of the printing localhost 
it says


 stopped
 "Filter failed"

I hope it's all right.  Logs I wouldn't know...


Is the printer attached to the Sid PC (was Bullseye)?
How's it attached?
Did you try print a plain text file?
There's commands to see what Cups thinks the printer is but I'd have to 
look it up.

mick

Re: Printer not working after upgrading

[Peter von Kaehne]

Thanks, Rodolfo ! Logs I wouldn't know...CUPSDebugging - Debian Wikiwiki.debian.orgSection 3 to start with. Basically enable debugging , do what you did before for printing and check the logs. Sometimes the errors are very obvious. Sometimes they drive one batty. Either way, it might all flow from there together with the wider context of the wiki or come back to here. Peter

Re: Printer not working after upgrading

[Rodolfo Medina]

Rodolfo Medina  writes:

> I noticed the problem just after upgrading to bullseye from previous stable
> Debian version; then I upgraded to Unstable in the hope of solving it but the
> problem remains, with error:
>
>  stopped "Filter failed"
>
> I also tried to remove and re-add the printer with no success.  I'm stuck,
> please help, thanks in advance.


Peter von Kaehne  writes:

> To help I think people need more than you have given. Printer model, software
> in use, version, printer driver, logs.


Brad Rogers  writes:

> Hello Rodolfo,
>
> Same sort of thing Celejar said about your gv issues;  What printer,
> what driver, what were the exact commands and error messages...


Thanks, sorry: the printer is the Samsung ML-191x 252x Series, the software I'm
using to manage it is the Debian package cups and `aptitude show' says it's
installed in my Sid box at the version 2.4.2-1+b2.  The driver I think is the
file called ML-191xspl2.ppd.  I do:

 $ lp -P 1 ing.pdf 

and the output:

 request id is Samsung_ML-191x_252x_Series-694 (1 file(s))

and nothing happens.  In the "Jobs" section of the printing localhost it says

 stopped 
 "Filter failed"

I hope it's all right.  Logs I wouldn't know...

Thanks,

Rodolfo

Re: Printer not working after upgrading

[Brad Rogers]

On Tue, 22 Nov 2022 09:42:34 +
Rodolfo Medina  wrote:

Hello Rodolfo,

>I also tried to remove and re-add the printer with no success.  I'm
>stuck, please help, thanks in advance.

Same sort of thing Celejar said about your gv issues;  What printer,
what driver, what were the exact commands and error messages...

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
I'm in need of your help now
Burn - Judgement Centre


pgpx6qmt4uT0F.pgp
Description: OpenPGP digital signature

Re: Printer not working after upgrading

[Peter von Kaehne]

> please help

To help I think people need more than you have given. Printer model, software 
in use, version, printer driver, logs.

Peter

Printer not working after upgrading

[Rodolfo Medina]

I noticed the problem just after upgrading to bullseye from previous stable
Debian version; then I upgraded to Unstable in the hope of solving it but the
problem remains, with error:

 stopped "Filter failed"

I also tried to remove and re-add the printer with no success.  I'm stuck,
please help, thanks in advance.

Rodolfo

Re: installing & upgrading backport package & upgrading system

[David Wright]

On Wed 02 Nov 2022 at 04:52:51 (+), Andy Smith wrote:
> Hi,
> 
> On Wed, Nov 02, 2022 at 04:20:22AM +, jindam, vani wrote:
> > * i want to install lo package from bullseye-backports.
> 
> There is no such package name "lo" in bullseye-backports or any other
> version of Debian. What are you actually trying to do?

Likely LO = LibreOffice; cf. FF = Firefox etc.

Cheers,
David.

Re: installing & upgrading backport package & upgrading system

[Andy Smith]

Hi,

On Wed, Nov 02, 2022 at 04:20:22AM +, jindam, vani wrote:
> * i want to install lo package from bullseye-backports.

There is no such package name "lo" in bullseye-backports or any other
version of Debian. What are you actually trying to do?

> * correct method for before installation 
> of backport lo package? :
> (1)
> sudo apt -t bullseye-backports update && 
> sudo apt -t bullseye-backports full-upgrade
> sudo apt -t bullseye-backports install lo

If there were a package called 'lo' in bullseye-backports then all you'd
need (after editing your apt sources to include bullseye-backports) is
the last line.

> * for upgrading entire system after 
> installation of backport lo package? :

You do not have to update the entire system after installing one
backports package.

The backports suites aren't full distributions and you could not have a
working system where every package comes from -backports as most of
those packages won't exist. bullseye-backports is only intended to
provide a relatively small number of newer packages for systems
nominally running Debian bullseye.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

installing & upgrading backport package & upgrading system

[jindam, vani]

* i want to install lo package from bullseye-backports.

* correct method for before installation 
of backport lo package? :
(1)
sudo apt -t bullseye-backports update && 
sudo apt -t bullseye-backports full-upgrade
sudo apt -t bullseye-backports install lo

(2)
sudo apt update && sudo apt full-upgrade
sudo apt -t bullseye-backports install lo

* for upgrading entire system after 
installation of backport lo package? :
(1) 
sudo apt update && sudo apt full-upgrade &&
sudo apt -t bullseye-backports update && 
sudo apt -t bullseye-backports full-upgrade

(2)
sudo apt -t bullseye-backports update && 
sudo apt -t bullseye-backports full-upgrade

regards,
jindam, vani

toots: @jindam_v...@c.im
others: en.wikipedia.org/wiki/User:Jindam_vani

Re: linux headers and upgrading nvidia driver

[Andrew M.A. Cater]

On Thu, Sep 15, 2022 at 10:22:09PM +0800, Bret Busby wrote:
> On 15/9/22 21:01, Thomas Anderson wrote:
> > First off, I am running Debian 9, Stretch. I know it is old and I should
> > upgrade and that is something I want to do.
> > 
> > The primary problem is that I have a lot of important systems (email,
> > cloud), and other less important (web host). Simple dist-upgrades have
> > always broken my mail server, that I was not immediately able to recover
> > (fortunately, I had made a backup before). I have tried a couple of
> > times to upgrade, but all attempts have failed. Thus, why I am still
> > stick on 9. I don't like it, and still want to upgrade.
> > 
> > All that said, also I have been stuck on installing a simple nvidia
> > driver, also for months. I can install both the backports version and
> > the downloaded from nvidia version, but a driver can never be loaded
> > because of some linux headers error.  I know nvidia and linux have never
> > been nice to each other.
> > 

You may be able to do an upgrade from 9 to 10 and then reinstall the Nvidia
drivers - at this point, I wouldn't be running a 9 that's internet connected.

> > I think these problems are related.
> > 
> > How can i find the linux header, to point my driver to?
> > 
> > thanks in advance, sorry for the long sob story.
> > 
> 
> Hello.
> 
> Have you tried Ubuntu, with your nvidia stuff?
> 
> I note that you do not specify the nvidia hardware that you have.
> 
> I have two Acer laptops, unfortunately, one of which; my most powerful
> computer that I have, I can no longer boot, after an electricity grid supply
> failure here, in the last few days - the electricity grid supply here, is
> erratic, unstable, unsafe, and, harmful.
> 

Boo - that's a shame.

> The two Acer laptops both have nvidia graphics, and, nvidia Optimus.
> 
> When I got the more powerful one, in about 2013, I could not find a non-MS
> operating system to run the hardware, at first, and, the MS Windows version
> was too difficult to use. After about 18 months (it took me 18 months, to
> get the computer operating, so that I could start using it), I had found
> that only two non-MS operating systems had drivers for the CPU; an i7 of the
> Haskell (?) architecture - dragonflyBSD and Ubuntu Linux, and, of those,
> only Ubuntu Linux had drivers for the nvidia graphics, that ran with
> Optimus.
> 
> My understanding is that, to run Linux, or, any non-MS operating system,
> with nvidia graphics, especially, if you have nvidia Optimus, you need to
> run Ubuntu Linux.
> 
> I do not know whether Debian, as yet, has the drivers to run the nvidia
> graphics, and, in the absence of your nvidia hardware details, I think you
> might need to try running Ubuntu with your hardware.
> 

No, it should run fine - Debian has optimus packages and wiki pages
on how to run everything together. It is really helpful if you can do
a text mode install FIRST and then install the prerequisites for the
Nvidia drivers and at that point install the windowing system using tasksel.

If it fails horribly, that's usually because you've installed a desktop
environment that installs nouveau and fails with odd bugs including lock-ups.

> I am no expert, and, after about 20-25 years of using Linux, I still regard
> myself as a learner - this opinion is based solely on my personal
> experience.
> 
> ..
> Bret Busby
> Armadale
> West Australia
> (UTC+0800)
> ..
> 
All the very best, as ever,

Andy Cater

> 

Re: linux headers and upgrading nvidia driver

[Greg Wooledge]

On Thu, Sep 15, 2022 at 08:34:05PM +0200, Thomas Anderson wrote:
> I tried: sudo apt install linux-headers-$(uname -r)
> 
> says there is some c compiler requirement that is not fulfilled. And, there
> are broken packages that are being held back.

You probably need build-essential then.

> Where is the kernel located anyway?

/boot

Modules are in /lib/modules.

Re: linux headers and upgrading nvidia driver

[Thomas Anderson]

I tried the suggestions mentioned in this thread. I forgot to mention 
the hardware in question. It is a rather modern GTX 1030 low profile 
Nvidia card. it is nothing fancy at all, and would not expect to game 
from it, but that is not what I bought it for. Just wanted more than 
null graphics. Over the past half dozen years, have mostly done things 
over ssh anyway, just wanted something nicer to work on. Admittedly, 
it's not even that important, I have had this issue for maybe a year, 
but when I fired up a new installation this past weekend, in my bid to 
set everything up again, and saw that the card actually works (on a 
clean install), I thought I would give it another go.


I tried: sudo apt install linux-headers-$(uname -r)

says there is some c compiler requirement that is not fulfilled. And, 
there are broken packages that are being held back. I have gone deep 
into this rabbit hole, and still can't seem to find a solution to 
whatever shows up.


Where is the kernel located anyway? The nvidia software, to it's credit, 
has an option flag that will allow me to show the software where the 
kernel is located. I looked where nvidia suggests it should be, don't 
remember off the top of my head, and found an older kernel there, like 
4.9..whatever. But, not the 4.19...version.


I have been using Linux for 20 years, and usually can find a solution, 
but in this particular case, it's possible that my box is just beyond 
repair--at least by me =)


On 15/09/2022 18:37, Paul Johnson wrote:



On Thu, Sep 15, 2022, 09:46 Bret Busby  wrote:

My understanding is that, to run Linux, or, any non-MS operating
system,
with nvidia graphics, especially, if you have nvidia Optimus, you
need
to run Ubuntu Linux.


Have you looked at the Debian wiki?  Because the Nvidia pages do 
correctly show how to set up optimus five different ways.


https://wiki.debian.org/NVIDIA%20Optimus

The default render offload option works perfectly and I wished I 
bothered to try that first instead of fighting constantly with 
Bumblebee, which is both slow and brittle by comparison.

Re: linux headers and upgrading nvidia driver

[Paul Johnson]

On Thu, Sep 15, 2022, 09:46 Bret Busby  wrote:

> My understanding is that, to run Linux, or, any non-MS operating system,
> with nvidia graphics, especially, if you have nvidia Optimus, you need
> to run Ubuntu Linux.
>

Have you looked at the Debian wiki?  Because the Nvidia pages do correctly
show how to set up optimus five different ways.

https://wiki.debian.org/NVIDIA%20Optimus

The default render offload option works perfectly and I wished I bothered
to try that first instead of fighting constantly with Bumblebee, which is
both slow and brittle by comparison.

Re: linux headers and upgrading nvidia driver

[Anssi Saari]

Bret Busby  writes:

> My understanding is that, to run Linux, or, any non-MS operating
> system, with nvidia graphics, especially, if you have nvidia Optimus,
> you need to run Ubuntu Linux.

Maybe in 2012 that was the case? I have 2016 vintage HP zbook gen3 which
worked without issue when I put Debian 11 on it last fall. Nvidia M2000M
video and Optimus, although I'm not clear what this Optimus stuff
does. Video worked poorly with the Nouveau driver so I upgraded to
Nvidia's driver.

External displays work fine, I can connect one to HDMI and another to
Thunderbolt, with a TB to DP adapter cable.

Also, the OP said he has trouble with updating his video driver,
not that his video doesn't work.

Re: linux headers and upgrading nvidia driver

[Charles Curley]

On Thu, 15 Sep 2022 15:01:24 +0200
Thomas Anderson  wrote:

> I have tried a couple of 
> times to upgrade, but all attempts have failed. Thus, why I am still 
> stick on 9. I don't like it, and still want to upgrade.

The only way to upgrade is one major version at a time. In your case, 9
-> 10, then 10 -> 11. It may be less of a PITA to do a new install to
11.

-- 
Does anybody read signatures any more?

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

Re: linux headers and upgrading nvidia driver

[Bret Busby]

On 15/9/22 21:01, Thomas Anderson wrote:
First off, I am running Debian 9, Stretch. I know it is old and I should 
upgrade and that is something I want to do.


The primary problem is that I have a lot of important systems (email, 
cloud), and other less important (web host). Simple dist-upgrades have 
always broken my mail server, that I was not immediately able to recover 
(fortunately, I had made a backup before). I have tried a couple of 
times to upgrade, but all attempts have failed. Thus, why I am still 
stick on 9. I don't like it, and still want to upgrade.


All that said, also I have been stuck on installing a simple nvidia 
driver, also for months. I can install both the backports version and 
the downloaded from nvidia version, but a driver can never be loaded 
because of some linux headers error.  I know nvidia and linux have never 
been nice to each other.


I think these problems are related.

I currently have 4.19.0-0.bpo.amd64 headers. I try rebuilding them, also 
tried going back to 4.9.0-13--but the former still stays. the nvidia 
installer always says it can't find the kernel to build the driver. If 
my system keeps saying it's 4.19.0-0.bpo, why isn't it in the standard 
location? I have tried to locate it, but I cannot find it?


How can i find the linux header, to point my driver to?

thanks in advance, sorry for the long sob story.



Hello.

Have you tried Ubuntu, with your nvidia stuff?

I note that you do not specify the nvidia hardware that you have.

I have two Acer laptops, unfortunately, one of which; my most powerful 
computer that I have, I can no longer boot, after an electricity grid 
supply failure here, in the last few days - the electricity grid supply 
here, is erratic, unstable, unsafe, and, harmful.


The two Acer laptops both have nvidia graphics, and, nvidia Optimus.

When I got the more powerful one, in about 2013, I could not find a 
non-MS operating system to run the hardware, at first, and, the MS 
Windows version was too difficult to use. After about 18 months (it took 
me 18 months, to get the computer operating, so that I could start using 
it), I had found that only two non-MS operating systems had drivers for 
the CPU; an i7 of the Haskell (?) architecture - dragonflyBSD and Ubuntu 
Linux, and, of those, only Ubuntu Linux had drivers for the nvidia 
graphics, that ran with Optimus.


So, as it happened, the only way that I could get the i7 laptop (an Acer 
Aspire V3-772G) to run an external monitor, was to run Ubuntu Linux; at 
that time, v12.04. Prior to getting that computer operational, I had 
been running Debian, on most of my computers.


My understanding is that, to run Linux, or, any non-MS operating system, 
with nvidia graphics, especially, if you have nvidia Optimus, you need 
to run Ubuntu Linux.


I do not know whether Debian, as yet, has the drivers to run the nvidia 
graphics, and, in the absence of your nvidia hardware details, I think 
you might need to try running Ubuntu with your hardware.


I am no expert, and, after about 20-25 years of using Linux, I still 
regard myself as a learner - this opinion is based solely on my personal 
experience.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: linux headers and upgrading nvidia driver

[Dan Ritter]

Thomas Anderson wrote: 
> The primary problem is that I have a lot of important systems (email,
> cloud), and other less important (web host). Simple dist-upgrades have
> always broken my mail server, that I was not immediately able to recover
> (fortunately, I had made a backup before). I have tried a couple of times to
> upgrade, but all attempts have failed. Thus, why I am still stick on 9. I
> don't like it, and still want to upgrade.


All legitimate mail servers will retry delivery. If you're
concerned about timeliness, spend $10 and a day on setting up a
cloud VM as a secondary MX. That also gives you experience in 
setting up your mail server software.

-dsr-

Re: linux headers and upgrading nvidia driver

[Greg Wooledge]

On Thu, Sep 15, 2022 at 03:01:24PM +0200, Thomas Anderson wrote:
> How can i find the linux header, to point my driver to?

apt-get install linux-headers-$(uname -r)

linux headers and upgrading nvidia driver

[Thomas Anderson]

First off, I am running Debian 9, Stretch. I know it is old and I should 
upgrade and that is something I want to do.


The primary problem is that I have a lot of important systems (email, 
cloud), and other less important (web host). Simple dist-upgrades have 
always broken my mail server, that I was not immediately able to recover 
(fortunately, I had made a backup before). I have tried a couple of 
times to upgrade, but all attempts have failed. Thus, why I am still 
stick on 9. I don't like it, and still want to upgrade.


All that said, also I have been stuck on installing a simple nvidia 
driver, also for months. I can install both the backports version and 
the downloaded from nvidia version, but a driver can never be loaded 
because of some linux headers error.  I know nvidia and linux have never 
been nice to each other.


I think these problems are related.

I currently have 4.19.0-0.bpo.amd64 headers. I try rebuilding them, also 
tried going back to 4.9.0-13--but the former still stays. the nvidia 
installer always says it can't find the kernel to build the driver. If 
my system keeps saying it's 4.19.0-0.bpo, why isn't it in the standard 
location? I have tried to locate it, but I cannot find it?


How can i find the linux header, to point my driver to?

thanks in advance, sorry for the long sob story.

Re: ooops upgrading buster -> bullseye

[mick.crane]

On 2022-07-24 14:00, Dan Ritter wrote:

aces and eights wrote:
upgrading buster to bullseye answered "keep old config" to a few 
things now
roundcube is not working. Install I was using was from roundcube 
source not

debian.
I try to purge roundcube and start again,.
but there are messages.

<.>

apt purge roundcube roundcube-core
rm -rf /etc/roundcube
apt install roundcube

That said, unless you absolutely love roundcube, you might want
to look into alternatives. Although it's not packaged in Debian,
snappymail -- https://snappymail.eu/ -- is easy to install and
very good. The license is AGPL, so it could be packaged (and
probably should be.)


thanks

mick

Re: ooops upgrading buster -> bullseye

[Dan Ritter]

aces and eights wrote: 
> upgrading buster to bullseye answered "keep old config" to a few things now
> roundcube is not working. Install I was using was from roundcube source not
> debian.
> I try to purge roundcube and start again,.
> but there are messages.
> 
> apt install roundcube
> .
> Setting up roundcube-core (1.4.13+dfsg.1-1~deb11u1) ...
> Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
> dbconfig-common: writing config to /etc/dbconfig-common/roundcube.conf
> Not replacing deleted config file /etc/roundcube/debian-db.php
> ERROR: Configuration error. Unsupported database driver:
> dpkg: error processing package roundcube-core (--configure):
>  installed roundcube-core package post-installation script subprocess
> returned error exit status 1
> Setting up php-gd (2:7.4+76) ...
> dpkg: dependency problems prevent configuration of roundcube:
>  roundcube depends on roundcube-core (= 1.4.13+dfsg.1-1~deb11u1); however:
>   Package roundcube-core is not configured yet.
> 
> dpkg: error processing package roundcube (--configure):
>  dependency problems - leaving unconfigured
> Processing triggers for libapache2-mod-php7.4 (7.4.30-1+deb11u1) ...
> Processing triggers for fontconfig (2.13.1-4.2) ...
> Processing triggers for libc-bin (2.31-13+deb11u3) ...
> Processing triggers for man-db (2.9.4-2) ...
> Processing triggers for php7.4-cli (7.4.30-1+deb11u1) ...
> Processing triggers for php7.4-phpdbg (7.4.30-1+deb11u1) ...
> Errors were encountered while processing:
>  roundcube-core
>  roundcube
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> --
> I thought that the database was MarianDB but maybe not.
> How do I get rid of what causes the error and start again ?

apt purge roundcube roundcube-core
rm -rf /etc/roundcube
apt install roundcube

That said, unless you absolutely love roundcube, you might want
to look into alternatives. Although it's not packaged in Debian,
snappymail -- https://snappymail.eu/ -- is easy to install and
very good. The license is AGPL, so it could be packaged (and
probably should be.)

-dsr-

ooops upgrading buster -> bullseye

[aces and eights]

upgrading buster to bullseye answered "keep old config" to a few things now
roundcube is not working. Install I was using was from roundcube source not
debian.
I try to purge roundcube and start again,.
but there are messages.

apt install roundcube
.
Setting up roundcube-core (1.4.13+dfsg.1-1~deb11u1) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/roundcube.conf
Not replacing deleted config file /etc/roundcube/debian-db.php
ERROR: Configuration error. Unsupported database driver:
dpkg: error processing package roundcube-core (--configure):
 installed roundcube-core package post-installation script subprocess
returned error exit status 1
Setting up php-gd (2:7.4+76) ...
dpkg: dependency problems prevent configuration of roundcube:
 roundcube depends on roundcube-core (= 1.4.13+dfsg.1-1~deb11u1); however:
  Package roundcube-core is not configured yet.

dpkg: error processing package roundcube (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libapache2-mod-php7.4 (7.4.30-1+deb11u1) ...
Processing triggers for fontconfig (2.13.1-4.2) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for php7.4-cli (7.4.30-1+deb11u1) ...
Processing triggers for php7.4-phpdbg (7.4.30-1+deb11u1) ...
Errors were encountered while processing:
 roundcube-core
 roundcube
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
I thought that the database was MarianDB but maybe not.
How do I get rid of what causes the error and start again ?

mick

Re: debian app on UserLAnd: upgrading to bullseye

[Anssi Saari]

agyaana...@yahoo.com writes:

> am i missing on something. i have limited data plan. hence, requesting 
> opinion or suggestions here.

One suggestion then would be to uninstall any software you're not using
so it doesn't have to be updated and use up your data plan. The release
notes cover some other cleanup tasks as well.

I also like to make sure I have enough disk space for the update, this
is also covered in the release notes.

Re: debian app on UserLAnd: upgrading to bullseye

[Alexander V. Makartsev]

On 09.06.2022 19:41, agyaana...@yahoo.com wrote:

i have installed debian (buster) on userland app (UserLAnd is an open-source 
app which allows you to run several Linux distributions like Ubuntu,
Debian, and Kali.)

i am keen to upgrade to bullseye.
my action:
* sudo apt-get update && apt-get full-upgrade
* sudo nano /etc/apt/sources.list: replace buster with bullseye
* sudo apt-get update && apt-get upgrade && apt-get dist-upgrade

am i missing on something. i have limited data plan. hence, requesting opinion 
or suggestions here.
In addition to suggestion from Andrew you should skim through Bullseye's 
release notes¹.



[1] https://www.debian.org/releases/stable/amd64/release-notes/

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: debian app on UserLAnd: upgrading to bullseye

[Andrew M.A. Cater]

On Thu, Jun 09, 2022 at 02:41:40PM +, agyaana...@yahoo.com wrote:
> i have installed debian (buster) on userland app (UserLAnd is an open-source 
> app which allows you to run several Linux distributions like Ubuntu,
> Debian, and Kali.)
> 
> i am keen to upgrade to bullseye.
> my action:
> * sudo apt-get update && apt-get full-upgrade
> * sudo nano /etc/apt/sources.list: replace buster with bullseye
> * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade
> 
> am i missing on something. i have limited data plan. hence, requesting 
> opinion or suggestions here.
> 
> regards,
> agyaan
>

Hi Agyaan

One thing you _have_ to do is check your /etc/apt/sources.list as this changed
slightly between buster and bullseye - https://wiki.debian.org/SourcesList
refers to the changes.

With every good wish, as ever,

Andy Cater 

Re: debian app on UserLAnd: upgrading to bullseye

[Roberto C . Sánchez]

On Thu, Jun 09, 2022 at 02:41:40PM +, agyaana...@yahoo.com wrote:
> i have installed debian (buster) on userland app (UserLAnd is an open-source 
> app which allows you to run several Linux distributions like Ubuntu,
> Debian, and Kali.)
> 
> i am keen to upgrade to bullseye.
> my action:
> * sudo apt-get update && apt-get full-upgrade
> * sudo nano /etc/apt/sources.list: replace buster with bullseye
> * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade
> 
> am i missing on something. i have limited data plan. hence, requesting 
> opinion or suggestions here.
> 
Have you read the release notes?  That should be considered an
obligatory step.

Regards,

-Roberto

-- 
Roberto C. Sánchez

debian app on UserLAnd: upgrading to bullseye

[agyaanapan]

i have installed debian (buster) on userland app (UserLAnd is an open-source 
app which allows you to run several Linux distributions like Ubuntu,
Debian, and Kali.)

i am keen to upgrade to bullseye.
my action:
* sudo apt-get update && apt-get full-upgrade
* sudo nano /etc/apt/sources.list: replace buster with bullseye
* sudo apt-get update && apt-get upgrade && apt-get dist-upgrade

am i missing on something. i have limited data plan. hence, requesting opinion 
or suggestions here.

regards,
agyaan

Re: date & X copy/paste broke on upgrading to Debian 11

[Michael Stone]

On Sun, Feb 06, 2022 at 06:54:26PM +, Brian wrote:

It does. Installation of chrony or ntp removeds the traditional
systemd-timesyncd package.


I'm somewhat amused by the characterization of systemd-timesyncd as 
"traditional" over ntpd, a program which has existed since the late 80s.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 08:03:55PM -0600, David Wright wrote:
> Technically, I think you get bracketed paste through anything that
> uses readline (the animal that reads ~/.inputrc).

Yes.  Potentailly, at least.

> As a workaround, do the CUA keys work? That is, cutting with ^X,
> copying with ^C and pasting with ^V. Are there menus or options
> in XFCE for selecting this method?

Those won't work for copy/paste in a shell, of course.  They may work
in a GUI application.  Shift-Insert also tends to work for pasting in
many applications, including rxvt-unicode (my terminal emulator) and
xterm, even when sitting at a shell prompt.

Re: date & X copy/paste broke on upgrading to Debian 11

[David Wright]

On Sun 06 Feb 2022 at 18:03:42 (-0500), Greg Wooledge wrote:
> On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote:
> > On Sun, 6 Feb 2022 15:59:34 -0500 Greg Wooledge wrote:
> > > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > > > 
> > > > Does anybody know why the X copy/paste issue is happening? So far I
> > > > have only got help with time.
> > > 
> > > https://lists.debian.org/debian-user/2022/02/msg00144.html
> > > 
> > > https://lists.debian.org/debian-user/2022/02/msg00151.html
> > 
> > Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering 
> > from this everywhere, not only in bash.

Technically, I think you get bracketed paste through anything that
uses readline (the animal that reads ~/.inputrc).

And before what follows, is dragging actually working?

> What symptom are you actually seeing?  What happens when you click the
> middle button, while focus is on a terminal sitting at a bash prompt,
> and while something has been selected?
> 
> Do you get a mangled paste?  Do you get a correct paste, except that it's
> in "inverse video"?  Do you get nothing at all?
> 
> If it's nothing at all, how sure are you that it's not a hardware problem?
> Have you tried a different mouse?  Have you tried using xev to see whether
> the Button2 up/down events are actually being received by the X server?

As a workaround, do the CUA keys work? That is, cutting with ^X,
copying with ^C and pasting with ^V. Are there menus or options
in XFCE for selecting this method?

Cheers,
David.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote:
> On Sun, 6 Feb 2022 15:59:34 -0500
> Greg Wooledge  wrote:
> 
> > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > > Thanks everybody for your input.
> > > 
> > > Does anybody know why the X copy/paste issue is happening? So far I
> > > have only got help with time.
> > 
> > https://lists.debian.org/debian-user/2022/02/msg00144.html
> > 
> > https://lists.debian.org/debian-user/2022/02/msg00151.html
> 
> Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering 
> from this everywhere, not only in bash.

What symptom are you actually seeing?  What happens when you click the
middle button, while focus is on a terminal sitting at a bash prompt,
and while something has been selected?

Do you get a mangled paste?  Do you get a correct paste, except that it's
in "inverse video"?  Do you get nothing at all?

If it's nothing at all, how sure are you that it's not a hardware problem?
Have you tried a different mouse?  Have you tried using xev to see whether
the Button2 up/down events are actually being received by the X server?

Re: date & X copy/paste broke on upgrading to Debian 11

[José Luis González]

On Sun, 6 Feb 2022 15:59:34 -0500
Greg Wooledge  wrote:

> On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > Thanks everybody for your input.
> > 
> > Does anybody know why the X copy/paste issue is happening? So far I
> > have only got help with time.
> 
> https://lists.debian.org/debian-user/2022/02/msg00144.html
> 
> https://lists.debian.org/debian-user/2022/02/msg00151.html

Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering from 
this everywhere, not only in bash.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> Thanks everybody for your input.
> 
> Does anybody know why the X copy/paste issue is happening? So far I
> have only got help with time.

https://lists.debian.org/debian-user/2022/02/msg00144.html

https://lists.debian.org/debian-user/2022/02/msg00151.html

Re: date & X copy/paste broke on upgrading to Debian 11

[José Luis González]

On Sun, 6 Feb 2022 09:17:35 -0500
Greg Wooledge  wrote:

> On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote:
> > Hi,
> > 
> > José Luis González wrote:
> > > 2. Copy and paste in X don't work anymore by selecting and clicking on
> > > mouse button 2.
> > 
> > "bracketed paste", maybe ?
> 
> Depends on where he's pasting.  Bracketed paste doesn't actually stop
> middle-click pastes from working in bash in a terminal; it just makes
> it look weird, and requires a confirming Enter keypress if you paste
> commands with newlines in them.
> 
> José, *where* are you trying to paste, that isn't working?  At a bash
> prompt?  Inside an editor running in a terminal?  Inside an editor
> that is a GUI program?  Inside some other GUI program like a web
> browser?

From XFCE's to XFCE's terminal emulator, for instance. Also, I tried now from 
the terminal to Sylpheed (the window where I'm composing this message), and 
from Sylpheed to Sylpheed (same window text edit widget).

Re: date & X copy/paste broke on upgrading to Debian 11

[José Luis González]

Thanks everybody for your input.

Does anybody know why the X copy/paste issue is happening? So far I
have only got help with time.


On Sun, 6 Feb 2022 18:54:26 +
Brian  wrote:

> On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote:
> 
> > On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> > > That said, I notice you have ntp installed. Does that mean that
> > > you're keeping your time synchronised with ntp and, if so, what
> > > do you do about systemd-timesyncd, which I understand is enabled
> > > by default since several Debian versions ago.
> > 
> > If an NTP package is installed, systemd-timesyncd is not used.  It
> > just never starts.
> > 
> > On my system, it's not even installed.
> > 
> > After digging around a bit, I think Debian has changed something on me,
> > which I didn't notice until now.
> > 
> > In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
> > would coexist.  systemd-timesyncd.service was configured so that the
> > daemon wouldn't be started if any of the other NTP daemons existed on
> > the system.
> > 
> > I can no longer see that in the systemd-timesyncd.service file (which
> > I'm viewing as
> > 
> > because it's not on my system).
> > 
> > Instead, the ntp and systemd-timesyncd *packages* now appear to have
> > 
> > Provides: time-daemon
> > 
> > which might make them mutually exclusive.
> 
> It does. Installation of chrony or ntp removeds the traditional
> systemd-timesyncd package.
> 
> -- 
> Brian.
> 

Re: date & X copy/paste broke on upgrading to Debian 11

[José Luis González]

On Sun, 6 Feb 2022 11:20:37 +
"Andrew M.A. Cater"  wrote:

> On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote:
> > Hi,
> > 
> > Upon upgrading to Debian 11 several things broke.
> > 
> > The two that come to my attention now are:
> > 
> > 1. System time is one hour more than it should. Timezone (as set by
> > tzdata) is correct.
> > 
> 
> Hi 

Hi Andrew,

Thanks for stepping in.

> System time:  what time does the motherboard think it is - so BIOS / firmware?

It seems date was set for localtime at the BIOS, so I have updated it to UTC so 
that it works with Debian.

> Is the system dual booting with another OS which assumes that it has 
> control of the clock (usually Windows and setting local timezones
> with daylight saving time)?

No, the system only has Debian. No dual booting.

> Hope this helps, any more details you can give may be helpful.

It seems with the BIOS adjust it's running right. Thanks for your input. You 
made me realize what it was.

Re: date & X copy/paste broke on upgrading to Debian 11

[Brian]

On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote:

> On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> > That said, I notice you have ntp installed. Does that mean that
> > you're keeping your time synchronised with ntp and, if so, what
> > do you do about systemd-timesyncd, which I understand is enabled
> > by default since several Debian versions ago.
> 
> If an NTP package is installed, systemd-timesyncd is not used.  It
> just never starts.
> 
> On my system, it's not even installed.
> 
> After digging around a bit, I think Debian has changed something on me,
> which I didn't notice until now.
> 
> In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
> would coexist.  systemd-timesyncd.service was configured so that the
> daemon wouldn't be started if any of the other NTP daemons existed on
> the system.
> 
> I can no longer see that in the systemd-timesyncd.service file (which
> I'm viewing as
> 
> because it's not on my system).
> 
> Instead, the ntp and systemd-timesyncd *packages* now appear to have
> 
> Provides: time-daemon
> 
> which might make them mutually exclusive.

It does. Installation of chrony or ntp removeds the traditional
systemd-timesyncd package.

-- 
Brian.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> That said, I notice you have ntp installed. Does that mean that
> you're keeping your time synchronised with ntp and, if so, what
> do you do about systemd-timesyncd, which I understand is enabled
> by default since several Debian versions ago.

If an NTP package is installed, systemd-timesyncd is not used.  It
just never starts.

On my system, it's not even installed.

After digging around a bit, I think Debian has changed something on me,
which I didn't notice until now.

In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
would coexist.  systemd-timesyncd.service was configured so that the
daemon wouldn't be started if any of the other NTP daemons existed on
the system.

I can no longer see that in the systemd-timesyncd.service file (which
I'm viewing as

because it's not on my system).

Instead, the ntp and systemd-timesyncd *packages* now appear to have

Provides: time-daemon

which might make them mutually exclusive.

Re: date & X copy/paste broke on upgrading to Debian 11

[Brian]

On Sun 06 Feb 2022 at 09:44:54 -0700, Charles Curley wrote:

> On Sun, 6 Feb 2022 09:12:01 -0500
> Greg Wooledge  wrote:
> 
> > My first question for José is: what does the date command *actually*
> > say?  (Follow-ups: What time zone are you in?  How did you configure
> > the time zone?  Are you running an NTP daemon?  If so, which one, and
> > what does "ntpq -p" report?)
> 
> If you aren't running an NTP daemon, are you running systemd's time
> client, time-sync? What result do you get from
> 
> systemctl status time-sync.target
> 
> (I have a small herd of Debian boxen. One runs ntpd to synch with the
> outside world. All the rest run time-sync and synch on the ntpd box. It
> works quiet well.)

I have always used chrony. It appears have gained more traction over
ntpd recently.

  https://lists.debian.org/debian-devel/2022/01/msg00172.html
  https://engineering.fb.com/2020/03/18/production-engineering/ntp-service/

-- 
Brian.

Re: date & X copy/paste broke on upgrading to Debian 11

[Charles Curley]

On Sun, 6 Feb 2022 09:12:01 -0500
Greg Wooledge  wrote:

> My first question for José is: what does the date command *actually*
> say?  (Follow-ups: What time zone are you in?  How did you configure
> the time zone?  Are you running an NTP daemon?  If so, which one, and
> what does "ntpq -p" report?)

If you aren't running an NTP daemon, are you running systemd's time
client, time-sync? What result do you get from

systemctl status time-sync.target

(I have a small herd of Debian boxen. One runs ntpd to synch with the
outside world. All the rest run time-sync and synch on the ntpd box. It
works quiet well.)

-- 
Does anybody read signatures any more?

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

Re: date & X copy/paste broke on upgrading to Debian 11

[David Wright]

On Sun 06 Feb 2022 at 09:12:01 (-0500), Greg Wooledge wrote:
> On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote:
> > * 2022-02-06 11:58:08+0100, José Luis González wrote:
> > 
> > > 1. System time is one hour more than it should. Timezone (as set by
> > > tzdata) is correct.
> > 
> > Nowadays "timedatectl" is used to configure time.
> 
> Strongly disagree.  I mean, it *could* be... but you state it like it's
> an absolute imperative.
> 
> Many of us still use the traditional tools.
> 
> My first question for José is: what does the date command *actually*
> say?  (Follow-ups: What time zone are you in?  How did you configure
> the time zone?  Are you running an NTP daemon?  If so, which one, and
> what does "ntpq -p" report?)
> 
> E.g. for me, I am in the US/Eastern time zone (now called America/New_York)
> and I'm running the "ntp" daemon.  I don't have the TZ variable set.
> So, my setup looks like this:
> 
> unicorn:~$ echo "$TZ"
> 
> unicorn:~$ cat /etc/timezone
> America/New_York
> unicorn:~$ ls -ld /etc/localtime
> lrwxrwxrwx 1 root root 36 Oct 27 07:16 /etc/localtime -> 
> /usr/share/zoneinfo/America/New_York
> unicorn:~$ dpkg -l ntp | tail -1
> ii  ntp1:4.2.8p15+dfsg-1 amd64Network Time Protocol 
> daemon and utility programs
> unicorn:~$ ntpq -p
>  remote   refid  st t when poll reach   delay   offset  jitter
> ==
>  0.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
>  1.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
>  2.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
>  3.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
> -vps-d455c3c7.vp 91.189.91.1573 u  759 1024  377   74.942   +1.701   0.819
> +172.106.167.46  209.51.161.238   2 u  543 1024  377   62.995   +1.964   1.041
> -time.nullrouten 132.163.97.1 2 u  485 1024  377   93.519   +0.097   0.823
> *time-sjc.0xt.ca 17.253.4.125 2 u  845 1024  377   96.872   +0.563   2.251
> +li1210-167.memb 66.220.9.122 2 u  566 1024  377   96.236   +0.522  10.941
> -clock.fmt.he.ne .CDMA.   1 u  968 1024  377   93.254   -1.045   7.428
> unicorn:~$ date
> Sun Feb  6 09:05:43 EST 2022
> 
> Note in particular that the timezone is configured in *two* different
> places using two different mechanisms.  Some programs use one, and some
> use the other, so you need to do both.  "Welcome to Unix, kid."  (The
> Debian installer takes care of this for you, if you choose the time zone
> correctly during installation.)
> 
> Andrew's reply about hwclock is also relevant if José is dual-booting
> with another operating system.  Are you doing that, José?

It does seem quite likely that there's a misunderstanding over
timezones, as the OP is posting from +1 and their clock is one
hour in error. They may have to decide whether to run the RTC
in UT (in general the only sensible choice) or Local Time.

(I'm not sure whether DST in relevant at this time of year in
this timezone, unless they observe it in Tristan da Cunha.)

That said, I notice you have ntp installed. Does that mean that
you're keeping your time synchronised with ntp and, if so, what
do you do about systemd-timesyncd, which I understand is enabled
by default since several Debian versions ago.

About setting   hwclock --systohc   directly, I see two problems:
the system's timekeeper might merely set it again itself, losing
whatever you set it to, and also it screws up any calibrations
being made on the RTC's drift.

Cheers,
David.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote:
> Hi,
> 
> José Luis González wrote:
> > 2. Copy and paste in X don't work anymore by selecting and clicking on
> > mouse button 2.
> 
> "bracketed paste", maybe ?

Depends on where he's pasting.  Bracketed paste doesn't actually stop
middle-click pastes from working in bash in a terminal; it just makes
it look weird, and requires a confirming Enter keypress if you paste
commands with newlines in them.

José, *where* are you trying to paste, that isn't working?  At a bash
prompt?  Inside an editor running in a terminal?  Inside an editor
that is a GUI program?  Inside some other GUI program like a web
browser?

vim for example now has a default system-wide vimrc configuration that
does funky things with the mouse, and interferes with traditional
middle-click pasting.  If you're having this issue in vim, you can
work around it by doing either of these two things:

1) Have a personal ~/.vimrc file that overrides the system default.

2) Hold Shift while clicking to paste.

See  for more on that
change.

Re: date & X copy/paste broke on upgrading to Debian 11

[Greg Wooledge]

On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote:
> * 2022-02-06 11:58:08+0100, José Luis González wrote:
> 
> > 1. System time is one hour more than it should. Timezone (as set by
> > tzdata) is correct.
> 
> Nowadays "timedatectl" is used to configure time.

Strongly disagree.  I mean, it *could* be... but you state it like it's
an absolute imperative.

Many of us still use the traditional tools.

My first question for José is: what does the date command *actually*
say?  (Follow-ups: What time zone are you in?  How did you configure
the time zone?  Are you running an NTP daemon?  If so, which one, and
what does "ntpq -p" report?)

E.g. for me, I am in the US/Eastern time zone (now called America/New_York)
and I'm running the "ntp" daemon.  I don't have the TZ variable set.
So, my setup looks like this:

unicorn:~$ echo "$TZ"

unicorn:~$ cat /etc/timezone
America/New_York
unicorn:~$ ls -ld /etc/localtime
lrwxrwxrwx 1 root root 36 Oct 27 07:16 /etc/localtime -> 
/usr/share/zoneinfo/America/New_York
unicorn:~$ dpkg -l ntp | tail -1
ii  ntp1:4.2.8p15+dfsg-1 amd64Network Time Protocol daemon 
and utility programs
unicorn:~$ ntpq -p
 remote   refid  st t when poll reach   delay   offset  jitter
==
 0.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
 1.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
 2.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
 3.debian.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
-vps-d455c3c7.vp 91.189.91.1573 u  759 1024  377   74.942   +1.701   0.819
+172.106.167.46  209.51.161.238   2 u  543 1024  377   62.995   +1.964   1.041
-time.nullrouten 132.163.97.1 2 u  485 1024  377   93.519   +0.097   0.823
*time-sjc.0xt.ca 17.253.4.125 2 u  845 1024  377   96.872   +0.563   2.251
+li1210-167.memb 66.220.9.122 2 u  566 1024  377   96.236   +0.522  10.941
-clock.fmt.he.ne .CDMA.   1 u  968 1024  377   93.254   -1.045   7.428
unicorn:~$ date
Sun Feb  6 09:05:43 EST 2022

Note in particular that the timezone is configured in *two* different
places using two different mechanisms.  Some programs use one, and some
use the other, so you need to do both.  "Welcome to Unix, kid."  (The
Debian installer takes care of this for you, if you choose the time zone
correctly during installation.)

Andrew's reply about hwclock is also relevant if José is dual-booting
with another operating system.  Are you doing that, José?

Re: date & X copy/paste broke on upgrading to Debian 11

[Teemu Likonen]

* 2022-02-06 11:58:08+0100, José Luis González wrote:

> 1. System time is one hour more than it should. Timezone (as set by
> tzdata) is correct.

Nowadays "timedatectl" is used to configure time. Run the command
without arguments first. Then see its manual page and perhaps use some
of the following subcommands:

timedatectl set-timezone [...]
timedatectl set-local-rct [...]
timedatectl set-time [...]
timedatectl set-ntp [...]

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462


signature.asc
Description: PGP signature

Re: date & X copy/paste broke on upgrading to Debian 11

[Andrew M.A. Cater]

On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote:
> Hi,
> 
> Upon upgrading to Debian 11 several things broke.
> 
> The two that come to my attention now are:
> 
> 1. System time is one hour more than it should. Timezone (as set by
> tzdata) is correct.
> 

Hi 

System time:  what time does the motherboard think it is - so BIOS / firmware?

If you set the time using the date command / a systems setting app
and then run 

hwclock --systohc

what happens?

hwclock is a small utility to set the hardware clock.

[This way round is system time -> hardware clock or you can do 

hwclock --hctosys 

to set the other way round.]

Is the system dual booting with another OS which assumes that it has 
control of the clock (usually Windows and setting local timezones
with daylight saving time)?

Hope this helps, any more details you can give may be helpful.

With every good wish, as ever,

Andy Cater

> 2. Copy and paste in X don't work anymore by selecting and clicking on
> mouse button 2.
> 
> I'm running XFCE, if it is of any help.
> 

Re: date & X copy/paste broke on upgrading to Debian 11

[Thomas Schmitt]

Hi,

José Luis González wrote:
> 2. Copy and paste in X don't work anymore by selecting and clicking on
> mouse button 2.

"bracketed paste", maybe ?

It was discussed on this list in the recent months.
See

  
https://lists.debian.org/cgi-bin/search?P=bracketed+paste=or=Gdebian-user==10


Have a nice day :)

Thomas

date & X copy/paste broke on upgrading to Debian 11

[José Luis González]

Hi,

Upon upgrading to Debian 11 several things broke.

The two that come to my attention now are:

1. System time is one hour more than it should. Timezone (as set by
tzdata) is correct.

2. Copy and paste in X don't work anymore by selecting and clicking on
mouse button 2.

I'm running XFCE, if it is of any help.

Re: Problems upgrading from Debian 10 to 11

[Andrei POPESCU]

On Ma, 14 dec 21, 21:27:28, James Dutton wrote:
>
> I tried the newer xrdp/xorgxrdp .deb from the debian repo, but they
> did not install (dependent on different libs not in Bullseye.
> I then compiled xrdp and xorgxrdp from git sources, and they compiled
> and ran ok in Bullseye.
> That is what I am currently using, as a work around, for the Bullseye
> problem I am having with xrdp.
> So, yes, a newer version of xrdp/xorgxrdp does compile and work in Bullseye.
> 
> Are there any specific commands you would like me to run, to maybe
> test or compile a different version?
> I am happy to test anything that might help get a working xrdp, sooner
> rather than later in the debian bullseye repo.

My first suggestion would be to try to recompile the package in testing 
on stable, e.g. as per https://wiki.debian.org/SimpleBackportCreation. 
This could be easier for you to maintain instead of compiling from 
source.

You could also try asking for a backport on -backports, preferably with 
a Cc to the maintainer *and* mentioning the additional features of the 
version in testing (if any).

The backports archive isn't supposed to be used to fix bugs in stable 
(see the archives, this is constantly brought up), though I acknowledge 
this may leave users in a bad situation if the bug isn't fixed in stable 
either (regardless of the reason).

An offer for assistance in fixing the bug in stable, like identifying 
the relevant upstream commit(s) fixing the issue and helping with 
backporting them to the older versions could also help get things 
moving.

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Problems upgrading from Debian 10 to 11

[James Dutton]

On Tue, 14 Dec 2021 at 08:34, Andrei POPESCU  wrote:
>
> On Du, 12 dec 21, 11:25:14, James Dutton wrote:
> >
> > I am struggling to understand why debian would not move to the bug
> > fixed version from upstream xorgxrdp ?
> > Just to clarify, Debian has picked version 0.2.12 fairly randomly,
> > without ever testing it.
>
> This is rather dismissive of the Maintainer's work.
I apologise.

>
> > Version 0.2.12 results in xrdp having zero functionality.  Think P1 here.
> > The author of xorgxrdp acknowledges that 0.2.12 is faulty and should
> > not be used at all, because it does not work at all.
> > The author recommends moving to a version that actually works!
> > But will Debian upgrade it...
> > "Generally no, at least not in bullseye..."
> >
> > Where is the logic in that?
>
> Debian releases are built with the premise that versions shouldn't
> change (that's what 'stable' implies).
>
> Over the years specific exceptions were accepted and xrdb might qualify
> for one as well.
>
> Does a newer xrdp (e.g. the version in testing) even compile on
> bullseye?
>
I tried the newer xrdp/xorgxrdp .deb from the debian repo, but they
did not install (dependent on different libs not in Bullseye.
I then compiled xrdp and xorgxrdp from git sources, and they compiled
and ran ok in Bullseye.
That is what I am currently using, as a work around, for the Bullseye
problem I am having with xrdp.
So, yes, a newer version of xrdp/xorgxrdp does compile and work in Bullseye.

Are there any specific commands you would like me to run, to maybe
test or compile a different version?
I am happy to test anything that might help get a working xrdp, sooner
rather than later in the debian bullseye repo.

As some background. At work we have 100s of Linux virtual machines,
hosted on our own physical hardware. I.e. not AWS etc. They cover test
systems and production systems.
The work laptops are Windows (all the outsourced company will
support), and everyone uses windows "Remote Desktop Protocol" and
"putty" (ssh) to access them.
So, right now, xrdp not working kind of prevents any of those 1000s of
Linux servers from moving to Bullseye.
xrdp is actually an extremely useful tool, when integrating windows
and Linux environments.

So far, we have not discovered any other Bullseye packages that would
prevent us using Bullseye,

Kind Regards

James

Re: Problems upgrading from Debian 10 to 11

[Andrei POPESCU]

On Du, 12 dec 21, 11:25:14, James Dutton wrote:
> 
> I am struggling to understand why debian would not move to the bug
> fixed version from upstream xorgxrdp ?
> Just to clarify, Debian has picked version 0.2.12 fairly randomly,
> without ever testing it.

This is rather dismissive of the Maintainer's work.

> Version 0.2.12 results in xrdp having zero functionality.  Think P1 here.
> The author of xorgxrdp acknowledges that 0.2.12 is faulty and should
> not be used at all, because it does not work at all.
> The author recommends moving to a version that actually works!
> But will Debian upgrade it...
> "Generally no, at least not in bullseye..."
> 
> Where is the logic in that?

Debian releases are built with the premise that versions shouldn't 
change (that's what 'stable' implies).

Over the years specific exceptions were accepted and xrdb might qualify 
for one as well.

Does a newer xrdp (e.g. the version in testing) even compile on 
bullseye?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Problems upgrading from Debian 10 to 11

[James Dutton]

On Sun, 12 Dec 2021 at 09:10, Andrei POPESCU  wrote:
>
> On Sb, 11 dec 21, 16:54:04, James Dutton wrote:
> > Hi,
> >
> > After upgrading from Debian 10 to Debian 11, xrdp stopped working.
> > Someone else has a very good description of the problem here:
> > https://c-nergy.be/blog/?p=17113
> >
> > Essentially, the problem is fixed by upgrading xorgxrdp to a version
> > newer than 0.2.12.
> >
> > When I compiled the latest xrdp from the latest sources, xrdp worked again.
> > Please can debian release a more up to date version of xorgxrdp?
>
> Generally no, at least not in bullseye, but if it is possible to
> backport the fix it might qualify for a stable update.
>
> Is this your issue?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996176
>
> Kind regards,
> Andrei
>

I raised this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001539
It is similar to the one you mention.

I am struggling to understand why debian would not move to the bug
fixed version from upstream xorgxrdp ?
Just to clarify, Debian has picked version 0.2.12 fairly randomly,
without ever testing it.
Version 0.2.12 results in xrdp having zero functionality.  Think P1 here.
The author of xorgxrdp acknowledges that 0.2.12 is faulty and should
not be used at all, because it does not work at all.
The author recommends moving to a version that actually works!
But will Debian upgrade it...
"Generally no, at least not in bullseye..."

Where is the logic in that?

Re: Problems upgrading from Debian 10 to 11

[Andrei POPESCU]

On Sb, 11 dec 21, 16:54:04, James Dutton wrote:
> Hi,
> 
> After upgrading from Debian 10 to Debian 11, xrdp stopped working.
> Someone else has a very good description of the problem here:
> https://c-nergy.be/blog/?p=17113
> 
> Essentially, the problem is fixed by upgrading xorgxrdp to a version
> newer than 0.2.12.
> 
> When I compiled the latest xrdp from the latest sources, xrdp worked again.
> Please can debian release a more up to date version of xorgxrdp?

Generally no, at least not in bullseye, but if it is possible to 
backport the fix it might qualify for a stable update.

Is this your issue?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996176

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Problems upgrading from Debian 10 to 11

[Charles Curley]

On Sat, 11 Dec 2021 16:54:04 +
James Dutton  wrote:

> When I compiled the latest xrdp from the latest sources, xrdp worked
> again. Please can debian release a more up to date version of
> xorgxrdp?

You probably ought to file a bug against xrdp.

-- 
Does anybody read signatures any more?

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

Problems upgrading from Debian 10 to 11

[James Dutton]

Hi,

After upgrading from Debian 10 to Debian 11, xrdp stopped working.
Someone else has a very good description of the problem here:
https://c-nergy.be/blog/?p=17113

Essentially, the problem is fixed by upgrading xorgxrdp to a version
newer than 0.2.12.

When I compiled the latest xrdp from the latest sources, xrdp worked again.
Please can debian release a more up to date version of xorgxrdp?


Extract from the URL above:
Root Cause of the issue

We had to look a little bit further in order to find out what it’s
really causing the issue.  Based the the bug/issue reported to the
team behind xrdp software (see
https://github.com/neutrinolabs/xorgxrdp/issues/156),  the problem is
only present when using the xorgxrdp package version 0.2.12.  Previous
version of Debian (Debian 10) was using the package version 0.2.9 and
we didn’t encountered the issue…Debian 11 is shipping with the
problematic version (i.e. 0.2.12) and this explain why the connection
is failing.

The only fix proposed by xRDP team is basically to upgrade the
xorgxrdp package to a more recent version which is exactly what’s
happening when you are performing the custom installation….

Re: apt automatically upgrading packages in unstable

[Nils]

On Debian Sid I recommend disabling the unattended-upgrades services entirely:
sudo systemctl disable --now unattended-upgrades


On Friday, October 1, 2021 2:36:37 PM CEST Miguel A. Vallejo wrote:
> A few days ago I noticed my debian unstable started to update packages
> automatically. A quick inspection showed apt was updated, and also the
> configuration files in /etc/apt/apt.conf.d, including a
> 20auto-upgrades file with all options enabled.
> 
> Because auto update in sid is at least dangerous, what is the right
> way to keep apt configuration between apt updates?
> 
> Thank you



signature.asc
Description: This is a digitally signed message part.

Re: Upgrading binary: nginx

[Reco]

Hi.

On Sat, Oct 02, 2021 at 12:03:36PM +0200, pk wrote:
> I got this message when installing nginx-light today. What does it
> mean and where does it come from? I could not grep it in the
> nginx-light .deb.

It's the usual nginx behaviour on restart.
Instead of shutting down nginx completely and then running a new set of
nginx processes it merely re-executes the same binary in each its
process.
The end result is the same (i.e. you have fresh set of processes running
from an updated binary), the implementation requires some creative
coding (which is why nginx has it, and apache does not).

tl;dr version - nginx did what it was supposed to.

Reco

Upgrading binary: nginx

[pk]

I got this message when installing nginx-light today. What does it
mean and where does it come from? I could not grep it in the
nginx-light .deb.

# aptitude -D -V install nginx-light
Följande NYA paket kommer att bli installerade:
  libnginx-mod-http-echo{a} [1.18.0-6.1] (B: nginx-light)
nginx-common{a} [1.18.0-6.1] (B: libnginx-mod-http-echo, B:
nginx-light)
  nginx-light [1.18.0-6.1]
0 paket att uppgradera, 3 att nyinstallera, 0 att ta bort och 1 inte
uppgraderade.
Behöver hämta 726 kB arkiv. Efter uppackning kommer 1.744 kB diskplats
att användas.
Vill du fortsätta? [Y/n/?]
Läs: 1 http://deb.debian.org/debian bullseye/main amd64 nginx-common
all 1.18.0-6.1 [125 kB]
Läs: 2 http://deb.debian.org/debian bullseye/main amd64
libnginx-mod-http-echo amd64 1.18.0-6.1 [109 kB]
Läs: 3 http://deb.debian.org/debian bullseye/main amd64 nginx-light
amd64 1.18.0-6.1 [492 kB]
Hämtade 726 kB på 2s (379 kB/s)
Hämtar felrapporter... Klar
Tolkar hittad/tillrättad information... Klar
Förkonfigurerar paket ...
Väljer tidigare ej valt paket nginx-common.
(Läser databasen ... 316586 filer och kataloger installerade.)
Förbereder att packa upp .../nginx-common_1.18.0-6.1_all.deb ...
Packar upp nginx-common (1.18.0-6.1) ...
Väljer tidigare ej valt paket libnginx-mod-http-echo.
Förbereder att packa upp .../libnginx-mod-http-echo_1.18.0-6.1_amd64.deb ...
Packar upp libnginx-mod-http-echo (1.18.0-6.1) ...
Väljer tidigare ej valt paket nginx-light.
Förbereder att packa upp .../nginx-light_1.18.0-6.1_amd64.deb ...
Packar upp nginx-light (1.18.0-6.1) ...
Ställer in nginx-common (1.18.0-6.1) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/nginx.service →
/lib/systemd/system/nginx.service.
Ställer in libnginx-mod-http-echo (1.18.0-6.1) ...
Ställer in nginx-light (1.18.0-6.1) ...
Upgrading binary: nginx.
Hanterar utlösare för man-db (2.9.4-2) ...

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Andrei POPESCU]

On Mi, 29 sep 21, 07:05:37, pe...@easthope.ca wrote:
> From: Greg Wooledge 
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> > 
> > ls -ld / /var /var/log /var/log/journal
> 
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
> drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log

Please include also the output for /var/log/journal (as already 
requested by Greg), and if you have the 'acl' package already installed 
the output of `getfacl` for it.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Kushal Kumaran]

On Wed, Sep 29 2021 at 10:35:35 PM, David Wright  
wrote:
> On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
>> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
>> > From: Greg Wooledge 
>> > Date: Tue, 28 Sep 2021 13:41:05 -0400
>> > > What does it look like?
>> > > 
>> > > ls -ld / /var /var/log /var/log/journal
>> > 
>> > root@joule:/# ls -ld / /var /var/log
>> > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
>> > drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
>> > drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log
>> 
>> The ownership of the / directory is wrong.  It should be root:root,
>> not peter:peter.
>> 
>> chown root:root /
>> 
>> Everything else looks OK at the moment.
>
> Similar to https://lists.debian.org/debian-user/2021/07/msg00907.html
> but even worse (there, it was only group ownership that was wrong).
> It does appear that there's a subset of people who immediately
> recognise this warning message as meaning "wrong ownership",
> Greg (possibly), Kushal and of course Poettering:
>

FWIW, that email was the first I'd ever heard of the problem.  My
solution was based on a web search, which probably led me to the
following link, but I neglected to include that in my email.

> https://github.com/systemd/systemd/issues/11282
>
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.

According to the code at
https://github.com/systemd/systemd/blob/dd4c15296cce001287d03a6647a751f253de2a51/src/basic/fs-util.c#L736,
the message has been updated three months ago to include ownership of
the offending directories.  At this point, we'd need to wait for a newer
version of systemd to migrate into debian repos.

>
> Is this being done by people, say, untarring archives as root, or
> are there some buggy programs out there? One person claimed it
> happened through formatting a partition with some gnome program.
> Is that likely?
>
> Cheers,
> David.

Re: apt automatically upgrading packages in unstable

[piorunz]

On 01/10/2021 15:43, Andrew M.A. Cater wrote:


Probably to reconfigure the unattended-upgrades functionality in apt

dpkg-reconfigure unattended-upgrades

should do it.


IMO unattended-upgrades should be uninstalled in Sid. No reason to auto
update. Everything should be checked by hand.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: apt automatically upgrading packages in unstable

[Andrew M.A. Cater]

On Fri, Oct 01, 2021 at 02:36:37PM +0200, Miguel A. Vallejo wrote:
> A few days ago I noticed my debian unstable started to update packages
> automatically. A quick inspection showed apt was updated, and also the
> configuration files in /etc/apt/apt.conf.d, including a
> 20auto-upgrades file with all options enabled.
> 
> Because auto update in sid is at least dangerous, what is the right
> way to keep apt configuration between apt updates?
> 
> Thank you
> 

Probably to reconfigure the unattended-upgrades functionality in apt

dpkg-reconfigure unattended-upgrades

should do it.

All best

apt automatically upgrading packages in unstable

[Miguel A. Vallejo]

A few days ago I noticed my debian unstable started to update packages
automatically. A quick inspection showed apt was updated, and also the
configuration files in /etc/apt/apt.conf.d, including a
20auto-upgrades file with all options enabled.

Because auto update in sid is at least dangerous, what is the right
way to keep apt configuration between apt updates?

Thank you

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Greg Wooledge]

On Wed, Sep 29, 2021 at 10:35:35PM -0500, David Wright wrote:
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.

That would be a good question to ask the systemd developers.

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Nils]

>From my experience gnome-disks automatically chowns / to the executing user 
>when creating a filesystem.
But I don't think Peter did that.
I'd rather say it's been caused by some installation script, those are usually 
buggy when it comes to file ownership.
Peter, did you install anything via a .run or .sh file?

Nils

On Wed, 29 Sep 2021 22:35:35 -0500
David Wright  wrote:

> On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
> > On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> > > From: Greg Wooledge 
> > > Date: Tue, 28 Sep 2021 13:41:05 -0400
> > > > What does it look like?
> > > > 
> > > > ls -ld / /var /var/log /var/log/journal
> > > 
> > > root@joule:/# ls -ld / /var /var/log
> > > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> > > drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
> > > drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log
> > 
> > The ownership of the / directory is wrong.  It should be root:root,
> > not peter:peter.
> > 
> > chown root:root /
> > 
> > Everything else looks OK at the moment.
> 
> Similar to https://lists.debian.org/debian-user/2021/07/msg00907.html
> but even worse (there, it was only group ownership that was wrong).
> It does appear that there's a subset of people who immediately
> recognise this warning message as meaning "wrong ownership",
> Greg (possibly), Kushal and of course Poettering:
> 
> https://github.com/systemd/systemd/issues/11282
> 
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.
> 
> Is this being done by people, say, untarring archives as root, or
> are there some buggy programs out there? One person claimed it
> happened through formatting a partition with some gnome program.
> Is that likely?
> 
> Cheers,
> David.
> 


-- 
Nils 


pgptXrJud4m_W.pgp
Description: PGP signature

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[David Wright]

On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> > From: Greg Wooledge 
> > Date: Tue, 28 Sep 2021 13:41:05 -0400
> > > What does it look like?
> > > 
> > > ls -ld / /var /var/log /var/log/journal
> > 
> > root@joule:/# ls -ld / /var /var/log
> > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> > drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
> > drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log
> 
> The ownership of the / directory is wrong.  It should be root:root,
> not peter:peter.
> 
> chown root:root /
> 
> Everything else looks OK at the moment.

Similar to https://lists.debian.org/debian-user/2021/07/msg00907.html
but even worse (there, it was only group ownership that was wrong).
It does appear that there's a subset of people who immediately
recognise this warning message as meaning "wrong ownership",
Greg (possibly), Kushal and of course Poettering:

https://github.com/systemd/systemd/issues/11282

Would it be sensible for the message to actually mention ownership,
or can it apply to very different circumstances (beyond permissions,
that is)? I've failed to find any other cause, but see a lot of
people messing up their ownership.

Is this being done by people, say, untarring archives as root, or
are there some buggy programs out there? One person claimed it
happened through formatting a partition with some gnome program.
Is that likely?

Cheers,
David.

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Charles Curley]

On Wed, 29 Sep 2021 08:01:00 -0700
pe...@easthope.ca wrote:

> root@joule:~# cat /etc/apt/sources.list
> #deb http://mirror.it.ubc.ca/debian/ bullseye main
> deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> 
> deb http://ftp.ca.debian.org/debian/ bullseye main contrib
> non-free deb-src http://ftp.ca.debian.org/debian/ bullseye main
> contrib non-free
> 
> deb http://deb.debian.org/debian-security/ bullseye-security main
> contrib non-fr ee
> deb-src http://deb.debian.org/debian-security/ bullseye-security main
> contrib no n-free
> 
> Has anyone installed or upgraded to bullseye on a 32 bit PC?

Yes, several times.

Looking at your sources.list, you can probably remove either the ubc
stanza or the ca.debian.org stanza. I suspect that lags between mirrors
could cause referential integrity issues.

However, it may be simpler to use deb.debian.org, which will assign a
mirror, reducing your reliance on any one mirror. Mine look like so:

root@freeman:~# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux 11.0.0 _Bullseye_ - Official i386 NETINST 
20210814-10:03]/ bullseye main

#deb cdrom:[Debian GNU/Linux 11.0.0 _Bullseye_ - Official i386 NETINST 
20210814-10:03]/ bullseye main

deb http://deb.debian.org/debian bullseye main contrib non-free
# deb-src http://deb.debian.org/debian bullseye main contrib non-free

deb http://security.debian.org/debian-security bullseye-security main
# deb-src http://security.debian.org/debian-security bullseye-security main

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

root@freeman:~# 


-- 
Does anybody read signatures any more?

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

[Greg Wooledge]

On Wed, Sep 29, 2021 at 02:35:10PM -0700, pe...@easthope.ca wrote:
> I can't explain why / was owned by me.  According to the above it 
> happened in the release upgrade two days ago.

No, that's not what that timestamp says.  The timestamp in "ls -ld"
is the modification time (mtime) on the directory, not the change time
(ctime).

The mtime on a directory changes when you create something (a new file
or subdirectory or whatever) inside it, or delete something from it,
or rename something in it.  It doesn't update on chown or chmod.
That would be ctime.

So, we don't know when the ownership changed.  It's probably not something
that can easily be tracked down at this point.  Either you remember
the reason, or you don't.

I'm happy that it's fixed now.

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

[peter]

From: Nils 
Date: Tue, 28 Sep 2021 17:16:30 +
> Are you sure you still need these journals? 

I don't know.

> ... my way to work around it would be to just delete those logs.

Did that and rebooted.  System behaviour unchanged.

APPARENT SOLUTION

root@joule:/home/peter# ls -ld / /var /etc /usr /var/lib /var/log
drwxr-xr-x  18 peter peter  4096 Sep 27 18:00 /
drwxr-xr-x 132 root  root  12288 Sep 29 09:34 /etc
drwxr-xr-x  14 root  root   4096 Nov 11  2020 /usr
drwxr-xr-x  11 root  root   4096 Nov  3  2020 /var
drwxr-xr-x  50 root  root   4096 Sep 27 19:28 /var/lib
drwxr-xr-x  10 root  root   4096 Sep 29 14:09 /var/log

root@joule:/home/peter# chown root:root /

Then the upgrade completes with no errors.

I can't explain why / was owned by me.  According to the above it 
happened in the release upgrade two days ago.

Apologies for the disturbance.

Regards,... P.

-- 
48.7693 N 123.3053 W
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Greg Wooledge]

On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge 
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> > 
> > ls -ld / /var /var/log /var/log/journal
> 
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
> drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log

The ownership of the / directory is wrong.  It should be root:root,
not peter:peter.

chown root:root /

Everything else looks OK at the moment.

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[peter]

From: Nils 
Date: Tue, 28 Sep 2021 17:16:30 +
> Are you sure you still need these journals? 

I don't know.

> ... my way to work around it would be to just delete those logs.

Did that and rebooted.  System behaviour is unchanged.

plymouth-label was the last package reported unconfigured.  So ...

root@joule:~# apt-get --reinstall install plymouth-label
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for plymouth-label:i386

The i386 archive is defective?  The sources.list here doesn't rely on 
one site.

root@joule:~# cat /etc/apt/sources.list
#deb http://mirror.it.ubc.ca/debian/ bullseye main
deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free

deb http://ftp.ca.debian.org/debian/ bullseye main contrib non-free
deb-src http://ftp.ca.debian.org/debian/ bullseye main contrib non-free

deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-fr
ee
deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib no
n-free

Has anyone installed or upgraded to bullseye on a 32 bit PC?

Thx,   ... P.

-- 
48.7693 N 123.3053 W
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[peter]

From: Greg Wooledge 
Date: Tue, 28 Sep 2021 13:41:05 -0400
> What does it look like?
> 
> ls -ld / /var /var/log /var/log/journal

root@joule:/# ls -ld / /var /var/log
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 11 root  root  4096 Nov  3  2020 /var
drwxr-xr-x 10 root  root  4096 Sep 29 06:39 /var/log

root@joule:/# ls -lR /var/log/journal
/var/log/journal:
total 4
drwxr-xr-x 2 root root 4096 Sep 29 06:46 82516769d28444b49bf2553c1a9d8b27

/var/log/journal/82516769d28444b49bf2553c1a9d8b27:
total 32776
-rw-r-  1 root root 25165824 Sep 29 06:49 system.journal
-rw-r-+ 1 root root  8388608 Sep 29 06:54 user-1000.journal

The two files contain binary data.  Any chance they are file system 
journals?  

Thx,... P.



-- 
48.7693 N 123.3053 W
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Greg Wooledge]

On Tue, Sep 28, 2021 at 06:33:52PM +, Andrew M.A. Cater wrote:
> On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> > Errors were encountered while processing:
> >  systemd
> >  libpam-systemd:i386
> >  policykit-1
> >  policykit-1-gnome
> >  plymouth
> >  mate-polkit:i386
> >  lxpolkit
> >  modemmanager
> >  plymouth-label
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > root@joule:~# 

> If this appears to be complete apart from the errors you have: it may be 
> worth rebooting and running dpkg -C to configure anything that is unpacked
> but remains unconfigured.

This would not be my advice.  For two reasons:

1) If the underlying problem isn't fixed, there is no reason to expect
   that "dpkg -C" is going to fix things.  It should just run the same
   post-inst scripts again, and produce the same errors again.

2) With systemd in a possibly messed-up state, rebooting is risky.

I would focus on fixing the underlying issue, starting with looking at
the things that it complained about.

ls -ld / /var /var/log /var/log/journal

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Andrew M.A. Cater]

On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the 
> following transcript.
> 
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
> 
> /var/log/journal exists here.
> 
> The command "systemd-tmpfiles --create --prefix /var/log/journal" gives 
> complaints similar to those in the transcript.
> 
> Likely the solution is obvious once the problem is understood. What is 
> unsafe about the path transition?  How is systemd journaling meant to 
> work?
> 
> Thx,... P.
> 
> ===
> root@joule:~# apt update
> Hit:1 https://mirror.it.ubc.ca/debian bullseye InRelease
> Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> All packages are up to date.
> root@joule:~# apt upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 9 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] 
> Setting up systemd (247.3-6) ...
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> dpkg: error processing package systemd (--configure):
>  installed systemd package post-installation script subprocess returned error 
> exit status 73
> dpkg: dependency problems prevent configuration of libpam-systemd:i386:
>  libpam-systemd:i386 depends on systemd (= 247.3-6); however:
>   Package systemd is not configured yet.
> 
> dpkg: error processing package libpam-systemd:i386 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of policykit-1:
>  policykit-1 depends on default-logind | logind; however:
>   Package default-logind is not installed.
>   Package libpam-systemd:i386 which provides default-logind is not configured 
> yet.
>   Package logind is not installed.
>   Package libpam-systemd:i386 which provides logind is not configured yet.
> 
> dpkg: error processing package policykit-1 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of policykit-1-gnome:
>  policykit-1-gnome depends on policykit-1; however:
>   Package policykit-1 is not configured yet.
> 
> dpkg: error processing package policykit-1-gnome (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of plymouth:
>  plymouth depends on systemd (>= 232-8~); however:
>   Package systemd is not configured yet.
> 
> dpkg: error processing package plymouth (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of mate-polkit:i386:
>  mate-polkit:i386 depends on policykit-1; however:
>   Package policykit-1 is not configured yet.
> 
> dpkg: error processing package mate-polkit:i386 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of lxpolkit:
>  lxpolkit depends on policykit-1; however:
>   Package policykit-1 is not configured yet.
> 
> dpkg: error processing package lxpolkit (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of modemmanager:
>  modemmanager depends on policykit-1; however:
>   Package policykit-1 is not configured yet.
> 
> dpkg: error processing package modemmanager (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of plymouth-label:
>  plymouth-label depends on plymouth (= 0.9.5-3); however:
>   Package plymouth is not configured yet.
> 
> dpkg: error processing package plymouth-label (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  systemd
>  libpam-systemd:i386
>  policykit-1
>  

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

[Greg Wooledge]

On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the 
> following transcript.
> 
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
> 
> /var/log/journal exists here.

What does it look like?

ls -ld / /var /var/log /var/log/journal

> The command "systemd-tmpfiles --create --prefix /var/log/journal" gives 
> complaints similar to those in the transcript.
> 
> Likely the solution is obvious once the problem is understood. What is 
> unsafe about the path transition?  How is systemd journaling meant to 
> work?

> Setting up systemd (247.3-6) ...
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> Detected unsafe path transition / -> /var during canonicalization of 
> /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> dpkg: error processing package systemd (--configure):
>  installed systemd package post-installation script subprocess returned error 
> exit status 73

 suggests an ownership
misconfiguration could be responsible.  Thus, seeing the output of the ls
command may help.