Bug#1040526: possible solution

[mh]

This is how the original template for /etc/grub.d/40_custom looks:


#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply
type the # menu entries you want to add after this comment.  Be careful
not to change # the 'exec tail' line above.
*

It should be changed to:

*
#!/bin/sh
if grep -Fxq "#GRUB_DISABLE_OS_PROBER=false" /etc/default/grub; then
  sed -En "s/^menuentry '([^']+).*/Found custom entry: \1/p" $0 >&2;
fi; #new for feedback on terminal
exec tail -n +6 $0 # +6 instead of +3 due to above lines
# This file provides an easy way to add custom menu entries.  Simply
type the # menu entries you want to add after this comment.  Be careful
not to change # the 'exec tail' line above.
*

This way the user gets a *complete* on screen feedback of what
kernel entries are found and copied to /boot/grub/grub.cfg .
(The explaining comments should obviously be deleted)

With os-prober enabled those custom entries would be found without this
new function and then copied to grub.cfg AND listed as such on screen.
To avoid double entries the new added function will therefore be
executed only if os-prober is _not_ active.


Greetings

Michael

Bug#1040526: Acknowledgement (grub-pc: update-grub; 40_custom - visible feedback)

[mh]

Am Fri, 07 Jul 2023 10:06:04 +
schrieb "Debian Bug Tracking System" :
...

I need to correct a wrong path:

wrong:

visible as on screen output (like all other kernels found by other
scripts under /etc/40_custom)


right:
***
visible as on screen output (like all other kernels found by other
scripts under /etc/grub.d/)
***

Michael

Bug#1040526: grub-pc: update-grub; 40_custom - visible feedback

[mh]

Package: grub-pc
Version: 2.06-14
Severity: wishlist

Dear Maintainer,

This is a followup to bug 1040455 (closed now) as a wishlist bug:

Please change the template 40_custom in a way that users get a visible
feedback for their entries when running update-grub.

