Bug#1001263: logind: IdleAction=ignore not effective

Thanks for the quick answer Michael; I see logind suspending the system but not because of "System idle": I have then to investigate what component is triggering such suspend after a certain inactivity time. I guess this bug can be therefore closed. Cheers, Andrea On Tue, Dec 7, 2021 at 11:55

Bug#935852: SOLVED

Through a lengthy I finally found this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448 Which hinted to the fact that "Heaphone Mic Boost" is to blame for this. Issuing: $ amixer -c 0 set 'Headphone Mic Boost',0 1 makes the problem totally disappear for me. But why it depends on

Bug#935852: Issue still present

Issue still there under linux-image-5.3.0-2-amd64 == 5.3.9-3. Currently, with the latest debian sid packages the kernel seems to be the culprit: as the static noise is NOT present with linux-image-4.19.0-5-amd64 == 4.19.37-6. Was this bug even reported upstream? Cheers, Andrea

Bug#897928:

see [2]. > > [1]: > > http://metadata.ftp-master.debian.org/changelogs/contrib/v/virtualbox/unstable_changelog > [2]: https://tracker.debian.org/pkg/virtualbox > > Best, > James > > On 2018-06-26 05:42 AM, Andrea Villa wrote: > > Any news on when virtualbox/5

Bug#897928:

Any news on when virtualbox/5.2.10-dfsg-7 will be uploaded to the Debian FTP? This bug is marked as resolved, but there is no package available to users with this bug fixed. Sincerely, Andrea

Bug#896888: #896888 - panics during start on protocol.DeviceIDFromBytes

The above seems to fix the issue indeed! Syncthing did a full rescan and complained about folder's ID mismatching though. On Thu, May 10, 2018 at 4:15 PM, Alexandre Viau wrote: > Apparently syncthing -reset-database should fix your issue. > > Cheers, > > -- > Alexandre Viau >

Bug#896888: panics during start on protocol.DeviceIDFromBytes

Package: syncthing Version: 0.14.46+ds1-1 Severity: grave Tags: upstream Justification: renders package unusable Syncthing refuses to start with the following error: [edited] 14:47:33 INFO: syncthing v0.14.46-ds1 "Dysprosium Dragonfly" (go1.10.1 linux-amd64) debian@debian 2018-04-04 18:28:29 UTC

Bug#888647: [pkg-lxc-devel] Bug#888647: lxc: unprivileged container doesn't boot due to cgroup ownership

Thanks for the reply Evgeni, On Sun, Jan 28, 2018 at 12:24 PM, Evgeni Golov <evg...@debian.org> wrote: > Hi Andrea, > > On Sun, Jan 28, 2018 at 11:34:03AM +0100, Andrea Villa wrote: > >Just create a simple user unprivileged lxc container after following >

Bug#888647: [pkg-lxc-devel] Bug#888647: lxc: unprivileged container doesn't boot due to cgroup ownership

On Sun, Jan 28, 2018 at 12:24 PM, Evgeni Golov <evg...@debian.org> wrote: > Hi Andrea, > > On Sun, Jan 28, 2018 at 11:34:03AM +0100, Andrea Villa wrote: > > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > > > >

Bug#888647: lxc: unprivileged container doesn't boot due to cgroup ownership

Package: lxc Version: 1:2.0.7-2+deb9u1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? Just create a simple user unprivileged lxc container after following the official Debian documentation https://wiki.debian.org/LXC# Unprivileged_container. Container

Bug#869670: Dependency missing

The reason for this bug is a dependency problem: The current sid kernel is linux-image-4.11.0-2-amd64 -> corresponding headers are linux-headers-4.11.0-2-amd64: -> they depend on linux-headers-4.11.0-2-common (= 4.11.11-1+b1) -> there is no such version (only 4.11.11-1 *NO +b1*), maybe never made

Bug#866863: Mainters active?

Are bugs for this package addressed at all? I don't see any answer to even old bugs...

Bug#866863: Debug output

Here is the --debug output of the daemon failing on assigning the mentioned CGroups: EXEC Event: PID = 17096, tGID = 17096 Scanned proc values are 1000 1000 1000 1000 Scanned proc values are 1000 1000 1000 1000 Found matching rule karimo

