Bug#1010038: monitoring-plugins-basic: check_ide_smart introduces risk of data loss
Package: monitoring-plugins-basic Severity: normal Tags: upstream X-Debbugs-Cc: atga...@gmail.com Dear maintainer, I've been relying on check_ide_smart for some time to monitor my HDDs and up to now there has never been a malfunction reported, with all disks being reported as passing all tests and in the OK status. While setting up a new server I've found two issues with this plugin that I think should be enough to mark it as deprecated, both in Debian and in upstream: - It just doesn't recognize drives connected through an HBA, even though smartctl does. This is a known limitation of the plugin. - When using a more up to date alternative, I've found that some of the HDDs that check_ide_smart was reporting as OK have in fact reached some pre-failure conditions and are worth replacing. This isn't related to the hardware interface as those drives are in production and have been monitored with check_ide_smart for quite some time, I've just changed the monitoring plugin. So, as check_ide_smart isn't properly reporting HDD status (or, at least, failing to report early warnings) I believe keeping it available as is introduces the risk for a potential data loss. There are alternatives available, so I suggest to consider substituting the plugin instead of updating it. The best I've found is Kurt Yoder and Claudio Kuenzler's check_smart[1][2], but I'm not sure of the licensing status (the code shows that "This script was initially created under contract for the US Government and is therefore Public Domain", but there's no specific license mentioned). Regards. [1]https://www.claudiokuenzler.com/monitoring-plugins/check_smart.php [2]https://exchange.nagios.org/directory/Plugins/System-Metrics/Storage- Subsystem/check_smart-2Epl--2D-physical-drive-monitoring/details -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages monitoring-plugins-basic depends on: ii iputils-ping 3:20211215-1 ii libc6 2.33-7 ii libssl1.1 1.1.1n-1 pn monitoring-plugins-common ii procps 2:3.3.17-7+b1 ii ucf3.0043 Versions of packages monitoring-plugins-basic recommends: ii libcap2-bin 1:2.44-1 Versions of packages monitoring-plugins-basic suggests: pn icinga2
Bug#1002746: thinkfan: Please update to new upstream
Package: thinkfan Version: 1.2.1-3.1+b2 Severity: normal X-Debbugs-Cc: atga...@gmail.com Dear maintainer, 1.2.1 is afected by a bug that prevents monitoring "optional" sensors, including the current handling of discrete GPUs with bumblebee/primus, that has been apparently solved in upstream's 1.2.2. Furthermore, upstream has released 1.3.0 addressing a couple more bugs. Please consider upgrading at least to 1.2.2. Thanks in advance. -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thinkfan depends on: ii init-system-helpers 1.61 ii libatasmart4 0.19-5 ii libc62.33-1 ii libgcc-s111.2.0-13 ii libstdc++6 11.2.0-13 ii libyaml-cpp0.7 0.7.0+dfsg-8 thinkfan recommends no packages. thinkfan suggests no packages. -- no debconf information
Bug#945958: gnome-builder: Changes to modified&unsaved files are when closing
Package: gnome-builder Version: 3.32.4-2 Severity: important Tags: upstream Hi, While editing source files, if the user closes an editor pane before saving changes to that file the pane is closed without saving changes or asking the user for confirmation to save or discard changes, so every last minute changes after the last autosave (if active) are lost without notice. This also happens when closing the program, this time affecting every unsaved file still open. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-builder depends on: ii clang1:8.0-48.3 ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii exuberant-ctags 1:5.9~svn20110310-12 ii gir1.2-dazzle-1.03.34.1-1 ii gir1.2-ggit-1.0 0.28.0.1-1+b1 ii gir1.2-glib-2.0 1.62.0-2 ii gir1.2-gtk-3.0 3.24.12-1 ii gir1.2-gtksource-4 4.4.0-1 ii gir1.2-jsonrpc-1.0 3.34.0-1 ii gir1.2-peas-1.0 1.22.0-4 ii gir1.2-template-1.0 3.34.0-1 ii gir1.2-vte-2.91 0.58.2-1 ii gir1.2-webkit2-4.0 2.26.2-dmo1 ii libatk1.0-0 2.34.1-1 ii libc62.29-3 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libclang1-8 1:8.0.1-4 ii libdazzle-1.0-0 3.34.1-1 ii libdevhelp-3-6 3.34.0-1 ii libenchant1c2a 1.6.0-11.3 ii libflatpak0 1.4.3-1 ii libfontconfig1 2.13.1-2+b1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1 ii libgirepository-1.0-11.62.0-2 ii libgit2-glib-1.0-0 0.28.0.1-1+b1 ii libgladeui-2-6 3.22.1-4 ii libglib2.0-0 2.62.3-1 ii libgspell-1-11.6.1-2 ii libgtk-3-0 3.24.12-1 ii libgtksourceview-4-0 4.4.0-1 ii libjson-glib-1.0-0 1.4.4-2 ii libjsonrpc-glib-1.0-13.34.0-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpangoft2-1.0-01.42.4-7 ii libpcre3 2:8.39-12+b1 ii libpeas-1.0-01.22.0-4 ii libsoup2.4-1 2.68.2-1 ii libtemplate-glib-1.0-0 3.34.0-1 ii libvala-0.46-0 0.46.5-1 ii libvala-0.46-dev [libvala-dev] 0.46.5-1 ii libvte-2.91-00.58.2-1 ii libwebkit2gtk-4.0-37 2.26.2-dmo1 ii libxml2 2.9.4+dfsg1-8 ii python3 3.7.5-1 ii python3-gi 3.34.0-3 ii sysprof 3.32.0-2 Versions of packages gnome-builder recommends: ii build-essential 12.8 ii flatpak-builder 1.0.9-1 ii gettext 0.19.8.1-10 ii meson0.52.0-2 ii pkg-config 0.29-6 ii python3-jedi 0.14.1-1 ii python3-lxml 4.4.1-1+b1 ii valgrind 1:3.15.0-1 gnome-builder suggests no packages. -- no debconf information
Bug#939606: linux-image-5.2.0-2-amd64: Fails to shutdown/reboot/suspend
x-doc-5.2 Versions of packages linux-image-5.2.0-2-amd64 is related to: ii firmware-amd-graphics 20190717-2 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20190717-2 pn firmware-libertas ii firmware-linux-nonfree20190717-2 ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information El sáb., 7 sept. 2019 a las 20:28, Ben Hutchings () escribió: > Control: tag -1 moreinfo > > Does this still happen if you remove the bbswitch module? > > Ben. > > -- > Ben Hutchings > The most exhausting thing in life is being insincere. > - Anne Morrow Lindberg > > > -- Antonio Trueba atga...@gmail.com
Bug#939606: linux-image-5.2.0-2-amd64: Fails to shutdown/reboot/suspend
Package: src:linux Version: 5.2.9-2 Severity: important Tags: upstream After installing and booting kernel 5.2.0-2 everything seems to be running OK until I try to shutdown or suspend the machine, either via the UI's shutdown options or via command-line. What happens then is: - Trying to shutdown or reboot: the system enters the normal shutdown sequence, closes all running programs and services normally, completes the shutdown sequence and shows the message "Reached power-off" or "Reached reboot" and stops there, never actually powering off nor rebooting the machine. In order to complete the action, I need to press the power button for about 10 seconds until the BIOS cuts the power and then press again to restart. - Trying to suspend: The suspend sequence normally shows no progress messages, and even if it did what I normally do is close the lid and Gnome triggers a suspend to RAM. This laptop has a LED (a Lenovo thinklight) that shows the power state. On previous kernels, a couple of seconds after ordering the suspend action, this LED changes from solid on (which indicates the system is running) to a slow blink, which indicates the machine is a suspended state. With kernel 5.2.0 it seems that the suspend sequence is initiated, but instead of the slow blink the LED start to flash rapidly (which indicates that the system is entering hibernation state),and stays in that state. The machine does not respond to wakeup events, and I need to force a shutdown via long-pressing the power button. This started happening with the first installation of a 5.x kernel. If I reboot the system with a current 4.x kernel (4.19.0-5 as of now), everything works OK. My guess is that the kernel is not issuing the correct orders to the BIOS in order to complete those actions. Either the new 5.x kernel series has changed the power management strategy in some way breaking those calls to the BIOS, which would be an upstream error, or is relying in a new software package which is not normally installed in a 4.x-based system such as buster to complete those calls, which will lead to this problem when the user wants to upgrade to testing/unstable or when 5.x reaches stable. -- Package-specific info: ** Version: Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21) ** Command line: BOOT_IMAGE=/vmlinuz-5.2.0-2-amd64 root=/dev/mapper/urco--vg-root ro quiet ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [4.035204] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input23 [4.035261] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input24 [4.035323] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input25 [4.035368] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input26 [4.035416] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input27 [4.035466] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input28 [4.035516] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input29 [4.069239] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [4.069724] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized! [4.069726] uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not initialized! [4.069728] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized! [4.069729] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized! [4.069827] input: Integrated Camera: Integrated C as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input30 [4.069944] usbcore: registered new interface driver uvcvideo [4.069945] USB Video Class driver (1.1.1) [4.150576] iwlwifi :03:00.0: base HW address: 88:b1:11:0b:22:eb [4.205370] Bluetooth: Core ver 2.22 [4.205384] NET: Registered protocol family 31 [4.205385] Bluetooth: HCI device and connection manager initialized [4.205388] Bluetooth: HCI socket layer initialized [4.205392] Bluetooth: L2CAP socket layer initialized [4.205395] Bluetooth: SCO socket layer initialized [4.221372] usbcore: registered new interface driver btusb [4.230616] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [4.237610] Bluetooth: hci0: Device revision is 5 [4.237624] Bluetooth: hci0: Secure boot is enabled [4.237624] Bluetooth: hci0: OTP lock is enabled [4.237625] Bluetooth: hci0: API lock is enabled [4.237625] Bluetooth: hci0: Debug lock is disabled [4.237626] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [4.239798] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi [4.239803] Bluetooth: hci0: Found device
Bug#878165: Fixed upstream, update package
Hi, It seems this bug is gone with kernel version 4.16.0-2 and firmware iwlwifi-8000C v36. Please consider updating the firmware version in this package. Regards.
Bug#878165: firmware-iwlwifi: Some firmware versions cause 8260 Bluetooth malfunction
Package: firmware-iwlwifi Version: 20170823-1 Followup-For: Bug #878165 Hi, I can confirm this bug, it's root cause seems to be interference between 2.4GHz wifi and bluetooth. In my case, I have 2 wifi networks in range, one in 5GHz range and the other in 2.4GHz range. My main network is the 5GHz one, and while connected to it there's no problem with my bluetooth mouse. However, from time to time the laptop roams to the 2.4GHz one and there appears the interference. With firmware-iwlwifi's version 20170823-1 (which contains firmware v31 of iwlwifi-8000C), the bluetooth mouse is inmediately disconnected and the only way to reconnect is to reboot the laptop. Note that connecting back to the 5GHz network doesn't solve the problem, it seems that the bluetooth stack somehow gets stuck. On the other hand, version 20161130-3 contais v28 of the firmware. In this case, connecting to a 2.4GHz network causes some interference with the mouse (mainly erratic movements), but after completing the connection both radios can coexist (although there is some interference from time to time). Connecting back to 5GHz restores everything to normal. There's a newer version (v34) of the firmware in the kernel's github, but unfortunately current Debian's kernel doesn't support it. For the time being, it seems that our best solution is to force loading v28 of the firmware, either by: - downgrading firmware-iwlwifi to 20161130-3 or - manually removing /lib/firmware/iwlwifi-8000C.ucode-31.ucode, so the system will fall back to v28 instead or - somehow instruct the kernel to prefer v28 over v31, but I don't know if that can be done Regards. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.130 -- no debconf information
Bug#883341: slic3r: Missing dependencies: wx-common, libopengl-perl, libwx-glcanvas-perl
Package: slic3r Version: 1.2.9+dfsg-8 Severity: grave Justification: renders package unusable Dear Maintainer, After installation, slic3r gui fails to start due to missing dependencies. Installing the following packages solves the problem: - wx-common - libopengl-perl - libwx-glcanvas-perl -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages slic3r depends on: ii libboost-geometry-utils-perl 0.15-2+b6 ii libc6 2.25-2 ii libencode-locale-perl 1.05-1 ii libgcc11:7.2.0-16 ii libio-stringy-perl 2.111-2 ii libmath-convexhull-monotonechain-perl 0.1-1+b6 ii libmath-geometry-voronoi-perl 1.3-2+b5 ii libmath-planepath-perl 124-1 ii libmoo-perl2.003002-1 ii libperl5.26 [libtime-hires-perl] 5.26.1-2 ii libstdc++6 7.2.0-16 pn libstorable-perl ii perl 5.26.1-2 ii perl-base [perlapi-5.26.0] 5.26.1-2 Versions of packages slic3r recommends: pn libclass-xsaccessor-perl pn libio-all-perl ii libopengl-perl0.7000+dfsg-1 pn libpdf-api2-perl pn libsvg-perl ii libwx-glcanvas-perl 0.09-3+b5 ii libwx-perl1:0.9932-2 pn libxml-sax-expatxs-perl slic3r suggests no packages. -- no debconf information
Bug#869271: flightgear-data-base: Soft-link to tzdata should be absolute
Package: flightgear-data-base Version: 1:2017.2.1+dfsg-2 Severity: important Dear Maintainer, file /usr/share/games/flightgear/Timezone is a soft link to tzdata's files, with a relative path "../../zoneinfo", which works OK in a standard installation. Due to this game's disk requirement's I've decided to move /usr/share/games folder to a separate partition, and soft-link it to it's new home. This resulted in fgfs failing to start with an erorr: "unable to find Timezone/zone.tab", due to the previous soft-link now incorrectly pointing to a non-existing relative path. Changing that soft-link to point to the absolute path "/usr/share/zoneinfo" solves the problem and the game can start normally again. I suggest to change that link in the installation package since, given the disk requirements of this game, many users would be tempted to proceed as I did in order to save a significant amount of free space in root partition. Thanks. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flightgear-data-base depends on: ii fonts-liberation 1:1.07.4-2 ii tzdata2017b-2 flightgear-data-base recommends no packages. flightgear-data-base suggests no packages. -- no debconf information
Bug#844006: gnome-system-monitor: Memory usage statistic may be wrong
Package: gnome-system-monitor Version: 3.22.0-1 Severity: important Dear Maintainer, In the "resources" page, the memory graphs in my system are showing a different value than those of top: at the time, g-s-m is showing 1.0 GiB used (28,3%) out of 3,7 GiB, while "top" running in a terminal is showing "3845332 total, 1731960 free, 697804 used, 1415616 buff/cache". I've been getting those readings recently with a freshly booted system, and I consider them a little too high for my system, so lately I've been trying to reduce that memory usage, to little or no result. As it happens, these last days I've tested a few live distros in this machine, including Jessie with a very similar setup as that of my regular system, and found the memory usage to range between 600-700 MiB in those setups. After comparing those readings to the present "top" output, I think this version of gnome-system-monitor is somehow miscalculating the memory usage. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-system-monitor depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2 ii libc62.24-5 ii libcairo21.14.6-1.1 ii libgcc1 1:6.2.0-13 ii libgdk-pixbuf2.0-0 2.36.0-1 ii libglib2.0-0 2.50.2-1 ii libglibmm-2.4-1v52.50.0-1 ii libgtk-3-0 3.22.3-1 ii libgtkmm-3.0-1v5 3.22.0-1 ii libgtop-2.0-10 2.34.1-2 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii librsvg2-2 2.40.16-1 ii libsigc++-2.0-0v52.10.0-1 ii libstdc++6 6.2.0-13 ii libsystemd0 232-3 ii libwnck-3-0 3.20.1-2 Versions of packages gnome-system-monitor recommends: ii gvfs 1.30.2-2 gnome-system-monitor suggests no packages. -- no debconf information
Bug#837201:
Hi, > Andreas Kloeckner writes: > > Michael Biebl writes: > > > >> [ Unknown signature status ] > >> Am 10.09.2016 um 02:27 schrieb Andreas Kloeckner: > >>> Package: systemd > >>> Version: 231-4 > >>> Severity: normal > >>> > >>> Dear Maintainer, > >>> > >>> on my system, the following happens (from journalctl -e) on trying to > start the > >>> services in the subject. > >>> > >>> -- > >>> Sep 09 19:04:17 bolt systemd[2685]: systemd-hostnamed.service: Failed > at step NAMESPACE spawning /lib/systemd/systemd-hostnamed: Too many levels > of symbolic links > >> > >> Is /home or /tmp a symbolic link? > >> How exactly does the /var/run symlink look like > >> > >> Please post the output of > >> # ls -ld /home /tmp /var/run > > > > Thanks for your response! > > > > # ls -ld /home /tmp /var/run > > drwxr-xr-x 3 root root 4096 Jun 25 13:38 /home > > drwxrwxrwt 13 root root 36864 Sep 10 11:40 /tmp > > lrwxrwxrwx 1 root root 5 Sep 9 19:25 /var/run -> /run/ > So, it turns out that my /root directory was a symlink. And that's what > was causing all this grief. Fixed now, thanks for your help. > Andreas I've also been bitten by this bug, in my case /home was a symlink. Upstream reports the bug as closed[1] few weeks ago, but it seems to be still present in latest Debian package (231-10). Can anyone confirm that this patch is included in that version, or will it be included in a future one? [1] https://github.com/systemd/systemd/issues/567 Thanks, -- Antonio Trueba atga...@gmail.com
Bug#824492: nautilus: Nautilus ignores setting to not create thumbnail of remote files
Package: nautilus Version: 3.20.1-2 Severity: normal Tags: upstream Dear Maintainer, My nautilus preferences are set to create previews of local files only, and even then only for filesizes 10 MB or less but, while browsing a LAN sftp share, nautilus is creating previews of everything, even files well over 500 MB. Remote FS is mounted through gvfs or gvfs-fuse (not sure), but in any case I think nautilus is aware that it is a remote share, as the location bar shows sftp://foo/bar -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nautilus depends on: ii desktop-file-utils 0.22-1 ii gsettings-desktop-schemas 3.20.0-3 ii gvfs 1.28.2-1 ii libatk1.0-02.20.0-1 ii libc6 2.22-9 ii libcairo-gobject2 1.14.6-1+b1 ii libcairo2 1.14.6-1+b1 ii libexempi3 2.3.0-2 ii libexif12 0.6.21-2 ii libgail-3-03.20.4-1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.1-1 ii libglib2.0-data2.48.1-1 ii libgnome-desktop-3-12 3.20.2-1 ii libgtk-3-0 3.20.4-1 ii libnautilus-extension1a3.20.1-2 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-01.40.1-1 ii libselinux12.5-2 ii libtracker-sparql-1.0-01.8.0-2+b1 ii libx11-6 2:1.6.3-1 ii nautilus-data 3.20.1-2 ii shared-mime-info 1.6-1 Versions of packages nautilus recommends: ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-sushi3.19.90-1 ii gvfs-backends 1.28.2-1 ii librsvg2-common2.40.15-1 Versions of packages nautilus suggests: ii brasero 3.12.1-1 ii eog 3.20.2-1 ii evince [pdf-viewer] 3.20.0-3 ii totem3.20.1-2 ii tracker 1.8.0-2+b1 pn xdg-user-dirs -- no debconf information
Bug#819371: Please depend on "firefox | firefox-esr" rather than the reverse
On Sun, 27 Mar 2016 10:43:02 -0700 Josh Triplett wrote: > Package: gnome-core > Version: 1:3.14+4 > Severity: wishlist > > gnome-core depends on "firefox-esr | firefox". However, the firefox > package already only exists in unstable; users of testing and stable > only have firefox-esr available. If gnome-core depended on "firefox | > firefox-esr", users of unstable would get firefox installed, while users > of testing or stable would still get firefox-esr. Assuming those users > continue running unstable, they'll get timely updates for the firefox > package, so no concern about becoming unsupported. > > This would also make it easier for users like me who have metapackages > depending on both gnome and "firefox | iceweasel" (to support both > unstable and stable). With those dependencies, I end up with both > firefox and firefox-esr installed; with gnome-core's dependencies > swapped around, I'd end up with only firefox installed. I think a better approach would be to depend on gnome-www-browser instead, or at least include it as an alternative to a default browser. The point is, I prefer chromium rather than firefox, and I guess other people do also, but installing gnome-core forces me to keep both browsers installed. Given that neither is part of the gnome project and both provide gnome-www-browser (as does epiphany-browser[1]), I think that gnome-core should at least let the user decide. I know there's the posibility to uninstall gnome-core and keep all its dependencies as manual selections, but in the long (medium?) run that would mean that the system will be out of sync with gnome-core, as there could be additions/removals to the package list that are considered to represent "core gnome". BTW, this bug is related/duplicates #662150. [1] From a gnome point of view, I think the natural setting should be "epiphany-browser | gnome-www-browser", but I believe eppiphany fell off that list because of security issues a while ago. Don't know if that problem is still there. -- Antonio Trueba atga...@gmail.com
Bug#748978: transmission-daemon: segfaults in libgnutls.so.28 due to offending tracker
Package: transmission-daemon Version: 2.82-1.1 Severity: important Hi, I've been suffering frequent segfaults in transmission-daemon recently, usually when adding new torrent files or soon after. Crash log says: transmission-da[14287]: segfault at 0 ip b70f4802 sp b58fedf0 error 4 in libgnutls.so.28.30.5[b706c000+10c000] And the program keeps crashing everytime I restart it. The only solution is to find the offending torrent file, remove it from the download list and restart the program. A little trial and error led me to think that the problem is in one of the trackers referred in those torrent files, maybe a malformed response from the server or an unhandled error in the communication. Removing those trackers from the .torrent file seems to solve the problem, but as it's not a trivial task I guess there's a need to debug the actual problem and make tranmission handle the error, maybe just ignore those offending trackers. With the downloads I have running at the moment, I needed to remove two trackers to avoid the segfault: *.sumotracker.com: my ISP resolves this server to 127.0.0.2, so I guess there may be a 404 error or a dropped connection *.thepiratebay.org: This server resolves to a valid IP (194.71.107.50) but seems to be down, unresponding or blocked by ISP Possibly this bug affects upstream, and may be related to other segfault reports. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages transmission-daemon depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.18 ii libc62.18-5 ii libcurl3-gnutls 7.36.0-2 ii libevent-2.0-5 2.0.21-stable-1 ii libminiupnpc81.6-3 ii libnatpmp1 20110808-3 ii libssl1.0.0 1.0.1g-4 ii libsystemd-daemon0 204-8 ii lsb-base 4.1+Debian12 ii transmission-common 2.82-1.1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages transmission-daemon recommends: ii transmission-cli 2.82-1.1 transmission-daemon suggests no packages. -- Configuration Files: /etc/transmission-daemon/settings.json changed [not included] -- no debconf information -- Antonio Trueba atga...@gmail.com
Bug#534481: [Pkg-dia-team] Bug#534481: dia 0.97-2 eats up all system memory
Hi Roland, Tested with several objects at random, the problem seems to be zooming while antialias feature is enabled. Try the following: - Start with a blank canvas (my default here is A3 size, guess the problem isn't related to this) - Add a "regval" object from "chemeng" sheet. - Zoom in & out, resize or move at random, the memory usage should stay moreless stable (~30MB here). - Enable antialias - Zoom in & out to random scales, the memory usage starts increasing (~35MB). - Resize the object to a big scale, say half the canvas' paper size. - Zoom at random again, the memory usage grows faster this time. Performing as above with just one object may not eat up memory too fast, but drawing three of four simple objects speeds things way up. Also, I found no differences while playing with the object's properties, nor when playing as above without antialias feature. Also, if you close the diagram but keep dia's toolbar open the memory is not freed. Hope this helps. 2009/6/24 Roland Stigge > Hi Antonio, > > Antonio Trueba wrote: > >> While editing simple diagrams, dia's memory consumption grows way too >> much. >> >> After adding two or three standard objects to a blank canvas, modifying >> some of their properties and zooming >> >> in and out a couple of times, the program ate all available RAM (1,5GB) >> and about 500MB of swap >> before I had to kill it. Reverting dia-gnome, dia-common and dia-libs back >> to 0.96.1 everything >> went back to normal, with memory usage around 30MB. >> > > Thanks for your report. Unfortunately, I can't reproduce this. Can you > please tell me which objects and properties you changed before zooming in > and out? > > Thanks in advance, > > Roland > Regards, -- Antonio Trueba atga...@gmail.com
Bug#534481: dia 0.97-2 eats up all system memory
Package: dia-gnome Version: 0.97-2 While editing simple diagrams, dia's memory consumption grows way too much. After adding two or three standard objects to a blank canvas, modifying some of their properties and zooming in and out a couple of times, the program ate all available RAM (1,5GB) and about 500MB of swap before I had to kill it. Reverting dia-gnome, dia-common and dia-libs back to 0.96.1 everything went back to normal, with memory usage around 30MB. Running Debian sid, kernel 2.6.30-1-686 and libc6 2.9-18. -- Antonio Trueba atga...@gmail.com
Bug#412193: Malformed line in /usr/lib/mime/packages/gnumeric
Package: gnumeric Version: 1.7.7 Lines #22 and #23 of /usr/lib/mime/packages/gnumeric are malformed, they should be only one line (i.e., no carriage return between them). This results in a malformed /etc/mailcap file after update-mime, which leads to error dialogs on opening some applications, mainly wxWidgets based ones (i.e. poEdit). I'm using Debian GNU/Linux 4.0, kernel 2.6.18-4-686 and mime-support 3.39-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
