hplip: hp-check error in line 630 since last update

Hello, someone else has the problem with hp-check since last update? $ hp-check /usr/bin/hp-check:630: SyntaxWarning: invalid escape sequence '\s' lsusb_pat = re.compile("""^Bus\s([0-9a-fA-F]{3,3})\sDevice\s([0-9a-fA-F]{3,3}):\sID\s([0-9a-fA-F]{4,4}):([0-9a-fA-F]{4,4})(.*)""", re.IGNORECASE)

Re: Luks/lvm => migration vers un nouveau disque : grub rescue grub error lvmid/48r3xxxx

a2c544 /etc/crypttab > 202407 UUID=3ca2c544-2104-4e57-9a17-d636921a7b8a none luks,discard > > # update-grub ou update-initramfs -c -u => donne le même resultat au > boot ... grub rescue > "grub error lvmid/48r3 ." not found(c'est le VG UUID de mon > nouveau lvm)

Re: Luks/lvm => migration vers un nouveau disque : grub rescue grub error lvmid/48r3xxxx

j'ai potentiellement répondu un peu trop vitre: ma réponse précédente n'est valable que si tu utilises KVM/Qemu. Et si tu utilises bien KVM/Qemu, tu peux aussi ne pas être radin sur la taille des disques virtuels: sauf si tu spécifies explicitement d'allouer entièrement la taille maximale du

Re: Luks/lvm => migration vers un nouveau disque : grub rescue grub error lvmid/48r3xxxx

Bonjour, j'ai pas lu dans le détail parce que, simplement je me suis posé la question: pourquoi, si c'est possible (et apparemment ça l'est même si je n'ai jamais pratiqué), ne pas agrandir le disque virtuel actuel plutôt qu'en créer un nouveau plus grand? on se retrouve alors ensuite avec

Luks/lvm => migration vers un nouveau disque : grub rescue grub error lvmid/48r3xxxx

ca2c544-2104-4e57-9a17-d636921a7b8a none luks,discard # update-grub ou update-initramfs -c -u => donne le même resultat au boot ... grub rescue "grub error lvmid/48r3 ." not found(c'est le VG UUID de mon nouveau lvm) J'ai tenté un sed dans /boot/grub/grub.cfg /boot/grub/i38

[SUCESS with caution] Re: Corrupt MATE configuration due to OPERATOR ERROR

On 06/17/2024 09:33 AM, Mike Kupfer wrote: Richard Owlett wrote: I created a new, _apparently_ identical, panel. *HOWEVER* it displays something for each item open/active in *ANY* workspace. How do I get back to displaying something for each item open/active in the *CURRENT* workspace?

Re: Corrupt MATE configuration due to OPERATOR ERROR

Richard Owlett wrote: > I created a new, _apparently_ identical, panel. > *HOWEVER* > it displays something for each item open/active in *ANY* workspace. > > How do I get back to displaying something for each item open/active in > the *CURRENT* workspace? This is the "window list" applet that

Re: Corrupt MATE configuration due to OPERATOR ERROR

On Mon, 17 Jun 2024 05:35:17 -0500 Richard Owlett wrote: > ENVIRONMENT: > Running Debian 9.13 with MATE 1.16.3 on DELL LATITUDE E6410 laptop > an external monitor is used via ARandR 0.1.9 > Using SeaMonkey 2.49.4 for browser and email > Yes. Multiple rev's behind. Doing

Corrupt MATE configuration due to OPERATOR ERROR

ENVIRONMENT: Running Debian 9.13 with MATE 1.16.3 on DELL LATITUDE E6410 laptop an external monitor is used via ARandR 0.1.9 Using SeaMonkey 2.49.4 for browser and email Yes. Multiple rev's behind. Doing housekeeping before updating ;} MATE with installation defaults had run fine.

Re: Synaptic Update Error

On Fri, May 24, 2024 at 08:14:16AM -0400, Stephen P. Molnar wrote: > E: Release file for > http://debian.uchicago.edu/debian/dists/bookworm-updates/InRelease is > expired (invalid since 1d 15h 6min 44s). Updates for this repository will > not be applied. Slightly worrisome. > deb

