Bug#965932: libc6: breaks openssh-server/buster

Package: libc6 Version: 2.31-1 Followup-For: Bug #965932 Having the same issue, found an additional tidbit that may be of use: When the failure happens, kernel logs a line like this: Jul 20 20:04:38 hostname kernel: [ 373.963787] audit: type=1326 audit(1595289878.694:7): auid=4294967295

Bug#837788: munin: systemd control scripts are missing

On Fri, 10 Mar 2017, Simon McVittie wrote: However, Matthew Gabeler-Lee's reply: I argue this merits worse than "important" -- in a default install of Stretch currently, munin doesn't work at all. suggests that there may be something else going on. Matthew, please could you describe what

Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google.

Package: pepperflashplugin-nonfree Followup-For: Bug #833741 This is a grave issue for existing installations as well, as it is thus impossible to upgrade them away from the releases that have critical security vulnerabilities actively being exploited in the wild.

Bug#817929: mosh fails to connect, giving a UDP error

On 03/24/2016 12:31 AM, john hood wrote: > I haven't been able to chase these glibc details down. Do you have > pointers to specifics for this? My assessment was based just on reading the referenced glibc-help thread, and the commit it referenced --

Bug#817929: mosh fails to connect, giving a UDP error

On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli wrote: > Please give a look to > > https://sourceware.org/ml/libc-help/2016-03/msg00010.html > > to me it seems that the real problem is in glibc. >From reading that thread and looking at the referenced git commit, I'm

Bug#817929: mosh fails to connect, giving a UDP error

Package: mosh Version: 1.2.5-1.1 Followup-For: Bug #817929 Looks like upstream has a patch for this: https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790 Though it looks like that's a hack and they really want this fixed in protobuf:

Bug#808466: update error at configure

Package: redmine Version: 3.0~20140825-8 Followup-For: Bug #808466 I believe this may be related to rails updating to 4.2.x in testing, whereas redmine seems to still be searching for 4.1.x given the error message? Hacking on /usr/share/redmine/Gemfile to change it to look for 4.2.x (making the

Bug#747863: systemd service fails by default and causes package install failure

On Sun, 1 Mar 2015, Sebastian Harl wrote: I think that MODE=none should no longer be a valid option when using systemd as you'd then use 'systemctl disable' instead. I don't know systemd very well, so there could be other options as well and/or maybe a way to disable upsmon in systemd by

Bug#747863: systemd service fails by default and causes package install failure

Package: nut-client Version: 2.7.2-3 Followup-For: Bug #747863 Unfortunately this bug is still present. A virgin install of nut-client results in a service start failure and thus package install failure. $ sudo systemctl status nut-monitor.service ● nut-monitor.service - Network UPS Tools -

Bug#759777: closed by Sebastian Reichel s...@debian.org (Bug#759777: fixed in tt-rss 1.15+dfsg-1)