Bug#865998: Info received ()

I think the severity of this bug should be increased, it makes the package unusable. On Tue, Jun 27, 2017 at 6:51 PM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically

Bug#865998:

I report the same issue. cgmanager.service fails to start. As I result I cannot launch any of the unpriviledged LXC containers on my system.

Bug#843427:

I can confirm that systemd.legacy_systemd_cgroup_controller is not necessary anymore. With systemd 232-3, /sys/fs/cgroup/systemd mounts with cgroup instead of cgroup2.

Bug#843524:

Report on OSdir: http://osdir.com/ml/general/2016-10/msg40775.html libtorrent-rasterbar9 1.1.1-1 breaks QBittorrent.

Bug#843427:

I can confirm that adding systemd.legacy_systemd_cgroup_controller in GRUB_CMDLINE_LINUX_DEFAULT inside /etc/default/grub effectively works around the issue. systemd's Cgroup is infact mounted under cgroup hierarchy now: $ mount | grep systemd cgroup on /sys/fs/cgroup/systemd type cgroup

Bug#843524:

The GH issue thread https://github.com/qbittorrent/qBittorrent/issues/5905 didn't actually reveal if this is a Debian-specific problem or not; in fact a user reported this also on an Arch-based distro. Most of the affected users are Debian though. Should we remove the upstream tag?

Bug#843427: [pkg-lxc-devel] Bug#843427: Bug#843427: Bug#843427: lxc-ls -f aborts with Glibc invalid pointer to free()

I will give that a shot, although a bit of an obscure toggle, doesn't seem to be documented anywhere. On Mon, Nov 7, 2016 at 12:59 PM, Evgeni Golov wrote: > On Mon, Nov 07, 2016 at 12:20:55PM +0100, Evgeni Golov wrote: > > > As explained by the GH thread

Bug#843427: [pkg-lxc-devel] Bug#843427: lxc-ls -f aborts with Glibc invalid pointer to free()

Thanks for your reply Evgeni, I can confirm that the issue is related to the /sys/fs/cgroup/systemd to be mounted under the cgroup2 hierarchy with systemd 232-2. The 4.8 kernel doesn't play a role here: I tried to revert to an older snapshot with systemd 231-10 and 4.8 kernel and lxc behaves

Bug#843427:

Just as an extra detail: the -f switch is not required to produce this behaviour. A simple execution of lxc-ls without arguments produces the same effect.

Bug#836734:

My experience is similar to yours. Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838491 I filed. Do you also report crazy-high load averages?

Bug#796149: i3: fullscreened Virtualbox VM shows black screen

Package: i3 Version: 4.10.3-1 Severity: normal After upgrade to Virtualbox 5, fullscreened VMs show black fullscreen window under i3 wm. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures:

Bug#791604: python-z3: __init__.py is missing in the base module folder. This makes the module not importable.

Package: python-z3 Version: 4.4.0-1 Severity: grave Tags: patch Justification: renders package unusable It is enough to touch a __init__.py file inside /usr/lib/python2.7/dist-packages/z3/ to make the module importable. -- System Information: Debian Release: stretch/sid APT prefers unstable

Bug#786519:

Pinning to the stable libwine (1.6.2-20) might be the only option for now: -- Package: libwine libwine:i386 Pin: release a=stable Pin-Priority: 700 -- You may want to either remove and install against pin or increase Priority to force downgrade from

Bug#676509: Any followup?

Hello everybody, was just looking at this today and wondered if it got any further. Cheers, Andrea

Bug#732568: Same Kernel, Same Run, Another distro: works

I wanted to add that mount-binding /dev /proc /sys and chrooting into a Slackware 14.1 with cryptsetup 1.4.3 worked. Don't know if this could be useful, but this way we can exclude a kernel-related problem.

Bug#732568: cryptsetup-bin: luksFormat fails to initalize KeySlot

Package: cryptsetup-bin Version: 2:1.6.1-1 Severity: important When trying to format a luks partition the cryptsetup command fails with the following error. I tried with two different USB drives (one with a DOS partition table and the other with GPT partition table).