A somewhat skilled user might be able to create a new menuentry in
/ect/grub.d/*40_custom. But making something like
"menuentry 'what-name-ever'"
visible as on screen output (like all other kernels found by other
scripts under /etc/40_custom) needs too much scripting skills for
average users. So please enhance the existing script template
accordingly (upstream) to show some usefull feedback / visible output.

Michael


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sdb1 / ext4 rw,noatime 0 0
/dev/sdb3 /dtn/archiv ext4 rw,noatime 0 0
/dev/sdc3 /dtn/soft_alt ext4 rw,noatime 0 0
/dev/sdc6 /dtn/vid ext4 rw,noatime 0 0
/dev/sdc5 /dtn/musik ext4 rw,noatime 0 0
/dev/sda7 /dtn/rec ext4 rw,noatime 0 0
/dev/sda5 /home ext4 rw,noatime 0 0
/dev/sda2 /var ext4 rw,noatime 0 0
/dev/sda9 /var/cache/apt-cacher-ng ext4 rw,noatime 0 0
/dev/sda3 /var/cache/apt/archives ext4 rw,noatime 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-SAMSUNG_HM320II_S1X4J9CB302135
(hd1)
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_120GB_S1D5NSAF622954R
(hd2)   /dev/disk/by-id/ata-WDC_WD5000AVDS-63U7B0_WD-WCAV95203084
(hd3)   /dev/disk/by-id/ata-WDC_WD10EFRX-68FYTN0_WD-WCC4J4CPT7VA
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1'
 655268bd-541f-4863-a960-951dc0cdcb46 else search --no-floppy --fs-uuid
--set=root 655268bd-541f-4863-a960-951dc0cdcb46 fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1280x1024
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=1280x1024
export linux_gfx_mode
menuentry 'siduction 2018.3.0 Patience (Xorg) GNU/Linux, with Linux
6.3.11-1-siduction-amd64' --class siduction --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-6.3.11-1-siduction-amd64-advanced-655268bd-541f-4863-a960-951dc0cdcb46'
{ load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform =
xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root
--hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1
--hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1'
655268bd-541f-4863-a960-951dc0cdcb46 else search --no-floppy --fs-uuid
--set=root 655268bd-541f-4863-a960-951dc0cdcb46 fi echo 'Loading
Linux 6.3.11-1-siduction-amd64 ...' linux
/boot/vmlinuz-6.3.11-1-siduction-amd64
root=UUID=655268bd-541f-4863-a960-951dc0cdcb46 ro  quiet
systemd.show_status=1 echo  'Loading initial ramdisk ...'
initrd  /boot/initrd.img-6.3.11-1-siduction-amd64 } menuentry
'siduction 2018.3.0 Patience (Xorg) GNU/Linux, with Linux
6.3.4-1-siduction-amd64' --class siduction --class gnu-linux --class
gnu --class os $menuentry_id_option

Bug#1040455: update-grub: when generating new grub.cfg entries from 40_custom not show as output on screen

[mh]

Am Thu, 6 Jul 2023 11:20:32 +0100
schrieb Steve McIntyre :

> Hi,
>
> On Thu, Jul 06, 2023 at 10:03:23AM +0200, mh wrote:
> >Package: grub-pc
> >Version: 2.06-14
> >Severity: important
> >
> >Dear Maintainer,
> >
> >* What led up to the situation?
> >executing "update-grub" (os-prober disabled!)
> >
> >* What exactly did you do (or not do) that was effective (or
> > ineffective)?
> >"update-grub" as root (os-prober disabled!)
> >
> >* What was the outcome of this action?
> >On screen (xterm) I saw all the installed kernels of system grub was
> >  running from. In addition all bootable siduction-live.iso files
> > were listed and appended to the list (due to a script in
> >  /etc/grub.d/60_fll-fromiso). The entries defined in
> >  /etc/grub.d/40_custom did not appear in this on screen list.
> >
> >This leads  to the seemingly obvious conclusion they were not found
> >or honoured. Only further investigation will show they had been
> >copied to /boot/grub/grub.cfg .
>
> Sorry, but this bug report is way too vague to be useful. You've shown
> no output here, so we can only guess at what you're seeing. You're
> comparing normal output to what an extra local script is saying,
> maybe?
>

Sorry, you are right, I should have shown what's the output on screen
(xterm) and how the generated file /boot/grub/grub.cfg looks. Here it
is:

This what the user sees in xterm:

**
# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.3.11-1-siduction-amd64
Found initrd image: /boot/initrd.img-6.3.11-1-siduction-amd64
Found linux image: /boot/vmlinuz-6.3.4-1-siduction-amd64
Found initrd image: /boot/initrd.img-6.3.4-1-siduction-amd64
Found linux image: /boot/vmlinuz-6.3.0-2-amd64
Found initrd image: /boot/initrd.img-6.3.0-2-amd64
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable
partitions. Systems on them will not be added to the GRUB boot
configuration. Check GRUB_DISABLE_OS_PROBER documentation entry.
Found fromiso: siduction-21.1.0-cblues-lxqt-amd64-202102141944.iso on
/dev/sdc3
Found fromiso: siduction-future-plasma-amd64-latest.iso on /dev/sdc3
Found fromiso: siduction-patience-lxqt-amd64-latest.iso on /dev/sdc3
done
**

And this is the generated /boot/grub/grub.cfg

*

# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1'
 UUID-edited else search
--no-floppy --fs-uuid --set=root UUID-edited fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1280x1024
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=1280x1024
export linux_gfx_mode
menuentry 'siduction 2018.3.0 Patience (Xorg) GNU/Linux, with Linux
6.3.11-1-siduction-amd64' --class siduction --class gnu-linux --class
gnu --clas

Bug#1040455: update-grub: when generating new grub.cfg entries from 40_custom not show as output on screen

[mh]

Package: grub-pc
Version: 2.06-14
Severity: important

Dear Maintainer,

* What led up to the situation?
executing "update-grub" (os-prober disabled!)

* What exactly did you do (or not do) that was effective (or
 ineffective)?
"update-grub" as root (os-prober disabled!)

* What was the outcome of this action?
On screen (xterm) I saw all the installed kernels of system grub was
  running from. In addition all bootable siduction-live.iso files were
  listed and appended to the list (due to a script in
  /etc/grub.d/60_fll-fromiso). The entries defined in
  /etc/grub.d/40_custom did not appear in this on screen list.

This leads  to the seemingly obvious conclusion they were not found or
honoured. Only further investigation will show they had been copied to
/boot/grub/grub.cfg .

This is confusing behaviour as the user expects to see the outcome of
his action, i.e. the *complete* final result on screen (xterm), not
only a part of a list which gives the impression something has gone
wrong.

* What outcome did you expect instead?
Show the complete list with all entries as copied to /boot/grub/grub.cfg

I classified it as "important" as this bug gives the user the
(wrong but convincing) impression of not successfully working!

(I accidentally booted a Debian-siduction kernel, not the pure Debian
Kernel. The bug is always the same)


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sdb1 / ext4 rw,noatime 0 0
/dev/sdb3 /dtn/archiv ext4 rw,noatime 0 0
/dev/sdc5 /dtn/musik ext4 rw,noatime 0 0
/dev/sdc3 /dtn/soft_alt ext4 rw,noatime 0 0
/dev/sdc6 /dtn/vid ext4 rw,noatime 0 0
/dev/sda7 /dtn/rec ext4 rw,noatime 0 0
/dev/sda5 /home ext4 rw,noatime 0 0
/dev/sda2 /var ext4 rw,noatime 0 0
/dev/sda3 /var/cache/apt/archives ext4 rw,noatime 0 0
/dev/sda9 /var/cache/apt-cacher-ng ext4 rw,noatime 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-SAMSUNG_SNR
(hd1)
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_120GB_SNR
(hd2)   /dev/disk/by-id/ata-WDC_SNR
(hd3)   /dev/disk/by-id/ata-WDC_SNR
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1'
 UUID-deleted else search
--no-floppy --fs-uuid --set=root
UUID-deleted fi
font="/usr/share/grub/unicode.pf2" fi

if loadfont $font ; then
  set gfxmode=1280x1024
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=1280x1024
export linux_gfx_mode
menuentry 'siduction 2018.3.0 Patience (Xorg) GNU/Linux, with Linux
6.3.11-1-siduction-amd64' --class siduction --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-6.3.11-1-siduction-amd64-advanced-UUID-deleted'
{ load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform =
xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root
--hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1
--hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1'
655268bd-541f-4863-a960-951dc0cdcb46 else search --no-floppy 

Bug#1038068: additional info

[mh]

 is against the do-not-break-userspace-rule.

Thanks

MH

Bug#1034746: Bug: mk2efs/mkfs.ext4 does not create the correct amount of inodes if -i is specified with 640k to 832k

[The MH]

You are completely right. I misunderstood the function to be linear
between -i 512k and -i 1M, thus my expectation to see a linear
decrease in inodes when increasing the -i option. But of course this
isn't the case, since the number of inodes is being halved every time
the -i option is doubled. So there is no bug and this issue can be
closed. Thank you for the quick response and for clarifying.

Greetings.

Am Di., 25. Apr. 2023 um 05:16 Uhr schrieb Theodore Ts'o :
>
> On Sun, Apr 23, 2023 at 09:34:39AM +0200, The MH wrote:
> > Package: e2fsprogs
> > Version: 1.46.5
> > Severity: minor
> >
> > I did not find this bug in the patchnotes for the latest versions on
> > e2fsprogs.sourceforge.net/e2fsprogs-release.html, so I assume it is
> > still present.
> >
> > I stumbled upon this, because I wanted to specifiy -i 768k for my main
> > data drive (a 2 TB hard drive) as kind of less "aggressive" option
> > than -i 1M or -T largefile.
> >
> > I proceeded to test this behaviour against a file container with
> > exactly 4 GiB. From what I know the value should increment in steps of
> > 512 for every 64k as this is the boundary for one inode block per
> > block group which ranges from 16 to 8 in this scenario.
> >
> > -i 512k: number of inodes: expected 8192 actual 8192 -> ok
> > -i 576k: number of inodes: expected 7680 actual 7680 -> ok
> >
> > -i 640k: number of inodes: expected 7168 actual 6656
>
> I'm not sure how you are calculating the "expected" value, but the
> inode ratio is literally that.  So when you have an inode ratio of
> 640k, we take the total size of the file system, and divide it by the
> inode ratio to determine the target number of inodes.  So the target is
>
> 4GiB / 640k or 4294967296 / 655360 or 6553.60.  This gets rounded up
> to 6556.
>
> > -i 704k: number of inodes: expected 6656 actual 6144
>
> And...
>
> 4 GiB / 704k or 4294967296 / 720896 or 5957.78
>
> ... which gets rounded up to 6144.  So how does the rounding up
> happen?  Well, a 4GiB file system, using a 4k block size, has 1048576
> 4k blocks.  Since there are 32,768 blocks in a block group, that means
> there are 32 block groups.  So that means we need roughly 186.18
> inodes per block group.  Since the default inode size is 256 bytes,
> that means we can have 16 inodes per 4k block, and if we had 11 inode
> table blocks per block group, that would work out to be 176 inodes per
> block group, which is too small (it's less than 186 inodes), and 12
> inode table blocks works out to 192 inodes per block group.  And 32
> block groups times 192 inodes per block group works out to 6144, which
> is the actual number that you've seen.
>
> So this isn't a bug in mke2fs, but rather an apparent misunderstanding
> of how the inode ratio is used.  In general, the basic idea is if the
> system administrator thinks that the average size of the inodes is,
> say, 704k, we need to make sure that there are at *least* 5958 inodes
> (that is, 4 GiB / 704k and since the .78 in 5957.78 makes no sense,
> that gets rounded to 5958).  But we need to have an integral number of
> inode table blocks, and there's no point in having a partially filled
> inode table block, and that's why it ends up being 6144 inodes.  I'm
> not at all sure how you came up with your expected 6656 inodes,
> consider that 6656 * 704k is 4.47 GiB, which is quite a bit more than
> 4GiB.
>
> Cheers,
>
> - Ted

Bug#1034746: Bug: mk2efs/mkfs.ext4 does not create the correct amount of inodes if -i is specified with 640k to 832k

[The MH]

Package: e2fsprogs
Version: 1.46.5
Severity: minor

I did not find this bug in the patchnotes for the latest versions on
e2fsprogs.sourceforge.net/e2fsprogs-release.html, so I assume it is
still present.

I stumbled upon this, because I wanted to specifiy -i 768k for my main
data drive (a 2 TB hard drive) as kind of less "aggressive" option
than -i 1M or -T largefile.

I proceeded to test this behaviour against a file container with
exactly 4 GiB. From what I know the value should increment in steps of
512 for every 64k as this is the boundary for one inode block per
block group which ranges from 16 to 8 in this scenario.

-i 512k: number of inodes: expected 8192 actual 8192 -> ok
-i 576k: number of inodes: expected 7680 actual 7680 -> ok

-i 640k: number of inodes: expected 7168 actual 6656
-i 704k: number of inodes: expected 6656 actual 6144
-i 768k: number of inodes: expected 6144 actual 5632
-i 832k: number of inodes: expected 5632 actual 5120

-i 896k: number of inodes: expected 5120 actual 5120 -> ok
-i 960k: number of inodes: expected 4608 actual 4608 -> ok
-i 1024k or 1M: number of inodes: expected 4096 actual 4096 -> ok


Also I want to say a big thank you for all the great work with Debian
and FOSS software.

Bug#1022275: Acknowledgement (nala: missing option "download only")

[mh]

Am Sun, 23 Oct 2022 12:27:04 +
schrieb "Debian Bug Tracking System" :

Hi, I need to change the "severity", it is not a wishbug but a bug.

There is a "-d" option, but it does not work (I am not the only to have
experieced it) whereas the long version "--download-only" works.

So This wishbug should be changed to whatever is appropriate.

Sorry for the confusion

MH


> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1022275:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022275.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Volian Developers 
>
> If you wish to submit further information on this problem, please
> send it to 1022...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>

Bug#1022174: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#1021974: fixed in nvidia-graphics-drivers-tesla-470 470.141.03-3)

[mh]

Am Mon, 24 Oct 2022 16:24:08 +
schrieb "Debian Bug Tracking System" :

> This is an automatic notification regarding your Bug report
> which was filed against the src:nvidia-graphics-drivers-tesla-470
> package:
>
> #1022174: linux-image-6.0.0-1-amd64: nvidia 470 modul builds
> successfully, but does not get loaded on boot -> no X
>
> It has been closed by Debian FTP Masters
>  (reply to Andreas Beckmann
> ).
>
> 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 Debian FTP
> Masters  (reply to Andreas Beckmann
> ) by replying to this email.
>
>

Confirmed. New Version solves the problem.

Bug#1022174: Acknowledgement (linux-image-6.0.0-1-amd64: nvidia 470 modul builds successfully, but does not get loaded on boot -> no X)

[mh]

ion is not an integer
2> /var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/nv-acpi.c:1576:72:
2> error: ‘struct acpi_device’ has no member named ‘node’; did you mean
2> ‘fwnode’? if nm
2> /var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/nv.o
2> 2>/dev/null | grep -q __ksymtab; then  gcc-12 -E -D__GENKSYMS__
2> 2>-Wp,-MMD,/var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/.nv.o.d
2> 2>-nostdinc -I/usr/src/linux-headers-6.0.0-1-common/arch/x86/include
2> 2>-I./arch/x86/include/generated
2> 2>-I/usr/src/linux-headers-6.0.0-1-common/include -I./include
2> 2>-I/usr/src/linux-headers-6.0.0-1-common/arch/x86/include/uapi
2> 2>-I./arch/x86/include/generated/uapi
2> 2>-I/usr/src/linux-headers-6.0.0-1-common/include/uapi
2> 2>-I./include/generated/uapi -include
2> 2>/usr/src/linux-headers-6.0.0-1-common/include/linux/compiler-version.h
2> 2>-include
2> 2>/usr/src/linux-headers-6.0.0-1-common/include/linux/kconfig.h
2> 2>-include
2> 2>/usr/src/linux-headers-6.0.0-1-common/include/linux/compiler_types.h
2> 2>-D__KERNEL__
2> 2>-fmacro-prefix-map=/usr/src/linux-headers-6.0.0-1-common/= -Wall
2> 2>-Wundef -Werror=strict-prototypes -Wno-trigraphs
2> 2>-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE
2> 2>-Werror=implicit-function-declaration -Werror=implicit-int
2> 2>-Werror=return-type -Wno-format-security -std=gnu11 -mno-sse
2> 2>-mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64
2> 2>-falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387
2> 2>-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
2> 2>-mno-red-zone -mcmodel=kernel -Wno-sign-compare
2> 2>-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern
2> 2>-mindirect-branch-register -mindirect-branch-cs-prefix
2> 2>-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
2> 2>-fno-delete-null-pointer-checks -Wno-frame-address
2> 2>-Wno-format-truncation -Wno-format-overflow
2> 2>-Wno-address-of-packed-member -O2 -fno-allow-store-data-races
2> 2>-Wframe-larger-than=2048 -fstack-protector-strong
2> 2>-Wno-array-bounds -Wimplicit-fallthrough=5 -Wno-main
2> 2>-Wno-unused-but-set-variable -Wno-unused-const-variable
2> 2>-Wno-dangling-pointer -ftrivial-auto-var-init=zero
2> 2>-fno-stack-clash-protection -pg -mrecord-mcount -mfentry
2> 2>-DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla
2> 2>-Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation
2> 2>-Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized
2> 2>-Wno-alloc-size-larger-than -fno-strict-overflow -fno-stack-check
2> 2>-fconserve-stack -Werror=date-time
2> 2>-Werror=incompatible-pointer-types -Werror=designated-init
2> 2>-Wno-packed-not-aligned -g
2> 2>-I/var/lib/dkms/nvidia-tesla-470/470.141.03/build/common/inc
2> 2>-I/var/lib/dkms/nvidia-tesla-470/470.141.03/build -Wall -MD
2> 2>-Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__
2> 2>-DMODULE -DNVRM -DNV_VERSION_STRING=\"470.141.03\"
2> 2>-Wno-unused-function -Wuninitialized -fno-strict-aliasing
2> 2>-mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
2> 2>-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
2> 2>-I/var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia
2> 2>-DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG
2> 2>-DMODULE  -DKBUILD_BASENAME='"nv"' -DKBUILD_MODNAME='"nvidia"'
2> 2>-D__KBUILD_MODNAME=kmod_nvidia
2> 2>/var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/nv.c |
2> 2>scripts/genksyms/genksyms   -r /dev/null >>
2> 2>/var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/.nv.o.cmd;
2> 2>fi


Thanks and Good Luck

MH

 


Am Fri, 21 Oct 2022 12:45:04 +
schrieb "Debian Bug Tracking System" :

> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 1022174:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022174.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
> 
> If you wish to submit further information on this problem, please
> send it to 1022...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#1021032: vlc black screen while streaming TV

[mh]

Package: vlc
Version: 3.0.17.4-5
Followup-For: Bug #1021032

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

   * What led up to the situation?
The current version solves the problem only in part:

No problems viewing videos from HD.

But when I use VLC to view a TV channel, I can see the first it
connects to, but when I switch channels I have a black vlc window.
HW: Bus 002 Device 003: ID 2040:0265 Hauppauge WinTV-dualHD DVB
$ lsmod | grep haup
rc_hauppauge   16384  0
rc_core40960  3 em28xx_rc,rc_hauppauge

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

"/usr/bin/vlc .xspf"

   * What was the outcome of this action?

vlc connects successfully to first channel on the list; I have embedded
video in vlc window.

But as soon as I change the channel by selectin a new item on the
channel list, the embeddet vindow becoms black and stays black no
matter how often or to which channel I try to connect.
But on closing vlc I can see the video in a no embedded window behind
the vlc window for a fraction of a second (pleas note: in this case VLC
was ***not*** opened with the "--no-embedded-video" option).


   * What outcome did you expect instead?

embedded video.

*** End of the template - remove these template lines ***

I had a similar problem when using vlc for TV streaming prior to the
current black screen bug: I had *occasionally* a black screen when
switching channels, which the in most cases this could be solved by
switching again to an other channel and back again. Sometimes however
it would freeze vlc completely and I had to close my X session.

Now the blackscreen doesn't show up randomly but every time and
reproducibly when I switch the TV channel. When I open VLS using the
"--no-embedded-video" option all works well.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.13-1-siduction-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 vlc depends on:
ii  vlc-bin  3.0.17.4-5
ii  vlc-plugin-base  3.0.17.4-5
ii  vlc-plugin-qt3.0.17.4-5
ii  vlc-plugin-video-output  3.0.17.4-5

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.17.4-5
ii  vlc-plugin-access-extra3.0.17.4-5
ii  vlc-plugin-notify  3.0.17.4-5
ii  vlc-plugin-samba   3.0.17.4-5
ii  vlc-plugin-skins2  3.0.17.4-5
ii  vlc-plugin-video-splitter  3.0.17.4-5
ii  vlc-plugin-visualization   3.0.17.4-5

Versions of packages vlc suggests:
ii  vlc-plugin-fluidsynth  3.0.17.4-5
pn  vlc-plugin-jack
ii  vlc-plugin-pipewire3-2
ii  vlc-plugin-svg 3.0.17.4-5

Versions of packages libvlc-bin depends on:
ii  libc62.35-2
ii  libvlc5  3.0.17.4-5

Versions of packages libvlc5 depends on:
ii  libc62.35-2
ii  libvlccore9  3.0.17.4-5

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.17.4-5

Versions of packages vlc-bin depends on:
ii  libc6   2.35-2
ii  libvlc-bin  3.0.17.4-5
ii  libvlc5 3.0.17.4-5

Versions of packages vlc-plugin-access-extra depends on:
ii  libc62.35-2
ii  libsrt1.5-gnutls 1.5.1-1
ii  libvlccore9 [vlc-plugin-abi-3-0-0f]  3.0.17.4-5
ii  libvncclient10.9.13+dfsg-4
ii  libxcb-composite01.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-20
ii  libarchive13 3.6.0-1
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.2.7.2-1
ii  libass9  1:0.16.0-1
ii  libavahi-client3 0.8-6
ii  libavahi-common3 0.8-6
ii  libavc1394-0 0.5.4-5
ii  libavcodec59 7:5.1.2-1
ii  libavformat597:5.1.2-1
ii  libavutil57  7:5.1.2-1
ii  libbluray2   1:1.3.3-1
ii  libc62.35-2
ii  libcairo21.16.0-6
ii  libcddb2 1.3.2-7
ii  libchromaprint1  1.5.1-2+b1
ii  libdav1d61.0.0-2
ii  libdbus-1-3  1.14.2-1
ii  libdc1394-25 2.2.6-4
ii  libdca0  0.0.7-2
ii  libdvbpsi10  1.3.3-1
ii  libdvdnav4   

Bug#1021032: Your mail

[mh]

On Mon, 3 Oct 2022 07:46:54 +0100 Rik Mills  wrote:
...

> Since it seems to affect only the Qt UI, it is most probably a
> problem with the last Qt update. Again, please check with
> --no-embedded-video."
>
>

I have the same black screen problem. "vlc --no-embedded-video"
circumvents/solves the problem.

My timeline as well strengthens your statement that QT
might be responsible for the black screen as this fits my update
timeline:

last vlc update was September, 23., and it worked until yesterdays QT
update.

Thanks

Michael

Bug#1009320: FW issue

[mh]

It seems 5.17.x has problems with the respective FW (no problems with
prior kernels)

dmesg output after trying to load list of broadcasters
*
[ 6801.250773] si2168 2-0064: downloading firmware from file
'dvb-demod-si2168-b40-01.fw' [ 6801.634181] si2168 2-0064: firmware
version: B 4.0.11 [ 6801.643054] si2157 5-0060: found a 'Silicon Labs
Si2157-A30 ROM 0x50' [ 6801.643117] si2157 5-0060: Can't continue
without a firmware.
**

Greetings

MH

Bug#1004402: revoke bugreport

[mh]

Hi

I revoke the bugreport. Problem seems solved with current version.

I encountered this problem with the previous version. While writing the
bug report I was made aware of a newer version ... which I installed.
Then I tried and had the same problems. Now, next day after a reboot the
problem is gone. So it seems this reboot was necessary for all new
features come into effect.

Sorry for the noise.

Thanks.

MH

Bug#1004402: it's worse

[mh]

As you can't navigate to the folder you like to save your document to,
it's even worse. I'd like to0 raise the severity to important, because
this makes (under fluxbox) the file management somewhat pointless. You
have to dump you document to some available folder and the use a
working filemanger to move it where it belongs. Then you have lost it
in your libreoffice file history!

Greetings

MH

Bug#996503: however sddm-greeter --test-mode starts from session

[mh]

running sddm-greeter --test-mode from a running session does start sddm 
properly. Maybe a race condition? Willing to help test suggestions.

Bug#982742: solved

[mh]

Hi to all,

comparing avahi settings was much less pain then I expected.

On the installation with ipp-usb not working the file

/etc/avahi/avahi-daemon.conf

had an active (non commented out) line:

allow-interfaces=eth9


On my installation with ipp-usb working this line in the respective
file reads:

#allow-interfaces=eth0

So it is commented out and names a different interface.


After commenting out this line in the problematic installation the
printer is visible and configurable in the cups administration. As with
the other installations, two printers show up in the print menue
(Libreoffice) and I can print successfully.

I have no idea how this setting ended up in /etc/avahi/avahi-daemon.conf

Thanks to all who helped finding the flaw. Feel free to contact me if
you think I could help here in the region where I live (Aachen/Germany).

Greetings

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Tue, 16 Feb 2021 01:11:32 +0300
schrieb Alexander Pevzner :

Hi Alexander. Thanks for helping here.

>
> As I'm not very familiar with Avahi troubleshooting, any help or
> ideas are welcome.
>

Do you suspect some configuration issue or anything which leaves traces
within the file system?

If so, is there a way (other than comparing file by file looking at it)
to compare the avahi settings (or whatever) of my working installation
with to one not working?
I could mount one system somewhere into the other. Is there a
software or command to compare the relevant directories? Would this
help at all?

Or would it help to purge avahi* together with the few depending
packages and reinstall them?

Greetings

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Tue, 16 Feb 2021 00:00:47 +0300
schrieb Alexander Pevzner :

> Hi Michael,
>
> On 2/15/21 11:45 PM, mh wrote:
> > Thanks. Let me know any time how I can help.
>
> Thanks for logs. Looks like something goes wrong with Avahi. To
> check, please do the following experiment.
>
> 1. From one console, run: avahi-publish -s test _test._tcp 0
>
> This command should print "Established under name 'test'", and should
> not exit.

That's how it is.

>
> 2. From another console, run: avahi-browse -rt _test._tcp
>
> I want to see output of this command.

No output:
# avahi-browse -rt _test._tcp
~#

>
> And one more question: what Debian version do you use

it is Debian/sid(uction) up to date, booted with

# uname -r
5.10.0-3-amd64

standard Debian Kernel. (this siduction installation was made based on a
siduction live-ISO years ago)

Siduction is pure Debian/sid with some artwork and own kernel (not
booted here).

> and what Avahi
> version do you use?
>

avahi-daemon:
  Installiert:   0.8-5

avahi-utils:
  Installiert:   0.8-5


Thanks

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Mon, 15 Feb 2021 18:57:44 +
schrieb Brian Potkin :

> ...
> siduction is based on Debian unstable, so, if (A) and (B) are fully
> uo to date, the printing systems should be identical. You have shown
> that ipp-usb works fine on the siduction installation. That is what
> (to me at least) is so puzzling.

The same goes for me. That's the situation which drove me crazy the
last year. I was about to buy a new printer ... until, as a
last-ditch attempt I wrote this bug report. So thanks again.
> 
> I realise you are now happy with your printing situation, so thanks
> for continuing to engage with this ipp-usb issue.

Sure. See above ;-)
But the thing that makes me hesitant is the following: I migrated his
installation multiple times from one partition and disk to another. And
it once had serious systemd problems during a dist-upgrade due to the
drive giving up slowly. I could
repair/overwrite/reinstall/whatever-one-would-call-it this installtion
years ago. And it worked since. But I can't exclude there's a sutble
flaw hidden in some corner.
On the bright side: The printer worked the first years.

> ...
> > (B) There is a flaw somewhere within this installation which
> > *affects* ipp-usb without ipp-usb neccessarily being the cause.  
> 
> A fair assessment.

> ... 

> > The same on the problematic installation (B) with ipp-usb
> > reinstalled and rebooted:
> > 
> > $  lp -d OKI_B432_010E46_USB_ ~/.bashrc
> > lp: Error - The printer or class does not exist.
> > 
> > ~$ lp -d OKI_DATA_CORP_B432 ~/.bashrc
> > Anfrage-ID ist OKI_DATA_CORP_B432-5 (1 Datei(en))
> > 
> > but NO print. And in the cups joblist the same long known error:
> > 
> > "Warte darauf dass der Drucker verfügbar wird."
> > Waiting for the printer to become available
> > 
> > And the printer's little LCD is showing: Ready to print.
> > 
> > And the moment I purge ipp-usb again, the printer starts to
> > print without the job being sent again.  
> 
> Just to clear up something: would you stop ipp-usb on (B):
> 
>   systemctl stop ipp-usb
> 
> Do you get an output from 'lpstat -l -e'?

# systemctl stop ipp-usb
~#

# lpstat -l -e
OKI_DATA_CORP_B432 permanent
ipp://localhost/printers/OKI_DATA_CORP_B432
usb://OKI%20DATA%20CORP/B432?serial=AK76039718


> ...

> The file I downloaded has the PPDs under the General Public License.

Didn't know PPD is text. You are right. That's in contrast to what the
linked document on the website says. All the better. I updated my
wishlist bug accordingly.

> 
> Cheers,
> 
> Brian.


Thanks

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Mon, 15 Feb 2021 15:12:49 +
schrieb Brian Potkin :

> On Mon 15 Feb 2021 at 14:27:59 +0100, mh wrote:
>
> > Am Mon, 15 Feb 2021 10:26:52 +
> > schrieb Brian Potkin :
> >
> > > On Sun 14 Feb 2021 at 20:31:28 +0100, mh wrote:
> > >
> > > [...]
> > >
> > > > # ippfind -T 5
> > > > ~#
> > >
> > > An IPP printer is not found. This would fit the observation that
> > > cups-browsed has not set up a print queue. I have come to the
> > > conclusion that the B432 does not implement IPP-over-USB
> > > correctly.
> >
> > First: Thanks for your help and for all your efforts. But further
> > investigation and tests based on the new knowledge provided by you
> > lets me come to a different conclusion (see below). I didn't know
> > about ipp-usb, how it works and what it does and it automagically
> > being configured.
>
> I've tried to help with understanding by quoting a wiki link.

Yes. Thanks for that. I only wanted to point out I wasn't aware of
what actually happens during cups config. I have a better
understanding.

>
> > > A queue set up with a vendor PPD will not function while ipp-usb
> > > is active,

Only for curiosity:
On systems where there is NO problem, why do I see one printer in cups
config (network printer) resulting in two printers in the printing menu?

> so purge it and proceed as you did with the Live ISO.
> > > Also see #982190:
> > >
> > >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982190
> > >
> > > Cheers,
> > >
> > > Brian.
> >
> > Purging ipp-usb instantly made the cups webinterface showing my
> > printer. So I could configure it using the vendor PPD file. Printing
> > menue (Libreoffice) shows one OKI printer. Print succeeded.
> > Thanks.
>
> The printer would have shown under Local Printers. With ipp-usb
> active it shows under Discovered Network Printers. This is because
> IPP-over-USB effectively treats the printer as a network connected
> device, not a USB connected device.
>
>   https://wiki.debian.org/SystemPrinting#The_CUPS_Web_Interface
>
> > So the main issue is solved as I can print from within my
> > default system. From what I've seen during configuration and
> > printing, the printer setup seems stabel, the printer showed up
> > immediately, the print job is carried out without much delay.
>
> Good.

> ...

>
> > I then investigated the LIVE-ISO. To my surprise ipp-usb is
> > installed within the LIVE-ISO. All the commands which failed/did
> > have an empty output on my default system work here with the
> > expected output (I guess), except for # avahi-browse -rt _ipp._tcp
> > due to avahi-browse not being installed:
>
> This is the concerning part. Why do some commands like ippfind,
> lpstat -e and avahi-browse give empty outputs on Debian unstable? Are
> the Debian and Live ISO versions of ipp-usb the same?

It is all Debian/unstable. And it does not depend on the version of
ipp-usb ( 0.9.16-1  and 0.9.17-1 ). Both work on live-iso (from
2021.02, the 2020.07 version didn't ship ipp-usb ) or new installation
(2021.02 dist-upgraded), neither work with my old installation. I know
this for a fact because the problem persist longer than 0.9.17-1 exists.

I can live without ipp-usb working on this installation. But if someone
tells me how to investigate the flaw, I am happy to investigate, too.


> ...

> You would submit a wishlist bug against printer-driver-oki.

I will.

>
> Thank you for your detailed report.
>
> Brian.

Thank you for all your help.

Michael

Bug#982875: Acknowledgement (cups-printer-oki: could PPD file for okiB432 be included?)

[mh]

Am Mon, 15 Feb 2021 18:57:04 +
schrieb "Debian Bug Tracking System" :

> Thank you for filing a new Bug report with Debian.

In contrast to what a document states to which a link on the website
points to, the PPD file is free software:

*PPD-Adobe: "4.3"
*% ==
*% Printer Description File for OKI B432(PS) (Linux)
*% Copyright 2016 Oki Data Corporation
*% Date:Jun 10, 2016
*%
*% ==
*% GPL $Revision: 1.0 $ $RCSfile: OKB432_a.ppd,v $
*%
*% Note)
*% This PostScript Printer Description(PPD) file is free software; you
*% can redistribute it and/or modify it under the terms of the GNU
*% General Public License version 2 or later as published by the Free
*% Software Foundation.

...

So, it should be no problem to include this file and the three others in
the package to the cups-printer-oki database.

Thanks

Michael




>
> You can follow progress on this Bug here: 982875:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982875.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  unknown-pack...@qa.debian.org
>
> If you wish to submit further information on this problem, please
> send it to 982...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Mon, 15 Feb 2021 15:28:57 +0100
schrieb Till Kamppeter :

Hi Till,

thanks for your efforts to help. But to avoid any confusion I summarize
the situation:

(A) 
My printer works fine with this computer under the following
conditions:
Booting a LIVE-ISO (Debain/sid based ISO from siduction.org) or booting
an installation based on this LIVE-ISO which then got dist-upgraded. 
On both installations I can configure and then print either using
OKI-B432_010E46_USB (which seams to be the driverless IPP printer) or
OKI_DATA_CORP_B432 (which seams to be the printer configured using the
vendor PPD file). No problem whatsoever (allthough avahi-utils not
installed here).


(B)
The problem occured in my years old comprehensive installation which I
use daily. Here the printer used to work
initially (printer bought 2017) until it stopped working about a year
ago.
Now, with Brians help, we could narrow down the problem to ipp-usb
not working correctly. On this installation, removing ipp-usb makes
the printer visible and configurable using the vendor PPD file in the
cups administration. (BTW, avahi-utils installed here).

So my overall conclusion is the following:
(A) indicates, there is no HW failure and ipp-usb works fine and
reliably with this printer.

(B) There is a flaw somewhere within this installation which *affects*
ipp-usb without ipp-usb neccessarily being the cause.

So if we still dig deeper into this it boils down to searching for
whatever flaw prevents ipp-usb to work correctly *on this installation
(B)*. 
I therefor reinstalled ipp-usb here (B).




> On 15/02/2021 14:27, mh wrote:
> > I then investigated the LIVE-ISO. To my surprise ipp-usb is
> > installed within the LIVE-ISO.   
> 
> ipp-usb is part of the standard installation in Debian and Ubuntu, to 
> support printers which do driverless IPP printing.
> Standard-conforming printers should work out-of-the-box with that.
> 
> > All the commands which failed/did have an empty
> > output on my default system work here with the expected output (I
> > guess), except for # avahi-browse -rt _ipp._tcp due to avahi-browse
> > not being installed:
> > 
> > # /usr/lib/cups/backend/usb
> > DEBUG: Loading USB quirks from "/usr/share/cups/usb".
> > DEBUG: Loaded 98 quirks.
> > DEBUG: list_devices
> > DEBUG: libusb_get_device_list=9
> > DEBUG: Failed to detach "usblp" module from 06bc:0357
> >   
> 
> The "usb" backend probably simply encounters your printer's USB
> occupied by some process here, not knowing that it is actually
> ipp-usb and not the "usblp" kernel module. The method for getting rid
> of the kernel module seems no to remove the connection of ipp-usb.
> 
> > # systemctl list-units "ipp-usb*" | grep service
> >ipp-usb.service loaded active running Daemon for IPP over USB
> > printer support
> > 
> > # lpstat -t
> > Zeitplandienst läuft
> > Keine systemvoreingestellten Ziele
> > Gerät für OKI_DATA_CORP_B432:
> > ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/
> > OKI_DATA_CORP_B432 akzeptiert Anfragen seit Mo 15 Feb 2021 12:45:49
> > CET Drucker OKI_DATA_CORP_B432 ist im Leerlauf.  Aktiviert seit Mo
> > 15 Feb 2021 12:45:49 CET
> > 
> > # lpstat -l -e
> > OKI_B432_010E46_USB_ network none
> > ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/
> > OKI_DATA_CORP_B432 permanent
> > ipp://localhost/printers/OKI_DATA_CORP_B432
> > ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/
> >   
> 
> This looks like that a driverless print queue got created
> automatically. Could you run these two commands:
> 
> lp -d OKI_B432_010E46_USB_ ~/.bashrc
> lp -d OKI_DATA_CORP_B432 ~/.bashrc
> 
> Do you get something printed? If yes, by the first command? By the 
> second? Both?
> 
> > # avahi-browse -rt _ipp._tcp
> > Command 'avahi-browse' not found, but can be installed with:
> > apt install avahi-utils
> >   
> 
> Install this command by actually doing
> 
> sudo apt install avahi-utils
> 
> Then run the command again and post the output here.
> 
> > 
> > @ till.kamppeter
> > As much as I'm willing to help, from what I can tell now I assume
> > there is not much to debug *direktly* related to the printer. Tell
> > me if you think otherwise.
> >  
> 
> If the printer is capable of driverless printing via an
> auto-generated all is OK. But if it is not capable of that but
> pretends to be capable then somewhere is a bug, in our software or in
> the printer, in the latter case we caould perhaps work around in our
> software.
> 

I am not sure whether it's worth to investigate the (A) situation, as
there all is working fine. But as you think 
DEBUG: Fail

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Mon, 15 Feb 2021 10:26:52 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 20:31:28 +0100, mh wrote:
> 
> [...]
> 
> > # ippfind -T 5
> > ~#   
> 
> An IPP printer is not found. This would fit the observation that
> cups-browsed has not set up a print queue. I have come to the
> conclusion that the B432 does not implement IPP-over-USB correctly.

First: Thanks for your help and for all your efforts. But further
investigation and tests based on the new knowledge provided by you lets
me come to a different conclusion (see below). I didn't know about
ipp-usb, how it works and what it does and it automagically being
configured. 

> 
> A queue set up with a vendor PPD will not function while ipp-usb is
> active, so purge it and proceed as you did with the Live ISO. Also
> see #982190:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982190
> 
> Cheers,
> 
> Brian.

Purging ipp-usb instantly made the cups webinterface showing my
printer. So I could configure it using the vendor PPD file. Printing
menue (Libreoffice) shows one OKI printer. Print succeeded.
Thanks. 
So the main issue is solved as I can print from within my
default system. From what I've seen during configuration and printing,
the printer setup seems stabel, the printer showed up immediately, the
print job is carried out without much delay.

I then reinstalled ipp-usb which again prevented the cups webinterface
from seeing the printer. So clearly something around ipp-usb is broken.
I purged ipp-usb again and all is well.

I then investigated the LIVE-ISO. To my surprise ipp-usb is installed
within the LIVE-ISO. All the commands which failed/did have an empty
output on my default system work here with the expected output (I
guess), except for # avahi-browse -rt _ipp._tcp due to avahi-browse not
being installed:

# /usr/lib/cups/backend/usb
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 98 quirks.
DEBUG: list_devices
DEBUG: libusb_get_device_list=9
DEBUG: Failed to detach "usblp" module from 06bc:0357

# systemctl list-units "ipp-usb*" | grep service
  ipp-usb.service loaded active running Daemon for IPP over USB printer
support

# lpstat -t
Zeitplandienst läuft
Keine systemvoreingestellten Ziele
Gerät für OKI_DATA_CORP_B432:
ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/
OKI_DATA_CORP_B432 akzeptiert Anfragen seit Mo 15 Feb 2021 12:45:49 CET
Drucker OKI_DATA_CORP_B432 ist im Leerlauf.  Aktiviert seit Mo 15 Feb
2021 12:45:49 CET

# lpstat -l -e
OKI_B432_010E46_USB_ network none
ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/
OKI_DATA_CORP_B432 permanent
ipp://localhost/printers/OKI_DATA_CORP_B432
ipp://OKI-B432-010E46%20(USB)._ipp._tcp.local/

# avahi-browse -rt _ipp._tcp
Command 'avahi-browse' not found, but can be installed with:
apt install avahi-utils

I then tested my secound installation (the one based on the Live-ISO)
where I yesterday couldn't configure reliably my printer. I now realized
the printer can be configured here, too. I *suspect* this may have
happend because the printer wasn't switched off long enough or not at
all between unsuccessfull attempts and thus remaind in an undefined
state which then prevented a successfull configuration? Whether or not
the browser cache (which I emptied before every new attempt) played a
role, too ... I dont't know. Anyway, It now works here, too.


So it's my default system where the ipp-usb <-> printer communication
remains broken for whatever reason. This is a some years old and
comprehensive installation where this printer used to work until about a
year ago. Something subtle must have gone broken over time ... but I
can live with the printer not using ipp-usb as PPD is what I've allways
used.


@ till.kamppeter
As much as I'm willing to help, from what I can tell now I assume there
is not much to debug *direktly* related to the printer. Tell me if you
think otherwise.


BTW (not related the this malfunction):
There are already some OKI PPD files available in the cups config,
including the PPD file for the preceding model. Could I do anything to
help to include the appropriate vendor PPD file
for my printer (freely availabe on their webite) in the
printer-driver-oki package (or whichever package is the rightone)? 


Thanks

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 19:04:48 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 18:47:18 +0100, mh wrote:
> 
> > Am Sun, 14 Feb 2021 17:35:47 +
> > schrieb Brian Potkin :
> >   
> > > Is avahi-daemon active?
> > > 
> > >   systemctl status avahi-daemon  
> > 
> > Yes.
> > 
> > # systemctl status avahi-daemon
> > ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
> >  Loaded: loaded (/lib/systemd/system/avahi-daemon.service;
> > enabled; vendor preset: enabled) Active: active (running) since Sun
> > 2021-02-14 14:01:53 CET; 4h 38min ago TriggeredBy: ●
> > avahi-daemon.socket Main PID: 711 (avahi-daemon)
> >  Status: "avahi-daemon 0.8 starting up."
> >   Tasks: 2 (limit: 4634)
> >  Memory: 1.7M
> > CPU: 402ms
> >  CGroup: /system.slice/avahi-daemon.service
> >  ├─711 avahi-daemon: running [neutower.local]
> >  └─749 avahi-daemon: chroot helper
> > 
> > Feb 14 14:01:51 neutower avahi-daemon[711]: Found user 'avahi' (UID
> > 106) and group 'avahi' (GID 114). Feb 14 14:01:51 neutower
> > avahi-daemon[711]: Successfully dropped root privileges. Feb 14
> > 14:01:51 neutower avahi-daemon[711]: avahi-daemon 0.8 starting up.
> > Feb 14 14:01:53 neutower avahi-daemon[711]: Successfully called
> > chroot(). Feb 14 14:01:53 neutower avahi-daemon[711]: Successfully
> > dropped remaining capabilities. Feb 14 14:01:53 neutower
> > avahi-daemon[711]: Loading service file
> > /services/apt-cacher-ng.service. Feb 14 14:01:53 neutower
> > avahi-daemon[711]: Network interface enumeration completed. Feb 14
> > 14:01:53 neutower avahi-daemon[711]: Server startup complete. Host
> > name is neutower.local. Local service cookie is 294> Feb 14
> > 14:01:53 neutower avahi-daemon[711]: Service "apt-cacher-ng proxy
> > on neutower" (/services/apt-cacher-ng.service) succe> Feb 14
> > 14:01:53 neutower systemd[1]: Started Avahi mDNS/DNS-SD Stack.
> > lines 1-23/23 (END)
> > 
> >   
> > > 
> > > Do you have a firewall?  
> > 
> > No.  
> 
> I am running out of ideas. Please try
> 
>   lpinfo -v

# lpinfo -v
file cups-brf:/
network beh
serial serial:/dev/ttyS0?baud=115200
network ipp
network https
network socket
network ipps
network lpd
network http
network smb

> 
> and
> 
>   ippfind -T 5

# ippfind -T 5
~# 

> 
> Cheers,
> 
> Brian.

Greetings

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 17:35:47 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 17:44:20 +0100, mh wrote:
> 
> > Am Sun, 14 Feb 2021 15:39:51 +
> > schrieb Brian Potkin :
> >   
> > > The whole point is that the printer installion is done via
> > > ipp-usb, which you have shown is active on your machine. There is
> > > no need for you to select a PPD or a vendor driver.  
> > 
> > If I could have all features my printer offers available this way,
> > then yes. OTOH the whole problem does not seam to be the protocol
> > used, but cups administration not seeing the printer. 
> > 
> > Is there a way to completly resett systemd/udev/avahi/whatever?
> > Month ago I tried "apt install --reinstall systemd udev" as an
> > attempt to exclude any malfunction.  
> 
> Is avahi-daemon active?
> 
>   systemctl status avahi-daemon

Yes.

# systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
 Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled;
vendor preset: enabled) Active: active (running) since Sun 2021-02-14
14:01:53 CET; 4h 38min ago TriggeredBy: ● avahi-daemon.socket
   Main PID: 711 (avahi-daemon)
 Status: "avahi-daemon 0.8 starting up."
  Tasks: 2 (limit: 4634)
 Memory: 1.7M
CPU: 402ms
 CGroup: /system.slice/avahi-daemon.service
 ├─711 avahi-daemon: running [neutower.local]
 └─749 avahi-daemon: chroot helper

Feb 14 14:01:51 neutower avahi-daemon[711]: Found user 'avahi' (UID
106) and group 'avahi' (GID 114). Feb 14 14:01:51 neutower
avahi-daemon[711]: Successfully dropped root privileges. Feb 14
14:01:51 neutower avahi-daemon[711]: avahi-daemon 0.8 starting up. Feb
14 14:01:53 neutower avahi-daemon[711]: Successfully called chroot().
Feb 14 14:01:53 neutower avahi-daemon[711]: Successfully dropped
remaining capabilities. Feb 14 14:01:53 neutower avahi-daemon[711]:
Loading service file /services/apt-cacher-ng.service. Feb 14 14:01:53
neutower avahi-daemon[711]: Network interface enumeration completed.
Feb 14 14:01:53 neutower avahi-daemon[711]: Server startup complete.
Host name is neutower.local. Local service cookie is 294> Feb 14
14:01:53 neutower avahi-daemon[711]: Service "apt-cacher-ng proxy on
neutower" (/services/apt-cacher-ng.service) succe> Feb 14 14:01:53
neutower systemd[1]: Started Avahi mDNS/DNS-SD Stack. lines 1-23/23
(END)


> 
> Do you have a firewall?

No.

> 
> Regards,
> 
> Brian.

Greetings

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 15:39:51 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 16:17:34 +0100, mh wrote:
> 
> > Am Sun, 14 Feb 2021 14:35:53 +
> > schrieb Brian Potkin :
> >   
> > > On Sun 14 Feb 2021 at 14:47:42 +0100, mh wrote:
> > >   
> 
> [...]
> 
> > > > # systemctl start ipp-usb
> > > > ~#
> > > > 
> > > > # systemctl status ipp-usb
> > > > ● ipp-usb.service - Daemon for IPP over USB printer support
> > > >  Loaded: loaded (/lib/systemd/system/ipp-usb.service;
> > > > static) Active: active (running) since Sun 2021-02-14 14:01:53
> > > > CET; 32min ago Docs: man:ipp-usb(8)
> > > >Main PID: 854 (ipp-usb)
> > > >   Tasks: 10 (limit: 4634)
> > > >  Memory: 7.9M
> > > > CPU: 52ms
> > > >  CGroup: /system.slice/ipp-usb.service
> > > >  └─854 /sbin/ipp-usb udev
> > > > 
> > > > Feb 14 14:01:53 neutower systemd[1]: Started Daemon for IPP
> > > > over USB printer support
> > > 
> > > That's exactly what should happen. cups-browsed should now
> > > install a queue. Anything from 'lpstat -t' now?   
> > 
> > Nothing
> >   
> > > How about 'lpstat -l -e' and  
> > 
> > Nothing
> >   
> > > 'avahi-browse -rt _ipp._tcp'?  
> > 
> > Nothing  
> 
> Inexplicable, especially not getting any outputs from the last two
> commands. I hope you did not type the apostrophes ('   ').

I did not ;-)

> 
> > But to be clear: Currently there is *no printer installed* here in
> > this system. It has been, but as I could not print I purged cups*
> > entierly and than reinstalled it as described in my initial report.
> > And now in the cups admin webpanel no Oki or USB printer is visible
> > to select a PPD file for (whereas it works fine and reliably in a
> > live ISO system).  
> 
> The whole point is that the printer installion is done via ipp-usb,
> which you have shown is active on your machine. There is no need for
> you to select a PPD or a vendor driver.

If I could have all features my printer offers available this way, then
yes. OTOH the whole problem does not seam to be the protocol used,
but cups administration not seeing the printer. 

Is there a way to completly resett systemd/udev/avahi/whatever? Month
ago I tried "apt install --reinstall systemd udev" as an attempt to
exclude any malfunction.

thanks


Michael 

> 
> Regards,
> 
> Brian.

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 14:35:53 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 14:47:42 +0100, mh wrote:
> 
> > Am Sun, 14 Feb 2021 13:06:09 +
> > schrieb Brian Potkin :
> >   
> > > On Sun 14 Feb 2021 at 12:56:11 +0100, mh wrote:
> > >   
> > > > Am Sun, 14 Feb 2021 11:21:45 +
> > > > schrieb Brian Potkin :
> > > > 
> > > > > Michael, don't forget to mail the bug; I sent the last one
> > > > > there for you.
> > > > 
> > > > Thanks. I wondered whether I should respond to your mail
> > > > address. Now I did CC 982...@bugs.debian.org if that's what you
> > > > suggested.
> > > 
> > > That's better. Thanks.
> > >
> > > > > 
> > > > > "bInterfaceProtocol  4" indicates that the printer
> > > > > understands IPP=over-USB. Now give
> > > > > 
> > > > >   systemctl list-units "ipp-usb*" | grep service
> > > > 
> > > > # systemctl list-units "ipp-usb*" | grep service
> > > > ~#
> > > 
> > > An empty output is unexpected. What happens with
> > > 
> > >   systemctl start ipp-usb
> > > 
> > > and
> > > 
> > >   systemctl status ipp-usb
> > > 
> > > with the printer connected   
> > 
> > # systemctl start ipp-usb
> > ~#
> > 
> > # systemctl status ipp-usb
> > ● ipp-usb.service - Daemon for IPP over USB printer support
> >  Loaded: loaded (/lib/systemd/system/ipp-usb.service; static)
> >  Active: active (running) since Sun 2021-02-14 14:01:53 CET;
> > 32min ago Docs: man:ipp-usb(8)
> >Main PID: 854 (ipp-usb)
> >   Tasks: 10 (limit: 4634)
> >  Memory: 7.9M
> > CPU: 52ms
> >  CGroup: /system.slice/ipp-usb.service
> >  └─854 /sbin/ipp-usb udev
> > 
> > Feb 14 14:01:53 neutower systemd[1]: Started Daemon for IPP over USB
> > printer support  
> 
> That's exactly what should happen. cups-browsed should now install a
> queue. Anything from 'lpstat -t' now? 

Nothing

> How about 'lpstat -l -e' and

Nothing

> 'avahi-browse -rt _ipp._tcp'?

Nothing


But to be clear: Currently there is *no printer installed* here in this
system. It has been, but as I could not print I purged cups* entierly
and than reinstalled it as described in my initial report. And now in
the cups admin webpanel no Oki or USB printer is visible to select a PPD
file for (whereas it works fine and reliably in a live ISO system).

> 
> Regards,
> 
> Brian.

Greetings

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 13:06:09 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 12:56:11 +0100, mh wrote:
> 
> > Am Sun, 14 Feb 2021 11:21:45 +
> > schrieb Brian Potkin :
> >   
> > > Michael, don't forget to mail the bug; I sent the last one there
> > > for you.  
> > 
> > Thanks. I wondered whether I should respond to your mail address.
> > Now I did CC 982...@bugs.debian.org if that's what you suggested.  
> 
> That's better. Thanks.
>  
> > > 
> > > "bInterfaceProtocol  4" indicates that the printer understands
> > > IPP=over-USB. Now give
> > > 
> > >   systemctl list-units "ipp-usb*" | grep service  
> > 
> > # systemctl list-units "ipp-usb*" | grep service
> > ~#  
> 
> An empty output is unexpected. What happens with
> 
>   systemctl start ipp-usb
> 
> and
> 
>   systemctl status ipp-usb
> 
> with the printer connected 

# systemctl start ipp-usb
~#

# systemctl status ipp-usb
● ipp-usb.service - Daemon for IPP over USB printer support
 Loaded: loaded (/lib/systemd/system/ipp-usb.service; static)
 Active: active (running) since Sun 2021-02-14 14:01:53 CET; 32min
ago Docs: man:ipp-usb(8)
   Main PID: 854 (ipp-usb)
  Tasks: 10 (limit: 4634)
 Memory: 7.9M
CPU: 52ms
 CGroup: /system.slice/ipp-usb.service
 └─854 /sbin/ipp-usb udev

Feb 14 14:01:53 neutower systemd[1]: Started Daemon for IPP over USB
printer support.


> and disconnected?

(printer switched off)

~# systemctl status ipp-usb
● ipp-usb.service - Daemon for IPP over USB printer support
 Loaded: loaded (/lib/systemd/system/ipp-usb.service; static)
 Active: inactive (dead)
   Docs: man:ipp-usb(8)

Feb 14 14:01:53 neutower systemd[1]: Started Daemon for IPP over USB
printer support. Feb 14 14:37:24 neutower systemd[1]: ipp-usb.service:
Succeeded. Feb 14 14:38:18 neutower systemd[1]: Started Daemon for IPP
over USB printer support. Feb 14 14:38:18 neutower systemd[1]:
ipp-usb.service: Succeeded.


> 
> > > 
> > > and
> > > 
> > >   lpstat -t  
> > 
> > # lpstat -t
> > Zeitplandienst läuft
> > Keine systemvoreingestellten Ziele
> > lpstat: Keine Druckziele hinzugefügt.
> > lpstat: Keine Druckziele hinzugefügt.
> > lpstat: Keine Druckziele hinzugefügt.
> > lpstat: Keine Druckziele hinzugefügt.
> > 
> > Meaning:
> > time table service running
> > No preconfigured system targets
> > lpstat: No printing targets added.  
>  
> This is the expected output if ipp-usb is not active.
>  
> > BTW: I had IPP-USB configured once, but for that to happen I had to
> > connect the printer using a LAN cable. And I could not print either.
> > But there may have been other misconfigurations be involved, too,
> > as I didn't really understand how to configure a LAN connection for
> > the printer.   
> 
> IPP-over-USB is for a USB connection only. See sections 13, 14 and 15
> at
> 
>   https://wiki.debian.org/CUPSDriverlessPrinting

Thanks for the info.

> 
> 
> > *As a layman* I am guessing whether this USB mess happens due to
> > timing issues (live ISO is runing in RAM, so runs very responsive).
> > Shouldn't any solution involve solving the apparent conflict
> > between libusb and usblp?  
> 
> I am not skilled in USB matters and first wanted to discover whether
> the printing system is working as designed.

Ok, understood.

> 
> Regards,
> 
> Brian.

Greetings from Germany

Michael

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sun, 14 Feb 2021 11:21:45 +
schrieb Brian Potkin :

> On Sun 14 Feb 2021 at 01:04:57 +0100, mh wrote:
> 
> > Am Sat, 13 Feb 2021 23:30:04 +
> > schrieb Brian Potkin :
> >   
> 
> [...]
> 
> > > Thank you for your report, Michael, Let's see what we can do about
> > > this.
> > >
> > > Are you using a USB connection? If so, give what you get for
> > >  
> > 
> > Hi Brian,
> > 
> > thanks for trying to help.
> > 
> > Yes, I am using an USB connection.
> > 
> >   
> > >   lsusb -v | grep -A 3 bInterfaceClass.*7  
> > 
> > 
> >  bInterfaceClass 7 Printer
> >   bInterfaceSubClass  1 Printer
> >   bInterfaceProtocol  2 Bidirectional
> >   iInterface  4 OKI B432 Printer
> > --
> >   bInterfaceClass 7 Printer
> >   bInterfaceSubClass  1 Printer
> >   bInterfaceProtocol  4
> >   iInterface  6 OKI B432 IPP0
> > --
> >   bInterfaceClass 7 Printer
> >   bInterfaceSubClass  1 Printer
> >   bInterfaceProtocol  4
> >   iInterface  9 OKI B432 IPP1  
> 
> Michael, don't forget to mail the bug; I sent the last one there for
> you.

Thanks. I wondered whether I should respond to your mail address. Now I
did CC 982...@bugs.debian.org if that's what you suggested.

> 
> "bInterfaceProtocol  4" indicates that the printer understands
> IPP=over-USB. Now give
> 
>   systemctl list-units "ipp-usb*" | grep service

# systemctl list-units "ipp-usb*" | grep service
~#

> 
> and
> 
>   lpstat -t

# lpstat -t
Zeitplandienst läuft
Keine systemvoreingestellten Ziele
lpstat: Keine Druckziele hinzugefügt.
lpstat: Keine Druckziele hinzugefügt.
lpstat: Keine Druckziele hinzugefügt.
lpstat: Keine Druckziele hinzugefügt.

Meaning:
time table service running
No preconfigured system targets
lpstat: No printing targets added.


BTW: I had IPP-USB configured once, but for that to happen I had to
connect the printer using a LAN cable. And I could not print either.
But there may have been other misconfigurations be involved, too, as I
didn't really understand how to configure a LAN connection for the
printer. 

*As a layman* I am guessing whether this USB mess happens due to timing
issues (live ISO is runing in RAM, so runs very responsive). Shouldn't
any solution involve solving the apparent conflict between libusb and
usblp?

Anyway, thanks so far.

Michael  



> 
> Regards,
> 
> Brian.
> > 
> >   
> > >
> > > Regards,
> > >
> > > Brian.  

Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

[mh]

Am Sat, 13 Feb 2021 23:30:04 +
schrieb Brian Potkin :

> On Sat 13 Feb 2021 at 21:23:19 +0100, Michael Hatzold wrote:
>
> > Package: cups
> > Version: 2.3.3op2-3
> > Severity: important
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> >
> >* What led up to the situation?
> >
> > I tried to install an USB printer (oki B432).
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > localhost:631/administration -> new printer
> >
> >* What was the outcome of this action?
> >
> > The printer is not listed anymore and thus I cannot select the
> > neccesary ppd- file, which used to work this way years ago
> > (2017-2019/20). It still works *reliably* on a debian/sid(uction)
> > live_ISO from 2020.07. But on my up to date installation it does
> > not work anymore:
>
> Thank you for your report, Michael, Let's see what we can do about
> this.
>
> Are you using a USB connection? If so, give what you get for
>

Hi Brian,

thanks for trying to help.

Yes, I am using an USB connection.


>   lsusb -v | grep -A 3 bInterfaceClass.*7


 bInterfaceClass 7 Printer
  bInterfaceSubClass  1 Printer
  bInterfaceProtocol  2 Bidirectional
  iInterface  4 OKI B432 Printer
--
  bInterfaceClass 7 Printer
  bInterfaceSubClass  1 Printer
  bInterfaceProtocol  4
  iInterface  6 OKI B432 IPP0
--
  bInterfaceClass 7 Printer
  bInterfaceSubClass  1 Printer
  bInterfaceProtocol  4
  iInterface  9 OKI B432 IPP1
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable



That's it.

Thanks again!

Michael










>
> Regards,
>
> Brian.

Bug#982742: this how it looks when the printer IS listed:

[mh]

# /usr/lib/cups/backend/usb
DEBUG: Loading USB quirks from "/usr/share/cups/usb". DEBUG: Loaded 181
quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=9 DEBUG2:
Printer found with device ID: MANUFACTURER:OKI DATA CORP;COMMAND
SET:PJL,PCL,IBMPPR,EPSONFX,POSTSCRIPT,PCLXL,IPDL,XPS;MODEL:B432;CLASS:PRINTER;DESCRIPTION:OKI
B432;COMPATIBLE ID:OK_N_7800; Device URI:
usb://OKI%20DATA%20CORP/B432?serial=AK76039718 direct
usb://OKI%20DATA%20CORP/B432?serial=AK76039718 "OKI DATA CORP B432"
"OKI DATA CORP B432" "MANUFACTURER:OKI DATA CORP;COMMAND
SET:PJL,PCL,IBMPPR,EPSONFX,POSTSCRIPT,PCLXL,IPDL,XPS;MODEL:B432;CLASS:PRINTER;DESCRIPTION:OKI
B432;COMPATIBLE ID:OK_N_7800;" ""



I wonder why here are 181 quirks!

Bug#968838: cdrom: Debian installer fails to detect hard drive

[MH]

Package: cdrom
Severity: important
X-Debbugs-Cc: haa...@zoho.com

Dear Maintainer,

Debian installer fails to detect SATA SSD hard drive in Samsung NC10 netbook.
It is possible to continue "without drive" to the partitioner, which
correctly detects disk and existing partitions.


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

Kernel: Linux 5.7.0-2-686 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#962528: pulseaudio: Surround sound center channel muted

[MH]

Package: pulseaudio
Version: 12.2-4+deb10u1
Severity: important

Dear Maintainer,

no sound from center channel during 5.1 audio playback using VLC or Kodi. 
Surprisingly, there is no issue with surround playback with netflix via Firefox.


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1:1.1.8-dmo1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.16-1
ii  libgcc1  1:8.3.0-6
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-9
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-4+deb10u1
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-6
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.3.0-6
ii  libsystemd0  241-7~deb10u4
ii  libtdb1  1.3.16-2+b1
ii  libudev1 241-7~deb10u4
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 10.2019051400
ii  pulseaudio-utils 12.2-4+deb10u1

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.16-1
ii  libpam-systemd 241-7~deb10u4
ii  rtkit  0.11-6

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 241-7~deb10u4

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; 

Bug#901689: libasound2: Fails to find configuration for Intel HDA soundcard

[mh]

Dear Maintainer,

I can verify this problem using libasound2 version 1.1.7-1. However, 
when I downgraded to libasound2_1.1.6-1 sound worked properly. The 
suggest fix of adding


'HDA Intel' cards.HDA-Intel

worked for me with version libasound2_1.1.7-1.

Running sid, amd64, kernel version 4.18.0-2-amd64.


Regards,

Michael Heyes

Bug#908043: plasma-desktop: Plasma-desktop loads with black screen

[MH]

Package: plasma-desktop
Version: 4:5.8.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When PC is connected to AVR via HDMI, plasma-desktop loads with a black screen. 
Apparently, it queries the EDID of the connected TV, which is 4k. Previously,
SDDM did the same thing. The AVR is limited to 1920x1080 input. Creating an 
xorg.conf file using NVidia Settings solve the issue for SDDM, but that file
seems to be ignored by plasma-desktop. The desktop still responds to keyboard
input, but is otherwise unusable. This situation also exists under Buster.

IMO the problem is not with the AVR, which needs to passthrough EDID so
monitors with lesser resolutions are correctly detected. Plasma-desktop
should not requery for EDID but should accept the same settings as SDDM.
Or maybe this is an issue with Xserver?

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.8.5-2
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-2
ii  kded55.28.0-1
ii  kio  5.28.0-2
ii  libc62.24-11+deb9u3
ii  libcanberra0 0.30-3
ii  libfontconfig1   2.11.0-6.7+b1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libkf5activities55.28.0-1
ii  libkf5activitiesstats1   5.28.0-1
ii  libkf5archive5   5.28.0-2
ii  libkf5auth5  5.28.0-2
ii  libkf5baloo5 5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5codecs55.28.0-1+b2
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5dbusaddons55.28.0-1
ii  libkf5emoticons-bin  5.28.0-1
ii  libkf5emoticons5 5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5itemmodels55.28.0-2
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-2
ii  libkf5kcmutils5  5.28.0-2
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5people55.28.0-1
ii  libkf5peoplewidgets5 5.28.0-1
ii  libkf5plasma55.28.0-2
ii  libkf5plasmaquick5   5.28.0-2
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5solid5 5.28.0-3
ii  libkf5sonnetui5  5.28.0-2
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5widgetsaddons5 5.28.0-3
ii  libkf5windowsystem5  5.28.0-2
ii  libkf5xmlgui55.28.0-1
ii  libkfontinst54:5.8.6-1
ii  libkfontinstui5  4:5.8.6-1
ii  libkworkspace5-5 4:5.8.6-2.1+deb9u1
ii  libpackagekitqt5-0   0.9.6-1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libpulse-mainloop-glib0  10.0-1+deb9u1
ii  libpulse010.0-1+deb9u1
ii  libqt5concurrent55.7.1+dfsg-3+b1
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5network5   5.7.1+dfsg-3+b1
ii  libqt5printsupport5

Bug#903812: kmail: KMail fails to import from archive

[MH]

Package: kmail
Version: 4:17.12.3-1
Followup-For: Bug #903812

Dear Maintainer,

I exported an IMAP folder containing fewer than 100 messages to see how well it 
would work.
Accepting the default settings, it created an archive file with "tar.bz2" 
extension without
reporting any errors. However, when I tried to import the archive using the same
Import/Export tool I got a "Cannot read file" error message.

I CAN open and view the file using Ark, but that's of little use restoring the 
mail folder
to it's original state.

I may have reported this bug previously, but I'm not sure if I included the 
note about
Ark. 


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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kmail depends on:
ii  akonadi-server   4:17.12.3-2+b1
ii  kdepim-runtime   4:17.12.3-2
ii  kio  5.47.0-1
ii  libc62.27-5
ii  libgcc1  1:8.1.0-12
ii  libgpgmepp6  1.11.1-1
ii  libkf5akonadiagentbase5  4:17.12.3-2+b1
ii  libkf5akonadicontact54:17.12.3-2
ii  libkf5akonadicore5abi1   4:17.12.3-2+b1
ii  libkf5akonadimime5   4:17.12.3-1
ii  libkf5akonadisearch-bin  4:17.12.3-1
ii  libkf5akonadisearch-plugins  4:17.12.3-1
ii  libkf5akonadisearchdebug54:17.12.3-1
ii  libkf5akonadisearchpim5  4:17.12.3-1
ii  libkf5akonadiwidgets5abi14:17.12.3-2+b1
ii  libkf5bookmarks5 5.47.0-1
ii  libkf5calendarcore5abi1  4:17.12.3-1
ii  libkf5calendarutils5 4:17.12.3-1
ii  libkf5codecs55.47.0-1
ii  libkf5completion55.47.0-1
ii  libkf5configcore55.47.0-1
ii  libkf5configgui5 5.47.0-1
ii  libkf5configwidgets5 5.47.0-1
ii  libkf5contacts5  4:17.12.3-1
ii  libkf5coreaddons55.47.0-1
ii  libkf5crash5 5.47.0-1
ii  libkf5dbusaddons55.47.0-1
ii  libkf5followupreminder5  4:17.12.3-1
ii  libkf5grantleetheme-plugins  17.12.3-1
ii  libkf5gravatar5abi1  4:17.12.3-1
ii  libkf5guiaddons5 5.47.0-1
ii  libkf5i18n5  5.47.0-1
ii  libkf5iconthemes55.47.0-1
ii  libkf5identitymanagement517.12.3-1
ii  libkf5itemmodels55.47.0-1
ii  libkf5itemviews5 5.47.0-1
ii  libkf5jobwidgets55.47.0-1
ii  libkf5kcmutils5  5.47.0-1
ii  libkf5kiocore5   5.47.0-1
ii  libkf5kiofilewidgets55.47.0-1
ii  libkf5kiowidgets55.47.0-1
ii  libkf5kontactinterface5  17.12.3-1
ii  libkf5ksieveui5  4:17.12.3-1
ii  libkf5libkdepim-plugins  4:17.12.3-1
ii  libkf5libkdepim5 4:17.12.3-1
ii  libkf5libkdepimakonadi5  4:17.12.3-1
ii  libkf5libkleo5   4:17.12.3-2
ii  libkf5mailcommon5abi14:17.12.3-1
ii  libkf5mailtransport5 17.12.3-1
ii  libkf5mailtransportakonadi5  17.12.3-1
ii  libkf5messagecomposer5   4:17.12.3-1
ii  libkf5messagecore5   4:17.12.3-1
ii  libkf5messagelist5   4:17.12.3-1
ii  libkf5messageviewer5 4:17.12.3-1
ii  libkf5mime5abi1  17.12.3-2
ii  libkf5mimetreeparser54:17.12.3-1
ii  libkf5notifications5 5.47.0-1
ii  libkf5notifyconfig5  5.47.0-1
ii  libkf5parts5 5.47.0-1
ii  libkf5pimcommon5abi1 4:17.12.3-1
ii  libkf5pimcommonakonadi5  4:17.12.3-1
ii  libkf5pimtextedit5abi1   17.12.3-2
ii  libkf5sendlater5 4:17.12.3-1
ii  libkf5service-bin5.47.0-1
ii  libkf5service5   5.47.0-1
ii  libkf5sonnetui5  5.47.0-1
ii  libkf5templateparser54:17.12.3-1
ii  libkf5textwidgets5   5.47.0-1
ii  libkf5tnef5  4:17.12.3-1
ii  libkf5wallet-bin 5.47.0-1
ii  libkf5wallet55.47.0-1
ii  libkf5webengineviewer5   4:17.12.3-1
ii  libkf5widgetsaddons5 5.47.0-1
ii  libkf5windowsystem5  5.47.0-1
ii  libkf5xmlgui55.47.0-1
ii  libqgpgme7   1.11.1-1
ii  libqt5core5a 5.10.1+dfsg-7
ii  libqt5dbus5  5.10.1+dfsg-7
ii  libqt5gui5   5.10.1+dfsg-7
ii  libqt5network5   5.10.1+dfsg-7
ii  libqt5widgets5   5.10.1+dfsg-7
ii  libqt5xml5   5.10.1+dfsg-7
ii  libstdc++6   8.1.0-12

Versions of packages kmail recommends:
ii  accountwizard   4:17.12.3-1
ii  gnupg   2.2.9-1
ii  kdepim-addons   17.12.3-2
ii  kdepim-themeeditors 4:17.12.3-1
ii  mbox-importer   4:17.12.3-1
ii  pim-data-exporter   4:17.12.3-1
ii  pim-sieve-editor

Bug#903812: kmail: KMail fails to import from archive

[MH]

Package: kmail
Version: 4:17.12.3-1
Severity: important

Dear Maintainer,

After archiving an IMAP mail folder, I was unable to restore (import) it.
The PIM Setting Explorer states:  "unable to open the (archived) file.
When I exported to archive, I accepted default settings (tar.bz2). This
bug should be tagged as "grave" but I do not have that option. 


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmail depends on:
ii  akonadi-server   4:17.12.3-2+b1
ii  kdepim-runtime   4:17.12.3-2
ii  kio  5.47.0-1
ii  libc62.27-3
ii  libgcc1  1:8.1.0-9
ii  libgpgmepp6  1.11.1-1
ii  libkf5akonadiagentbase5  4:17.12.3-2+b1
ii  libkf5akonadicontact54:17.12.3-2
ii  libkf5akonadicore5abi1   4:17.12.3-2+b1
ii  libkf5akonadimime5   4:17.12.3-1
ii  libkf5akonadisearch-bin  4:17.12.3-1
ii  libkf5akonadisearch-plugins  4:17.12.3-1
ii  libkf5akonadisearchdebug54:17.12.3-1
ii  libkf5akonadisearchpim5  4:17.12.3-1
ii  libkf5akonadiwidgets5abi14:17.12.3-2+b1
ii  libkf5bookmarks5 5.47.0-1
ii  libkf5calendarcore5abi1  4:17.12.3-1
ii  libkf5calendarutils5 4:17.12.3-1
ii  libkf5codecs55.47.0-1
ii  libkf5completion55.47.0-1
ii  libkf5configcore55.47.0-1
ii  libkf5configgui5 5.47.0-1
ii  libkf5configwidgets5 5.47.0-1
ii  libkf5contacts5  4:17.12.3-1
ii  libkf5coreaddons55.47.0-1
ii  libkf5crash5 5.47.0-1
ii  libkf5dbusaddons55.47.0-1
ii  libkf5followupreminder5  4:17.12.3-1
ii  libkf5grantleetheme-plugins  17.12.3-1
ii  libkf5gravatar5abi1  4:17.12.3-1
ii  libkf5guiaddons5 5.47.0-1
ii  libkf5i18n5  5.47.0-1
ii  libkf5iconthemes55.47.0-1
ii  libkf5identitymanagement517.12.3-1
ii  libkf5itemmodels55.47.0-1
ii  libkf5itemviews5 5.47.0-1
ii  libkf5jobwidgets55.47.0-1
ii  libkf5kcmutils5  5.47.0-1
ii  libkf5kiocore5   5.47.0-1
ii  libkf5kiofilewidgets55.47.0-1
ii  libkf5kiowidgets55.47.0-1
ii  libkf5kontactinterface5  17.12.3-1
ii  libkf5ksieveui5  4:17.12.3-1
ii  libkf5libkdepim-plugins  4:17.12.3-1
ii  libkf5libkdepim5 4:17.12.3-1
ii  libkf5libkdepimakonadi5  4:17.12.3-1
ii  libkf5libkleo5   4:17.12.3-2
ii  libkf5mailcommon5abi14:17.12.3-1
ii  libkf5mailtransport5 17.12.3-1
ii  libkf5mailtransportakonadi5  17.12.3-1
ii  libkf5messagecomposer5   4:17.12.3-1
ii  libkf5messagecore5   4:17.12.3-1
ii  libkf5messagelist5   4:17.12.3-1
ii  libkf5messageviewer5 4:17.12.3-1
ii  libkf5mime5abi1  17.12.3-2
ii  libkf5mimetreeparser54:17.12.3-1
ii  libkf5notifications5 5.47.0-1
ii  libkf5notifyconfig5  5.47.0-1
ii  libkf5parts5 5.47.0-1
ii  libkf5pimcommon5abi1 4:17.12.3-1
ii  libkf5pimcommonakonadi5  4:17.12.3-1
ii  libkf5pimtextedit5abi1   17.12.3-2
ii  libkf5sendlater5 4:17.12.3-1
ii  libkf5service-bin5.47.0-1
ii  libkf5service5   5.47.0-1
ii  libkf5sonnetui5  5.47.0-1
ii  libkf5templateparser54:17.12.3-1
ii  libkf5textwidgets5   5.47.0-1
ii  libkf5tnef5  4:17.12.3-1
ii  libkf5wallet-bin 5.47.0-1
ii  libkf5wallet55.47.0-1
ii  libkf5webengineviewer5   4:17.12.3-1
ii  libkf5widgetsaddons5 5.47.0-1
ii  libkf5windowsystem5  5.47.0-1
ii  libkf5xmlgui55.47.0-1
ii  libqgpgme7   1.11.1-1
ii  libqt5core5a 5.10.1+dfsg-7
ii  libqt5dbus5  5.10.1+dfsg-7
ii  libqt5gui5   5.10.1+dfsg-7
ii  libqt5network5   5.10.1+dfsg-7
ii  libqt5widgets5   5.10.1+dfsg-7
ii  libqt5xml5   5.10.1+dfsg-7
ii  libstdc++6   8.1.0-9

Versions of packages kmail recommends:
ii  accountwizard   4:17.12.3-1
ii  gnupg   2.2.8-3
ii  kdepim-addons   17.12.3-2
ii  kdepim-themeeditors 4:17.12.3-1
ii  mbox-importer   4:17.12.3-1
ii  pim-data-exporter   4:17.12.3-1
ii  pim-sieve-editor4:17.12.3-1
ii  pinentry-qt [pinentry-x11]  1.1.0-1+b1

Versions of packages kmail suggests:
pn  clamav 
ii  kaddressbook   4:17.12.3-1
ii  kleopatra 

Bug#903541: nvidia-driver: Nvidia-driver 390-67 displays SDDM black screen

[MH]

Package: nvidia-driver
Version: 390.67-2
Severity: normal

Dear Maintainer,

Recent upgrade causes system to boot to a black screen. I can login (sddm)
and the KDE desktop loads normally. This is identical to a bug I reported
with an earlier version of the driver. That bug was subsequently resolved
in an updated driver. It has now reappeared in this newer version.

Interestingly, it only affects my HTPC with a 4k monitor. It does not
affect my desktop PC with a standard HD monitor.


-- Package-specific info:
uname -a:
Linux mediacenter 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 
GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.67  Fri Jun  1 04:04:27 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-24) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 
710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 
710] [1462:8c93]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jul 11 11:56 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jul 11 11:56 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jul 11 11:57 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jul 11 11:56 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jul 11 11:56 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jul 11 11:56 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jul 11 11:56 pci-:01:00.0-render -> ../renderD128
video:x:44:

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jul 11 10:50 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 Jul 11 10:50 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 Jul 11 10:50 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jul 11 10:50 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   54 Jul 11 10:50 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Jul 11 10:50 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 Jul 11 10:50 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Jul 11 10:50 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jul 11 10:50 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jul 11 10:50 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jul 11 10:50 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jul 11 10:50 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jul 11 10:50 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jul 11 10:50 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   23 Jul 11 10:49 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root   59 Jul 11 10:49 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   62 Jul 11 10:49 
/etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2
lrwxrwxrwx 1 root root   62 Jul 11 10:49 
/etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2
lrwxrwxrwx 1 root root   61 Jul 11 10:49 
/etc/alternatives/nvidia--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_indirect.so.0
lrwxrwxrwx 1 root root   61 Jul 11 10:49 
/etc/alternatives/nvidia--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_indirect.so.0
lrwxrwxrwx 1 root root   59 Jul 11 10:49 

Bug#902744: plasma-workspace: Applications won't stay pinned to their Activity

[MH]

Package: plasma-workspace
Version: 4:5.12.5-1
Severity: important

Dear Maintainer,

Applications will not stay "pinned" or "locked" to their assigned Activity. 
I've tried using 
window placement rules by right-clicking on the window title bar and choosing 
the 
appropriate Activity. I've tried to set application placement under Advanced 
window settings
using both "Remember" and "Force" options--nothing works. After logging out and 
logging
back in, various applications (all native KDE apps) will show up on in ALL 
Activities. This
does not happen every time. Sometimes it will be days before it happens, 
sometimes after
two or three logouts during a single day. This has been happening across 
several versions
of plasma-workspace. The problem pretty much makes using Actitities pointless. 
Given the
severity of it, I thought it would eventually be fixed. It hasn't.

The problem is repeatable. I tried cleaning out old config files. I even 
created a new 
user. Same problem. I tried going back to Virtual Desktops, but it happens 
there as well.


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.12.8-3
ii  drkonqi  5.12.5-1
ii  frameworkintegration 5.46.0-1
ii  gdb-minimal [gdb]7.12-6+b2
ii  iso-codes3.79-1
ii  kactivitymanagerd5.12.5-1
ii  kde-cli-tools4:5.12.5-1
ii  kded55.46.0-1
ii  kinit5.46.0-1
ii  kio  5.46.0-1
ii  kpackagetool55.46.0-1
ii  kwin-common  4:5.12.5-1
ii  libappstreamqt2  0.12.1-1
ii  libc62.27-3
ii  libcln6  1.3.4-4
ii  libcolorcorrect5 4:5.12.5-1
ii  libgcc1  1:8.1.0-8
ii  libgps23 3.17-5+b1
ii  libice6  2:1.0.9-2
ii  libkf5activities55.46.0-1
ii  libkf5auth5  5.46.0-1
ii  libkf5baloo5 5.46.0-1
ii  libkf5bookmarks5 5.46.0-1
ii  libkf5calendarevents55.46.0-1
ii  libkf5completion55.46.0-1
ii  libkf5config-bin 5.46.0-1
ii  libkf5configcore55.46.0-1
ii  libkf5configgui5 5.46.0-1
ii  libkf5configwidgets5 5.46.0-1
ii  libkf5coreaddons55.46.0-1
ii  libkf5crash5 5.46.0-1
ii  libkf5dbusaddons55.46.0-1
ii  libkf5declarative5   5.46.0-1
ii  libkf5globalaccel-bin5.46.0-1
ii  libkf5globalaccel5   5.46.0-1
ii  libkf5guiaddons5 5.46.0-1
ii  libkf5holidays5  1:5.47.0-1
ii  libkf5i18n5  5.46.0-1
ii  libkf5iconthemes55.46.0-1
ii  libkf5idletime5  5.46.0-1
ii  libkf5itemviews5 5.46.0-1
ii  libkf5jobwidgets55.46.0-1
ii  libkf5js55.46.0-1
ii  libkf5jsembed5   5.46.0-1
ii  libkf5kdelibs4support5   5.46.0-1
ii  libkf5kiocore5   5.46.0-1
ii  libkf5kiofilewidgets55.46.0-1
ii  libkf5kiogui55.46.0-1
ii  libkf5kiowidgets55.46.0-1
ii  libkf5networkmanagerqt6  5.47.0-1
ii  libkf5newstuff5  5.46.0-1
ii  libkf5notifications5 5.46.0-1
ii  libkf5notifyconfig5  5.46.0-1
ii  libkf5package5   5.46.0-1
ii  libkf5plasma55.46.0-1
ii  libkf5plasmaquick5   5.46.0-1
ii  libkf5prison55.47.0-1
ii  libkf5quickaddons5   5.46.0-1
ii  libkf5runner55.46.0-1
ii  libkf5service-bin5.46.0-1
ii  libkf5service5   5.46.0-1
ii  libkf5solid5 5.46.0-1
ii  libkf5texteditor55.46.0-1
ii  libkf5textwidgets5   5.46.0-1
ii  libkf5wallet-bin 5.46.0-3
ii  

Bug#900280: plasma-desktop: Applications load in wrong/all activities

[MH]

Package: plasma-desktop
Version: 4:5.12.5-1
Severity: normal

Dear Maintainer,

Applications (ksysguard, korganizer, kdiskfree, etc.) randomly reassign 
themselves to 
all/other activities to which they were originally assigned after logout and 
login.

This does not occur every time I logout, but it does occur frequently. I am 
unable
to detect any pattern in this behavior, but it has been present since at least
plasma 5.10. I have the same problem on multiple computers.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.12.5-1
ii  kactivitymanagerd5.12.5-1
ii  kde-cli-tools4:5.12.5-1
ii  kded55.45.0-1
ii  kio  5.45.0-1
ii  kpackagetool55.45.0-1
ii  libappstreamqt2  0.12.0-3
ii  libc62.27-3
ii  libcanberra0 0.30-6
ii  libfontconfig1   2.13.0-5
ii  libgcc1  1:8.1.0-3
ii  libkf5activities55.45.0-1
ii  libkf5activitiesstats1   5.45.0-1
ii  libkf5archive5   5.45.0-1
ii  libkf5auth5  5.45.0-1
ii  libkf5baloo5 5.45.0-1
ii  libkf5codecs55.45.0-1
ii  libkf5completion55.45.0-1
ii  libkf5configcore55.45.0-1
ii  libkf5configgui5 5.45.0-1
ii  libkf5configwidgets5 5.45.0-1
ii  libkf5coreaddons55.45.0-1
ii  libkf5dbusaddons55.45.0-1
ii  libkf5declarative5   5.45.0-1
ii  libkf5emoticons-bin  5.45.0-1
ii  libkf5emoticons5 5.45.0-1
ii  libkf5globalaccel5   5.45.0-1
ii  libkf5guiaddons5 5.45.0-1
ii  libkf5i18n5  5.45.0-1
ii  libkf5iconthemes55.45.0-1
ii  libkf5itemmodels55.45.0-1
ii  libkf5itemviews5 5.45.0-1
ii  libkf5jobwidgets55.45.0-1
ii  libkf5kcmutils5  5.45.0-1
ii  libkf5kdelibs4support5   5.45.0-1
ii  libkf5kiocore5   5.45.0-1
ii  libkf5kiofilewidgets55.45.0-1
ii  libkf5kiowidgets55.45.0-1
ii  libkf5newstuff5  5.45.0-1
ii  libkf5notifications5 5.45.0-2
ii  libkf5notifyconfig5  5.45.0-2
ii  libkf5package5   5.45.0-1
ii  libkf5parts5 5.45.0-1
ii  libkf5people55.45.0-1
ii  libkf5peoplewidgets5 5.45.0-1
ii  libkf5plasma55.45.0-1
ii  libkf5plasmaquick5   5.45.0-1
ii  libkf5quickaddons5   5.45.0-1
ii  libkf5runner55.45.0-1
ii  libkf5service-bin5.45.0-1
ii  libkf5service5   5.45.0-1
ii  libkf5solid5 5.45.0-1
ii  libkf5sonnetui5  5.45.0-1
ii  libkf5wallet-bin 5.45.0-1
ii  libkf5wallet55.45.0-1
ii  libkf5widgetsaddons5 5.45.0-1
ii  libkf5windowsystem5  5.45.0-1
ii  libkf5xmlgui55.45.0-1
ii  libkfontinst54:5.12.5-1
ii  libkfontinstui5  4:5.12.5-1
ii  libkworkspace5-5 4:5.12.5-1
ii  libphonon4qt5-4  4:4.10.1-1
ii  libpulse-mainloop-glib0  11.1-5
ii  libpulse011.1-5
ii  libqt5concurrent55.10.1+dfsg-7
ii  libqt5core5a 5.10.1+dfsg-7
ii  libqt5dbus5  5.10.1+dfsg-7
ii  libqt5gui5   5.10.1+dfsg-7
ii  libqt5network5   5.10.1+dfsg-7
ii  libqt5printsupport5  5.10.1+dfsg-7
ii  libqt5qml5   5.10.1-4
ii  libqt5quick5 5.10.1-4
ii  libqt5quickwidgets5  5.10.1-4
ii  libqt5sql5   5.10.1+dfsg-7
ii  libqt5svg5 

Bug#743824: digikam: Digikam no longer displays any album thumbnails

[MH]

Package: digikam
Version: 4:5.6.0-4+b2
Followup-For: Bug #743824

Dear Maintainer,

Digikam v. 5.6.0 in Debian Buster (Build date: Dec 21 2017 (target: Debian)) no 
longer displays
thumbnails under any of the albums in my collection. As far as I can tell, 
there has been no
recent update of digikam and it has been functioning normally.

I tried deleting the databases, rebuilding thumbnails, purging digikam and 
reinstalling.
Problem remains. No error messages displayed at any time.

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages digikam depends on:
ii  digikam-data  4:5.6.0-4
ii  digikam-private-libs  4:5.6.0-4+b2
ii  kipi-plugins  4:5.6.0-4+b2
ii  libc6 2.27-3
ii  libgcc1   1:8-20180402-1
ii  libkf5configcore5 5.44.0-1
ii  libkf5coreaddons5 5.44.0-1
ii  libkf5filemetadata3   5.44.0-1
ii  libkf5i18n5   5.44.0-1
ii  libqt5core5a  5.10.1+dfsg-5
ii  libqt5gui55.10.1+dfsg-5
ii  libqt5sql55.10.1+dfsg-5
ii  libqt5sql5-mysql  5.10.1+dfsg-5
ii  libqt5sql5-sqlite 5.10.1+dfsg-5
ii  libqt5widgets55.10.1+dfsg-5
ii  libstdc++68-20180402-1
ii  perl  5.26.1-5

Versions of packages digikam recommends:
ii  ffmpegthumbs   4:17.08.3-1
ii  firefox-esr [www-browser]  52.7.3esr-1
ii  konqueror [www-browser]4:17.08.3-2

Versions of packages digikam suggests:
ii  digikam-doc 4:5.6.0-4
ii  systemsettings  4:5.12.4-1

-- no debconf information

Bug#884917: nvidia-driver: Black screen after SDDM login

[MH]

Package: nvidia-driver
Version: 384.98-3
Severity: important

Dear Maintainer,

Video is broken when passed from PC through AVR. No problem when video is
passed directly to TV using the same HDMI cabling. 

Hardware setup as follows: HTPC>HDMI>AVR>HDMI>HDTV

Black screen after logging in via SDDM. I can access a terminal, login in as 
root, run startx and my KDE desktop will display but no audio device is 
detected. I can also do this as a regular user via the su command.

This problem did not exist with an older card using the nvidia-legacy driver.
The problem first exhibited as a black SDDM screen. However, I was still able
to login. After login, KDE desktop worked normally, both video and audio.
After a recent update, the SDDM login screen appeared normally, but I could
no longer see my desktop. Keyboard navigation is still possible with the
black screen.

-- Package-specific info:
uname -a:
Linux mediacenter 4.13.0-1-amd64 #1 SMP Debian 4.13.13-1 (2017-11-16) x86_64 
GNU/Linux

/proc/version:
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.4.0 20171112 (Debian 6.4.0-10)) #1 SMP Debian 4.13.13-1 (2017-11-16)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.98  Thu Oct 26 15:16:01 PDT 
2017
GCC version:  gcc version 6.4.0 20171206 (Debian 6.4.0-11) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 
710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GK208 [GeForce GT 
710B] [1462:8c93]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Dec 21 17:24 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Dec 21 17:24 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Dec 21 17:24 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Dec 21 17:24 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Dec 21 17:24 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Dec 21 17:24 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Dec 21 17:24 pci-:01:00.0-render -> ../renderD128
video:x:44:mhaag

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Dec  4 18:23 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 Dec  4 18:23 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 Dec  4 18:23 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Dec  4 18:23 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Dec  4 18:23 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 Dec  4 18:23 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   54 Dec  4 18:23 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Dec  4 18:23 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 Dec  4 18:23 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Dec  4 18:23 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Dec  4 18:23 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Dec  4 18:23 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Dec  4 18:23 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Dec  4 18:23 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Dec  4 18:23 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Dec  4 18:23 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   23 Dec 19 18:09 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root   59 Dec 19 18:09 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   58 Dec 

Bug#882571: kactivities-bin: Activities fail to remember associated applications

[MH]

Package: kactivities-bin
Version: 5.37.0-2
Severity: normal

Dear Maintainer,

After logging out of a session then logging back in, some applications will
load across all activities, not just the one they were associated with. This
appears to occur totally randomly. Sometimes applications load correctly,
sometimes not. This happens regularly on two different computers, both 
running Debian Buster.


-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kactivities-bin depends on:
ii  libc6  2.24-17
ii  libkf5activities5  5.37.0-2
ii  libqt5core5a   5.9.1+dfsg-9
ii  libstdc++6 8-20170923-1

kactivities-bin recommends no packages.

kactivities-bin suggests no packages.

-- no debconf information

Bug#848628: korganizer: Multiple event categories

[MH]

Package: korganizer
Version: 4:16.04.3-4
Followup-For: Bug #848628

Dear Maintainer,

After assigning an existing category tag to a new event, KOrganizer creates 
multiple copies
of that category in subsequent categories list. Sometimes it creates only one, 
sometimes
more than one. The duplicates have to be repeatedly deleted to keep the 
categories list sane.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages korganizer depends on:
ii  kdepim-runtime   4:16.04.2-2+b2
ii  kf5-kdepimlibs-kio-plugins   4:16.04.2-2
ii  kio  5.37.0-2
ii  libc62.24-17
ii  libgcc1  1:7.2.0-8
ii  libkf5akonadicalendar5   16.04.2-2
ii  libkf5akonadicontact54:16.04.2-2
ii  libkf5akonadicore5   4:16.04.3-6
ii  libkf5akonadimime5   4:16.04.2-2
ii  libkf5akonadinotes5  4:16.04.2-2
ii  libkf5akonadisearchpim5  16.04.3-1+b2
ii  libkf5akonadiwidgets54:16.04.3-6
ii  libkf5calendarcore5  4:16.04.2-1
ii  libkf5calendarsupport5   4:16.04.2-2
ii  libkf5calendarutils5 16.04.3-1
ii  libkf5codecs55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5contacts5  16.04.2-1
ii  libkf5coreaddons55.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5eventviews54:16.04.2-2
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5identitymanagement516.04.2-1
ii  libkf5incidenceeditor-bin16.04.2-2+b2
ii  libkf5incidenceeditor5   16.04.2-2+b2
ii  libkf5itemmodels55.37.0-2
ii  libkf5itemviews5 5.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kcmutils5  5.37.0-2
ii  libkf5kdelibs4support5   5.37.0-2
ii  libkf5kdepimdbusinterfaces5  4:16.04.2-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5mailcommon-plugins 4:16.04.2-2
ii  libkf5mailcommon54:16.04.2-2
ii  libkf5mailtransport5 16.04.2-3
ii  libkf5mime5  16.04.2-1
ii  libkf5newstuff5  5.37.0-2
ii  libkf5notifications5 5.37.0-2
ii  libkf5parts5 5.37.0-2
ii  libkf5pimcommon-plugins  4:16.04.2-2
ii  libkf5pimcommon5 4:16.04.2-2
ii  libkf5pimtextedit5   16.04.2-1
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5windowsystem5  5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libphonon4qt5-4  4:4.9.0-4
ii  libqt5core5a 5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5gui5   5.9.1+dfsg-9
ii  libqt5widgets5   5.9.1+dfsg-9
ii  libstdc++6   8-20170923-1
ii  phonon4qt5   4:4.9.0-4

Versions of packages korganizer recommends:
ii  kdepim-doc  4:16.04.3-4

korganizer suggests no packages.

-- no debconf information

Bug#879255: digikam: HTML export tool missing from tools menu

[MH]

Package: digikam
Version: 4:5.6.0-2
Severity: normal

Dear Maintainer,

An option to export images to an HTML page was reinstated in version 5.6 
according to
the Digikam website. This option is supposed to be listed under the Tools menu 
on the
main toolbar. However, it does not appear there, nor in any other menu.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages digikam depends on:
ii  digikam-data  4:5.6.0-2
ii  digikam-private-libs  4:5.6.0-2
ii  kipi-plugins  4:5.6.0-2
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-8
ii  libkf5configcore5 5.37.0-2
ii  libkf5coreaddons5 5.37.0-2
ii  libkf5filemetadata3   5.37.0-2
ii  libkf5i18n5   5.37.0-2
ii  libqt5core5a  5.9.1+dfsg-9
ii  libqt5gui55.9.1+dfsg-9
ii  libqt5sql55.9.1+dfsg-9
ii  libqt5sql5-mysql  5.9.1+dfsg-9
ii  libqt5sql5-sqlite 5.9.1+dfsg-9
ii  libqt5widgets55.9.1+dfsg-9
ii  libstdc++68-20170923-1
ii  perl  5.26.0-8

Versions of packages digikam recommends:
ii  ffmpegthumbs   4:16.08.3-1
ii  firefox-esr [www-browser]  52.4.0esr-2
ii  konqueror [www-browser]4:16.08.3-1

Versions of packages digikam suggests:
ii  digikam-doc 4:5.6.0-2
ii  systemsettings  4:5.10.5-2

-- no debconf information

Bug#879080: sddm: Sddm fails to display Debian theme

[MH]

Package: sddm
Version: 0.15.0-1
Severity: minor

Dear Maintainer,

Recent update of sddm resulted in the loss of the Debian sddm theme.
Sddm defaults to blue background. System settings indicate Debian theme
is selected, but sddm fails to display it. Tried resetting without success.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sddm depends on:
ii  adduser 3.116
ii  debconf 1.5.63
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-8
ii  libpam0g1.1.8-3.6
ii  libqt5core5a5.9.1+dfsg-9
ii  libqt5dbus5 5.9.1+dfsg-9
ii  libqt5gui5  5.9.1+dfsg-9
ii  libqt5network5  5.9.1+dfsg-9
ii  libqt5qml5  5.9.1-6
ii  libqt5quick55.9.1-6
ii  libstdc++6  8-20170923-1
ii  libsystemd0 235-2
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.9.1-6
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd 235-2
ii  sddm-theme-breeze [sddm-theme] 4:5.10.5-2
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.10.5-2

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.10.5-2

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#878622: pulseaudio defaults to disabled output device

[MH]

Package: pulseaudio
Version: 11.1-1
Severity: normal

Dear Maintainer,

Pulseaudio defaults to video card audio device instead of headphones/speakers
even after disabling that device's profile (set to "off"). It enables the
device as "line-out" even though nothing is plugged into the HDMI port on
the video card. It fails to recognize the headphones, which are plugged in
at all times, reporting the headphones as "unplugged".

I have to manually reset the output device to "headphones" everytime I log
onto the system to get sound. When I do this, onboard sound is enabled to
both the external speakers connected to the MB ports and the headphones,
but the setting is never retained.


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.116
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-17
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.11.20-1
ii  libgcc1  1:7.2.0-8
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.27-1
ii  libpulse011.1-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8-20170923-1
ii  libsystemd0  234-3
ii  libtdb1  1.3.13-2
ii  libudev1 234-3
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 11.1-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-5

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
pn  pavucontrol  
pn  pavumeter
ii  udev 234-3

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; 

Bug#873080: SDDM

[MH]

This bug, previously reported by me, still exists in sddm 0.15.0-1

Additional information:

The problem (black/blank screen) exhibits only when connected via an A/V 
receiver.  Sddm displays normally when attached directly to the TV (4k).

NVidia softare correctly enumerates the A/V device, so the latter must be 
sending correct EDID info. Also, it reports 1080p resolution, which is the 
maximum input resolution for the A/V device.

The problem clearly lies with sddm. BIOS displays correctly, grub boot menu 
displays correctly, and the KDE desktop displays correctly. Only sddm fails to 
display correctly, though it did display correctly when previously using a 
legacy NVidia device on the same system.

-- 
"The world is a dangerous place to live -- not because of the people who are
evil but because of the people who don't do anything about it."

--Albert Einstein

Bug#873080: sddm black screen no cursor

[MH]

Package: sddm
Version: 0.14.0-4
Severity: normal

Dear Maintainer,

Upon loading, sddm displays black screen with no cursor. It is still possible
to login. Once logged in sddm brings up the KDE desktop normally.

This occurs only over hdmi with nvidia-driver (current). When switching to a
vga cable problem disappears. Also, this problem does NOT occur with
nvidia-legacy-340xx-driver regardless of connection type.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * 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.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 sddm depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.61
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libpam0g1.1.8-3.6
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5qml5  5.7.1-2+b2
ii  libqt5quick55.7.1-2+b2
ii  libstdc++6  6.3.0-18
ii  libsystemd0 232-25+deb9u1
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.7.1-2+b2
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd 232-25+deb9u1
ii  sddm-theme-breeze [sddm-theme] 4:5.8.6-2.1
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.8.6-2.1
ii  sddm-theme-debian-elarun [sddm-theme]  0.14.0-4
ii  sddm-theme-debian-maui [sddm-theme]0.14.0-4
ii  sddm-theme-elarun [sddm-theme] 0.14.0-4
ii  sddm-theme-maldives [sddm-theme]   0.14.0-4
ii  sddm-theme-maui [sddm-theme]   0.14.0-4

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.4-1

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#851826: pulseaudio: USB headset detected, but no sound

[MH]

Package: pulseaudio
Version: 9.0-5
Severity: important

Dear Maintainer,

Pulseaudio correctly detects USB headset (headphones and microphone) but sound
is only output through external speakers.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.2-1
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-8
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.14-1
ii  libgcc1  1:6.2.1-5
ii  libice6  2:1.0.9-1+b1
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse09.0-5
ii  libsm6   2:1.2.2-1+b1
ii  libsndfile1  1.0.27-1
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1
ii  libstdc++6   6.2.1-5
ii  libsystemd0  232-8
ii  libtdb1  1.3.11-2
ii  libudev1 232-8
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 9.0-5

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
pn  pavucontrol  
pn  pavumeter
ii  udev 232-8

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; 

Bug#848628: korganizer creates duplicate event categories

[MH]

Package: korganizer
Version: 4:16.04.3-2
Severity: normal

Dear Maintainer,

When adding a category tag to an event, the category is replicated in the 
category
drop down selection list. There was a previous bug report on this but it was
closed. I do not have the old bug report number.

System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages korganizer depends on:
ii  kdepim-runtime   4:16.04.2-2
ii  kf5-kdepimlibs-kio-plugins   4:16.04.2-2
ii  libc62.24-8
ii  libgcc1  1:6.2.1-5
ii  libkf5akonadicalendar5   16.04.2-2
ii  libkf5akonadicontact54:16.04.2-2
ii  libkf5akonadicore-bin4:16.04.3-3+b1
ii  libkf5akonadicore5   4:16.04.3-3+b1
ii  libkf5akonadimime5   4:16.04.2-2
ii  libkf5akonadinotes5  4:16.04.2-2
ii  libkf5akonadisearchpim5  16.04.3-1
ii  libkf5akonadiwidgets54:16.04.3-3+b1
ii  libkf5calendarcore5  4:16.04.2-1
ii  libkf5calendarsupport5   4:16.04.2-2
ii  libkf5calendarutils5 16.04.3-1
ii  libkf5codecs55.27.0-1
ii  libkf5completion55.27.0-1
ii  libkf5configcore55.27.0-1
ii  libkf5configgui5 5.27.0-1
ii  libkf5configwidgets5 5.27.0-1
ii  libkf5contacts5  16.04.2-1
ii  libkf5coreaddons55.27.0-1
ii  libkf5dbusaddons55.27.0-1
ii  libkf5eventviews54:16.04.2-2
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.27.0-2
ii  libkf5iconthemes55.27.0-1
ii  libkf5identitymanagement516.04.2-1
ii  libkf5incidenceeditor-bin16.04.2-2
ii  libkf5incidenceeditor5   16.04.2-2
ii  libkf5itemmodels55.27.0-1
ii  libkf5itemviews5 5.27.0-1
ii  libkf5jobwidgets55.27.0-1
ii  libkf5kcmutils5  5.27.0-1
ii  libkf5kdelibs4support5   5.27.0-1
ii  libkf5kdepimdbusinterfaces5  4:16.04.2-2
ii  libkf5kiocore5   5.27.0-2
ii  libkf5kiowidgets55.27.0-2
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5mailcommon-plugins 4:16.04.2-2
ii  libkf5mailcommon54:16.04.2-2
ii  libkf5mailtransport5 16.04.2-3
ii  libkf5mime5  16.04.2-1
ii  libkf5newstuff5  5.27.0-1
ii  libkf5notifications5 5.27.0-1
ii  libkf5parts5 5.27.0-1
ii  libkf5pimcommon-plugins  4:16.04.2-2
ii  libkf5pimcommon5 4:16.04.2-2
ii  libkf5pimtextedit5   16.04.2-1
ii  libkf5service-bin5.27.0-1
ii  libkf5service5   5.27.0-1
ii  libkf5widgetsaddons5 5.27.0-1
ii  libkf5windowsystem5  5.27.0-1
ii  libkf5xmlgui55.27.0-1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libqt5core5a 5.7.1~20161021+dfsg-6
ii  libqt5dbus5  5.7.1~20161021+dfsg-6
ii  libqt5gui5   5.7.1~20161021+dfsg-6
ii  libqt5widgets5   5.7.1~20161021+dfsg-6
ii  libstdc++6   6.2.1-5
ii  phonon4qt5   4:4.9.0-4

Versions of packages korganizer recommends:
ii  kdepim-doc  4:16.04.3-2

korganizer suggests no packages.

-- no debconf information

Bug#641807: digikam: Digikam process still active after quitting application

[MH]

Package: digikam
Version: 2:1.2.0-7
Severity: normal


Digikam process still active after quitting application. If not manually 
killed, digikam will auto-restart upon reboot/login.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'testing'), (500, 'stable-updates')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-35-phenom (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 digikam depends on:
ii  digikam-data2:1.2.0-7digikam architecture-independant d
ii  kdebase-runtime 4:4.6.5-1runtime components from the offici
ii  kdepim-runtime  4:4.4.11.1-2 Runtime components for akonadi-kde
ii  libc6   2.13-10  Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.6.1-4GCC support library
ii  libglib2.0-02.28.6-1 The GLib library of C routines
ii  libgphoto2-22.4.6-3  gphoto2 digital camera library
ii  libgphoto2-port02.4.6-3  gphoto2 digital camera port librar
ii  libjasper1  1.900.1-7+b1 The JasPer JPEG-2000 runtime libra
ii  libjpeg62   6b1-1The Independent JPEG Group's JPEG 
ii  libkabc44:4.6.5-1library for handling address book 
ii  libkdcraw8  4:4.4.5-2RAW picture decoding C++ library (
ii  libkde3support4 4:4.6.5-2KDE 3 Support Library for the KDE 
ii  libkdecore5 4:4.6.5-2KDE Platform Core Library
ii  libkdeui5   4:4.6.5-2KDE Platform User Interface Librar
ii  libkexiv2-8 4:4.4.5-2Qt like interface for the libexiv2
ii  libkfile4   4:4.6.5-2File Selection Dialog Library for 
ii  libkhtml5   4:4.6.5-2KHTML Web Content Rendering Engine
ii  libkio5 4:4.6.5-2Network-enabled File Management Li
ii  libkipi74:4.4.5-2library for apps that want to use 
ii  libkjsapi4  4:4.6.5-2KJS API Library for the KDE Develo
ii  libknotifyconfig4   4:4.6.5-2library for configuring KDE Notifi
ii  libkparts4  4:4.6.5-2Framework for the KDE Platform Gra
ii  libkresources4  4:4.6.5-1KDE Resource framework library
ii  libkutils4  4:4.6.5-2dummy transitional library
ii  liblcms11.18.dfsg-1.2+b3 Color management library
ii  liblensfun0 0.2.4-1  Lens Correction library - Runtime 
ii  liblqr-1-0  0.4.1-1  converts plain array images into m
ii  libmarblewidget44:4.4.5-2Marble globe widget library
ii  libphonon4  4:4.6.0really4.5.0-4 multimedia framework from KDE - co
ii  libpng12-0  1.2.44-1+squeeze1PNG library - runtime
ii  libqt4-dbus 4:4.7.3-5Qt 4 D-Bus module
ii  libqt4-network  4:4.7.3-5Qt 4 network module
ii  libqt4-qt3support   4:4.7.3-5Qt 3 compatibility library for Qt 
ii  libqt4-sql  4:4.7.3-5Qt 4 SQL module
ii  libqt4-sql-sqlite   4:4.7.3-5Qt 4 SQLite 3 database driver
ii  libqt4-svg  4:4.7.3-5Qt 4 SVG module
ii  libqt4-xml  4:4.7.3-5Qt 4 XML module
ii  libqtcore4  4:4.7.3-5Qt 4 core module
ii  libqtgui4   4:4.7.3-5Qt 4 GUI module
ii  libsolid4   4:4.6.5-2Solid Library for KDE Platform
ii  libstdc++6  4.6.1-4  GNU Standard C++ Library v3
ii  libtiff43.9.4-5+squeeze3 Tag Image File Format (TIFF) libra
ii  libx11-62:1.3.3-4X11 client-side library
ii  libxau6 1:1.0.6-1X11 authorisation library
ii  libxdmcp6   1:1.0.3-2X11 Display Manager Control Protoc
ii  phonon  4:4.6.0really4.5.0-4 multimedia framework from KDE - me
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages digikam recommends:
ii  iceweasel [www-browser]   5.0-6  Web browser based on Firefox
ii  kipi-plugins  1.2.0-2+b1 image manipulation/handling plugin
ii  konqueror [www-browser]   4:4.6.5-1  advanced file manager, web browser
ii  w3m [www-browser] 0.5.2-9WWW browsable pager with excellent

Versions of packages digikam suggests:
ii  digikam-doc 1.2~svn1134171-1 handbook for digikam and showfoto 

-- 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#641178: recordmydesktop: Files larger than ~265 MiB are truncated and corrupted

[MH]

Package: recordmydesktop
Version: 0.3.8.1+svn602-1+b1
Severity: important


Subject says it all. Repeatable.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'testing'), (500, 'stable-updates')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-35-phenom (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 recordmydesktop depends on:
ii  libasound2 1.0.24.1-2shared library for ALSA applicatio
ii  libc6  2.13-10   Embedded GNU C Library: Shared lib
ii  libice62:1.0.6-2 X11 Inter-Client Exchange library
ii  libjack0 [libjack-0.11 1:0.118+svn3796-7 JACK Audio Connection Kit (librari
ii  libogg01.2.0~dfsg-1  Ogg bitstream library
ii  libpopt0   1.16-1lib for parsing cmdline parameters
ii  libsm6 2:1.1.1-1 X11 Session Management library
ii  libtheora0 1.1.1+dfsg.1-3The Theora Video Compression Codec
ii  libvorbis0a1.3.1-1   The Vorbis General Audio Compressi
ii  libvorbisenc2  1.3.1-1   The Vorbis General Audio Compressi
ii  libvorbisfile3 1.3.1-1   The Vorbis General Audio Compressi
ii  libx11-6   2:1.3.3-4 X11 client-side library
ii  libxdamage11:1.1.3-1 X11 damaged region extension libra
ii  libxext6   2:1.1.2-1 X11 miscellaneous extension librar
ii  libxfixes3 1:4.0.5-1 X11 miscellaneous 'fixes' extensio
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

recordmydesktop recommends no packages.

recordmydesktop 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#543402: gtk-qt-engine: Iceweasel consumes 100% cpu upon exit

[MH]

Package: gtk-qt-engine
Version: 1:1.1+svn5-4+b1
Severity: normal


Iceweasel fails to exit properly. Firefox-bin consumes 100% cpu. Process must 
be manually killed. Repeatable.

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

Kernel: Linux 2.6.32-34-phenom (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 gtk-qt-engine depends on:
ii  libatk1.0-0   1.30.0-1   The ATK accessibility toolkit
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libcairo2 1.10.2-6   The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-2.1  generic font configuration library
ii  libfreetype6  2.4.2-2.1  FreeType 2 font engine, shared lib
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libglib2.0-0  2.28.6-1   The GLib library of C routines
ii  libgtk2.0-0   2.20.1-2   The GTK+ graphical user interface 
ii  libpango1.0-0 1.28.3-1+squeeze2  Layout and rendering of internatio
ii  libqtcore44:4.6.3-4+squeeze1 Qt 4 core module
ii  libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3
ii  libx11-6  2:1.3.3-4  X11 client-side library

Versions of packages gtk-qt-engine recommends:
ii  kde-config-gtk-style 1:1.1+svn5-4+b1 KDE configuration module for GTK+ 

gtk-qt-engine 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#603949: apt-cacher: error during package upgrade prevents download/installation of packages

[MH]

Package: apt-cacher
Version: 1.6.12
Severity: important
Tags: d-i

Err http://zeus squeeze/main konversation 1.3.1-2   
 
  502  apt-cacher: libcurl error: Failed to connect to 2001:4070:1::fafb:
Network is unreachable
Err http://zeus squeeze/main konversation-data 1.3.1-2  
 
  502  apt-cacher: libcurl error: Failed to connect to 2001:4070:1::fafb:
Network is unreachable
Err http://zeus squeeze/main libgadu3 1:1.9.0-1
  502  apt-cacher: libcurl error: Failed to connect to 2001:4070:1::fafb:
Network is unreachable
Err http://zeus squeeze/main libkopete4 4:4.4.5-1
  502  apt-cacher: libcurl error: Failed to connect to 2001:4070:1::fafb:
Network is unreachable


Updating the remainder packages then this:

E: Failed to fetch
http://zeus:3142/ftp.pl.debian.org/debian/pool/main/k/kdebase-workspace/kdebase-
workspace-data_4.4.5-4_all.deb: 502  apt-cacher: libcurl error: Failed to
connect to 2001:4070:1::fafb: Network is unreachable
 


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

Kernel: Linux 2.6.32-15-phenom (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 apt-cacher depends on:
ii  ed1.4-3  The classic UNIX line editor
ii  libdigest-sha1-perl   2.13-1 NIST SHA-1 message digest algorith
ii  libfilesys-diskspace-perl 0.05-13fetch filesystem size and usage in
ii  libfreezethaw-perl0.5001-1   module to serialize and deserializ
pn  libio-compress-bzip2-perl none (no description available)
ii  libio-compress-perl [libio-co 2.024-1bundle of IO::Compress modules
ii  libio-interface-perl  1.05-1 socket methods to get/set interfac
ii  libwww-curl-perl  4.12-1 Perl bindings to libcurl
ii  libwww-perl   5.836-1Perl HTTP/WWW client/server librar
ii  perl [libio-compress-zlib-per 5.10.1-16  Larry Wall's Practical Extraction 

Versions of packages apt-cacher recommends:
ii  libberkeleydb-perl   0.42-1~squeeze1 use Berkeley DB 4 databases from P

Versions of packages apt-cacher suggests:
pn  libio-socket-inet6-perl   none (no description available)

-- Configuration Files:
/etc/default/apt-cacher changed:
AUTOSTART=1


-- 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#555747: kdeadmin: knetworkconf unusable

[MH]

Package: kdeadmin
Version: 4:4.4.4-1
Severity: normal

No interfaces listed under available network interfaces, all other options 
greyed out.

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

Kernel: Linux 2.6.32-15-phenom (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 kdeadmin depends on:
ii  kde-config-cron   4:4.4.4-1  program scheduler frontend
ii  knetworkconf  4:4.4.4-1  network configuration tool for KDE
ii  ksystemlog4:4.4.4-1  system log viewer for KDE
ii  kuser 4:4.4.4-1  user and group administration tool

Versions of packages kdeadmin recommends:
ii  system-config-printer-kde 4:4.4.4-1  KDE printer configuration utility

kdeadmin 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#588603: usb: Wireless USB keyboard no longer works

[MH]

Package: usb
Version: other
Severity: important

Logitech wireless bluetooth USB keyboard no longer works afer recent Squeeze 
update.

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

Kernel: Linux 2.6.32-15-phenom (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



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

Bug#586397: okular: Ocular fails to print to selected printer

[MH]

Package: okular
Version: 4:4.4.4-1
Severity: important

Okular fails to print to selected printer. Printer dialog reopens each time 
OK to print is selected. 

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

Kernel: Linux 2.6.32-15-phenom (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 okular depends on:
ii  kdebase-runtime 4:4.4.4-1runtime components from the offici
ii  libc6   2.11.1-3 Embedded GNU C Library: Shared lib
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libgcc1 1:4.4.4-1GCC support library
ii  libjpeg62   6b-16.1  The Independent JPEG Group's JPEG 
ii  libkdecore5 4:4.4.4-1the KDE Platform Core Library
ii  libkdeui5   4:4.4.4-1the KDE Platform User Interface Li
ii  libkio5 4:4.4.4-1the Network-enabled File Managemen
ii  libkparts4  4:4.4.4-1the Framework for the KDE Platform
ii  libkpty44:4.4.4-1the Pseudo Terminal Library for th
ii  libkutils4  4:4.4.4-1various utility classes for the KD
ii  libokularcore1  4:4.4.4-1libraries for the Okular document 
ii  libphonon4  4:4.6.0really4.4.2-1 the core library of the Phonon mul
ii  libpoppler-qt4-30.12.4-1 PDF rendering library (Qt 4 based 
ii  libqca2 2.0.2-1  libraries for the Qt Cryptographic
ii  libqimageblitz4 1:0.0.4-4QImageBlitz image effects library
ii  libqt4-dbus 4:4.6.3-1Qt 4 D-Bus module
ii  libqt4-svg  4:4.6.3-1Qt 4 SVG module
ii  libqt4-xml  4:4.6.3-1Qt 4 XML module
ii  libqtcore4  4:4.6.3-1Qt 4 core module
ii  libqtgui4   4:4.6.3-1Qt 4 GUI module
ii  libspectre1 0.2.5-1  Library for rendering PostScript d
ii  libstdc++6  4.4.4-1  The GNU Standard C++ Library v3
ii  phonon  4:4.6.0really4.4.2-1 metapackage for the Phonon multime
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

okular recommends no packages.

Versions of packages okular suggests:
ii  ghostscript 8.71~dfsg2-3 The GPL Ghostscript PostScript/PDF
pn  kttsd   none   (no description available)
pn  okular-extra-backends   none   (no description available)
pn  poppler-datanone   (no description available)
pn  texlive-binariesnone   (no description available)
pn  unrar   none   (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#586080: plasma-desktop: CD/DVD fails to automount

[MH]

Package: plasma-desktop
Version: 4:4.4.4-1
Severity: normal
Tags: squeeze

After updating to latest KDE4 in testing CD/DVD no longer automounts. Can 
manually mount, read, write eject.

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

Kernel: Linux 2.6.32-15-phenom (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 plasma-desktop depends on:
ii  kdebase-runtime   4:4.4.4-1  runtime components from the offici
ii  libc6 2.11.1-3   Embedded GNU C Library: Shared lib
ii  libkdecore5   4:4.4.4-1  the KDE Platform Core Library
ii  libkdeui5 4:4.4.4-1  the KDE Platform User Interface Li
ii  libkephal44:4.4.4-1  API for easier handling of multihe
ii  libkfile4 4:4.4.4-1  the File Selection Dialog Library 
ii  libkio5   4:4.4.4-1  the Network-enabled File Managemen
ii  libktexteditor4   4:4.4.4-1  the KTextEditor interfaces for the
ii  libkutils44:4.4.4-1  various utility classes for the KD
ii  libkworkspace44:4.4.4-1  library for the kdebase workspace
ii  libplasma34:4.4.4-1  the Plasma Library for the KDE Pla
ii  libplasmagenericshell44:4.4.4-1  shared elements for all the plasma
ii  libqt4-dbus   4:4.6.3-1  Qt 4 D-Bus module
ii  libqt4-script 4:4.6.3-1  Qt 4 script module
ii  libqt4-xml4:4.6.3-1  Qt 4 XML module
ii  libqtcore44:4.6.3-1  Qt 4 core module
ii  libqtgui4 4:4.6.3-1  Qt 4 GUI module
ii  libsolid4 4:4.4.4-1  Solid Library for KDE Platform
ii  libsolidcontrol4  4:4.4.4-1  library for Solid based network ma
ii  libstdc++64.4.4-1The GNU Standard C++ Library v3
ii  libtaskmanager4a  4:4.4.4-1  library which provides task manage
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  libxext6  2:1.1.1-3  X11 miscellaneous extension librar
ii  plasma-widgets-workspace  4:4.4.4-1  KDE 4 base workspace Plasma widget

Versions of packages plasma-desktop recommends:
ii  kdebase-workspace 4:4.4.4-1  base workspace components from the

plasma-desktop 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#586112: plasma-desktop: Fails to automount USB cardreader

[MH]

Package: plasma-desktop
Version: 4:4.4.4-1
Severity: normal
Tags: squeeze

After update to most recent KDE packages (testing), USB cardreader fails to 
automount. Can be manually mounted, sometimes requires system reboot.

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

Kernel: Linux 2.6.32-15-phenom (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 plasma-desktop depends on:
ii  kdebase-runtime   4:4.4.4-1  runtime components from the offici
ii  libc6 2.11.1-3   Embedded GNU C Library: Shared lib
ii  libkdecore5   4:4.4.4-1  the KDE Platform Core Library
ii  libkdeui5 4:4.4.4-1  the KDE Platform User Interface Li
ii  libkephal44:4.4.4-1  API for easier handling of multihe
ii  libkfile4 4:4.4.4-1  the File Selection Dialog Library 
ii  libkio5   4:4.4.4-1  the Network-enabled File Managemen
ii  libktexteditor4   4:4.4.4-1  the KTextEditor interfaces for the
ii  libkutils44:4.4.4-1  various utility classes for the KD
ii  libkworkspace44:4.4.4-1  library for the kdebase workspace
ii  libplasma34:4.4.4-1  the Plasma Library for the KDE Pla
ii  libplasmagenericshell44:4.4.4-1  shared elements for all the plasma
ii  libqt4-dbus   4:4.6.3-1  Qt 4 D-Bus module
ii  libqt4-script 4:4.6.3-1  Qt 4 script module
ii  libqt4-xml4:4.6.3-1  Qt 4 XML module
ii  libqtcore44:4.6.3-1  Qt 4 core module
ii  libqtgui4 4:4.6.3-1  Qt 4 GUI module
ii  libsolid4 4:4.4.4-1  Solid Library for KDE Platform
ii  libsolidcontrol4  4:4.4.4-1  library for Solid based network ma
ii  libstdc++64.4.4-1The GNU Standard C++ Library v3
ii  libtaskmanager4a  4:4.4.4-1  library which provides task manage
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  libxext6  2:1.1.1-3  X11 miscellaneous extension librar
ii  plasma-widgets-workspace  4:4.4.4-1  KDE 4 base workspace Plasma widget

Versions of packages plasma-desktop recommends:
ii  kdebase-workspace 4:4.4.4-1  base workspace components from the

plasma-desktop 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#585406: klipper applet not available

[MH]

Package: klipper
Version: 4:4.4.3-1
Severity: important
Tags: squeeze

klipper icon does not appear in system tray. systemtray display settings have 
no effect. This only seems to affect some users.

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

Kernel: Linux 2.6.32-15-phenom (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 klipper depends on:
ii  kdebase-runtime 4:4.4.3-1runtime components from the offici
ii  libc6   2.10.2-9 Embedded GNU C Library: Shared lib
ii  libkdecore5 4:4.4.3-2the KDE Platform Core Library
ii  libkdeui5   4:4.4.3-2the KDE Platform User Interface Li
ii  libqt4-dbus 4:4.6.2-4Qt 4 D-Bus module
ii  libqtcore4  4:4.6.2-4Qt 4 core module
ii  libqtgui4   4:4.6.2-4Qt 4 GUI module
ii  libstdc++6  4.4.4-1  The GNU Standard C++ Library v3
ii  libx11-62:1.3.3-3X11 client-side library
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

klipper recommends no packages.

klipper 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#584668: kde-plasma-desktop: CD/DVD fails to automount

[MH]

Package: kde-plasma-desktop
Version: 5:61
Severity: normal
Tags: squeeze

SATA CD/DVD fails to automount. Notifier indicates No devices plugged in. Can 
mount /dev/sr0 manually.

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

Kernel: Linux 2.6.32-15-phenom (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 kde-plasma-desktop depends on:
ii  kdebase-apps  4:4.4.3-1  base applications from the officia
ii  kdebase-runtime   4:4.4.3-1  runtime components from the offici
ii  kdebase-workspace 4:4.4.3-1  base workspace components from the
ii  plasma-desktop4:4.4.3-1  The KDE Plasma workspace for deskt

Versions of packages kde-plasma-desktop recommends:
ii  kdm   4:4.4.3-1  KDE Display Manager for X11
ii  xserver-xorg  1:7.5+6the X.Org X server

Versions of packages kde-plasma-desktop suggests:
pn  kde-l10n  none (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#584577: kde-plasma-desktop: Panel resizes unexpectedly

[MH]

Package: kde-plasma-desktop
Version: 5:61
Severity: normal
Tags: squeeze

Panel resizes unexpectedly from full-screen to half-screen, left justified. Can 
be reset, but the issue recurs.

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

Kernel: Linux 2.6.32-15-phenom (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 kde-plasma-desktop depends on:
ii  kdebase-apps  4:4.4.3-1  base applications from the officia
ii  kdebase-runtime   4:4.4.3-1  runtime components from the offici
ii  kdebase-workspace 4:4.4.3-1  base workspace components from the
ii  plasma-desktop4:4.4.3-1  The KDE Plasma workspace for deskt

Versions of packages kde-plasma-desktop recommends:
ii  kdm   4:4.4.3-1  KDE Display Manager for X11
ii  xserver-xorg  1:7.5+6the X.Org X server

Versions of packages kde-plasma-desktop suggests:
pn  kde-l10n  none (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#577534: base: cdrom fails to mount

[MH]

Package: base
Severity: important
Tags: squeeze


No device for IDE CD/DVD is created in /dev. CD/DVD is unmountable.

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

Kernel: Linux 2.6.32-phenom (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



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

Bug#525167: 3.0.9 available (security update)

[mh]

On Wed, Apr 29, 2009 at 07:23:33PM +0200, Alberto wrote:
  The version in Lenny is very up-to-date, thank you.
  (except for the new release today).
 
 Uhm... but the version is still 3.0.6. Is it updated
 via xulrunnel? Just to avoid futher mistakes...

Yes. Also, don't feel like you need to report these bugs, the debian
security team and the mozilla team are tracking these anyway.

Mike



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

Bug#487949: gentoo: gtk located as error source

[mh]

Package: gentoo
Version: 0.11.56-1
Followup-For: Bug #487949


This bug makes gentoo quite unusable because copying of directory trees and 
automatic unmounting
of mass-storage devices is broken.


It seems, that the following construct in the sources are causing the trouble:

while( gtk_events_pending() )
gtk_main_iteration();

this construct sets the errno variable to value 11.
I dont know the reason for this, but if you reset errno after every occurence 
of the construct
gentoo seems work fine again. (maybe its a bug in gtk1.2?)

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

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gentoo depends on:
ii  libc62.7-10  GNU C Library: Shared libraries
pi  libglib1.2ldbl   1.2.10-19   The GLib library of C routines
ii  libgtk1.21.2.10-18.1 The GIMP Toolkit set of widgets fo
ii  libx11-6 2:1.1.4-2   X11 client-side library
ii  libxext6 2:1.0.4-1   X11 miscellaneous extension librar
ii  libxi6   2:1.1.3-1   X11 Input extension library

gentoo recommends no packages.

-- no debconf information



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

Bug#487949: gentoo: pop error message with (code 11) on every directory which is entered

[mh]

Package: gentoo
Version: 0.11.56-1
Severity: important


Since last update gentoo pops up an error message on _every_ directory one trys 
to enter.
The message is (original text in german): 'Konnte nicht direnter xxx: Die 
Ressource ist zur Zeit nicht verfügbar (code 11)'.
Translated into english would mean: 'Could not direnter xxx: the resource is 
not available (code 11)'
xxx is the path of the directory you try to enter.

The error occures in actual testing and in actual unstable distribution (tested 
with 3 different independend linux boxes).
It seems to be an error with an library gentoo depends on, but I am unable to 
locate it.
Every other program works fine and doesn't show this error.


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

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gentoo depends on:
ii  libc62.7-10  GNU C Library: Shared libraries
pi  libglib1.2ldbl   1.2.10-19   The GLib library of C routines
ii  libgtk1.21.2.10-18.1 The GIMP Toolkit set of widgets fo
ii  libx11-6 2:1.1.4-2   X11 client-side library
ii  libxext6 2:1.0.4-1   X11 miscellaneous extension librar
ii  libxi6   2:1.1.3-1   X11 Input extension library

gentoo recommends no packages.

-- no debconf information



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

Bug#467096: still buggy

[mh]

The newest version (traverso_0.42.0-2) still is compiled in an 
overoptimized way and fails completely to start on a computer with duron 
900 cpu.


I am no expert, but following the log

http://buildd.debian.org/fetch.cgi?pkg=traversover=0.42.0-2arch=i386stamp=1207443881file=log

it seems, that the package is built with sse enabled and thus 
overoptimized for duron 900 (and other) cpu_s.



Is this sufficient for a bug report or do I need to file a new one?

Regards

mh




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

Bug#467096: need to revoke in part

[mh]

As far as it regards the icons, I have to revoke this bug.

My comparison regarding the output of # dpkg -L traverso was based on 
 incomplete information. The user I compared the output with did not 
mention, that he added the icons manually. So I appologize for the 
confusion I might have created regarding the icons.



Meanwhile I compiled traverso from a tarball. This version opens with 
some errors regarding memory lock and so on, but does not crash. After 
adding tree lines to /etc/security/limits.conf, this version opens 
without any error.


added lines:
@audio - rtprio  90
@audio - nice-10
@audio - memlock 300


The debian/sid version still crashes. In so far, the bug persists. I am 
courious to know whether the debian version is compiled with some 
settings that make traverso incompatible with a duron 900 cpu (which 
still is i686)?



kind regards

mh




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

Bug#467096: no icons

[mh]

It seems, the icons did not get packed in:

This is the whole output of dpkg -L traverso (installed from debian sid):


# dpkg -L traverso
/.
/usr
/usr/bin
/usr/bin/traverso
/usr/share
/usr/share/applications
/usr/share/applications/traverso.desktop
/usr/share/doc
/usr/share/doc/traverso
/usr/share/doc/traverso/README
/usr/share/doc/traverso/TODO
/usr/share/doc/traverso/copyright
/usr/share/doc/traverso/changelog.Debian.gz
/usr/share/doc/traverso/changelog.gz
/usr/share/menu
/usr/share/menu/traverso
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/traverso.1.gz


Users, with self-compiled svn versions have this output:

$ dpkg -L traverso
/.
/usr
/usr/bin
/usr/bin/traverso
/usr/share
/usr/share/applications
/usr/share/applications/traverso.desktop
/usr/share/doc
/usr/share/doc/traverso
/usr/share/doc/traverso/changelog.gz
/usr/share/doc/traverso/README
/usr/share/doc/traverso/TODO
/usr/share/doc/traverso/copyright
/usr/share/doc/traverso/changelog.Debian.gz
/usr/share/doc/traverso/traverso-manual-0.42.0.pdf
/usr/share/doc/traverso/traverso-manual-german-0.42.0.pdf
/usr/share/menu
/usr/share/menu/traverso
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/traverso.1.gz
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/128x128
/usr/share/icons/hicolor/128x128/apps
/usr/share/icons/hicolor/128x128/apps/traverso.png
/usr/share/icons/hicolor/128x128/mimetypes
/usr/share/icons/hicolor/128x128/mimetypes/gnome-mime-application-x-traverso.png
/usr/share/icons/hicolor/16x16
/usr/share/icons/hicolor/16x16/apps
/usr/share/icons/hicolor/16x16/apps/traverso.png
/usr/share/icons/hicolor/16x16/mimetypes
/usr/share/icons/hicolor/16x16/mimetypes/gnome-mime-application-x-traverso.png
/usr/share/icons/hicolor/24x24
/usr/share/icons/hicolor/24x24/apps
/usr/share/icons/hicolor/24x24/apps/traverso.png
/usr/share/icons/hicolor/24x24/mimetypes
/usr/share/icons/hicolor/24x24/mimetypes/gnome-mime-application-x-traverso.png
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/48x48/apps/traverso.png
/usr/share/icons/hicolor/48x48/mimetypes
/usr/share/icons/hicolor/48x48/mimetypes/gnome-mime-application-x-traverso.png
/usr/share/icons/hicolor/64x64
/usr/share/icons/hicolor/64x64/apps
/usr/share/icons/hicolor/64x64/apps/traverso.png
/usr/share/icons/hicolor/64x64/mimetypes
/usr/share/icons/hicolor/64x64/mimetypes/gnome-mime-application-x-traverso.png
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/icons/hicolor/scalable/apps/traverso.svg
/usr/share/icons/hicolor/scalable/mimetypes
/usr/share/icons/hicolor/scalable/mimetypes/gnome-mime-application-x-traverso.sv


kind regards

mh



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

Bug#467096: traverso: missing theme file - crash on start

[mh]

Package: traverso
Version: 0.42.0-1
Severity: grave
Justification: renders package unusable


Traverso crashes on start.

$ traverso
No Hardware specific optimizations in use
Themer:: Using themefile: :/themes/TraversoLight/traversotheme.xml
Ungültiger Maschinenbefehl

No theme file for traverso exists.

No additional output with debug level 1-4.

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

Kernel: Linux 2.6.24-2.6.24.2.slh.11-sidux-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages traverso depends on:
ii  libasound2  1.0.15-3 ALSA library
ii  libc6   2.7-8GNU C Library: Shared libraries
ii  libfftw3-3  3.1.2-3  library for computing Fast Fourier
ii  libflac81.2.1-1.1Free Lossless Audio Codec - runtim
ii  libgcc1 1:4.3-20080219-1 GCC support library
ii  libjack00.109.2-1JACK Audio Connection Kit (librari
ii  libmad0 0.15.1b-2.1  MPEG audio decoder library
ii  libogg0 1.1.3-3  Ogg Bitstream Library
ii  libqt4-core 4.3.3-2  Qt 4 core non-GUI functionality ru
ii  libqt4-gui  4.3.3-2  Qt 4 core GUI functionality runtim
ii  libraptor1  1.4.16-1 Raptor RDF parser and serializer l
ii  librdf0 1.0.7-1  Redland Resource Description Frame
ii  libsamplerate0  0.1.2-5  audio rate conversion library
ii  libsndfile1 1.0.17-4 Library for reading/writing audio 
ii  libstdc++6  4.3-20080219-1   The GNU Standard C++ Library v3
ii  libvorbis0a 1.2.0.dfsg-3 The Vorbis General Audio Compressi
ii  libvorbisenc2   1.2.0.dfsg-3 The Vorbis General Audio Compressi
ii  libvorbisfile3  1.2.0.dfsg-3 The Vorbis General Audio Compressi
ii  libwavpack1 4.41.0-1 an audio codec (lossy and lossless

traverso recommends no packages.

-- no debconf information

Bug#398030: exim: diff for NMU version 3.36-18.2

[mh+debian-packages]

Package: exim
Version: 3.36-18.1
Severity: normal
Tags: patch

Hi,

The following is the diff for my exim 3.36-18.2 NMU.

Greetings
Marc

diff -u exim-3.36/OS/os.h-Linux exim-3.36/OS/os.h-Linux
--- exim-3.36/OS/os.h-Linux
+++ exim-3.36/OS/os.h-Linux
@@ -25,0 +26,15 @@
+
+/* Fudge added because this Linux doesn't appear to have a definition
+for ip_options in /usr/include/linux/ip.h. */
+
+#define ip_options options
+
+/* Fudge added because this Linux doesn't appear to have a definition
+for ip_options in /usr/include/linux/ip.h. */
+
+#define ip_options options
+
+/* Fudge added because this Linux doesn't appear to have a definition
+for ip_options in /usr/include/linux/ip.h. */
+
+#define ip_options options
diff -u exim-3.36/debian/changelog exim-3.36/debian/changelog
--- exim-3.36/debian/changelog
+++ exim-3.36/debian/changelog
@@ -1,3 +1,22 @@
+exim (3.36-18.2) unstable; urgency=low
+
+  * Non-maintainer upload prepared by Amaya - thanks!
+  * the make exim 3 to be released with etch release, courtesy of
+the stable release team
+  * Get rid of the /usr/doc link in postinst
+(Closes: #359397, #359404, #332303).
+  * Now consistently using invoke-rc.d in maintainer scripts (Closes: #367741).
+  * Add a depencency on libdb3-util (Closes: #375965).
+  * Move exim_lock man page from 1 to 8
+  * Add netbase dependency for exim binary package
+  * debian/copyright:
+* Fix FSF postal address
+* Fix Debian GNU/Linux spelling error
+  * manually strip exim_* and eximon.bin
+  * Standards-Version: 3.7.2.2 (no changes necessary with a lot of good will).
+
+ -- Marc Haber [EMAIL PROTECTED]  Sat, 11 Nov 2006 10:45:55 +0100
+
 exim (3.36-18.1) unstable; urgency=low
 
   * Non-maintainer upload.
@@ -43,7 +62,7 @@
 list instead (Closes: #295844)
   * debian/postinst: tell people exim 3 is obsolete on new installations
 or upgrades from woody versions
- * debian/postinst: only chown databases if db directory exists (Closes:
+  * debian/postinst: only chown databases if db directory exists (Closes:
 #297897)
   * src/readconf.c: validate pid_file_path to avoid security problem (note
 that this is only a security hole if you don't trust someone who has
diff -u exim-3.36/debian/control exim-3.36/debian/control
--- exim-3.36/debian/control
+++ exim-3.36/debian/control
@@ -2,7 +2,7 @@
 Section: mail
 Priority: extra
 Maintainer: Mark Baker [EMAIL PROTECTED]
-Standards-Version: 3.1.0
+Standards-Version: 3.7.2.2
 Build-Depends: libpcre3-dev, libldap2-dev, libpam0g-dev, libident-dev, 
libwrap0-dev, libdb3-dev, libice-dev, libxaw7-dev, libxmu-dev, libxt-dev, 
libxext-dev, libx11-dev
 
 Package: exim
@@ -12,8 +12,7 @@
 Provides: mail-transport-agent
 Conflicts: mail-transport-agent, exim-doc-html (=3.00-2), suidregister 
(0.50)
 Replaces: mail-transport-agent
-Depends: ${shlibs:Depends}, cron (=3.0pl1-42)
-Recommends: netbase
+Depends: ${shlibs:Depends}, netbase, cron (=3.0pl1-42), libdb3-util
 Description: An obsolete MTA (Mail Transport Agent), replaced by exim4
  This package contains exim 3, an outdated version of the exim Mail
  Transport Agent. This package is not going to be updated any more,
diff -u exim-3.36/debian/config exim-3.36/debian/config
--- exim-3.36/debian/config
+++ exim-3.36/debian/config
@@ -37,7 +37,7 @@
 system( 'update-rc.d exim defaults /dev/null' ) ;
 
 # Restart daemon
-system( '/etc/init.d/exim start' ) ;
+system( ' invoke-rc.d exim start' ) ;
 
 exit 0 ;
 }
diff -u exim-3.36/debian/rules exim-3.36/debian/rules
--- exim-3.36/debian/rules
+++ exim-3.36/debian/rules
@@ -96,6 +96,8 @@
install -m 0644 doc/ChangeLog debian/tmp/usr/share/doc/exim/changelog
gzip -9v debian/tmp/usr/share/doc/exim/*
install -m 0644 debian/copyright debian/tmp/usr/share/doc/exim
+   # strip binaries
+   strip --remove-section=.comment --remove-section=.note --strip-unneeded 
debian/tmp/usr/sbin/exim_*
# Generate md5sums
(cd debian/tmp; find -type f | sed s#^./## | grep -v DEBIAN | \
xargs md5sum  DEBIAN/md5sums )
@@ -123,6 +125,8 @@
# Move eximon back
mv eximon debian/tmp/usr/sbin
mv eximon.bin debian/tmp/usr/lib/exim
+   #
+   strip --remove-section=.comment --remove-section=.note --strip-unneeded 
debian/tmp/usr/lib/exim/eximon.bin
# Install man page
cp debian/eximon.8 debian/tmp/usr/share/man/man8
gzip -9v debian/tmp/usr/share/man/man8/*
diff -u exim-3.36/debian/postinst exim-3.36/debian/postinst
--- exim-3.36/debian/postinst
+++ exim-3.36/debian/postinst
@@ -23,10 +23,10 @@
 
install -d -omail -gmail /var/run/exim
 
-   # Create /usr/doc symlink
-   if [ -d /usr/doc -a ! -e /usr/doc/exim ]; then
-   ln -sf ../share/doc/exim /usr/doc/exim
-   fi
+   # Remove /usr/doc symlink
+if [ -d /usr/doc -a -h /usr/doc/exim -a -d /usr/share/doc/exim ]; then
+rm -f /usr/doc/exim
+