Re: Maximum time for offline updates?
On Thu, Dec 22, 2022 at 04:57:54PM -0500, Stefan Monnier wrote: [...] > I find the idea of offline update rather odd: not only it's inconvenient > since the machine is unusable during this time, but on top of it, in > case of trouble, it can make it harder to fix the problem because you > may not be able to boot into a conveniently-usable system. That was my feeling, too. Only very involved scenarios came to mind, like "you have connectivity now, but are running on battery, and later you'll have AC power but no connectivity" or something. Cheers -- t signature.asc Description: PGP signature
Re: no sound after installing pulseaudio
It's necessary to unmute resources in pulseaudio and I don't know how to do that. No problem with alsa but pulseaudio given naming conventions for me was opaque. You may have good luck with pipewire but be prepared to install wireplumber if necessary. Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Fri, 23 Dec 2022, lou wrote: > i am running buster and install pulseaudio > > to let pulseaudio take effect i have to reboot > > but there's no sound though pavucontrol seems ok > > (pavucontrol shows sound is playing properly) > > to get sound back, i have to remove pulseaudio and reboot > > Thanks! > > >
no sound after installing pulseaudio
i am running buster and install pulseaudio to let pulseaudio take effect i have to reboot but there's no sound though pavucontrol seems ok (pavucontrol shows sound is playing properly) to get sound back, i have to remove pulseaudio and reboot Thanks!
Re: Maximum time for offline updates?
> I am using testing with KDE (but I suppose the desktop environnent does not > matter). I had a LOT of updates to apply today, so I used KDE Discover > (Gnome Software equivalent for KDE) to apply those in offline mode, ie > updates are dowloaded and then computer reboots in a special mode just to > update packages, and reboot normally when finished. Why? > Also, do you think I should report this issue? Yes. > Against which package? The package you used to do this "offline update" (hadn't heard of such a thing until now for Debian). I find the idea of offline update rather odd: not only it's inconvenient since the machine is unusable during this time, but on top of it, in case of trouble, it can make it harder to fix the problem because you may not be able to boot into a conveniently-usable system. Stefan
Re: latest testing update broke my laptop
>>> I can recommend the laptop as a reasonable candidate for Linux. Apart from >>> the need for proprietary drivers, which is something I blame nVidia for, it >>> seems to work perfectly. >> IME, getting the nVidia driver to work is easy, but keeping the nVidia >> driver working over time across upgrades is a real PITA... > In what sense? What problems have you had? Incompatibilities with the different packages. > These days, nvidia-kernel has been updated in Debian Stable so I could I use Debian Testing (and occasionally move/clone my system disks between machines), so that might be a good part of the difference of experience. As I said, the initial setup usually works fine (as long as the hardware is not too new to be supported), so if you mostly reinstall from scratch when an upgrade comes along you'd likely be fine. Stefan
Re: latest testing update broke my laptop
>>> I can recommend the laptop as a reasonable candidate for Linux. Apart from >>> the need for proprietary drivers, which is something I blame nVidia for, it >>> seems to work perfectly. >> IME, getting the nVidia driver to work is easy, but keeping the nVidia >> driver working over time across upgrades is a real PITA, and to the >> extent that most other machines should also be fully supported, I read >> what you wrote as "better choose something else" :-) > I have been using nVIDIA Optimus based systems for several years, with > Ubuntu Linux and now with Linux Mint, without any problems, since, when This is a Debian mailing list, tho. So your experience with other distributions is not directly relevant. > only Ubuntu (12.04) had the drivers for NVIDIA Optimus, [...] > The problem is NOT with nVIDIA. AFAIK it is, because they insist on doing things their way (and keeping their code proprietary), thus imposing more work on the rest of the infrastructure, which causes things like "only Ubuntu (12.04) had the drivers for NVIDIA Optimus" because only Ubuntu had the motivation&manpower to handle it quickly enough. > And, I am now running different computers, with different nVIDIA > configurations - some with Optimus, some without Optimus, with no problems > relating to nVIDIA. What would it take for a problem to be attributed to nVidia? Stefan
Re: loss of screen resolution, part 2
On 21/12/2022 00:26, Kleene, Steven (kleenesj) wrote: On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote: get-edid | parse-edid edid-decode /sys/class/drm/card0-HDMI-A-1/edid Thanks. get-edid doesn't find any EDIDs, and there are no edid files under /sys/devices. Have you checked "journalctl -b" (current boot only) output for messages related to missing firmware? It may be noticeable in "apt upgrade" messages when initramfs is created during installing of new kernel. As an experiment (it is better to remove new file or restore old version) latest firmware files may be taken from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree Such changes usually requires "update-initramfs -u" (normally performed by scripts insides firmware .deb packages).
Re: Maximum time for offline updates?
Hi Махно, No I had not read this manpage (by the way, maybe it should be mentioned in packagekit-offline-update.service?), thanks for the pointer. While very interesting, I could not find something related to my issue. Did I miss something? Regards, Yvan Le 22/12/2022 à 13:38, Махно a écrit : Hello. Did you read systemd.offline-updates man page? If not, here link: https://manpages.debian.org/testing/systemd/systemd.offline-updates.7.en.html 2022-12-22, kt, 09:43 Yvan Masson rašė: Le 21/12/2022 à 21:42, Georgi Naplatanov a écrit : On 12/21/22 19:59, Yvan Masson wrote: Hi list, I am using testing with KDE (but I suppose the desktop environnent does not matter). I had a LOT of updates to apply today, so I used KDE Discover (Gnome Software equivalent for KDE) to apply those in offline mode, ie updates are dowloaded and then computer reboots in a special mode just to update packages, and reboot normally when finished. However, update stopped before all packages where updated and computer rebooted with packages in a broken state. When I look journalctl, I see beginning of the update process: 17:44:41 pk-offline-update[742]: sent mode to plymouth 'updates' And exactly ten minutes later it stops brutally: 17:54:40 systemd[1]: packagekit-offline-update.service: Main process exited, code=killed, status=15/TERM 17:54:40 systemd[1]: packagekit-offline-update.service: Failed with result 'signal'. I suppose this maximum time comes somewhere from a systemd configuration or systemd unit, but could not find where. Any idea? Also, do you think I should report this issue? Against which package? Hi Yvan, I don't know what the problem is. Possible workarounds could be to try to upgrade the system from console: - option #1 # apt update # apt upgrade - option #2 # aptitude update # aptitude upgrade Kind regards Georgi Hi Georgi, Thanks for the suggestion, but I already know how to do that. I think offline updates are a good thing for "average user", so I would like either: - knowing how to configure Debian properly so that it works realiably - or reporting this issue somewhere so that it can be fixed in Debian/upstream Regards, Yvan OpenPGP_signature Description: OpenPGP digital signature
xscreensaver problem
I have now a big problem with xscreensaver. Up to yesterday, it worked perfectly, but I had to re-install Debian on my PC, and now if fails when I run "xscreensaver" I get: xscreensaver-systemd: 13:59:54: user bus connection failed: No medium found If I run "xscreensaver-demo", I get "Segmentation fault" I was unable to find what changes from my previous install to the new one can explain that. Has anybody an idea? best regards, Pierre Frenkiel
xscreensaver problem
I have now a big problem with xscreensaver. Up to yesterday, it worked perfectly, but I had to re-install Debian on my PC, and now if fails when I run "xscreensaver" I get: xscreensaver-systemd: 13:59:54: user bus connection failed: No medium found If I run "xscreensaver-demo", I get "Segmentation fault" I was unable to find what changes from my previous install to the new one can explain that. Has anybody an idea? best regards, Pierre Frenkiel
xscreensaver problem
hi, I have now a big problem with xscreensaver. Up to yesterday, it worked perfectly, but I had to re-install Debian on my PC, and now if fails when I run "xscreensaver" I get: xscreensaver-systemd: 13:59:54: user bus connection failed: No medium found If I run "xscreensaver-demo", I get "Segmentation fault" I was unable to find what changes from my previous install to the new one can explain that. Has anybody an idea? best regards, Pierre Frenkiel
Re: Maximum time for offline updates?
Hello. Did you read systemd.offline-updates man page? If not, here link: https://manpages.debian.org/testing/systemd/systemd.offline-updates.7.en.html 2022-12-22, kt, 09:43 Yvan Masson rašė: > > Le 21/12/2022 à 21:42, Georgi Naplatanov a écrit : > > On 12/21/22 19:59, Yvan Masson wrote: > >> Hi list, > >> > >> I am using testing with KDE (but I suppose the desktop environnent > >> does not matter). I had a LOT of updates to apply today, so I used KDE > >> Discover (Gnome Software equivalent for KDE) to apply those in offline > >> mode, ie updates are dowloaded and then computer reboots in a special > >> mode just to update packages, and reboot normally when finished. > >> > >> However, update stopped before all packages where updated and computer > >> rebooted with packages in a broken state. > >> > >> When I look journalctl, I see beginning of the update process: > >> > >> 17:44:41 pk-offline-update[742]: sent mode to plymouth 'updates' > >> > >> And exactly ten minutes later it stops brutally: > >> > >> 17:54:40 systemd[1]: packagekit-offline-update.service: Main process > >> exited, code=killed, status=15/TERM > >> 17:54:40 systemd[1]: packagekit-offline-update.service: Failed with > >> result 'signal'. > >> > >> > >> I suppose this maximum time comes somewhere from a systemd > >> configuration or systemd unit, but could not find where. Any idea? > >> Also, do you think I should report this issue? Against which package? > >> > > > > Hi Yvan, > > > > I don't know what the problem is. Possible workarounds could be to try > > to upgrade the system from console: > > > > - option #1 > > # apt update > > # apt upgrade > > > > - option #2 > > # aptitude update > > # aptitude upgrade > > > > > > Kind regards > > Georgi > > > Hi Georgi, > > Thanks for the suggestion, but I already know how to do that. I think > offline updates are a good thing for "average user", so I would like either: > - knowing how to configure Debian properly so that it works realiably > - or reporting this issue somewhere so that it can be fixed in > Debian/upstream > > Regards, > Yvan
