Bug#952669: reportbug output
On 3/3/20 6:56 PM, Andreas Beckmann wrote: > On 03/03/2020 18.05, Lucas B. Cohen wrote: >> Attached is partial output of : reportbug --template -T none -s none -S >> normal -b --list-cc none -q xserver-xorg-video-nvidia-legacy-390xx (with >> repeated lines removed, and some irrelevant info sanitized). > > You were running the current (418.xx) nvidia-driver: > >> /proc/driver/nvidia/version: >> NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.74 Wed May 1 11:49:41 >> CDT 2019 >> GCC version: gcc version 8.3.0 (Debian 8.3.0-6) > >> lrwxrwxrwx 1 root root 23 Mar 3 16:33 /etc/alternatives/nvidia > -> /usr/lib/nvidia/current > > therefore the collected information is mostly irrelevant for the 390xx > driver. Right. I had switched back to the current driver before running reportbug. My bad. > You don't seem to have the nvidia-legacy-390xx-driver package installed > either ... Well, this is awkward. Indeed, after checking more closely it appears I only had small bits and pieces of the complete legacy driver installed. (Perhaps only a couple packages, including the dkms-support package, which misled me into reassigning this bug here). > Were you using the glvnd or nonglvnd variant of the 390xx driver? > nvidia-legacy-390xx-driver-libs | nvidia-legacy-390xx-driver-libs-nonglvnd Judging from my apt logs, neither one was present on my system! (This is consistent with strace output I was seeing previously, showing some nvidia libs not being found when launching my userspace program.) > Since that card seems to be supported by all driver versions: > is there any reason to use the 390xx legacy driver for this card? Not that I can tell. Properly installed, both work well on my system. Given the strange, quite broken state in which my system was, it's probably not worth anyone's time investigating this any further. Thank you for your answer, and sorry for the noise. > BTW, the README.txt in the 390.xx driver lists the GeForce GTX 750 Ti as > a supported card. (D'oh. This is me failing to read the last three lines of the package description.)
Bug#952669: not an Aegisub bug
reassign 952669 nvidia-graphics-drivers-legacy-390xx severity wishlist retitle 952669 bad interaction between nvidia legacy driver 3900xx and wxWidgets 3.0 when using unsupported GM107 chip thanks Mucking around with my system, I've managed to figure that the wxWidgets UI issue in Aegisub only occurs when this driver is in use on my system. Because I'm not even using a graphics chip in the list of supported ones for this driver (GM107 aka GeForce GTX 750 Ti), I'm lowering the severity to the minimum. (I believe the upgrade process pulled this driver for me through the xserver-xorg-video-all dependency.) Switching to nouveau or to nvidia-driver caused the issue to disappear.
Bug#618658: gtk-doc-tools: prerm script returns an error, it seems to depend on emacsen-common being fully configured
Package: gtk-doc-tools Version: 1.15-2 Severity: minor File: gtk-doc-tools When upgrading a system from Lenny to Squeeze (dist-upgrade phase), dpkg ran into trouble tyring to upgrade this package. Being unfamiliar with both the GTK development environment, and emacs, here is the relevant output which I will leave to a more competent person to interpret. BEING APT-GET / DPKG OUTPUT Preparing to replace gtk-doc-tools 1.10-1 (using .../gtk-doc-tools_1.15-2_all.deb) ... ERROR: emacsen-common being used before being configured. ERROR: This is likely a bug in the gtk-doc-tools package, which needs to ERROR: add one of the appropriate dependencies. ERROR: See /usr/share/doc/emacsen-common/debian-emacs-policy.gz ERROR: for details. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: error processing /var/cache/apt/archives/gtk-doc-tools_1.15-2_all.deb (--unpack): there is no script in the new version of the package - giving up configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/gtk-doc-tools_1.15-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) END APT-GET / DPKG OUTPUT Apologies if this is irrelevant. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (995, 'stable'), (600, 'oldstable'), (600, 'testing'), (500, 'squeeze-updates'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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/bash Versions of packages gtk-doc-tools depends on: ii docbook-dsssl 1.79-6 modular DocBook DSSSL stylesheets, ii docbook-to-man 1:2.0.0-28 converter from DocBook SGML into r ii docbook-xml 4.5-7standard XML documentation system ii docbook-xsl 1.75.2+dfsg-5stylesheets for processing DocBook ii gnome-common2.28.0-1 common scripts and macros to devel ii highlight 2.16-1 Universal source code to formatted ii jade1.2.1-47 James Clark's DSSSL Engine ii perl5.10.1-17Larry Wall's Practical Extraction ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii xsltproc1.1.26-6 XSLT 1.0 command line processor Versions of packages gtk-doc-tools recommends: ii pkg-config0.25-1.1 manage compile and link flags for gtk-doc-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617318: new upstream version 0.17
On Tue, Mar 8, 2011 at 10:03 AM, RjY r...@users.sourceforge.net wrote: I noticed on the git list that there is a new upstream version out to fix this problem[1]: Here's an updated tig, which fixes an incompatibility with ncurses 2.8.[2] [1] http://permalink.gmane.org/gmane.comp.version-control.git/168563 [2] I think he means 5.8 :-) the particular patch is this http://repo.or.cz/w/tig.git/commitdiff/ddae52065f967db43f4d9aa07340c950cdb2b433 -- http://rjy.org.uk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546246: bacula-director-pgsql: missing -T template0 in creation of database
retitle 546246 bacula-director-pgsql: missing -T template0 in creation of database with PostgreSQL 8.4 tag 546246 upstream, confirmed thanks Michael, thank you for reporting. I am not comfortable with patching things this way, as I am afraid it could break things for users of previous versions. Upstream seems to believe it is the case too. A discussion has been initiated with the PostgreSQL developers on http://marc.info/?l=bacula-develm=125975994721892w=2 I'll try to see if some kind of version detection is possible for a more general solution. Until then this will at least be documented. Best Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509301: bacula : CVE-2008-5373: insecure temp file handling in mtx-changer.Adic-Scalar-24
The example script was corrected in v2.4, and no occurrences of either 'mktemp' nor '/tmp' come un in v3.0.3. However the vulnerability is still present in v1.38.11-8 (etch), in at least all of the autochangers example scripts. Upgrading to critical, since this vuln can compromise a whole system if these old scripts are used. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520508: bacula-sd with bacula user and tape group (defaut) can't run dvd+rw-mediainfo
severity 520508 + minor tag 520508 + pending usertag 520508 + doc-debian thanks Hi Raphael, Thank you for the report. This is not a bug but. The solution in your case is to add the 'bacula' user to the 'cdrom' group (as root : 'gpasswd -a bacula'). This is worth mentioning in README.Debian, or perhaps doing automatically during installation as a Debian enhancement. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#452182: bacula-fd - restart writes to console
Hi Bastian, Thank you for your interest in Debian and Bacula. Unfortunately I was unable to reproduce this behavior. Does this behavior still happen using the newer versions released in Debian ? Perhaps the debuglevel for bacula-fd was set at the time. Best Regards, Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