Synaptic Update Error

During a routine update I got the error: E: Release file for http://debian.uchicago.edu/debian/dists/bookworm-updates/InRelease is expired (invalid since 1d 15h 6min 44s). Updates for this repository will not be applied. /etc/apt/sources.lis entries are: # deb cdrom:[Debian GNU/Linux

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Hi, I think that the core problem which led to this also was on GRPCs side. They should not tell users to compile their library but rather point them to install it from their distros' packet manager (https://grpc.io/docs/languages/cpp/quickstart/#install-grpc) if possible. I will try to do the

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Hi, Chung Jonathan wrote: > Yes, I think the local fix is the way to go. I wrote: > > (You forgot to Cc: debian-user@lists.debian.org. > > Consider to send your mail to the list address, too. I too would then > > resend my following reply to the list.) Since my "following reply" is quoted in

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

On Tue, Apr 02, 2024 at 06:34:43PM -0400, Jeffrey Walton wrote: > On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan wrote: > > > > Dear Franco Martelli, dear Thomas Schmitt, > > > > Sorry for the potential duplication. This mail should now also go to the > > list. > > > > I believe I found the

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan wrote: > > Dear Franco Martelli, dear Thomas Schmitt, > > Sorry for the potential duplication. This mail should now also go to the list. > > I believe I found the problem which was on my side. I do have libz.so.1.3, > since I manually compiled grpc

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Thomas Schmitt, Yes, /etc/debian_version reports 12.5. However, as I have the docker sources as external repository those might have introduced an update to zlib. I will try to narrow it down and then open a subsequent bug report - possibly on a clean VM too. The error first occurred as I installed

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Dear Thomas Schmitt, Yes, I think the local fix is the way to go. Probably even getting rid of the source of this, my manual GRPC install and replacing it with libgrpc++-dev. But that’s outside of this issue. Yours, Jonathan Chung Am 02.04.2024 um 23:34 schrieb Thomas Schmitt : Hi, (You

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

. The error first occurred as I installed a docker image. However, pigz --version also gave this error. Thank you for pointing me to the correct directions, Jonathan Chung > Am 02.04.2024 um 21:07 schrieb Franco Martelli : > On 02/04/24 at 10:27, Jonathan Chung wrote: >> Dear sir or madam

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

On 02/04/24 at 10:27, Jonathan Chung wrote: Dear sir or madam, I'm new with Debian bug reporting and thus need some help with that. pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on upstream https://github.com/madler/pigz/issues/111 Installing the version from sid resolves the

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

On Tue, 2 Apr 2024 10:27:33 +0200 Jonathan Chung wrote: > I'm new with Debian bug reporting and thus need some help with that. > pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on > upstream https://github.com/madler/pigz/issues/111 Are you sure this is a bug and not a problem

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Hi, Jonathan Chung wrote: > > pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on > > upstream https://github.com/madler/pigz/issues/111 > > Installing the version from sid resolves the issue which is clearly not > > optimal. I think the fix should be backported. > > Can someone help

Re: How to file a Debian bug report? was: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

On 2 Apr 2024 10:27 +0200, from jch...@student.ethz.ch (Jonathan Chung): > Can someone help me to file a bug report? https://www.debian.org/Bugs/Reporting -- Michael Kjörling  https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”

Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

Dear sir or madam, I'm new with Debian bug reporting and thus need some help with that. pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on upstream https://github.com/madler/pigz/issues/111 Installing the version from sid resolves the issue which is clearly not optimal. I think the

Re: 404 Not Found Error Problem

not encountered this particular problem before. Are you "abnormal.att.net"? Or at least pretending to be that host in your error messages? Or is your web browser going to that host, when you expected it to go to localhost or something? When I went to abnormal.att.net there was an index.html in /va

Re: 404 Not Found Error Problem

icular problem before. Are you "abnormal.att.net"? Or at least pretending to be that host in your error messages? Or is your web browser going to that host, when you expected it to go to localhost or something?

Re: 404 Not Found Error Problem

Am 06.03.2024 schrieb "Stephen P. Molnar" : > The requested URL was not found on this server. > Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80 Check the apache config. What is the Webroot? Is the file you are looking for available in the webroot?

404 Not Found Error Problem

I am running a new installation of Bookworm and have encountered a 404 Not Found error problem with WebMO (https://www.webmo.net): Not Found The requested URL was not found on this server. Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80 I've installed WebMO a number of times

Re: “Secure Connection Failed” Error in Firefox

e site is accessed normally. However, when > > attempting to access this site on the desktop, Debian Firefox-ESR version > > 115.8.0esr (64-bit), the following error occurs: > > > > Secure Connection Failed > > An error occurred during a connection to gontijoonibus.gonti

Re: “Secure Connection Failed” Error in Firefox

op, Debian Firefox-ESR version > 115.8.0esr (64-bit), the following error occurs: > > Secure Connection Failed > An error occurred during a connection to gontijoonibus.gontijo.com.br. > The page you are trying to view cannot be displayed because the authenticity > of the received

Re: “Secure Connection Failed” Error in Firefox

115.8.0esr (64-bit), the following error occurs: > https://www.ssllabs.com/ssltest/analyze.html?d=gontijoonibus.gontijo.com.br shows that there are several IP addresses that could be serving this, but only 206.41.74.19 seems to be responsive. And then it doesn't serve any content. I would sa

Re: “Secure Connection Failed” Error in Firefox

On Sun, 3 Mar 2024 12:26:20 -0300 Marcelo Laia wrote: Hello Marcelo, >website https://gontijoonibus.gontijo.com.br/ on I get the same results as Greg - in several browsers. -- Regards _ "Valid sig separator is {dash}{dash}{space}" / ) "The blindingly obvious is never

Re: “Secure Connection Failed” Error in Firefox

R version > 115.8.0esr (64-bit), the following error occurs: > > > Secure Connection Failed > An error occurred during a connection to gontijoonibus.gontijo.com.br. > The page you are trying to view cannot be displayed because the authenticity > of the received data could not

“Secure Connection Failed” Error in Firefox

Hello Debian users! When accessing the website https://gontijoonibus.gontijo.com.br/ on Firefox Android (on my smartphone), the site is accessed normally. However, when attempting to access this site on the desktop, Debian Firefox-ESR version 115.8.0esr (64-bit), the following error occurs

Re: Error: Failed to start Apache2 service on boot

Stephen P. Molnar wrote: > > > On 03/01/2024 11:08 AM, Markus Schönhaber wrote: > > > > [1] Look at /etc/apache2/mods-enabled/userdir.conf line 11 > > there you should see something like > > [2] "ExecCG" which probably should read "ExecCGI" instead. > > > That was the problem. Many thanks.

Re: Error: Failed to start Apache2 service on boot

On 03/01/2024 11:08 AM, Markus Schönhaber wrote: 01.03.24, 16:36 +0100, Stephen P. Molnar: I am running up to date Bookworm and get the 'Failed to start Apache2 service on boot' error message. I searched Google and found https://forums.debian.net/voew.top9c,php?t=14419s which didn't solve

Re: Error: Failed to start Apache2 service on boot

01.03.24, 16:36 +0100, Stephen P. Molnar: > I am running up to date Bookworm and get the 'Failed to start Apache2 > service on boot' error message. > > I searched Google and found > https://forums.debian.net/voew.top9c,php?t=14419s which didn't solve the > problem. >

Error: Failed to start Apache2 service on boot

I am running up to date Bookworm and get the 'Failed to start Apache2 service on boot' error message. I searched Google and found https://forums.debian.net/voew.top9c,php?t=14419s which didn't solve the problem. I then tried sudo systemctl status apache2.service resulting in: × apache2

timeshift error

Hi all I keep getting the following error when trying to use "timeshift 1". Ive tried reloading the software  but still get the same error. ** (process:4286): CRITICAL**: 12:39:19.897: gee_abstract_collection_get_size: ass ertion 'self != NULL' failed App config saved: /etc

Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"

>> In general, the first thing you should try is running >> sensors-detect again, as root. > > Okay, I did that ('sudo sensors-detect') and answered with the > default value to all questions, after that I did 'sensors -j' > but it displayed the same error. > >>

Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"

Dan Ritter wrote: > In general, the first thing you should try is running > sensors-detect again, as root. Okay, I did that ('sudo sensors-detect') and answered with the default value to all questions, after that I did 'sensors -j' but it displayed the same error. > It is possible

Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"

Emanuel Berg wrote: > sensors(1) and in particular the command 'sensors -j' now > reports > > ERROR: Can't get value of subfeature in0_input: Can't read > ERROR: Can't get value of subfeature in1_input: Can't read > > for the CPU and GPU temperatures. > > This p

'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"

sensors(1) and in particular the command 'sensors -j' now reports ERROR: Can't get value of subfeature in0_input: Can't read ERROR: Can't get value of subfeature in1_input: Can't read for the CPU and GPU temperatures. This previously worked so I don't know why it doesn't all of a sudden

Re: Determining which file is at a given LBA offset; was: HDD error: Current_Pending_Sector

Hi, On Tue, Feb 20, 2024 at 07:53:38PM -0500, Default User wrote: > Note: I occurs to me that another idea would be to simply delete all > files from the "bad" drive, then rsync everything fresh from the "good" > drive back onto the "bad" drive.   You can do it in one step with rsync --delete …

Re: Determining which file is at a given LBA offset; was: HDD error: Current_Pending_Sector

On Tue, 2024-02-20 at 21:36 +, Michael Kjörling wrote: > On 20 Feb 2024 12:51 -0500, from hunguponcont...@gmail.com (Default > User): > > But since the sector already can not be read, How can it be re- > > written > > to a "good" sector? > > Generally, it can't. It will be remapped if

Re: HDD error: Current_Pending_Sector

On Tue, 20 Feb 2024 at 17:51, Default User wrote: > > Hi guys! Hi to all readers, > Now it "works", BUT . . . I ran: > > sudo smartctl --test=long /dev/sdb on it, > > and it reports a Current_Pending_Sector error, at LBA 325904690. [...] > According to

Re: Determining which file is at a given LBA offset; was: HDD error: Current_Pending_Sector

On 20 Feb 2024 12:51 -0500, from hunguponcont...@gmail.com (Default User): > But since the sector already can not be read, How can it be re-written > to a "good" sector? Generally, it can't. It will be remapped if necessary when something else is written to that sector. > If I knew which file

Re: HDD error: Current_Pending_Sector

re-mounted as read only, due to a filesystem error. I used the gnome-disks utility to unmount and then remount it. It was remounted as read-write. Now it "works", BUT . . . I ran: sudo smartctl --test=long /dev/sdb on it, and it reports a Current_Pending_Sector error, at LBA 3259046

HDD error: Current_Pending_Sector

to a filesystem error.   I used the gnome-disks utility to unmount and then remount it. It was remounted as read-write. Now it "works", BUT . . . I ran:  sudo smartctl --test=long /dev/sdb on it,  and it reports a Current_Pending_Sector error, at LBA 325904690. >From sudo smartctl -

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 u

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 w

Re: Debian 12.5 upgrade error

On 12/02/2024 05:45, piorunz wrote: Anyone affected should make sure to upgrade nvidia-kernel-dkms package once new version become available. Sorry, the package in question is nvidia-graphics-drivers, that's the one being fixed. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The

Re: Debian 12.5 upgrade error

On 11/02/2024 12:48, Teemu Likonen wrote: * 2024-02-11 14:13:51+0200, Alexis Grigoriou wrote: I have encountered an error upgrading to 12.5 from 12.4 regarding the nvidia-driver and linux-image 6.1.0.18. The error is: Very likely this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Re: Debian 12.5 upgrade error

On 11/02/2024 12:13, Alexis Grigoriou wrote: I have encountered an error upgrading to 12.5 from 12.4 regarding the nvidia-driver and linux-image 6.1.0.18. The error is: env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.1.0-18- amd64(bad exit status: 2) I get that error twice

Re: Debian 12.5 upgrade error

On Sun, 2024-02-11 at 19:14 +0200, Alexis Grigoriou wrote: > On Sun, 2024-02-11 at 21:37 +0900, Byunghee HWANG (황병희) wrote: > > Hellow Alexis, > > > > > > What command did you type exactly? > > > > In normal cases, i do like this: > > > > > > sudo su - > > apt update > > apt upgrade > > > >

Re: Debian 12.5 upgrade error

On Sun, 2024-02-11 at 21:37 +0900, Byunghee HWANG (황병희) wrote: > Hellow Alexis, > > > What command did you type exactly? > > In normal cases, i do like this: > > > sudo su - > apt update > apt upgrade > > I logged on as root on tty1 /etc/init.d/lightdm stop apt update apt upgrade I always

Re: Debian 12.5 upgrade error

* 2024-02-11 14:13:51+0200, Alexis Grigoriou wrote: > I have encountered an error upgrading to 12.5 from 12.4 regarding the > nvidia-driver and linux-image 6.1.0.18. The error is: Very likely this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063656 Not your fault. -- ///

Re: Debian 12.5 upgrade error

Hellow Alexis, On Sun, 2024-02-11 at 14:13 +0200, Alexis Grigoriou wrote: >  I have encountered an error upgrading to 12.5 from 12.4 regarding > the > nvidia-driver and linux-image 6.1.0.18. The error is: > > env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.1.0-18- > amd64...

Debian 12.5 upgrade error

I have encountered an error upgrading to 12.5 from 12.4 regarding the nvidia-driver and linux-image 6.1.0.18. The error is: env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.1.0-18- amd64(bad exit status: 2) I get that error twice. After the upgrade I get a non-bootable 6.1.0-18

Re: please, help to get the image write done, due to an error. Thank you!

ge Write to get your lates >Debian 12.4.1 XFCE on my USB. Unfortunately after a few try I get always an >error and so I cannot get the job done. I do have a Lenovo X200 which comes >without DVD writer. Ummm. What image exactly are you trying to write, and how? We don't have any images labe

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On Wed, 24 Jan 2024 07:33:59 + Tixy wrote: > On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote: > [...] > > As you've already found out, that's not the latest one, and if I'm not > mistaken is the one that introduce a wifi bug [1], so that could > explain it getting stuck in the

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote: > I went to shut down the machine, and it got stuck trying to shut down > wpa_supplicant and Network Manager. Ten minutes into the shutdown, I > finally pulled the plug. A few reboots and shutdowns later, I decided > to try another kernel. I

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On Wed, 24 Jan 2024 09:25:58 +0700 Max Nikulin wrote: > On 24/01/2024 03:34, Charles Curley wrote: > > So I purged the newer kernel, inux-image-6.1.0-15-amd64 > > The current kernel is linux-image-6.1.0-17-amd64 > > Perhaps you have not restored your sources.list or apt preferences > after

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On 24/01/2024 03:34, Charles Curley wrote: So I purged the newer kernel, inux-image-6.1.0-15-amd64 The current kernel is linux-image-6.1.0-17-amd64 Perhaps you have not restored your sources.list or apt preferences after the accidents with kernel bugs. Check that nothing extra is added and

SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

run chromium, I get: > > charles@jhegaala:~$ chromium & > [2] 33609 > charles@jhegaala:~$ libva error: > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed > > charles@jhegaala:~$ I seem to have solved this problem, entirely by accident. I went to shut down the

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On 19/01/2024 04:08, Charles Curley wrote: charles@jhegaala:~$ chromium chrome://gpu libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed ^C Killed charles@jhegaala:~$ I did a killall -9 in another window to kill it. Does it happen in the case of a new system user and a new

Re: NUT and Eaton UPS produce a lot of error messages

uctuation -- quite possibly an undervoltage so brief that nothing else in the house noticed. > Jan 19 05:17:04 servername nut-monitor[849]: Poll UPS > [Eaton@localhost] failed - Write error: Broken pipe > Jan 19 05:17:04 servername nut-monitor[849]: Communications with UPS > Eaton@lo

Re: Mariadb error

On 19.01.2024 13:46, Gift Rain wrote: Good day, I'm running Debian 11 and getting error "Failed to start MariaDB 10.5.12 database server. Your MySQL database server doesn't start for some reason. Is there anything helpful in the output? $ sudo journalctl --no-pager -x -

Mariadb error

Good day, I'm running Debian 11 and getting error "Failed to start MariaDB 10.5.12 database server. My emails are not working. Another error on my logs is : "warning:proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf lookup error for" Please help, Gift

NUT and Eaton UPS produce a lot of error messages

and then post the errors of nut-monitor and nut server. I hope someone can help fix the underlying problem behind these error messages. lsusb shows the UPS: Bus 001 Device 003: ID 0463: MGE UPS Systems UPS So I made this changes to ups.conf [Eaton] driver = usbhid-ups port = auto vendorid = 0463

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

is too old for it, so i965 loaded next. I am unsure if it is possible to suppress attempt to load iHD and so to avoid an error message e.g. by setting some environment variable. I see nothing in chromium's rather minimal man page. I also tried several command line switches in https://peter.sh/experiment

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

graphics card is too old for it, > so i965 loaded next. I am unsure if it is possible to suppress > attempt to load iHD and so to avoid an error message e.g. by setting > some environment variable. I see nothing in chromium's rather minimal man page. I also tried several command line switche

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

On 14/01/2024 00:19, Charles Curley wrote: charles@jhegaala:~$ chromium & [2] 33609 charles@jhegaala:~$ libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed charles@jhegaala:~$ vainfo libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu

Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

aala:~$ libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed charles@jhegaala:~$ ps PID TTY TIME CMD 32502 pts/800:00:00 bash 32506 pts/800:00:04 emacs 33609 pts/800:00:00 chromium 33630 pts/800:00:00 chromium 33631 pts/800:00:00 chromium 3

Re: ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100)

On Jan 12, 2024, Vincent Lefevre wrote: > In one of my new machines, I have a DVD+/-RW drive. There were > no issues on January 8 and 9. But today, I'm getting > > ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100) > > errors at boot time. > [...] > > Any idea?

ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100)

