Re: Kernel not upgrading in all systems

On 2025-02-27 15:59, Gary Dale wrote: On 2025-02-14 22:00, Michael Stone wrote: On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return o

Re: Kernel not upgrading in all systems

> > > On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: > > > > All 3 systems have the linux-image-amd64 metapackage installed. On Sat 15 Mar 2025 at 10:44:40 (-0400), Gary Dale wrote: > After today's upgrades, I note that RM1 showed these autoremove > messages "Removing linux-headers-6.1

Re: Kernel not upgrading in all systems

On 2025-02-14 22:00, Michael Stone wrote: On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return on each system? If you apt update on ea

Re: Kernel not upgrading in all systems

On 14/02/2025 21:49, Gary Dale wrote: On 2025-02-09 11:46, Max Nikulin wrote: I recommend to compare     apt policy linux-image-amd64 and     apt policy I can't see any differences between them on the various systems. If it is true and the latest kernel is installed on all systems then you

Re: Kernel not upgrading in all systems

On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return on each system? If you apt update on each system, are there any error messages?

Re: Kernel not upgrading in all systems

On 2025-02-09 11:46, Max Nikulin wrote: On 09/02/2025 00:05, Gary Dale wrote: VM1: /etc/apt/sources.list I recommend to compare     apt policy linux-image-amd64 and     apt policy I can't see any differences between them on the various systems.

Re: Kernel not upgrading in all systems

On 2025-02-09 09:01, Greg Wooledge wrote: On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote: On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this mornin

Re: Kernel not upgrading in all systems

On 2025-02-09 06:22, Henrik Ahlgren wrote: On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this morning's update, I noticed that 2 of the 3 systems upgraded the ke

Re: Kernel not upgrading in all systems

On 09/02/2025 00:05, Gary Dale wrote: VM1: /etc/apt/sources.list I recommend to compare apt policy linux-image-amd64 and apt policy

Re: Kernel not upgrading in all systems

Dis you install the package "linux-image-amd64" ? If yes, the it should always update to the newest kernel. (Same for package "linux-headers-amd64") Hans

Re: Kernel not upgrading in all systems

On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote: > On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: > > I have a few systems running Debian/Stable (Bookworm). However the kernel > > version isn't always the same for some reason. After this morning's update, > > I noticed that 2 of

Re: Kernel not upgrading in all systems

On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: >   > I have a few systems running Debian/Stable (Bookworm). However the kernel > version isn't always the same for some reason. After this morning's update, I > noticed that 2 of the 3 systems upgraded the kernel but to different > versions. T

Kernel not upgrading in all systems

I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this morning's update, I noticed that 2 of the 3 systems upgraded the kernel but to different versions. This is shown by running uname -a. The first is a VM. It has be

[SOLVED?] Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

Oct 4, 2024, 19:59 by loca...@tutanota.com: > After upgrading to Firefox v128 from v115, Firefox seems to have stopped > using some mouse cursors as per the active KDE theme (the Oxygen White theme, > in my case). For some reason, instead of showing the white arrow mouse cursor >

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

On Sunday 06 October 2024 05:28:26 am Michael Kjörling wrote: > The only other simultaneous package upgrades in my case are the libgsf > and oath-toolkit security upgrades, which seem unlikely to be relevant > to this. > I just got a notice about libgsf in a security mailing list: https://securi

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

Oct 6, 2024, 09:28 by c9bc136c6...@ewoof.net: > A data point: KeepassXC has been doing the same for me (with the same > mouse cursor theme, no less) for a very long time; I chalked that one > down to it being a Qt application in a GTK environment. > KeepassXC seems to be not affected by the issu

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

On 4 Oct 2024 21:59 +0200, from loca...@tutanota.com (local10): > After upgrading to Firefox v128 from v115, Firefox seems to have > stopped using some mouse cursors as per the active KDE theme (the > Oxygen White theme, in my case). For some reason, instead of showing > the white

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

Oct 5, 2024, 12:06 by loca...@tutanota.com: > Oct 5, 2024, 09:15 by c9bc136c6...@ewoof.net: > >> I can't imagine it's related to your issue, but the current kernel on >> Bookworm is 6.1.0-26 after a security update the other day. DSA 5782-1 >> https://lists.debian.org/debian-security-announce/2024

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

