Re: I need help with my var partition.
On 4/28/23 17:25, Maureen L Thomas wrote: I am 72 and have forgotten a few things. I looked up debian/var and was told I could delete /var/log/ and /var/tmp/ and /var/cores/. I left cores alone and deleted the other two. Now I cannot burn a backup, download files and even go to web sites from my nord vpn which was working great until I deleted the above files. I really want to upgrade to debian 11. I am using debian 10, on a Lonovo all in one and have had no problems. I followed the directions for var that I found and now have a screwed up machine. Is there any help available. I was thinking of upgrading online but don't want to loose my data. Please help this old lady. On 4/28/23 17:57, Maureen L Thomas wrote: > OK so I went looking on the net /debian/var to find out why it is > running out of room. All I could find is the directions to delete said > files. I will put them back, now. On 4/28/23 19:05, Maureen L Thomas wrote: > ... I still cannot burn a back up disk. On 4/28/23 19:36, Maureen L Thomas wrote: > Here is what I got. > > root@debian:/var# /bin/ls -ld */ > drwxr-xr-x 2 root root 4096 Apr 28 15:46 backups/ > drwxr-xr-x 19 root root 4096 Apr 12 20:20 cache/ > drwxr-xr-x 2 root root 4096 Apr 28 20:59 cores/ > drwxr-xr-x 2 root root 4096 Nov 13 2020 games/ > drwxr-xr-x 62 root root 4096 Apr 12 20:20 lib/ > drwxrwsr-x 2 root staff 4096 Sep 19 2020 local/ > drwxrwxrwt 3 root root100 Apr 28 21:13 lock/ > drwxr-xr-x 8 root root 4096 Apr 28 21:36 log/ > drwx-- 2 root root 16384 Nov 12 2020 lost+found/ > drwxrwsr-x 2 root mail 4096 Nov 12 2020 mail/ > drwxr-xr-x 2 root root 4096 Nov 12 2020 opt/ > drwxr-xr-x 27 root root760 Apr 28 22:31 run/ > drwxr-xr-x 14 root root 4096 Apr 27 22:58 snap/ > drwxr-xr-x 7 root root 4096 Nov 12 2020 spool/ > drwxr-xr-x 8 root root 4096 Apr 28 22:32 tmp/ > root@debian:/var# I assume you have a Lenovo computer. What is the model name and number? What processor? How much memory? How many drives, what type, and what size? What backup software are you using? Do you have recent backups? Do you know how to restore? What other resources do you have available -- computers, network, USB flash drives, external HDD's, spare SSD/HDD's? When I break an OS instance, or when I want to re-install or do a major version upgrade, I back up the system configuration files and data files, remove the system disk, install a (zeroed) replacement system disk, do a fresh install, manually merge the old configuration settings into the new configuration files, and restore the data. So long as I do each step correctly, I end up with a correct result. Disaster preparedness and disaster recovery are easier if your OS is on one disk and your data is on another disk. What is your layout? David
Re: Wireshark does not show physical interfaces for capture
Hello On 2023-04-29 17:33, Lee wrote: On 4/29/23, Victor Sudakov wrote: Lee wrote: On 4/29/23, Victor Sudakov wrote: [dd] > > However when I startup wireshark from the GUI, it does not show the > physical interfaces in the list of interfaces to capture from, so I > cannot really capture anything from the non-root user. When started > via sudo, it does show enp3s0 and other interfaces and can capture. > > What am I missing? See if the interfaces have been hidden from the GUI. eg $ grep devices_hide .config/wireshark/preferences capture.devices_hide: any,nflog,nfqueue,dbus-system,dbus-session Nothing much there: $ grep devices_hide .config/wireshark/preferences #capture.devices_hide: Or check from the GUI: Capture / Refresh Interfaces Does not add the NICs to the list. Capture / Options select the Input tab and click Manage Interfaces select the Local Interfaces tab and make sure there's a checkmark under Show for all the physical interface names I don't see any physical interfaces there, this is all I see: https://ibb.co/190ytwv Have you looked at https://www.wireshark.org/faq.html#capprobunix I have a vague memory of having to do sudo dpkg-reconfigure wireshark-common a few years ago before I was able to capture packets without using sudo Good memory, actually. The full steps are $ sudo dpkg-reconfigure wireshark-common # [1] Should non-superusers be able to capture packets => Yes $ sudo usermod -a -G wireshark $USER # [1] $ newgrp wireshark $ groups # The output should now include "wireshark" group name 1. Or execute these commands as root, if sudo is not installed. Regards Lee
Bug após atualização do sistema Debian 11.7
Prezados, Não estou familiarizado ainda com o sitema linux. Mas estava utilizando meu Debian 11 normalmente, mas após a ultima atualização dos pacotes alguma funcionalidades ficaram prejudicas exemplo: alterar brilho da tela não funciona mais. Além disso, o sistema ficou extremamente lento para tarefas simples e e programas ficaram extremamente lentos. Gostaria de saber qual atualização causou isto e como reverter. Obrigado,
Re: Wireshark does not show physical interfaces for capture
On 4/29/23, Victor Sudakov wrote: > Lee wrote: >> On 4/29/23, Victor Sudakov wrote: > > [dd] > >> > >> > However when I startup wireshark from the GUI, it does not show the >> > physical interfaces in the list of interfaces to capture from, so I >> > cannot really capture anything from the non-root user. When started >> > via sudo, it does show enp3s0 and other interfaces and can capture. >> > >> > What am I missing? >> >> See if the interfaces have been hidden from the GUI. eg >> $ grep devices_hide .config/wireshark/preferences >> capture.devices_hide: any,nflog,nfqueue,dbus-system,dbus-session > > Nothing much there: > > $ grep devices_hide .config/wireshark/preferences > #capture.devices_hide: > >> >> Or check from the GUI: >> Capture / Refresh Interfaces > > Does not add the NICs to the list. > >> Capture / Options >> select the Input tab and click Manage Interfaces >> select the Local Interfaces tab and make sure there's a checkmark >> under Show for all the physical interface names > > I don't see any physical interfaces there, this is all I see: > https://ibb.co/190ytwv Have you looked at https://www.wireshark.org/faq.html#capprobunix I have a vague memory of having to do sudo dpkg-reconfigure wireshark-common a few years ago before I was able to capture packets without using sudo Regards Lee
Re: sudo and echo
On 29.04.2023 02:52, cor...@free.fr wrote: Hello list, When I run this command: $ sudo echo 123 > /root/123.txt A better use is to do: echo 123 | sudo tee /root/123.txt or sudo tee /root/123.txt <
Re: Wireshark does not show physical interfaces for capture
Victor Sudakov wrote: > > I don't see any physical interfaces there, this is all I see: > https://ibb.co/190ytwv Sorry I forgot to mention that dumpcap sees the NICs, but the Wireshark GUI does not: $ whoami ; dumpcap -D vas 1. enp3s0 2. any 3. lo (Loopback) 4. bluetooth-monitor 5. nflog 6. nfqueue 7. dbus-system 8. dbus-session $ -- Victor Sudakov VAS4-RIPE http://vas.tomsk.ru/ 2:5005/49@fidonet signature.asc Description: PGP signature
Re: Wireshark does not show physical interfaces for capture
Lee wrote: > On 4/29/23, Victor Sudakov wrote: [dd] > > > > However when I startup wireshark from the GUI, it does not show the > > physical interfaces in the list of interfaces to capture from, so I > > cannot really capture anything from the non-root user. When started > > via sudo, it does show enp3s0 and other interfaces and can capture. > > > > What am I missing? > > See if the interfaces have been hidden from the GUI. eg > $ grep devices_hide .config/wireshark/preferences > capture.devices_hide: any,nflog,nfqueue,dbus-system,dbus-session Nothing much there: $ grep devices_hide .config/wireshark/preferences #capture.devices_hide: > > Or check from the GUI: > Capture / Refresh Interfaces Does not add the NICs to the list. > Capture / Options > select the Input tab and click Manage Interfaces > select the Local Interfaces tab and make sure there's a checkmark > under Show for all the physical interface names I don't see any physical interfaces there, this is all I see: https://ibb.co/190ytwv -- Victor Sudakov VAS4-RIPE http://vas.tomsk.ru/ 2:5005/49@fidonet signature.asc Description: PGP signature
Re: Re: (Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Hello everyone, I partly solved my problem and I would like to share my solution: Until now, I thought that the EFI removable media path (\EFI\BOOT\BOOTX64.EFI) is really a fallback location, i.e. a location for putting the boot loader that just always works. Therefore I thought that I could forget about EFI variables altogether if I just put the boot loader there. My recipes don't bind-mount /sys/firmware/efi/efivars for that reason. And when trying things out with the emulator, this assumption holds true, i.e. running "qemu-system-x86_64 -accel kvm -bios /usr/share/ovmf/OVMF.fd ..." will create a virtual machine that behaves like I expected. However, my Asus UX31A does things differently and insists on EFI variables being used for the internal drive, i.e. it doesn't look at the fallback location (\EFI\BOOT\BOOTX64.EFI) of the internal drive. That's the solution for the EFI boot interface, use EFI variables. For the BIOS boot interface, I'm still clueless why it doesn't work. However, I'll leave it at that. Thanks to everyone who helped! Kind regards, Valentin Caracalla
Re: Wireshark does not show physical interfaces for capture
On 4/29/23, Victor Sudakov wrote: > Dear Colleages, > > My user is a member of the "wireshark" group and can start /usr/bin/dumpcap > all right: > > $ ls -al /usr/bin/dumpcap > -rwxr-xr-- 1 root wireshark 129696 мар 4 2022 /usr/bin/dumpcap > > $ id > uid=1000(vas) gid=1000(vas) > группы=1000(vas),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),30(dip),44(video),46(plugdev),121(lpadmin),136(lxd),137(sambashare),138(wireshark),1002(admin) > > $ /usr/bin/dumpcap > Capturing on 'enp3s0' > File: /tmp/wireshark_enp3s0Y3LW31.pcapng > Packets captured: 126 > Packets received/dropped on interface 'enp3s0': 126/0 > (pcap:0/dumpcap:0/flushed:0/ps_ifdrop:0) (100.0%) > $ > > However when I startup wireshark from the GUI, it does not show the > physical interfaces in the list of interfaces to capture from, so I > cannot really capture anything from the non-root user. When started > via sudo, it does show enp3s0 and other interfaces and can capture. > > What am I missing? See if the interfaces have been hidden from the GUI. eg $ grep devices_hide .config/wireshark/preferences capture.devices_hide: any,nflog,nfqueue,dbus-system,dbus-session Or check from the GUI: Capture / Refresh Interfaces Capture / Options select the Input tab and click Manage Interfaces select the Local Interfaces tab and make sure there's a checkmark under Show for all the physical interface names Regards, Lee
Re: Proper use of checkrestart
On Sat, 29 Apr 2023 05:38:05 -0400 Jeffrey Walton wrote: > I have a script that fully updates a machine each night around 4:00 > AM. It also reboots the machine as required. You might look at the unattended-upgrades package, which does exactly this. (Except for the 4:00 AM, but you can adjust that.) -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: I need help with my var partition.
On Fri 28 Apr 2023 at 22:36:39 (-0400), Maureen L Thomas wrote: > Here is what I got. > > root@debian:/var# /bin/ls -ld */ > drwxr-xr-x 2 root root 4096 Apr 28 15:46 backups/ > drwxr-xr-x 19 root root 4096 Apr 12 20:20 cache/ > drwxr-xr-x 2 root root 4096 Apr 28 20:59 cores/ > drwxr-xr-x 2 root root 4096 Nov 13 2020 games/ > drwxr-xr-x 62 root root 4096 Apr 12 20:20 lib/ > drwxrwsr-x 2 root staff 4096 Sep 19 2020 local/ > drwxrwxrwt 3 root root 100 Apr 28 21:13 lock/ > drwxr-xr-x 8 root root 4096 Apr 28 21:36 log/ > drwx-- 2 root root 16384 Nov 12 2020 lost+found/ > drwxrwsr-x 2 root mail 4096 Nov 12 2020 mail/ > drwxr-xr-x 2 root root 4096 Nov 12 2020 opt/ > drwxr-xr-x 27 root root 760 Apr 28 22:31 run/ > drwxr-xr-x 14 root root 4096 Apr 27 22:58 snap/ > drwxr-xr-x 7 root root 4096 Nov 12 2020 spool/ > drwxr-xr-x 8 root root 4096 Apr 28 22:32 tmp/ > root@debian:/var# You've effectively got no /tmp available for most users. drwxrwxrwt 6 root root 4096 Apr 28 21:02 tmp/ On Sat 29 Apr 2023 at 07:12:13 (+0200), to...@tuxteam.de wrote: > On Fri, Apr 28, 2023 at 10:05:01PM -0400, Maureen L Thomas wrote: > > Yes my figures are very similar to yours. But even after a reboot I still > > cannot burn a back up disk. > > One problem may be that /var/log has subdirectories which don't > belong to root. Applications trying to write their logs might > fail, either because they can't create "their" log subdirectory > or because they even don't try (because they rely on the install > process having done that). > > Here's an example, but note that your package set will differ > from mine, so take this as illustrative: Can I also add to your listing (as a systemd-user): drwxr-sr-x+ 3 root systemd-journal 4096 Jan 1 2022 /var/log/journal $ getfacl -p /var/log/journal/ # file: /var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x group:adm:r-x mask::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x $ Cheers, David.
Unsubscription instructions (WAS Re: AW: why symbolic link arnt visible?)
On Sat, Apr 29, 2023 at 01:17:33PM +0200, Maurizio Caloro wrote: > Hello All > > Meny meny Thanks again for everyone who has written to me here. > > please where do I go so I can unsubscribe here > > gently > Maurizio > Hello Maurizio, The instructions to subscribe/unsubscribe are on every email. Mail to debian-user-requ...@lists.debian.org with a subject of unsubscribe OR Go to the mailing lists web page at https://lists.debian.org/ and follow the web form prompts. With every good wish, as ever, Andy Cater
Re: sha256sum --text generating blank spaces and hyphens?
Max Nikulin (12023-04-29): > > incorrect > This word was stripped in the following quote as well. I was being charitable in not pointing the logical contradiction that if it intentional then it is not incorrect, at least for somebody. > Writing the cited phrase I had in mind an attack which target You can send your movie-plot attacks to Bruce Schneier's next competition; as for me, I will not answer further. -- Nicolas George signature.asc Description: PGP signature
Re: sha256sum --text generating blank spaces and hyphens?
On 28/04/2023 23:42, Max Nikulin wrote:
incorrect
This word was stripped in the following quote as well.
On 29/04/2023 15:50, Nicolas George wrote:
Max Nikulin (12023-04-28):
value may be intentionally specified
I am stripping your mail to just these few words, because they are the
core flaw of your argument.
If your prefer to ignore other arguments, I am leaving it up to you.
Source of Content-Type HTTP header values may be a simple file suffix
map like
types {
text/html html;
image/gif gif;
image/jpeg jpg;
}
http://nginx.org/en/docs/http/ngx_http_core_module.html#types
If something has been done intentionally, overriding it with an
heuristic is a very bad practice.
Writing the cited phrase I had in mind an attack which target is to pass
an innocently looking file name to specific application usually used for
another purpose.
As for invalid values that are mistakenly specified, they are a
minority, and basing your entire design on a minority of mistakes is
also not a very good practice.
I consider it is important to notify user that something might go wrong
and perhaps inconsistent data have been received. Even if it is a rare
case, it should help to perform an appropriate action, to correct a
mistake, to minimize damage.
Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver
On Fri, Apr 14, 2023 at 5:16 PM Schwibinger Michael wrote: > > Good afternoon. > The new printer is not working. > EPSON is saying > You cant use EPSON with Linux. > > Is this true? Plonk!
AW: AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver
Good afternoon Is somebody here familiar with printing emails using DEBIAN? Regards Sophie Thank You for help. Von: Andrew M.A. Cater Gesendet: Dienstag, 25. April 2023 20:28 An: Schwibinger Michael Betreff: Re: AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver On Tue, Apr 25, 2023 at 10:08:27AM +, Schwibinger Michael wrote: > Good afternoon > > Is the problem the printer or Sophie? > The problem is people not being patient and not being helpful. Somewhere in the list of messages, there is one from me asking people to be helpful - I see you have copied it below.. I'm guessing Sophie is a young person and is working in English which for her is a second language. I'm also guessing that she is doing this because she wants to learn for herself. There is a Debian user mailing list in the German language if this would be more helpful. The lists of messages often all have the same subject even if the question changes. That's fine but can be confusing at times. My latest message was asking a series of questions so that we can perhaps narrow down the problem. > > Can DEBIAN itself find a printerdriver? > It should be possible to find a printer driver or to find something to work on Settings to find something for you. Thank you for contacting me. With every good wish / Mit besten Gruesse Andy Cater > > Regards > Sophie > > > > Von: Andrew M.A. Cater > Gesendet: Samstag, 15. April 2023 10:04 > An: debian-user@lists.debian.org > Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are using > the wrong driver > > On Sat, Apr 15, 2023 at 07:17:23AM +0800, Bret Busby wrote: > > Why not just everyone attack each other? > > > > This looks like an uncontrolled pillow fight. > > > > .. > > Bret Busby > > Armadale > > West Australia > > (UTC+0800) > > .. > > > > Agreed: in this instance, however, we've had a series of emails from this > person in the past. Most of them don't reset a subject so go on a long time > on various subjects in the same thread. > > That said: people - please remember that this list is subject to the Code > of Conduct. Part of that involves being constructive and helpful: sniping > doesn't really help at all. > > We are all human and can get annoyed when someone just doesn't *get it* > but it's useful to remember that email is hard because you can't see > the circumstances of the person on the other end. That's also one of > the reasons why these threads keep asking for technical details / accuracy: > whenever these sorts of questions get asked, we're using guesswork because > we can't see over your shoulder. > > With every good wish, as ever, > > Andy Cater > [amaca...@debian.org] > >
AW: why symbolic link arnt visible?
Hello All We've been talking about the broth for sooo long now, I almost don't remember what the initial request was. But joking aside, I would like to thank you very much for the advertising that I have received again. I found the solution myself yesterday, like almost all the other questions I had asked for individually in this forum. Unfortunately, such "small" inquiries are simply discussed deeply and for a long time and philosophized heavily, unfortunately I didn't have that much time for this small inquiry. Meny meny Thanks again for everyone who has written to me here. please where do I go so I can unsubscribe here gently Maurizio -Ursprüngliche Nachricht- Von: to...@tuxteam.de Gesendet: Samstag, 29. April 2023 06:52 An: debian-user@lists.debian.org Betreff: Re: why symbolic link arnt visible? On Fri, Apr 28, 2023 at 04:09:12PM -0400, Greg Wooledge wrote: > On Fri, Apr 28, 2023 at 08:20:37PM +0200, to...@tuxteam.de wrote: > > On Fri, Apr 28, 2023 at 01:28:11PM -0400, Greg Wooledge wrote: > > > On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote: > > > > f: /var/lib/rancid/routers/configs > > > > drwxr-xr-x root root / > > > > drwxr-xr-x root root var > > > > drwxr-xr-x root root lib > > > > drwxr-xr-x rancid rancid rancid > > > > drwxr-x--- rancid rancid routers > > > > drwxr-x--- rancid rancid configs > > > > > > The last two directories are missing world +x permission. This > > > means the web server process can't touch them -- can't enter them, > > > can't open files within them, etc. > > > > [...] > > > > I guess they need read permission too? > > Only if the web server process needs to generate a directory listing. > If it knows the file name in advance, read permission isn't needed -- > just execute. That's right. "Experimentally" confirmed :) I always had this (obviously mislead) notion that the web server checks read permission along the whole path to read-access a file. At least lighttpd doesn't (but I gues this kind of convention will be common to all servers). > > And the file itself, c3560, also needs read permissions. > > We don't know that, yet :) > > Yes, assuming the intent is to deliver the file's content, it'll need > read permission on the file itself. So, Maurizio -- to finish this riddle: what does "ls -l c3560" say? C'mon, the suspense is hard to bear ;-) Cheers -- t
Proper use of checkrestart
Hi Everyone, I have a script that fully updates a machine each night around 4:00 AM. It also reboots the machine as required. I noticed Debian has checkrestart. The man page is at https://manpages.debian.org/bullseye/debian-goodies/checkrestart.8.en.html. I want to ensure I understand "Exit Status" correctly: Normally, the program will exit with error (1) if a non-root user tries to run it. Otherwise, it will always exit with error status 0. If the --terse switch is given, the exit code is 1 when there are deleted open files and 0 when there are none. This is intended for consumption by Nagios and similar automated monitoring tools. I think the script should use --terse, as in: if command -v checkrestart >/dev/null 2>&1; then if ! checkrestart --terse >/dev/null 2>&1; then needs_reboot=1 fi fi I think using an option like --terse is unusual to get an exit code that can be used in a script. I want to ensure it is correct. My question is, is that usage correct? Thanks in advance.
Re: sha256sum --text generating blank spaces and hyphens?
Max Nikulin (12023-04-28): > value may be intentionally specified I am stripping your mail to just these few words, because they are the core flaw of your argument. If something has been done intentionally, overriding it with an heuristic is a very bad practice. As for invalid values that are mistakenly specified, they are a minority, and basing your entire design on a minority of mistakes is also not a very good practice. -- Nicolas George signature.asc Description: PGP signature
Re: Unable to print PDF file with evince on Debian 12.
On 29/4/23 14:50, Serkan KURT wrote: Hi friends. When I tried to print a PDF document, I got the message "Print job canceled at printer". I was able to print the same document to file with a PDF printer. I was able to print the original document with "Okular" and "LibreOffice Draw" with physical printer. I created a very simple document with "LibreOffice Writer" and saved it as a PDF. I could not print this document either. I can print "Printer test page" with HP printer. How can I solve this problem? FWIY I also have problems printing PDF with evince. It's just some documents and the symptom is the printer lights up and then goes back to sleep and the job is stalled. I can always print the document by some other route so I haven't explored further. -- Jeremy (Lists)
Re: I need help with my var partition.
Hi, Maureen L Thomas wrote: > even after a reboot I still cannot burn a back up disk. In case the crisis lasts longer or you need to make a backup before its solution: What program do you use to burn your backups and what does it report when failing ? What kind of media shall be burnt ? Have a nice day :) Thomas
Re: bind9 and dns forward
Le 28 avril 2023 Bonno Bloksma a écrit : > We use a different dns server(s) and zonefile for the external dns > environment from what we use internally. Company dns is Windows server 2016 > incase that is relevant. It's better to use dig (package bind9-dnsutils) to first eliminate problems on other DNS. Give us: dig @13.107.206.240 trafficmanager.net SOA dig @13.107.206.240 outlook.ha.office365.com IN dig @172.16.128.40 vijl.staf.tio.nl dig @172.16.128.10 vijl.staf.tio.nl > Apr 28 12:07:53 linbobo named[546]: DNS format error from 172.16.128.40#53 > resolving staf.tio.nl/ for client 172.16.17.11#65033: Name tio.nl (SOA) > not subdomain of zone staf.tio.nl -- invalid response I suppose you reboot after your upgrade ? Do you have defined somewhere on linbobo a zone staf.tio.nl ? I guess not but do a grep just to be sure.
Wireshark does not show physical interfaces for capture
Dear Colleages, My user is a member of the "wireshark" group and can start /usr/bin/dumpcap all right: $ ls -al /usr/bin/dumpcap -rwxr-xr-- 1 root wireshark 129696 мар 4 2022 /usr/bin/dumpcap $ id uid=1000(vas) gid=1000(vas) группы=1000(vas),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),30(dip),44(video),46(plugdev),121(lpadmin),136(lxd),137(sambashare),138(wireshark),1002(admin) $ /usr/bin/dumpcap Capturing on 'enp3s0' File: /tmp/wireshark_enp3s0Y3LW31.pcapng Packets captured: 126 Packets received/dropped on interface 'enp3s0': 126/0 (pcap:0/dumpcap:0/flushed:0/ps_ifdrop:0) (100.0%) $ However when I startup wireshark from the GUI, it does not show the physical interfaces in the list of interfaces to capture from, so I cannot really capture anything from the non-root user. When started via sudo, it does show enp3s0 and other interfaces and can capture. What am I missing? -- Victor Sudakov VAS4-RIPE http://vas.tomsk.ru/ 2:5005/49@fidonet signature.asc Description: PGP signature
Re: W: Possible missing firmware /lib/firmware/brand/yada*
On 2023-04-28 21:30 -0400, Felix Miata wrote: > # inxi -Gxx > Graphics: > Device-1: Intel 82Q963/Q965 Integrated Graphics vendor: Dell driver: i915 > v: kernel arch: Gen-4 ports: active: DVI-D-1 empty: VGA-1 bus-ID: 00:02.0 > chip-ID: 8086:2992# aka ancient > # grep MODULES /etc/initramfs-tools/initramfs.conf > # MODULES: [ most | netboot | dep | list ] > MODULES=dep > # > > These many per transaction $SUBJECT initrd construction messages have been > routine > for a long time in Bullseye and Bookworm regardless of active GPU installed, > and > whether or not a firmware-brand-graphics .deb exists and is installed > for it. It would be useful to give an example of these messages, as well as a list of firmware packages you have installed. > Is there something that can be done to avoid this screen and log > litter? Install the package that contains the firmware files. For Intel and NVidia graphics that is firmware-misc-nonfree, for AMD it is firmware-amd-graphics. > Can anyone > point to an existing meta-bug report on the subject of stopping the litter? > Searching seems to find only reports pointing to particular GPUs, e.g. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016286 It's the same for any GPUs, as well as for other hardware. The update-initramfs script runs modinfo(8) to find out which firmware files a loaded module might request and issues a warning for any such file which is not there. You can check the code for yourself[1]. Cheers, Sven 1. https://sources.debian.org/src/initramfs-tools/0.142/hook-functions/#L109
Evince ile PDF dosyaları yazdıramıyorum.
Merhaba arkadaşlar. Debian 12'de evince ile PDF dosyaları yazdıramıyorum. Fakat aynı dosyayı Okular ile yazdırabiliyorum. LibreOffice Writer ile oluşturduğum PDF'i de evince ile yazdıramıyorum. Printer test page'i yazdırılıyor.LibreOffice ile belgeler yazdırılabiliyor. Şurada bir hata kaydı girdim fakat cevap yok henüz.https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030626 Çözüm önerisi var mıdır?
Unable to print PDF file with evince on Debian 12.
Hi friends.When I tried to print a PDF document, I got the message "Print job canceled at printer". I was able to print the same document to file with a PDF printer. I was able to print the original document with "Okular" and "LibreOffice Draw" with physical printer. I created a very simple document with "LibreOffice Writer" and saved it as a PDF. I could not print this document either. I can print "Printer test page" with HP printer.How can I solve this problem? Gnome DesktopDebian 12