In one of my new machines, I have a DVD+/-RW drive. There were no issues on January 8 and 9. But today, I'm getting ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100) errors at boot time. Excerpts of the journal concerning ata6: journalctl-9:Jan 08 11:23:19 disset kernel: ata6: SATA max

Re: Perl module installation via CPAN and signature error

With strace, I could see the command that was executed: gpg --verify --batch --no-tty -q --logger-fd=1 --keyserver=hkp://pool.sks-keyservers.net:11371 on a temporary file, but almost equivalent to the CHECKSUMS file. Now, I can try that directly: qaa:~> gpg --verify --batch --no-tty -q

Perl module installation via CPAN and signature error

VAC/CHECKSUMS ok Checksum for /home/vinc17/.cpan/sources/authors/id/C/CA/CAVAC/XML-RPC-2.tar.gz ok Package came without SIGNATURE CPAN: YAML loaded ok (v1.31) [...] CAVAC/XML-RPC-2.tar.gz /bin/make install -- OK But on the other one (an older machine), I get an error: zira:~> cpan -i XML::RP

Re: cups error -- SOLVED

On Mon, Dec 25, 2023 at 09:36:44PM -0500, Stefan Monnier wrote: I copied the file to another computer in the LAN, ran LaTeX and dvips, and sent it to the same printer, but the file hung at the same spot. Any chance you can use `pdflatex` instead of `latex + dvips`? Have you tried to manually