Oct 5, 2024, 09:15 by c9bc136c6...@ewoof.net: > I can't imagine it's related to your issue, but the current kernel on > Bookworm is 6.1.0-26 after a security update the other day. DSA 5782-1 > https://lists.debian.org/debian-security-announce/2024/msg00195.html > via > https://www.debian.org/secur

Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?

On 4 Oct 2024 21:59 +0200, from loca...@tutanota.com (local10): > Operating System: Debian GNU/Linux 12 > KDE Plasma Version: 5.27.5  KDE Frameworks Version: 5.103.0  Qt Version: > 5.15.8 > Kernel Version: 6.1.0-25-amd64 (64-bit) > Graphics Platform: X11 I can't imagine it's related to your issue

Bookworm: Mouse cursor issues after upgrading to FireFox v128?

Hi, After upgrading to Firefox v128 from v115, Firefox seems to have stopped using some mouse cursors as per the active KDE theme (the Oxygen White theme, in my case). For some reason, instead of showing the white arrow mouse cursor as per the theme, FF now shows a black mouse cursor. Used to

Re: Finding a Debian consultancy for help with large-scale platform upgrade (Was Re: Systems upgrading)

Andy Smith wrote: > Just as some free advice though… > > 1. I find it hard to believe you have more than 2000 Debian installs >without some sort of existing automation / configuration >management > > 2. Given (1), I would approach the task by learning your config >management and modi

Re: Finding a Debian consultancy for help with large-scale platform upgrade (Was Re: Systems upgrading)

And yes we just experienced a p0 accident which affected 100 millions end users. (There is maybe already the news on internet.) So we are taking serious consideration on hiring a consultant for our system upgrading. Thank you. On 2024-08-20 23:49, Andy Smith wrote: Hi Wesley, On Tue, Aug

Finding a Debian consultancy for help with large-scale platform upgrade (Was Re: Systems upgrading)

Hi Wesley, On Tue, Aug 20, 2024 at 11:29:26PM +0800, Wesley wrote: > We have 2000+ dedi servers planning to upgrade from debian 11 to Debian 12. I should think that the typical debian-user subscriber manages only a small number of systems with all of them for personal/hobby use, with the rest of

Systems upgrading

Hello We have 2000+ dedi servers planning to upgrade from debian 11 to Debian 12. The main tech stacks on them are apache, mysql, redis, resin/tomcat, ceph and some hdfs nodes. We are looking for a consultancy for the implementation. If there is any who have the interest, please contact me

Re: Upgrading systemd may silently break your Unstable/Sid system!

On Sun 28 Jul 2024 at 09:45:44 (-0500), allan wrote: > I've run Sid exclusively for years; the last time I broke it badly > enough to justify a reinstall was in 2013 and that was for not paying > attention during an upgrade :) > > My heartburn is I would have expected to see this change in a > ch

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

