Bug#1051796: thunderbird not displaying message headers correctly.

[js jb]

I've noticed that the behavior described in this bug tends to happen in 
messages whose attachments were deleted.
thanks

Bug#1032972: handbrake: debian version of handbrake does NOT handle subtitles correctly

[js jb]

This is the exact version of handbrake I used from fr.handbrake.ghb that fixed 
the subtitles issue (which seems caused because the character encoding of the 
subtitles is not always recognized):
 =>  flatpak info fr.handbrake.ghb
HandBrake - Video Transcoder

  ID: fr.handbrake.ghb
 Ref: app/fr.handbrake.ghb/x86_64/stable
    Arch: x86_64
  Branch: stable
 Version: 1.6.1
 License: GPL-2.0+
  Origin: ghb-origin
  Collection: 
Installation: user
   Installed: 123.3 MB
 Runtime: org.gnome.Platform/x86_64/43
 Sdk: org.gnome.Sdk/x86_64/43

  Commit: 227d2a8398a850cd93a6662116c0bc64be187eeb4f2e5a2ae1e490838cd03248
 Subject: Export fr.handbrake.ghb
    Date: 2023-01-23 18:08:28 +

Bug#1032972: handbrake: debian version of handbrake does NOT handle subtitles correctly

[js jb]

I've installed the snapshot version of handbrake from handbrake.fr directly 
(via flatpak)and verified that on the same DVDs, it generates the subtitles 
perfectly.
I also built the debian version of handbrake from source and that one still has 
the same problems.One can also see the subtitles overlaying each other so that 
in rapid dialog multiple subtitles appearone on top of each other, making them 
all illegible.  This does not happen in the handbrake snaphshot.
thanks,--jack

Bug#1031249: Re: Bug#1031249: VLC 3.0.18 crash FIXED with downgrade of libva2 libraries to 2.14.0-1

[js jb]

 Thanks,
There was an old version of vdpau-va-driver installed in the system even though 
it's no longer in Debian.
Removing it allowed vlc to work with the 2.17.0-1 libva libraries.
Perhaps this should be moved to the libva bug list with a request to add a 
conflict with vdpau-va-driver?
thanks,--jack

On Sunday, February 19, 2023 at 03:03:51 PM EST, Rémi Denis-Courmont 
 wrote:  
 
 Le sunnuntaina 19. helmikuuta 2023, 19.13.51 EET js jb a écrit :
> I've verified that by downgrading these libva2 libraries from  2.17.0-1 to
> 2.14.0-1, VLC_3.0.18 works fine again: libva-dev=2.14.0-1
>    libva-drm2=2.14.0-1
>    libva-glx2=2.14.0-1
>    libva-wayland2=2.14.0-1
>    libva-x11-2=2.14.0-1
>    libva2=2.14.0-1
>    intel-media-va-driver=22.4.2+dfsg1-2  (downgraded from 23.1.0+dfsg1-1
> only to avoid removing the package). Therefore this bug should be
> reassigned to the libva2 package instead of vlc. thanks,--jack

AFAICT, the bug is caused by vdpau-va-driver, which is no longer in Debian.

But of course, libva should set lay out adequate conflict statements to prevent 
this from causes crashes, and forcing the package to be uninstalled.

-- 
レミ・デニ-クールモン
http://www.remlab.net/



  

Bug#1031249: VLC 3.0.18 crash FIXED with downgrade of libva2 libraries to 2.14.0-1

[js jb]

I've verified that by downgrading these libva2 libraries from  2.17.0-1 to 
2.14.0-1, VLC_3.0.18 works fine again:
    libva-dev=2.14.0-1
    libva-drm2=2.14.0-1
    libva-glx2=2.14.0-1
    libva-wayland2=2.14.0-1
    libva-x11-2=2.14.0-1
    libva2=2.14.0-1
    intel-media-va-driver=22.4.2+dfsg1-2   (downgraded from 23.1.0+dfsg1-1 only 
to avoid removing the package).
Therefore this bug should be reassigned to the libva2 package instead of vlc.
thanks,--jack

Bug#1029815: Problem fixed in fetchmail version 6.4.36-1

[js jb]

 After rebooting my computer, with no changes to fetchmailrc or the version of 
fetchmail, I see in syslog:    
2023-02-05T11:15:34.903940-05:00 berkeley fetchmail[4457]: The nodetach option 
is in effect, ignoring logfile option.
The file /usr/lib/systemd/user/fetchmail.service  has a --nodetach option but 
removing it (and restarting the fetchmail service)makes no difference and 
fetchmail still appears running with the --nodetach option in place.
It seems for the logfile to work one must restart fetchmail immediately, 
otherwise the default --nodetach takes effect:FAIL:  fetchmail -q ; sleep 5; 
fetchmailWORK: fetchmail -q ; fetchmail
Clarifying this would be useful in the man page or other documentation.


thanks,--jack

On Friday, February 3, 2023 at 10:20:36 AM EST, js jb  
wrote:  
 
 After upgrading to the new fetchmail 6.4.36-1, the problem has been fixed 
without any change at all to my .fetchmailrc.
This bug can now be closed.
thanks,--jack
  

Bug#1029815: Problem fixed in fetchmail version 6.4.36-1

[js jb]

After upgrading to the new fetchmail 6.4.36-1, the problem has been fixed 
without any change at all to my .fetchmailrc.
This bug can now be closed.
thanks,--jack

Bug#1029045: ledgersmb: login page Perl error in default config

[JB]

Package: ledgersmb
Version: 1.6.9+ds-2+deb11u3
Severity: important
X-Debbugs-Cc: j-dbug.666.114.1...@x.firehead.org

Dear Maintainer,

I installed LedgerSMB with defaults on Debian-11 with systemd.  It 
starts fine

with Starman, but when I go to http://localhost:5762/login.pl it shows only
this message:

-
Error!

Can't locate object method "new" via package "Template" at 
/usr/share/ledgersmb/bin/../lib/LedgerSMB/Template.pm line 599.


dbversion: , company: 1.6.9
-