Re: cups error

On Mon, Dec 25, 2023 at 09:36:44PM -0500, Stefan Monnier wrote: I copied the file to another computer in the LAN, ran LaTeX and dvips, and sent it to the same printer, but the file hung at the same spot. Any chance you can use `pdflatex` instead of `latex + dvips`? Have you tried to manually

Re: cups error

> I copied the file to another computer in the LAN, ran LaTeX and dvips, > and sent it to the same printer, but the file hung at the same spot. Any chance you can use `pdflatex` instead of `latex + dvips`? Have you tried to manually convert the PS to PDF before sending to the printer? or to

cups error

On a desktop debian 12.2 amd64 system with HP_LaserJet_P3010_Series_48E436 (ethernet), LaTeX documents composed with Emacs frequently print only up to a certain point (it varies with the document), and CUPS prints the error message: ERROR: typecheck OFFENDING COMMAND: known xdvi displays

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 14:04:08 -0500, Greg Wooledge wrote: > On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > > I have the latest version!!! I recall that this is a Debian/unstable > > machine, which I upgrade regularly. So, everytime I get such an error, > > I h

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. Just for the record, saying you have the "l

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. > > Note also that this is an error that occurs randomly. Then I'm sorry, that I can'

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

x.x port 22 > > This sounds most likely that your SSH client (program at your local > machine) has an outdated SSH implementation. Try to update this > program first. I have the latest version!!! I recall that this is a Debian/unstable machine, which I upgrade regularly. So, everytime

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > errors like > > kex_exchange_identification: read: Connection reset by peer > Connection reset by x.x.x.x port 22 This sounds most likely that your SSH client (program at your local machine) has an

openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Since 2 years (from early 2022 to 2023-11-26), I've got recurrent errors like kex_exchange_identification: read: Connection reset by peer Connection reset by x.x.x.x port 22 or kex_exchange_identification: Connection closed by remote host Connection closed by x.x.x.x port 22 But yesterday, the

Re: broadcast error messages, unofficial Debian 12

r > query appears to be user support, which takes place on debian-user. > I've set Reply-To: debian-user. > > On Wed, Dec 13, 2023 at 02:52:11PM -0500, Alan Corey wrote: > > I can have 2 or more Zutty terminal windows running to work on a > > program. When I get a compil

Re: EIO error - I/O error

that service. _That said,_ > Please, we are using Debian GNU/Linux 9.13 (stretch) installed on a > UC-8112-LX controller version 3.4, I am not familiar with the UC-8112-LX controller. Also note that Debian 9 receives very limited updates by now, being on ELTS since mid-2022. > and

Re: EIO error - I/O error

s, we notice this error. Can you connect the serial port to a computer and rund minicom to see the tty? Does that work?

Re: EIO error - I/O error

Am 11.12.2023 um 15:46:03 Uhr schrieb Rachid Oubelk: > Please, we are using Debian GNU/Linux 9.13 (stretch) installed on a > UC-8112-LX controller version 3.4, and it shows the error EIO ( IO > error ). Where does that error message appear? In which application?

