6[00:03:07] <dpkg> If you have a question, just ask! For example: "I have a problem with ___; I'm running Debian version ___. When I try to do ___ I get the following output ___. I expected it to do ___." Don't ask if you can ask, if anyone uses it, or pick one person to ask. We're all volunteers; make it easy for us to help you. If you don't get an answer try a few hours later or on debian-user@lists.debian.org. See <smart questions><errors>.
7[00:03:17] <dka> I broke my Debian os. I did apt autoremove because it was advised and it have removed the Linux kernel 5.2 while I use 5.7
8[00:03:41] <dka> For some reason now I syst start in emergency mode and.i don't have internet
127[00:44:26] <LiquidAcid> invalid magic number usually indicates a corrupted file (iirc it's a message from the bootloader)
128[00:44:32] <dka> And how can i do without it?
129[00:44:40] <dka> I don't have USB on my s9
130[00:45:21] <wrksx> I'd try to fix the UUID in /proc/cmdline
131[00:45:23] <LiquidAcid> well, you should use a different/new usb key anyway
132[00:45:34] <dka> I dont have one its Saturday evening
133[00:45:44] <dka> I have another one but there is no debian on it
134[00:45:51] *** Quits: rgr (~rgr@replaced-ip) (Remote host closed the connection)
135[00:45:57] <dka> I cant transfer from.my phone to my laptop anyway
136[00:46:11] <LiquidAcid> well, i'm just saying that using a corrupted usb key to recover your system is probably going to break more than it's going to fix
137[00:46:16] <dka> I am a bit fucked am I?
138[00:46:34] <dka> I have what I have. In the middle of nowhere
142[00:47:02] <dka> I can wait Monday and buy a new laptop to fix this one
143[00:47:35] <LiquidAcid> dka, that's a bit... radical
144[00:48:03] <wrksx> a working bootable stick with a live system could probably help too
145[00:48:11] *** Guest94007 is now known as S3xyL1nux
146[00:48:14] <wrksx> and cheaper
147[00:48:53] <dka> I am in prague
148[00:49:02] <dka> Not sur where can I get those. First time gère
149[00:49:34] <dka> I know I must have my work weekly meeting on Wednesday and work to finish. So I need a way fast to boot this think or get a new one
150[00:49:39] <dka> I didnt expected that today.
151[00:50:00] <LiquidAcid> dka, you could probably try to provide the rootfs directly
152[00:50:05] <dka> Lenovo center is near door and the laptop is under warranty but not sure if they can warranty on Linux or fix it soon
153[00:50:14] <dka> How do i do that ?
154[00:50:25] <LiquidAcid> can you access the bootloader? i assume it's grub2
155[00:50:34] <dka> I can
156[00:50:38] <dka> How ?
157[00:50:44] <LiquidAcid> grub should let you edit the boot commandline
158[00:50:47] <dka> When it boot I have 3 choices
159[00:50:59] <dka> Ok but is it gonna break more ?
160[00:51:07] <LiquidAcid> i think if you select an entry and press e it goes into edit mode
161[00:51:18] <dka> That's the only way ? Teach me
162[00:51:23] <LiquidAcid> edits are volatile, i don't think you even save them to disk
222[01:12:21] <n4dir> what i do in such cases is a) create a different user and test if he has the same problem b) stop the display-manager from autostart during boot via systemctl and install a window-manager to start that one with startx
255[01:22:35] <nifker> Why cant I select btrfs in gparted?
256[01:22:56] <another> did you install btrfs-progs?
257[01:26:12] <nifker> ah ok
258[01:26:18] <nifker> thank you
259[01:31:10] <nifker> Im trying to add a disk to fstab like this: "UUID=ac08836f-f9b5-4218-b06a-7a976fe708a7 /data btrfs errors=remount-ro 0 3"
260[01:31:34] <nifker> but I get this "mount: /data: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error." when I exec mount -a
261[01:31:48] <nifker> but mount /dev/sda1 /data works fine
262[01:33:51] <another> blkid /dev/sda1
263[01:34:02] <another> does the uuid match?
264[01:35:44] <another> btw: you might want to specify how to handle atime
265[01:36:09] <dka> I lost my sound
266[01:36:13] <dka> it seems pulseaudio is not running
271[01:36:53] *** Quits: lle-bout (~lle-bout@replaced-ip) (Remote host closed the connection)
272[01:36:55] <dka> I can connect to a bluetooth speaker and play the sound there, but I must keep the terminal open after typing `pulseaudio`, how can I do ?
437[04:57:25] <dpkg> If you have a question, just ask! For example: "I have a problem with ___; I'm running Debian version ___. When I try to do ___ I get the following output ___. I expected it to do ___." Don't ask if you can ask, if anyone uses it, or pick one person to ask. We're all volunteers; make it easy for us to help you. If you don't get an answer try a few hours later or on debian-user@lists.debian.org. See <smart questions><errors>.
438[04:58:02] <another> I have a problem with btrfs; Debian buster; can't mount
439[04:58:09] <another> mount: /srv: wrong fs type, bad option, bad superblock on /dev/vdc, missing codepage or helper program, or other error.
458[05:22:07] <themill> how do you suppose that you'd not have it
459[05:22:28] <somiaj> Until recentally debian offically supported systemd and sysvinit, so many packages provide both systemd unit files and sysv init.d files.
466[05:23:53] <JordiGH> themill: I figure that if I'm using systemd, I don't need scripts to start/stop services, that systemd units would do the whole work.
467[05:23:59] <JordiGH> So why do I have init.d?
468[05:24:13] <sney> aiui, debian tries to distribute software as is from upstream, as much as possible. so if upstream includes a sysv-style init script, it goes into the package unless there's a good reason not to
469[05:24:42] <JordiGH> Okay, so it's a vestigial appendix.
470[05:24:58] <ryouma> it's a good policy :)
471[05:24:58] <sney> it's more like a second kidney
472[05:24:59] <JordiGH> We had this script, you're not using, but we'll stick it in /etc/init.d anyway.
474[05:25:48] <ryouma> the biggest bug debian ever had was produced because a package was changed i think
475[05:26:02] <JordiGH> The OpenSSL bug.
476[05:26:06] <ryouma> yes
477[05:26:21] <sney> the wonderful thing about debian is it's not made for only one use case. so maybe you're not using an init.d script but someone else might be, for whatever reason. you're both supported. hooray!
478[05:26:38] <JordiGH> Okay, just wanted to make sure I really don't need it.
479[05:26:52] <themill> JordiGH: you're not using selinux either, but you have those libraries installed so that others can use selinux. same for ldap etc etc
480[05:26:56] <JordiGH> systemd units for Debian packages aren't written to refer to init.d scripts, are they?
481[05:27:11] <themill> some are
482[05:27:22] <somiaj> and debian packages don't install files based on which init system (or other configuration choice) you make. And the disk space lost by having /etc/init.d/ files in packages is so little.
483[05:27:23] <JordiGH> Oh no.
484[05:27:28] <themill> (but generally not as that's a crap way of doing it)
485[05:27:35] <sney> you should be able to tell pretty easily by looking at the unit file
486[05:27:52] <JordiGH> sney: That's a lot of unit files to look through.. let's grep.
487[05:28:11] <another> 132K /etc/init.d/
488[05:28:32] <JordiGH> Yes, it's small, but so was my appendix.
489[05:28:38] *** Quits: EagleTG (~eagletg@replaced-ip) (Remote host closed the connection)
490[05:28:42] * themill wonders what problem JordiGH is trying to solve
491[05:28:51] <JordiGH> not everything is a problem.
492[05:28:56] <JordiGH> Some questions are just questions.
500[05:29:36] <sney> I would say it's a safe assumption that anything in the big tasks / big popcon numbers is working with systemd directly. anything with a duct tape unit that is just a wrapper for a shell script is probably on the fringes with 1 person maintaining it who didn't have time
501[05:30:03] <sney> certainly now that systemd has been the default for a few years
506[05:31:42] <sney> and #debian is typically a support channel, so usually when someone has a "why" question it's related to something practical they're trying to figure out. but if you want a problem, I'm sure one can be devised
514[05:34:38] <themill> In the sense of argued endlessly about the same things and occasionally tried to rip themselves apart because quite minor things were blown out of all proportion?
515[05:35:17] <sney> having more clarity as to the popularity of runner-up positions is nice
516[05:35:50] <themill> some sort of 'preferential' vote is certainly much more sensible than first past the post
518[05:36:56] <sney> also, endless argument with periodic loss of perspective might be an integral part of a functional representative government. but oh, I can see the offtopic weeds from here
519[05:36:56] <JordiGH> themill: But the endless debate makes for such a good show. Sure beats watching C-SPAN. replaced-url
520[05:39:17] <JordiGH> Ooh, runs with no flash now.
567[06:37:24] <redbrass> How do I tell the installer that a) I need the firmware drivers for my wifi card, and b) use the wifi card for installation instead of eth0 (or equivalent)?
569[06:39:04] <lxkraken> Is this your ISO: replaced-url
570[06:39:29] <lxkraken> That ISO includes any non-free drivers you might need.
571[06:40:46] <redbrass> ok. I'll give it a shot. I was using the netinst iso. AND the bullseye testing iso. (I need the newer kernel for my hardware - I'm attempting to fix a black screen issue with xorg...)
572[06:41:31] <redbrass> thanks for the link.. my google searches hadn't found that one yet...
581[06:48:58] <dpkg> Repeat after me: the testing installer is for testing the <installer>, not for installing <testing>. To install testing, do a minimal installation using the <stable> installer and ask me about <stable->testing>. Installer bugs should be filed against the debian-installer pseudopackage. replaced-url
582[06:49:54] <somiaj> redbrass: Tradtionally it is often suggested to install a minimum system with the netinstaller, then dist-upgrade to testing. You can read the install guide for how to supply firmware to the offical 'free' installer, but most just use the unoffical 'non-free' installer with the firmware included for most wifi cards.
583[06:50:03] <somiaj> *install a minimum stable system
584[06:51:58] <alex11> redbrass, for what it's worth backports exist too if you just need a kernel
585[06:55:40] <redbrass> I've tried the usual troubleshooting first, Backports, nvidia commercial drivers, etc. Today I installed Arch Linux (for the first time) and was able to get lightdm and kde running. So I know my hardware *can* work. But most the resources I know offer deb or rpm files, so I'd rather stick with Debian. Unfortunately Debian isn't giving me a useful install easily.
586[06:56:57] <lxkraken> redbrass: Maybe try a more recent version: replaced-url
587[06:57:19] <redbrass> Ausus TUF A15 laptop - Ryzen 7 4800H, with Nvidia GTX 1650. It took a bit but I found out the Nvidia drivers are NOT the issue... it is something about the XOrg config. So I'm trying to install a debian system with a more recent kernel (natively, not via backports) to see if that works better.
588[06:57:20] <somiaj> redbrass: It might just be missing firmware, lots of graphics cards need firmware these days too. Debian DSFG just states that all packages in main must be free, but debian does provide most firmware in its non-free repo
589[06:57:27] <redbrass> I'll give that one a shot too. Thanks.
590[06:59:05] <somiaj> redbrass: you shouldn't need an xorg config, so if you have xorg.conf, that could be your problem. I would just use the text installer and worry about xorg at a future date, so far non of your hardware should need testing (that you have shared)
591[07:00:52] <lxkraken> redbrass: somiaj is right. An xorg config file might be causing you more trouble than you think.
632[08:11:33] <redbrass> Thanks for the help gang. I installed with both of the ISOs linked above. Neither could find my wireless adapter. So I hooked up a 50 foot network cable from the basement and did a wired install. Neither was able to give me a stable system. I'm getting a PPM error that breaks any graphical steps (after a fresh boot)
633[08:12:49] <redbrass> I previously fixed this by installing the Nvidia commercial driver. So I tried that and I can't even get the file to run properly. And there are a bunch of noveux errors dumped to the terminal. Even doing a lspci is hanging the box.
635[08:13:02] <redbrass> running ip addr does not list the wireless device at all.
636[08:14:06] <redbrass> so, I think I am probably better served by moving to a different distro for a few months. (I know I could fix each error individually, but I'm after a low maintenance box, and that effort is contrary to the low maintenance focus...)
637[08:14:38] <redbrass> ironically, I know Arch Linux installs properly. I don't consider Arch Linux low maintenance. :)
638[08:14:57] <redbrass> I appreciate the efforts here though.
639[08:14:58] <diogenes_> redbrass, what unfriendly PC is that? a lenovo?
641[08:15:39] <redbrass> Asus TUF A15, with a Ryzen 7 4800H and Nvidia GTX 1650.
642[08:16:39] <redbrass> The hardware is sweet - the installs are FAST. Getting the install right though.... I feel like I'm back in 2003 installing Gentoo for the first time.. :)
643[08:16:44] <diogenes_> so it's quite new, i'd recommend you to try liquorix and xanmode kernels.
644[08:17:36] <redbrass> diogenes_: That is why I was trying out the Bullseye install tonight... after the newer kernels and hardware support.
645[08:17:57] <somiaj> redbrass: what is your wifi chipset?
646[08:18:51] <somiaj> YOu should be able to use buster just fine with that nvidia card you have, as I said use the text installer, then install the non-free nvidia driver from debian's repos.
647[08:18:59] <diogenes_> redbrass, it's not the same, as a final instance i'd give xanmod a try before going to other distro.
648[08:19:16] <redbrass> realtek 86xx (I'd have to fire up the machine again to get to the specific model)
649[08:19:42] <somiaj> I think my issue was I am out of date on what nvidia card numbers, so it might just need a backport kernel. One second
652[08:19:55] <redbrass> somiaj: I've tried buster. I ran into all these problems there too. I've seen some references to others running Debian on this box, but not problem free initially.
656[08:23:04] <somiaj> hmm, seems nvidia has updated their site so I can't as easly see what cards are supported, the 418.52 only supports the 1660, maybe 1650 was added to the 418.152
658[08:23:48] <somiaj> but the 440.100 from buster-backcports supports that card just fine. As for the wifi card, unless you have more info, it might just be you need the firmware and kernel from backports
661[08:24:37] <redbrass> judd: firmware-realtek is installed on the laptop - still can't see the wireless device.
662[08:24:42] <somiaj> redbrass: anyways, it will take a bit of manual work, but you could get buster to work with that hardare from what I see, but due to needing non-free firmware and non-free drivers, it will take a bit more work than something like arch that will install non-free stuff without making you do extra steps
663[08:24:44] <redbrass> lspci lists it though
664[08:25:05] <somiaj> as I said, it could be you need the firmware from backports, and a kernel from backports
665[08:25:28] <somiaj> So you could get debian stable to work on that machine, but it will take some knowledge of debian and doing things from a text console and wired interface
667[08:27:44] <redbrass> I have that know how.. :) Been using Linux since 2002ish. This isn't new... I'm just getting lazy and prefer low maintenance over a high(er) maintencance system (like Gentoo or such...) And Ubuntu has burned me by retiring repos/versions quickly.
670[08:28:20] <somiaj> redbrass: Well here is the steps I would do. 1) Install a minimum system (don't choose a desktop) using the stable netinstall. Install over a wired interface
671[08:28:30] <somiaj> the installer should ask to enable backports, do that. Also enable non-free
672[08:28:52] <redbrass> This is why I luv IRC though - awesome folks who are willing to offer assistance. :)
673[08:28:58] <Praematura> So three times now in the past 4 days, my Debian system has "frozen" on me and NOTHING is in the logs. Would someone like to tell me what could be happening, or was me choosing Debian for a server/desktop OS a bad choice? Because this keeps happening and it's very frustrating.
674[08:29:08] <somiaj> 2) install the realtek-firmware and linux-image-amd64 from backports (apt install -t buster-backports realtek-firmware linux-image-amd64), and then reboot and get your wifi working
675[08:29:17] <somiaj> 3) install the non-free nvidia driver from backports
676[08:29:22] <somiaj> 4) install the desktop of your choice
677[08:29:31] <klys> praematura, are you running a desktop?
678[08:29:35] <redbrass> Praematura: could be hardware related - I've seen bad memory have that sort of behavior.
679[08:30:13] <somiaj> Praematura: are you running a graphical enviroment (Xorg)? Or is this all console base. If the linux kernel in debian is freezing, it could be hardware (or some bug with the hardware you have).
680[08:30:27] <Praematura> kyls, yes, xfce
681[08:30:30] <somiaj> Praematura: in general debian is a good choice for servers, provided it supports the hardware of the machine.
682[08:30:38] <somiaj> Praematura: do you have an ssh server running?
684[08:30:59] <Praematura> I will note: this was NOT an issue until a few days ago when I lost power.
685[08:31:30] <klys> praematura, I haven't tried xfce myself, though I would advise testing it for a day or two without a desktop (try a windowmanager + compton) and see where that gets you.
687[08:31:45] <somiaj> Praematura: reason I ask, is sometimes xorg will crash, but the system is still running and you can ssh into it. If that is the case, the issue is probably with the gpu. You can also enable presistant logging with systemd that can help (though everything should also be in /var/log/syslog)
688[08:32:14] <somiaj> Praematura: power loss can cause corruption of files, maybe try debsums and see if you have corrupt files
689[08:32:17] <somiaj> !debsums
690[08:32:18] <dpkg> debsums is a utility that will check a package's files against their checksums. The "-a" argument will instruct it to also check configuration files: "apt install debsums; debsums -a -s". Almost all packages come with md5sums included in the package or apt will have generated them for you; generate missing ones with "apt-get install --reinstall `debsums -l`". Ask me about <md5sums>.
691[08:32:27] <Praematura> The thing is, Xorg doesn't crash: the screen just freezes, and everything there stays until the screen goes blank. Network connectivity dies.
692[08:32:44] <diogenes_> Praematura, BTRFS by any chance?
693[08:32:57] <Praematura> Originally I found out is was going into 'suspend' mode and had fixed that, but now something seems to have been reset.
694[08:33:59] <Praematura> [BTRFS] Oh HELL no, I'll never touch that filesystem. ext4 only
695[08:34:33] <Praematura> Up until the power outage, my system had been running without restart for months.
696[08:34:38] <redbrass> When this happens try hitting CTRL-ALT-F1 a couple of times. If that brings up a terminal, try logging in. If you are able too then the graphical system has frozen. If you can't do that then you are truly locked up...
697[08:35:01] <Praematura> redbrass: Thank you, will write that down right now to try.
698[08:35:38] <somiaj> redbrass: graphical system locking up will take the keyboard with it most the time, that is why I suggested ssh.
699[08:35:41] <diogenes_> Praematura, setting editor > xfce4-session > SaveOnExit is it enabled?
700[08:35:41] <redbrass> once at a TTY terminal, you can hit CTRL-F7 to return to the graphical interface
701[08:36:02] <somiaj> If the network is truely going down, it sounds like a kernel lockup. There is the magic sys key you can try
702[08:36:17] <redbrass> somiaj: agreed, but troubleshooting is a series of steps to isolating the specific culprit.
703[08:36:49] <Praematura> The worrying thing is NONE of the logs in /var/log show anything during the freeze. No errors, no warnings, nothing.
705[08:37:55] <somiaj> kernel panics/lockups won't log things, because the lockup happens faster than it can be logged. The main on you should check is /var/log/syslog
706[08:38:14] <somiaj> though I would follow klys suggestion, and disable the desktop (its a server right?) and see if it still locksup
707[08:39:50] <Praematura> Sadly it's both a server AND a desktop, because my partner didn't want me to have two separate systems. But like I said, I've been running buster for months and zero issues until our power outage about a week ago. Now it just keeps "freezing", and I haven't been able to find any sort of kernal errors or anytning else.
708[08:40:12] <somiaj> Praematura: try debsums and see if any packages are corrupt, then reinstall them.
709[08:40:55] <somiaj> Praematura: are you sure that debian hasn't had a kernel update in that time too. Maybe trying to older kernel would help, if it is the case the older kernel works, you have a regression bug.
713[08:41:38] <Praematura> somiaj: I'll give debsums a try. I actually did an 'apt-get upgrade' and the only things updated were my nVidia drivers (probably a good thing) and Firefox.
714[08:42:02] <somiaj> nvidia drivers could cause xorg to crash, though often times ssh/network will still be functional.
721[08:48:01] <Praematura> 'debsums -s' didn't show anything concerning, just a few changed files from the 'aspell-*' packages
722[08:50:58] <somiaj> follow the instructions at the top of /usr/share/doc/systemd/README.Debian to enable presistant logging in systemd. This could make searching through the logs via journalctl after a crash a bit easier, maybe that can help you track down the issue
723[08:52:16] <Praematura> somiaj: The sad thing is: it's never a crash. My system literally freezes, and the only way to get it back is to powercycle.
730[08:55:06] <somiaj> That will still make it so you can access all the systemd logs after a reboot (though they should be in /var/log/syslog, you can then search them with journalctl)
731[08:55:17] <somiaj> It might give you an idea of exactly what was the last thing before the freeze
732[08:57:20] *** Quits: leorat (~leorat@replaced-ip) (Remote host closed the connection)
932[12:43:22] *** Quits: Sierra (~sierrakom@replaced-ip) (Remote host closed the connection)
933[12:44:43] <oxek> does paste.debian.net have a way I can upload a textfile from terminal?
934[12:45:51] <jelly> !pastebinit
935[12:45:51] <dpkg> A command-line tool to send data to a <pastebin>. To paste e.g. your sources.list do "apt-get install pastebinit; pastebinit /etc/apt/sources.list"; to paste the output of a program do e.g. "dmesg 2>&1 | pastebinit". For a list of pastebin sites do "pastebinit -l". See also <pastebinit config>, <nopaste>.
936[12:46:09] <jelly> oxek, pipe or redirect into "pastebinit -b replaced-url
970[13:03:50] <petn-randall> Lope: It'll show up in buster, it's one of the very few exception of things that get feature upgrades in stable. The reasoning behind it is that browsers become less useful with time if they don't support current web standards, and also because security updates get more and more difficult to backport with time.
981[13:12:02] <oxek> tomreyn: that works, but I prefer p.d.n because it's https upload, and because I can delete the entry afterwards
982[13:13:37] <tomreyn> oxek: then you'll need to find a way to solve "some python error"
983[13:14:18] <unborn> oxek: you might write your own pastebin script with little knowledge of php and html, you don't need even need sql.. just couple of text files and host it on your own or solve some python errors right there
1012[13:53:39] <oxek> right now, I'd say chromium is not to be used in debian, and if you really need it, get it from snap
1013[13:53:46] <petn-randall> oxek: Only RC bug on chromium is #967124, which is only about unversioned python dependencies. chromium 84 is aready in experimental.
1015[13:54:39] <petn-randall> It might be delayed due to some transitions, but I'm only going by what tracker.debian.org says.
1016[13:55:32] <oxek> chromium 84 was released 2020-07-14, and the fixes were not backported to 83 by debian. It is highly unusual for a package to remain in debian with known security issues for this long.
1020[13:58:51] <oxek> the version in experimental replaced-url
1021[13:58:58] <oxek> it is just the language packs
1022[13:59:21] <oxek> and it has been like that since August 1st
1023[13:59:39] <oxek> so I'd still say chromium is dead in debain for now
1024[13:59:49] <oxek> until upstream fixes the python issue
1025[13:59:53] <cronolio> hi, how i can use less as pager if alternatives says /bin/less but mare is used as pager when i type ls /bin/<tab> for example
1028[14:01:04] <oxek> cronolio: that's not more being used, that's your shell's internal pager
1029[14:01:23] <petn-randall> cronolio: Do you have $PAGER set?
1030[14:01:29] <cronolio> even set export PAGER=less doesn't help
1031[14:01:42] <cronolio> by default PAGER is not set
1032[14:01:52] <oxek> petn-randall: "source package has 2 unsatisfiable build dependencies" at replaced-url
1033[14:02:41] <cronolio> what the shell internal pager
1034[14:05:34] <petn-randall> oxek: python2-minimal exists on amd64, which is why I'm confused by this info. Might be a transient build error, or it really was like that in the past.
1035[14:06:44] *** Quits: silverwhitefish (~hidden@replaced-ip) (Quit: One for all, all for One (2 Corinthians 5))
1036[14:08:19] *** Quits: Repox (~textual@replaced-ip) (Quit: My MacBook has gone to sleep. ZZZzzz…)
1040[14:09:58] <EdePopede> cronolio: it says "More", not "more". htop only shows me xterm and bash, no pager. seems bash handles it on its own.
1041[14:10:08] <oxek> I don't remember the details, just passing on the info from a month ago, that chromium cannot be built anymore on debian and will remain that way until upstream fixes it's dependency on python2
1042[14:10:20] *** Quits: rgr (~rgr@replaced-ip) (Remote host closed the connection)
1076[14:39:48] <k3tan> hi, the latest version of virtualbox doesn't install properly on debian 10.5 due to a few dependency issues (not being the latest versions). is there a timeframe of when they're likely to be updated? libc6, libqt5, libvpx6 are the packages.
1079[14:42:11] <dpkg> If you don't tell us the exact error messages you get, we can't tell you what's wrong, and it's also useful to know exactly what command you're typing. Please look for the *first* error that occurs, as this is often the cause of later errors -- ask me about <localized errors> too. Please don't paste in the channel, use a pastebin instead; ask me about <pastebin>.
1080[14:42:14] <nkuttler> !bat
1081[14:42:14] <dpkg> [Basic Apt* Troubleshooting]. To diagnose your problem, we need ALL OF THE FOLLOWING information: 1. complete output of your apt-get/apt/aptitude run (including the command used) 2. output from "apt-cache policy pkg1 pkg2..." for ALL packages mentioned ANYWHERE in the problem, and 3. "apt-cache policy". Use replaced-url
1100[14:49:07] <petn-randall> screen resize and HW acceleration also work fine, though I remember a dark past where this wasn't the case.
1101[14:49:50] <nkuttler> i use linux and windows vms with virt-manager, everything works fine except for copy pasting, but i can't say i spent time on getting that to work
1119[14:57:54] <petn-randall> FuzzyByte, blebz, do you have a support question?
1120[14:58:12] <FuzzyByte> I don't.
1121[14:58:22] <FuzzyByte> Sorry or the sudden off-topic
1122[14:58:40] <blebz> Yeh .. Does anyone know where there is a good newbies guide for Debian? Something that shows you how to set up paths and set-up sudo and basic stuff like that?
1123[14:59:01] *** debhelper sets mode: +l 1126
1124[14:59:08] <blebz> Also why does my computer keep going to sleep?
1125[14:59:27] <FuzzyByte> blebz: probably your de, check in the graphical tool of it
1140[15:01:44] <petn-randall> blebz: Regarding your suspend, I'd check the power management settings in your DE. It's likely that it's set to go to sleep when the machine is idle for a while.
1159[15:05:54] <blebz> Yeh I guess I could set-up vnc .. hmmm...
1160[15:08:00] <FuzzyByte> blebz: install tightvncserver on the computer you want to control, and xtightvncviewer on the computer you want to control your other computer from.
1250[16:40:28] <jmcnaught> hassoon: playonlinux seems to be working here, do you have any more information? Tried running it from a terminal to get warnings or errors?
1310[17:36:13] <carlesc> I am currently running socat to listen to a TCP port and redirect a serial port to it whenever a client connects. Can I also execute a script using socat *after* the client connects but *before* the serial port redirection begins?
1568[22:26:10] <bigfluff> Is anybody using Cinnamon on Debian? Looking for a more 'traditional' desktop environment than Gnome, and not in love with KDE's bloat...
1575[22:28:08] <jelly> also, most of KDE's thingies can be switched off
1576[22:28:28] <jelly> I basically use kde and xfce interchangeably with the same featureset
1577[22:28:31] <sney> KDE's bloat is mostly in your head, it has lower memory usage at idle than you'd expect. still not for everyone though. xfce is also popular
1578[22:28:51] <jelly> that indexer thing is not in their head
1579[22:29:08] <jelly> forgot what the name was, disabled it years ago
1580[22:29:17] <beelzebuzz> bigfluff: xfce/mate/cinnamon are the medium sized ones
1581[22:29:17] <jelly> asomething? nepomuk?
1582[22:29:22] <sney> I remember the indexer thing being an issue in kde4 but haven't run afoul of it since... 2016?
1583[22:30:30] <sney> I also disabled it years ago but I've had too many brand new profiles since then for it to still be disabled.
1584[22:30:42] *** Quits: pvdp66556 (~pvdp@replaced-ip) (Remote host closed the connection)
1585[22:31:25] <beelzebuzz> bigfluff: there's also pantheon from elementary os if you want something similar to osx
1586[22:31:32] <oxek> amlchief: don't use chromium in debian, it is no longer supported by debian
1587[22:31:49] <oxek> use some fork of chromium, or upstream chrome
1588[22:31:56] <oxek> (or the snap package)
1589[22:32:18] *** Quits: BenjiProd (~BenjiProd@replaced-ip) (Remote host closed the connection)
1590[22:32:20] <amlchief> oxek, any suggestion for a fork of chromium?
1591[22:32:21] <sney> chromium is still supported, there's just an issue right now with the python dependency
1592[22:32:23] <bigfluff> Is there a way to install Plasma without all of the Kontacts + Konversation etc out-of-box?
1598[22:33:37] <beelzebuzz> bigfluff: plasma desktop is a thing
1599[22:33:46] <sney> bigfluff: sure, there are multiple metapackages and you can always pick and choose components. the 'kde-plasma-desktop' package will get you a pretty minimal starting point
1600[22:33:56] <jelly> if it was unsupported you would be told by the debian-security-support package (provided that's installed)
1601[22:33:57] <amlchief> me too, almost impossible to work, i.e. login to google cloud console or aws and get constant crashes
1616[22:36:20] <sney> the python issue looks like it'll be solved relatively soon with the python2-* compromise packages being kept in bullseye, just need to fix the build-deps in the package and it'll *probably* come down the pipe in a couple weeks (or less if it's considered truly urgent).
1617[22:36:27] *** Quits: Jerrynicki (~niklas@replaced-ip) (Remote host closed the connection)
1634[22:41:36] <oxek> (I'm using that as a very simple issue that I could fix, just to learn how to contribute to debian)
1635[22:41:53] <sney> those docs give the overview of debian's patching approach, then you make the patch and attach it to the appropriate bug report and tag it with 'patch'
1637[22:42:01] <beelzebuzz> bigfluff: depends but probably networkmanager
1638[22:42:11] <sney> #debian-mentors on OFTC is a great resource for learning how to contribute as well
1639[22:42:26] <FuzzyByte> bigfluff: nmtui or nmcli shoudl wirk
1640[22:42:33] <FuzzyByte> should work
1641[22:42:35] <oxek> sney: yeah, I think I'll try to learn how to do that.
1642[22:42:49] <oxek> it's a lot more involved that doing a simple github pull request
1643[22:43:10] <sney> I used to be a package maintainer but I quit because I couldn't keep up with it at that time in my life. I think I'm going to try to get back into it soon as well
1644[22:43:36] <NetTerminalGene> does anyone use samsung evo 860 ssd on buster? how compatible is it? do i need to set up trim?
1645[22:43:45] <yanmaani> oxek: There was a project to run lintian and send in automated patches
1646[22:43:46] <n4dir> if you want to contribute you could also do some work at wiki.debian.org, for example translations. or whatever needs some loving
1647[22:43:50] <yanmaani> debian janitor?
1648[22:44:08] <oxek> I wouldn't want to be a package maintainer for some package, I'd just like to fix some little issues that are relevant to debian packaging that don't come from upstream - such as the lintian-identified issues
1649[22:44:26] <oxek> n4dir: I can't even access the debian wiki :D
1650[22:44:40] <n4dir> ah, right, now i remember. then sorry
1664[22:48:07] <NetTerminalGene> i am wondering if there is a problem that you should upgrade firmware
1665[22:48:15] <oxek> I did not do a firmware upgrade on this ssd, but for a different samsung one I used the samsung enterprise magician (don't remember exact name) which is available for linux
1666[22:48:21] <oxek> and I did the upgrade from a livecd
1667[22:49:00] <oxek> speed is crappy, but that's my own fault - I use full disk encryption without trim
1669[22:49:11] <sney> hardware vendors usually only support the latest firmware revision for a given device, so if you need vendor support, it's good to have it upgraded. but in my experience over years using various SSDs in linux, they're always fast regardless of firmware revisions/tweaks/etc and I've never needed to do anything special
1670[22:49:52] <sney> I guess it depends on your standard for "fast" - for me it's not having noticeable i/o lag except with large file transfers/opens
1674[22:50:47] <sney> there used to be major concerns with using TRIM etc to make sure you didn't run out of writes but AIUI that stopped being a real problem with the 2nd generation of devices, almost a decade ago
1727[23:33:18] *** Quits: akp55 (~akp55@replaced-ip) (Remote host closed the connection)
1728[23:33:28] <jelly> dd "from" the drive sounds like read; read perf can be different than write
1729[23:35:22] <FuzzyByte> jelly: Don't make him overwrite it lol
1730[23:35:24] <jelly> oxek, I leave about 15% of the ssd completely unused, it helps a lot on older devices and maybe also on newer; I also do not disable trim with luks
1731[23:35:49] <dvs> oxek, started over?
1732[23:37:07] <jelly> thus my 120GB ocz vertex 3, almost 10 years old, still lives
1733[23:37:21] <flayer> i have one of those as well
1734[23:37:31] <flayer> ^5
1735[23:37:50] *** Quits: donofrio_ (~donofrio@replaced-ip) (Remote host closed the connection)
1736[23:38:01] <jelly> (I learned a lesson after I killed an ocz vertex 2 with swapping after 8 months, and they replaced the unit with this one under warranty ;-)
1740[23:39:12] <jelly> lesson isn't "don't swap to ssd", but "have enough RAM" and also "ssd firmware might be smarter now but it still can breathe better if you leave 15-20% of space never, ever, used"
1741[23:39:30] *** Quits: donofrio_ (~donofrio@replaced-ip) (Remote host closed the connection)