Thus leaving the package in an unusable state.


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 ledgersmb depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.77
ii  dpkg  1.20.12
ii  libcarp-always-perl   0.16-1
ii  libcgi-emulate-psgi-perl  0.23-1
ii  libcgi-simple-perl    1.115-2
ii  libclass-c3-xs-perl   0.15-1+b1
ii  libconfig-inifiles-perl   3.03-1
ii  libdata-uuid-perl 1.226-1+b1
ii  libdatetime-format-strptime-perl  1.7800-1
ii  libdatetime-perl  2:1.54-1
ii  libdbd-pg-perl    3.14.2-1+b1
ii  libdbi-perl   1.643-3+b1
ii  libhtml-escape-perl   1.10-1+b3
ii  libhttp-exception-perl    0.04007-1
ii  libio-stringy-perl    2.111-3
ii  libjs-dojo-dijit  1.15.4+dfsg1-1+deb11u1
ii  libjson-perl  4.03000-1
ii  liblocale-codes-perl  3.66-1
ii  liblocale-maketext-lexicon-perl   1.00-1.1
ii  liblog-log4perl-perl  1.54-1
ii  libmime-lite-perl 3.031-1
ii  libmime-types-perl    2.18-1
ii  libmoose-perl 2.2014-2
ii  libmoosex-nonmoose-perl   0.26-1.1
ii  libnamespace-autoclean-perl   0.29-1
ii  libnumber-format-perl 1.75-1.1
ii  libpgobject-perl  2.2.0-1
ii  libpgobject-simple-perl   3.02-1.1
ii  libpgobject-simple-role-perl  2.02-1.1
ii  libpgobject-type-bigfloat-perl    2.001-1
ii  libpgobject-type-bytestring-perl  1.2.3-1
ii  libpgobject-type-datetime-perl    2.02-1
ii  libpgobject-util-dbadmin-perl 1.4.0-1
ii  libpgobject-util-dbmethod-perl    1.00.003-1
ii  libplack-builder-conditionals-perl    0.05-1.1
ii  libplack-middleware-reverseproxy-perl 0.16-1
ii  libplack-perl 1.0048-1
ii  libplack-request-withencoding-perl    0.14-1
ii  libtemplate-perl  2.27-1+b3
ii  libtext-markdown-perl 1.31-3
ii  libtry-tiny-perl  0.30-1
ii  libversion-compare-perl   0.14-1.1
ii  libxml-simple-perl    2.25-1
ii  perl  5.32.1-4+deb11u2
ii  postgresql-client 13+225
ii  postgresql-client-13 [postgresql-client]  13.9-0+deb11u1
ii  postgresql-contrib    13+225
ii  starman   0.4015-1
ii  ucf   3.0043

Versions of packages ledgersmb recommends:
pn  libjson-xs-perl    
pn  liblatex-driver-perl   
pn  libmath-bigint-gmp-perl    
pn  libtemplate-plugin-latex-perl  
pn  libtex-encode-perl 
ii  lighttpd   1.4.59-1+deb11u2
pn  texlive-latex-recommended  

Versions of packages ledgersmb suggests:
pn  default-mta | mail-transport-agent  
pn  latex-cjk-all   
pn  libimage-size-perl  
pn  libopenoffice-oodoc-perl    
pn  libx12-parser-perl  
pn  lpr 
ii  postgresql  13+225
pn  texlive-xetex   

-- debconf information:
* ledgersmb/lsmb_proxy: Lighttpd
* ledgersmb/admin_login: lsmb_dbadmin

Bug#1028924: ledgersmb: Init script calls start-stop-daemon incorrectly, fails to start

[JB]

Package: ledgersmb
Version: 1.6.9+ds-2+deb11u3
Severity: important
X-Debbugs-Cc: j-dbug.666.114.1...@x.firehead.org

Dear Maintainer,

I installed LedgerSMB with defaults on Debian-11 with sysvinit (instead of
systemd).  When I try to start the daemon, it produces the following output:

# /etc/init.d/ledgersmb start
$Starting ledgersmb:
start-stop-daemon: unrecognized option '--interval=5'
Try 'start-stop-daemon --help' for more information.
#

I am not an expert on start-stop-daemon, but looking at the init script, it
seems start-stop-daemon is invoked with /usr/bin/start_server as the 
intended

program to run, which then has further arguments for that to start
/usr/bin/starman.  However the start-stop-daemon invocation lacks a 
"--start"
argument prior to the /usr/bin/start_server, and the "--start" seems to 
be the
norm among other uses of start-stop-daemon in the system's /etc/init.d/* 
files.

So maybe the init script is for some completely different version of
start-stop-daemon, or the arguments are really for a different program, or
something.  I'm not quite sure.


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'stable'), (500, 'oldstable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ledgersmb depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.77
ii  dpkg  1.20.12
ii  libcarp-always-perl   0.16-1
ii  libcgi-emulate-psgi-perl  0.23-1
ii  libcgi-simple-perl    1.115-2
ii  libclass-c3-xs-perl   0.15-1+b1
ii  libconfig-inifiles-perl   3.03-1
ii  libdata-uuid-perl 1.226-1+b1
ii  libdatetime-format-strptime-perl  1.7800-1
ii  libdatetime-perl  2:1.54-1
ii  libdbd-pg-perl    3.14.2-1+b1
ii  libdbi-perl   1.643-3+b1
ii  libhtml-escape-perl   1.10-1+b3
ii  libhttp-exception-perl    0.04007-1
ii  libio-stringy-perl    2.111-3
ii  libjs-dojo-dijit  1.15.4+dfsg1-1+deb11u1
ii  libjson-perl  4.03000-1
ii  liblocale-codes-perl  3.66-1
ii  liblocale-maketext-lexicon-perl   1.00-1.1
ii  liblog-log4perl-perl  1.54-1
ii  libmime-lite-perl 3.031-1
ii  libmime-types-perl    2.18-1
ii  libmoose-perl 2.2014-2
ii  libmoosex-nonmoose-perl   0.26-1.1
ii  libnamespace-autoclean-perl   0.29-1
ii  libnumber-format-perl 1.75-1.1
ii  libpgobject-perl  2.2.0-1
ii  libpgobject-simple-perl   3.02-1.1
ii  libpgobject-simple-role-perl  2.02-1.1
ii  libpgobject-type-bigfloat-perl    2.001-1
ii  libpgobject-type-bytestring-perl  1.2.3-1
ii  libpgobject-type-datetime-perl    2.02-1
ii  libpgobject-util-dbadmin-perl 1.4.0-1
ii  libpgobject-util-dbmethod-perl    1.00.003-1
ii  libplack-builder-conditionals-perl    0.05-1.1
ii  libplack-middleware-reverseproxy-perl 0.16-1
ii  libplack-perl 1.0048-1
ii  libplack-request-withencoding-perl    0.14-1
ii  libtemplate-perl  2.27-1+b3
ii  libtext-markdown-perl 1.31-3
ii  libtry-tiny-perl  0.30-1
ii  libversion-compare-perl   0.14-1.1
ii  libxml-simple-perl    2.25-1
ii  perl  5.32.1-4+deb11u2
ii  postgresql-client-13 [postgresql-client]  13.9-0+deb11u1
ii  postgresql-contrib    13+225
ii  starman   0.4015-1
ii  ucf   3.0043

Versions of packages ledgersmb recommends:
ii  apache2    2.4.54-1~deb11u1
pn  libjson-xs-perl    
pn  liblatex-driver-perl   
pn  libmath-bigint-gmp-perl    
pn  libtemplate-plugin-latex-perl  
pn  libtex-encode-perl 
pn  texlive-latex-recommended  

Versions of packages ledgersmb suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.94.2-7
pn  latex-cjk-all  
pn  libimage-size-perl 
pn  libopenoffice-oodoc-perl   
pn  libx12-parser-perl 
pn  lpr    
ii  postgresql  

Bug#990160: closed by Florian Schlichting (Re: [Pkg-mpd-maintainers] Bug#990160: mpd: music players using mpd do not play concatenated mp3 files to the end)

[js jb]

 Thank you,
The workaround that worked for me, from the discussion of the bug, was to 
modify  /etc/mpd.conf with this decoder section,using ffmpeg and preventing mad 
and mpg123 from being used.


# Decoder #
#
decoder {
    plugin "ffmpeg"
    enabled "yes"
}

decoder {
    plugin  "hybrid_dsd"
    enabled "no"
#   gapless "no"
}

# disable mad to allow concatenated mp3 to play through to the end:
decoder {
    plugin "mad"
    enabled "no"
}

decoder {
    plugin "mpg123"
    enabled "no"
}



thanks again,--jack

On Saturday, November 26, 2022 at 11:39:05 AM EST, Debian Bug Tracking 
System  wrote:  
 
 This is an automatic notification regarding your Bug report
which was filed against the mpd package:

#990160: mpd: music players using mpd do not play concatenated mp3 files to the 
end

It has been closed by Florian Schlichting .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Florian Schlichting 
 by
replying to this email.


-- 
990160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Sun, Jul 04, 2021 at 12:02:13AM +, js jb wrote:
>  After posting the files to reproduce the problem on github, they posted a 
>work-around for this issue:
> In /etc/mpd.conf, disable the 'mad' decoder with the lines:decoder {
>    plugin "mad"
>    enabled "no"
> }This solved the problem.

I'm closing this bug after reading the upstream discussion (different
decoders behaving differently, observing or ignoring Xing headers
present in the file). If someone has a suggestion how to document the
workaround, that could probably be useful for other users.