EIO error - I/O error

Dear support team, Please, we are using Debian GNU/Linux 9.13 (stretch) installed on a UC-8112-LX controller version 3.4, and it shows the error EIO ( IO error ). Could you please help us understand the cause of this error? Very urgent. Best regards, <https://elum-energy.com/> Rachid

Re: Fastly error: unknown domain: 199.232.150.132 : Fastly is cdn for Debian.

is repository > will not be applied. > E: Release file for > http://deb.devuan.org/merged/dists/daedalus-backports/InRelease is not > valid yet (invalid for another 8744d 7h 58min 11s). Updates for this > repository will not be applied. > Your real time clock isn't :( Set th

Re: Fastly error: unknown domain: 199.232.150.132 : Fastly is cdn for Debian.

Am 10.12.2023 um 14:38:34 Uhr schrieb Mario Marietto: > http://deb.devuan.org/merged/dists/daedalus-updates/InRelease is not > valid yet (invalid for another 8744d 7h 58min 21s). Updates for this > repository will not be applied. Is your date correct on your machine?

Fastly error: unknown domain: 199.232.150.132 : Fastly is cdn for Debian.

for this repository will not be applied. E: Release file for http://deb.devuan.org/merged/dists/daedalus-backports/InRelease is not valid yet (invalid for another 8744d 7h 58min 11s). Updates for this repository will not be applied. After a little experimenting it looks like to me that it is a Fastly error

firewalld runttime to permanen error

I've just installed Debian 12 on a new machine. I'm setting up the firewall with firewalld. I have two interfaces (and lo). I'd like to change the zone of one of them from "trusted" to "home". I can do that in the runtime, but when I go to make that change permanent, I get a

  1   2   3   4   5   6   7   8   9   10   >