Re: systemd version 256.7-2 on Debian testing disabled UTMP support
> I am guessing from the version number that this is on trixie/sid. On Correct, thanks for guessing. > November 4th, systemd 256.7-3 came through. Have you tested whether > that fixed the issue? Nothing has changed with that version (note the "-UTMP"): , | [~]$ systemctl --version | systemd 256 (256.7-3) | +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE | | [~]$ grep utmp /usr/lib/tmpfiles.d/systemd.conf || echo no hits | no hits ` and given the fact that the change has been explicitly mentioned in systemd's Debian changelog I doubt that anything will change here. IOW, I do not consider this a systemd bug, but I'm curious about how Debian plans to handle the bigger utmp picture here. Please CC me in replies, as I'm not subscribed to the list. Thanks!
Re: systemd version 256.7-2 on Debian testing disabled UTMP support
On Wed, 6 Nov 2024 21:18:33 +0100 Jens Schmidt wrote: > [I hope this is the right way to address this question - apologies > if not or if I have overlooked an existing discussion ...] > > systemd version 256.7-2 on Debian disabled UTMP support (from the > Debian changelog): I am guessing from the version number that this is on trixie/sid. On November 4th, systemd 256.7-3 came through. Have you tested whether that fixed the issue? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
systemd version 256.7-2 on Debian testing disabled UTMP support
[I hope this is the right way to address this question - apologies if not or if I have overlooked an existing discussion ...] systemd version 256.7-2 on Debian disabled UTMP support (from the Debian changelog): , | [ Luca Boccassi ] | * systemd-boot: depend on systemd for kernel-install (Closes: #1085012) | * Disable utmp support, not y2038 safe. utmp support in tmux has been | disabled, so autopkgtest should no longer break | * Backport fixes for upstream autopkgtest suite ` As a result, no `utmp' file is created on systems having that version of systemd installed. However, utmp(5) states that , | Unlike various other systems, where utmp logging can be disabled by re‐ | moving the file, utmp must always exist on Linux. [...] ` And at least on my system I get the following errors logged in my journal: , | [ 24.434215] host01 lightdm[2087]: Failed to write utmpx: No such file or directory | [...] | [ 30.866566] host01 systemd[2094]: Started app-xterm1fxd.service - /home/farblos/bin/lwsdi shutdown "FVWM Child" "Wait for explicit exit" block xterm -name xterm1fxd -title "XTerm 1". | [ 31.026661] host01 utempter[2538]: [ppid=2536] pututline: No such file or directory ` Since: - I'd like to get rid of these warnings/errors, - I'd like to have an `utmp' file that does *not* last across reboots and - I don't care (yet) about the Y2038 problem, I came up with file `/etc/tmpfiles.d/90-local-utmp.conf' containing what `/usr/lib/tmpfiles.d/systemd.conf' previously provided, namely: , | f+! /run/utmp 0664 root utmp - ` Would that be the "correct" or "Debian-ish" way to provide an `utmp' file that fulfills my above requirements? And: Should users file Debian bugs against applications still relying on `utmp'? Or will there be some replacement for what systemd has provided?
Re: System getting slower and slower (debian Testing)
Hi, please ignore the previous message It seems that upgrading from 6-0-1 to 6-0-5 fix the problem (that or autoremove) regards, Laurent Le dim. 17 déc. 2023 à 10:44, Laurent Debian a écrit : > Dear All, > I am running debian Testing, > I did two things recently, upgrading the debian and changing my graphic > cards (radeon RX 570 -> radeon RX 7600). > Before that my desktop was in good shape, quite reactive and so on. > For a few days I have experienced a super slow system with a lot of lag. > I first thought of not enough free space but it does not seem to be the > case > I can't even play an audio files, without having it stutter, not to > mention videos or audio online. > A lot of problems seem to show in the dmesg output related to the graphic > driver but I don't know what to do :/ > Any help would be appreciated ! > > Regards, > Laurent >
GNOME 43.3 performance issues after Debian Testing update (March 1)
Dear Mantainer, After the last update, the GNOME desktop animations have not been smooth, and things only turn fluid again after setting the performance mode. I am 100% sure that hardware isn't the problem here as this issue didn't occur before the upgrade. This issue however is not like the one that GNOME 3.30 had. What happens here is that there are noticeable and random frame drops in the animations. It happens on Wayland and Xorg. === The packages that were upgraded (and probably are related to the issue) === manpages-dev:amd64 (6.02-1, 6.03-1), libtss2-tcti-cmd0:amd64 (3.2.1-2, 3.2.1-3), avahi-autoipd:amd64 (0.8-8, 0.8-9), tzdata:amd64 (2022g-5, 2022g-7), yt-dlp:amd64 (2023.01.06-1, 2023.02.17-1), libpipewire-0.3-common:amd64 (0.3.65-2, 0.3.65-3), pipewire-pulse:amd64 (0.3.65-2, 0.3.65-3), libtss2-tcti-device0:amd64 (3.2.1-2, 3.2.1-3), libavahi-common-data:amd64 (0.8-8, 0.8-9), libavahi-common-data:i386 (0.8-8, 0.8-9), libavahi-core7:amd64 (0.8-8, 0.8-9), libmutter-11-0:amd64 (43.2-6, 43.3-3), libtss2-tcti-swtpm0:amd64 (3.2.1-2, 3.2.1-3), libtiffxx6:amd64 (4.5.0-4, 4.5.0-5), linux-compiler-gcc-12-x86:amd64 (6.1.8-1, 6.1.12-1), libtiff6:amd64 (4.5.0-4, 4.5.0-5), libtiff6:i386 (4.5.0-4, 4.5.0-5), linux-cpupower:amd64 (6.1.8-1, 6.1.12-1), avahi-daemon:amd64 (0.8-8, 0.8-9), linux-headers-amd64:amd64 (6.1.8-1, 6.1.12-1), pipewire:amd64 (0.3.65-2, 0.3.65-3), libtss2-mu0:amd64 (3.2.1-2, 3.2.1-3), mutter-common:amd64 (43.2-6, 43.3-3), libtss2-rc0:amd64 (3.2.1-2, 3.2.1-3), linux-kbuild-6.1:amd64 (6.1.8-1, 6.1.12-1), libfuse3-3:amd64 (3.13.0-2, 3.14.0-2), linux-image-amd64:amd64 (6.1.8-1, 6.1.12-1), libspa-0.2-bluetooth:amd64 (0.3.65-2, 0.3.65-3), manpages:amd64 (6.02-1, 6.03-1), gir1.2-mutter-11:amd64 (43.2-6, 43.3-3), gstreamer1.0-pipewire:amd64 (0.3.65-2, 0.3.65-3), fuse3:amd64 (3.13.0-2, 3.14.0-2), libtss2-tctildr0:amd64 (3.2.1-2, 3.2.1-3), libtss2-tcti-mssim0:amd64 (3.2.1-2, 3.2.1-3), pipewire-audio:amd64 (0.3.65-2, 0.3.65-3), pipewire-bin:amd64 (0.3.65-2, 0.3.65-3), libavahi-common3:amd64 (0.8-8, 0.8-9), libavahi-common3:i386 (0.8-8, 0.8-9), libtss2-sys1:amd64 (3.2.1-2, 3.2.1-3), libspa-0.2-modules:amd64 (0.3.65-2, 0.3.65-3), libavahi-glib1:amd64 (0.8-8, 0.8-9), sudo:amd64 (1.9.12p2-1, 1.9.13p1-1), libgnutls30:amd64 (3.7.8-5, 3.7.9-1), libgnutls30:i386 (3.7.8-5, 3.7.9-1), libcpupower1:amd64 (6.1.8-1, 6.1.12-1), libpipewire-0.3-modules:amd64 (0.3.65-2, 0.3.65-3), libtss2-esys-3.0.2-0:amd64 (3.2.1-2, 3.2.1-3), xterm:amd64 (378-1, 379-1), libtiff-dev:amd64 (4.5.0-4, 4.5.0-5), libavahi-client3:amd64 (0.8-8, 0.8-9), libavahi-client3:i386 (0.8-8, 0.8-9), intel-media-va-driver-non-free:amd64 (23.1.0+ds1-1, 23.1.1+ds1-1), pipewire-alsa:amd64 (0.3.65-2, 0.3.65-3), linux-libc-dev:amd64 (6.1.8-1, 6.1.12-1), libpipewire-0.3-0:amd64 (0.3.65-2, 0.3.65-3) === === Sytem Details === System: Host: moura Kernel: 6.1.0-5-amd64 arch: x86_64 bits: 64 Desktop: GNOME v: 43.3 Distro: Debian GNU/Linux bookworm/sid Machine: Type: Laptop System: LENOVO product: 82NM v: Lenovo V14 G2 ITL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40688 WIN serial: UEFI: LENOVO v: GGCN29WW date: 08/18/2021 CPU: Info: quad core model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP cache: L2: 5 MiB Speed (MHz): avg: 2063 min/max: 400/4700 cores: 1: 1352 2: 2800 3: 1268 4: 614 5: 2800 6: 2073 7: 2800 8: 2800 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce MX350] driver: nvidia v: 525.85.12 Device-3: Chicony Integrated Camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Xe Graphics (TGL GT2) ===
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
On Tue, Jan 31, 2023 at 9:42 AM Shalom Ben-Zvii Kazaz wrote: > > On Mon, Jan 30, 2023 at 6:00 PM Alexandre Rossi wrote: > >> Hi, >> >> > In the past week my laptop freezes randomly, I can say it happens every >> 2-3 >> > hours. but there are actions that consistently always cause a freeze, >> like >> > opening Zoom or executing lspci in Terminator. >> >> I would suggest: >> - try to get more debugging info using SysRQ keys [1] >> - try to get more debugging info using netconsole[2] (needs wired >> connection) >> - try another OS (Ubuntu live CD, Windows) to rule out hardware problem >> > > following the suggestion to try another OS i booted the computer with > ubuntu 22.4 live usb, i'm working with since yesterday with no issues. i > have enough memory so i installed some of the applications i use like > slack,zoom,terminator and more, i even installed intellij idea and worked > on my project for hours. zoom works with video ,slack works, there is no > freeze , the computer is up with ubuntu 22.4 for almost 24 hours and > everything looks ok. > So i guess there is no hardware problem. > So i don't know what to do, I'm thinking to reinstall debian but I'm not > sure the problem will disappear because it may be something with the kernel > of some package. > Try booting with Debian 11 Bullseye live images. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0-live+nonfree/amd64/iso-hybrid/ If all your hardware works with Bullseye then go with it. Debian testing is nice but it can from time to time get hosed. Since you have been running testing since Bullseye was in testing it should be good to go for you. I have debian testing running on AMD Ryzen 7 4700U with Radeon Graphics with 16 Gig's of RAM and I have had some shell crashes recently. The background turns grey and everything freezes except the mouse. I am able to switch to a command line terminal without issue. TOP and free -h both show that I have lots of available resources and there isn't any one run away process using all my resources. I am also having a problem with KDE's instant messenger complaining that I do not have kaccounts-integration installed. I tried reinstalling it and it still reports that it is not installed. Trying to launch "Instant Messaging Settings" caused the system shell to crash and appear to be locked up. The mouse still moves just fine. I would move to Bullseye but I need Firmware in Bookworm to run my Sound and WiFi. I am not a fan of backports, I have never had a good experience with it. Installing software with backports is no trouble but keeping them up to date is an issue because it does not automatically want to install newer versions even when the package was installed form backports. > >> [1] https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html >> [2] https://debamax.com/blog/2019/01/03/debugging-with-netconsole/ >> >> Alex >> >> -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
On Tue 31 Jan 2023 at 14:41:24 (+), Shalom Ben-Zvii Kazaz wrote: > On Mon, Jan 30, 2023 at 6:00 PM Alexandre Rossi wrote: > > > In the past week my laptop freezes randomly, I can say it happens every > > 2-3 > > > hours. but there are actions that consistently always cause a freeze, > > like > > > opening Zoom or executing lspci in Terminator. > > > > I would suggest: > > - try to get more debugging info using SysRQ keys [1] > > - try to get more debugging info using netconsole[2] (needs wired > > connection) > > - try another OS (Ubuntu live CD, Windows) to rule out hardware problem > > > > following the suggestion to try another OS i booted the computer with > ubuntu 22.4 live usb, i'm working with since yesterday with no issues. i > have enough memory so i installed some of the applications i use like > slack,zoom,terminator and more, i even installed intellij idea and worked > on my project for hours. zoom works with video ,slack works, there is no > freeze , the computer is up with ubuntu 22.4 for almost 24 hours and > everything looks ok. > So i guess there is no hardware problem. > So i don't know what to do, I'm thinking to reinstall debian but I'm not > sure the problem will disappear because it may be something with the kernel > of some package. Earlier you wrote "I've been using this laptop for the past 3 years with the same setup with debian testing since its new", which means that you should be able to run this machine with bullseye. If you run testing, do full-upgrades, and expect full-upgrades are going to fix things, then you might be better off sticking with the stable distribution, assuming you were to go back to Debian. Cheers, David.
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
On Mon, Jan 30, 2023 at 6:00 PM Alexandre Rossi wrote: > Hi, > > > In the past week my laptop freezes randomly, I can say it happens every > 2-3 > > hours. but there are actions that consistently always cause a freeze, > like > > opening Zoom or executing lspci in Terminator. > > I would suggest: > - try to get more debugging info using SysRQ keys [1] > - try to get more debugging info using netconsole[2] (needs wired > connection) > - try another OS (Ubuntu live CD, Windows) to rule out hardware problem > following the suggestion to try another OS i booted the computer with ubuntu 22.4 live usb, i'm working with since yesterday with no issues. i have enough memory so i installed some of the applications i use like slack,zoom,terminator and more, i even installed intellij idea and worked on my project for hours. zoom works with video ,slack works, there is no freeze , the computer is up with ubuntu 22.4 for almost 24 hours and everything looks ok. So i guess there is no hardware problem. So i don't know what to do, I'm thinking to reinstall debian but I'm not sure the problem will disappear because it may be something with the kernel of some package. > > [1] https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html > [2] https://debamax.com/blog/2019/01/03/debugging-with-netconsole/ > > Alex > >
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
I can get lspci listing with Gnome terminal with no problem , but when i try with Terminator, the second i press the enter key the computer freezes, well most of the time at least once it succeeded with Terminator too. On Mon, Jan 30, 2023 at 8:43 PM Charles Curley < charlescur...@charlescurley.com> wrote: > On Mon, 30 Jan 2023 18:59:19 +0200 > Shalom Ben-Zvii Kazaz wrote: > > > In the past week my laptop freezes randomly, I can say it happens > > every 2-3 hours. but there are actions that consistently always cause > > a freeze, like opening Zoom or executing lspci in Terminator. > > lspci leads me to wonder if lspci is triggering a hardware flaw > somewhere on the PCI bus. And Zoom might do the same thing: I > conjecture that it looks for cameras on the PCI and USB busses. > > Does it always freeze at the same point in the lspci listing? What > happens if you do a verbose listing? 'lspci -v' > > Can you get a complete lspci listing using an older version of Linux, > or a live CD version (e.g. finnix)? > > > > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > >
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
I tried SysRQ and there is no response when the computer freezes. i tried before freeze to make sure i know how to use it and it worked, i tried b and k and it worked. but when the computer freezes there is nothing, no response. On Mon, Jan 30, 2023 at 8:00 PM Alexandre Rossi wrote: > Hi, > > > In the past week my laptop freezes randomly, I can say it happens every > 2-3 > > hours. but there are actions that consistently always cause a freeze, > like > > opening Zoom or executing lspci in Terminator. > > I would suggest: > - try to get more debugging info using SysRQ keys [1] > - try to get more debugging info using netconsole[2] (needs wired > connection) > - try another OS (Ubuntu live CD, Windows) to rule out hardware problem > > [1] https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html > [2] https://debamax.com/blog/2019/01/03/debugging-with-netconsole/ > > Alex > >
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
On Mon, 30 Jan 2023 18:59:19 +0200 Shalom Ben-Zvii Kazaz wrote: > In the past week my laptop freezes randomly, I can say it happens > every 2-3 hours. but there are actions that consistently always cause > a freeze, like opening Zoom or executing lspci in Terminator. lspci leads me to wonder if lspci is triggering a hardware flaw somewhere on the PCI bus. And Zoom might do the same thing: I conjecture that it looks for cameras on the PCI and USB busses. Does it always freeze at the same point in the lspci listing? What happens if you do a verbose listing? 'lspci -v' Can you get a complete lspci listing using an older version of Linux, or a live CD version (e.g. finnix)? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: laptop freezes randomly - please help!! dell xps 15 with debian testing
Hi, > In the past week my laptop freezes randomly, I can say it happens every 2-3 > hours. but there are actions that consistently always cause a freeze, like > opening Zoom or executing lspci in Terminator. I would suggest: - try to get more debugging info using SysRQ keys [1] - try to get more debugging info using netconsole[2] (needs wired connection) - try another OS (Ubuntu live CD, Windows) to rule out hardware problem [1] https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html [2] https://debamax.com/blog/2019/01/03/debugging-with-netconsole/ Alex
laptop freezes randomly - please help!! dell xps 15 with debian testing
Hello, Sorry for starting a new conversation, the previous one didn't help me and I hope that now I have more details. I don't have any idea how to approach that, its my workstation and the past few days I just couldn't really work. I'm also not experienced with this mailing list and a bit confused how to reply here. I hope this time I will do it right. In the past week my laptop freezes randomly, I can say it happens every 2-3 hours. but there are actions that consistently always cause a freeze, like opening Zoom or executing lspci in Terminator. Its a dell xps 15 7590, Intel® Core™ i9-9980HK × 16, 64.0 GiB memory, Mesa Intel® UHD Graphics 630 (CFL GT2), The laptop is attached to a dell docking station wd19 with an external monitor and keyboard and external mouse. It's running Debian GNU/Linux bookworm (debian testing) with Gnome. I've been using this laptop for the past 3 years with the same setup with debian testing since its new. two month ago an official Dell technician replaced the keyboard and fans and cooling board while still under Dell warranty. The freeze started a few days ago after I did full-upgrade. Since then I did full-upgrade again a few times hoping that it's a bug that was fixed but it's still freezing. I always have a few projects open in Jetbrains Intellij idea and rider. I configure Intellij with 20GB memory, always a few browser windows open with many tabs, usually brave and chromium. I always have a few windows and tabs open in Terminator. and more. The freeze always happens as a result of some UI action. examples are when i tried to open settings, or some action in Intellij idea. It's completely random and happens with other applications too. there are actions that always cause a freeze, i tried that again and again restarting the computer every time and it's always the same result, and something suspicious with terminator: trying to open the Zoom app always causes a freeze, I use zoom regularly and there was never a problem until a few days ago. trying to execute the command lspci in Terminator always causes a freeze, everything else in terminator works. executing lspci in Gnome terminal works, that looks to me very suspicious. I tried that at least 10 times to make sure that it's not a coincidence and it's always the same, typing lspci in Terminator and then Enter freezes the computer, but not in Gnome terminal. What I did: As suggested to me here, I connected an ssh session with top and journalctrl -f from another computer and waited for a freeze. I have the latest messages from both at the bottom of this message. I started the computer with a gnome classic session, same thing, computer freeze. started with xfce session, same thing. I ran the Dell pre-boot performance test including a full memory test and it passed OK. I removed all the devices connected like external mouse and keyboard and same thing. I detached the laptop from the docking station and the computer freezes when trying to open zoom or execute lspci in Terminator. I hope someone can help in finding the cause of that freeze. this is info i collected This is journalctrl from another computer in ssh session just before the computer freeze, the freeze was exactly at 16:39 Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: java.lang.RuntimeException: Cannot invoke (class=, method=projectClosing, topic=ProjectManagerListener) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.util.messages.impl.MessageBusImplKt.invokeListener(MessageBusImpl.kt:639) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.util.messages.impl.MessageBusImplKt.executeOrAddToQueue(MessageBusImpl.kt:466) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.util.messages.impl.ToDirectChildrenMessagePublisher.publish$intellij_platform_core(CompositeMessageBus.kt:295) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.util.messages.impl.MessagePublisher.invoke(MessageBusImpl.kt:421) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at jdk.proxy2/jdk.proxy2.$Proxy97.projectClosing(Unknown Source) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.openapi.project.impl.ProjectManagerImplKt.fireProjectClosing(ProjectManagerImpl.kt:1040) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.openapi.project.impl.ProjectManagerImplKt.access$fireProjectClosing(ProjectManagerImpl.kt:1) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.openapi.project.impl.ProjectManagerImpl.closeProject(ProjectManagerImpl.kt:426) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.openapi.project.impl.ProjectManagerImpl.closeProject$default(ProjectManagerImpl.kt:369) Jan 30 16:38:57 xps-debian jetbrains-idea-ce.desktop[82252]: at com.intellij.openapi.project.impl.ProjectMana
Re: laptop frozen when opening apps, debian testing with gnome
OK, I did it. i didn't wait for the freeze to happen randomly because it may take time, i tried to open zoom which always causes a freeze, It started only in the past few days and after a full-upgrade, i use zoom regularly and there was no problem before the last full-upgrade. its debian testing. I opened zoom with super key, search for zoom and enter. the computer freezes immediately. there was nothing in dmesg or /var/log/messages before the freeze, this is what was in journalctl and top, i don't know how to tell if there is something suspicious. journalctl Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.Contacts.SearchProvider' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.Nautilus' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.Characters' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.clocks' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.seahorse.Application' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Settings.SearchProvider' Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Calculator.SearchProvider' Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.clocks' Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.seahorse.Application' Jan 30 00:01:49 xps-debian nautilus[9317]: Connecting to org.freedesktop.Tracker3.Miner.Files Jan 30 00:01:49 xps-debian systemd[3253]: Starting GNOME Terminal Server... Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Nautilus' Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Contacts.SearchProvider' Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Characters' Jan 30 00:01:49 xps-debian nautilus[9317]: g_hash_table_foreach: assertion 'hash_table != NULL' failed Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.DiskUtility' requested by ':1.170' (uid=1000 pid=9317 comm="/usr/bin/nautilus --gapplication-service") Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.DiskUtility' Jan 30 00:01:49 xps-debian gnome-character[9321]: JS LOG: Characters Application started Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated service 'org.gnome.Terminal' Jan 30 00:01:49 xps-debian systemd[3253]: Started GNOME Terminal Server. Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Activating service name='org.gnome.seahorse.Application' requested by ':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell") Jan 30 00:01:49 xps-debian gnome-shell[3523]: Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Terminal/SearchProvider” Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297] Successfully activated ser
Re: freezing / unstable Debian Testing on MSI Stealth GS77 laptop
Hi JD, sorry to hear that you have these kind of troubles. I dont know much about this gpu/igpu setups, but I want to give some proceedings I would choose: You write that there dont seem to be any logs. Where did You look? I would expect, that there might me /var/log/syslog messages concerning kernel panics or maybe SystemD journal entries from that last boot (journalctl -b 1 or smth). What kind of logs did You check or are some logs Your google searches might have produced not there or empty? They might have to bee enabled. Also there might be error messages of the xserver /var/log/Xorg.0.log. On top I would take a look into the messages of my Xsession itself (~.xsession-errors) Many places to check, I'm afraid to say :) If You have another system You could ssh into Your crash prone laptop to get messages live. Posting some details about the versions of the nvidia modules and such might be useful. Some other readers might be able to compare such strings. And which CPU version does Your notebook have? (cat /proc/cpuinfo, maybe). If this is a CPU in a combo setup "some big/beefy cores and some lightweight/lowpower cores" it have implications w. applications in my opinion. And one thing I would like to recommend: try another, maybe more recent system. Boot from a ubuntu or fedora or some outher fresh distributions live iso and check / compare modules and configuration parameters and - if possible - behaviour of the particular applications. Good luck and please post log contents or snippes of logs, if You find some. Cheers, Martin On 2023-01-25 09:56, JD wrote: Hello, I'm trying to find some help in order to debug or resolve the issues I'm facing. Hopefully, someone will be able to help me here. The main problem that prevents me from trying to solve it myself is the absence of logs and messages. So, my laptop MSI Stealth GS77 with a Debian testing (up to date) installed on it can freeze when launching 3D programs (both with setting the nVidia card or the integrated Intel chipset). Once it also complained about missing SSD drive (nvme). I currently don't know if both could be related, but I'd say it's unlikely. Some information about my system: I installed Debian testing since latest Debian stable had many issues (no audio, not wifi, unstable 3D graphics...). Debian stable with backports didn't helped much (it fixed some issues but not all). Therefore, the most practicable is Debian testing. The issue I have is that seldom (but quite often), when running a 3D program, the OS is completely freezing. There is no way to retrieve any logs or information about the issue. The screen freezes, the keyboard doesn't respond. The only thing I can do is to use a long press on the power button to switch the laptop off (alt sys o doesn't work either). And on the next reboot, my filesystem fixes wrong inodes and therefore this is not possible to consultate any logs. I don't really like to say that, but the laptop works well on Windows 11 (no freeze, no crash, no nvme issues). Thus my belief that the issue is on the Linux side. More information: Desktop: XFCE nvidia: latest proprietary modules available on Debian. Also tested with modules directly provided by nVidia. 3D programs run on nVidia or the Intel chipset (with setting appropriately __NV_PRIME_RENDER_OFFLOAD and __GLX_VENDOR_LIBRARY_NAME). I played a lot with bumblebee, update-glx, keeping updating packages, but nothing worked at this time. uname -a Linux wormhole 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #1 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:0d.3 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #1 (rev 02) 00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3
Re: laptop frozen when opening apps, debian testing with gnome
On Sunday, January 29, 2023 01:59:51 AM Shalom Ben-Zvii Kazaz wrote: > There is no ssh when its frozen Hmm, I'm a little confused, and maybe you are, also. I think the intent of the advice was to log into the frozen laptop from another computer / device, using ssh *while the frozen laptop is not frozen*. Further, on that other device, run a command like top or journalctrl -f, and then wait (or cause) the laptop to freeze. Then examine top or such on the working computer to look for clues as to why the frozen laptop has frozen. (I may be confused. ;-) -- rhk (sig revised 20221206) If you reply: snip, snip, and snip again; leave attributions; avoid HTML; avoid top posting; and keep it "on list". (Oxford comma (and semi-colon) included at no charge.) If you revise the topic, change the Subject: line. If you change the topic, start a new thread. Writing is often meant for others to read and understand (legal documents excepted?) -- make it easier for your reader by various means, including liberal use of whitespace (short paragraphs, separated by whitespace / blank lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and references. If someone has already responded to a question, decide whether any response you add will be helpful or not ... A picture is worth a thousand words. A video (or "audio"): not so much -- divide by 10 for each minute of video (or audio) or create a transcript and edit it to 10% of the original. A speaker who uses ahhs, ums, or such may have a real physical or mental disability, or may be showing disrespect for his listeners by not properly preparing in advance and thinking before speaking. (Remember Cicero who did not have enough time to write a short missive.) (That speaker might have been "trained" to do this by being interrupted often if he pauses.) A radio (or TV) station which broadcasts speakers with high pitched voices (or very low pitched / gravelly voices) (which older people might not be able to hear properly) disrespects its listeners. Likewise if it broadcasts extraneous or disturbing sounds (like gunfire or crying), or broadcasts speakers using their native language (with or without an overdubbed translation). A person who writes a sig this long probably has issues and disrespects (and offends) a large number of readers. ;-) '
Re: laptop frozen when opening apps, debian testing with gnome
There is no ssh when its frozen On Mon, Jan 23, 2023 at 11:19 PM Stefan Monnier wrote: > > completely frozen, need to shut down and restart. > > I'd check to see "how" frozen it is: e.g. try to log into it via SSH (or > better yet, keep an `ssh` or `mosh` connection to it with an `atop` or > `top` running inside of it, and/or `journalctl -f` so when it freezes > you can immediately see if the remote connection is also frozen and > what it is/was doing). > > > Stefan > >
debian testing updates - python3.11 landed today
for those running the testing distribution: just thought i would put this out there for those here who are heavy python users who might not be aware of how this transition is going (seems to be mostly ok for now but i'm sure some people who are doing strange things might find it needs some work to get things running again). if you are a heavy processing user i'll be interested to hear how your system changes because there are supposed to be some performance improvements. songbird
freezing / unstable Debian Testing on MSI Stealth GS77 laptop
Hello, I'm trying to find some help in order to debug or resolve the issues I'm facing. Hopefully, someone will be able to help me here. The main problem that prevents me from trying to solve it myself is the absence of logs and messages. So, my laptop MSI Stealth GS77 with a Debian testing (up to date) installed on it can freeze when launching 3D programs (both with setting the nVidia card or the integrated Intel chipset). Once it also complained about missing SSD drive (nvme). I currently don't know if both could be related, but I'd say it's unlikely. Some information about my system: I installed Debian testing since latest Debian stable had many issues (no audio, not wifi, unstable 3D graphics...). Debian stable with backports didn't helped much (it fixed some issues but not all). Therefore, the most practicable is Debian testing. The issue I have is that seldom (but quite often), when running a 3D program, the OS is completely freezing. There is no way to retrieve any logs or information about the issue. The screen freezes, the keyboard doesn't respond. The only thing I can do is to use a long press on the power button to switch the laptop off (alt sys o doesn't work either). And on the next reboot, my filesystem fixes wrong inodes and therefore this is not possible to consultate any logs. I don't really like to say that, but the laptop works well on Windows 11 (no freeze, no crash, no nvme issues). Thus my belief that the issue is on the Linux side. More information: Desktop: XFCE nvidia: latest proprietary modules available on Debian. Also tested with modules directly provided by nVidia. 3D programs run on nVidia or the Intel chipset (with setting appropriately __NV_PRIME_RENDER_OFFLOAD and __GLX_VENDOR_LIBRARY_NAME). I played a lot with bumblebee, update-glx, keeping updating packages, but nothing worked at this time. uname -a Linux wormhole 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #1 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:0d.3 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #1 (rev 02) 00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation Device 51b8 (rev 01) 00:1c.6 PCI bridge: Intel Corporation Device 51be (rev 01) 00:1c.7 PCI bridge: Intel Corporation Alder Lake PCH-P PCI Express Root Port #9 (rev 01) 00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01) 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 01:00.0 3D controller: NVIDIA Corporation GA104 [Geforce RTX 3070 Ti Laptop GPU] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO 2e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5261 PCI Express Card Reader (rev 01) 2f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer E3000 2.5GbE Controller (rev 06) lsmod Module Size Used by dm_mod 184320 0 snd_ctl_led 24576 0 snd_soc_skl_hda_dsp 24576 6 snd_soc_intel_hda_dsp_common 20480 1 snd_soc_skl_hda_dsp snd_soc_hdac_hdmi 45056 1 snd_soc_skl_hda_dsp snd_sof_probes 24576 0 snd_soc_dmi
Re: laptop frozen when opening apps, debian testing with gnome
> completely frozen, need to shut down and restart. I'd check to see "how" frozen it is: e.g. try to log into it via SSH (or better yet, keep an `ssh` or `mosh` connection to it with an `atop` or `top` running inside of it, and/or `journalctl -f` so when it freezes you can immediately see if the remote connection is also frozen and what it is/was doing). Stefan
Re: laptop frozen when opening apps, debian testing with gnome
On 1/23/23 11:59, Shalom Ben-Zvii Kazaz wrote: since the latest full-upgrade three days ago on my laptop the computer gets completely frozen sometimes, yesterday got frozen few times when i tried to open zoom. today few times when i tried to open brave browser. completely frozen, need to shut down and restart. i'm running debian testing for three years on that laptop, dell xps 15, gnome desktop. what can i do,check? i'm not so experienced, usually there are no problems. Three things I'd try (for diagnostic testing): 1 - log in as a different user; does that user have the same freezing issues? 2 - log into a different Desktop Environment (Plasma, Cinnamon, etc); does that DE have the same freezing issues? 3 - On boot, choose Advanced options; does that give you the ability to boot into the last kernel you had before the upgrade? If so, select it; does that option have the same freezing issues? -- Kent West<")))>< IT Support::Client Support Abilene Christian University Westing Peacefully - http://kentwest.blogspot.com
Re: laptop frozen when opening apps, debian testing with gnome
On Mon, Jan 23, 2023 at 1:00 PM Shalom Ben-Zvii Kazaz wrote: > > since the latest full-upgrade three days ago on my laptop the computer gets > completely frozen sometimes, yesterday got frozen few times when i tried to > open zoom. today few times when i tried to open brave browser. completely > frozen, need to shut down and restart. > i'm running debian testing for three years on that laptop, dell xps 15, gnome > desktop. > what can i do,check? i'm not so experienced, usually there are no problems. I would start with a hardware check. Is memtest available when you boot the machine? I would also be interested to know if you can test the video card. I don't know of any utilities to perform the check, however. Jeff
laptop frozen when opening apps, debian testing with gnome
Hi since the latest full-upgrade three days ago on my laptop the computer gets completely frozen sometimes, yesterday got frozen few times when i tried to open zoom. today few times when i tried to open brave browser. completely frozen, need to shut down and restart. i'm running debian testing for three years on that laptop, dell xps 15, gnome desktop. what can i do,check? i'm not so experienced, usually there are no problems.
Re: No emacs source files in Debian testing?
Charles Curley writes: > On Wed, 5 Oct 2022 08:40:14 -0400 > Haines Brown wrote: > >> With an upgrade to testing, I get this warning when I load emacs: >> >> Warning (comp): Cannot look-up eln file as no source file was found >> for /home/haines/.emacs.d/elisp/ibus.elc > > Judging by the location (in your user directory) and by the fact that > searching with apt-file on Bullseye turns up neither ibus.elc nor > ibus.el, I don't think that ibus.elc or its source file, ibus.el is in > Bullseye, and so likely not in Debian testing. Nor did I find anything > by searching for an emacs ibus package. I suspect you got it from > somewhere else. https://www.emacswiki.org/emacs/IBusMode I suspect you > did a manual installation. > https://www.emacswiki.org/emacs/IBusMode#h5o-4 > > >> >> I gather that with emacs version 28 the ibus.el source file is no >> longer installed, although it must found if the compiled ibus.enc >> file is to load. Testing is at 27.1 - 28.1 is in unstable and currently broken. > Emacs can run byte-compiled files without having the source files > handy. Did you mean ibus.elc here? > >> >> I tried to find a testing version of ibus.el but did not succeed. I >> tied to use an old ibus.el file from Jul 2020, but it had obsolete >> functions and so was not usable. >> >> Can I just ignore the warning? If I do does it leave ibus >> non-functional? Should I file a bug report? >> > > The acid test is whether you can run without the source file. I'm > pretty sure you can ignore the warning. I would try it. > > As for filing a bug report, I don't know where you got ibus.elc, so > can't advise you. > -- regards. Thinkpad T60p 2.33Ghz 2GB SXGA+
Re: No emacs source files in Debian testing?
On Wed, 5 Oct 2022 08:40:14 -0400 Haines Brown wrote: > With an upgrade to testing, I get this warning when I load emacs: > > Warning (comp): Cannot look-up eln file as no source file was found > for /home/haines/.emacs.d/elisp/ibus.elc Judging by the location (in your user directory) and by the fact that searching with apt-file on Bullseye turns up neither ibus.elc nor ibus.el, I don't think that ibus.elc or its source file, ibus.el is in Bullseye, and so likely not in Debian testing. Nor did I find anything by searching for an emacs ibus package. I suspect you got it from somewhere else. https://www.emacswiki.org/emacs/IBusMode I suspect you did a manual installation. https://www.emacswiki.org/emacs/IBusMode#h5o-4 > > I gather that with emacs version 28 the ibus.el source file is no > longer installed, although it must found if the compiled ibus.enc > file is to load. Emacs can run byte-compiled files without having the source files handy. Did you mean ibus.elc here? > > I tried to find a testing version of ibus.el but did not succeed. I > tied to use an old ibus.el file from Jul 2020, but it had obsolete > functions and so was not usable. > > Can I just ignore the warning? If I do does it leave ibus > non-functional? Should I file a bug report? > The acid test is whether you can run without the source file. I'm pretty sure you can ignore the warning. I would try it. As for filing a bug report, I don't know where you got ibus.elc, so can't advise you. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
No emacs source files in Debian testing?
With an upgrade to testing, I get this warning when I load emacs: Warning (comp): Cannot look-up eln file as no source file was found for /home/haines/.emacs.d/elisp/ibus.elc I gather that with emacs version 28 the ibus.el source file is no longer installed, although it must found if the compiled ibus.enc file is to load. I tried to find a testing version of ibus.el but did not succeed. I tied to use an old ibus.el file from Jul 2020, but it had obsolete functions and so was not usable. Can I just ignore the warning? If I do does it leave ibus non-functional? Should I file a bug report? -- Haines Brown /"\ \ / ASCII Ribbon Campaign Xagainst HTML e-mail / \
debian testing and cannot change the display picture on gnome
Hello there , I moved to debian and I cannot change the display picture that also showing on gdm . What I do excactly . opening the settings > users > unlock the permissions > and then I choose my picture . is there any other way even with commoand line ? -- Klearchos-Angelos Gkountras jema...@cryptolab.net
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
On 2/25/22 17:34, Karel Gardas wrote: hardware: amd64 + radeon R5? 230 + 2 monitors connected. One connected to DVI, one to VGA. Monitor connected to VGA is on the left and rotated to the portrait position. - what I do to crash is: - start Settings - search for 'disp' - select Display Configuration node - move VGA monitor from right to left - select rotation on left monitor (rotate 90 clockwise) - hit 'Apply' button ^ and right after hitting Apply I get crash. IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from right to left, X11 are able to survive! If I do *NOT* move VGA monitor from right to left, but just rotate it, I will get again immediate crash. Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 230 GPU. I've also verified that while being logged into KDE following command: $ xrandr --output VGA-0 --rotate left crashes X11 server and I'm back into SDDM login window. I tested this to remove any doubt if KDE framework here (thorough display config) is the culprit or not. Now, I'm pretty confident that this issue happened last week (7 days) or so since this is my debian testing and I've been using it more recently hence also updating every using day. The question is: where to report that to get some fix? Thanks, Karel
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
Him you could try to diable compositing to work around problems with the graphics driver. And you can report a bug at bugs.debian.org (you should first do some more investigation about which component causes the problem.) On 2022-02-25 17:34 UTC+0100, Karel Gardas wrote: > > Hi Cindy, > > you helped a lot. Indeed, I've moved all dot files and folders into > backup and even problematic user is able to log in. > > However, first configuration step brings X11 to the knees, crashing and > then I'm seeing login windows again. So I guess this is the real culprit > of what happened on problematic user. The step to duplicate is this: > > hardware: amd64 + radeon R5? 230 + 2 monitors connected. One connected > to DVI, one to VGA. Monitor connected to VGA is on the left and rotated > to the portrait position. > > - what I do to crash is: > - start Settings > - search for 'disp' > - select Display Configuration node > - move VGA monitor from right to left > - select rotation on left monitor (rotate 90 clockwise) > - hit 'Apply' button > > ^ and right after hitting Apply I get crash. > > IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from > right to left, X11 are able to survive! If I do *NOT* move VGA monitor > from right to left, but just rotate it, I will get again immediate crash. > > Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 > 230 GPU. > > Question: is there any forum where should I report this conclusion to > get attention of the X11 packagers/developers? > > Thanks! > Karel > > > > On 2/25/22 16:56, Cindy Sue Causey wrote: >> On 2/25/22, Karel Gardas wrote: >>> On 2/25/22 13:29, Christian Britz wrote: Hello Karel, please try it with a temporary clean profile. >>> >>> thanks for the idea, indeed after creating a random new and clean user >>> and attempt to log into the Plasma (X11) session I went in well. >>> >>> On my problematic user I tried to rename some .cache and .config dirs to >>> remove possibility of corrupted config but this still does not help. >>> >>> Do you have any idea where everywhere KDE stores its bits of data? Ref >>> to web page describing this will be enough so I can debug the issue and >>> find the culprit behind this issue... >> >> >> When I'd encounter something like this, one of the things that worked >> for me was to rename (dot)Xauthority in the user's home directory. My >> memory is that the file would be recreated during a (FINALLY) >> successful login. >> >> If that doesn't work, how I tripped over that was by going into the >> file manager (Thunar in XFCE4) and sorting files by newest modified >> dates. That hinted at what files might have been most recently touched >> and thus might be a possible culprit. >> >> Good luck! >> >> Cindy :) > -- http://www.cb-fraggle.de
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
Hi Cindy, you helped a lot. Indeed, I've moved all dot files and folders into backup and even problematic user is able to log in. However, first configuration step brings X11 to the knees, crashing and then I'm seeing login windows again. So I guess this is the real culprit of what happened on problematic user. The step to duplicate is this: hardware: amd64 + radeon R5? 230 + 2 monitors connected. One connected to DVI, one to VGA. Monitor connected to VGA is on the left and rotated to the portrait position. - what I do to crash is: - start Settings - search for 'disp' - select Display Configuration node - move VGA monitor from right to left - select rotation on left monitor (rotate 90 clockwise) - hit 'Apply' button ^ and right after hitting Apply I get crash. IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from right to left, X11 are able to survive! If I do *NOT* move VGA monitor from right to left, but just rotate it, I will get again immediate crash. Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 230 GPU. Question: is there any forum where should I report this conclusion to get attention of the X11 packagers/developers? Thanks! Karel On 2/25/22 16:56, Cindy Sue Causey wrote: On 2/25/22, Karel Gardas wrote: On 2/25/22 13:29, Christian Britz wrote: Hello Karel, please try it with a temporary clean profile. thanks for the idea, indeed after creating a random new and clean user and attempt to log into the Plasma (X11) session I went in well. On my problematic user I tried to rename some .cache and .config dirs to remove possibility of corrupted config but this still does not help. Do you have any idea where everywhere KDE stores its bits of data? Ref to web page describing this will be enough so I can debug the issue and find the culprit behind this issue... When I'd encounter something like this, one of the things that worked for me was to rename (dot)Xauthority in the user's home directory. My memory is that the file would be recreated during a (FINALLY) successful login. If that doesn't work, how I tripped over that was by going into the file manager (Thunar in XFCE4) and sorting files by newest modified dates. That hinted at what files might have been most recently touched and thus might be a possible culprit. Good luck! Cindy :)
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
On 2/25/22, Karel Gardas wrote: > On 2/25/22 13:29, Christian Britz wrote: >> Hello Karel, >> >> please try it with a temporary clean profile. >> > > thanks for the idea, indeed after creating a random new and clean user > and attempt to log into the Plasma (X11) session I went in well. > > On my problematic user I tried to rename some .cache and .config dirs to > remove possibility of corrupted config but this still does not help. > > Do you have any idea where everywhere KDE stores its bits of data? Ref > to web page describing this will be enough so I can debug the issue and > find the culprit behind this issue... When I'd encounter something like this, one of the things that worked for me was to rename (dot)Xauthority in the user's home directory. My memory is that the file would be recreated during a (FINALLY) successful login. If that doesn't work, how I tripped over that was by going into the file manager (Thunar in XFCE4) and sorting files by newest modified dates. That hinted at what files might have been most recently touched and thus might be a possible culprit. Good luck! Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
Hello Christian, thanks for the idea, indeed after creating a random new and clean user and attempt to log into the Plasma (X11) session I went in well. On my problematic user I tried to rename some .cache and .config dirs to remove possibility of corrupted config but this still does not help. Do you have any idea where everywhere KDE stores its bits of data? Ref to web page describing this will be enough so I can debug the issue and find the culprit behind this issue... Thanks a lot! Karel On 2/25/22 13:29, Christian Britz wrote: Hello Karel, please try it with a temporary clean profile. Regards, Christian On 2022-02-25 13:12 UTC+0100, Karel Gardas wrote: Hello, I'm using debian testing so not sure if this is the right ML, but after Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma. I simply log into, seeing KDE progress gear and then it returns back to login. My .xsession errors shows that KDE complains about connection to X server claiming perhaps this died. Anybody seen this? Is there any procedure how to better debug and report such issue? Thanks! Karel
Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
Hello Karel, please try it with a temporary clean profile. Regards, Christian On 2022-02-25 13:12 UTC+0100, Karel Gardas wrote: > > Hello, > > I'm using debian testing so not sure if this is the right ML, but after > Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma. > I simply log into, seeing KDE progress gear and then it returns back to > login. My .xsession errors shows that KDE complains about connection to > X server claiming perhaps this died. > > Anybody seen this? Is there any procedure how to better debug and report > such issue? > > Thanks! > Karel > -- http://www.cb-fraggle.de
After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)
Hello, I'm using debian testing so not sure if this is the right ML, but after Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma. I simply log into, seeing KDE progress gear and then it returns back to login. My .xsession errors shows that KDE complains about connection to X server claiming perhaps this died. Anybody seen this? Is there any procedure how to better debug and report such issue? Thanks! Karel
Re: Debian testing is very slow on statup (boot), after upgrade to bookworm
On 16/11/2021 16:40, Marcelo Laia wrote: Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] vendor: Dell driver: amdgpu v: kernel bus-ID: 03:00.0 I guess problem is here. You have no hardware acceleration. Or you using wrong GPU. Or system is trying to use both and conflict occurs. Disable one of them (in BIOS?) and use only one. Also, provide /var/log/Xorg.0.log file, let's see if there are any errors. Also looked at your system repositories. For some reason, you decided to use bookworm system (Debian 12). With experimental repository. VirtualBox from Debian 10. "QGIS" from Debian 11. Docker from Debian 10. And so on.. What a mess. I am surprised your system actually works. You need to fix this, before you do anything else. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Debian testing is very slow on statup (boot), after upgrade to bookworm
Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 4000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Dell Vostro 3470 driver: ath9k v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: IF-ID-1: docker0 state: down mac: Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 3-1.5:7 Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: Drives: Local Storage: total: 931.51 GiB used: 1.39 TiB (152.6%) ID-1: /dev/sda vendor: Seagate model: ST1000LM014-1EJ164 size: 931.51 GiB temp: 34 C Partition: ID-1: / size: 38.89 GiB used: 31.17 GiB (80.1%) fs: ext4 dev: /dev/sda2 ID-2: /boot/efi size: 475.1 MiB used: 3.4 MiB (0.7%) fs: vfat dev: /dev/sda1 ID-3: /home size: 869.84 GiB used: 694.98 GiB (79.9%) fs: ext4 dev: /dev/sda4 ID-4: /home//Private size: 869.84 GiB used: 694.98 GiB (79.9%) fs: ecryptfs source: ERR-102 Swap: ID-1: swap-1 type: partition size: 7.45 GiB used: 14.1 MiB (0.2%) dev: /dev/sda3 Sensors: System Temperatures: cpu: 51.0 C mobo: N/A gpu: amdgpu temp: 52.0 C Fan Speeds (RPM): cpu: 4300 Repos: Packages: 4200 Active apt repos in: /etc/apt/sources.list 1: deb http://deb.debian.org/debian/ testing main non-free contrib 2: deb-src http://deb.debian.org/debian/ testing main non-free contrib 3: deb http://deb.debian.org/debian/ testing-updates main contrib non-free 4: deb-src http://deb.debian.org/debian/ testing-updates main contrib non-free 5: deb http://security.debian.org/debian-security testing-security main contrib non-free 6: deb-src http://security.debian.org/debian-security testing-security main contrib non-free 7: deb http://deb.debian.org/debian/ unstable main non-free contrib 8: deb-src http://deb.debian.org/debian/ unstable main non-free contrib 9: deb http://deb.debian.org/debian/ stable main non-free contrib 10: deb-src http://deb.debian.org/debian/ stable main non-free contrib 11: deb http://deb.debian.org/debian/ experimental main non-free contrib 12: deb-src http://deb.debian.org/debian/ experimental non-free contrib 13: deb http://ftp.de.debian.org/debian stretch main 14: deb [trusted=yes] http://www.openprinting.org/download/printdriver/debian/ lsb3.2 main contrib main-nonfree 15: deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian buster contrib 16: deb [trusted=yes] https://cinelerra-gg.org/download/pkgs/debian10 buster main 17: deb https://qgis.org/ubuntu bullseye main Active apt repos in: /etc/apt/sources.list.d/docker.list 1: deb [arch=amd64] https://download.docker.com/linux/debian buster stable Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main 2: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main No active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list Active apt repos in: /etc/apt/sources.list.d/mono-official-stable.list 1: deb https://download.mono-project.com/repo/debian stable-buster main 2: deb https://download.mono-project.com/repo/debian buster main Active apt repos in: /etc/apt/sources.list.d/spotify.list 1: deb http://repository.spotify.com stable non-free Active apt repos in: /etc/apt/sources.list.d/teams.list 1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main Info: Processes: 257 Uptime: 8h 26m Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 Shell: Bash v: 5.1.8 inxi: 3.3.07 systemd-analyze Startup finished in 5.040s (kernel) + 1min 16.605s (userspace) = 1min 21.646s graphical.target reached after 1min 16.145s in userspace systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 16.145s └─multi-user.target @1min 16.145s └─plymouth-quit-wait.service @24.172s +51.972s └─systemd-user-sessions.service @23.975s +193ms └─network.target @23.931s └─NetworkManager.service @20.702s +3.228s └─dbus.service @20.699s └─basic.target @20.674s └─sockets.target @20.674s └─docker.socket @20.650s +22ms └─sysinit.target @20.443s └─systemd-timesyncd.service @20.342s +100ms └─systemd-tmpfiles-setup.service @20.027s +269ms └─systemd-journal-flush.service @2.898s +17.102s └─systemd-journald.service @2.545s +335ms └─systemd-journald.socket @2.474s └─system.slice @2.436s └─-.slice @2.436s cat /var/log/boot.log /dev/s
Looking for Brasero testers on Debian Testing for bug 998718
Hi, i am looking for volunteers with up-to-date Debian Testing, a CD/DVD/BD burner, Brasero, and the willingness to reboot after bug 998718 struck. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718 indicates that a DVD drive ASUS DRW-24D5MT gets disconnected from the kernel when Brasero tries to write a Debian netinst ISO to a CD-RW medium. The drive then gets reconnected with another device file (probably /dev/sr1) which becomes target of the /dev/cdrom link and works. But the old device file (/dev/sr0) does not vanish and lures software into using it, which then fails with a kernel error that indicates a bad connection to the drive. Only rebooting resolves this mess. The bug is only observed with Brasero on Testing. K3B, wodim and xorriso burn CD-RW without spoiling the relation of kernel and drive. Brasero does not cause the problem if run on Debian Stable. My question is whether this happens with other drives too, i.e. whether the ASUS firmware has a particular stake in the bug. Please send answers to 998...@bugs.debian.org Cc: mauro.sacche...@gmail.com Have a nice day :) Thomas
Re: Packages with upgradable origin but kept back: Debian testing: guile-2.2-libs
On Mon, 17 May 2021 09:36:03 -0500 David Wright wrote: > So I'd look for any non-bullseye holdover packages, and > particlarly any that depend directly or indirectly on > libgc1c2, probably via guile 2.2. Interesting, thank you. I ran apt-cache rdepends guile-2.2-libs /bullseye on orca (fresh install of Bullseye) and iorich (upgraded from Buster). The difference is that on iorich, gnucash is in the output. I have gnucash 1:3.4-1+b10 on iorich, gnucash 1:4.4-1 on orca. Both versions of gnucash have the same dependency for guile: ...guile-3.0-libs,... guile-3.0 | guile-2.2 | guile-2.0,... So why did the upgrade not upgrade gnucash? According to https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#upgrading-full, ["apt full-upgrade"] will perform a complete upgrade of the system, installing the newest available versions of all packages, and resolving all possible dependency changes between packages in different releases. If necessary, it will install some new packages (usually new library versions, or renamed packages), and remove any conflicting obsoleted packages. But the man page for apt says: upgrade (apt-get(8)) upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. *If an upgrade for a package requires the removal of an installed package the upgrade for this package isn't performed.* full-upgrade (apt-get(8)) full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole. (*emphasis added*) With gnucash already installed, if I run "apt install gnucash" I get a long list of packages to be installed, many of which are not already installed in one form or another. It also reports: The following packages will be REMOVED: libgc1c2 Indeed, upgrading gnucash solved that question. So that explains why guile and gnucash weren't upgraded. I wonder how many other programs weren't upgraded. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Packages with upgradable origin but kept back: Debian testing: guile-2.2-libs
On Mon 17 May 2021 at 07:16:21 (-0600), Charles Curley wrote: > I upgraded a laptop from Buster to Bullseye recently. I had unattended > upgrades running, and have kept it running since. I have gotten the > following in the unattended upgrades report since: > > Packages with upgradable origin but kept back: > Debian testing: > guile-2.2-libs > > root@iorich:/etc/apt# apt list --upgradable -a > Listing... Done > guile-2.2-libs/testing 2.2.7+1-5.4 amd64 [upgradable from: 2.2.4+1-2+deb10u1] > guile-2.2-libs/now 2.2.4+1-2+deb10u1 amd64 [installed,upgradable to: > 2.2.7+1-5.4] > > root@iorich:/etc/apt# Well, it wouldn't surprise me if you've still got some buster (or foreign) software that depends on an old version of guile. For example, I've a program, running on buster, that uses guile 1.8 and python 2.4 (but it does include their support in its tarball). > Meanwhile, on another AMD64 machine with a fresh installation of > Bullseye: > > root@orca:~# pre guile > guile-2.2-libs2.2.7+1-5.4 amd64 > guile-3.0 3.0.5-2 amd64 > guile-3.0-libs3.0.5-2 amd64 > root@orca:~# > > And on a i686 machine with a fresh installation of Bullseye: > > root@grissom:~# pre guile > guile-2.2-libs2.2.7+1-5.4 i386 > root@grissom:~# > > > If I try installing guile-3.0 on the first machine, iorich, I get: > > root@iorich:/etc/apt# apt install guile-3.0 > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > The following additional packages will be installed: > guile-2.2-libs guile-3.0-libs libgc1 > Suggested packages: > guile-3.0-doc > The following packages will be REMOVED: > libgc1c2 > The following NEW packages will be installed: > guile-3.0 guile-3.0-libs libgc1 > The following packages will be upgraded: > guile-2.2-libs > 1 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. > Need to get 6,431 kB/11.7 MB of archives. > After this operation, 53.4 MB of additional disk space will be used. > Do you want to continue? [Y/n] n > Abort. > root@iorich:/etc/apt# So I'd look for any non-bullseye holdover packages, and particlarly any that depend directly or indirectly on libgc1c2, probably via guile 2.2. Cheers, David.
Packages with upgradable origin but kept back: Debian testing: guile-2.2-libs
I upgraded a laptop from Buster to Bullseye recently. I had unattended upgrades running, and have kept it running since. I have gotten the following in the unattended upgrades report since: Packages with upgradable origin but kept back: Debian testing: guile-2.2-libs root@iorich:/etc/apt# apt list --upgradable -a Listing... Done guile-2.2-libs/testing 2.2.7+1-5.4 amd64 [upgradable from: 2.2.4+1-2+deb10u1] guile-2.2-libs/now 2.2.4+1-2+deb10u1 amd64 [installed,upgradable to: 2.2.7+1-5.4] root@iorich:/etc/apt# Meanwhile, on another AMD64 machine with a fresh installation of Bullseye: root@orca:~# pre guile guile-2.2-libs 2.2.7+1-5.4 amd64 guile-3.0 3.0.5-2 amd64 guile-3.0-libs 3.0.5-2 amd64 root@orca:~# And on a i686 machine with a fresh installation of Bullseye: root@grissom:~# pre guile guile-2.2-libs 2.2.7+1-5.4 i386 root@grissom:~# If I try installing guile-3.0 on the first machine, iorich, I get: root@iorich:/etc/apt# apt install guile-3.0 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: guile-2.2-libs guile-3.0-libs libgc1 Suggested packages: guile-3.0-doc The following packages will be REMOVED: libgc1c2 The following NEW packages will be installed: guile-3.0 guile-3.0-libs libgc1 The following packages will be upgraded: guile-2.2-libs 1 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 6,431 kB/11.7 MB of archives. After this operation, 53.4 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. root@iorich:/etc/apt# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Firefox and Citrix on Debian Testing
Semih Ozlem wrote: > Just out of curiosity, does one have to be in an organization that has a > contract with citrix to be able to use citrix products or is it available > for individual use? If you are willing to pay the huge amount of money for a Citrix infrastructure, you can of course use it as an individual. S° -- Sigmentation fault. Core dumped.
Re: Firefox and Citrix on Debian Testing
Just out of curiosity, does one have to be in an organization that has a contract with citrix to be able to use citrix products or is it available for individual use? For your question Aaron, the following link https://docs.citrix.com/en-us/citrix-workspace-app-for-linux/system-requirements.html has some requirements listed. Maybe it would help. Aaron Elmquist , 20 Şub 2021 Cmt, 17:45 tarihinde şunu yazdı: > I am on debian testing. I installed the latest citrix workspace client > from here: > > > https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html > - amd64 bit version. > > This seemed to work fine except firefox no longer downloaded content > (chrome did) and syslogd was throwing errors. > > Removing the icaclient from the system seems to have resolved the issue. > > some of the error messages from the /var/log/syslog > Feb 18 13:29:42 debian citrix-chrome[7962]: Failed to connect with logd. > Feb 18 13:29:42 debian citrix-AppProtectionService[697]: Failed to connect > with logd. > Feb 18 13:29:42 debian citrix-kded5[2284]: Failed to connect with logd. > Feb 18 13:29:42 debian citrix-kactivitymanagerd[2465]: Failed to connect > with logd. > > Basically they are all saying that citrix cannot connect to logd. > > Also I did not install anything beyond just the client - did not configure > citrix for any remote desktop. > > Wondering if this is just broken on testing, or are there other packages I > need to install or workarounds available. > > Thanks, > Aaron >
Re: Firefox and Citrix on Debian Testing
On Sat, Feb 20, 2021, 8:51 AM Dan Ritter wrote: > Aaron Elmquist wrote: > > I am on debian testing. I installed the latest citrix workspace client > > from here: > > > > > https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html > > - amd64 bit version. > > > > This seemed to work fine except firefox no longer downloaded content > > (chrome did) and syslogd was throwing errors. > > > > Removing the icaclient from the system seems to have resolved the issue. > > > > some of the error messages from the /var/log/syslog > > Feb 18 13:29:42 debian citrix-chrome[7962]: Failed to connect with logd. > > Feb 18 13:29:42 debian citrix-AppProtectionService[697]: Failed to > connect > > with logd. > > Feb 18 13:29:42 debian citrix-kded5[2284]: Failed to connect with logd. > > Feb 18 13:29:42 debian citrix-kactivitymanagerd[2465]: Failed to connect > > with logd. > > > > Basically they are all saying that citrix cannot connect to logd. > > > > Also I did not install anything beyond just the client - did not > configure > > citrix for any remote desktop. > > > > Wondering if this is just broken on testing, or are there other packages > I > > need to install or workarounds available. > > Have you asked Citrix to support the product that they are delivering to > you? > No, I did not. You're right. I should start there. Incidentally, what you are describing is "syslog is showing me > the errors", not "syslogd was throwing errors" which implies > that syslogd is not functioning properly. > Correct. I don't believe there is an issue with syslogd and wrote that incorrectly. -dsr- > >
Re: Firefox and Citrix on Debian Testing
Aaron Elmquist wrote: > I am on debian testing. I installed the latest citrix workspace client > from here: > > https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html > - amd64 bit version. > > This seemed to work fine except firefox no longer downloaded content > (chrome did) and syslogd was throwing errors. > > Removing the icaclient from the system seems to have resolved the issue. > > some of the error messages from the /var/log/syslog > Feb 18 13:29:42 debian citrix-chrome[7962]: Failed to connect with logd. > Feb 18 13:29:42 debian citrix-AppProtectionService[697]: Failed to connect > with logd. > Feb 18 13:29:42 debian citrix-kded5[2284]: Failed to connect with logd. > Feb 18 13:29:42 debian citrix-kactivitymanagerd[2465]: Failed to connect > with logd. > > Basically they are all saying that citrix cannot connect to logd. > > Also I did not install anything beyond just the client - did not configure > citrix for any remote desktop. > > Wondering if this is just broken on testing, or are there other packages I > need to install or workarounds available. Have you asked Citrix to support the product that they are delivering to you? Incidentally, what you are describing is "syslog is showing me the errors", not "syslogd was throwing errors" which implies that syslogd is not functioning properly. -dsr-
Firefox and Citrix on Debian Testing
I am on debian testing. I installed the latest citrix workspace client from here: https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html - amd64 bit version. This seemed to work fine except firefox no longer downloaded content (chrome did) and syslogd was throwing errors. Removing the icaclient from the system seems to have resolved the issue. some of the error messages from the /var/log/syslog Feb 18 13:29:42 debian citrix-chrome[7962]: Failed to connect with logd. Feb 18 13:29:42 debian citrix-AppProtectionService[697]: Failed to connect with logd. Feb 18 13:29:42 debian citrix-kded5[2284]: Failed to connect with logd. Feb 18 13:29:42 debian citrix-kactivitymanagerd[2465]: Failed to connect with logd. Basically they are all saying that citrix cannot connect to logd. Also I did not install anything beyond just the client - did not configure citrix for any remote desktop. Wondering if this is just broken on testing, or are there other packages I need to install or workarounds available. Thanks, Aaron
Re: Firefox over JACK in Debian Testing
On 10/1/20, Olivier Humbert wrote: >> On 6/6/2020 11:25 PM, riveravaldez wrote: > >> AFAIK Firefox lacks JACK support (in the sense that you can start >> JACK and then Firefox and then, automatically, all I/O audio-ports >> Firefox generated, appear as available JACK connections, let's say) > > Join in if you like to do so > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844688 . > > Cheers, > Olivier Thanks, Olivier. That seems like a 'requested feature', but I'm failing to see what the issue is (there's a repetition of "please do", but not an elaboration on the matter). I guess it would be useful to know at least what's the reason why official firefox-esr package is not being compiled with JACK support enabled. Thanks again, cheers.
Re: Firefox over JACK in Debian Testing
On 6/6/2020 11:25 PM, riveravaldez wrote: AFAIK Firefox lacks JACK support (in the sense that you can start JACK and then Firefox and then, automatically, all I/O audio-ports Firefox generated, appear as available JACK connections, let's say) Join in if you like to do so https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844688 . Cheers, Olivier
Re: Firefox over JACK in Debian Testing
On 6/8/20, Christopher David Howie wrote: > On 6/6/2020 11:25 PM, riveravaldez wrote: >> Hi, here's the thing: >> >> AFAIK Firefox lacks JACK support (in the sense that you can start >> JACK and then Firefox and then, automatically, all I/O audio-ports >> Firefox generated, appear as available JACK connections, let's say) >> >> Is there any Debian package that can serve this purpose? > > If JACK is already running when pulseaudio starts, pulseaudio will > create a single JACK sink and JACK source that redirects audio to/from a > matching JACK source/sink. > > I then use the following script to create additional sinks in PA that > each have an independent source in JACK: (...) Thanks a lot, Chris, I've finally found the time to try this, and these are the steps that seems (at least for now) to be working: 0. An installed and functional JACK and PulseAudio. 1. Install package: pulseaudio-module-jack 2. Close anything that requires PA. 3. Kill PA: $ pulseaudio --kill 4. Start JACK (in my case, through qjackctl). 5. Then start Firefox (this should start PA). 6. Then load (as seen in [1]) the source/sink modules[2] to have I/O audio through PA administered/connected by JACK (these will appear in its Connections): $ pactl load-module module-jack-sink/source 7. Use JACK as usual. 8. After stop/exit JACK remember to kill/restart PA in order to it to retake control of Audio Device. There are other methods (some more complex) there [3] and there [4]. I couldn't find these steps or Chris' explanations neither in [5] nor in [6]: should it be added? Let me know what you think. Thanks a lot to everybody for all your useful and kind help. I had no idea before this that this was possible and so easily achievable. Best regards. [1] https://wiki.debian.org/PulseAudio#Echo_test:_hearing_the_microphone [2] https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#jackconnectivity [3] https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_PulseOnJack [4] https://wiki.archlinux.org/index.php/PulseAudio/Examples#PulseAudio_through_JACK [5] https://wiki.debian.org/PulseAudio [6] https://wiki.debian.org/JACK
Re: Can one install packages from Parrot or Kali on Debian testing? (Was: Re: Hi :))
Parrot and Kali both have their own support lists. Kali, in particular, use a modified Debian testing as the basis of their rolling release but modify kernels and other packages. In general, people would suggest not mixing Debian stable and Debian testing. Using packages from another Debian-derived distribution risks creating a "FrankenDebian" that you can't control and can't readily fix without removing significant numbers of packages: this also applies to Ubuntu and, especially, Ubuntu PPAs mixed with Debian. All the very best Andy C https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiczpvn0-DrAhWTA2MBHUrsDXwQFjAAegQIARAB&url=https%3A%2F%2Fwiki.debian.org%2FDontBreakDebian&usg=AOvVaw2uYNQvEqW0ju-bH_QNSw08 On Fri, Sep 11, 2020 at 5:35 AM Andy Smith wrote: > Hi Richard, > > Your question is one of user support but you've sent it to the > debian-project list, which is about the Debian project itself and > not for asking user questions. So, I have directed replies to the > correct place which is debian-user. > > On Thu, Sep 10, 2020 at 04:14:35PM -0400, richard loomis wrote: > > I have a question using debian 10 i noticed ive upgraded till theres no > > more using testing, > > Use "testing" is probably for advanced users, but the question you > ask below about mixing in things that aren't Debian suggests you are > maybe not that familiar with Debian. Be careful! > > > when i add parrot os repos and kali linux repos theres tons of > > upgrades knowing there using testing also, Is it safe to upgrade > > debian 10 with there repos? > > No. You should not mix in things that aren't Debian into Debian > without knowing exactly what you are doing. None of those things > (Parrot, Kali) are designed to be installed on a Debian system. You > will very likely break your entire system doing this. It may even > appear to work for a while, but will break later in mysterious ways. > > See https://wiki.debian.org/DontBreakDebian for more details. > > In general, upgrading to newer versions of packages for no reason > other than that they exist is not a good practice. You should have a > reason for wanting a newer package than what exists in Debian > testing. I recommend that if you do have such a need for specific > newer packages, you install them individually from upstream > following upstream's instructions. > > Cheers, > Andy > >
Can one install packages from Parrot or Kali on Debian testing? (Was: Re: Hi :))
Hi Richard, Your question is one of user support but you've sent it to the debian-project list, which is about the Debian project itself and not for asking user questions. So, I have directed replies to the correct place which is debian-user. On Thu, Sep 10, 2020 at 04:14:35PM -0400, richard loomis wrote: > I have a question using debian 10 i noticed ive upgraded till theres no > more using testing, Use "testing" is probably for advanced users, but the question you ask below about mixing in things that aren't Debian suggests you are maybe not that familiar with Debian. Be careful! > when i add parrot os repos and kali linux repos theres tons of > upgrades knowing there using testing also, Is it safe to upgrade > debian 10 with there repos? No. You should not mix in things that aren't Debian into Debian without knowing exactly what you are doing. None of those things (Parrot, Kali) are designed to be installed on a Debian system. You will very likely break your entire system doing this. It may even appear to work for a while, but will break later in mysterious ways. See https://wiki.debian.org/DontBreakDebian for more details. In general, upgrading to newer versions of packages for no reason other than that they exist is not a good practice. You should have a reason for wanting a newer package than what exists in Debian testing. I recommend that if you do have such a need for specific newer packages, you install them individually from upstream following upstream's instructions. Cheers, Andy
Lost sound upgrading to kernel 5.7.0-1-amd64 on Debian testing
Just a heads up: yesterday, I decided to upgrade all of my packages. I know: what a silly thing to do when having the computer working is critical for work. Anyway... My system is mostly Debian testing (with a couple of bits from sid). In upgrading, I lost sound completely. I spent a few hours trying to sort this out, playing with pulseaudio, alsamixer, ... Eventually, I rebooted with the older kernel (version 5.6.0-1-amd64) which sorted (some) things out. I have sound again although only through my HDMI display, not through the headphones, but that's enough for now. -- Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid
Re: my Laptop feels 5 times faster after today's Debian/testing update!!!
On Wednesday, 1 July 2020 23:16:47 CEST Marco Möller wrote: > !THANK YOU! Thank You Debian Developers! > > My Laptop feels 5 times faster after today's Debian/testing update!!! > > My old laptop running on Debian/testing since the update from today > flies like a rocket!! It before was fine, I didn't feel any need to > upgrade the hardware. Concerning its responsiveness I attributed small > delays to my WiFi connection being slow because of being far away from > the WLAN router, and the rest because of running my OS off from an > USB-Stick. But now I see three superb effects: all apps in general > appear to start up much faster, like at triple speed, contents in the > RIOT messenger and in the Firefox browser load at least at fivefold > speed, and all screen rendering, bang, it simply bursts onto the screen! > > It is most likely the fortunate combination of various packages which > all became updated today! > > It will not be the kernel. The kernel upgrade from today is not the one > addressing the version which is actively running. For the web browsing > (download and rendering of pages) there could be an effect by the > upgrade to Firefox v78. But this would not explain the significantly > increased speed observed also for all other applications. > I am pretty sure that these two updates have boosted my felt system > speed significantly: > modemmanager > mesa-vulkan-drivers > > /var/log/apt/history.log > Start-Date: 2020-07-01 21:55:32 > Commandline: apt upgrade > Requested-By: (1000) > Install: linux-image-5.7.0-1-amd64:amd64 (5.7.6-1, automatic) > Upgrade: libegl-mesa0:amd64 (20.1.1-1, 20.1.2-1), libglapi-mesa:amd64 > (20.1.1-1, 20.1.2-1), flatpak:amd64 (1.6.3-1, 1.8.0-1), > libxatracker2:amd64 (20.1.1-1, 20.1.2-1), libgbm1:amd64 (20.1.1-1, > 20.1.2-1), fonts-firacode:amd64 (5.2+dfsg1-1, 5.2+dfsg1-2), > linux-image-amd64:amd64 (5.6.14-2, 5.7.6-1), libmm-glib0:amd64 > (1.12.10-0.2, 1.14.0-0.1), libgl1-mesa-dri:amd64 (20.1.1-1, 20.1.2-1), > firefox:amd64 (77.0-1, 78.0-1), modemmanager:amd64 (1.12.10-0.2, > 1.14.0-0.1), libglibmm-2.4-1v5:amd64 (2.64.2-1, 2.64.2-2), > libhunspell-1.7-0:amd64 (1.7.0-2+b1, 1.7.0-3), mesa-vulkan-drivers:amd64 > (20.1.1-1, 20.1.2-1), libglx-mesa0:amd64 (20.1.1-1, 20.1.2-1) > End-Date: 2020-07-01 21:57:49 > > > GREAT! GREAT! GREAT! GREAT! > !THANK YOU! Thank You Debian Developers! > Marco The support for your graphic chip must be improved with the upgrade signature.asc Description: This is a digitally signed message part.
my Laptop feels 5 times faster after today's Debian/testing update!!!
!THANK YOU! Thank You Debian Developers! My Laptop feels 5 times faster after today's Debian/testing update!!! My old laptop running on Debian/testing since the update from today flies like a rocket!! It before was fine, I didn't feel any need to upgrade the hardware. Concerning its responsiveness I attributed small delays to my WiFi connection being slow because of being far away from the WLAN router, and the rest because of running my OS off from an USB-Stick. But now I see three superb effects: all apps in general appear to start up much faster, like at triple speed, contents in the RIOT messenger and in the Firefox browser load at least at fivefold speed, and all screen rendering, bang, it simply bursts onto the screen! It is most likely the fortunate combination of various packages which all became updated today! It will not be the kernel. The kernel upgrade from today is not the one addressing the version which is actively running. For the web browsing (download and rendering of pages) there could be an effect by the upgrade to Firefox v78. But this would not explain the significantly increased speed observed also for all other applications. I am pretty sure that these two updates have boosted my felt system speed significantly: modemmanager mesa-vulkan-drivers /var/log/apt/history.log Start-Date: 2020-07-01 21:55:32 Commandline: apt upgrade Requested-By: (1000) Install: linux-image-5.7.0-1-amd64:amd64 (5.7.6-1, automatic) Upgrade: libegl-mesa0:amd64 (20.1.1-1, 20.1.2-1), libglapi-mesa:amd64 (20.1.1-1, 20.1.2-1), flatpak:amd64 (1.6.3-1, 1.8.0-1), libxatracker2:amd64 (20.1.1-1, 20.1.2-1), libgbm1:amd64 (20.1.1-1, 20.1.2-1), fonts-firacode:amd64 (5.2+dfsg1-1, 5.2+dfsg1-2), linux-image-amd64:amd64 (5.6.14-2, 5.7.6-1), libmm-glib0:amd64 (1.12.10-0.2, 1.14.0-0.1), libgl1-mesa-dri:amd64 (20.1.1-1, 20.1.2-1), firefox:amd64 (77.0-1, 78.0-1), modemmanager:amd64 (1.12.10-0.2, 1.14.0-0.1), libglibmm-2.4-1v5:amd64 (2.64.2-1, 2.64.2-2), libhunspell-1.7-0:amd64 (1.7.0-2+b1, 1.7.0-3), mesa-vulkan-drivers:amd64 (20.1.1-1, 20.1.2-1), libglx-mesa0:amd64 (20.1.1-1, 20.1.2-1) End-Date: 2020-07-01 21:57:49 GREAT! GREAT! GREAT! GREAT! !THANK YOU! Thank You Debian Developers! Marco
Re: Firefox over JACK in Debian Testing
On 6/6/2020 11:25 PM, riveravaldez wrote: Hi, here's the thing: AFAIK Firefox lacks JACK support (in the sense that you can start JACK and then Firefox and then, automatically, all I/O audio-ports Firefox generated, appear as available JACK connections, let's say) Is there any Debian package that can serve this purpose? I have a JACK setup that runs all audio through Ardour so I can perform compression and EQ either system-wide or per-application. I accomplish this by using pulseaudio. If JACK is already running when pulseaudio starts, pulseaudio will create a single JACK sink and JACK source that redirects audio to/from a matching JACK source/sink. I then use the following script to create additional sinks in PA that each have an independent source in JACK: -- #!/bin/sh exec pactl load-module module-jack-sink \ client_name=pulse_sink_"$1" \ connect=no \ channels=2 -- Run like "./make-jack-sink music" which gives me a "music" PA sink connected to the "music" JACK source. You don't automatically get a JACK port per audio stream, but you can make as many separate PA sinks as your system can handle and use the PA volume control application to switch audio streams between different PA sinks (and therefore JACK sources). Then you can wire everything up on the JACK side, as usual. -- Chris Howie http://www.chrishowie.com http://en.wikipedia.org/wiki/User:Crazycomputers If you correspond with me on a regular basis, please read this document: http://www.chrishowie.com/email-preferences/ PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5 IMPORTANT INFORMATION/DISCLAIMER This document should be read only by those persons to whom it is addressed. If you have received this message it was obviously addressed to you and therefore you can read it. Additionally, by sending an email to ANY of my addresses or to ANY mailing lists to which I am subscribed, whether intentionally or accidentally, you are agreeing that I am "the intended recipient," and that I may do whatever I wish with the contents of any message received from you, unless a pre-existing agreement prohibits me from so doing. This overrides any disclaimer or statement of confidentiality that may be included on your message.
Re: Firefox over JACK in Debian Testing
On Du, 07 iun 20, 00:25:30, riveravaldez wrote: > > By other side, I've seen in Arch a different approach: using a JACK > plugin for ALSA and ad hoc configuration file to make kind of a > "bridge" that sends I/O audio through JACK. It works fine.[4] > Is it possible to do something similar in Debian (testing)? ... > [4] > https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#Playing_nice_with_ALSA It should work after some "translation" for Debian, e.g. the package names in Arch may not correspond 1:1 to Debian's *binary* package names, but are likely to correspond to the Debian *source* package names. An easy way to find out the Debian binary package name is to look at the Tracker page: https://tracker.debian.org/alsa-plugins Binaries: libasound2-plugins Hope this helps, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Firefox over JACK in Debian Testing
On Sun, Jun 07, 2020 at 12:25:30AM -0300, riveravaldez wrote: > Hi, here's the thing: > > AFAIK Firefox lacks JACK support (in the sense that you can start JACK > and then Firefox and then, automatically, all I/O audio-ports Firefox > generated, appear as available JACK connections, let's say), even > more: that seems to be a design/development decision - meaning: will > not change. No idea about JACK, but, FWIW Debian still builds its Firefox with ALSA enabled [1] (I don't know about the situation in testing, though). You can find our about your browser's compile config by invoking about:buildconfig (about:support may be of interest, too). That said, I never got Firefox to play nice with ALSA. There are many hints strewn around in the intra tubes, like reducing the syscall sandbox's security level and things. No idea about whether my fingers are too fat or whether the non-Pulse audio code in FF has rotted beyond the point. In the end, I resorted to apulse (packaged in Debian), which just pretends to be a pulse lib but then goes and talks directly to ALSA. Works a charm. Ugly details on request :-) Cheers [1] That's the version I'm referring to: firefox-esr/stable,now 68.8.0esr-1~deb10u1 amd64 [installed] -- tomás signature.asc Description: Digital signature
Firefox over JACK in Debian Testing
Hi, here's the thing: AFAIK Firefox lacks JACK support (in the sense that you can start JACK and then Firefox and then, automatically, all I/O audio-ports Firefox generated, appear as available JACK connections, let's say), even more: that seems to be a design/development decision - meaning: will not change.[1] It's possible to build Firefox with such support - some people do it - but Mozilla will not do.[2,3] Is there any Debian package that can serve this purpose? By other side, I've seen in Arch a different approach: using a JACK plugin for ALSA and ad hoc configuration file to make kind of a "bridge" that sends I/O audio through JACK. It works fine.[4] Is it possible to do something similar in Debian (testing)? In short, I'm looking for the best way to play I/O Firefox audio through/over JACK. Any help to solve this I will thank it very much. Regards! [1] https://askubuntu.com/questions/923990/jack-pulseaudio-and-firefox-enable-jack-for-firefox-in-the-near-future [2] http://www.zamaudio.com/?p=1580 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=783733 [4] https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#Playing_nice_with_ALSA
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Lu, 30 mar 20, 12:47:45, Martin wrote: > On Sun, 29 Mar 2020 at 20:59, Andrei POPESCU wrote: > > > > > For my apt preferences I had: > > > > > > Package: * > > > Pin: release a=testing > > > Pin-Priority: 650 > > > > > > Package: * > > > Pin: release a=unstable > > > Pin-Priority: 600 > > > > > > To be honest back in the day when I did that, I struggled to really > > > understand it. My intention was to have the system take packages from > > > unstable and if a package is not available there then from testing. > > > Does it even do that? > > > > It does the exact opposite, because in your configuration testing has > > higher priority. > > > > For what you wrote above you don't need any pinning, just have both > > unstable and testing your sources.list. > > Great, thank you very much for clearing this up for me! Problems solved! To explain, apt by default will always prefer the newest version it can find in your repositories. Pins are only necessary if for some reason you want to override that. If you intend to stay on unstable it is safe to remove the pins completely and still retain testing in sources.list (having testing in sources.list when running unstable is a good idea anyway). As for bugs in individual packages, you need a negative pin (any value below 0) for the specific version with the bug. That way a newer version (hopefully without the bug) will be installed automatically. If you are using aptitude there is also 'forbid-version' which does the same. A pin with a value > 1000 (any value) will force apt to keep the package at that version, regardless of what updates are available. As you found out, this will block regular updates that explicitly require a newer version of the pinned package. One has to decide on a case-by-case basis what is more important (pin or updates). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Sun, 29 Mar 2020 at 20:59, Andrei POPESCU wrote: > According to your 'apt policy' you also had repositories configured for > Skype and Docker. Did you remove those as well? They remain, just were in their own files. > > > For my apt preferences I had: > > > > Package: * > > Pin: release a=testing > > Pin-Priority: 650 > > > > Package: * > > Pin: release a=unstable > > Pin-Priority: 600 > > > > To be honest back in the day when I did that, I struggled to really > > understand it. My intention was to have the system take packages from > > unstable and if a package is not available there then from testing. > > Does it even do that? > > It does the exact opposite, because in your configuration testing has > higher priority. > > For what you wrote above you don't need any pinning, just have both > unstable and testing your sources.list. Great, thank you very much for clearing this up for me! Problems solved! Best regards, Marty
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Du, 29 mar 20, 16:40:03, Martin wrote: > On Sun, 29 Mar 2020 at 13:33, Andrei POPESCU wrote: > > > > > Pinned packages: > > > libpython3.8-minimal -> 3.8.2-1 with priority -3 > > > libcrypt1 -> 1:4.4.15-1 with priority -3 > > > libcrypt1:i386 -> 1:4.4.15-1 with priority -3 > > > powertop -> 2.10-1+b1 with priority 3 > > > openssh-server -> 1:8.1p1-1 with priority 3 > > > grub-efi-amd64 -> 2.04-3 with priority 3 > > > isc-dhcp-client -> 4.4.1-2 with priority 3 > > > > Why did you add these pins? > > When I did the upgrade (the big one after 4 months) apt-listbugs > warned about a number of bugs and I felt safer to pin those packages. > > > > > > I tried to unpin these packages: > > > > > > sudo apt-mark unhold libcrypt1 > > > > Pins are not holds... > > Thank you, this was not obvious to me. I now deleted the pins from > /etc/apt/preferences.d/apt-listbugs and rerun update+upgrade and that > seems to have fixed my problems. > \o/ Ok. > > Your system is a... complex mixture that is very easy to break. > > You refer to my apt policy I assume and/or my apt sources list? I > would be happy to simplify it. In my sources.list I now only have > unstable: > > deb http://deb.debian.org/debian/ unstable main non-free contrib > deb-src http://deb.debian.org/debian/ unstable main non-free contrib According to your 'apt policy' you also had repositories configured for Skype and Docker. Did you remove those as well? > For my apt preferences I had: > > Package: * > Pin: release a=testing > Pin-Priority: 650 > > Package: * > Pin: release a=unstable > Pin-Priority: 600 > > To be honest back in the day when I did that, I struggled to really > understand it. My intention was to have the system take packages from > unstable and if a package is not available there then from testing. > Does it even do that? It does the exact opposite, because in your configuration testing has higher priority. For what you wrote above you don't need any pinning, just have both unstable and testing your sources.list. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Sun, 29 Mar 2020 at 13:33, Andrei POPESCU wrote: > > So you have a multiarch (amd64 and i386) system, with amd64 repositories > for Skype and Docker. > > Why do you need i386? I'm guessing you might have some locally installed > packages as well. Please show also the output of > > aptitude search '~o' > aptitude search '~b' I would not bot able to answer it, maybe the scanner driver. I do use skype and docker. Anyway, here the output: sudo aptitude search '~o' Warning: Invalid locale (please review locale settings, this might lead to problems later): locale::facet::_S_create_c_locale name not valid i libapt-inst2.0 - deb package format runtime library i libapt-pkg5.0 - package management runtime library i libdns-export1104 - Exported DNS Shared Library i libip4tc0 - netfilter libip4tc library i libip6tc0 - netfilter libip6tc library i libisc-export1100 - Exported ISC Shared Library i libjson-c3 - JSON manipulation library - shared library i libprocps7 - library for accessing process information from /proc i libreadline7- GNU readline and history libraries, run-time libraries i A linux-image-5.2.0-3-amd64 - Linux 5.2 for 64-bit PCs (signed) i net.downloadhelper.coapp- Video DownloadHelper companion app i perl-modules-5.28 - Core Perl modules i scangearmp-common - ScanGear MP for Linux. i scangearmp-mg2500series - ScanGear MP for Linux. sudo aptitude search '~b' Warning: Invalid locale (please review locale settings, this might lead to problems later): locale::facet::_S_create_c_locale name not valid downloadhelper is part of a firefox extension. "locale" is one of the packages that is currently broken (update: could reinstall and it is working now) > > > Pinned packages: > > libpython3.8-minimal -> 3.8.2-1 with priority -3 > > libcrypt1 -> 1:4.4.15-1 with priority -3 > > libcrypt1:i386 -> 1:4.4.15-1 with priority -3 > > powertop -> 2.10-1+b1 with priority 3 > > openssh-server -> 1:8.1p1-1 with priority 3 > > grub-efi-amd64 -> 2.04-3 with priority 3 > > isc-dhcp-client -> 4.4.1-2 with priority 3 > > Why did you add these pins? When I did the upgrade (the big one after 4 months) apt-listbugs warned about a number of bugs and I felt safer to pin those packages. > > > I tried to unpin these packages: > > > > sudo apt-mark unhold libcrypt1 > > Pins are not holds... Thank you, this was not obvious to me. I now deleted the pins from /etc/apt/preferences.d/apt-listbugs and rerun update+upgrade and that seems to have fixed my problems. \o/ > > Your system is a... complex mixture that is very easy to break. You refer to my apt policy I assume and/or my apt sources list? I would be happy to simplify it. In my sources.list I now only have unstable: deb http://deb.debian.org/debian/ unstable main non-free contrib deb-src http://deb.debian.org/debian/ unstable main non-free contrib For my apt preferences I had: Package: * Pin: release a=testing Pin-Priority: 650 Package: * Pin: release a=unstable Pin-Priority: 600 To be honest back in the day when I did that, I struggled to really understand it. My intention was to have the system take packages from unstable and if a package is not available there then from testing. Does it even do that? Thank you a lot for your help! Marty
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Du, 29 mar 20, 12:37:39, Martin wrote: > > Here is apt policy: > > Package files: > 100 /var/lib/dpkg/status > release a=now > 500 https://repo.skype.com/deb stable/main amd64 Packages > release o=. stable,a=stable,n=stable,l=. stable,c=main,b=amd64 > origin repo.skype.com > 600 http://deb.debian.org/debian unstable/contrib i386 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=i386 > origin deb.debian.org > 600 http://deb.debian.org/debian unstable/contrib amd64 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64 > origin deb.debian.org > 600 http://deb.debian.org/debian unstable/non-free i386 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=i386 > origin deb.debian.org > 600 http://deb.debian.org/debian unstable/non-free amd64 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64 > origin deb.debian.org > 600 http://deb.debian.org/debian unstable/main i386 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=i386 > origin deb.debian.org > 600 http://deb.debian.org/debian unstable/main amd64 Packages > release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/contrib i386 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=contrib,b=i386 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/contrib amd64 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=contrib,b=amd64 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/non-free i386 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=non-free,b=i386 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/non-free amd64 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=non-free,b=amd64 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/main i386 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=main,b=i386 > origin deb.debian.org > 650 http://deb.debian.org/debian testing/main amd64 Packages > release o=Debian,a=testing,n=bullseye,l=Debian,c=main,b=amd64 > origin deb.debian.org > 500 https://download.docker.com/linux/debian buster/stable amd64 Packages > release o=Docker,a=buster,l=Docker CE,c=stable,b=amd64 > origin download.docker.com So you have a multiarch (amd64 and i386) system, with amd64 repositories for Skype and Docker. Why do you need i386? I'm guessing you might have some locally installed packages as well. Please show also the output of aptitude search '~o' aptitude search '~b' > Pinned packages: > libpython3.8-minimal -> 3.8.2-1 with priority -3 > libcrypt1 -> 1:4.4.15-1 with priority -3 > libcrypt1:i386 -> 1:4.4.15-1 with priority -3 > powertop -> 2.10-1+b1 with priority 3 > openssh-server -> 1:8.1p1-1 with priority 3 > grub-efi-amd64 -> 2.04-3 with priority 3 > isc-dhcp-client -> 4.4.1-2 with priority 3 Why did you add these pins? > I tried to unpin these packages: > > sudo apt-mark unhold libcrypt1 Pins are not holds... Your system is a... complex mixture that is very easy to break. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
I commented out the testing repository in my apt sources list and ran apt update/upgrade/clean/autoremove. It helped e.g. with updating firefox from 69 to 74 but other packages are still stuck. apt list --upgradable libc-bin/unstable 2.30-4 amd64 [upgradable from: 2.29-2] libc6/unstable 2.30-4 amd64 [upgradable from: 2.29-2] libc6/unstable 2.30-4 i386 [upgradable from: 2.29-2] libpam-systemd/unstable 245.2-1 amd64 [upgradable from: 244.3-1] libruby2.5/unstable 2.5.7-1+b1 amd64 [upgradable from: 2.5.7-1] libselinux1/unstable 3.0-1+b2 amd64 [upgradable from: 3.0-1+b1] libsystemd0/unstable 245.2-1 amd64 [upgradable from: 244.3-1] libudev1/unstable 245.2-1 amd64 [upgradable from: 244.3-1] login/unstable 1:4.8.1-1 amd64 [upgradable from: 1:4.7-2] passwd/unstable 1:4.8.1-1 amd64 [upgradable from: 1:4.7-2] ruby-debian/unstable 0.3.10+b3 amd64 [upgradable from: 0.3.10+b2] ruby-sqlite3/unstable 1.4.2-2+b2 amd64 [upgradable from: 1.4.2-2+b1] ruby-unf-ext/unstable 0.0.7.6-1+b2 amd64 [upgradable from: 0.0.7.6-1+b1] ruby-unicode/unstable 0.4.4-2+b11 amd64 [upgradable from: 0.4.4-2+b10] ruby-xmlparser/unstable 0.7.3-3+b4 amd64 [upgradable from: 0.7.3-3+b3] ruby/unstable 1:2.7 amd64 [upgradable from: 1:2.5.7.1] shim-unsigned/unstable 15+1533136590.3beb971-8 amd64 [upgradable from: 15+1533136590.3beb971-7] systemd/unstable 245.2-1 amd64 [upgradable from: 244.3-1] udev/unstable 245.2-1 amd64 [upgradable from: 244.3-1] whois/unstable 5.5.6 amd64 [upgradable from: 5.5.2] On Sun, 29 Mar 2020 at 07:56, Andrei POPESCU wrote: > > On Sb, 28 mar 20, 23:59:17, Martin wrote: > > > > I have a debian bullseye/testing machine on a 2017 HP i7 machine that > > I used daily for many months but was not running since end of November > > 2019. I upgraded everything with apt update + dist-upgrade + > > autoremove + clean this week. > > [...] > > > This is my apt sources list: > > > > deb http://deb.debian.org/debian/ testing main non-free contrib > > deb-src http://deb.debian.org/debian/ testing main non-free contrib > > deb http://deb.debian.org/debian/ unstable main non-free contrib > > deb-src http://deb.debian.org/debian/ unstable main non-free contrib > > With this sources list you appear to be running unstable, not testing. > > Please show also the output of 'apt policy'. > > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
Hello Andrei, thank you for your time! > With this sources list you appear to be running unstable, not testing. > Please show also the output of 'apt policy'. > sorry, yes I am usually happy to be on "unstable". Here is apt policy: Package files: 100 /var/lib/dpkg/status release a=now 500 https://repo.skype.com/deb stable/main amd64 Packages release o=. stable,a=stable,n=stable,l=. stable,c=main,b=amd64 origin repo.skype.com 600 http://deb.debian.org/debian unstable/contrib i386 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=i386 origin deb.debian.org 600 http://deb.debian.org/debian unstable/contrib amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64 origin deb.debian.org 600 http://deb.debian.org/debian unstable/non-free i386 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=i386 origin deb.debian.org 600 http://deb.debian.org/debian unstable/non-free amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64 origin deb.debian.org 600 http://deb.debian.org/debian unstable/main i386 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=i386 origin deb.debian.org 600 http://deb.debian.org/debian unstable/main amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64 origin deb.debian.org 650 http://deb.debian.org/debian testing/contrib i386 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=contrib,b=i386 origin deb.debian.org 650 http://deb.debian.org/debian testing/contrib amd64 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=contrib,b=amd64 origin deb.debian.org 650 http://deb.debian.org/debian testing/non-free i386 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=non-free,b=i386 origin deb.debian.org 650 http://deb.debian.org/debian testing/non-free amd64 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=non-free,b=amd64 origin deb.debian.org 650 http://deb.debian.org/debian testing/main i386 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=main,b=i386 origin deb.debian.org 650 http://deb.debian.org/debian testing/main amd64 Packages release o=Debian,a=testing,n=bullseye,l=Debian,c=main,b=amd64 origin deb.debian.org 500 https://download.docker.com/linux/debian buster/stable amd64 Packages release o=Docker,a=buster,l=Docker CE,c=stable,b=amd64 origin download.docker.com Pinned packages: libpython3.8-minimal -> 3.8.2-1 with priority -3 libcrypt1 -> 1:4.4.15-1 with priority -3 libcrypt1:i386 -> 1:4.4.15-1 with priority -3 powertop -> 2.10-1+b1 with priority 3 openssh-server -> 1:8.1p1-1 with priority 3 grub-efi-amd64 -> 2.04-3 with priority 3 isc-dhcp-client -> 4.4.1-2 with priority 3 I tried to unpin these packages: sudo apt-mark unhold libcrypt1 E: Can't select installed nor candidate version from package 'libcrypt1' as it has neither of them E: No packages found sudo -i root@lemon:~# echo libcrypt1 install | dpkg --set-selections dpkg: warning: package not in status nor available database at line 1: libcrypt1 dpkg: warning: found unknown packages; this might mean the available database is outdated, and needs to be updated through a frontend method; please see the FAQ <https://wiki.debian.org/Teams/Dpkg/FAQ> Running apt update makes no difference to that. Best regards, Marty On Sun, 29 Mar 2020 at 07:56, Andrei POPESCU wrote: > > On Sb, 28 mar 20, 23:59:17, Martin wrote: > > > > I have a debian bullseye/testing machine on a 2017 HP i7 machine that > > I used daily for many months but was not running since end of November > > 2019. I upgraded everything with apt update + dist-upgrade + > > autoremove + clean this week. > > [...] > > > This is my apt sources list: > > > > deb http://deb.debian.org/debian/ testing main non-free contrib > > deb-src http://deb.debian.org/debian/ testing main non-free contrib > > deb http://deb.debian.org/debian/ unstable main non-free contrib > > deb-src http://deb.debian.org/debian/ unstable main non-free contrib > > With this sources list you appear to be running unstable, not testing. > > Please show also the output of 'apt policy'. > > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser
Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
On Sb, 28 mar 20, 23:59:17, Martin wrote: > > I have a debian bullseye/testing machine on a 2017 HP i7 machine that > I used daily for many months but was not running since end of November > 2019. I upgraded everything with apt update + dist-upgrade + > autoremove + clean this week. [...] > This is my apt sources list: > > deb http://deb.debian.org/debian/ testing main non-free contrib > deb-src http://deb.debian.org/debian/ testing main non-free contrib > deb http://deb.debian.org/debian/ unstable main non-free contrib > deb-src http://deb.debian.org/debian/ unstable main non-free contrib With this sources list you appear to be running unstable, not testing. Please show also the output of 'apt policy'. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye
Dear all, I have a debian bullseye/testing machine on a 2017 HP i7 machine that I used daily for many months but was not running since end of November 2019. I upgraded everything with apt update + dist-upgrade + autoremove + clean this week. I can't exactly say how but while everything appeared fine initially I now struggle with having a partially working system. Something with a very fundamental library seems to have created a unsolvable dependency situation and I can't get out of it. I think it started with libcrypt1 that was dependency but could not be found. My question is foremost if I can get out of it myself and how or if it is due to some package currently not available (in Incoming as one error message suggests) and I just have to wait? Maybe my sources list does not make sense? apt list --upgradable Listing... Done firefox/unstable 74.0-1 amd64 [upgradable from: 69.0.1-1] libc-bin/testing 2.30-2 amd64 [upgradable from: 2.29-2] libc6/testing 2.30-2 amd64 [upgradable from: 2.29-2] libc6/testing 2.30-2 i386 [upgradable from: 2.29-2] libruby2.5/testing,unstable 2.5.7-1+b1 amd64 [upgradable from: 2.5.7-1] login/testing,unstable 1:4.8.1-1 amd64 [upgradable from: 1:4.7-2] passwd/testing,unstable 1:4.8.1-1 amd64 [upgradable from: 1:4.7-2] whois/testing,unstable 5.5.6 amd64 [upgradable from: 5.5.2] When I do: sudo apt install whois The following packages have unmet dependencies: whois : Depends: libcrypt1 (>= 1:4.1.0) but it is not installable sudo apt install locales libc-bin Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc-bin : Depends: libc6 (> 2.30) but 2.29-2 is to be installed sudo apt install libc6 libcrypt1 Reading package lists... Done Building dependency tree Reading state information... Done Package libcrypt1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libcrypt1:i386 This is my apt sources list: deb http://deb.debian.org/debian/ testing main non-free contrib deb-src http://deb.debian.org/debian/ testing main non-free contrib deb http://deb.debian.org/debian/ unstable main non-free contrib deb-src http://deb.debian.org/debian/ unstable main non-free contrib By trying to remove and reinstall I ended up losing some important packages, so I made it worse already. The general advice to clean/dist-upgrade/install -f does not get me any further. Any advice appreciated! Best regards, Marty.
debian/testing: plasma5 - systemsettings is crashing
Hi folks, some weeks ago I told about several issues with instability of the x-server when using plasma on my EEEPC (32-bit/graphics card: Intel I945) Now things are getting worse! First of all, after an upgrade it appeared, that the compositor is not working any more. When I tried to reactivate it in the systemsettings, I discovered, that when chosing the plugin for these settings, systemsettings is crashing. But not only this one is crashing, whenever I tried to call a module, systemsetings is crashing. Below I am attaching the output, hope this helps and make things clearer. Any help is welcome, and thank you very much for your help! Best regards Hans -- snip - Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb2116780 (LWP 14756))] Thread 6 (Thread 0xa30cab40 (LWP 14776)): #0 0xb7f9fbad in __kernel_vsyscall () #1 0xb6186403 in __GI___libc_read (nbytes=16, buf=0xa30ca06c, fd=17) at ../ sysdeps/unix/sysv/linux/read.c:26 #2 __GI___libc_read (fd=17, buf=0xa30ca06c, nbytes=16) at ../sysdeps/unix/ sysv/linux/read.c:24 #3 0xb42f6be5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb42ae214 in g_main_context_check () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #5 0xb42ae686 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb42ae824 in g_main_context_iteration () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #7 0xb670cf9c in QEventDispatcherGlib::processEvents(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb66afb5e in QEventLoop::exec(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb64ecef1 in QThread::exec() () from /lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #10 0xb56cb1af in ?? () from /lib/i386-linux-gnu/libQt5Qml.so.5 #11 0xb64ee34b in ?? () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb4ba2fb9 in start_thread (arg=) at pthread_create.c:486 #13 0xb6197d86 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 5 (Thread 0xaaff4b40 (LWP 14765)): #0 0xb7f9fbad in __kernel_vsyscall () #1 0xb618d873 in __GI___poll (timeout=-1, nfds=1, fds=0x2871d80) at ../ sysdeps/unix/sysv/linux/poll.c:29 #2 __GI___poll (fds=0x2871d80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/ linux/poll.c:26 #3 0xb42bdb50 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb42ae6e3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb42ae824 in g_main_context_iteration () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #6 0xb670cf9c in QEventDispatcherGlib::processEvents(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb66afb5e in QEventLoop::exec(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb64ecef1 in QThread::exec() () from /lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #9 0xb56cb1af in ?? () from /lib/i386-linux-gnu/libQt5Qml.so.5 #10 0xb64ee34b in ?? () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb4ba2fb9 in start_thread (arg=) at pthread_create.c:486 #12 0xb6197d86 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 4 (Thread 0xad354b40 (LWP 14761)): #0 0xb42ac6ab in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb42adb35 in g_main_context_prepare () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #2 0xb42ae5f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb42ae824 in g_main_context_iteration () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #4 0xb670cf9c in QEventDispatcherGlib::processEvents(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb66afb5e in QEventLoop::exec(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb64ecef1 in QThread::exec() () from /lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #7 0xb56cb1af in ?? () from /lib/i386-linux-gnu/libQt5Qml.so.5 #8 0xb64ee34b in ?? () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb4ba2fb9 in start_thread (arg=) at pthread_create.c:486 #10 0xb6197d86 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 3 (Thread 0xb0490b40 (LWP 14759)): #0 0xb7f9fbad in __kernel_vsyscall () #1 0xb7f9fad1 in __vdso_clock_gettime () #2 0xb61a5641 in __GI___clock_gettime (clock_id=1, tp=0xb048ff84) at ../ sysdeps/unix/clock_gettime.c:115 #3 0xb670c6bc in ?? () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb670ae72 in QTimerInfoList::updateCurrentTime() () from /lib/i386-linux- gnu/sse2/libQt5Core.so.5 #5 0xb670b384 in QTimerInfoList::timerWait(timespec&) () from /lib/i386- linux-gnu/sse2/libQt5Core.so.5 #6 0xb670cce9 in ?? () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb42adbb2 in g_main_context_prepare () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #8 0xb42ae5f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb42ae824 in g_main_context_iteration () from /lib/i386-linux-gnu/ libglib-2.0.so.0 #10 0xb670cf9c in QEventDispatcherGlib::processEvents(QFlags) () from /lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb66afb5e in Q
Re: Several issues with Xorg in debian/testing
Am Donnerstag, 6. Februar 2020, 09:26:53 CET schrieb Andrei POPESCU: Hi Andrei, no, if the update did not install Wayland secretly, Wayland is not installed. I rechecked on my EEEPC - NO, there is no Wayland. But thanks to the pointment. Best Hans > On Mi, 05 feb 20, 12:42:16, Hans wrote: > > Dear list, > > > > since almost 3 months I am noticing several issues, with xserver based > > applications. > > [...] > > > You may think, this is a plasma problem, however, I believe, it appears > > especially in plasma, because plasma needs the most ressources. > > Could it be that you are running Wayland instead of Xorg? > > Kind regards, > Andrei signature.asc Description: This is a digitally signed message part.
Re: Several issues with Xorg in debian/testing
On Mi, 05 feb 20, 12:42:16, Hans wrote: > Dear list, > > since almost 3 months I am noticing several issues, with xserver based > applications. [...] > You may think, this is a plasma problem, however, I believe, it appears > especially in plasma, because plasma needs the most ressources. Could it be that you are running Wayland instead of Xorg? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Several issues with Xorg in debian/testing
Hi, Hans I've had similar problems for the past couple years with 2 laptops with Intel graphics. The problem is that someone on the kernel team was jealous of the pretty Windows startup screens so they HAD to bring them to Linux. So they put graphic mode setting in the kernel. So now the graphic situation in Linux is like - if you consider your graphic driver as Rembrandt painting pretty pictures on your screen, the kernel is now like an 8 year old boy with attention deficit disorder and a paintbrush, putting splotches and stripes on the canvas. You can reduce the effects by modifying the /etc/default/grub file. Before you modify the file, be sure you are familiar with logging in as root in tty1 thru tty6 and re-editing the file with vi or nano to get X back. Look at https://ubuntuforums.org/showthread.php?t=1613132 and https://askubuntu.com/questions/618169. Good luck Jim Daldry Raleigh NC On 2/5/20, Hans wrote: > Dear list, > > since almost 3 months I am noticing several issues, with xserver based > applications. > > Please notice, that all the following described issues appeared all at once > > and all on different systems. Please also note, that the different systems I > am > mentioning are 32-bit as well as 64-bit and got different graphic cards. > > And please note, that on all systems the same package versions are running. > > The issues: > > 1. On my EEEPC, X is running rather unstable. When hovering the mouse over > > the taskbar, then the window manager is flickering and sometimes > reinitialises > within a second. This is mostly seen in plasma (which of course needs most > performance), but also appears in LXDE (but quite seldom). > > 2. On my other notebook, which is using a Nvidia graphics card, it appears, > > when plasma is starting while I am in another console (i.e. tty 2), and the > > switch to console 7 (where X is started), then it appears, that letters from > > the description of the icons or in the taskbar are disappeared. But not all, > > only a few. So for example there is not the word "wireshark", but the word > "w r s har ". Also the numbers for the different virtual desktops are gone. > > This issue is not only related to the icon names, but to all text. > > When starting plasma while switched to tty7 this issue never happens. > > You may think, this is a plasma problem, however, I believe, it appears > especially in plasma, because plasma needs the most ressources. > > I would file a bugreport, but I am not exatly sure, which package is > responsible for these issues. Is it X? Plasma? Libs? They all play together, > > but maybe someone did notice these things also. > > Last but not least, it looks like a system problem, as both computers got > very > different hardware - the EEEPC is 32-bit and has a i915 graphics chip, > whilst > the Acer is 64-bit and has a Nvidia GF8600 card. > > Both are running debian/testing. > > Thank you for reading this, and if someone discovered these things, too, I > would be happy this to be confirmed. > > Best regards > > Hans
Several issues with Xorg in debian/testing
Dear list, since almost 3 months I am noticing several issues, with xserver based applications. Please notice, that all the following described issues appeared all at once and all on different systems. Please also note, that the different systems I am mentioning are 32-bit as well as 64-bit and got different graphic cards. And please note, that on all systems the same package versions are running. The issues: 1. On my EEEPC, X is running rather unstable. When hovering the mouse over the taskbar, then the window manager is flickering and sometimes reinitialises within a second. This is mostly seen in plasma (which of course needs most performance), but also appears in LXDE (but quite seldom). 2. On my other notebook, which is using a Nvidia graphics card, it appears, when plasma is starting while I am in another console (i.e. tty 2), and the switch to console 7 (where X is started), then it appears, that letters from the description of the icons or in the taskbar are disappeared. But not all, only a few. So for example there is not the word "wireshark", but the word "w r s har ". Also the numbers for the different virtual desktops are gone. This issue is not only related to the icon names, but to all text. When starting plasma while switched to tty7 this issue never happens. You may think, this is a plasma problem, however, I believe, it appears especially in plasma, because plasma needs the most ressources. I would file a bugreport, but I am not exatly sure, which package is responsible for these issues. Is it X? Plasma? Libs? They all play together, but maybe someone did notice these things also. Last but not least, it looks like a system problem, as both computers got very different hardware - the EEEPC is 32-bit and has a i915 graphics chip, whilst the Acer is 64-bit and has a Nvidia GF8600 card. Both are running debian/testing. Thank you for reading this, and if someone discovered these things, too, I would be happy this to be confirmed. Best regards Hans signature.asc Description: This is a digitally signed message part.
Re: Issue with headset on debian testing
Anton Vorobyov wrote: > > Hi. > > I want to file a bug report, but I am not familiar with sound system in > linux enough to determine which package is to blame. > > So, my issue started only recently. I have a laptop with Debian Testing. > Previously, when I plug in my headset (2x 3.5mm jacks - one for > headphones, one for mic) the system automatically switched to it, both > input and output. After some system update whenever I plug my headset in, > Gnome started showing prompt if I plugged in headphones, headset or > external mic, and according to my choice it configures sound settings. > > The issue is that when I have Headphones selected for output and External > mic for input (which correspond to my headset headphones and mic > correspondingly), sound cannot be played via headset’s headphones. > Whenever I switch input from external mic to built-in laptop mic, sound > from headphones resumes. But it results in me being unable to use the > headset (as I am unable to use either headphones or mic). > > I believe the issue started after an upgrade which involved linux image > update from 5.3.9-3 to 5.4.8-1. I haven’t been able to confirm that as > rolling back to the older kernel version did not fix the issue, though. I > did multiple system updates before final reboot which exposed the issue, > so identifying which update broke it is very hard. > > I have spent some time to rule out PulseAudio as possible cause of the > issue. More details on the issue overall and how I ruled PA out are > available in this thread: > http://forums.debian.net/viewtopic.php?f=6&t=144902 > > I have little understanding on what is involved in the sound system below > PA. ALSA? Kernel? What could be broken and how to debug it? > > Any help is appreaciated. > > Regards, > -av First of all you choose using testing + unstable. Secondly you do not have understanding of all the sub systems. Why not choosing stable then? Regarding the problem my view: PA is mixer layer on top of ALSA and it gives an interface for applications to use the audio system in an easy way. To stop PA relaunching you put in the config file autospawn=no and shut down PA. Then you start PA in the console with verbose output and repeat your use case. Honestly what I think is that if you are connected with 3.5" jacks to line/mic in and line/audio out from the headset could be that the system automatically mutes one input/output in favor to another. >From your description of the problem http://forums.debian.net/viewtopic.php?f=6&t=144902 it looks like it could be also a wrong mapping or configuration within alsa. Then it could be that you might want to look any specific settings for the audio card. For this you could use amixer or aplay. In my opinion it is better to use pavucontrol with PA enabled. I also think it could be some driver settings or udev rule ... hard to say. When I look for your audio card, I get many recent (2019) issues related with this card. Very interesting I found https://blog.kafaiworks.com/posts/arch-linux-audio-setup-on-msi-gp63/ regards
Issue with headset on debian testing
Hi. I want to file a bug report, but I am not familiar with sound system in linux enough to determine which package is to blame. So, my issue started only recently. I have a laptop with Debian Testing. Previously, when I plug in my headset (2x 3.5mm jacks - one for headphones, one for mic) the system automatically switched to it, both input and output. After some system update whenever I plug my headset in, Gnome started showing prompt if I plugged in headphones, headset or external mic, and according to my choice it configures sound settings. The issue is that when I have Headphones selected for output and External mic for input (which correspond to my headset headphones and mic correspondingly), sound cannot be played via headset’s headphones. Whenever I switch input from external mic to built-in laptop mic, sound from headphones resumes. But it results in me being unable to use the headset (as I am unable to use either headphones or mic). I believe the issue started after an upgrade which involved linux image update from 5.3.9-3 to 5.4.8-1. I haven’t been able to confirm that as rolling back to the older kernel version did not fix the issue, though. I did multiple system updates before final reboot which exposed the issue, so identifying which update broke it is very hard. I have spent some time to rule out PulseAudio as possible cause of the issue. More details on the issue overall and how I ruled PA out are available in this thread: http://forums.debian.net/viewtopic.php?f=6&t=144902 I have little understanding on what is involved in the sound system below PA. ALSA? Kernel? What could be broken and how to debug it? Any help is appreaciated. Regards, -av
Re: Best/Proper way to dist-upgrade Debian Testing except the kernel?
On Lu, 09 dec 19, 20:27:28, riveravaldez wrote: > > Just to clarify: How long one could go on upgrading debian-testing > (kernel included) without rebooting? As long as it is acceptable for you to run the system with known security flaws. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Best/Proper way to dist-upgrade Debian Testing except the kernel?
riveravaldez wrote: ... > Hi, thanks a lot for the answers/info. > > Just to clarify: How long one could go on upgrading debian-testing > (kernel included) without rebooting? why would you not want to reboot? if you aren't going to use the upgrades why are you making them? if you think there are too many risks in rebooting then you perhaps should be sticking to stable. every time i start up in the morning i check updates and reboot or restart if checkrestart shows anything is using updated libraries. checkrestart is in package debian-goodies. songbird
Re: Best/Proper way to dist-upgrade Debian Testing except the kernel?
On 12/4/19, songbird wrote: > Sven Hartge wrote: >> riveravaldez wrote: >> >>> Because updating the kernel requires to reboot the system -AFAIK- in >>> many cases I would prefer to 'dist-upgrade' (all packages) except the >>> kernel -until a moment in which I can reboot the system-, so: >> >>> 1. Is this something right/viable/acceptable to do? >> >> You don't *need* to reboot the system the very moment an new kernel is >> installed. Just upgrade all packages including the kernel and reboot >> when it is convenient for you. > > yes, the other thing worth mentioning is how to find > out which versions you have installed to begin with. > > i commonly use dpkg -l with grep to find out so for > the kernel images i would use: > > $ dpkg -l | grep linux-image Hi, thanks a lot for the answers/info. Just to clarify: How long one could go on upgrading debian-testing (kernel included) without rebooting? Thanks again.
Re: Best/Proper way to dist-upgrade Debian Testing except the kernel?
Sven Hartge wrote: > riveravaldez wrote: > >> Because updating the kernel requires to reboot the system -AFAIK- in >> many cases I would prefer to 'dist-upgrade' (all packages) except the >> kernel -until a moment in which I can reboot the system-, so: > >> 1. Is this something right/viable/acceptable to do? > > You don't *need* to reboot the system the very moment an new kernel is > installed. Just upgrade all packages including the kernel and reboot > when it is convenient for you. yes, the other thing worth mentioning is how to find out which versions you have installed to begin with. i commonly use dpkg -l with grep to find out so for the kernel images i would use: $ dpkg -l | grep linux-image mainly out of habit. in newer lingo: $ apt list linux-imag* which will show which linux-images are out there and which ones you have installed. songbird
Re: Best/Proper way to dist-upgrade Debian Testing except the kernel?
riveravaldez wrote: > Because updating the kernel requires to reboot the system -AFAIK- in > many cases I would prefer to 'dist-upgrade' (all packages) except the > kernel -until a moment in which I can reboot the system-, so: > 1. Is this something right/viable/acceptable to do? You don't *need* to reboot the system the very moment an new kernel is installed. Just upgrade all packages including the kernel and reboot when it is convenient for you. Grüße, Sven. -- Sigmentation fault. Core dumped.
Best/Proper way to dist-upgrade Debian Testing except the kernel?
Because updating the kernel requires to reboot the system -AFAIK- in many cases I would prefer to 'dist-upgrade' (all packages) except the kernel -until a moment in which I can reboot the system-, so: 1. Is this something right/viable/acceptable to do? 2. Which would be the best/proper way to do it? (I mean, 'apt-get update && apt-get dist-upgrade' for all packages *except* the kernel.) 3. If 'apt-mark hold package' would be the way to do it: which 'package' -exactly- should I mark for hold? Thanks a lot!
Can not active fcitx or scim for Chinese inputing after Debian testing upgrade on 10 Oct 2019
Hi, I upgraded my Debian testing on 10 Oct 2019, and I found that fcitx and scim can not be used. When I press ctrl+Space, the Chinese input UI can not be actived. Who knows what matter it is? And how to resolve it? Thank you very much! Best regards, Gulfstream
Re: Debian testing (buster), "vfat not found"
On Sb, 12 ian 19, 17:11:11, Dan Marshall wrote: > Hi, first time caller... I know it's been several months... > Originally posted this is Linux Questions' Hardware subforum. Copying and > pasting the tasty bits: > > Trying to mount a thumb drive and an mp3 player under Debian testing > (buster), got a "filesystem vfat not found" message from the automounter. > > Tried "sudo modprobe vfat," got an "operation not permitted." > > Modinfo did find the vfat module, so at least there's that. > > Both the kernel and the vfat module are the same version, 4.19.0-1-amd64. That would be the kernel package *name*. According to snapshot.debian.org there were 3 different versions of that package in the archive: http://snapshot.debian.org/binary/linux-image-4.19.0-1-amd64/ > sudo /sbin/depmod -a /lib/modules/4.19.0-1-amd64/kernel/fs/fat/vfat.ko > depmod: ERROR: Bad version passed > /lib/modules/4.19.0-1-amd64/kernel/fs/fat/vfat.ko > [/code] > > Not sure what that "ERROR: Bad version passed" means, but it looks > important. I would have suggested to purge and reinstall the *package* linux-image-4.19.0-1-amd64, just to make sure there is no mismatch between the kernel and modules. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Hibernation issue with 4.19.0-4-amd64 on Debian testing
G'day I am not subscribed to the list, so I would appreciate being cc'ed on any replies. I have an issue with hibernation on my Lenovo ThinkPad laptop (E531) that runs the Debian testing stream. The default kernel is 4.19.0-4-amd64 and I use the KDE Plasma desktop. The laptop will hibernate once after a fresh start using the default kernel. But the second time, it refuses to hibernate and I have to do a hard reboot. With the other kernel available on the system - as you are all aware, apt retains the latest two kernels for boot purposes - 4.19.0-2-amd64, the behaviour is somewhat different. As with the 4.19.0-4-amd64 kernel, this 4.19.0-2-amd64 kernel also allows the laptop to hibernate once and resume. On the second time, it refuses to hibernate. But if I select the 4.19.0-2-amd64 kernel afresh when I resume from hibernation, the laptop will hibernate without any issue. Otherwise, if I just let it return from hibernation without any intervention, even though the system is using the 4.19.0-2-amd64 kernel, it does not hibernate when I try to put it into this state and I have to do a hard reboot. Has anyone seen this kind of behaviour? Thanks, Sam -- (Sam Varghese)
debian/testing - consoleblank on i386 too short
Hi folks, you might remember, I was searching for the reason, that on tty1 -5 the blank time is too short. After I checked all the variable, now I believe, it is a bug in the kernel itself. As I tested with two identical configured systems (one is amd64, the other i386) and confirmed all configurations are identical (including /etc/console-tools/config), I checked cat /sys/module/kernel/parameters/consoleblank On the working system, I got "600" (which is 10 minutes) and the non working system I got "60" (which is only 1 minute). I also tried "consoleblank=600" as kernel parameter, but with no success, just as the kernel does ignore the setting. It looks like the kernel itself got the problem, as when setting "setterm -blank 60", then it is working until next boot. The only differnce between both systems is just the kernel. Ah, and of course I checked the initscript, which is reading from /etc/console-tools/config, here also both systems are identical. Maybe there was a typo in the i386-kernel when built? 60 instead of 600? As far as I read, the blanktime is hardcoded in the kernel. The running kernel here is 4.19.0-4-i386. Would be nice, if someone could confirm my issue before I file a bugreport. Again: This issue appeares only on my i386-system and appeared suddenly after an upgrade. Best regards Hans signature.asc Description: This is a digitally signed message part.
Debian testing (buster), "vfat not found"
Hi, first time caller... Originally posted this is Linux Questions' Hardware subforum. Copying and pasting the tasty bits: Trying to mount a thumb drive and an mp3 player under Debian testing (buster), got a "filesystem vfat not found" message from the automounter. Tried "sudo modprobe vfat," got an "operation not permitted." Modinfo did find the vfat module, so at least there's that. Both the kernel and the vfat module are the same version, 4.19.0-1-amd64. dmesg did not report anything interesting. I can post a tail or grep for something if somebody asks. I did verify that my user account had access to the mount point. I also repeated the modprobe su-ed as root. Same error message. I verified that the thumbdrive is fat32 (which vfat should handle, if I could get the module to load). Did a cat /proc/devices got what I *think* is a list of numbers associated with all the devices on my system. Not sure how to get the vfat module to cough up what number it's trying to grab. I can post the cat /proc/devices list if anybody asks. [code] sudo /sbin/modprobe -vv vfat modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom logging function 0x5648b5e8ced0 registered insmod /lib/modules/4.19.0-1-amd64/kernel/fs/fat/fat.ko modprobe: INFO: ../libkmod/libkmod-module.c:886 kmod_module_insert_module() Failed to insert module '/lib/modules/4.19.0-1-amd64/kernel/fs/fat/fat.ko': Operation not permitted modprobe: ERROR: could not insert 'vfat': Operation not permitted modprobe: INFO: ../libkmod/libkmod.c:331 kmod_unref() context 0x5648b7d91410 released [/code] [code] sudo /sbin/modprobe -vvv vfat modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom logging function 0x5558b37deed0 registered modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.19.0-1-amd64/modules.dep.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.19.0-1-amd64/modules.alias.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.19.0-1-amd64/modules.symbols.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.19.0-1-amd64/modules.builtin.bin modprobe: DEBUG: ../libkmod/libkmod-module.c:556 kmod_module_new_from_lookup() input alias=vfat, normalized=vfat modprobe: DEBUG: ../libkmod/libkmod-module.c:562 kmod_module_new_from_lookup() lookup modules.dep vfat modprobe: DEBUG: ../libkmod/libkmod.c:574 kmod_search_moddep() use mmaped index 'modules.dep' modname=vfat modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get module name='vfat' found=(nil) modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add 0x5558b4632fe0 key='vfat' modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get module name='fat' found=(nil) modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get module name='fat' found=(nil) modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add 0x5558b46330f0 key='fat' modprobe: DEBUG: ../libkmod/libkmod-module.c:196 kmod_module_parse_depline() add dep: /lib/modules/4.19.0-1-amd64/kernel/fs/fat/fat.ko modprobe: DEBUG: ../libkmod/libkmod-module.c:202 kmod_module_parse_depline() 1 dependencies for vfat modprobe: DEBUG: ../libkmod/libkmod-module.c:583 kmod_module_new_from_lookup() lookup vfat=0, list=0x5558b4632600 modprobe: DEBUG: ../libkmod/libkmod.c:501 lookup_builtin_file() use mmaped index 'modules.builtin' modname=vfat modprobe: DEBUG: ../libkmod/libkmod-module.c:1750 kmod_module_get_initstate() could not open '/sys/module/vfat/initstate': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:1760 kmod_module_get_initstate() could not open '/sys/module/vfat': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=snd_pcsp mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=snd_usb_audio mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=cx88_alsa mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=snd_atiixp_modem mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=snd_intel8x0m mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=snd_via82xx_modem mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=md_mod mod->name=fat mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() modname=bonding mod->name=fat mod->alias=(null)
Re: Warning: Debian/testing full-upgrade removes security packages!
Hi. On Sun, Jul 15, 2018 at 01:02:48PM -0400, Roberto C. Sánchez wrote: > On Sun, Jul 15, 2018 at 06:07:32PM +0200, Hans wrote: > > Am Sonntag, 15. Juli 2018, 17:43:47 CEST schrieb Henrique de Moraes > > Holschuh: > > > > Maybe I was not clear enough. I did not mourn,. that packages are > > dienstalled, > > this may happen in testing. I mourned,m that almost ALL SECURITY related > > packages are deinstalled. And I would have nothing said, if it would have > > been > > one or maybe two, bat ALL most important rootkit watchers? And intrusion > > detection? This was the point. > > The idea that this is part of some conspiracy just seems wrong. There > must be another logical explanation. I'd put my money on some debconf breakage (the only Depends all those packages have at common), but [1] claims that the most recent debconf migration to testing happened a month ago. Next most possible candidate is a perl-base, but if [2] is to be trusted, perl migration to testing was more than a month ago too. So a conspiracy idea does not seem that weird. On the contrary, it would look absolutely hilarious in the light of the news such as [3]. Or it might be broken Debian mirror that OP's using. Reco [1] https://tracker.debian.org/pkg/debconf [2] https://tracker.debian.org/pkg/perl [3] https://linux.slashdot.org/story/18/06/09/052249
Re: Warning: Debian/testing full-upgrade removes security packages!
Henrique de Moraes Hols writes: > Same goes for dist-upgrade. dist-upgrade/full-upgrade will more > aggressively attempt to remove packages than the alternatives > safe-upgrade and upgrade. I always do "upgrade" and look at what did not get upgraded and why. I then sometimes follow with "full-upgrade" and other times just upgrade selected packages. Testing is always consistent but not always complete. Unstable is always complete but not always consistent. Only Stable is both. -- John Hasler jhas...@newsguy.com Elmwood, WI USA
Re: Warning: Debian/testing full-upgrade removes security packages!
On Sun, Jul 15, 2018 at 06:07:32PM +0200, Hans wrote: > Am Sonntag, 15. Juli 2018, 17:43:47 CEST schrieb Henrique de Moraes Holschuh: > > Maybe I was not clear enough. I did not mourn,. that packages are > dienstalled, > this may happen in testing. I mourned,m that almost ALL SECURITY related > packages are deinstalled. And I would have nothing said, if it would have > been > one or maybe two, bat ALL most important rootkit watchers? And intrusion > detection? This was the point. > What you are writing does not make sense. I almost replied to your first message after you posted it, but I had to leave. After researching the packages you mention, they are all currently in testing. That means that the removal would have to be triggered by a package conflict. Even if a package were not in testing, the system would not automatically removed it (unless you explicitly removed packages without a corresponding apt source). Can you post your sources.list and/or sources.list.d/ entries and also your dpkg.log that shows the specific packages being removed? The idea that this is part of some conspiracy just seems wrong. There must be another logical explanation. Regards, -Roberto -- Roberto C. Sánchez
Re: Warning: Debian/testing full-upgrade removes security packages!
Am Sonntag, 15. Juli 2018, 17:43:47 CEST schrieb Henrique de Moraes Holschuh: Maybe I was not clear enough. I did not mourn,. that packages are dienstalled, this may happen in testing. I mourned,m that almost ALL SECURITY related packages are deinstalled. And I would have nothing said, if it would have been one or maybe two, bat ALL most important rootkit watchers? And intrusion detection? This was the point. Best regards Hans > On Sun, 15 Jul 2018, The Wanderer wrote: > > >> be warned: Wheh you do apt full-upgrade, > > > > > > You're in testing: what are you "full-upgrade"-ing to and why? > > > > To testing, of course. > > Eh, I believe the meant that as "why are you using full-upgrade instead > of safe-upgrade or upgrade" (depending on which frontend), which are not > nearly as aggressive at removing packages. > > Same goes for dist-upgrade. dist-upgrade/full-upgrade will more > aggressively attempt to remove packages than the alternatives > safe-upgrade and upgrade. AFAIK, anyway.
Re: Warning: Debian/testing full-upgrade removes security packages!
On Sun, 15 Jul 2018, The Wanderer wrote: > >> be warned: Wheh you do apt full-upgrade, > > > > You're in testing: what are you "full-upgrade"-ing to and why? > > To testing, of course. Eh, I believe the meant that as "why are you using full-upgrade instead of safe-upgrade or upgrade" (depending on which frontend), which are not nearly as aggressive at removing packages. Same goes for dist-upgrade. dist-upgrade/full-upgrade will more aggressively attempt to remove packages than the alternatives safe-upgrade and upgrade. AFAIK, anyway. -- Henrique Holschuh
Re: Warning: Debian/testing full-upgrade removes security packages!
On 2018-07-15 at 10:09, David Wright wrote: > On Sun 15 Jul 2018 at 07:49:36 (+0200), Hans wrote: > >> Hi folks, >> >> be warned: Wheh you do apt full-upgrade, > > You're in testing: what are you "full-upgrade"-ing to and why? To testing, of course. Just because you're running testing doesn't mean the package versions you have installed are the ones currently available from testing. If you last upgraded more than about a day ago, there's a very good chance that one or more of your installed packages has a newer version available in testing now. Running upgrade commands on at least an intermittent basis is just good, normal practice for tracking testing. That said, the nature of testing does sometimes mean that the result is not entirely stable and consistent, so occasionally you get undesired package-removal results such as the ones described in this thread. The solution is generally to either specify explicitly (on the upgrade command line) which packages you want to retain, or wait until whatever dependency-resolution situation led to the problem gets resolved. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Warning: Debian/testing full-upgrade removes security packages!
On Sun 15 Jul 2018 at 07:49:36 (+0200), Hans wrote: > Hi folks, > > be warned: Wheh you do apt full-upgrade, You're in testing: what are you "full-upgrade"-ing to and why? > then most security tools, we rely on, > are deinstallesd. These are rkhunter, chrootkit, autopsy, tripwire, > needrestart and tiger. Also forensics-full and forensics-all are deinstalled > (however, this might have other reasons). > > This is no good behaviour, and it looks for me like the preparation for a > global attack on debian. > > Maybe it is wanted by the maintainers, but to remove suddenly almost all of > the most effective tools looks very, very fishy to me! > > Keep your eyes open, the NSA is everywhere. Cheers, David.
Re: Warning: Debian/testing full-upgrade removes security packages!
On 07/15/2018 02:49 PM, Hans wrote: > be warned: Wheh you do apt full-upgrade, then most security tools, we rely > on, > are deinstallesd. These are rkhunter, chrootkit, autopsy, tripwire, > needrestart and tiger. Also forensics-full and forensics-all are deinstalled > (however, this might have other reasons). Most likely the upgrade is changing packages that are depended on by the packages you mention. Just re-install them. Just examine which packages are being changed, see why apt wants to uninstall, and reinstall if needed. > This is no good behaviour, and it looks for me like the preparation for a > global attack on debian. The extent of the evidence that supports the idea that this is in fact an attack on Debian is just that apt is removing these packages on update. This behavior could be explained by other means, without first jumping to conclusions about NSA interference. "Never attribute to malice that which is adequately explained by stupidity." or, in this case, basically any simpler explanation than "the preparation for a global attack on debian". I believe it would have been more helpful if this had been written as a question on why apt might be removing said packages on upgrade, with more context, instead of spreading FUD on the list.
Warning: Debian/testing full-upgrade removes security packages!
Hi folks, be warned: Wheh you do apt full-upgrade, then most security tools, we rely on, are deinstallesd. These are rkhunter, chrootkit, autopsy, tripwire, needrestart and tiger. Also forensics-full and forensics-all are deinstalled (however, this might have other reasons). This is no good behaviour, and it looks for me like the preparation for a global attack on debian. Maybe it is wanted by the maintainers, but to remove suddenly almost all of the most effective tools looks very, very fishy to me! Keep your eyes open, the NSA is everywhere. Best regards Hans
Re: Debian testing - release number
On Wed 11 Jul 2018 at 11:53:29 (+), Curt wrote: > On 2018-07-10, David Wright wrote: Yes, I wrote a post on 2018-07-10 but you haven't quoted any of it here. > You following up to Woole[d]ge: > > Hmm, I struggle to see the connection between what I asked for and > what you wrote. From your later post, I guess the answer is that > editing /etc/debian_version risks provoking expletives from other > users of the system. > > That said, I do agree with what you wrote. > > So there was an equivocal quality there, Dav[id], as to which of Woole[d]ge's > articles "what you wrote" was referring (the one you were following up > to above, or the "fucking" one below to which you alluded--so I *asked*, > indicated by my question mark, which my tone may have rendered somehow > accusatory). Your tone, and your language, indicated that the question was rhetorical. But you are now peddling "an equivocal quality" argument by stripping the quotation above away from the post it belonged to: https://lists.debian.org/debian-user/2018/07/msg00185.html 'Your hypothetical case describes a shell script that is supposed to detect what version of Debian it's running on, for whatever reason. If this script doesn't know how to handle the string "testing/unstable" then it's doing a really crappy job of "supporting" Debian systems.' and unilaterally deciding that it's the response to a post that (a) I disagree with and (b) that's actually in a different subthread, the Nicholas Geovanis one: 167 sL 180704 Richard Hector (4.2K) └─> 168 L 180704 John Crawley(2.7K)├─> 169 L 180705 Curt(1.0K)├─> 170 L 180705Joe(0.8K)│ └─> 171 L 180705 Curt(1.0K)│ ├─> 172 F 180705 To Debian-User (2.1K)│ └─> 173 L 180705 Greg Wooledge (0.6K)│ └─> 174 F 180705 To Debian-User (1.5K)│ └─> 175 L 180705 Greg Wooledge (0.9K)│ └─> ← I commented on this (msg00185.html) 176 L 180705 Nicholas Geovanis (1.4K)│ ├─> 177 L 180705Joe(1.1K)│ │ ├─> 178 L 180705 Greg Wooledge (1.0K)│ │ └─> 179 L 180705 Nicholas Geovanis (0.9K)│ │ └─> 180 L 180705 Greg Wooledge (0.4K)│ │ └─> ← contains the f-word (msg00191.html) 181 L 180705 Nicholas Geovanis (1.5K)│ │ └─> 182 F 180705 To Debian-User (1.8K)│ │ ├─> 183 sL 180706 The Wanderer(2.5K)│ │ └─> 184 L 180706 Curt(1.5K)│ │ └─> 185 F 180705 To Debian-User (1.2K)│ └─> ← my comment under discussion (msg00199.html) 186 L 180706 Curt(1.5K)│ └─> 187 L 180706 Greg Wooledge (0.7K)│ ├─> 188 L 180706 Curt(0.1K)│ │ └─> 189 L 180706 davidson (1.5K)│ │ └─> 190 L 180707 Curt(1.9K)│ │ └─> 191 L 180709 Greg Wooledge (1.2K)│ │ └─> 192 L 180709 Curt(0.5K)│ │ └─> There's no reference to Message-id: 0180705204615.xlgol2g2kuace...@eeg.ccf.org (that's msg00191.html) in my msg00199.html. Check it for yourself. Perhaps it's threading as well as quoting that's causing you difficulty. > I do admit that I believed the latter interpretation > without even considering the real possibility that it was indeed the > former, probably because of a minor incident in the Latex/PDF thread we were > both involved in a few moons ago, a can of beans not worth opening. Without any reference, it's difficult to know what you're talking about. But I'm sorry that it's obviously bugging you. Here's the contents of the post that you keep wanting to attach my comment to. If it helps, I'll annotate it here. > The Woole[d]ge post: > > It is not a fucking configuration file that you edit. https://lists.debian.org/debian-devel/2001/01/msg00502.html > It is supposed to be read only. > > Only a crazy idiot would manually edit the file that tells you what > version of the OS you're running. https://lists.debian.org/debian-devel/2001/01/msg00550.html https://lists.debian.org/debian-devel/2001/01/msg00558.html > It would be like editing registry entries in Microsoft Windows to make > it look like you're running a different version of Windows. I lost track of windows versions around 1996 and never got beyond DOS 6.22 for serious work. Apart from knowing that there are versions 7 (good?), 8 (bad?) and 10 (current) still around, I don't know any more than that, so the metaphor is lost on me. Cheers, David.
Re: Debian testing - release number
On 2018-07-10, David Wright wrote: You following up to Woolege: Hmm, I struggle to see the connection between what I asked for and what you wrote. From your later post, I guess the answer is that editing /etc/debian_version risks provoking expletives from other users of the system. That said, I do agree with what you wrote. So there was an equivocal quality there, Dave, as to which of Woolege's articles "what you wrote" was referring (the one you were following up to above, or the "fucking" one below to which you alluded--so I *asked*, indicated by my question mark, which my tone may have rendered somehow accusatory). I do admit that I believed the latter interpretation without even considering the real possibility that it was indeed the former, probably because of a minor incident in the Latex/PDF thread we were both involved in a few moons ago, a can of beans not worth opening. The Woolege post: It is not a fucking configuration file that you edit. It is supposed to be read only. Only a crazy idiot would manually edit the file that tells you what version of the OS you're running. It would be like editing registry entries in Microsoft Windows to make it look like you're running a different version of Windows. Anyway, have a nice day.
Re: Debian testing - release number
On Fri 06 Jul 2018 at 08:41:58 (+), Curt wrote:
> On 2018-07-06, David Wright wrote:
>
> > Hmm, I struggle to see the connection between what I asked for and
> > what you wrote. From your later post, I guess the answer is that
> > editing /etc/debian_version risks provoking expletives from other
> > users of the system.
> >
> > That said, I do agree with what you wrote.
>
> So wait, now, after saying this
>
> What seems to be lost on people who feel a pressing need for
> /etc/debian_version to contain a number to satisfy some script that
> they have written (which seems to be the usual reason) is that
> /etc/debian_version is a configuration file. Look in the
> .deb file and there it is, along with /etc/issue{,.net} which
> determine how you are greeted {locally,remotely}. So admins are
> free to set them all how they like.
That paragraph is a correct quotation of what I wrote.
> we discover that what you actually believe is, although admins are free to do
> so (like you're free to blindfold yourself and jog in the middle of the
> freeway
> at rush hour in L.A with a broom sticking out of your wazoo), you'd have to be
> insane to actually edit /etc/debian_version, which is *not*, in fact, a
> configuration file
This is something you just made up and is unrelated to what I have written.
> (because that's what Wooledge said that you're agreeing
> with here)?
[I think you mean "because that's what Wooledge said, which you're agreeing
with here".]
Perhaps you have temporarily forgotten how quoting should work on a
mailing list, and therefore your interpretation of
https://lists.debian.org/debian-user/2018/07/msg00199.html
is completed erroneous. Read what I posted:
1)
"[DW] Hmm, I struggle to see the connection between what I asked for
and what you wrote."
In other words, this reply:
'[GW] Your hypothetical case describes a shell script that is
supposed to detect what version of Debian it's running on,
for whatever reason.
If this script doesn't know how to handle the string
"testing/unstable" then it's doing a really crappy job of
"supporting" Debian systems.'
does not answer:
"[DW] Would you explain what is unsafe about it and why
/etc/debian_version is a configuration file, or offer
a sensible alternative."
2)
"[DW] That said, I do agree with what you wrote."
In other words, I agree with the statement I quoted there:
'[GW] Your hypothetical case describes a shell script that is
supposed to detect what version of Debian it's running on,
for whatever reason.
If this script doesn't know how to handle the string
"testing/unstable" then it's doing a really crappy job of
"supporting" Debian systems.'
It doesn't mean I agree with everything they ever wrote in the thread
on the matter, just what I quoted, which is why I quoted it.
> So, Joey Hess is a crazy idiot, for instance?
Why would you think of calling Joey a "crazy idiot"?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81249
>
> Local changes made to /etc/debian_version (in this case changing it from
> "testing/unstable" to "unstable" since that is what this system is really
> using) are wiped out when the package is upgraded or reinstalled:
The evidence presented in the bug report clearly shows that
/etc/debian_version gets overwritten, so one has to assume that,
at the time, it wasn't flagged as a conffile. That's supported
by typing:
$ zgrep -A7 '(2.2.8)' /usr/share/doc/base-files/changelog.gz
There was some debate around this time about what /etc/debian_version
should contain during development, as you can see with:
$ zgrep -A16 '(2.2.6)' /usr/share/doc/base-files/changelog.gz
The fact that /etc/debian_version *is* a *configuration* file
was clearly promulgated in:
https://lists.debian.org/debian-devel/2001/01/msg00502.html
Cheers,
David.
Re: debian/testing repo question
On 7/10/18, The Wanderer wrote: > > (I'm really surprised to see someone with an @debian.org address > advising people to run unstable for any other reason than helping with > developing Debian. Cherry-picking a single package from unstable for > new-version reasons may be one thing, but tracking unstable on a > production system is dangerous and inadvisable, and I've gotten multiple > machines into unsupportable configurations that way. I've also seen it > stated repeatedly on debian-devel that people not interested in helping > develop / improve Debian should not run sid.) +1,000. I played with Sid because it was a cool, nerdy thing to be able do *so easily*. A few months in, it became very clear just how UNSTABLE Sid is. It's called that for a reason. Sid is *NOT* for usage situations where #Life itself... or on a lesser scale perhaps one's financial status... may possibly be relying on a computer being available every second Humanly possible. Stable Stretch right now could be used to change the Lives of poverty level people by spending time teaching them how to access it via the very minimalist debootstrap install way. It's a game changer that I personally haven't been able to duplicate elsewhere so far. *cough* Hint: I've looked. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * Sid and I are on a break. *
Re: debian/testing repo question
On Tue, Jul 10, 2018 at 04:10:22PM +0200, Hans wrote: > > Most users I am supporting are using stable, but some are using testing. > Should I advise them to upgrade tu unstable? > For non-production use, unstable or testing should be fine. Both will be broken from time-to-time. The question is whether you are willing to deal with the different forms of breakage you are likely to encounter with each. Regards, -Roberto -- Roberto C. Sánchez
Re: debian/testing repo question
On Tue, Jul 10, 2018 at 10:27:19AM -0400, The Wanderer wrote: > > (I'm really surprised to see someone with an @debian.org address > advising people to run unstable for any other reason than helping with > developing Debian. I say that because testing gets "stuck" in various ways. In particular, library transitions can result in the removal of many packages from testing because of delays in updating them. > Cherry-picking a single package from unstable for > new-version reasons may be one thing, but tracking unstable on a > production system is dangerous and inadvisable, Using anything other than stable on a production system is rather high risk. Testing gets no security support. Suppose that a package you are using has a new upsrteam release come out to fix security issues. The security team will backport those fixes to stable. The maintainer will usually upload a new version to unstable. There are instances where that new version also introduces new bugs and is prevented from migrating to testing. So now you have a package with potentially severe security vulnerabilities that you cannot update from Debian sources. That sounds like a real problem to me. Of course, there is no guarantee that unstable will get the latest security-fixed version in a timely manner. > and I've gotten multiple > machines into unsupportable configurations that way. I've also seen it > stated repeatedly on debian-devel that people not interested in helping > develop / improve Debian should not run sid.) > That is true of both testing and unstable. Counterintuitively, unstable tends to stay broken for shorter periods than testing. So, for users who are not willing or able to deal with lengthy delays in problems being fixed, testing is a bad choice. Regards, -Roberto -- Roberto C. Sánchez
Re: debian/testing repo question
> > For myself, I track stable+testing, dist-upgrade on at least a weekly > basis, and deal with occasional breakage when it happens. So do I. But in the past I (some years agho) I ran unstable but never got iun big trouble (I believe, I wa just luicky, wasn't I?) Best Hans