FlorianPackage: mpd
Version: 0.22.6-1+b1
Severity: normal

Dear Maintainer,

==

I've noticed that music players that use mpd,like cantata, do not play
concatenated mp3 files to the end but stop after the first part of the
concatenated file.

For example: cat mvmt1.mp3 mvmt2.mp3 mvmt3.mp3 > symph1.mp3
will play only mvmt1.mp3 on an mpd-based player when symph1.mp3 is
played.

This does NOT happen on music players that do not use mpd, like vlc or
elisa (or any android music player).

The only work-around is to use a non-mpd player for this.

Concatenated mp3 files are useful when one wants to create a single mp3 for
a classical piece composed of many movements, as above, and create a
playlist of several of these. Each symphony will then be played
completely but the next symphony to play can be a shuffle choice (but
without shuffling the individual movements within each symphony).

==


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-2-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpd depends on:
ii  adduser                            3.118
ii  init-system-helpers                1.60
ii  libadplug-2.3.3-0                  2.3.3+dfsg-2
ii  libao4                            1.2.2+20180113-1.1
ii  libasound2                        1.2.4-1.1
ii  libaudiofile1                      0.3.6-5
ii  libavahi-client3                  0.8-5
ii  libavahi-common3                  0.8-5
ii  libavcodec-extra58 [libavcodec58]  7:4.3.2-0+deb11u1
ii  libavformat58                      7:4.3.2-0+deb11u1
ii  libavutil56                        7:4.3.2-0+deb11u1
ii  libbz2-1.0                        1.0.8-4
ii  libc6                              2.31-12
ii  libcdio-cdda2                      10.2+2.0.0-1+b2
ii  libcdio-paranoia2                  10.2+2.0.0-1+b2
ii  libcdio19                          2.1.0-2
ii  libchromaprint1                    1.5.0-2
ii  libcurl3-gnutls                    7.74.0-1.2
ii  libdbus-1-3                        1.12.20-2
ii  libexpat1                          2.2.10-2
ii  libfaad2                          2.10.0-1
ii  libflac8                          1.3.3-2
ii  libfluidsynth2                    2.1.7-1.1
ii  libgcc-s1                          10.2.1-6
ii  libgme0                            0.6.3-2
ii  libicu67                          67.1-6
ii  libid3tag0                        0.1

Bug#996031: nvidia-driver breaks 'apt-get update' when kernel 5.14.6 is candidate kernel

[js jb]

I should add that making nvidia-driver conflict with later kernel versions for 
which it has not been tested is only an *example* solution,but clearly not the 
only way to keep apt-get upgrade working properly with nvidia-driver.
A more flexible solution would be to create an optional dummy package, 
nvidia-dkms-compat, with the same version as nvidia-kernel-dkmsbut which 
conflicts with later kernel versions than the ones where nvidia-kernel-dkms was 
tested.
Users that want to keep the current informal status can avoid installing 
nvidia-dkms-compat and rely on the description of nvidia-driver to choose newer 
kernel versions.

Users that do install nvidia-dkms-compat will be alerted through the usual apt 
methods that there is an incompatibility with a newer kernel.
Regardless of how this is solved, I think an important goal is that apt-get 
upgrade should work properly when nvidia-kernel-dkms is installed;this means 
that a newer kernel on which nvidia does not build will not be installed by 
default, not appear as a candidate upgrade version.

thanks,--jack

Bug#950586: REDEFINITION: dkms build fails with kernel 5.4.0-3-686-pae but NOT with 4.17.0-3-686-pae

[js jb]

 Thank you very much Andreas for your quick response and explanation of the 
problem.
I was able to install nvidia-driver_440.44-2 on my 4.17 and, after a few days 
of testing, expect the upgrade tothe 5.4 kernel will work,.
However, I had some difficulty getting the 440.44-2 driver to work at first: 
this was because the install did notremove a number of packages from the old 
390.87 driver (listed below), including nvidia-kernel-support and 
nvidia-kernel-source,so that after the initial install the nvidia module was 
not found.
Removing the list of 390.87 packages fixed that problem: perhaps the new driver 
should have removed some of these packages.
I did not check the package description before upgrading, so missed the part 
that said it had been tested only through linux 4.20 kernel.Perhaps this would 
have been easier if the nvidia-driver package depended on a linux kernel 
version <= 4.20?
thanks again,--jack

List of nvidia 390.87 packages not remove after install nvidia-driver 440.44-2

libegl-nvidia0
libgl1-nvidia-glvnd-glx
libgl1-nvidia-glx-390.87
libgles-nvidia2
libglx-nvidia0
libnvidia-cfg1
libnvidia-compiler
libnvidia-compiler-390.87
libnvidia-eglcore
libnvidia-eglcore-390.87
libnvidia-encode1
libnvidia-fatbinaryloader
libnvidia-fatbinaryloader-390.87
libnvidia-glcore
libnvidia-glcore-390.87
libnvidia-ifr1
libnvidia-ml1
libnvidia-ptxjitcompiler1
nvidia-alternative
nvidia-cuda-mps
nvidia-detect
nvidia-driver-bin
nvidia-driver-bin-390.87
nvidia-driver-libs
nvidia-egl-icd
nvidia-kernel-390.87
nvidia-kernel-source
nvidia-kernel-support
nvidia-legacy-check
nvidia-opencl-icd
nvidia-vdpau-driver



On Monday, February 3, 2020, 4:27:39 PM EST, Andreas Beckmann 
 wrote:  
 
 On 03/02/2020 22.14, js wrote:
