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

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

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

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

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

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

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

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

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

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

grub-pc error when upgrading from buster to bullseye

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.

Re: Issues after upgrading 11 -> 12

grade, 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

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

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

Re: Issues after upgrading 11 -> 12

ily 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

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

e 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, no

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

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 diffe

Re: Problem with php after upgrading to Bookworm

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 >

Re: Problem with php after upgrading to Bookworm

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

Re: Problem with php after upgrading to Bookworm

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

Re: Problem with php after upgrading to Bookworm

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

Re: Problem with php after upgrading to Bookworm

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

Problem with php after upgrading to Bookworm

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

Re: USB2 not working after upgrading to bookworm

ntains 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 "

Re: USB2 not working after upgrading to bookworm

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 machi

USB2 not working after upgrading to bookworm

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

Re: a couple of problems after upgrading to bookworm

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

Re: a couple of problems after upgrading to bookworm

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

a couple of problems after upgrading to bookworm

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

Re: Printer not working after upgrading

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

Re: Printer not working after upgrading

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 faile

Re: Printer not working after upgrading

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 faile

Re: Printer not working after upgrading

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

Re: Printer not working after upgrading

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

Re: Printer not working after upgrading

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 t

Re: Printer not working after upgrading

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

Re: Printer not working after upgrading

> 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

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, p

Re: installing & upgrading backport package & upgrading system

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

Re: installing & upgrading backport package & upgrading system

ng 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

installing & upgrading backport package & upgrading system

p; 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-upg

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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.

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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,

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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

Re: linux headers and upgrading nvidia driver

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

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

Re: ooops upgrading buster -> bullseye

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 ar

Re: ooops upgrading buster -> bullseye

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. >

ooops upgrading buster -> bullseye

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-co

Re: debian app on UserLAnd: upgrading to bullseye

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

Re: debian app on UserLAnd: upgrading to bullseye

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

Re: debian app on UserLAnd: upgrading to bullseye

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: > *

Re: debian app on UserLAnd: upgrading to bullseye

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: > *

debian app on UserLAnd: upgrading to bullseye

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:

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

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

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

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

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

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

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

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

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. > >

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

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

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

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

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

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

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

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: &g

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

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,

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

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

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

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

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

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"

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

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. > > > >

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

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

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

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

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

* 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

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

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 corre

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

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

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

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

Re: Problems upgrading from Debian 10 to 11

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

Re: Problems upgrading from Debian 10 to 11

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, > >

Re: Problems upgrading from Debian 10 to 11

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

Re: Problems upgrading from Debian 10 to 11

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: > &

Re: Problems upgrading from Debian 10 to 11

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

Re: Problems upgrading from Debian 10 to 11

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?

Problems upgrading from Debian 10 to 11

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

Re: apt automatically upgrading packages in unstable

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

Re: Upgrading binary: nginx

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

Upgrading binary: nginx

) ... Upgrading binary: nginx. Hanterar utlösare för man-db (2.9.4-2) ...

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

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 / >

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

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?

Re: apt automatically upgrading packages in unstable

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. --

Re: apt automatically upgrading packages in unstable

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

apt automatically upgrading packages in unstable

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,

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

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

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

>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

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

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 > > > >

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

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

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

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

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

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

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

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

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

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

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

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

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

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 >

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

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 > >

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

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 > >

  1   2   3   4   5   6   7   8   9   10   >