On Mon 29 Jul 2024 at 09:23:16 (+0700), Max Nikulin wrote: > On 28/07/2024 20:08, Erwan David wrote: > > I also have a 99-systcl.conf which is a copy of the former /etc/sysctl.conf > > When you are going to replace a file provided by a package, check if > it is a configuration file at first (e.g.

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

On 28/07/2024 20:08, Erwan David wrote: I also have a 99-systcl.conf which is a copy of the former /etc/sysctl.conf When you are going to replace a file provided by a package, check if it is a configuration file at first (e.g. dpkg -s). Despite most of files in /etc/ are marked as configurati

Re: Upgrading systemd may silently break your Unstable/Sid system!

inux-sysctl-defaults > Bug fixed by upload, closed. > > 2024-07-11: procps (unstable) upload: /etc/sysctl.conf is "removed" > (but not when upgrading) > Closes #1074156 > > 2024-07-12: bug #1076190 filed against package systemd > Installs danglin

Re: Upgrading systemd may silently break your Unstable/Sid system!

l-defaults Bug fixed by upload, closed. 2024-07-11: procps (unstable) upload: /etc/sysctl.conf is "removed" (but not when upgrading) Closes #1074156 2024-07-12: bug #1076190 filed against package systemd Installs dangling symlink /etc/sysctl.d/99-sysctl.conf Bug fixe

Re: Upgrading systemd may silently break your Unstable/Sid system!

On 2024-07-28 14:13:09 +, Michael Kjörling wrote: > And posting on debian-user with a bombastic Subject line which implies > that this is a widespread issue when it really only seems to exist in > Unstable is, quite frankly, in my opinion at best dishonest. No, the breakage was done *on purpos

Re: Upgrading systemd may silently break your Unstable/Sid system!

I've run Sid exclusively for years; the last time I broke it badly enough to justify a reinstall was in 2013 and that was for not paying attention during an upgrade :) My heartburn is I would have expected to see this change in a changelog and apt-listchanges didn't say a word about this. As far

Re: Upgrading systemd may silently break your Unstable/Sid system!

On 2024-07-28 at 10:13, Michael Kjörling wrote: > On 28 Jul 2024 15:08 +0200, from er...@rail.eu.org (Erwan David): >> Le 28/07/2024 à 14:28, allan a écrit : >>> I would agree with you *if* the change had been publicized. >> >> [...] But in my view it is a bug to remove something else than the >>

Re: Upgrading systemd may silently break your Unstable/Sid system!

On 28 Jul 2024 15:08 +0200, from er...@rail.eu.org (Erwan David): > Le 28/07/2024 à 14:28, allan a écrit : >> I would agree with you *if* the change had been publicized. > > [...] But in my view it is a bug to remove something else than > the symlink even with the same name At the risk of repeati

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

Le 28/07/2024 à 14:28, allan a écrit : I would agree with you *if* the change had been publicized. I found the 99-sysctl.conf symlink accidentally. I removed the symlink and moved sysctl.conf to 99-sysctl.conf since the original config was not being read. This turned out to be a lousy idea sin

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

I would agree with you *if* the change had been publicized. I found the 99-sysctl.conf symlink accidentally. I removed the symlink and moved sysctl.conf to 99-sysctl.conf since the original config was not being read. This turned out to be a lousy idea since the symlink was removed with the next

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

On 28 Jul 2024 04:25 +0200, from vinc...@vinc17.net (Vincent Lefevre): >> A conffile is user-managed, so any changes you make to a conffile must >> be respected by the package. It can't just overwrite your changes, or >> restore a conffile if you've deleted it. > > This is rather poor design, bec

Re: Upgrading Buster LTS (10) to Bookworm (current stable) concerns

On Mon, Jun 17, 2024 at 3:38 AM Nick Sal wrote: > > I plan to upgrade a server running Buster to Bookworm. > Server is running: {web,mail} servers, mysql and postregre, docker, ssh, > ldap, ferm (firewall), and few other non-critical services. > > I'd like to appeal to your experience for a coupl

Re: Upgrading Buster LTS (10) to Bookworm (current stable) concerns

On 17 Jun 2024 03:41 +, from specialrou...@proton.me (Nick Sal): > 1) Should I upgrade in two steps from Buster to Bullseye > (oldstable), and then to Bookworm? Or should I go directly from > Buster to Bookworm in one step? > The upgrade will be done by changing sources.list NEVER skip major

Upgrading Buster LTS (10) to Bookworm (current stable) concerns

Hi, I plan to upgrade a server running Buster to Bookworm. Server is running: {web,mail} servers, mysql and postregre, docker, ssh, ldap, ferm (firewall), and few other non-critical services. I'd like to appeal to your experience for a couple concerns: 1) Should I upgrade in two steps from Bus

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 star

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 grub

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

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

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

Re: Issues after upgrading 11 -> 12

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

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

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

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 differen

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

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 ar

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

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

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

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 /lib/firmware/i915/skl

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 ke

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 thos

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 als

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

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 and

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 stu

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 you

Re: installing & upgrading backport package & upgrading system

ed (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 distribu

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 i

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

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 sh

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 D

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

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 tri

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 I

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 ot

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 ful

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

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

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

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 issue

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. > > https://lists.debia

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 https://lists.debian.org/debia

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

  1   2   3   4   5   6   7   8   9   10   >