> I expected the dkms module would be built for 5.4 as it was for 4.17.

The nvidia kernel module build usually breaks with every new major
kernel release, e.g. 5.4 -> 5.5

> [I understand this is an older version of nvidia-kernel-dkms but did not

Please check the description of the package, it will tell you the
maximum kernel version where we successfully built the module for.
(Usually the current kernel version at the time the package was uploaded.)

> find a bug report regarding this and would normally not upgrade both
> kernel and nvidia at the same time.]

Then upgrade nvidia first. The driver should be backwards compatible.


Andreas
  

Bug#939941: The solution

[JB]

I found the issue: yesterday I had been trying to see if another monitor was 
working on this particular machine, and shut it down.

The thing is: this particular monitor had precedence over all others and so, 
gdm was displaying the "primary" screen to this monitor. Since it was shut 
down, I was not obvious that it was taken into account.

Anyway, sorry for the inconvenience. It seems that all the "NVRM: Xid" errors 
were linked to this monitor being connected and not turned on, because there is 
no errors of this kind now.

Sorry again for pulling the trigger too soon.

Cheers,

JB

Bug#939941: Adding details to bug #939941

[JB]

Out of desperation, I went and purged everything labelled as nvidia on my 
system.

After rebooting, and nouveau being not blacklisted anymore,
I was surprised to see that I had the same issue.

Indeed, nouveau was back:

$ sudo lsmod | grep video
video  45056  1 nouveau

I guess I might have targeted the wrong package with "nvidia-driver" and I am 
sorry for the inconvenience. However, I do not know against which package I 
should submit this bug.

I am sort of lost at the moment because I do know what could have caused this 
issue, especially so suddenly (maybe the hardware became faulty?)

If you have any clue, I would appreciate anything that could point me in the 
right direction.

Cheers,

JB

Bug#939941: Adding details to bug #939941

[JB]

Here is an excerpt of dmesg after a reboot ; as you can see, it does not 
"flood" anymore the ttys with the "NVRM: Xid ... " error but still, I got 
several of them when booting up.

sudo dmesg | grep NVRM
[3.050208] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  418.74  Wed May  
1 11:49:41 CDT 2019
[   59.635526] NVRM: GPU at PCI::01:00: 
GPU-f0e782b4-4a3b-7bc5-6030-fd3d1d9afa12
[   59.635541] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 031c
[   67.836608] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 031d
[   76.024961] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 031e
[   84.215000] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 031f
[   92.405456] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 0320
[  100.596350] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 0321
[  108.787424] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 0322
[  116.978757] NVRM: Xid (PCI::01:00): 16, Head 0002 Count 0323

