Bug#1013933: Keep xsane out of Debian releases
On Thu, 8 Dec 2022 17:29:53 + (UTC) Alexis PM wrote: > Please consider reducing the severity of the bug to allow the inclusion of xsane in the next stable release. > > xsane has no equivalent software available. Its GUI allows you to use advanced features of SANE not available graphically in other GUIs. > > xsane is usable in the currently packaged version (removed in testing due to this bug). It does not have any bug that prevent me from using it on a daily basis. > > At https://popcon.debian.org/by_inst xsane is ranked 2346, by comparison sane is ranked 7457. > > Its development is low in the last years, the last commit is from 6 months ago ( https://gitlab.com/sane-project/frontend/xsane ), but this is not a reason to remove a software that is useful, usable, popular and no equivalent available. > > Thank you very much. > > I agree. As long as there are no alternative, please keep xsane in the bookworm release. While the GUI has it's flaws it does NOT render the entire package unusable so removing it (when no alternative exist) is a bit drastic. -- - Regards Svein Engelsgjerd
Bug#942877: goattracker sliently quits wiht exit code 1 on Debian Bullseye
Package: goattracker Version: 2.75-3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Trying to start goattracker * What exactly did you do (or not do) that was effective (or ineffective)? run it under gdb. Goattracker quits with exit code 1 * What was the outcome of this action? Goattracker did not start * What outcome did you expect instead? An error message explaining to me why goattracker does not start (and preferably a working goattracker) -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages goattracker depends on: ii libc62.29-2 ii libgcc1 1:9.2.1-8 ii libsdl1.2debian 1.2.15+dfsg2-5 ii libstdc++6 9.2.1-8 goattracker recommends no packages. Versions of packages goattracker suggests: ii milkytracker 1.02.00+dfsg-1 pn opencubicplayer pn schism -- no debconf information
Bug#890102: openshot: Openshot 2.4.1-2 will not start
Package: openshot Version: 2.4.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I ran an upgrade * What exactly did you do (or not do) that was effective (or ineffective)? I did not do anything special * What was the outcome of this action? When I start openshot the GUI constantly flickers between the main window and the "welcome window" / tutorial dialog. It is not possible to click the next button so the welcome window prevents the application from being useful. (the desktop environment is XFCE) * What outcome did you expect instead? I expect that the GUI does not flicker and does not constantly change focus between the two windows. *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openshot depends on: ii openshot-qt 2.4.1-2 openshot recommends no packages. openshot suggests no packages. -- no debconf information
Bug#874105: virtualbox: Virtualbox seems to conflict with BTRFS when trying to install ReactOS 0.4.6
Package: virtualbox Version: 5.1.26-dfsg-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, * What led up to the situation? I wanted to try to install ReactOS 0.4.6. My rootfs is btrfs with metadata=raid10 and data=raid1 While VirtualBox was running dmesg showed a constant stream of csum failed root 5 ino XXX off XXX csum XXX expected csum XXX mirror 1 messages. Note that the mirror was always 1. * What exactly did you do (or not do) that was effective (or ineffective)? I stopped the VM that was running the ReactOS installer. All the errors stopped I ran a scrub on my btrfs filesystem afterwards. No errors detected. I checked smart data for my SSD's No errors detected, no sign of wear. I tried various file operations (md5sum, sha1sum, cp, hexeditor etc...) on the .vdi file - no corruption messages * What was the outcome of this action? While this could just as easily be a btrfs bug I suspect that VirtualBox's vboxdrv is the cause here. I may be wrong about this, so my apologies if that is the case. Btrfs fixes the corruptions and appear to be in a good state as long as the VirutalBox VM is not running. qemu/kvm works fine. Using that instead. * What outcome did you expect instead? I expected no errors while running VirtualBox on top of my BTRFS rootfilessytem. * Other information: While I did not experience any dataloss I fear that this is fragile and *might* cause dataloss for some. this is the reason I classify this bug as grave. This is also causing me to avoid testing for a while until I get some feedback on this one. I am aware that BTRFS have it's share of bugs, but I run with a minimal configuration that have not caused any issues for years (it has actually fixed a few silent data corruptions here and there). So since my hardware and data checked out fine and the data is instact I think this could be a conflict between the btrfs and/or vboxdrv module. I am not skilled enoguh to find that out for myself. BTW: The VirtualBox vdi file contains a VFAT filesystem (reactos uses that). This does NOT appear to be the issues as I have tested other stuff with VFAT without any issues. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.116 ii init-system-helpers 1.49 ii iproute2 4.9.0-1 ii libc6 2.24-14 ii libcurl3-gnutls 7.55.0-1 ii libdevmapper1.02.12:1.02.137-2+b1 ii libgcc1 1:7.2.0-1 ii libgsoap-2.8.49 2.8.49-1 ii libpng16-16 1.6.31-1 ii libpython3.5 3.5.4-2 ii libsdl1.2debian 1.2.15+dfsg2-0.1 ii libssl1.1 1.1.0f-4 ii libstdc++67.2.0-1 ii libvncserver1 0.9.11+dfsg-1 ii libvpx4 1.6.1-3 ii libx11-6 2:1.6.4-3 ii libxcursor1 1:1.1.14-1+b4 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-3.1 ii libxmu6 2:1.1.2-2 ii libxt61:1.1.5-1 ii procps2:3.3.12-3 ii python3 3.5.3-3 ii python3.5 3.5.4-2 ii virtualbox-dkms [virtualbox-modules] 5.1.26-dfsg-2 ii zlib1g1:1.2.8.dfsg-5 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libqt5core5a 5.9.1+dfsg-9 ii libqt5opengl5 5.9.1+dfsg-9 ii libqt5widgets55.9.1+dfsg-9 ii virtualbox-qt 5.1.26-dfsg-2 Versions of packages virtualbox suggests: ii vde22.3.2+r586-2.1 pn virtualbox-guest-additions-iso -- no debconf information
Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up
Package: src:linux Followup-For: Bug #863290 Dear Maintainer, I would like voice my concern as well. Btrfs RAID5/6 really needs a warning. These days most (if not all) of the problems you see with Btrfs is caused by the unstable features (https://btrfs.wiki.kernel.org/index.php/Status). RAID5/6 in kernel 4.9 is less than stellar and should absolutely not be used for anything except testing and experimentation. RAID1 actually needs a warning too. It will not work as "classic" RAID1 e.g. it need to be able to make two copies always to not get stuck in read only mode. You will not loose your data which is a good thing, but to be safe you need a minimum of 3 devices (I would prefer four or more to be on the safe side). -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#844285: pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED]
Package: pidgin Followup-For: Bug #844285 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Read the bugreport * What exactly did you do (or not do) that was effective (or ineffective)? For what it's worth. I have also been using Pidgin (on XFCE4) for years. Never observed the mentioned bug. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages pidgin depends on: ii libatk1.0-0 2.22.0-1 ii libc6 2.24-9 ii libcairo2 1.14.8-1 ii libdbus-1-3 1.10.16-1 ii libdbus-glib-1-20.108-2 ii libfontconfig1 2.11.0-6.7 ii libfreetype62.6.3-3+b1 ii libgadu31:1.12.1-4 ii libgdk-pixbuf2.0-0 2.36.4-1 ii libglib2.0-02.50.2-2 ii libgstreamer1.0-0 1.10.3-1 ii libgtk2.0-0 2.24.31-2 ii libgtkspell02.0.16-1.1 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii libpangoft2-1.0-0 1.40.3-3 ii libpurple0 2.11.0-3 ii libsm6 2:1.2.2-1+b1 ii libx11-62:1.6.4-3 ii libxss1 1:1.2.2-1 ii perl-base [perlapi-5.24.1] 5.24.1-1 ii pidgin-data 2.11.0-3 Versions of packages pidgin recommends: ii gstreamer1.0-alsa 1.10.3-1 ii gstreamer1.0-libav 1.10.3-1 ii gstreamer1.0-plugins-base 1.10.3-1 ii gstreamer1.0-plugins-good 1.10.3-1 ii gstreamer1.0-pulseaudio1.10.3-1 Versions of packages pidgin suggests: ii libsqlite3-0 3.16.2-2 -- no debconf information
Bug#827022: fs-uae: FS-UAE segfaults when started
Package: fs-uae Version: 2.6.2+dfsg-4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Trying to start fs-uae * What exactly did you do (or not do) that was effective (or ineffective)? I did not do anything other than start it. * What was the outcome of this action? Since I did nothing there was no outcome * What outcome did you expect instead? I expected fs-uae to start -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fs-uae depends on: ii libc6 2.22-9 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:6.1.1-4 ii libgl1-mesa-glx [libgl1] 11.2.2-1 ii libglew1.13 1.13.0-2 ii libglib2.0-0 2.48.1-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libmpeg2-40.5.1-7 ii libopenal11:1.17.2-1 ii libpng16-16 1.6.21-5 ii libsdl2-2.0-0 2.0.4+dfsg2-1 ii libstdc++66.1.1-4 ii libx11-6 2:1.6.3-1 ii zlib1g1:1.2.8.dfsg-2+b1 fs-uae recommends no packages. fs-uae suggests no packages. -- no debconf information
Bug#767996: fs-uae-launcher fails to launch fsuae
Package: fs-uae-launcher Version: 2.4.1+ds-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? A upgrade of the system. Sadly can't say when it happened * What exactly did you do (or not do) that was effective (or ineffective)? starting fs-uae-launcher with this fixes the problem. __GL_WRITE_TEXT_SECTION=0 fs-uae-launcher * What was the outcome of this action? fs-uae-launcher now launches fsuae seemingly without any issues. * What outcome did you expect instead? I expected fsuae to work "out of box" without this workaround. As far as I was told this is a nvidia problem and not exactly a problem with fsuae per.se. However I still think that as long as this is a known problem with nvidia a workaround should be considered since it basically makes fs-uae-launcher useless. (Using nvidia packages from the debian repos) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fs-uae-launcher depends on: ii fs-uae 2.4.1+ds-2 ii python 2.7.8-1 ii python-pyside 1.2.2-1 ii python-setuptools 5.5.1-1 fs-uae-launcher recommends no packages. fs-uae-launcher suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
