Re: Change root subvolume on btrfs
Disclaimer: I only have limited experience with btrfs and never used it for root partition. On Thu, Oct 28, 2021 at 04:10:08 +0100, piorunz wrote: > I have / partition on btrfs subvolume, default name @rootfs created by > Debian. > [...] > > Question: > How can I rename / subvolume on btrfs from @rootfs to @? If it doesn't move to another parent folder, just `mv`ing it is the correct approach afaik. > I tried: > rename folder name by hand from USB stick Linux Mint from @rootfs to @, > and then changing @rootfs to @ in /etc/fstab, but grub didn't booted, it > thrown me out to grub emergency console. I had to revert it back. Maybe the grub command for booting also explicitly specifies the subvolume. Can you take a look at the relevant line in /boot/grub/grub.cfg? (If you're not sure what to look at, serach for the text of the netry you use in the GRUB-menu, everything from there until a line starting with `initrd` could possibly be relevant). If yes, you'll need to change that in /etc/default/grub and/or /etc/default/grub.d/* and then run update-grub as root. > Some context: > $ sudo btrfs subvolume list / > ID 256 gen 176714 top level 5 path @rootfs > ID 265 gen 21191 top level 256 path var/lib/portables > ID 266 gen 21192 top level 256 path var/lib/machines What does `sudo btrfs subvolume get-default /` tell you before _and_ after you renamed the subvolume? If it was @rootfs before but is not @ afterwards, you'll need to set the default using sudo btrfs subvolume set-default ...
Re: Bug: missing package
On Sun, Mar 14, 2021 at 21:20:39 -0400, Jude DaShiell wrote: > Why is frobtads missing from debian repositories? Looking at the tracker, the package is held back by "failure to build from source" bugs, which are considered RC critical: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836934 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966109 Those bugs need to be fixed before frobtads can enter testing again. ~~ Nito
Re: Firefox HTTPS-only mode breaks sites that return 404 for HTTPS connections
On Wed, Apr 14, 2021 at 16:01:13 -0300, riveravaldez wrote: > > Not sure if useful at all, but I've been using firefox-release (just running > the binary from Mozilla) as main browser for years, and enabled HTTPS- > Only Mode upon HTTPS Everywhere add-on/extension simply because > I had it installed and I was letting it be (?). And that (unexpected?) > combination seems to work fine Not OP, but a few months ago I did experience a similar problem when setting up a reverse-proxy for one of my private domains. For test purposes I initially did not set up nginx to deal with TLS for this domain (but others already had TLS enabled). Firefox (both with and without HTTPS Everywhere) would always switch to TLS, resulting in a cert-mismatch warning and me ending up on a different site than intended. I wasted a few hours trying to figure out what was wrong with my proxy config, before I realised (and verified with curl iirc) the fault was with the browsers (iinm Chromium messed up similarly). Once HTTPS was enabled for all domains on this server everything was working as expected in browsers again. -- Nito
Re: apt-cacher-ng and CNAMEs
On Tue, May 03, 2022 at 15:16:47 -0400, Celejar wrote: > [...], and I'm consequently somehow getting bitten by > this issue: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356 > > But that (as described by the maintainer) mess was supposedly resolved, > and the bug was closed. Am I missing something, or does that bug need > to be reopened? Are you using stable? The bug has been closed with version 3.7.1-1 of apt-cacher-ng. Stable currently has 3.6.4-1 with no indication of a patch being applied for this bug. Bullseye-backoprts offers 3.7.4-1~bpo11+1 though, so you could likely use this to get a fix for #986356. > -- > Celejar >
Re: Buster with MATE without systemd
On Tue, Sep 15, 2020 at 19:28:34 -0700, Marc Shapiro wrote: > I have a fresh install of Buster which is running MATE as the Desktop > Environment. […] The next thing that I > want to do is replace systemd with sysvinit. > > Now I get a full screen of packages to be removed. Most are libraries, and > what seem to be MATE virtual packages, along with some other packages, > including the GIMP. I DO want MATE and the GIMP. This looks like a > problem. The problem with MATE is that many MATE packages depend on mate-polkit, which depends on policykit-1, which in buster depends on libpam-systemd. In Bullseye this dependency is changed to the new virtual package logind, which can be provided by either systemd or elogind. There may be other packages pulling in systemd. Using MATE without any logind backend does mostly work, but you'll miss things like auto-mounting drives etc. Until bullseye becomes stable, you could maybe try to trick apt into accepting elogind, by creating your own 'libpam-system', 'libsystemd0' packages that just pull in the elogind counterparts. This may however have unintended side-effects if something genuinely depends on systemd specifically. There's also an old bug about this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909192 ~~ Nito
Boot warnings: "No irq handler for vector …"
Hi, after updating the BIOS, I'm now met with warning/error messages every boot, however it continues to boot normally. There has since been one crash related to PCIe errors, but I'm not sure if this was related to the BIOS update or "just" a driver bug. Downgrading the BIOS to the previous version is - as I found out - not officially supported. I'm not sure how bad these warnings/errors are and if I should be concerned about it and if this should be reported to the manufacturer or kernel devs. I'd appreciate if someone more knowledgeable with this could give me an opinion on it. Relevant dmesg excerpt: [0.364305] rcu: Hierarchical SRCU implementation. [0.364572] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. [0.364641] smp: Bringing up secondary CPUs ... [0.364641] x86: Booting SMP configuration: [0.364641] node #0, CPUs:#1 [0.068359] __common_interrupt: 1.55 No irq handler for vector [0.364641] #2 [0.068359] __common_interrupt: 2.55 No irq handler for vector [0.364705] #3 [0.068359] __common_interrupt: 3.55 No irq handler for vector [0.366814] #4 [0.068359] __common_interrupt: 4.55 No irq handler for vector [0.368708] #5 [0.068359] __common_interrupt: 5.55 No irq handler for vector [0.372703] #6 [0.068359] __common_interrupt: 6.55 No irq handler for vector [0.374847] #7 [0.068359] __common_interrupt: 7.55 No irq handler for vector [0.376706] #8 [0.068359] __common_interrupt: 8.55 No irq handler for vector [0.378863] #9 [0.068359] __common_interrupt: 9.55 No irq handler for vector [0.380706] #10 [0.068359] __common_interrupt: 10.55 No irq handler for vector [0.382816] #11 #12 #13 #14 #15 [0.394846] smp: Brought up 1 node, 16 CPUs [0.394846] smpboot: Max logical packages: 2 [0.394846] smpboot: Total of 16 processors activated (102210.65 BogoMIPS) [0.397401] devtmpfs: initialized Full dmesg logs from before and after the BIOS update are attached. Those irq errors happen with all tested kernel versions. ( Buster's 4.19.0-11-amd64, backport's 5.7.0-0.bpo.2-amd64 and local 5.8.12 and 5.8.14 kernels ) As for why I was updating the BIOS: With the previous BIOS version I wasn't able to run the RAM at the advertised speeds. Now I can, but I get these warnings/errors instead — regardless of memory speed. Nito before.log.xz Description: application/xz after.log.xz Description: application/xz
Re: Who installed package "foo"?
On Mon, Nov 02, 2020 at 09:51:29 +0700, Victor Sudakov wrote: > Jean-Philippe MENGUAL wrote: > > or apt-cache rdepends foo > > I got the impression that it shows all possible reverse dependencies, > not just those installed locally. apt-cache rdepends --installed foo will limit this to locally installed reverse dependencies. > It lists plenty of stuff which "dpkg -l" does not list.
Memory Leaks or Mem. being misreported
Hi everyone, after upgrading my hardware I started to notice what seemed like memory leaks. After booting my desktop machine usually around 450MiB(with i3) or 650MiB(with MATE) of RAM are being used and after extended use, when closing all gui-programs except a terminal, based on prior experience I would expect the RAM usage to not be more than +120MiB compared to after booting. I am *not* counting file cache/buffers in this (or I severely misunderstand how to read free's and top's output). But now I would often end up with something between +600MiB and +2.5GiB. When looking at top or htop no process using nearly that much memory is listed. I tried to figure this out and will give some more details in a minute, but I'm left confused as to why this is happening how to continue debugging this and where I could file a bug report. Any advice on how to proceed or where to file a bug would be appreciated. Or maybe I'm just stupid and misreading top's and free's output. Unfortunately the only reliable way to reproduce this, that I found, involves manual interaction with some Firefox profiles. I know this means there's probably an issue with Firefox, but afaik when a user-space process with a memleak is closed, the leaked memory should be cleaned up as well. My failed attempt to recreate the leaks with a simple C program seems to support this. Also this seems to be hardware specific. Affected are: Debian 10 with kernels: 4.19 (from main) 5.4.0~bpo.3 5.4.0~bpo.4 (from backports) 5.4.23 with Manjaro patches and config 5.4.26 (vanilla; config based on Debian's config) 5.6-rc7 (vanilla; config based on Debian's config) Manjaro with kernel: 5.4.23-MANJARO Ubuntu-18.04 with kernels: 5.3 5.4.xy (vanilla) In Manjaro and Ubuntu proprietary firmware was used. In Debian I was first only using the proprietary AMD-GPU firmware but later also added firmware for the Ethernet-controller and microcode for the CPU without any change. dmesg does not seem to show anything relevant*. (*or atleast not anymore since cpu-bootcode is installed) (The following was only tested with kernel 5.6-rc7): Now yesterday on accident I noticed, that after running a backup, which "filled" RAM with file cache, the reported memory fell again to a normal level. With i3: --After Boot: $ free -h totalusedfree shared buff/cache available Mem: 31Gi 397Mi30Gi11Mi 314Mi30Gi Swap: 6,0Gi 0B 6,0Gi --After using and closing Firefox --(no processes using that much RAM are listed in htop): $ free -h totalusedfree shared buff/cache available Mem: 31Gi 1,1Gi 2,4Gi13Mi27Gi29Gi Swap: 6,0Gi 0B 6,0Gi --After Backing up which "filled" RAM with file caches: $ free -h totalusedfree shared buff/cache available Mem: 31Gi 471Mi 328Mi13Mi30Gi30Gi Swap: 6,0Gi 0B 6,0Gi The reported memory usage of htop,top and free was all in accordance with each other here. Now as I couldn't find a way to reliably "fill" up my RAM with file caches, I tried to recreate this (with MATE) with a C program that allocates memory, writes pseudo-random data to it and exits (without freeing). I allocated 30GiB, so more than MAX-used, but less than MAX-(expected usage). After that (h)top and free are disagreeing on how much memory is being used (see SWAP). --After Firefox (htop,top and free report more or less the same): $ free -h totalusedfree shared buff/cache available Mem: 31Gi 1,5Gi27Gi92Mi 2,7Gi29Gi Swap: 6,0Gi 0B 6,0Gi -- After allocating 30GiB and then exiting: $ top -b -n 1 | grep "^MiB" MiB Mem : 32092,0 total, 27747,1 free,744,3 used, 3600,6 buff/cache MiB Swap: 6144,0 total, 6143,5 free, 0,5 used. 30458,0 avail Mem $ free -h totalusedfree shared buff/cache available Mem: 31Gi 743Mi27Gi93Mi 3,5Gi29Gi Swap: 6,0Gi 0,0Ki 6,0Gi htop was reporting around 500MiB swap usage (before and also after running the above two commands). So maybe this is not a memory leak but memory usage is being misreported ? Where should I file a bug for this; or am I just misreading (h)top's and free's output and everything is as expected ? free's manpage states: > used Used memory (calculated as total - free - buffers - cache) which I take as this being the memory actually in use, that I could not just allocated in a process without needing to fallback to swap. Sorry for this wall of text. Kind Regards Nils
Re: Memory Leaks or Mem. being misreported
On Sat, Mar 28, 2020 at 10:12:52AM -0400, Dan Ritter wrote: > Did this cause a problem, or are you chasing a number you don't > like? I avoided possible problems until now, as every time I expected to need a lot of memory and the "used memory" was larger than expected I rebooted beforehand. Also not understanding why this happens or possibly having misunderstood how to read (h)top's and free's memory usage is a problem in itself and might also lead to further problems in the future. > What different hardware have you tried? I am mainly comparing these two setups, but have briefly tried some other hardware as well: | Previously (unaff.) | Current (affected) ——+——+——— CPU | AMD Athlon II X3 450 | AMD Ryzen 7 2700 GPU | AMD Radeon RX580 | AMD Radeon RX 580 Mainboard | AsRock 770 Extreme3 | ASUS X570 TUF-Gaming RAM | 3×2GB DDR3-1333 | 2×16GB DDR4-2800 Debian and Manjaro were freshly installed after the hardware change, Ubuntu was kept for a while but is now removed. Ubuntu 18.04 did not show this behaviour with the old hardware and kernels 4.15, 5.0, 5.3 (from Ubuntu repos) and various versions of 5.4.xy (vanilla) but did show this behaviour with the new hardware and kernels 5.3 and 5.0(from repo) and various vanilla 5.4 versions. I did not test Ubuntu with new hardware and kernel 4.15. > This all looks fine. You are barely using your memory. See the > available number at the end? That's what would be available for > programs that want to use it. In all 3 instances there were only some daemons, the X-Server, WM and one terminal running as I closed all other applications beforehand. (including Firefox). Also this is not the biggest memory increase I observed, as I said this "idle usage" can increase to several GiB. - On Sat, Mar 28, 2020 at 05:10:07PM +0300, Reco wrote: > /proc/meminfo (please *do not soft* it), and the output of slabtop. > If you're need to understand where all that memory gone - you're in need > of proper tools. Thanks. I will look into it this later this day. Nils
Re: Memory Leaks or Mem. being misreported
On Sat, Mar 28, 2020 at 05:10:07PM +0300, Reco wrote: > /proc/meminfo (please *do not soft* it), and the output of slabtop. > If you're need to understand where all that memory gone - you're in need > of proper tools. I have saved the output of slabtop and /proc/meminfo for: aboot: Directly after booting and logging into a graphical i3-session afirefox: After using an affected Firefox profile afill-alloc: After afirefox and running a simple C program that allocates almost all of the total physical memory afill-alloc+swaponoff: After afill-alloc and swapoff and swapon. In all cases only some daemons, X-Server, i3 and one or two terminals were running. htop and free were reporting memory usage as around 450MiB for aboot and afill-* and around 1,3GiB for afirefox. I've read the part about meminfo here https://www.kernel.org/doc/Documentation/filesystems/proc.txt but I'm not experienced enough to tell if anything/what in the meminfo output is unusual. For reference: htop calculates the memory usage from /proc/meminfo like this: Cached memory = Cached + SReclaimable - Shmem Non cache/buffer memory = MemTotal - MemFree - (Buffers + 'Cached memory') Swap= SwapTotal - SwapFree As they are rather lengthy and there are 4 of them, I attached the output of the commands to this email. According to the mailing list guidelines large attachments should be avoided, but since they are in total 68K and compressed just 8K this should probably be fine. If the attachment doesn't work I can resend it in the mail body. Nils meminfo+slabtop.tar.gz Description: application/gzip
Re: Memory Leaks or Mem. being misreported
On Sun, Mar 29, 2020 at 07:04:36PM +0300, Reco wrote: > > afirefox: After using an affected Firefox profile > > Ok, let's breakdown it (left is aboot, right is afirefox). > Here we see about 2Gb of memory consumed: > > MemFree:32124660 kB / MemFree:30144704 kB > > Such discrepancy can be attributed, first, […] > > Summing it up, it gives us 668382 kB of discrepancy. > […] > So the big question is - where 650M of memory gone? My money is on > kernel modules. Maybe it's Intel's VideoRAM steal (don't know if AMD do > it the same way). Maybe it's some proprietary kernel module. > > I know no way of accounting memory usage of kernel module, but I can > spot some possible candidates from "lsmod" output. Thanks. Afaik there are no proprietary kernel modules in the default buster install and I did not install proprietary modules either. BUT I did install proprietary firmware for the devices. First I only installed firmware-amd-graphics as it is necessary for XServer to work. But the same GPU was already present in my previous desktop system. After I noticed the issue with memory I also installed in that order ·firmware-realtek for the ethernet controller (The controller does work without it, possibly not at full speed, but it works fast enough for my connection) ·amd64-microcode for the CPU But this does not seem to have made any difference. Beside these 3 package the only other installed package from non-free is a font-package. Here's the lsmod output (while some programs are running in case that's relevant): Module Size Used by binfmt_misc24576 1 amdgpu 5373952 26 nls_ascii 16384 1 nls_cp437 20480 1 vfat 20480 1 fat86016 1 vfat mfd_core 20480 1 amdgpu gpu_sched 40960 1 amdgpu i2c_algo_bit 16384 1 amdgpu ttm 122880 1 amdgpu snd_usb_audio 290816 0 drm_kms_helper245760 1 amdgpu snd_hda_codec_realtek 126976 1 snd_hda_codec_generic98304 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic snd_hda_codec_hdmi 73728 1 snd_hda_intel 53248 10 snd_intel_dspcfg 20480 1 snd_hda_intel snd_hda_codec 163840 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 102400 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_usbmidi_lib40960 1 snd_usb_audio snd_rawmidi45056 1 snd_usbmidi_lib snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec snd_pcm 131072 6 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd_timer 45056 2 snd_pcm cec49152 1 drm_kms_helper snd 102400 29 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi drm 581632 17 gpu_sched,drm_kms_helper,amdgpu,ttm mc 57344 1 snd_usb_audio kvm_amd 114688 0 kvm 806912 1 kvm_amd eeepc_wmi 16384 0 irqbypass 16384 1 kvm asus_wmi 40960 1 eeepc_wmi battery20480 1 asus_wmi pcspkr 16384 0 sparse_keymap 16384 1 asus_wmi video 53248 1 asus_wmi crct10dif_pclmul 16384 1 crc32_pclmul 16384 0 soundcore 16384 1 snd rfkill 28672 2 asus_wmi ghash_clmulni_intel16384 0 aesni_intel 368640 0 ccp 106496 1 kvm_amd sp5100_tco 20480 0 glue_helper16384 1 aesni_intel crypto_simd16384 1 aesni_intel cryptd 24576 2 crypto_simd,ghash_clmulni_intel evdev 28672 15 k10temp16384 0 rng_core 16384 1 ccp watchdog 28672 1 sp5100_tco wmi_bmof 16384 0 sg 36864 0 efi_pstore 16384 0 efivars20480 1 efi_pstore wmi36864 2 asus_wmi,wmi_bmof acpi_cpufreq 28672 0 button 24576 0 parport_pc 32768 0 ppdev 24576 0 lp 20480 0 parport61440 3 parport_pc,lp,ppdev efivarfs 16384 1 ip_tables 32768 0 x_tables 53248 1 ip_tables autofs453248 2 ext4 770048 3 crc32c_generic 16384 0 crc16 16384 1 ext4 mbcache16384 1 ext4 jbd2 139264 1 ext4 sd_mod 57344 5 hid_generic16384 0 usbhid 65536 0 hid 139264 2 usbhid,hid_generic sr_mod 28672 0 cdrom
Re: Small Open Source Digital Classroom
On Tue, Mar 31, 2020 at 08:17:56PM +0200, deloptes wrote: > […] Recently I was looking at zoom.us - seems to be in > hype now - can be installed in debian and can be used as video conferencing > tool. Based on zoom's "privacy" policy and everything I've herad so far about it, I would not recommend using zoom. Some examples: - Just a week or so ago it was exposed that zoom was sharing data with facebook without informing the user about it or giving any choice on that. Alledgedly they stopped it now [1] - Zoom created Security-Holes with it's Mac-Client, that persisted even after deinstalling zoom on OSX. [2] Personally I wouldn't trust their other clients either. - Zoom can collect more data about you then you might think and share this with the meeting-creator. [3] [1] https://www.komando.com/security-privacy/zoom-ios-app-facebook/732681/ [2] https://www.vice.com/en_us/article/8xzjj4/zoom-video-conferencing-vulnerability-lets-hackers-turn-on-your-webcam [3] https://www.eff.org/deeplinks/2020/03/what-you-should-know-about-online-tools-during-covid-19-crisis Jitsi has already been mentioned and while I only ever used it for smaller groups, from what I've heard it can also handle larger groups, though in that case you might need to host your own instance on a server with enough bandwith. That's if just a simple video conference is enough for this use case.
Re: xfce4-terminal appears upon log in
Hi, On Wed, Apr 01, 2020 at 05:15:37PM +0800, kaye n wrote: > I'm not sure what I did, but when I log into my Debian, xfce4-terminal > opens automatically. > > Desktop: Xfce 4.12.4 I'm guessing you either added the terminal to autostart on login, or you once told XFCE to save your session on logout. Even if you uncheck the "save session" checkbox, xfce will continue to start up with the last saved session. The infos may be outdated or incomplete as I only rarely used xfce, but you can try this: GUI: somewhere under settings there should be something called "startup and sessions" or similar. If there are any saved sessions you can delete them and you can also check on autostart. Non-GUI: Check .config/autostart and .cache/sessions ~~ Nito
Re: Debian is testing Discourse
On Sun, Apr 12, 2020 at 11:45:02 +0300, Reco wrote: > Why are you doing this? > […] Secondly, I genuinely believe that ease of access to new > contributors is of paramount importance to the project. I'd say a mailing list is actually way *more* accessible, than some web forum (esp. with javascript). For one thing virtually everyone already has an email, so no additional accounts/pw need to be managed. Furthermore customising the display of plain text emails to fit your needs is easy, while doing the same with discourse requires more work and knowledge – or might not be feasible for the non-text elements of discourse. (E.g. increasing font size and contrast to make up for bad eyesight, using different fonts due to preference or to help with dyslexia etc ) > Be specific! > Ok... I think *debian-user*, debian-vote and possibly debian-project > would be better off in Discourse. […] While I'm not eligible to vote in debian matters, I'd say that *especially* debian-vote should *not* be in discourse. One reason is the accessibility mentioned above, another reason is that I believe the absence of likes etc on debian-votes to be a *good* thing. This helps to avoid influencing the readers and gives all proposals a fairer chance. Let's say supporters of one proposal are primarily using discourse and all like the proposal, while another proposal has roughly the same amount of supporters, but the supporters are using the mail interface and can't like/don't see a point in liking. This will distort perceived support for the proposals. Also I think that taking the time to write down what you believe to be good/bad about a proposal instead of +1/-1 helps everyone to get a better picture on the situation.
Re: Debian is testing Discourse
On Sun, Apr 12, 2020 at 18:16:44 +0300, Andrei POPESCU wrote: > What if someone else already wrote that, possibly in better words than I > could? If you really feel like it's necessary, you can reply to the thread with: I like this proposal mainly because of A and B, but I am a bit concerned about C. Person P. already gave an good argument as to why. > The rules for submitting or sponsoring actual voting proposals / > amendments etc. are clearly laid out, I don't see any danger here. Well, I do, though none of us can see into the future. But that makes me wonder: If you don't think likes/dislikes as present on discourse have an influence on this: Why bother using it at all ? And even if I only mentioned it with one sentence in the debian-vote section as I wrote about it before: The accessibility, which would *decrease* with discourse, (and exclude mail-interface users from the like/disliking) should be a top priority for debian-vote. If you want to give people more familiar with forums a familiar interface, I'd say the reverse approach is much more feasible and does not create problems with accessibility: Offer a forum-like front-end for the mailing list. There are already 3rd parties offering something like that for debian mailing-lists. One that sometimes shows up in my search results, would be nabble (note that I'm not endorsing or recommending any such 3rd party provider) http://debian.2.n7.nabble.com/Debian-is-testing-Discourse-td4669989.html If there is a need for that debian could offer something like that itself (if it does not yet exists, didn't check). As the backend would still be purely text based, there is no issue with accessibility or feature exclusion. This leaves us only with "moderation" as a _potential_ benefit of discourse as a primary interface. Stronger moderation with retroactive editing and deleting however, while it night offer _some_ benefits, also creates a fair share of problems and potential for abuse in the future. Given the disadvantages with a forum focused interface, I don't think a potential benefit in moderation is worth it. -- Nito signature.asc Description: PGP signature
Re: DOH (was: geolocation services disabled and Gnome maps)
On Tue, Apr 14, 2020 at 07:06:05 -0400, Lee wrote: > Is there some other DNS provider that has a published privacy policy? > That's anywhere near as good as CloudFlare's? > > To be clear - I'm not saying you should trust CloudFlare. It's just > that I don't see a whole lot of options & quite possibly CloudFlare is > more trustworthy than your USA ISP. Some non-profit organisations here operate public non-logging[1] DNS servers. They all support DoT, only some support DoH. But none of them would have enough resources to serve all Firefox users in the world though. --- Nito [1]: Only malformed queries are logged for diagnosis.
Re: cleanly getting rid of manually installed transitional packages due to rename
On Tue, Apr 21, 2020 at 17:07:52 +0200, Vincent Lefevre wrote: > Sometimes packages get renamed. [...] > > [...] if one > wants to remove it, then apt or aptitude will also want to remove > the new package because this new package has not been installed > manually and its only reverse dependency (the transitional package) > has just been removed by this operation. [...] > > Is there a way to avoid this behavior automatically, i.e. by > forwarding the "manually installed" state automatically to the > new package? You can use apt-mark to mark the new package as manually installed. -- Nito
Re: Please help me find a good Debian compatible video card
On Sat, Apr 25, 2020 at 18:58:45 +0500, Alexander V. Makartsev wrote: > On 25.04.2020 16:20, Jiangsu Kumquat wrote: > > I want to get a good fast Debian compatible card for 1080p. > > > > […] > > > > However, I think most or all of those cards won't work that great for > > Linux because of compatibility issues. > > > > Can you recommend a good card for me to use? I play windows games in > > Debian with wine. > > > > I tend to prefer AMD cards, but Nvidia cards are okay I guess as long > > as they work well with Debian. > > I highly recommend Nvidia-based cards, if you don't mind closed-source > drivers. > Many (Most?) games with Linux-native ports officially support only > Nvidia by game developers. I think, this is because of the drivers, > their quality and stability. Many games officially recommend the proprietary drivers, though with any recent AMD-GPUs (as in: supported by AMDGPU instead of radeon) I've never needed them (some Phoronix benchmarks even seem to indicate, that AMDGPU often but not always even works better than AMDGPU-PRO). With NVidia cards the open source noveau driver will not be sufficient for gaming though. I can't complain about the AMDGPU driver more than any of the other graphic drivers. In fact I tend to find AMDGPU easier to handle than the proprietary NVidia drivers. As far as I heard, for stability you should not use a GPU that was just released some months prior, though. The drivers need some time. > AMD-based card will usually work too, but (as long as I can remember) > quality of their drivers were something to be desired and drivers for > Linux are under heavy development, but they are open-source. If choosing a AMD GPU for gaming I'd recommend to atleast use kernel 5.4 from backports, as afaik there were some (for gaming) signinficant improvements after 5.0. > In case of Proton\WINE, you could get mixed results, because some games > (via DXVK) will work better with Nvidia and some are better with AMD. > "Better" here as in "less graphical glitches, more performance and > stability." > To play modern games in 1080p 60fps with high graphics settings you > would want minimum GTX1660 or better with 6Gb VRAM or more. If you want to achieve the highest of high gaming performance, Nvidia cards currently offer better (and more expensive) hardware. If you are happy with (just) decent performance Nvidia vs AMD probably doesn't matter too much and is mostly game dependent.
Re: Missing Courier font
On Mon, Apr 27, 2020 at 12:45:58 +0300, Tommi Höynälänmaa wrote: > Courier fonts is missing in my system (in Gtk/Pango). What Debian > package contains this font? My copy of the Courier font was installed by 'texlive-fonts-recommended'. If you want 'Courier 10pitch' instead of the original Courier, you need the package 'xfonts-scalable'. The ttf-mscorefonts package from contrib mentioned before, does *not* seem to contain the original Courier font, only Microsoft's variant 'Courier New'. In case you *did* mean MS's 'Courier New' instead of 'Courier': If you need to view documents with Microsoft's Courier New , Arial or Times New Roman and you don't care about the fonts specifically, only that formatting is right, you can replace them with free metric-compatible fonts: Either (Arimo, Cousine and Tinos) from fonts-croscore or the Liberation font family from fonts-liberation. These packages are in main. Most programs seem to pick them up as replacements automatically, if installed. In case this doesn't work you can alias them in your fontconfig configuration. --- Nito
Re: Missing Courier font
On Mon, Apr 27, 2020 at 14:21:10 +0200, Nicolas George wrote: > n...@dismail.de (12020-04-27): > > The ttf-mscorefonts package from contrib mentioned before, does *not* seem > > to > > contain the original Courier font, only Microsoft's variant 'Courier New'. > > The original Courier font was physical. All the files we have nowadays > are variants / reimplementation, That's right, sorry I wasn't clear on this. What I meant was, that this is the font that is a) Actually named plain 'Courier' b) The texlive Courier fonts are the digitalised version released by IBM themselves under some free font license > [...] and Courier New is not less authentic > than the others. Well as 'Courier' as used by texlive was released by IBM, who commissioned the original Courier font, you could make an argument that 'Courier' is somehow more authentic than the others ;) . Not that this matters much as long as you get a font that is to liking in appearance and usage rights. --- Nito
Re: Missing Courier font
On Mon, Apr 27, 2020 at 15:24:29 +0200, Nicolas George wrote: > n...@dismail.de (12020-04-27): > > b) The texlive Courier fonts are the digitalised version released by > > IBM themselves under some free font license > > How did you obtain that information? AFAICS, the Courier fonts in > TeXlive are the Adobe and URW variants. https://www.ctan.org/pkg/courier The font is in Adobe's Postscript Type 1 format, but IBM is listed as copyright holder and maintainer. Wikipedia also seems to agree with IBM having released a Type 1 Courier: https://en.wikipedia.org/wiki/Courier_%28typeface%29#IBM_Courier
Re: How to start offlineimap systemd
On Sun, May 03, 2020 at 15:28:11 +0200, jose...@posteo.net wrote: > Everything is working smoothly except offlineimap. Actually I works > well, the problem is that I can't start the systemd service. > > I've tried like this: > > systemctl --user start offlineimap > Failed to start offlineimap.service: Unit offlineimap.service not > found. You need a systemd-service file to use it as an systemd-service. Either you disabled it (try systemctl enable offlineimap.service), or create a new service file. The package seems to contain an example service file: https://packages.debian.org/stretch/all/offlineimap/filelist /usr/share/doc/offlineimap/examples/systemd/offlineimap.service > You can see that the service is not found. I have also tried starting > with socket activation but it is the same. I'm not a systemd expert, but I think if there's no service file you can't start it as a systemd service anyway. --- Nito
Re: GPU support for Linux 4.19
On Fri, May 22, 2020 at 13:24:38 +, Liam Powell wrote: > Greetings to all of you. I have a question, which is bugging me. > > First of all I use Debian Stable. > > I wanto to buy a new graphics card because my old one, a GTX 1060 3GB, was > corrupt (random system locks by it's fault). So I wonder if a RTX 20 Series > GPU from NVIDIA or an AMD RX 5000 Series GPU would work on Linux v4.19. No idea about NVIDIA's propietary drivers, you'll have to see what NVIDIA says about that. As for AMD RX 5000 cards, I think they probably work somewhat with 4.19, but I'd recommend grabbing a a newer Kernel >=5.4 from backports, if you want to use it with debian for gaming. > I only need Debian GNU/Linux to detect it and know which GPU is to > passthrough it to my Windows gaming VM, to play Windows-only games. For > Debian I already have Intel's IGPU. I may be mistaken, but doesn't a proper GPU passthrough mean, the GPU to be passed through is never used by the host system and only by the guest (Windows) ? Meaning wherever or not the GPU works with Debian (your host) is irrelevant as the GPU will only be used by MS Windows as if MS Windows was the host itself ? The ArchWiki seems to agree: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Isolating_the_GPU > So how's the support for these GPUs? > > Thank you so much! > > -- > Liam Powell
Re: Remove undesired entries in MATE "Applications" sub-menus
On Sat, Jul 04, 2020 at 06:53:56 -0500, Richard Owlett wrote: > I'm using Debian10 with the MATE desktop. > The Debian installer defaults to installing a mess of applications I rarely > want. They end up with entries on MATE's Applications sub-menus. > > Without deleting the offending applications from the system, how can I > delete those menu entries and replace them with links to suitable > applications. MATE has graphical editor for this. If not already installed, the package is named "mozo" as is the tool itself. Otherwise you could try to edit the relevant .desktop files manually. -- Nito
Re: How to properly import the configuration of the Buster kernel into own development ?
On Sun, Aug 09, 2020 at 13:14:19 +0200, Thomas Schmitt wrote: > Hi, > > are people here who make their own kernels and know how to import the > configuration of the originally installed kernel ? > > What should i do in order to bring the configuration of the original Buster > kernel 4.19.0 to my experimental kernel which stems from the Buster package > "linux-source-4.19" ? > (There seem to be some new configuration options in the source kernel.) For Debian systems the kernel config is shipped in /boot as /boot/config-(versioan and variant). You can use this as a basis, if you are on stable, maybe grab a newer config from unstable or testing first to reduce the config-differences between mainline and Debian's config. Copy this config to your source tree as .config. Then update your config with: make oldconfig You'll be asked what to do about new config options that arent already ruled out by other selected options. (If you just want to select default for everything: make olddefconfig) Now you can treat it like every other (probably valid) config. > I got lured by > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html > into following > "generate a configuration based on the running kernel and the currently >loaded modules (make localmodconfig)" > which was obviously a poor decision. If you want to save yourself some trouble with localmod, start with a known good distribution config (like debian's) and plug in all devices you will ever use before you run make localmodconfig, to make sure necessary modules are loaded. You might still need to reenable some filesystems afterwards, if they weren't in use. Nito
Re: Установка Debian
On Wed, Sep 21, 2022 at 16:05:17 +0500, Костя Тарасов wrote: > Здравствуйте, устанавливаю debian 8, в пк установлена материнская плата MSI > H510M-A PRO, во время установки возникла ошибка, что программа установки не > обнаружила сетевую карту, сетевая карта интегрирована в материнскую плату, > дальнейшая установка невозможна, как быть в такой ситуации? Этот текст был переведен машинным переводом, извините, если он читается немного странно. MSI H510M-A PRO, похоже, довольно недавняя материнская плата, а Debian 8 (Jessie) был выпущен в 2015 году и больше не поддерживается. Попробуйте вместо него установить текущий “stable” Debian 11 (Bullseye). Но также, если какой-либо компонент, который вы хотите использовать, требует несвободной прошивки, вам нужно будет использовать альтернативный установочный образ, содержащий несвободную прошивку. Вы можете найти их здесь: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/ Также существует специальный русскоязычный список пользователей Debian: debian-russ...@lists.debian.org. Я думаю, что там будет проще получить помощь на русском языке (без необходимости машинного перевода). (Оригинальный непереведенный текст ниже.) ~ Original Text ~ This text was machine translated, sorry if it reads a bit odd. MSI H510M-A PRO appears to be a rather recent motherboard, while Debian 8 (Jessie) was released in 2015 and is no longer supported. Try installing the current “stable” Debian 11 (Bullseye) instead. But also, if any component you want to use needs non-free firmware, you will need to use the alternative installation image containing non-free firmware. You can find them here: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/ Also there's a dedicated Russian language user list for Debian: debian-russ...@lists.debian.org. I'd guess it will be easier to get help in Russian there (without needing machine translation).
Re: Fixing errors on a BTRFS partition?
On Thu, Jan 12, 2023 at 14:10:22 +, piorunz wrote: > To satiate your curiosity, you can find out what files are corrupted, some > of the errors are giving filenames. If not, this is my saved command to > obtain filename from inode numbers: > sudo btrfs inspect-internal inode-resolve 50845 / > > And obtain filename from logical error: > sudo btrfs inspect-internal logical-resolve -v 540115857408 / > > As far as I know, Btrfs may refuse to read file with wrong checksum, there > may be another command to do that. I believe mounting with -o rescue=all will allow to read corrupted files, so the remaining parts of non-replaceable files can be salvaged; though I fortunately never had to put this to test myself. Specifically the ignoredatacsums setting, see https://btrfs.readthedocs.io/en/stable/Administration.html#mount-options Note that this requires a sufficiently new kernel. On Thu, Jan 12, 2023 at 08:58:52 -0500, Dan Ritter wrote: > For the future: don't let things go this long. I know it's > tempting to say "maybe it won't happen again", but the second > time should be the last time before you take action. To add to this: usually it is recommended to regularly run `btrfs scrub` to detect (and in case of redunancy repair) data degradation. Running also `btrfs check` regularly to verify the fs structure also isn't a bad idea. This makes it more likely you'll notice a failing device before it gets as bad as it is now. > 2: Reinstall Debian on the new disk. Don't use btrfs on a > single-drive system; only use btrfs on a mirrored system. In most cases, > use ext4. For the record, I don't agree with BTRFS only being useful with RAID. BTRFS’ scrub and check can detect corruption early, rather then bitrot silently continuing until it starts crashing and there might be other features like e.g. transparent compression which might make it worthwhile for one’s single-device usecases. (In theory redunancy can also be used with a single device by creating the FS with the "dup" data profile, but this of course offers les protection than separate devices.)
Re: mkdir: cannot create directory ... : Invalid argument
On Sun, Feb 12, 2023 at 21:04:35 +, Albretch Mueller wrote: > while in the Windows NT directory: > [...] > mkdir: cannot create directory ‘WeltUndWirkungsprinzip2.Aufl.’: Invalid > argument > [...] > /dev/sda1 fuseblk 286G 274G 12G 96% /media/user/<...> > > [...] So, the problem > seems to relate to a dot as the last character of the name of a > subdirectory on Windows NT filesystems mounted by fuseblk. Is that the > case? I had never heard of such thing. Yes, Win32/NTFS has a bunch of arbitrary seeming path restrictions, magic normalisation and illegal names. A single or two trailing dot(s) are one of the things not valid in Win32 namepsace, in this case due to path normalisation. (There are special ways to bypass normalisation, but chances are you’d have trouble to interact with or even delete such a dir from Windows) See: https://learn.microsoft.com/en-us/archive/blogs/jeremykuhne/path-normalization and the relevant ntfs-3g option the mounting GUI probably uses: https://manpages.debian.org/bullseye/ntfs-3g/ntfs-3g.8.en.html#windows_names