According to this link (https://docs.nvidia.com/deploy/xid-errors/#topic_4), 
this error refers to a driver error which causes the display engine to hang, 
which seems to be exactly what's affecting my system.

I could try to purge the package nvidia-driver and going back to nouveau to see 
if that works ; let me know if that's something you would be interested in, or 
if I could provide any other detail to help.

Cheers,

JB

Bug#939471: Adding details

[JB]

Hello again,

After spending some time without my headphones on (which, sort of, prevent me 
from hearing small sounds around me), I noticed that I could hear the same 
sound coming out of the speakers (even though the only selected output is the 
DAC, therefore the headphones) whenever I was launching applications which are 
dealing with audio (games, voice chat applications, etc.).

Therefore, I think I was wrong assuming it could be gnome-settings-center, 
because that's all I had been seeing by then, but know it seems it could a 
broader issue, or, at least, because of other packages.

Sorry for the inconvenience,

JB

Bug#932879: Add details

[JB]

Just an additional message to include a screenshot of the GNOME GUI panel I am 
talking about.


JB

Bug#907733: curlpp package still orphaned?

[JB]

Hi,

I would be interested in taking over this package but I'm confused ; it seemed 
to have attracted other interested people as well, but the package is still 
being listed as looking for a maintainer.

So, I just wanted to know if someone (Jaime?) had taken over or if this package 
was still waiting for a maintainer.

Thanks!

Have a good one,

JB

Bug#927317: Adding details to 927317

[JB]

Here is a screenshot of the screen right after login in.

For the record, I have a dual screen so the left part of the screenshot is the 
second monitor (not the primary) and I am using Nvidia proprietary driver 
(updating it does not change anything).

Bug#927401: Add details

[JB]

Please find herewith enclosed the output of `dmesg` which shows the device 
booting up in a bad state and at the end after unplugging/plugging it back 
several times to try to see if the issue was reproducible that way, and not 
only during a (re)boot.

Note that, AFAIK, this issue appears only on (re)boot.




dmesg
Description: Binary data

Bug#927173: Adding details

[JB]

Thanks for your input, and sorry for reporting a bug on the wrong package.

How should I report this bug then? I am not sure what to say to demonstrate it 
is a kernel issue.

‐‐‐ Original Message ‐‐‐
On Friday, April 19, 2019 2:17 AM, Felipe Sateler  wrote:

> On Thu, Apr 18, 2019 at 8:05 PM JB  wrote:
>
>> My bad, I thought it was the case but I mixed up the numbers.
>>
>> Please find enclosed the details you've asked for.
>
> This confirms that ID_MODEL_ID changes and that ID_VENDOR changes although 
> ID_VENDOR_ID does not. I think this is a kernel bug.
>
> --
>
> Saludos,
> Felipe Sateler

Bug#927173: Adding details

[JB]

My bad, I thought it was the case but I mixed up the numbers.

Please find enclosed the details you've asked for.

‐‐‐ Original Message ‐‐‐
On Friday, April 19, 2019 1:47 AM, Felipe Sateler  wrote:

> On Thu, Apr 18, 2019 at 5:32 PM Michael Biebl  wrote:
>
>> Am 18.04.19 um 19:35 schrieb JB:
>>> If it can help, it happened to other people, e.g. here with Arch : 
>>> https://bbs.archlinux.org/viewtopic.php?id=222301
>>>
>>
>> Felipe, with your PA hat on, can you take a look at this?
>
> PA simply reads information udev relays to it (ID_MODEL, ID_VENDOR, etc).
>
> Julien, can you post the output of:
>
> udevadm info -p /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/sound/card2
>
> in both cases?
>
> From the pacmd output I see that the product id is not the same: 10e0 in the 
> correct case vs 9023 in the wrong case. These are picked from the ID_MODEL_ID 
> udev property.
>
>> To me this looks like a kernel/driver issue, but would welcome your
>> input on this.
>
> IIUC, ID_MODEL_ID is originated in the kernel rather than udev, which would 
> make this a kernel bug.
>
> --
>
> Saludos,
> Felipe Sateler

udevadm_info_good_state
Description: Binary data


udevadm_info_bad_state
Description: Binary data

Bug#927173: Adding details

[JB]

If that helps, please find enclosed the output of `pacmd list-sinks` when in 
bad state and in good state.

Best regards,

JB


‐‐‐ Original Message ‐‐‐
On Thursday, April 18, 2019 11:32 PM, Michael Biebl  wrote:

> Am 18.04.19 um 19:35 schrieb JB:
>
> > If it can help, it happened to other people, e.g. here with Arch : 
> > https://bbs.archlinux.org/viewtopic.php?id=222301
>
> Felipe, with your PA hat on, can you take a look at this?
>
> To me this looks like a kernel/driver issue, but would welcome your
> input on this.
>
> Regards,
> Michael




pacmd_list-sinks_good_state
Description: Binary data


pacmd_list-sinks_bad_state
Description: Binary data

Bug#927173: Adding details

[JB]

If it can help, it happened to other people, e.g. here with Arch : 
https://bbs.archlinux.org/viewtopic.php?id=222301

Bug#927173: udev: wrong device name when booting

[JB]

Long story short, my USB DAC was listed at index 0 within the list of 
pulseaudio sinks.

-> when in good state:
$ pacmd list-sinks
2 sink(s) available.
index: 0
name: 



So, I usually set it as the default output sink:

$ pacmd set-default-sink 0

I thought it might worked as workaround using the index; I reached out to the 
pulseaudio team to know more. The previous command is actually using the index 
to retrieve the sink name and store it as the reference for the default sink.

At this point, they stressed on how pulseaudio retrieved the sink name through 
alsa. Therefore, I discovered that the alsa name what, as well not the proper 
one (using `cat /proc/asound/cards`) after some (re)boots.

-> when in good state:
$ cat /proc/asound/cards

...
 2 [Audio  ]: USB-Audio - SA9023 USB Audio
  HiFimeDIY Audio SA9023 USB Audio at usb-:00:14.0-3, 
full speed

I reached out to the alsa team, just to be sure, they told me what I already 
suspected, that alsa was just handling device names given by udev.

Some people on the udev IRC channel were puzzled as well, thought it was a good 
time to report the problem.


‐‐‐ Original Message ‐‐‐
On Thursday, April 18, 2019 5:06 PM, Michael Biebl  wrote:

> Am 18.04.19 um 17:03 schrieb JB:
>
> > I managed to track this bug down to udev,
>
> How?
>
>
> 
>
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?

Bug#927173: udev: wrong device name when booting

[JB]

I managed to track this bug down to udev, but I am no expert when it comes to 
it, so I might be wrong. I also thought it could be the kernel when I saw the 
dmesg output but first I had to be sure it was not a udev issue.

At this point, I suspect it might even be a hardware issue (device which could 
be not respecting USB standards).

Anyway, if you think udev can be ruled out of the list of packages which could 
be the source of the problem, so be it. But I would gladly try to troubleshoot 
this issue, and since I'm now stuck on udev level, I welcome any suggestion on 
how to expose the problem.

Best,

JB


‐‐‐ Original Message ‐‐‐
On Thursday, April 18, 2019 9:45 AM, Michael Biebl  wrote:

> Am 18.04.19 um 01:43 schrieb Jul':
>
> > Sorry for the lack of details.
> >
> > 1.  how udev assigns this name?
> >
> > Since I have no custom udev rule, AFAIK, udev assigns it with the standards 
> > rules (in "/lib/udev/rules.d/60-persistent-alsa.rules" since it is a sound 
> > device).
>
> This rules file just creates a few symlinks in /dev/snd/by-id/ and
> /dev/snd/by-path/
>
> I don't see how that could influence your card being detected under
> different names.
>
> The dmesg output you posted looks like those messages come directly from
> the kernel. Maybe this is a kernel issue?
>
>
> --
>
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?

Bug#891578: xscreensaver often slows down, taking 1+ minute to respond to keystrokes, Xorg 100% CPU

[js jb]

This problem is still present with the new nvidia-driver (390.42) and 
xserver-xorg (1.7.7+19).
I now believe this is an issue either with the nvidia driver for 32 bit linux 
or with xorg rather than xscreensaveras I have found another application, 
flightgear, that show exactly the same symptoms when runin full screen mode.
Both xscreensaver and flightgear run fine in a window but slow down to a crawl 
in full screen modeonce X windows has been running continuously for 10+ days. 
Restarting X fixes the problem for another10 days or so.
thanks,--jack

Bug#895335: geeqie: edit-orientation corrupts EXIF in image

[js jb]

Package: geeqie
Version: 1:1.4-3
Severity: important

Dear Maintainer,

===

I noticed that in a handful of cases (26 jpegs out of 529), the EXIF 
information as seen by exiftool was incorrect;the lens type was a list (see 
below) instead of a specific type.
Several tests with the camera and lens showed no problem with the EXIF.
I stumbled on the error and can now reproduce it; the problem is using any of 
the Edit->Orientation functionsin geeqie. Here is an example; after applying a 
rotate operation from geeqie, lens info is corrupted:

2018 => exiftool A6K01199.JPG | grep -i Lens
Lens Type   : E-Mount, T-Mount, Other Lens or no lens
Lens Spec   : E PZ 18-105mm F4 G OSS
Lens Mount 2    : E-mount
Lens Type 3 : Sony E PZ 18-105mm F4 G OSS
Lens E-mount Version    : 1.41
Lens Firmware Version   : Ver.04.003
Lens Mount  : E-mount
Lens Format : APS-C
Lens Type 2 : Sony E PZ 18-105mm F4 G OSS
Lens Spec Features  : E PZ G OSS
Lens Info   : 18-105mm f/4
Lens Model  : E PZ 18-105mm F4 G OSS
Lens ID : Sony E PZ 18-105mm F4 G OSS

["Apply the orientation to the image content"]  (also happens with losslessly 
rotate functions)

2018 => exiftool A6K01199.JPG | grep -i Lens
Lens Type   : E-Mount, T-Mount, Other Lens or no lens
Lens Spec   : Unknown (01 0 1 0 0 00)
Lens Mount 2    : Unknown (97)
Lens Type 3 : Unknown (38213)
Lens E-mount Version    : 47.61
Lens Firmware Version   : Ver.cf.069
Lens Mount  : Unknown
Lens Format : Unknown
Lens Spec Features  :
Lens ID : Sony E 16-70mm F4 ZA OSS or Sony FE 24-70mm 
F4 ZA OSS or Sony E PZ 18-105mm F4 G OSS or Sony FE 24-105mm F4 G OSS or ...

I have verified this does NOT happen when rotating the images with ristretto.
This is a serious issue if one takes large numbers of pictures, views them and 
later depends on the EXIF data.
===


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.7.0-1-686-pae (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages geeqie depends on:
ii  geeqie-common    1:1.4-3
ii  libatk1.0-0  2.28.1-1
ii  libc6    2.27-2
ii  libcairo2    1.15.10-1
ii  libexiv2-14  0.25-3.1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8-20180207-2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.56.0-4
ii  libgtk2.0-0  2.24.32-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  liblirc-client0  0.10.0-2+b1
ii  liblua5.1-0  5.1.5-8.1+b2
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpangoft2-1.0-0    1.42.0-1
ii  libstdc++6   8-20180207-2
ii  libtiff5 4.0.9-4

Versions of packages geeqie recommends:
ii  cups-bsd [lpr]   2.2.7-1
ii  exiftran 2.10-2+b3
ii  exiv2    0.25-3.1
ii  imagemagick  8:6.9.9.34+dfsg-3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.9.34+dfsg-3
ii  librsvg2-common  2.40.20-2
ii  ufraw-batch  0.22-2
ii  zenity   3.27.90-1

Versions of packages geeqie suggests:
pn  geeqie-dbg   
ii  gimp 2.8.20-1.1
ii  libjpeg-turbo-progs [libjpeg-progs]  1:1.5.2-2+b1
pn  ufraw    
pn  xpaint   

-- no debconf information

Bug#894257: eog fails with 'BadAccess (attempt to access private resource denied)' for 6000x4000 JPG

[js jb]

Package: eog
Version: 3.28.0-2
Severity: important

Dear Maintainer,

=
After upgrading to eog 3.28.0-2 I saw it continues to fail when opening 24MP 
(6000x4000) JPG files,
although it still works on smaller 8MP files). This used to work as late as eog 
3.26 and there is no problemopening these files with ristretto or geeqie.
Below are some of the messages from /var/log/messages for eog and a backtrace 
of eog (withoug debug
symbols as eog-dbg 3.28 is not yet available on testing):



=> tail -5 /var/log/messages
Mar 27 07:55:04 localhost kernel: [125036.108772] traps: eog[11283] trap int3 
ip:b751e7b0 sp:bff40170 error:0 in libglib-2.0.so.0.5600.0[b74d+12e000]
Mar 27 11:36:20 localhost kernel: [138311.962382] traps: eog[13174] trap int3 
ip:b751f7b0 sp:bfc51240 error:0 in libglib-2.0.so.0.5600.0[b74d1000+12e000]
Mar 27 16:22:40 localhost kernel: [155492.314670] traps: eog[16015] trap int3 
ip:b754c7b0 sp:bfe79ad0 error:0 in libglib-2.0.so.0.5600.0[b74fe000+12e000]
Mar 27 16:23:04 localhost kernel: [155516.672124] traps: eog[16027] trap int3 
ip:b74fc7b0 sp:bfe0ce30 error:0 in libglib-2.0.so.0.5600.0[b74ae000+12e000]
Mar 27 16:27:52 localhost kernel: [155804.824810] traps: eog[16121] trap int3 
ip:b74fb7b0 sp:bfb5e950 error:0 in libglib-2.0.so.0.5600.0[b74ad000+12e000]


=> export GDK_SYNCHRONIZE=1
ME:=> gdb `which eog`
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/eog...(no debugging symbols found)...done.
(gdb) b gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) r A6K01000.JPG
Starting program: /usr/bin/eog A6K01000.JPG
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb3bdeb40 (LWP 16053)]
[New Thread 0xb31ffb40 (LWP 16054)]
[New Thread 0xb27ffb40 (LWP 16055)]
[New Thread 0xb1dffb40 (LWP 16056)]
[New Thread 0xace2eb40 (LWP 16057)]