reopen 759777 thanks This is not fully fixed. Special feeds and folders have no icons still. Menu roll-overs are better, but still have some detritus around the edges. Worse yet, now downgrading dojo to 1.7 makes tt-rss refuse to run, and dojo 1.9 (what's marked as required now) was never

Bug#759777: closed by Sebastian Reichel s...@debian.org (Bug#759777: fixed in tt-rss 1.15+dfsg-1)

Also broken are several pieces of horizontal layout. Items that are supposed to be right aligned to the viewport, causing leftwards items to be shortened, are instead often pushed off creating horizontal scrolling. This happens on both the left pane when expanding categories (often making _all_

Bug#769716: Give users option to download OpenH264?

Totally disabling this feature seems very user-unfriendly :( Digging in, clearly this can be re-enabled via about:config, perhaps this merits a NEWS entry to alert users to this? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#766359: gnome-shell: gdm shows a black screen when upgrading to 3.14.1-1

Package: gnome-shell Version: 3.14.1-1 Followup-For: Bug #766359 I too encountered this problem. By checking syslog, I eventually tracked it down to a missing dependency on the 3.14.1 version of libmutter0e: gnome-session[22789]: (gnome-shell:22822): Gjs-WARNING **: JS ERROR: GLib.Error

Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot

Package: laptop-mode-tools Version: 1.65-2 Severity: serious Justification: Breaks normal system boot The lmt-udev script appears to be breaking systemd boot for me due to introducing a deadlock / dependency circle. Based on usage of debug-shell.service, it appears that systemd is waiting for

Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot

severity 755518 normal reopen 755518 retitle 755518 laptop-mode-tools: fails to boot when /usr is on LVM quit On Mon, 21 Jul 2014, Ritesh Raj Sarraf wrote: On 07/21/2014 09:50 PM, Matthew Gabeler-Lee wrote: Removing laptop-mode-tools causes my system to boot properly. In the 1.65-2 release

Bug#703472: iceweasel freezes in _MD_WaitUnixProcess after mailcap test command terminates

Package: iceweasel Version: 26.0-1 Followup-For: Bug #703472 I've found a workaround for this issue, for both iceweasel and icedove. Launch the app from a terminal (xterm, etc.), backgrounded, and then dismiss the terminal. I.e. open a terminal and run iceweasel or icedove , and then exit.

Bug#713612: vdpau-video: FTBFS: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC'

Package: vdpau-video Version: 0.7.3-2 Followup-For: Bug #713612 I know debian-multimedia.org is persona non grata in some portions of the debian circle, but they do have patches for this (and other FTBFS problems) in vdpau-video-dmo 0.7.4-dmo1. The dmo patches for 0.7.4 apply cleanly to the

Bug#703472: iceweasel freezes in _MD_WaitUnixProcess after mailcap test command terminates

Package: iceweasel Version: 26.0-1 Followup-For: Bug #703472 I'm not sure how to represent this to the debian BTS (clone this bug?), but it appears that this also affects icedove, at least version 24.1.1-1. -- Package-specific info: -- Extensions information Name: Adblock Plus Location:

Bug#714279: fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization.

Package: fontconfig-config Version: 2.10.2-2 Followup-For: Bug #714279 I encountered the same problems. By fiddling some configuration bits, I was able to restore the previous good font rendering: 1. Fix the symlink for /etc/fonts/conf.d/11-lcdfilter-default.conf (it was pointing to

Bug#702715: tortoisehg: broken pyqt4 version check

Package: tortoisehg Version: 2.4-2 Severity: grave Followup-For: Bug #702715 This bug has now landed. As the packages in testing / unstable now stand, you cannot use tortoisehg. Even worse, for reasons I cannot quite understand, it does not print any error message about this situation, nor does

Bug#702977: tt-rss: Missing Depends: libphp-simplepie

Package: tt-rss Version: 1.7.2+dfsg-1 Severity: grave Justification: renders package unusable tt-rss needs simplepie to do anything with RSS feeds, AFAICT. But the package does not have a Depends, or even a Recommends or Suggests on libphp-simplepie. Without that package, I cannot subscribe to

Bug#600739: dh-make-drupal: More Info

Package: dh-make-drupal Version: 0.7-1 Severity: normal I'm seeing this too. I did a little deeper looking, and I believe the problem is ocurring around line 828 of dh-make-drupal: # Get the project description. Fetch only the first paragraph - # This is usually enough for the

Bug#447172: lirc-modules-source: More information

Package: lirc-modules-source Version: 0.8.2-1 Followup-For: Bug #447172 I saw this problem too. It looks like it is including the automake-generated makefile for drivers/Makefile, with no include to get the kernel build rules. Items in debian/rules and elsewhere indicate that there were in the

Bug#392472: gpar2: Which Package?

Package: gpar2 Version: 0.3-2 Followup-For: Bug #392472 AFAICT, all packages gpar2 depends on directly are up to date in testing, and I'm seeing the same error as the original reporter. Which package specifically needs to be update to work properly with gpar2? If it depends on a particular