(eog:16049): Gdk-ERROR **: 16:24:09.919: The program 'eog' received an X Window 
System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 8188 error_code 10 request_code 130 (MIT-SHM) minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Thread 1 "eog" received signal SIGTRAP, Trace/breakpoint trap.
0xb7d9e7b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0xb7d9e7b0 in  () at /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb7da0fa9 in g_log_writer_default () at 
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb7d9f32c in g_log_structured_array () at 
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb7d9f582 in g_log_structured () at /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb7038a0c in  () at /usr/lib/i386-linux-gnu/libgdk-3.so.0
#5  0xb70462c4 in  () at /usr/lib/i386-linux-gnu/libgdk-3.so.0
#6  0xb68d3b7a in _XError () at /usr/lib/i386-linux-gnu/libX11.so.6
#7  0xb68d077b in  () at /usr/lib/i386-linux-gnu/libX11.so.6
#8  0xb68d083f in  () at /usr/lib/i386-linux-gnu/libX11.so.6
#9  0xb68d1866 in _XReply () at /usr/lib/i386-linux-gnu/libX11.so.6
#10 0xb68ccf7f in XSync () at /usr/lib/i386-linux-gnu/libX11.so.6
#11 0xb68cd01a in  () at /usr/lib/i386-linux-gnu/libX11.so.6
#12 0xb68d44d3 in  () at /usr/lib/i386-linux-gnu/libX11.so.6
#13 0xb63a2f23 in XShmAttach () at /usr/lib/i386-linux-gnu/libXext.so.6
#14 0xb6f3d2cd in  () at /usr/lib/i386-linux-gnu/libcairo.so.2
#15 0xb6f3de0f in  () at /usr/lib/i386-linux-gnu/libcairo.so.2
#16 0xb6f3deb4 in  () at /usr/lib/i386-linux-gnu/libcairo.so.2
#17 0xb6f0722b in cairo_surface_create_similar_image () at 
/usr/lib/i386-linux-gnu/libcairo.so.2
#18 0xb7001801 in gdk_cairo_set_source_pixbuf () at 
/usr/lib/i386-linux-gnu/libgdk-3.so.0
#19 0xb7f7fe80 in  () at /usr/lib/i386-linux-gnu/eog/libeog.so
#20 0xb7f827c2 in eog_scroll_view_set_image () 

Bug#818922: Please add explanation for converting firefox to firefox-esr in testing distribution

[js jb]

hello,
In addition to adding the explanation of ESR, could you add an explanation of 
the process involved in making a mozilla releaseof firefox into a firefox-esr 
package?
Currently the latest firefox-esr in the testing distribution is 52.6.0esr-2 
while the latest stable firefox is 58.0.1 and is available in sid only,not in 
testing.

There is a very big time lag between the two versions which has a noticeable 
user impact: Amazon videos will no longer play on 52.6.0,displaying an error 
message to upgrade the browser, but they play fine in 58.0.1.
Perhaps both firefox and firefox-esr packages could find their way into testing 
to avoid this problem?
thanks,--jack

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

[js jb]

Thanks,
"BTW, your pinning and sources.list is extreme. That's not really a sensible 
thing to do and can cause a lotof trouble. "
If you can be more explicit, I'd very much appreciate the feedback.
As it is, the pinning I use is to prevent unintentional changes to nvidia 
drivers, linux kernel, and to block all ubuntu packages other than the 2 codecs 
not available in debian.Plus block versions of some packages, like vivaldi 
browser, that no longer work well with the latest codecs. 
It there's a better way to achieve these goals, I'd very much like to learn 
about it.
thanks,--jack

  From: Julian Andres Klode 
 To: js ; 879...@bugs.debian.org 
 Sent: Wednesday, October 25, 2017 4:23 PM
 Subject: Re: Bug#879786: apt-secure man page needs to provide useful pointers 
for Release file info changes
   
On Wed, Oct 25, 2017 at 04:05:24PM -0400, js wrote:
> Package: apt
> Version: 1.5
> Severity: minor
> 
> Dear Maintainer,
> 
> ==
> I use only 2 packages from ubuntu (which are not available in debian): 
> chromium-codecs-ffmpeg-extra, oxideqt-codecs-extra.

The first one does not make much sense, Debian's chromium should already 
contain all codecs.


> For this I have the ubuntu repository in sources.list along with an 
> apt_preferences file to allow
> only those 2 packages (with priority 476 < 500 for all debian).
> 
> This recently gave these errors during apt-get update:
>  W: Conflicting distribution: http://archive.ubuntu.com/ubuntu devel 
>InRelease (expected devel but got bionic)
>  N: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its 
>'Version' value from '17.10' to '18.04'
>  E: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its 
>'Suite' value from 'artful' to 'bionic'
>  E: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its 
>'Codename' value from 'artful' to 'bionic'
>  N: This must be accepted explicitly before updates for this repository can 
>be applied. See apt-secure(8) manpage for details.
> 
> The apt-secure man page is of no help in resolving this (see bottom).

That's somewhat true. You likely want to use apt instead of apt-get, that would 
ask
the question interactively. apt-get is mostly for scripting.

BTW, your pinning and sources.list is extreme. That's not really a sensible 
thing to do and can cause a lot
of trouble. Also, well, it took me a minute to clean them out for the reply - 
it can only delete one line
at a time :/

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer


   

Bug#855042: kdenlive: crash after select a font in title clip editor

[jb]

Le 06.03.17 à 09:13, Patrick Matthäi a écrit :

Am 03.03.2017 um 19:15 schrieb Aleksey Samoilov:

Hi,

I tested Kdenlive with libqt5widgets5_5.7.1~20161021+dfsg-2. There is
no problem!
Bug has gone!

Thanks for your test!

@jb
Do you want to "fix" that around in your kdenlive code or should I
reassign this issue to Qt?

This is not fixable in Kdenlive. The issue should be reported to 
debian's qtbase packaging team, especially Dmitry Shachnev who committed 
the backport causing the crash.


Thanks,

Jean-Baptiste Mardelle

Bug#754248: Just a note

[jb]

This affects me too. Regrettably some of us still need to use and develop
systems based on legacy python versions, having virtualenv working with old
python versions is important.

Problem might be related to the fact that virtualenv command now uses
python3 by default.

which virtualenv
/usr/bin/virtualenv

cat /usr/bin/virtualenv
#! /usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT:
'virtualenv==1.11.6','console_scripts','virtualenv'
__requires__ = 'virtualenv==1.11.6'
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
sys.exit(
load_entry_point('virtualenv==1.11.6', 'console_scripts',
'virtualenv')()
)

JB

Bug#681615: apt output error

[jb]

Package: anubis
Version: 4.1.1+dfsg1-3
Severity: normal

debian-miniitx root@~
## apt-get install anubis
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  guile-1.8-libs libgmp3c2 libgsasl7 libntlm0
  Suggested packages:
pidentd ident-server
The following NEW packages will be installed:
  anubis guile-1.8-libs libgmp3c2 libgsasl7 libntlm0
  0 upgraded, 5 newly installed, 0 to remove and 5 not upgraded.
  Need to get 1,498 kB of archives.
  After this operation, 5,345 kB of additional disk space will be used.
  Do you want to continue [Y/n]?
  Get:1 http://debian.savoirfairelinux.net/debian/ squeeze/main libgmp3c2 
i386 2:4.3.2+dfsg-1 [325 kB]
  Get:2 http://debian.savoirfairelinux.net/debian/ squeeze/main 
guile-1.8-libs i386 1.8.7+1-3 [720 kB]
  Get:3 http://debian.savoirfairelinux.net/debian/ squeeze/main libntlm0 
i386 1.2-1 [18.1 kB]
  Get:4 http://debian.savoirfairelinux.net/debian/ squeeze/main libgsasl7 
i386 1.4.4-2 [190 kB]
  Get:5 http://debian.savoirfairelinux.net/debian/ squeeze/main anubis i386 
4.1.1+dfsg1-3 [245 kB]
  Fetched 1,498 kB in 2s (559 kB/s)
  Selecting previously deselected package libgmp3c2.
  (Reading database ... 83718 files and directories currently installed.)
  Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.3.2+dfsg-1_i386.deb) ...
  Selecting previously deselected package guile-1.8-libs.
  Unpacking guile-1.8-libs (from .../guile-1.8-libs_1.8.7+1-3_i386.deb) ...
  Selecting previously deselected package libntlm0.
  Unpacking libntlm0 (from .../libntlm0_1.2-1_i386.deb) ...
  Selecting previously deselected package libgsasl7.
  Unpacking libgsasl7 (from .../libgsasl7_1.4.4-2_i386.deb) ...
  Selecting previously deselected package anubis.
  Unpacking anubis (from .../anubis_4.1.1+dfsg1-3_i386.deb) ...
  Processing triggers for man-db ...
  Setting up libgmp3c2 (2:4.3.2+dfsg-1) ...
  Setting up guile-1.8-libs (1.8.7+1-3) ...
  Setting up libntlm0 (1.2-1) ...
  Setting up libgsasl7 (1.4.4-2) ...
  Setting up anubis (4.1.1+dfsg1-3) ...
  update-rc.d: warning: anubis stop runlevel arguments (0 1 6) do not match 
LSB Default-Stop values (1)
  Starting an SMTP message submission daemon : anubis failed!
  invoke-rc.d: initscript anubis, action start failed.
  dpkg: error processing anubis (--configure):
   subprocess installed post-installation script returned error exit status 
1
   configured to not write apport reports
 Errors were encountered while 
processing:
  anubis
  E: Sub-process /usr/bin/dpkg 
returned an error code (1)
  
  

-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/4 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 anubis depends on:
ii  guile-1.8-libs1.8.7+1-3  Main Guile libraries
ii  libc6 2.11.3-3   Embedded GNU C Library: Shared lib
ii  libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library
ii  libgnutls26   2.8.6-1+squeeze2   the GNU TLS library - runtime libr
ii  libgpgme111.2.0-1.2  GPGME - GnuPG Made Easy
ii  libgsasl7 1.4.4-2GNU SASL library
ii  libltdl7  2.2.6b-2   A system independent dlopen wrappe
ii  libpam0g  1.1.1-6.1+squeeze1 Pluggable Authentication Modules l
ii  libpcre3  8.02-1.1   Perl 5 Compatible Regular Expressi
ii  libwrap0  7.6.q-19   Wietse Venema's TCP wrappers libra
ii  lsb-base  3.2-23.2squeeze1   Linux Standard Base 3.2 init scrip

anubis recommends no packages.

Versions of packages anubis suggests:
pn  pidentd | ident-servernone (no description available)

-- 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#680677: bash fails if PS1 has colour code

[jb]

Package: bash
Version: 4.1-3
Severity: normal

TERM=linux (Default)

LANG and LC_CTYPE mentioned below (en_US.UTF-8) , however this seems irrelevant 
as I get the same symptom even with LANG=C

I use a custom PS1 prompt in .bashrc as,
 export PS1='\e[1;33;40m\h\e[1;31;40m root\e[1;37;40m@\w\e[1;37;40m\e[m\n## '
this gives me something as ..

debian-miniitx root@~
##


If I take out the \n from my PS1, ctrl-r in bash is problematic.


Scenario i use to test,
vi .bashrc, edit PS1, (ctl-z), then I type bash, then ctl-c to see if there's 
an issue.


When trying ctl-c, i would type a few letters to match a history command, then 
tap the left/right arrow.

What I get is display corruption on the prompt line after tapping left/right 
arrow ..

PS1 with \n - no corruption
PS1 without \n - corruption


(not using an ssh session)


-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/4 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 bash depends on:
ii  base-files6.0squeeze5Debian base system miscellaneous f
ii  dash  0.5.5.1-7.4POSIX-compliant shell
ii  debianutils   3.4Miscellaneous utilities specific t
ii  libc6 2.11.3-3   Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-5 shared libraries for terminal hand

Versions of packages bash recommends:
ii  bash-completion   1:1.2-3programmable completion for the ba

Versions of packages bash suggests:
ii  bash-doc  4.1-3  Documentation and examples for the

-- 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#648750: settings not saved

[jb]

Package: lynx
Version: 2.8.8dev.5-1
Severity: important


'O' for options in application, then try to save 'Accept Changes'. Settings 
never saved.

I use lynx not primarily for web work.. but for file navigation/file editing.. 
but a bug like this shouldn't be in stable.

The only way I can make configuration changes is to make my own ~/.lynxrc file 
 And making this ~/.lynxrc is not clearly
documented anywhere.. (not in /usr/share/doc.. and only hinted of it's 
existence from  /etc/lynx-cur/lynx.cfg)


eg:

show_dotfiles=on
dir_list_style=directories_first
file_editor=mcedit



-- System Information:
Debian Release: 6.0.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/4 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 lynx depends on:
ii  lynx-cur2.8.8dev.5-1 Text-mode WWW Browser with NLS sup

lynx recommends no packages.

lynx 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#575503: nfs-common: mount.nfs defaults to nfs version 4

[JB]

Package: nfs-common
Version: 1:1.2.1-3
Severity: normal

Mounting nfs share from server running nfs version 3 results the
following:
$ sudo mount.nfs 10.0.0.121:/home/user /mnt -v
mount.nfs: timeout set for Fri Mar 26 13:44:02 2010
mount.nfs: trying text-based options
'addr=10.0.0.121,vers=4,clientaddr=10.0.0.227'
mount.nfs: mount(2): Operation not permitted
mount.nfs: Operation not permitted

Note the vers=4 option in output. Now if we use -o vers=3 to override,
all is fine.

Quoting manpage of mount.nfs:

mount.nfs4 is used for mounting NFSv4 file system, while  mount.nfs  is
used  to  mount  NFS  file  systems versions 3 or 2.

Apparently this is not true, since mount.nfs and mount -t nfs default to
nfs version 4.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser3.112 add and remove users and groups
ii  initscripts2.87dsf-8.1   scripts for initializing and shutt
ii  libc6  2.10.2-6  Embedded GNU C Library: Shared lib
ii  libcomerr2 1.41.11-1 common error description library
ii  libevent-1.4-2 1.4.13-stable-1   An asynchronous event notification
ii  libgssapi-krb5-2   1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries - k
ii  libgssglue10.1-4 mechanism-switch gssapi library
ii  libk5crypto3   1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries - C
ii  libkrb5-3  1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries
ii  libnfsidmap2   0.23-2An nfs idmapping library
ii  librpcsecgss3  0.19-2allows secure rpc communication us
ii  libwrap0   7.6.q-18  Wietse Venema's TCP wrappers libra
ii  lsb-base   3.2-23Linux Standard Base 3.2 init scrip
ii  netbase4.40  Basic TCP/IP networking system
ii  portmap6.0.0-2   RPC port mapper
ii  ucf3.0025Update Configuration File: preserv

nfs-common recommends no packages.

nfs-common 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#575359: rxvt-unicode-lite: Middle mouse paste of X selection does not work when pasting from remote VNC

[jb]

Package: rxvt-unicode-lite
Version: 9.06-3
Severity: normal

I am trying to paste a X selection with middle mouse button from remote VNC
session (running vncconfig with clipboard sharing enabled) to urxvt terminal
with n o luck. Pasting works fine in other applications (xterm, Iceweasel).
Using xvnc4viewer 4.1.1+X4.3.0-36 to access remote system. Remote system is
running:

Name: vnc-server   Relocations: (not relocatable)
Version : 4.1.1 Vendor: Red Hat, Inc.
Release : 36Build Date: Wed 01 Mar 2006 
03:28:09 PM EET
Install Date: Thu 05 Oct 2006 03:48:28 PM EEST  Build Host: 
hs20-bc1-2.build.redhat.com
Group   : User Interface/X  Source RPM: vnc-4.1.1-36.src.rpm
Size: 2637224  License: GPL
Signature   : DSA/SHA1, Mon 06 Mar 2006 10:47:23 PM EET, Key ID b44269d04f2a6fd2
Packager: Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
URL : http://www.realvnc.com
Summary : A VNC server.



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages rxvt-unicode-lite depends on:
ii  base-passwd   3.5.22 Debian base system master password
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libx11-6  2:1.3.3-1  X11 client-side library
ii  ncurses-base  5.7+20090803-2 basic terminal type definitions

rxvt-unicode-lite recommends no packages.

rxvt-unicode-lite 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#514197: ifmetric fails on amd64

[Jb boin]

Still having problems on a fresh Debian testing amd64 installation with 
a 2.6.29-2-amd64 kernel with libc6 package version 2.9-12 and ifmetric 
package version 0.3-2..




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#514197: ifmetric fails on amd64

[Jb boin]

Same here on a 2.6.28-1-amd64 official Debian kernel with ifmetric 
package version 0.3-2 and distribution is Debian Testing.


r...@servor:~# /usr/sbin/ifmetric cable3 16
NETLINK: Packet too small or truncated! 16!=16!=60



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#226172: She loves being on film

[jb Rotar]

She got so wet I could taste her even through her lace panties.

http://www.Aramovinet.com/
Be large even when flaccid



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#302326: sendmail options at gnarwl.cfg

[JB]

After create user gnarwl and chown'ed his home, I needed change from
mta /usr/sbin/sendmail -F $recipient to mta /usr/sbin/sendmail -F
$recipient -t $sender



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#327025: Watch trade

[jb Lips]

http://www.mypicshare.com/wxteowjspic.html

For GUI exes, error output is displayed using the MessageBox API.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#119471: libice6: want library to clean up stale lockfiles

[jb]

Hi Bruce,

 I haven't noticed this bug in years. If I ever see it again,
I will reopen the bug.

Thanks,

Jim

 Hi Jim,

 About 5 years ago, you reported a bug to the Debian BTS
 about libice not removing .ICEauthority lock files, causing
 X to fail to start after a poweroff crash. Did you reproduce
 this problem recently? If not, I will close this bug in the
 next weeks.

 Brice