Bug#1034124: udev security update breaks all ext4 removable storage handling

[Floris Bos]

Package: udisks2

Version: 2.8.1-4+deb10u1

Severity: serious


Hi,


The security team recently released udisks2 2.8.1-4+deb10u1 that forces 
the mount option 'errors=remount-ro' to be used for all mounting 
operations on ext4 file systems.
However it seems the code was not modified correctly to allow that 
option to be used.



On a system with a LXDE based desktop environment, hot-plugging an ext4 
formatted USB drive, result in the user being presented with an "Mount 
option `errors=remount-ro' is not allowed" error dialog box, and the 
mount not occurring.


Same when mounting manually as regular user through udisksctl:

==
max@pibuster:~ $ udisksctl mount -b /dev/sda2
Error mounting /dev/sda2: 
GDBus.Error:org.freedesktop.UDisks2.Error.OptionNotPermitted: Mount 
option `errors=remount-ro' is not allowed

==


Looking at debian/patches/mount-ext-readonly-on-errors.patch
It did seem the author of the patch knew options need to be allowed, as 
he does add "errors=remount-ro" to ext4_allow:


+static const gchar *ext4_allow[] = { "errors=remount-ro", NULL };

However looking at is_mount_option_allowed() in 
src/udiskslinuxfilesystem.c the allow list handling code only expect a 
lists of allowed option keys in ext4_allow, not entries in the form 
key=value...


So that is not going to fly without further changes to 
is_mount_option_allowed()...




Yours sincerely,

Floris Bos

Bug#1031649: wine: /usr/bin/wine64 still required

[Floris Renaud]

On zondag 19 februari 2023 20:08:54 (+01:00), Jens Reyer wrote:

> Source: wine
> Version: 8.0~repack-4
> Severity: serious
> 
> Hi Mike,
> 
> I wasn't aware of this, but it seems indeed that /usr/bin/wine64 is 
required somehow: winetricks fails to start with 8.0~repack-4, but works 
with 8.0~repack-2.
> 
> I don't understand yet what's exactly going wrong (winetricks complains 
about some empty output, but if I execute said command manually I get the 
output), but I think the recent change should be reverted.
> 
> Greets anyway!

> jre
> 
> 
> 
> Winetricks fails with 8.0~repack-4:
> 
> jens@thing:~$ wine --version

> wine-8.0 (Debian 8.0~repack-4)
> jens@thing:~$ winetricks
> Executing mkdir -p /home/jens
> --
> warning: You are using a 64-bit WINEPREFIX. Note that many verbs only 
install 32-bit versions of packages. If you encounter problems, please 
retest in a clean 32-bit WINEPREFIX before reporting a bug.

> --
> --
> WINEPREFIX INFO:
> Drive C: total 28
> drwxr-xr-x  7 jens jens 4096 Feb 13 21:28 .
> drwxr-xr-x  4 jens jens 4096 Feb 19 19:50 ..
> drwxr-xr-x  3 jens jens 4096 Feb 13 21:28 ProgramData
> drwxr-xr-x  6 jens jens 4096 Feb 13 21:28 Program Files
> drwxr-xr-x  6 jens jens 4096 Feb 19 19:28 Program Files (x86)
> drwxr-xr-x  4 jens jens 4096 Feb 13 21:28 users
> drwxr-xr-x 21 jens jens 4096 Feb 19 19:28 windows
> 
> Registry info:

> /home/jens/.wine/system.reg:#arch=win64
> /home/jens/.wine/user.reg:#arch=win64
> /home/jens/.wine/userdef.reg:#arch=win64
> --
> --
> warning: wine cmd.exe /c echo '%AppData%' returned empty string, error 
message ""

> --
> jens@thing:~$ echo $?
> 1
> jens@thing:~$ wine cmd.exe /c echo '%AppData%'
> 0098:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.
> 0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.

> C:\users\jens\AppData\Roaming
> 
> 

Isn't this a bug in winetricks? When Wine is compiled the new way 
(--enable-archs=i386,x86_64), there isn't, as far as I know, a wine64 file.


From 
https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L3113

---

# Wrapper around winetricks_early_wine()
# Same idea, but use $WINE_ARCH, i.e., always use wine64 for 64-bit 
prefixes

# Currently only used by w_expand_env()
winetricks_early_wine_arch()
{
WINE="${WINE_ARCH}" winetricks_early_wine "$@"
}
---

Bug#1030981: nvidia-kernel-dkms: Depends on missing firmware-nvidia-gsp-525.85.12

[Floris Renaud]

On vrijdag 10 februari 2023 08:04:56 (+01:00), Scott Tripp wrote:

> Package: nvidia-kernel-dkms
> Version: 525.85.12-1
> Severity: important
> X-Debbugs-Cc: kscott.tr...@gmail.com
> 
> Dear Maintainer,
> 
> I cannot install nvidia-driver, as that depends on nvidia-kernel-dkms

> (this package), which in turn depends on firmware-nvidia-gsp-525.85.12,
> which is missing.
> 
> The following packages have unmet dependencies:
>  nvidia-kernel-dkms : Depends: firmware-nvidia-gsp (= 525.85.12) but it 
is not installable or
>firmware-nvidia-gsp-525.85.12 but it is 
not installable
> 
> Thanks,

> Scott
> 


The firmware-nvidia-gsp package is moved from non-free to non-free-firmware


Add the non-free-firmware repository and try again
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split


Floris

Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume

[Floris Bruynooghe]

Hi Salvatore,

On Tue 20 Dec 2022 at 06:55 +0100, Salvatore Bonaccorso wrote:

> Hi Floris,
>
> On Sat, Dec 17, 2022 at 01:26:27PM +0100, Floris Bruynooghe wrote:
>> Hi Salvatore,
>> 
>> On Fri 16 Dec 2022 at 22:54 +0100, Salvatore Bonaccorso wrote:
>> > On Fri, Dec 16, 2022 at 10:34:08PM +0100, Floris Bruynooghe wrote:
>> >> On Fri 16 Dec 2022 at 21:50 +0100, Salvatore Bonaccorso wrote:
>> >> > On Fri, Dec 16, 2022 at 09:28:35PM +0100, Floris Bruynooghe wrote:
>> >> >> Package: src:linux
>> >> >> Version: 6.0.10-2
>> >> >> Severity: important
>> >> >> 
>> >> >> Dear Maintainer,
>> >> >> 
>> >> >> Since the 6.0.0-5 kernel the i915 graphics driver often fails on 
>> >> >> resume.
>> >> >> Downgrading to the 6.0.0-4 kernel fixes it and the driver works
>> >> >> flawlessly across resume, changing displays etc.
>> >> >> 
>> >> >> On the -5 kernel the following errors are observed when the driver
>> >> >> crashes:
>> >> >> 
>> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-9: PM: parent card0 
>> >> >> should not be sleeping
>> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-10: PM: parent card0 
>> >> >> should not be sleeping
>> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-11: PM: parent card0 
>> >> >> should not be sleeping
>> >> >> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: [drm] *ERROR* 
>> >> >> Sending link address failed with -5
>> >> >> Dec 13 11:26:58 fredriksen kernel: [ cut here ]
>> >> >> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: 
>> >> >> drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
>> >> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at 
>> >> >> drivers/gpu/drm/i915/display/intel_tc.c:711 int>
>> >> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm 
>> >> >> rfcomm cmac algif_hash algif_skcipher af_alg>
>> >> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic 
>> >> >> snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
>> >> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables 
>> >> >> x_tables autofs4 btrfs blake2b_generic libcrc32c>
>> >> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: 
>> >> >> kworker/u32:101 Not tainted 6.0.0-5-amd64 #1  Debian >
>> >> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 
>> >> >> 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
>> >> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound 
>> >> >> async_run_entry_fn
>> >> >> Dec 13 11:26:58 fredriksen kernel: RIP: 
>> >> >> 0010:intel_tc_port_sanitize+0x2d2/0x490 [i915]
>> >> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 
>> >> >> 8b 2f e8 a7 44 42 e3 48 c7 c1 f8 a6 d6 c0>
>> >> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:a84dc5debc08 EFLAGS: 
>> >> >> 00010286
>> >> >> Dec 13 11:26:58 fredriksen kernel: RAX:  RBX: 
>> >> >> 9c812065 RCX: 
>> >> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0001 RSI: 
>> >> >> a4b7eeea RDI: 
>> >> >> Dec 13 11:26:58 fredriksen kernel: RBP:  R08: 
>> >> >> a5262260 R09: a5b5348a
>> >> >> Dec 13 11:26:58 fredriksen kernel: R10:  R11: 
>> >> >> 004a R12: 9c81101a2000
>> >> >> Dec 13 11:26:58 fredriksen kernel: R13: 9c8101f19900 R14: 
>> >> >>  R15: 9c81101a2000
>> >> >> Dec 13 11:26:58 fredriksen kernel: FS:  () 
>> >> >> GS:9c883f40() knlGS:
>> >> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS:  ES:  CR0: 
>> >> >> 80050033
>> >> >> Dec 13 11:26:58 fredriksen kernel: CR2: 55710e140b16 CR3: 
>> >> >> 0002db810003 CR4: 00770ef0
>> >> >&g

Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume

[Floris Bruynooghe]

Hi Salvatore,

On Fri 16 Dec 2022 at 22:54 +0100, Salvatore Bonaccorso wrote:
> On Fri, Dec 16, 2022 at 10:34:08PM +0100, Floris Bruynooghe wrote:
>> On Fri 16 Dec 2022 at 21:50 +0100, Salvatore Bonaccorso wrote:
>> > On Fri, Dec 16, 2022 at 09:28:35PM +0100, Floris Bruynooghe wrote:
>> >> Package: src:linux
>> >> Version: 6.0.10-2
>> >> Severity: important
>> >> 
>> >> Dear Maintainer,
>> >> 
>> >> Since the 6.0.0-5 kernel the i915 graphics driver often fails on resume.
>> >> Downgrading to the 6.0.0-4 kernel fixes it and the driver works
>> >> flawlessly across resume, changing displays etc.
>> >> 
>> >> On the -5 kernel the following errors are observed when the driver
>> >> crashes:
>> >> 
>> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-9: PM: parent card0 
>> >> should not be sleeping
>> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-10: PM: parent card0 
>> >> should not be sleeping
>> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-11: PM: parent card0 
>> >> should not be sleeping
>> >> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: [drm] *ERROR* 
>> >> Sending link address failed with -5
>> >> Dec 13 11:26:58 fredriksen kernel: [ cut here ]
>> >> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: 
>> >> drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
>> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at 
>> >> drivers/gpu/drm/i915/display/intel_tc.c:711 int>
>> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm 
>> >> rfcomm cmac algif_hash algif_skcipher af_alg>
>> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic 
>> >> snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
>> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables 
>> >> autofs4 btrfs blake2b_generic libcrc32c>
>> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: 
>> >> kworker/u32:101 Not tainted 6.0.0-5-amd64 #1  Debian >
>> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 
>> >> 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
>> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound 
>> >> async_run_entry_fn
>> >> Dec 13 11:26:58 fredriksen kernel: RIP: 
>> >> 0010:intel_tc_port_sanitize+0x2d2/0x490 [i915]
>> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 
>> >> 2f e8 a7 44 42 e3 48 c7 c1 f8 a6 d6 c0>
>> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:a84dc5debc08 EFLAGS: 
>> >> 00010286
>> >> Dec 13 11:26:58 fredriksen kernel: RAX:  RBX: 
>> >> 9c812065 RCX: 
>> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0001 RSI: 
>> >> a4b7eeea RDI: 
>> >> Dec 13 11:26:58 fredriksen kernel: RBP:  R08: 
>> >> a5262260 R09: a5b5348a
>> >> Dec 13 11:26:58 fredriksen kernel: R10:  R11: 
>> >> 004a R12: 9c81101a2000
>> >> Dec 13 11:26:58 fredriksen kernel: R13: 9c8101f19900 R14: 
>> >>  R15: 9c81101a2000
>> >> Dec 13 11:26:58 fredriksen kernel: FS:  () 
>> >> GS:9c883f40() knlGS:
>> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS:  ES:  CR0: 
>> >> 80050033
>> >> Dec 13 11:26:58 fredriksen kernel: CR2: 55710e140b16 CR3: 
>> >> 0002db810003 CR4: 00770ef0
>> >> Dec 13 11:26:58 fredriksen kernel: PKRU: 5554
>> >> Dec 13 11:26:58 fredriksen kernel: Call Trace:
>> >> Dec 13 11:26:58 fredriksen kernel:  
>> >> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
>> >> Dec 13 11:26:58 fredriksen kernel:  
>> >> intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
>> >> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
>> >> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
>> >> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
>> >> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
>> >> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+

Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume

[Floris Bruynooghe]

Hi Salvatore,

On Fri 16 Dec 2022 at 21:50 +0100, Salvatore Bonaccorso wrote:

> Hi Floris,
>
> On Fri, Dec 16, 2022 at 09:28:35PM +0100, Floris Bruynooghe wrote:
>> Package: src:linux
>> Version: 6.0.10-2
>> Severity: important
>> 
>> Dear Maintainer,
>> 
>> Since the 6.0.0-5 kernel the i915 graphics driver often fails on resume.
>> Downgrading to the 6.0.0-4 kernel fixes it and the driver works
>> flawlessly across resume, changing displays etc.
>> 
>> On the -5 kernel the following errors are observed when the driver
>> crashes:
>> 
>> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-9: PM: parent card0 should 
>> not be sleeping
>> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-10: PM: parent card0 should 
>> not be sleeping
>> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-11: PM: parent card0 should 
>> not be sleeping
>> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: [drm] *ERROR* Sending 
>> link address failed with -5
>> Dec 13 11:26:58 fredriksen kernel: [ cut here ]
>> Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: 
>> drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
>> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at 
>> drivers/gpu/drm/i915/display/intel_tc.c:711 int>
>> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm rfcomm 
>> cmac algif_hash algif_skcipher af_alg>
>> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic 
>> snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
>> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables 
>> autofs4 btrfs blake2b_generic libcrc32c>
>> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: kworker/u32:101 
>> Not tainted 6.0.0-5-amd64 #1  Debian >
>> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 
>> 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
>> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound 
>> async_run_entry_fn
>> Dec 13 11:26:58 fredriksen kernel: RIP: 
>> 0010:intel_tc_port_sanitize+0x2d2/0x490 [i915]
>> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f 
>> e8 a7 44 42 e3 48 c7 c1 f8 a6 d6 c0>
>> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:a84dc5debc08 EFLAGS: 
>> 00010286
>> Dec 13 11:26:58 fredriksen kernel: RAX:  RBX: 
>> 9c812065 RCX: 
>> Dec 13 11:26:58 fredriksen kernel: RDX: 0001 RSI: 
>> a4b7eeea RDI: 
>> Dec 13 11:26:58 fredriksen kernel: RBP:  R08: 
>> a5262260 R09: a5b5348a
>> Dec 13 11:26:58 fredriksen kernel: R10:  R11: 
>> 004a R12: 9c81101a2000
>> Dec 13 11:26:58 fredriksen kernel: R13: 9c8101f19900 R14: 
>>  R15: 9c81101a2000
>> Dec 13 11:26:58 fredriksen kernel: FS:  () 
>> GS:9c883f40() knlGS:
>> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS:  ES:  CR0: 
>> 80050033
>> Dec 13 11:26:58 fredriksen kernel: CR2: 55710e140b16 CR3: 
>> 0002db810003 CR4: 00770ef0
>> Dec 13 11:26:58 fredriksen kernel: PKRU: 5554
>> Dec 13 11:26:58 fredriksen kernel: Call Trace:
>> Dec 13 11:26:58 fredriksen kernel:  
>> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  
>> intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
>> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
>> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
>> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
>> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+0x1a/0xe0 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  __intel_display_resume+0x1a/0xe0 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  intel_display_resume+0xfc/0x140 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  i915_drm_resume+0xba/0x130 [i915]
>> Dec 13 11:26:58 fredriksen kernel:  ? pci_pm_poweroff_noirq+0x100/0x100
>> Dec 13 11:26:58 fredriksen kernel:  dpm_run_callback+0x47/0x150
>> Dec 13 11:26:58 fredriksen kernel:  device_resume+0x88/0x190
>> Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
>> Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
>> Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
>> Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0

Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume

[Floris Bruynooghe]

nel:  device_resume+0x88/0x190
Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0x380
Dec 13 11:26:58 fredriksen kernel:  ? rescuer_thread+0x3a0/0x3a0
Dec 13 11:26:58 fredriksen kernel:  kthread+0xe6/0x110
Dec 13 11:26:58 fredriksen kernel:  ? kthread_complete_and_exit+0x20/0x20
Dec 13 11:26:58 fredriksen kernel:  ret_from_fork+0x1f/0x30
Dec 13 11:26:58 fredriksen kernel:  
Dec 13 11:26:58 fredriksen kernel: ---[ end trace  ]---
Dec 13 11:26:58 fredriksen kernel: i915 :00:02.0: [drm] *ERROR* Link 
Training Unsuccessful
Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to 
get ACT after 3000ms, last status: 00

Cheers,
Floris


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 21CBCTO1WW
product_version: ThinkPad X1 Carbon Gen 10
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N3AET67W (1.32 )
board_vendor: LENOVO
board_name: 21CBCTO1WW
board_version: Not Defined

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4621] (rev 02)
Subsystem: Lenovo Device [17aa:22e7]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P 
Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller 
[17aa:22e7]
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: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Alder Lake 
Innovation Platform Framework Processor Participant [8086:461d] (rev 02)
Subsystem: Lenovo Alder Lake Innovation Platform Framework Processor 
Participant [17aa:22e7]
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: proc_thermal_pci
Kernel modules: processor_thermal_device_pci

00:06.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI 
Express x4 Controller #0 [8086:464d] (rev 02) (prog-if 00 [Normal decode])
Subsystem: Lenovo 12th Gen Core Processor PCI Express x4 Controller 
[17aa:22e7]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:07.0 PCI bridge [0604]: Intel Corporation Alder Lake-P Thunderbolt 4 PCI 
Express Root Port #0 [8086:466e] (rev 02) (prog-if 00 [Normal decode])
Subsystem: Lenovo Alder Lake-P Thunderbolt 4 PCI Express Root Port 
[17aa:22e7]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:07.2 PCI bridge [0604]: Intel Corporation Alder Lake-P Thunderbolt 4 PCI 
Express Root Port #2 [8086:462f] (rev 02) (prog-if 00 [Normal decode])
Subsystem: Lenovo Alder Lake-P Thunderbolt 4 PCI Express Root Port 
[17aa:22e7]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 System peripheral [0880]: Intel Corporation 12th Gen Core Processor 
Gaussian & Neural Accelerator [8086:464f] (rev 02)
Subsystem: Lenovo 12th Gen Core Processor Gaussian & Neural Accelerator 
[17aa:22e7]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:0a.0 Signal processing controller [1180]: Intel Corporation Platform 
Monitoring Technology [8086:467d] (rev 01)
Subsystem: Lenovo Platform Monitoring Technology [17aa:22e7]
Control: I/O- Mem+ BusMaster- SpecCycl

Bug#919785: New version

[Floris Renaud]

Meanwhile, version 10.1 has been released.

Is it possible to modify the debian/watch file from
sourceforge (http://sourceforge.net/projects/yad-dialog/)
to
github (https://github.com/v1cont/yad)?

Bug#1003491: winetricks: Please allow co-installation with wine-staging

[Floris Renaud]

On Tuesday 11 January 2022 02:15:26 (+01:00), Unit 193 wrote:

> Package: winetricks
> Severity: wishlist
>
> Dear Maintainer,
>
> While it's a third-party repo and they should perhaps declare a provides 
on 'wine', even though it's installed in /opt, it would be very useful to 
have winetricks installed with wine-staging from winehq's repo.

>
>
> Thanks!
>
> ~Unit 193
> Unit193 @ Libera
> Unit193 @ OFTC
>

The winehq-staging package does provides 'wine'
(Note the 'hq' after wine)

dpkg -I winehq-staging_7.0_rc5_bookworm-1_amd64.deb 


 new Debian package, version 2.0.
 size 1936 bytes: control archive=708 bytes.
1086 bytes,19 lines  control  
   0 bytes, 0 lines  md5sums  
 Package: winehq-staging

 Source: wine-staging
 Version: 7.0~rc5~bookworm-1
 Architecture: amd64
 Maintainer: Rosanne DiMesio , Marcus Meissner 


 Installed-Size: 73
 Depends: wine-staging (= 7.0~rc5~bookworm-1)
 Conflicts: wine, wine-amd64, wine-i386
 Replaces: wine, wine-amd64, wine-i386, wine1.4, wine1.4-amd64, 
wine1.4-i386, wine1.5, wine1.5-amd64, wine1.5-i386, wine1.6, wine1.6-amd64, 
wine1.6-i386, wine1.7, wine1.7-amd64, wine1.7-i386, wine32, wine64


 Provides: wine, wine-amd64, wine-i386, wine1.4, wine1.4-amd64, 
wine1.4-i386, wine1.5, wine1.5-amd64, wine1.5-i386, wine1.6, wine1.6-amd64, 
wine1.6-i386, wine1.7, wine1.7-amd64, wine1.7-i386, wine32, wine64


 Section: otherosfs
 Priority: optional
 Description: WINE Is Not An Emulator - runs MS Windows programs
  Wine is a program which allows running Microsoft Windows programs
  (including DOS, Windows 3.x and Win32 executables) on Unix.
  .
  This compatibility package allows to use wine-staging system-wide as
  the default Wine version.
 Original-Maintainer: WineHQ Builds 

Bug#926037: systemd: localectl console keymap configuration delayed

[Floris Bos]

On 1/2/22 2:10 PM, Michael Biebl wrote:

On 02.01.22 13:32, Floris Bos wrote:
I recall in some cases it is also necessary to regenerate initramfs 
after a keyboard settings change.


E.g. when LUKS encryption is used and the user needs to be able to 
enter the password to unlock the disks in the console prior to the 
rest of the system being booted.


So just restarting one of the services actually may not be enough.


Well, I'm not yet convinced that doing this in localed is the correct 
place.
After all, if you run dpkg-reconfigure console-setup, it doesn't 
update the initramfs either, or does it?



It does on my Ubuntu box.

Not certain about upstream Debian.


--
Yours sincerely,

Floris Bos

Bug#926037: systemd: localectl console keymap configuration delayed

[Floris Bos]

On 1/2/22 12:01 PM, Michael Biebl wrote:

On 19.12.21 00:56, Floris Bos wrote:

Yes, your Debian specific stuff in 
debian/patches/debian/Use-Debian-specific-config-files.patch only 
seems to set /etc/default/keyboard


However with other Linux distributions the setting is also instantly 
applied to console, so that is what me and other users are expecting.



With other Linux distributions this seems to be done by restarting 
the systemd-vconsole-setup unit in src/local/localed.c 
vconsole_reload() :


https://github.com/systemd/systemd/blob/main/src/locale/localed.c#L97

Think that function needs to be patched by whatever is necessary to 
have the change do take effect on Debian (run "dpkg-reconfigure 
keyboard-configuration" and "setupcon -k --force" ?)


Currently we disable vconsole via debian/rules, so there is no 
systemd-vconsole-setup.service.


Maybe a fix could be as simple as shipping a symlink
systemd-vconsole-setup.service → keyboard-setup.service ?
Or do we need to restart console-setup.service as well?



I recall in some cases it is also necessary to regenerate initramfs 
after a keyboard settings change.


E.g. when LUKS encryption is used and the user needs to be able to enter 
the password to unlock the disks in the console prior to the rest of the 
system being booted.


So just restarting one of the services actually may not be enough.



Yours sincerely,


Floris Bos

Bug#926037: systemd: localectl console keymap configuration delayed

[Floris Bos]

Hi,


This issue is still present in recent Debian/Ubuntu versions.


> Am 30.03.19 um 18:11 schrieb Iiro Laiho:
> > When I set the system keymap using the "localectl" command, the

> > application of the new layout to the virtual consoles is delayed.


On Sun, 31 Mar 2019 20:23:09 +0200 Michael Biebl  wrote:

> TTBOMK, localectl just writes to /etc/default/keyboard and /etc/default

> /console-setup and leaves it up to console-setup to apply those changes,
> which is usually done during bootup.



Yes, your Debian specific stuff in 
debian/patches/debian/Use-Debian-specific-config-files.patch only seems 
to set /etc/default/keyboard


However with other Linux distributions the setting is also instantly 
applied to console, so that is what me and other users are expecting.



With other Linux distributions this seems to be done by restarting the 
systemd-vconsole-setup unit in src/local/localed.c vconsole_reload() :


https://github.com/systemd/systemd/blob/main/src/locale/localed.c#L97

Think that function needs to be patched by whatever is necessary to have 
the change do take effect on Debian (run "dpkg-reconfigure 
keyboard-configuration" and "setupcon -k --force" ?)




Yours sincerely,


Floris Bos

Bug#1001599: "x11vnc -auth guess" not working properly due to missing dependency on x11-utils

[Floris Bos]

Package: x11vnc


When x11vnc is started with "-auth guess" it runs a script that may call 
xdpyinfo.


This fails in cases the x11-utils package that provides xdpyinfo is not 
installed on the user's system.


Suggest a dependency on x11-utils is added to the x11vnc package.


Related to: https://github.com/LibVNC/x11vnc/issues/105

Bug#490848: 30 missing stable_copyright and stable_changelog files

[Floris Stoica]

Hello everyone,

Casually replying to a bug from 2008. Here's what I pieced together so far:

First of all security-master and ftp-master are two different servers. One 
handles security uploads and the other one handles other uploads. For a 
package's data to be synced to ftp-master, the package must first be approved.

The way everything is setup is by the way of mirroring, where ftp-master is 
setup as a mirror of security-master in the case of metadata. 

So what happens when approving a package?
We'll take this package as an example: https://packages.debian.org/stretch/vlc

A function named `_do_Approve()` is called from new_security_install.py that 
does the following:

1. Syncs package data with the security mirror, where it eventually calls:
sudo -u archvsync runmirrors ${pusharg} // pusharg='-a security'

This syncs the security mirror and the package data winds up here:
http://security.debian.org/debian-security/pool/updates/main/v/vlc/
vlc_3.0.11-0+deb9u2.dsc

This works as intended and is ok and implies that the next step is 
misconfigured.

2. Syncs package metadata with the metadata ftp-master mirror:

A script called `export.sh` is called that:
- creates the changelog data and exports it wherever the `changelog_url` path 
is set in the postgres database

I couldn't find if the security suite has a `changelog_url` set so this might 
be where it all comes down to. We'll keep this variable in mind for the next 
step.

- Rsyncs the exported changelog data into a public directory:
// edited for brevity
rsync ... ${exportdir}/changelogs/. ${exportpublic}/changelogs

If `exportdir` does not match with the `changelog_url` variable above then 
this also might prove to be the problem.

- Finally it notifies the mirror:
sudo -u archvsync runmirrors -a metasdo > ~dak/runmirrors-metadata.log 2>&1 &

If this step doesn't work, it implies that mirroring is misconfigured and might 
be simply a case of missing ssh keys or configuration between ftp-master and 
security-master.

If everything would run well, then the changelog should be present at:
https://metadata.ftp-master.debian.org/changelogs//main/v/vlc/
vlc_3.0.11-0+deb9u2_changelog


I don't have access to the servers or the database, so can anyone check the 
above and let us know where the problem lies?

Thanks,
Floris.

Bug#992069: libvkd3d-doc is not installable besides libvkd3d-dev

[Floris Renaud]

Package: libvkd3d-doc
Version: 1.2-5
Severity: important

Dear Maintainer,

sudo apt install libvkd3d-doc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
libvkd3d-doc
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/788 kB of archives.
After this operation, 2154 kB of additional disk space will be used.
(Reading database ... 365748 files and directories currently installed.)
Preparing to unpack .../libvkd3d-doc_1.2-5_all.deb ...
Unpacking libvkd3d-doc (1.2-5) ...
dpkg: error processing archive
/var/cache/apt/archives/libvkd3d-doc_1.2-5_all.deb (--unpack):
trying to overwrite '/usr/share/doc/libvkd3d-dev/ANNOUNCE.gz', which is 
also

in package libvkd3d-dev:i386 1.2-5
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libvkd3d-doc_1.2-5_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE not 
set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#992066: libvkd3d-headers: Package doesn't contain header files

[Floris Renaud]

Package: libvkd3d-headers
Version: 1.2-5
Severity: important

Dear Maintainer,

The libvkd3d-headers package does not contain any header files (for 
example,

vkd3d.h).

$ apt policy libvkd3d-headers
libvkd3d-headers:
Installed: 1.2-5
Candidate: 1.2-5
Version table:
*** 1.2-5 100
1 http://ftp.nl.debian.org/debian experimental/main amd64 Packages
1 http://ftp.nl.debian.org/debian experimental/main i386 Packages
100 /var/lib/dpkg/status
$ dpkg-query -L libvkd3d-headers
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libvkd3d-headers
/usr/share/doc/libvkd3d-headers/ANNOUNCE.gz
/usr/share/doc/libvkd3d-headers/AUTHORS
/usr/share/doc/libvkd3d-headers/README
/usr/share/doc/libvkd3d-headers/changelog.Debian.gz
/usr/share/doc/libvkd3d-headers/copyright



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE not 
set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

libvkd3d-headers depends on no packages.

Versions of packages libvkd3d-headers recommends:
ii libvkd3d-dev 1.2-5

libvkd3d-headers suggests no packages.

Bug#899623: *prod* Please fix omniorb-dfsg bug #899623?

[Floris Bruynooghe]

Hello,

On Sat 28 Mar 2020 at 17:28 +0100, Ivo De Decker wrote:
> On Sun, Mar 10, 2019 at 01:59:50PM +, Steve McIntyre wrote:
>> Hi guys,
>> 
>> I don't know if you've even seen this RC bug. Could you please update
>> the maintainer address to point to something that works?
>
> Any news on this? Are you still interested in maintaining omniorb-dfsg?
>
> The last maintainer upload was in 2015. Maybe this package should be orphaned
> instead?

Yes, this package should really be orphaned and possibly even removed
now if there are RC bugs and no dependencies for it.  I've never been a
DD myself only maintained this for a few years together with Thomas, but
AFAIK both me or Thomas have stopped maintaining this for years now.
IIRC I attempted to orphan this at some point, but it may never have had
the upload and svn seems gone by now too...

Apologies for not getting the state of the package correctly and the
extra work it causes you.

Cheers,
Floris

Bug#929410: RANDR extension not present

[Floris Bos]

Package: tigervnc-scraping-server

Version: 1.9.0+dfsg-3


Seems the tigervnc package is missing randr support.


==

$ x0tigervncserver -SecurityTypes none

Wed May 22 22:20:30 2019
 Geometry:    Desktop geometry is set to 1024x768+0+0
 XDesktop:    Using evdev codemap

 XDesktop:    XTest extension present - version 2.2
 XDesktop:    RANDR extension not present
 XDesktop:    Will not be able to handle session resize
 Main:    Listening on port 5900
^C

==


While my system/X server certainly has the RANDR extension:


==

$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 7680 x 7680
HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis 
y axis) 0mm x 0mm

   1024x768  60.00*
   800x600   60.32    56.25
   848x480   60.00
   640x480   59.94

==


Think you are missing a build dependeny on the libxrandr2 library.

If HAVE_XRANDR is not set at compile time, it always prints the message 
( 
https://github.com/TigerVNC/tigervnc/blob/master/unix/x0vncserver/XDesktop.cxx#L182 
)

Bug#928517: current symlink missing for jessie

[Floris Bos]

Package: mirrors


http://ftp.debian.org/debian/dists/jessie/main/installer-amd64/current/ 
no longer exists.


- It used to be there.

- "current" is still there for other Debian releases. (e.g. 
http://ftp.debian.org/debian/dists/stretch/main/installer-amd64/current/ )



We have some scripts that dedicated server providers use to provision 
servers in datacenters (PXE network installations), and those expect 
"current" to be there...




Yours sincerely,


Floris Bos

Bug#913007: cabextract: New upstream version

[floris]

Package: cabextract
Version: 1.6-1.1
Severity: important

Dear Maintainer,

There is a new version of cabextract (1.9). This version has a fix which is
necessary for winetricks.

Regression when extracting cabinets using "-F" option
https://github.com/Winetricks/winetricks/issues/1120

A bug introduced in cabextract 1.8 was fixed: using the --filter option gave
invisibly wrong results
https://www.cabextract.org.uk/#changes



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

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

Versions of packages cabextract depends on:
ii  libc6   2.27-8
ii  libmspack0  0.8-1

cabextract recommends no packages.

cabextract suggests no packages.

-- no debconf information

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[floris]

Andreas Beckmann schreef op 2018-06-25 17:38:

On 2018-06-24 11:49, floris wrote:


What about the following 
/etc/nvidia/current/nvidia-drm-outputclass.conf


---
Section "Files"
    ModulePath "/usr/lib/xorg/modules/linux"
    ModulePath "/usr/lib/xorg/modules"
EndSection

Section "OutputClass"
    Identifier "nvidia"
    MatchDriver    "nvidia-drm"
    Driver "nvidia"
EndSection
---

That seems to work for stable ... what about sid?


Andreas


Hmmm, this should work, but the NVidia glx module will always be 
loaded
for all screens by the xserver. This will break a multiseat system 
with

multiple gpu vendors and maybe other glvnd dispatch goodness.

Is the following situation a possibility?


We can consider such fancy setup for 396.xx and newer, since that will
change a lot anyway. For 390.xx I want to have a version in sid that 
can
be uploaded with minimal changes to stretch once the next CVE arrives 
...




I understand you ideally want one nvidia package for all Debian 
versions.


Stable -> nvidia-driver (up to version 390.xx in backports), 
compatible

with all versions of the xserver
 This version is shipped with a separate Files section in
nvidia-drm-outputclass.conf
 If xserver 1.20 is in backports, this version can be upgraded to 
match

the new Testing/Sid version

Testing and Sid -> nvidia-legacy-390xx-driver, xserver > 1.20
    -> nvidia-driver (version > 396.xx), xserver > 1.20
 These versions will have the ModulePath option in the OutputClass
section. (and we can drop the glx-alternative system)


Nope, we have to keep glx-alternatives around as long as 340xx is still
in the game.



Sorry, I forgot 340xx doesn't support glvnd

---
Floris

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[floris]

What about the following 
/etc/nvidia/current/nvidia-drm-outputclass.conf


---
Section "Files"
ModulePath "/usr/lib/xorg/modules/linux"
ModulePath "/usr/lib/xorg/modules"
EndSection

Section "OutputClass"
Identifier "nvidia"
MatchDriver"nvidia-drm"
Driver "nvidia"
EndSection
---

That seems to work for stable ... what about sid?


Andreas


Hmmm, this should work, but the NVidia glx module will always be loaded 
for all screens by the xserver. This will break a multiseat system with 
multiple gpu vendors and maybe other glvnd dispatch goodness.


Is the following situation a possibility?

Stable -> nvidia-driver (up to version 390.xx in backports), compatible 
with all versions of the xserver
 This version is shipped with a separate Files section in 
nvidia-drm-outputclass.conf
 If xserver 1.20 is in backports, this version can be upgraded to match 
the new Testing/Sid version


Testing and Sid -> nvidia-legacy-390xx-driver, xserver > 1.20
-> nvidia-driver (version > 396.xx), xserver > 1.20
 These versions will have the ModulePath option in the OutputClass 
section. (and we can drop the glx-alternative system)

---
Floris

Bug#900428: nvidia-driver: Drop the glx-alternative system.

[floris]

Package: nvidia-driver
Version: 390.59-1
Severity: wishlist

Dear Maintainer,

The new version of the Xserver (1.20) has support for a xorg.conf 
OutputClass section.

This makes the glx-alternative system obsolete.

The NVidia package could ship a nvidia.conf file in 
/usr/share/X11/xorg.conf.d


Section "OutputClass"
Identifier  "NVidia Modules"
MatchDriver "nvidia-drm"
Driver  "nvidia"
Option  "AllowEmtyInitialConfiguration"
ModulePath  "/usr/lib/nvidia"
EndSection

This will fix bug #900248
---
Floris

Bug#893574: Auto-suspend

[floris]

Simon McVittie schreef op 2018-03-29 11:55:

On Thu, 29 Mar 2018 at 10:43:00 +0200, floris wrote:
I found that gsd-power only monitors his/her seat. The suspend 
settings in
'gnome-control-center power' do work. When a user has set automatic 
suspend
to on, the computer will suspend even there is an active user on an 
other
seat. As a workaround I can disable the automatic suspend for all 
users, but

where can I change the suspend settings for Gdm3?


The gdm greeter has its own gnome-settings-demon, which can be 
configured

via /etc/gdm3/greeter.dconf-defaults in Debian. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893964#22

smcv


Thanks for pointing me to bug 893964. I think this bug is related and 
the workaround works.

---
Floris

Bug#893574: Auto-suspend

[floris]

I found that gsd-power only monitors his/her seat. The suspend settings 
in 'gnome-control-center power' do work. When a user has set automatic 
suspend to on, the computer will suspend even there is an active user on 
an other seat. As a workaround I can disable the automatic suspend for 
all users, but where can I change the suspend settings for Gdm3?

Bug#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

[floris]

Debian Bug Tracking System schreef op 2018-03-24 22:42:

This is an automatic notification regarding your Bug report
which was filed against the systemd package:

#893574: gnome-shell: Suspend after 20 minutes even there is activity 
on a seat


It has been closed by Simon McVittie <s...@debian.org>.

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 Simon McVittie
<s...@debian.org> by
replying to this email.



Sorry, I cheered too early.

After some testing I think gsd-power from gnome-settings-daemon is 
monitoring the state of each seat, but fails to check if another one is 
still active

(full log as attachment)

mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path 
/org/gnome/SessionManager/Client17

mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor

mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s 
<--- No user has a 20 minutes suspend setting in gnome-control-center 
power. Is this gdm3?


mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning 
callback 96 msec

mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
mrt 27 10:25:20 Jessica gsd-power[1568]: disabling server builtin 
screensaver: (xset s 0 0; xset s blank; xset s expose)
mrt 27 10:28:28 Jessica gsd-power[1568]: Received screensaver 
ActiveChanged signal: 1 (old: 0)
mrt 27 10:28:28 Jessica gsd-power[1568]: setting up blank callback for 
15s

mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep callback 1200s
mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep warning 
callback 96 msec

mrt 27 10:28:28 Jessica gsd-power[1568]: Doing a state transition: blank
mrt 27 10:28:28 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:28:29 Jessica gsd-power[1568]: idletime watch: blank (3)
mrt 27 10:28:29 Jessica gsd-power[1568]: Not going to 'less idle' mode 
blank (current: blank)
mrt 27 10:39:18 Jessica gsd-power[1568]: idletime watch: sleep-warning 
(5)
mrt 27 10:39:19 Jessica gsd-power[1568]: Doing a state transition: 
normal

mrt 27 10:39:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:39:34 Jessica gsd-power[1568]: Doing a state transition: blank
mrt 27 10:39:34 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:43:18 Jessica gsd-power[1568]: idletime watch: sleep (4)

mrt 27 10:43:18 Jessica gsd-power[1568]: Doing a state transition: sleep 
<-- Is gsd-power responsible for the sleep mode or only the messenger?


mrt 27 10:43:19 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:43:19 Jessica gsd-power[1568]: Removing suspend delay 
inhibitor

mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:43:29 Jessica gsd-power[1568]: Adding suspend delay inhibitor
mrt 27 10:43:29 Jessica gsd-power[1568]: Doing a state transition: 
normal

mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:43:29 Jessica gsd-power[1568]: System inhibitor fd is 14
mrt 27 10:43:29 Jessica gsd-power[1568]: idletime reset

I hope someone can point me in the right direction to find the source.

Floris-- Logs begin at Fri 2017-12-08 00:08:13 CET, end at Tue 2018-03-27 11:08:45 
CEST. --
mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1569]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1569]: Registered client at path 
/org/gnome/SessionManager/Client19
mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path 
/org/gnome/SessionManager/Client17
mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor
mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s
mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning callback 
96 msec
mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
mrt 27 10:23:19 Jessica gsd-power[1569]: Adding suspend delay inhibitor
mrt 27 10:23:19 Jessica gsd-power[1569]: setting up sleep callback 1200s
mrt 27 10:23:19 Jessica gsd-power[1569]: setting up sleep warning callback 
96 msec
mrt 27 10:23:19 Jessica gsd-power[1569]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1569]: System inhibitor fd is 13
mrt 27 10:23:25 Jessica gsd-power[1569]: Received session is active change: now 
inactive
mrt 27 10:23:30 Jessica gsd-power[1959]: Starting power manager
mrt 27 10:23:30 Jessica gsd-power[1959]: Registered client at path 
/org/gnome/SessionManager/Client15
mrt 27 10:23:32 Jessica gsd-power[1959]: Adding suspend delay inhibitor
mrt 27 10:23:32 Jessica gsd-power[1959]: setting up sleep callback 900s
mrt 27 10:23:32 Jessica gsd-power[1959]: settin

Bug#893574: fixed in systemd 238-3

[floris]

Sorry this was not a Gnome bug. The update from systemd 238-2 to 238-3 
fixed this bug.


---
Floris

Bug#893574: More information

[floris]

More information about this issue.

Nobody is logged in seat1. Only the gdm3 login screen. An user is logged 
in on seat0
- Change a /org/gnome/settings-daemon/plugins/power/sleep-inactive-... 
dconf key

This doesn't change anything. System suspend after 20 minutes.

- Disable sleep/ suspend/ hibernation with: sudo systemctl mask 
sleep.target suspend.target hibernate.target hybrid-sleep.target
The user on seat0 is logged out? Or the session is removed after 20 
minutes.



When a user is logged in on both seats the computer stays awake.

---
Floris

Bug#893574: gnome-shell: Suspend after 20 minutes even there is activity on a seat

[floris]

Package: gnome-shell
Version: 3.28.0-1
Severity: important

Dear Maintainer,

Since version 3.27.90 the default action is to suspend after 20 minutes of
inactivity. Unfortunately, the system also suspend when there is activity on a
seat while the other is idle.

   * What led up to the situation?

create a multiseat setup with the "loginctl attach seat1" command

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

Leave seat1 on the gdm3 login screen and go away.
Login on seat0 and play.

   * What was the outcome of this action?

The system go to sleep after 20 minutes

   * What outcome did you expect instead?

The system stays awake

When both seats are active the system doesn't go to sleep.

journalctl
mrt 20 00:42:21 Jessica gnome-shell[1403]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica kernel: PM: suspend entry (deep)
mrt 20 00:42:21 Jessica gnome-shell[3700]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
sleep: sleep requested (sleeping: no  enabled: yes)
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
NetworkManager state is now ASLEEP
mrt 20 00:42:21 Jessica systemd[1]: Reached target Sleep.
mrt 20 00:42:21 Jessica systemd[1]: Starting Suspend...
mrt 20 00:42:21 Jessica systemd-sleep[6914]: Suspending system...

See also Gnome bug 681869 https://bugzilla.gnome.org/show_bug.cgi?id=681869



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  evolution-data-server3.26.5-2
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.28.0-1
ii  gir1.2-freedesktop   1.56.0-1
ii  gir1.2-gcr-3 3.28.0-1
ii  gir1.2-gdesktopenums-3.0 3.28.0-1
ii  gir1.2-gdm-1.0   3.28.0-1
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.56.0-1
ii  gir1.2-gnomebluetooth-1.03.28.0-2
ii  gir1.2-gnomedesktop-3.0  3.28.0-1
ii  gir1.2-gtk-3.0   3.22.29-1
ii  gir1.2-gweather-3.0  3.28.0-2
ii  gir1.2-ibus-1.0  1.5.17-3
ii  gir1.2-mutter-2  3.28.0-2
ii  gir1.2-nm-1.01.10.6-2
ii  gir1.2-nma-1.0   1.8.10-2
ii  gir1.2-pango-1.0 1.40.14-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.20-2
ii  gir1.2-soup-2.4  2.62.0-1
ii  gir1.2-upowerglib-1.00.99.7-2
ii  gjs  1.52.0-1
ii  gnome-backgrounds3.28.0-1
ii  gnome-settings-daemon3.28.0-1
ii  gnome-shell-common   3.28.0-1
ii  gsettings-desktop-schemas3.28.0-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-2
ii  libcairo21.15.10-2
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libecal-1.2-19   3.26.5-2
ii  libedataserver-1.2-223.26.5-2
ii  libgcr-base-3-1  3.28.0-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgirepository-1.0-11.56.0-1
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.52.0-1
ii  libglib2.0-0 2.56.0-2
ii  libglib2.0-bin   2.56.0-2
ii  libgstreamer1.0-01.12.4-1
ii  libgtk-3-0   3.22.29-1
ii  libical3 3.0.1-5
ii  libjson-glib-1.0-0   1.4.2-3
ii  libmutter-2-03.28.0-2
ii  libnm0   1.10.6-2
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpolkit-agent-1-0  0.105-18
ii  

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

[Floris Bos]

On 01/25/2018 05:54 PM, Ryan Tandy wrote:


Nor an option to simply not move the thing, but delete it. We already 
have a dump of it, right?


Not sure. We have a dump of the config, but I don't think it dumps the 
data, does it?


That's pretty confusing as well.

You are right, in this case it only seems to have copied configuration 
to dump_database_destdir
While the documentation suggests that directory is meant to dump the 
whole database to on upgrades:


==
Template: slapd/dump_database
Type: select
__Choices: always, when needed, never
Default: when needed
_Description: Dump databases to file on upgrade:
 Before upgrading to a new version of the OpenLDAP server, the data from
 your LDAP directories can be dumped into plain text files in the
 standard LDAP Data Interchange Format.
 .
 Selecting "always" will cause the databases to be dumped
 unconditionally before an upgrade. Selecting "when needed" will only
 dump the database if the new version is incompatible with the old
 database format and it needs to be reimported. If you select "never",
 no dump will be done.

Template: slapd/dump_database_destdir
Type: string
Default: /var/backups/slapd-VERSION
_Description: Directory to use for dumped databases:
 Please specify the directory where the LDAP databases will be exported.
 In this directory, several LDIF files will be created which correspond
 to the search bases located on the server. Make sure you have enough
 free space on the partition where the directory is located. The first
 occurrence of the string "VERSION" is replaced with the server version
 you are upgrading from.

==

This can confuse unwitting users into thinking they do have a backup of 
everything, as the directory do is filled with .ldif files.



Yours sincerely,

Floris Bos

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

[Floris Bos]

Hi,

On 01/25/2018 05:54 PM, Ryan Tandy wrote:

On Thu, Jan 25, 2018 at 05:05:27PM +0100, Floris Bos wrote:

I am not seeing any easy option to prevent this from happening.


Removing the existing backup first isn't easy enough?


If you can guarantee us that the name of the folder we would need to 
delete is always /var/backups/unknown-2.4.44+dfsg-5+deb9u1.ldapdb -even 
in future package updates- that is a possibility.

However would prefer not to make assumptions like that :-)




There is a preseed option (slapd/dump_database_destdir) to change the 
backup directory the database dump goes to, but that doesn't seem to 
affect the directory the old folder is moved to.


Oh, really? If I understand you correctly, that sounds like a second 
bug - not respecting destdir for that location?


It is respecting it for the destination of the database dump.
But in addition to making a database dump, it also wants to move the 
original folder to /var/backups, and I do not see any option to change 
that destination.


==
# echo "slapd slapd/dump_database_destdir string 
/var/backups/just-testing" | debconf-set-selections

# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure slapd
  Backing up /etc/ldap/slapd.d in /var/backups/just-testing... done.
  Moving old database directory to /var/backups:

  Backup path /var/backups/unknown-2.4.44+dfsg-5+deb9u1.ldapdb exists. 
Giving up...

==


Yours sincerely,

Floris Bos

Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

[Floris Bos]

Package: slapd
Version: 2.4.44+dfsg-5+deb9u1


Hi,

Currently "dpkg-reconfigure slapd" wants to move the old database 
directory to /var/backups
However this fails if there already exists such a directory in 
/var/backups from a previous run.


==
# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure slapd
  Backing up /etc/ldap/slapd.d in 
/var/backups/slapd-2.4.44+dfsg-5+deb9u1... done.

  Moving old database directory to /var/backups:

  Backup path /var/backups/unknown-2.4.44+dfsg-5+deb9u1.ldapdb exists. 
Giving up...

==

I am not seeing any easy option to prevent this from happening.
There is a preseed option (slapd/dump_database_destdir) to change the 
backup directory the database dump goes to, but that doesn't seem to 
affect the directory the old folder is moved to.
Nor an option to simply not move the thing, but delete it. We already 
have a dump of it, right?



Yours sincerely,

Floris Bos

Bug#888426: certtool has year 2k38 problem, giving problems for scripts that generate 20 year certs today

[Floris Bos]

Package: gnutls-bin
Version: 3.5.8-5+deb9u3
Severity: important


Hi,

Seems certtool (at least the version shipped with Debian Stretch) has a 
year 2038 problem on 32-bit architectures.
We have a program that generates SSL certificates with 20 year validity 
for communication within an internal network, and it started failing today.


To reproduce (on i386 arch):

==
$ certtool --generate-privkey --outfile test.key
Generating a 3072 bit RSA private key...
$ cat >test.tpl <$ certtool --generate-self-signed --load-privkey test.key --template 
test.tpl

Generating a self signed certificate...
Overflow while parsing days
==


Does work if setting date backwards to yesterday.

==
$ sudo date --set '2018-1-24'
Wed 24 Jan 00:00:00 GMT 2018
$ certtool --generate-self-signed --load-privkey test.key --template 
test.tpl

Generating a self signed certificate...
X.509 Certificate Information:
    Version: 3
    Serial Number (hex): 5a67cc853834650f7069e6eb
    Validity:
    Not Before: Wed Jan 24 00:00:05 UTC 2018
    Not After: Thu Dec 31 23:23:23 UTC 2037
[...]
==


Yours sincerely,

Floris Bos

Bug#568577: Please provide pam-auth-update rule for pam_mkhomedir

[Floris Bos]

On 02/05/2010 11:25 PM, Petter Reinholdtsen wrote:

Package:  libpam-runtime
Version:  1.1.1-1
Severity: wishlist
File: /usr/sbin/pam-auth-update
Tags: patch
User: debian-...@lists.debian.org
UserTags: debian-edu

It would be nice if the pam_mkhomedir module was handled by
pam-auth-update, to allow it to be enabled during installation using
preseeding.  It is useful when setting up system loading home
directories from windows servers.  Here is a proposal for the content
to put in /usr/share/pam-configs/mkhomedir, based on the setup
provided for windows users with windows home directories.


Any update on this bug?
Meanwhile downstream distributions like Ubuntu did add 
/usr/share/pam-configs/mkhomedir to their libpam-runtime package.


And it is kinda annoying to have Debian and Ubuntu behave differently, 
if you are writing scripts that are supposed to work on both.



Yours sincerely,

Floris Bos

Bug#885127: vlc: Cast Chromecast unusable due to gnutls error

[Floris]

Op Fri, 29 Dec 2017 22:48:30 +0100 schreef Daniel Kahn Gillmor  
<d...@debian.org>:



On Tue 2017-12-26 22:24:59 +0100, Floris wrote:
I'm not sure this is a VLC bug, although I think it is odd that VLC 3  
has

a Chromecast feature, but it isn't working. Maybe build vlc without
Chromecast support in Debian until Google and/ or GnuTLS has a decent  
fix

for this issue. Or make a workaround.


Dropping chromecast support in debian doesn't seem like great option to
me if it's available upstream.  And GnuTLS has at least two different
fixes available.

One approach (as noted in my earlier post on this bug report) is to
explicitly grant that self-signed cert root CA status.  But that's
generally unpleasant, because it means that cert can MITM any of your
other connections.

A better approach to connecting to a persistently-named, self-signed
chromecast stream would be for VLC to take advantage of GnuTLS's "TOFU"
(trust on first use) functionality:

https://gnutls.org/manual/gnutls.html#Certificate-verification

or, if we already know that chromecast is never a strongly-secured
connection, we could just disable authentication on chromecast
connections (i do not have a chromecast, and i do not know what security
posture chromecast users expect from their connections).

hth,

--dkg



I think a lot of end users expect the "it just works" method. When you  
cast something from Chrome/ Chromium to the Chromecast there isn't a  
warning about a certificate. In addition, the certificate issued by the  
chromecast is only valid for 2 days. Does it mean that you get a new  
warning every two days? So I tend more to the last option.


gnutls-cli 192.168.1.14:8009
Processed 149 CA certificate(s).
Resolving '192.168.1.14:8009'...
Connecting to '192.168.1.14:8009'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
 - subject `CN=c036e8e6-dce8-c593-4624-e743f8eb7f04', issuer  
`CN=c036e8e6-dce8-c593-4624-e743f8eb7f04', serial 0x07b58554, RSA key 2048  
bits, signed using RSA-SHA256, activated `2017-12-29 09:57:32 UTC',  
expires `2017-12-31 09:57:32 UTC',  
pin-sha256="lqW7HJ396wf5w02vBO0Oyu3Os05S7OKUunht17mBwQE="

Public Key ID:
sha1:6b30af9317dcec5b8f16671aff24ccfa8af38bd4

sha256:96a5bb1c9dfdeb07f9c34daf04ed0ecaedceb34e52ece294ba786dd7b981c101
Public Key PIN:
pin-sha256:lqW7HJ396wf5w02vBO0Oyu3Os05S7OKUunht17mBwQE=
Public key's random art:
+--[ RSA 2048]+
| |
| |
| |
| |
|  o.So   |
|   +o.o.ooo  |
|   .+o. EB+ .|
|  oo..o+o+.o |
|  .o  +=*+o..|
+-+

- Status: The certificate is NOT trusted. The certificate issuer is  
unknown. The certificate chain uses insecure algorithm. The name in the  
certificate does not match the expected.

*** PKI verification of server certificate failed...
*** Fatal error: Error in the certificate.
*** handshake has failed: Error in the certificate.

Bug#885127: Workaround

[Floris]

To accept the Chromecast certificate:
1. Get the certificate with gnutls-cli
$ gnutls-cli --save-cert=chromecast.pem 192.168.1.14:8009

2. Start VLC with the --gnutls-dir-trust option
$ vlc -vv --gnutls-dir-trust=/home/floris  
--sout="#chromecast{ip=192.168.1.14}" 


3. A pop-up window appears with a "Insecure site" warning. Here you can  
accept the certificate.

Bug#885127: vlc: Cast Chromecast unusable due to gnutls error

[Floris]

Apparently, on a windows machine you get a "trust this certificate"  
pop-up

window and you are able to import the chromecast certificate.


That popup also exists in Linux. But it is not adequate to handle  
insecure

algorithms, only unknown or mismatched certificates.


In Debian
there isn't such window. How to accept the chromecast certificate?


The TLS support within VLC is identical for Windows and Linux. The  
difference
is the Windows version ships an older version of GnuTLS, than that in  
Debian.
Presumably, the server is using SHA-1 certificate signatures - which are  
being

phased out industry-wide, and no longer accepted by newer GnuTLS version.

I don't see how this is a VLC bug. It's actually working as intended. If  
you

think the diagnostic is wrong, then it's a problem with GnuTLS.



I'm not sure this is a VLC bug, although I think it is odd that VLC 3 has  
a Chromecast feature, but it isn't working. Maybe build vlc without  
Chromecast support in Debian until Google and/ or GnuTLS has a decent fix  
for this issue. Or make a workaround.

Bug#885127: vlc: Cast Chromecast unusable due to gnutls error

[floris]

-sse' '--disable-neon' 
'--disable-altivec' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/vlc-wexCJw/vlc-3.0.0~rc2=. -fstack-protector-strong 
-Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g -O2 
-fdebug-prefix-map=/build/vlc-wexCJw/vlc-3.0.0~rc2=. -fstack-protector-strong 
-Wformat -Werror=format-security ' 'OBJCFLAGS=-g -O2 
-fdebug-prefix-map=/build/vlc-wexCJw/vlc-3.0.0~rc2=. -fstack-protector-strong 
-Wformat -Werror=format-security'
[55f7c57bc1a0] main libvlc debug: searching plug-in modules
[55f7c57bc1a0] main libvlc debug: loading plugins cache file 
/usr/lib/x86_64-linux-gnu/vlc/plugins/plugins.dat
[55f7c57bc1a0] main libvlc debug: recursively browsing 
`/usr/lib/x86_64-linux-gnu/vlc/plugins'
[55f7c57bc1a0] main libvlc debug: plug-ins loaded: 515 modules
[55f7c57bc1a0] main libvlc debug: opening config file 
(/home/floris/.config/vlc/vlcrc)
[55f7c57bc4f0] main logger debug: looking for logger module matching "any": 
4 candidates
[55f7c57bc4f0] main logger debug: using logger module "console"
[55f7c57bc1a0] main libvlc debug: translation test: code is "nl"
[55f7c57bd300] main keystore debug: looking for keystore module matching 
"memory": 4 candidates
[55f7c57bd300] main keystore debug: using keystore module "memory"
[55f7c57bc1a0] main libvlc debug: CPU has capabilities MMX MMXEXT SSE SSE2 
SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 FPU 
[55f7c5859d30] main input debug: Creating an input for 'Mediabibliotheek'
[55f7c5859d30] main input debug: Input is a meta file: disabling unneeded 
options
[55f7c5859d30] main input debug: using timeshift granularity of 50 MiB
[55f7c5859d30] main input debug: using default timeshift path
[55f7c5859d30] main input debug: 
`file/directory:///home/floris/.local/share/vlc/ml.xspf' gives access `file' 
demux `directory' path `/home/floris/.local/share/vlc/ml.xspf'
[55f7c585f370] main input source debug: creating demux: access='file' 
demux='directory' location='/home/floris/.local/share/vlc/ml.xspf' 
file='/home/floris/.local/share/vlc/ml.xspf'
[55f7c585f4f0] main demux debug: looking for access_demux module matching 
"file": 17 candidates
[55f7c585f4f0] main demux debug: no access_demux modules matched
[55f7c5879950] main stream debug: creating access: 
file:///home/floris/.local/share/vlc/ml.xspf
[55f7c5879950] main stream debug:  (path: 
/home/floris/.local/share/vlc/ml.xspf)
[55f7c5879950] main stream debug: looking for access module matching 
"file": 28 candidates
[55f7c5879950] main stream debug: using access module "filesystem"
[55f7c587a8e0] main stream debug: looking for stream_filter module matching 
"prefetch,cache_read": 26 candidates
[55f7c587a8e0] cache_read stream debug: Using stream method for AStream*
[55f7c587a8e0] cache_read stream debug: starting pre-buffering
[55f7c587a8e0] cache_read stream debug: received first data after 0 ms
[55f7c587a8e0] cache_read stream debug: pre-buffering done 299 bytes in 0s 
- 10428 KiB/s
[55f7c587a8e0] main stream debug: using stream_filter module "cache_read"
[55f7c587baa0] main stream debug: looking for stream_filter module matching 
"any": 26 candidates
[55f7c587baa0] playlist stream debug: using XSPF playlist reader
[55f7c587baa0] main stream debug: using stream_filter module "playlist"
[55f7c587baa0] main stream debug: stream filter added to 0x55f7c587a8e0
[55f7c587efb0] main stream debug: looking for stream_filter module matching 
"any": 26 candidates
[55f7c587efb0] main stream debug: no stream_filter modules matched
[55f7c587efb0] main stream_directory debug: looking for stream_directory 
module matching "any": 1 candidates
[55f7c587efb0] main stream_directory debug: no stream_directory modules 
matched
[55f7c585f370] main input source debug: attachment of directory-extractor 
failed for file:///home/floris/.local/share/vlc/ml.xspf
[55f7c5882e10] main stream debug: looking for stream_filter module matching 
"record": 26 candidates
[55f7c5882e10] main stream debug: using stream_filter module "record"
[55f7c585f370] main input source debug: creating demux: access='file' 
demux='directory' location='/home/floris/.local/share/vlc/ml.xspf' 
file='/home/floris/.local/share/vlc/ml.xspf'
[55f7c5883610] main demux debug: looking for demux module matching 
"directory": 55 candidates
[55f7c5883610] main demux debug: using demux module "directory"
[55f7c5884070] main demux meta debug: looking for meta reader module 
matching "any": 2 candidates
[55f7c5884070] lua demux meta debug: Trying Lua scripts in 
/home/floris/.local/share/vlc/lua/meta/reader
[55f7c5884070

Bug#840804: chrome-gnome-shell: does not work with Google Chrome

[Floris]

Let's wait and hope to see the blocking bug (#840235) come to a  
conclusion.


Bug 840235 is solved!

Hopefully chrome-gnome-shell can be updated.


Floris

Bug#862225: pam_mount mounts using old password when a password change is forced on login

[Floris Bos]

On 06/26/2017 08:53 AM, Jochen Sprickerhof wrote:

Hi Floris,

Thanks for the bug report, I plan to add it in the next release.

* Floris Bos <b...@je-eigen-domein.nl> [2017-05-10 00:38]:

passwordoptionalpam_mount.so
disable_interactive

Is there any reason for the disable_interactive?


Without it, it prompted for password.
Not sure why it did that.

--
Yours sincerely,

Floris Bos

Bug#862225: pam_mount mounts using old password when a password change is forced on login

[Floris Bos]

Package: libpam-mount

Version: 2.14-1.1



I have a setup where client computers run Debian Jessie and use:


- libpam-ldapd for authentication
- libpam-mount to mount a remote home directory through sshfs, using the 
login password entered by the user. The remote server uses the same ldap 
server for authentication.



Normally works.

However if the user's password has expired, and he is forced to change 
it straight away on login, libpam-mount fails to mount the home directory.


It tries to login to the remote server with the old password, instead of 
the changed new one.



It seems the Debian package only adds libpam-mount to 
/etc/pam.d/common-auth (to capture the entererd password), and 
/etc/pam.d/common-session (where it uses the earlier captured password 
to do the actual mount).


However to be able to capture the new password on forced password 
changes on login, it should also be added to /etc/pam.d/common-password



Adding the following line there seems to fix it for me:


passwordoptionalpam_mount.so 
disable_interactive




--
Yours sincerely,

Floris Bos

Bug#802335: gdm3: gdm 3.18 does not switch to the right tty with a multi seat setup

[Floris]

Op Sun, 29 May 2016 13:22:43 +0200 schreef Laurent Bigonville  
<bi...@debian.org>:



tag 802335 + moreinfo
thanks

On Mon, 19 Oct 2015 18:20:30 +0200 floris <deb...@jkfloris.demon.nl>  
wrote:


 > Dear Maintainer,

Hi,

 > * What led up to the situation?
 >
 > Updating to gdm 3.18 with apt-get dselect-upgrade
 >
 > * What exactly did you do (or not do) that was effective (or
 > ineffective)?
 >
 > Purged all nvidia packages. Removed all 72-* files in  
/etc/udev/rules.d

 > Boot with only the nouveau modules.
 > Installed nvidia-kernel-dkms.
 > Reboot
 > Create the multi seat with:
 > $sudo loginctl attach seat1 /sys/devices/.../drm/card1
 > $sudo loginctl attach seat1 /sys/devices/.../usb1/1-1/1-1.4/
 > $sudo loginctl attach seat1 /sys/devices/.../sound/card1/
 > Reboot
 >
 > * What was the outcome of this action?
 > After logging in with gdm3 the screen remains gray (background of  
gdm3)

 >
 > * What outcome did you expect instead?
 > Gdm3 redirects me directly to the desktop. Now I have to press  
Ctrl-Alt-F2 to

 > get to my desktop.

Could you please try again with the last version of the gdm3 package?

I think this might actually be fixed.

Cheers,

Laurent Bigonville


You are right this bug is fixed.

Thanks,

Floris

Bug#804547: [nvidia-driver] Outdated nvidia drivers

[Floris]

Op Tue, 26 Apr 2016 09:03:00 +0200 schreef Peter Keel  
<bugzi...@discordia.ch>:



Yes, can we at least have a statement/explanation what to do?

- Do we need to install X from experimental in order to be able
to install newer nvidia-drivers? (because of ABI changes?)

- All the drivers in debian are outdated. Stable driver is 364.19
http://www.nvidia.co.uk/download/driverResults.aspx/101848/en-uk
what's the plan there? Do you still plan to release another one
or two outdated drivers (358, 361) first, after the other outdated
driver (355) migrates from experimental to unstable?

Thank you for your clarifications/outlying of your plans.

Peter


There is a statement:
https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012918.html

the alternative is build the packages yourself:
https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012917.html

Please build the packages and report all the issues you have, so the  
maintainers can make a stable package.


Success,

Floris

Bug#803779: Same behavior

[Floris]

I can confirm this bug.

See also bug 802335
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802335

Floris

Bug#804073: nvidia-detect: Does not work with multiple Nvidia cards

[Floris]

Op Thu, 05 Nov 2015 13:50:42 +0100 schreef Andreas Beckmann  
<a...@debian.org>:



On 2015-11-04 21:54, Floris wrote:
I made a little modification to the nvidia-detect script. Now it can  
check

multiple cards. The only problem is it can report two different versions
to the user.


I applied your patch with slight modifications, could you check again?
I also added support for passing multiple PCI IDs on the command line,
that simplifies testing (and revealed a bug, VERSIONS was not being  
reset).

For the problematic case, let's wait for someone to complain and provide
a patch, I'm not sure what would be the right recommendation in that  
case.



Andreas



The 5794 SVN version works for me.


Thanks,

floris

Bug#804073: nvidia-detect: Does not work with multiple Nvidia cards

[Floris]

Op Wed, 04 Nov 2015 19:29:05 +0100 schreef Andreas Beckmann  
<a...@debian.org>:



On 2015-11-04 18:00, floris wrote:

$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92  
[GeForce GTS

250] [10de:0615] (rev a2)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119  
[GeForce GT

610] [10de:104a] (rev a1)
Several NVIDIA GPUs detected. Checking only the first.
Usage: lspci []


Fixed in SVN.
Without a multi-gpu system available this code path was untested until
now ...


Andreas


I made a little modification to the nvidia-detect script. Now it can check
multiple cards. The only problem is it can report two different versions
to the user.

floris

nvidia-detect
Description: Binary data

Bug#804073: nvidia-detect: Does not work with multiple Nvidia cards

[Floris]

Op Wed, 04 Nov 2015 19:29:05 +0100 schreef Andreas Beckmann  
<a...@debian.org>:



On 2015-11-04 18:00, floris wrote:

$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92  
[GeForce GTS

250] [10de:0615] (rev a2)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119  
[GeForce GT

610] [10de:104a] (rev a1)
Several NVIDIA GPUs detected. Checking only the first.
Usage: lspci []


Fixed in SVN.
Without a multi-gpu system available this code path was untested until
now ...


Andreas


I confirm that the  SVN version is fixed.

Thanks,

floris

Bug#802335: more information

[Floris]

I found a strange situation:

- Boot the computer
- gdm3 is shown on both seats
- login on seat0 with user "floris"
The screen remains grey
- login on seat1 with user "eugenie"

Both seats load Gnome successfully


Here is the output of journalctl:
http://www.jkfloris.dds.nl/gdm-login.txt


Can someone tell me why Gnome is not loaded on seat0 after the first login?

Bug#802335: gdm3: gdm 3.18 does not switch to the right tty with a multi seat setup

[floris]

Package: gdm3
Version: 3.18.0-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

Updating to gdm 3.18 with apt-get dselect-upgrade

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

Purged all nvidia packages. Removed all 72-* files in /etc/udev/rules.d
Boot with only the nouveau modules.
Installed nvidia-kernel-dkms.
Reboot
Create the multi seat with:
$sudo loginctl attach seat1 /sys/devices/.../drm/card1
$sudo loginctl attach seat1 /sys/devices/.../usb1/1-1/1-1.4/
$sudo loginctl attach seat1 /sys/devices/.../sound/card1/
Reboot

   * What was the outcome of this action?
After logging in with gdm3 the screen remains gray (background of gdm3)

   * What outcome did you expect instead?
Gdm3 redirects me directly to the desktop. Now I have to press Ctrl-Alt-F2 to
get to my desktop.


The following sessions are active after logging in on one seat
$ loginctl show-session 4
Id=4
User=1000
Name=floris
Timestamp=ma 2015-10-19 17:52:05 CEST
TimestampMonotonic=677389926
VTNr=2
Seat=seat0
TTY=/dev/tty2
Remote=no
Service=gdm-password
Scope=session-4.scope
Leader=2688
Audit=4
Type=x11
Class=user
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1445269252232047
IdleSinceHintMonotonic=4202176

$ loginctl show-session c2
Id=c2
User=111
Name=Debian-gdm
Timestamp=ma 2015-10-19 17:40:55 CEST
TimestampMonotonic=7433209
VTNr=0
Seat=seat1
Display=:0
Remote=no
Service=gdm-launch-environment
Scope=session-c2.scope
Leader=1027
Audit=0
Type=x11
Class=greeter
Active=no
State=closing
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

$ loginctl show-session c3
Id=c3
User=111
Name=Debian-gdm
Timestamp=ma 2015-10-19 17:40:56 CEST
TimestampMonotonic=8296081
VTNr=7
Seat=seat0
TTY=/dev/tty7
Remote=no
Service=gdm-launch-environment
Scope=session-c3.scope
Leader=1121
Audit=0
Type=x11
Class=greeter
Active=no
State=online
IdleHint=yes
IdleSinceHint=1445269582227681
IdleSinceHintMonotonic=334197809

$ loginctl show-session c4
Id=c4
User=111
Name=Debian-gdm
Timestamp=ma 2015-10-19 17:46:16 CEST
TimestampMonotonic=328096979
VTNr=0
Seat=seat1
Display=:3
Remote=no
Service=gdm-launch-environment
Scope=session-c4.scope
Leader=2411
Audit=0
Type=x11
Class=greeter
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1445269881684407
IdleSinceHintMonotonic=633654536

$ loginctl show-seat seat0
Id=seat0
ActiveSession=4
CanMultiSession=yes
CanTTY=yes
CanGraphical=yes
Sessions=4 c3
IdleHint=yes
IdleSinceHint=1445269582227681
IdleSinceHintMonotonic=334197809

$ loginctl show-seat seat1
Id=seat1
ActiveSession=c4
CanMultiSession=no
CanTTY=no
CanGraphical=yes
Sessions=c4 c2
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0




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

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

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.40-3
ii  adduser   3.113+nmu3
ii  dconf-cli 0.24.0-2
ii  dconf-gsettings-backend   0.24.0-2
ii  debconf [debconf-2.0] 1.5.57
ii  gir1.2-gdm3   3.18.0-2
ii  gnome-session [x-session-manager] 3.18.0-1
ii  gnome-session-bin 3.18.0-1+b1
ii  gnome-settings-daemon 3.18.1-1+b1
ii  gnome-shell   3.18.0-1
ii  gnome-terminal [x-terminal-emulator]  3.18.1-1
ii  gsettings-desktop-schemas 3.18.0-1
ii  libaccountsservice0   0.6.40-3
ii  libaudit1 1:2.4.4-4
ii  libc6 2.19-22
ii  libcanberra-gtk3-00.30-2.1
ii  libcanberra0  0.30-2.1
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libgdm1   3.18.0-2
ii  libglib2.0-0  2.46.1-1
ii  libglib2.0-bin2.46.1-1
ii  libgtk-3-03.18.2-1
ii  libpam-modules1.1.8-3.1
ii  libpam-runtime1.1.8-3.1
ii  libpam-systemd227-2
ii  libpam0g  1.1.8-3.1
ii  librsvg2-common   2.40.11-1
ii  libselinux1   2.3-2+b1
ii  libsystemd0   227-2
ii  libwrap0  7.6.q-25
ii  libx11-6  2:1.6.3-1
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.2-1
ii  lsb-base  9.20150917
ii  metacity [x-window-manager]   1:3.18.1-1
ii  mutter [x-window-manager] 3.18.0-1+b1
ii  policykit-1

Bug#801749: gdm3: Does not start anymore

[Floris]

Same problem here. Updating gdm3 to 3.18 results in a flickering screen.  
(the X server is started over and over again)

The output of journalctl -b is here:
http://www.jkfloris.dds.nl/gdm3-update

After downgrading to 3.14 (testing) gdm3 does show the login prompt, but  
gnome does not load.


Output journalctl -b:
http://www.jkfloris.dds.nl/gdm3.14

So back to gnome 3.14

floris

Bug#778620: systemd: Add less to suggests or recommends

[Floris]

Op Wed, 18 Feb 2015 12:04:49 +0100 schreef Ansgar Burchardt  
ans...@debian.org:



Hi,

On 02/18/2015 11:03 AM, Floris wrote:

I have installed the Debian Base system and add gnome-session, gdm,
xserver-xorg-video-nvidia and probably some other packages to get a
working gnome environment. Maybe coincidental, but none of these
packages recommends less. Only man-db and gzip suggests it. Git have
a recommend, but I don't think an end-desktop-user will use it.


What does Debian Base system mean to you?


standard system



less in testing has Priority: important and should be included in all
new installs. In Debian 7, it had only Priority: standard and would only
be installed if you did not uncheck standard system (or similar) in
the installer.

Ansgar



You are right. less have also the priority important in unstable. So one
way or another I must have removed it from my system.

You may close this bug.

floris


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

Bug#778620: systemd: Add less to suggests or recommends

[Floris]

Op Wed, 18 Feb 2015 07:31:57 +0100 schreef Martin Pitt mp...@debian.org:


Hello Floris,

floris [2015-02-17 15:47 +0100]:

from man journalctl:
The output is paged through less by default, and long lines are  
truncated to
screen width. The hidden part can be viewed by using the left-arrow and  
right-

arrow keys.


In particular it's $PAGER, and it defaults to less. But I'm not sure
whether we should add a suggests to it -- it rather seems like if you
really have a minimal system without any pager, then you probably have
a good reason for it.


I have installed the Debian Base system and add gnome-session, gdm,
xserver-xorg-video-nvidia and probably some other packages to get a
working gnome environment. Maybe coincidental, but none of these
packages recommends less. Only man-db and gzip suggests it. Git have
a recommend, but I don't think an end-desktop-user will use it.


Also, systemd is installed by default, so
chances are high that a user would never actually see the suggestion.



When a program behave strange, I always look at the suggested packages.
(maybe I am the only one) I admit, the man pages had the same problem
as the journal, so eventually that package had pointed me to less.



So I'm inclined to wontfix and/or close this. But this isn't a strong
opinion, adding a Suggests: less is fairly harmless after all.

Martin



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

Bug#778620: systemd: Add less to suggests or recommends

[floris]

Package: systemd
Version: 218-10
Severity: minor

Dear Maintainer,

from man journalctl:
The output is paged through less by default, and long lines are truncated to
screen width. The hidden part can be viewed by using the left-arrow and right-
arrow keys.

But less is not a recommendation or suggestion of systemd

thanks,

floris



-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libapparmor12.9.0-3+exp1
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-5
ii  libc6   2.19-15
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.2-4+b1
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libmount1   2.25.2-5
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 218-10
ii  mount   2.25.2-5
ii  sysv-rc 2.88dsf-58
ii  udev218-10
ii  util-linux  2.25.2-5

Versions of packages systemd recommends:
ii  dbus1.8.16-1
ii  libpam-systemd  218-10

Versions of packages systemd suggests:
pn  systemd-ui  none

-- 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#767988: O: plotutils -- GNU plotutils command line tools based on libplot

[Floris Bruynooghe]

Package: wnpp
Severity: normal

I intend to orphan the plotutils package.  It is very low maintenance
and currently in a pretty good shape.  It may just require some updates
for policy changes but there shouldn't be anything major.

The package description is:
 The GNU plotting utilities include programs for plotting
 two-dimensional scientific data.  They are built on top of GNU
 `libplot', a library for device-independent two-dimensional vector
 graphics.


Regards,
Floris


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

Bug#756259: accountsservice: Series file not updated.

[Floris-Andrei Stoica-Marcu]

Package: accountsservice
Version: 0.6.37-2
Severity: important

Dear Maintainer,

I need the 009 patch in order to depend on accountsservice for the Muon package 
I am currently porting. (the one with the perl script)
I saw that all the patches are there, but you have not updated the series file. 
If you have other reasons that hold you from putting the patch, please let me 
know so that I can be of assistance.

Floris.

*** 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: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-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 /bin/dash

Versions of packages accountsservice depends on:
ii  dbus   1.8.2-1
ii  init-system-helpers1.18
ii  libaccountsservice00.6.37-2
ii  libc6  2.18-7
ii  libglib2.0-0   2.40.0-3
ii  libpolkit-gobject-1-0  0.105-5

accountsservice recommends no packages.

Versions of packages accountsservice suggests:
ii  gnome-control-center  1:3.8.3-7

-- 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#751082: Siduction

[Floris]

I made a temporary workaround for the problem I mentioned above in this  
comment:


 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755020#15


Or use the long-lived branch release (340.24 version) from Siduction

floris


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

Bug#742561: [Patch] Enable winearch variable

[Floris]

This patch make sure the wine loader looks for the WINEARCH variable or  
find if the executable is 64-bit.

Closes #742561

enable-winearch.patch
Description: Binary data

Bug#742561: [Patch] Enable $WINEARCH

[Floris]

a simpler version of the previous patch.
wine=$wine32 was always the standard option when both wine32-unstable and  
wine64-unstable were installed. So it is only necessary to change it to  
wine=$wine64 when the executable is 64-bit or the $WINEARCH variable is  
given. I used the same method as the wine stable version script.

enable-winearch.patch
Description: Binary data

Bug#742561: [Patch] Enable $WINEARCH or look in system.reg

[Floris]

When no $WINEARCH is given, search in system.reg to find if the WINEPREFIX  
is a 64 or 32 bit prefix

enable-winearch-wineprefix.patch
Description: Binary data

Bug#742561: [pkg-wine-party] Bug#742561: wineboot: Setting up a new 64bit wine prefix fails

[Floris]

Op Fri, 20 Jun 2014 03:16:38 +0200 schreef Camilo  
cam.report...@gmail.com:



Package: wine-unstable
Version: 1.7.20-1
Followup-For: Bug #742561

Dear Maintainer,

As of 1.7.20-1, wine-unstable still fails to create a 64bit prefix.

Steps:
~$ env WINEARCH=win64 WINEPREFIX=/path/to/prefix wine-unstable winecfg

The next message is displayed
WINEARCH set to win64 but '/path/to/prefix' is a 32-bit installation.

wine32-unstable and wine64-unstable are both installed.

When wine64-unstable is the only package installed, the prefix is  
correctly

created



Also see (and maybe answer)
http://lists.alioth.debian.org/pipermail/pkg-wine-party/2014-June/003861.html

Thanks,

floris


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

Bug#648376: gnome-shell: Craches when button_layout does not contain :

[Floris Bruynooghe]

Hi,

Yes I can confirm that this is no longer a problem and behaves as
expected.  Tested with 3.8.4-5+b1.

Thanks,
Floris


On 27 March 2014 22:54, althaser altha...@gmail.com wrote:
 Hey Floris,

 this is an old bug.

 Could you please still reproduce this issue with newer gnome-shell version
 like 3.4.2-7+deb7u1 or 3.8.4-5+b1 ?

 the new path from dconf-editor is: org.gnome.shell.overrides.button.layout

 here with 3.8.4-5+b1 if I remove the : on that field it just move the
 close button to left for instance.

 cheers,
 althaser







-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org


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

Bug#725422: systemd set kernel.sysrq=16

[Floris Kraak]

Allow me to summarize the argument here:
1) The sysrq keys can be an important (recovery) tool for administrators.
2) Having systemd disable them is unexpected behaviour for most of us, at
the very least.
3) Setting default value for the sysrq keys belongs in the kernel package,
not in the systemd package.
4) Besides, the default value of 16 is overly restrictive - just
restricting the signal and dump keys is good enough from a security
perspective, but allowing only sync to work is like having a car but then
taking away the engine, the wheels, and the steering wheel. Yes, you can
still sit in it, but it's effectively useless.
5) Quite frankly, just because you *can* do something in systemd doesn't
mean it's a good idea.

Regards,
Floris Kraak
-- 
REALITY.SYS corrupted. Reboot Universe? (Y/N/Q)

Bug#711351: Nouveau drivers

[Floris]

Maybe the Nvidia drivers are the pain, so I removed them and installed the  
nouveau drivers.


Removed all the extra rules in /etc/udev/rules.d/


run:
$systemd-loginctl attach seat1  
/sys/devices/pci:00/:00:05.0/:02:00.0/drm/card1
$systemd-loginctl attach seat1  
/sys/devices/pci:00/:00:05.0/:02:00.0/graphics/fb1
$systemd-loginctl attach seat1  
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
$systemd-loginctl attach seat1  
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input1
$systemd-loginctl attach seat1  
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input2


new rules where successful created

Unfortunately gdm3 doesn't show up on the second monitor

# cat /var/log/Xorg.1.log
[ 21974.612]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 21974.612] X Protocol Version 11, Revision 0
[ 21974.612] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
[ 21974.612] Current Operating System: Linux Alice 3.2.0-4-amd64 #1 SMP  
Debian 3.2.41-2 x86_64
[ 21974.612] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64  
root=UUID=a477244f-3efb-45a8-9f4c-12adc0b0130d ro quiet

[ 21974.612] Build Date: 17 April 2013  10:22:47AM
[ 21974.612] xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org)
[ 21974.612] Current version of pixman: 0.26.0
[ 21974.613]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 21974.613] Markers: (--) probed, (**) from config file, (==) default  
setting,

(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 21974.613] (==) Log file: /var/log/Xorg.1.log, Time: Thu Jun  6  
20:34:31 2013
[ 21974.613] (==) Using system config directory  
/usr/share/X11/xorg.conf.d

[ 21974.613] (==) No Layout section.  Using the first Screen section.
[ 21974.613] (==) No screen section available. Using defaults.
[ 21974.613] (**) |--Screen Default Screen Section (0)
[ 21974.613] (**) |   |--Monitor default monitor
[ 21974.613] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[ 21974.613] (==) Automatically adding devices
[ 21974.613] (==) Automatically enabling devices
[ 21974.613] (WW) The directory /usr/share/fonts/X11/cyrillic does not  
exist.

[ 21974.613]Entry deleted from font path.
[ 21974.613] (WW) The directory  
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist.

[ 21974.613]Entry deleted from font path.
[ 21974.614] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 21974.614] (==) ModulePath set to /usr/lib/xorg/modules
[ 21974.614] (II) The server relies on udev to provide the list of input  
devices.
	If no devices become available, reconfigure udev or disable  
AutoAddDevices.

[ 21974.614] (II) Loader magic: 0x7f00fc6fbae0
[ 21974.614] (II) Module ABI versions:
[ 21974.614]X.Org ANSI C Emulation: 0.4
[ 21974.614]X.Org Video Driver: 12.1
[ 21974.614]X.Org XInput driver : 16.0
[ 21974.614]X.Org Server Extension : 6.0
[ 21974.615] (--) PCI:*(0:1:0:0) 10de:0615:1043:82fb rev 162, Mem @  
0xf500/16777216, 0xd000/268435456, 0xf200/33554432, I/O @  
0xac00/128, BIOS @ 0x/131072
[ 21974.615] (--) PCI: (0:2:0:0) 10de:104a:3842:2615 rev 161, Mem @  
0xf600/16777216, 0xe800/134217728, 0xe600/33554432, I/O @  
0xbc00/128, BIOS @ 0x/524288

[ 21974.615] (II) Open ACPI successful (/var/run/acpid.socket)
[ 21974.615] (II) LoadModule: extmod
[ 21974.616] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 21974.616] (II) Module extmod: vendor=X.Org Foundation
[ 21974.616]compiled for 1.12.4, module version = 1.0.0
[ 21974.616]Module class: X.Org Server Extension
[ 21974.616]ABI class: X.Org Server Extension, version 6.0
[ 21974.616] (II) Loading extension SELinux
[ 21974.616] (II) Loading extension MIT-SCREEN-SAVER
[ 21974.616] (II) Loading extension XFree86-VidModeExtension
[ 21974.616] (II) Loading extension XFree86-DGA
[ 21974.616] (II) Loading extension DPMS
[ 21974.616] (II) Loading extension XVideo
[ 21974.616] (II) Loading extension XVideo-MotionCompensation
[ 21974.616] (II) Loading extension X-Resource
[ 21974.616] (II) LoadModule: dbe
[ 21974.617] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 21974.617] (II) Module dbe: vendor=X.Org Foundation
[ 21974.617]compiled for 1.12.4, module version = 1.0.0
[ 21974.617]Module class: X.Org Server Extension
[ 21974.617]ABI class: X.Org Server Extension, version 6.0
[ 21974.617] (II) Loading extension DOUBLE-BUFFER
[ 21974.617] (II) LoadModule: glx
[ 21974.617] (II) Loading 

Bug#711351: systemd: Setup multiseat with two nvidia cards using the proprietary drivers

[Floris]

Package: systemd
Version: 44-11
Severity: normal

Dear Maintainer,

I try to setup a multiseat system with two nvidia cards. Following the only
documentation I found on
http://code.lexarcana.com/blog/2012/06/17/simple-multiseat-setup-on-fedora-17/

Unfortunately the nvdia cards do not create a drm or graphics device in
sysfs, so the tag master-of-seat is needed.
There is no information on how to create such tag so I asked on the systemd-
devel list. The response was:

Then you'll need to add a rule equivalent to

SUBSYSTEM==graphics, KERNEL==fb[0-9]*, TAG+=seat, TAG+=master-of-seat

but replace fb[0-9] with whatever your device is (which depends on
your hardware/driver). Ideally your distro would ship the correct
rules file with the driver...

I created the next rule:
$cat /etc/udev/rules.d/02-seat.rules
SUBSYSTEM==pci, KERNEL==:02:00.0, TAG+=seat, TAG+=master-of-seat
SUBSYSTEM==pci, KERNEL==:01:00.0, TAG+=seat, TAG+=master-of-seat

attach a keyboard and a mouse to a seat
#systemd-loginctl attach seat2
/sys/devices/pci\:00/\:00\:03.0/\:01\:00.0
#systemd-loginctl attach seat2
/sys/devices/pci\:00/\:00\:1a.0/usb1/1-1/1-1.4/1-1.4\:1.0/input/input1
#systemd-loginctl attach seat2
/sys/devices/pci\:00/\:00\:1a.0/usb1/1-1/1-1.3/1-1.3\:1.0/input/input0

systemd create the 72-seat-device name.rules in /etc/udev/rules.d

After a restart I expected to have a working multiseat. But without succes

# udevadm info --query=all --path
/sys/devices/pci\:00/\:00\:03.0/\:01\:00.0/
P: /devices/pci:00/:00:03.0/:01:00.0
E: DEVPATH=/devices/pci:00/:00:03.0/:01:00.0
E: DRIVER=nvidia
E: ID_FOR_SEAT=pci-pci-_01_00_0
E: ID_PATH=pci-:01:00.0
E: ID_PATH_TAG=pci-_01_00_0
E: ID_SEAT=seat2
E: MODALIAS=pci:v10DEd0615sv1043sd82FBbc03sc00i00
E: PCI_CLASS=3
E: PCI_ID=10DE:0615
E: PCI_SLOT_NAME=:01:00.0
E: PCI_SUBSYS_ID=1043:82FB
E: SUBSYSTEM=pci
E: TAGS=:master-of-seat:seat:seat2:
E: UDEV_LOG=3
E: USEC_INITIALIZED=9061956

All the tags about the seat are present, but the systemd shows only one seat
$ systemd-loginctl list-seats
SEAT
seat0

1 seats listed.



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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  dpkg 1.16.10
ii  initscripts  2.88dsf-41
ii  libacl1  2.2.52-1
ii  libaudit01:1.7.18-1.1
ii  libc62.17-3
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.4.3-4
ii  libdbus-1-3  1.6.10-1
ii  libkmod2 9-3
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-9
ii  libselinux1  2.1.13-2
ii  libsystemd-daemon0   44-11
ii  libsystemd-id128-0   44-11
ii  libsystemd-journal0  44-11
ii  libsystemd-login044-11
ii  libudev0 175-7.2
ii  libwrap0 7.6.q-24
ii  udev 175-7.2
ii  util-linux   2.20.1-5.4

Versions of packages systemd recommends:
ii  libpam-systemd  44-11

Versions of packages systemd suggests:
ii  python2.7.3-5
ii  python-cairo  1.8.8-1+b2
ii  python-dbus   1.2.0-1
ii  systemd-gui   44-11

-- 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#681801: Preseeding console-keymaps-at/keymap=us no longer works to select keymap

[Floris Bos / Maxnet]

Package: console-setup-udeb
Version: 1.80


We perform automated preseeded Debian installations.
With Debian Squeeze we are able to use the following boot parameters to 
prevent Debian from prompting for country and keyboard settings:


==
debian-installer/locale=en_US kbd-chooser/method=us 
console-keymaps-at/keymap=us

==

However with Wheezy this no longer works, and we get prompted for 
keyboard map regardless (screenshot: 
http://s17.postimage.org/on6is922n/keymap_prompt.png )



In case a different preseed value then console-keymaps-at/keymap=us is 
necessary nowadays, please update the documentation ( 
http://d-i.alioth.debian.org/manual/en.amd64/apbs04.html#preseed-l10n )



--
Yours sincerely,

Floris Bos


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

Bug#650316: debian-maintainers: Please add Floris Bruynooghe as Debian Maintainer

[Floris Bruynooghe]

Package: debian-maintainers
Severity: normal

Hello,

I'd like to request to be added to the Debian Maintainers keyring.
Attached is the corresponding jetring changest with all the required
information.

Thanks,
Floris


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Comment: Add Floris Bruynooghe f...@devork.be as a Debian Maintainer
Date: Mon, 28 Nov 2011 19:27:32 +
Action: import
Recommended-by: 
Thomas Girard thomas.g.gir...@free.fr,
Santiago Vila sanv...@debian.org
Agreement: 
http://lists.debian.org/debian-newmaint/2011/11/msg00015.html
Advocates: 
http://lists.debian.org/debian-newmaint/2011/11/msg00023.html
http://lists.debian.org/debian-newmaint/2011/11/msg00032.html
Data: 
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1.4.11 (GNU/Linux)
  
  mQINBE3/igMBEACxJ2cHDuc345JGiSLtW6wij2zBstWLB6wA70AbHzLkBgazJW9A
  sDNvij7EXkyVL2BkRaTS1BVLI0ku/tcACfiSV66ob6kiBaxqGSTV/6yS7U4/HqO4
  4/0Hda5C9gO9vSCt+yC9efaAsHZvuMTiLJt1PMTgRDLSekM9qDI/H3mXGOvZEZ2V
  r4oppFN5aN2GWxjn+cGlyWms237LBz0k9TXGuWw9VRKFCSkmSmALnn5kyGhOwGhD
  g+qneG65QPzxLRNGvFTWewIIMFSAWlrG89qL7bj9yLSZhOV2TqvooSGz+bThA2Ha
  Ch+5+OdvROaJAc8746xNJgVZLxsotyjKTAB36VaaFp2c2vGqHJsR+fy6+lYS10f2
  ZF/qmeJYOBvNKXbBELyaHzfMWhdTTuHOdVLfoM65cXUF7lJek5O4Ybkw+L3j4Y7D
  YnW3y64r9k5/QUbr9086P2Ss9CII5I3vZCIbX/GFEUoIBDkq6bk728DD6cYEVMjK
  /mD4lPweYu+W8dxvqeUj/UO8yEEwwBmjbU198hZPWE8lVmvN7YRuSJeamlph+Lat
  RLiurvTZqfrz5mBxuAv0Yf4QncCc1WojDHeIec34CCFAR5SjIO23lyeoriaTD54P
  5VL9AvDCs3rWmdpIuFBv0lkUM81I3toC/4Avz9ViP6TFr45v0/1WaZoR3QARAQAB
  tCJGbG9yaXMgQnJ1eW5vb2doZSA8Zmx1YkBkZXZvcmsuYmU+iQI6BBMBCAAkAhsD
  BQsJCAcDBRUKCQgLBRYCAwEAAh4BAheABQJN/43kAhkBAAoJEHAqJttMyz/89A8P
  /1gF6U+Yr7CoCs9DkzH1xtIWnaoNBMBCccNooCT2i+MMHP65ToNpxv/TWenyCtfA
  faofR+4BjcsWYcozdtLYojuHIh15WV5X/kdShsD1Ltlp6PEr9rOW2Bao2m79cv4F
  pKymem/KgGFR+FsqiiE68P5UvkkHXmGwdtiP6DnjawaNnfjvFFsmhCPJh9HOdXek
  VsJR7AkBkX2qP2QL4WZhi6SpXDG993nqDrCkP1hJGpxiVx16EqPg5cONy4kENKNH
  uYWnDI4eQyWldC0ZaT61abAJB+L//Fs/auK0nb+OkynGAMdo14GCiHAxsMbi9H8b
  Jo1FxmMcoK4OjyU5bdCp1dHCLVdKSHP4WXEzapHFFeYcOoOKnzxqBOMIE9Gd832d
  ETxy4iWuXkkOcxWqvjrMa2PNDThsCO3Brydm2vnOjjIT/goweMjPBCdazQraiWm1
  oZw0MCVAs1UZEL2BC3s1KxOCscIJeDzZa5o+RtmZyVfomgwi7hSf3Dktrv2wqqZ7
  D5M7gvEVhYMmPYttn8TxgQXyK4NgVyXrSTCAHEfRFNxKd9IXjC4VXK8rk1JCL0p5
  F5Ycq81CwqtRoHihaYW1WtoVNwrR7Diw6h38vyNYIENq0k/Q/zXquicK6AUGI67q
  d+RXGt8IvQwlt0x0IV4IO7XhMoHqGJFHv9nyFeKfEy+TiEYEEBEIAAYFAk3/jkgA
  CgkQ1ZnMZEhp4EdS/wCfedYdjNGnmhPmy3OdAb6rYjLMTqEAn3ky6/cMRxFvJ1NF
  xtBCjJjhESG0iEYEEBECAAYFAk4E52AACgkQAukwV0RN2VA5igCcC/rF33IEny18
  tgKMqCIa3oXX1k4AoI1cHcBk9YrqKpj6vG97qrqaXHvpiEYEEBECAAYFAk4A9DcA
  CgkQaGRzDfCV5eT+bgCggbiLDjz7EgI9dBE6LOvFfJL6VAoAnim7g2EWXq3UG85x
  DGDEjK8Zbyl3tC9GbG9yaXMgQnJ1eW5vb2doZSA8ZmxvcmlzLmJydXlub29naGVA
  Z21haWwuY29tPokCNwQTAQgAIQUCTf+NWwIbAwULCQgHAwUVCgkICwUWAgMBAAIe
  AQIXgAAKCRBwKibbTMs//KUlD/0dIlI4ajemZFnYiKxpHi4or8/Y5wnwnr6qveft
  zseu9D8XbEJvWjbkY7PGUQS+uFRqf7GugMqPcsye/rOvshpCVFJE2SQy6m2c9O4f
  B1J+uCLgzW9o6bCFlOgvoQ/zQM8ZpkSBs/ANaGyIGQ5lbmoh4qLjq8QApeO0AVvM
  LueMGXlJKbko3EAe0Naw9BrnVBCsPcIDFRfLEBV+z0c5w4K9XahPFcDIxu2ggkaQ
  aEeHe88AkwXzeC48NK1+T799vXZ/SCSPhcgm6HthGWRkPiAi5UGNA1ZMnpex6xog
  uqTnW2w8RtMdxDRKTRP87ofdNcFJVogECnsuZG0izrFBfn3+YckwYE0pMcy/X4OE
  UTlILg2YU3CA5McWgCc4rEzZhwBPR5C2AQV7+ENdH6OG09g/GglYbm4Tuuzvdvj9
  65Y0AXVAcLUp5zMx6QQtVP823TQY5Xbn4Kdbnd3nZ9i3zi1BIva7IzZGGrYO/lE9
  ++3785f856F3mozCVFRydzfdnwQosuwxjaMoQfNGVaPwXog0hdjxA0gOJF8D2CMB
  gR2aHQBd+rSXaIJZlYUbYKZG4EoP9iT81HLkwGTPvbpAXxZ4qjVy0xc9y3xcpl26
  XEHYZlfL5tpKO5XyvARbXA3vmGSsPWeQIDbeZsKRr9WV2SU2pXx9CeTXqB+qowb4
  hQKLYohGBBARCAAGBQJN/45IAAoJENWZzGRIaeBHujIAnibXDi8+3LkWMNqQ8Nu9
  cgTQJ6k+AJ0VoSb/BsRvKGi+przDkv1oEhHL+IhGBBARAgAGBQJOAPQ3AAoJEGhk
  cw3wleXkSIUAnj0ITNV5xWuTryKSDDgj3/+s5D/PAJ4m9vUMtLO0juSFUaP8ZXTU
  ZFYj6rkCDQRN/4oDARAAxnp/HbGIKUIaab5GEJuLx1PnTIivsduJReSI8ibvKnNE
  GuxsD4qD4mOCIbMSivB2Ky7l1gm1/jCr+TIiILkoOCRa0gGdoh7p/kn7DgwUBxXL
  gdUtB1r8JrS0RZT64k0nW58MyTELirZYMnDpTW6kUKZMqnXU0LTX32Dln9QJboWc
  GUKlTdmxZyBaf1YVVLTRaDZKy8TWKp3lhvMfL5hY3C+7dvjJkErg6Cz/ng5nV5UT
  Ilc9A1aGn5TDgNjxFExLzvU1oi/swc99ee3sQ8anW9WcB0DoMbAe9FCJpXHO33hb
  qZSyO7RzqN7soE5+y0y+CM3wW2RvHsHzqHgjSV5+/nh/J2uKpFGUOPpKFwtb7h3G
  tmTGo+qeCmUXMI9JlNXO3ueCbddLEoaAl41s9gudQ7IUVjk5JB49hSXtXN/ylE2/
  CXH/tTu0Cmc+I8fr0R1d2+fONB1EISv1Wxsz3yo/qRJBDw6k0Fdb2m/waJ70v8pd
  0o6NCRbBmCfJb7egUlpR9I/fRnS/Sd5T7kSS5tEdfVEeImDg44DcSBZAR+nQGQhJ
  3B+iEkeImlBDPLhkqPPmUh/AYt2AFlf1OLUjrzoU8Z2YFLspMP91b3iJkkZySkJ5
  y/zVB6YdGGSLWOMJKBGkSZLFf/RMoGPp9SQGWXXbgO5V3PkvXf25kOxHUrlK9jsA
  EQEAAYkCHwQYAQgACQUCTf+KAwIbDAAKCRBwKibbTMs//J3VD/9qUtLVKABhbzxg
  cSgdMmcGCnahd3N0jmSEER+Rfn5cIjTY/00Q2hM8Ehdk2qp8tXbzWV0aB1aYNCoo
  GKnLHcKKdz21+zcAOL5P0vE3r76tdIPtZlaljA8480PDG4PvQM4KFxGCVtAyqbSv
  +d+QXN10EKWBlG0lKnIJbAES6LfglsYV

Bug#648376: gnome-shell: Craches when button_layout does not contain :

[Floris Bruynooghe]

Package: gnome-shell
Version: 3.0.2-5
Severity: minor

Hi,

If you manage to place a string which does not contain a colon (:) in
the /desktop/gnome/shell/windows/button_layout gconf key gnome-shell
will crash as soon as you try to open a window.  Yes that's a user
error, but a pretty bad and obtuse way of failing.

Regards,
Floris

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.7.5-3 
ii  gconf2   2.32.4-1
ii  gir1.2-atk-1.0   2.2.0-2 
ii  gir1.2-clutter-1.0   1.8.2-1 
ii  gir1.2-cogl-1.0  1.8.2-1 
ii  gir1.2-coglpango-1.0 1.8.2-1 
ii  gir1.2-freedesktop   0.10.8-2+b1 
ii  gir1.2-gconf-2.0 2.32.4-1
ii  gir1.2-gdkpixbuf-2.0 2.24.0-1
ii  gir1.2-gkbd-3.0  3.2.0-1 
ii  gir1.2-glib-2.0  0.10.8-2+b1 
ii  gir1.2-gnomebluetooth-1.03.2.1-1 
ii  gir1.2-gtk-3.0   3.0.12-2
ii  gir1.2-json-1.0  0.14.0-1
ii  gir1.2-mutter-3.03.0.2.1-4   
ii  gir1.2-networkmanager-1.00.9.0-2 
ii  gir1.2-pango-1.0 1.29.4-2
ii  gir1.2-polkit-1.00.102-1 
ii  gir1.2-telepathyglib-0.120.16.0-1
ii  gir1.2-telepathylogger-0.2   0.2.10-2
ii  gir1.2-upowerglib-1.00.9.14-1
ii  gjs  1.29.0-2+b1 
ii  gnome-bluetooth  3.2.1-1 
ii  gnome-icon-theme-symbolic3.2.1-1 
ii  gnome-settings-daemon3.0.3-3 
ii  gsettings-desktop-schemas3.0.1-1 
ii  libatk1.0-0  2.2.0-2 
ii  libc62.13-21 
ii  libcairo-gobject21.10.2-6.1  
ii  libcairo21.10.2-6.1  
ii  libcamel-1.2-23  3.0.3-1 
ii  libcanberra0 0.28-3  
ii  libclutter-1.0-0 1.8.2-1 
ii  libcogl-pango0   1.8.2-1 
ii  libcogl5 1.8.2-1 
ii  libcroco30.6.2-2 
ii  libdbus-1-3  1.4.16-1
ii  libdbus-glib-1-2 0.98-1  
ii  libdrm2  2.4.26-1
ii  libebook1.2-10   3.0.3-1 
ii  libecal1.2-8 3.0.3-1 
ii  libedataserver1.2-14 3.0.3-1 
ii  libedataserverui-3.0-0   3.0.3-1 
ii  libffi5  3.0.10-3
ii  libfontconfig1   2.8.0-3 
ii  libfreetype6 2.4.7-2 
ii  libgconf2-4  2.32.4-1
ii  libgdk-pixbuf2.0-0   2.24.0-1
ii  libgirepository-1.0-10.10.8-2+b1 
ii  libgjs0b [libgjs0-libmozjs7d]1.29.0-2+b1 
ii  libgl1-mesa-glx [libgl1] 7.11-6  
ii  libglib2.0-0 2.28.8-1
ii  libgnome-desktop-3-0 3.0.2-2 
ii  libgnome-menu2   3.0.1-3 
ii  libgstreamer0.10-0   0.10.35-1   
ii  libgtk-3-0   3.0.12-2
ii  libical0 0.44-3  
ii  libjson-glib-1.0-0   0.14.0-1
ii  libmozjs7d   7.0.1-4 
ii  libmutter0   3.0.2.1-4   
ii  libnspr4-0d  4.8.9-1 
ii  libnss3-1d   3.12.11-3   
ii  libpango1.0-01.29.4-2
ii  libpolkit-agent-1-0  0.102-1 
ii  libpolkit-gobject-1-00.102-1 
ii  libpulse-mainloop-glib0  1.0-4   
ii  libpulse01.0-4   
ii  libsoup2.4-1 2.34.3-1
ii  libsqlite3-0 3.7.7-2 
ii  libstartup

Bug#644904: [Pkg-corba-devel] Bug#644904: Bug#644904: omniidl: fails to install on sid

[Floris Bruynooghe]

Hello,

On Wed, Oct 12, 2011 at 10:20:20AM +0200, Haïkel Guémar wrote:
 i'm using pbuilder to build my package. The Debian Developer
 (Sylvestre Ledru) who sponsored my package had the same issue with
 cowbuilder.
 I reproduced that issue on a fresh pbuilder chroot (i refreshed apt
 package cache and checked that python 2.7.2 is installed before):

Thanks for this extra information, it was me who had an un-clean
chroot.  It seems I still had python 2.6 installed and with that
missing I can reproduce your problem.

Regards,
Floris

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#644904: [Pkg-corba-devel] Bug#644904: omniidl: fails to install on sid

[Floris Bruynooghe]

severity 644904 normal
thanks

Hello Haïkel,

Could you provide some more information on how the installation of
omniidl fails for you?  I've just installed it in my sid chroot with
python 2.7 as the default and everything works just fine (hence I
lowered the severity to not be RC).  Any chance your chroot is just in
a funny state?

Thanks,
Floris


-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#635161: open-iscsi: add a udeb

[Floris Bos]

Hi,

On Saturday, July 23, 2011 12:37:29 PM Colin Watson wrote:
 I'd like to merge Ubuntu's support for iSCSI during d-i back into
 Debian.  Here's a patch for open-iscsi to add a udeb, which is the first
 step in making this work.
 
 Once this has landed, I'll merge the partman-iscsi work I've done into
 the d-i repository.

I was wondering why the upstream iscsistart is not included in the udeb.

That way it would be possible to simply call iscsistart -b if an iBFT table 
is present to auto-configure the iSCSI settings, without having to prompt the 
user.



Related bugs: 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495042#15 (debian-installer: 
add iscsi root installation)


-- 
Yours sincerely,

Floris Bos



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

Bug#495042: debian-installer: add iscsi root installation

[Floris Bos]

Hi,

Bumping an old feature request.

On Thursday, August 14, 2008 09:42:31 AM you wrote:
 Add iscsi root installation feature to debian installer. 

I was wondering if there were any plans to add this?


Did experiment a bit with it myself, and it's not that much work to simply 
detect the iSCSI settings set in the BIOS/boot firmware, and connect to the 
iSCSI target automatically, like CentOS and Windows do.

See the attached (unpolished) patches as a starting point of a way this can be 
done.


In short what is necessary is:

- check for the presence of an iBFT table in memory. This can be done by 
loading the iscsi_ibft kernel module and checking /sys.
  Since it only scans a memory region and does not do any more agressive 
probing, it's safe to load by default.

- if found, it means iSCSI is configured on the computer and the other iscsi 
kernel modules should be loaded. As well as an udeb with the open-scsi 
usermode tools that are responsible for setting up the connection. Calling 
iscsistart -b is enough to automatically connect to the target using the 
information found in the iBFT and attach the disks.

- make sure open-iscsi is added to the packages to be installed, and that a 
initramfs with iscsi support is created, so that the system will start after 
reboot.


-- 
Yours sincerely,

Floris Bos
diff -ur hw-detect-1.87.orig/debian/disk-detect.templates hw-detect-1.87/debian/disk-detect.templates
--- hw-detect-1.87.orig/debian/disk-detect.templates	2011-06-23 21:57:17.0 +0200
+++ hw-detect-1.87/debian/disk-detect.templates	2011-07-13 01:10:41.0 +0200
@@ -42,3 +42,13 @@
 Description: for internal use; can be preseeded
  Check for the presence of multipath devices?
 
+Template: disk-detect/iscsi_connect
+Type: text
+# :sl2:
+_Description: Connecting to iSCSI target
+
+Template: disk-detect/iscsi_error
+Type: error 
+# :sl2:
+_Description: Error connecting to iSCSI target (using the login information found in the iBFT)
+ 
diff -ur hw-detect-1.87.orig/disk-detect.sh hw-detect-1.87/disk-detect.sh
--- hw-detect-1.87.orig/disk-detect.sh	2011-06-23 21:57:17.0 +0200
+++ hw-detect-1.87/disk-detect.sh	2011-07-13 01:24:09.0 +0200
@@ -120,10 +120,31 @@
 	fi
 }
 
+iscsi_probe() {
+
+	log Looking for iSCSI iBFT table...   
+	modprobe iscsi_ibft || true 
+
+	if [ -e /sys/firmware/ibft/target0 ]; then
+		anna-install open-iscsi-udeb
+		modprobe iscsi_tcp
+		db_progress START 0 1 disk-detect/iscsi_connect
+		iscsistart -b || db_input high disk-detect/iscsi_error 
+		db_progress STOP	
+		apt-install open-iscsi || true
+	else
+		log No iSCSI iBFT table found, not loading iSCSI package
+	fi
+
+	return 0
+}
+
 if ! hw-detect disk-detect/detect_progress_title; then
 	log hw-detect exited nonzero
 fi
 
+iscsi_probe
+
 while ! disk_found; do
 	CHOICES=
 	for mod in $(list_disk_modules | sort); do
diff -ur kernel-wedge-2.77.orig/modules/scsi-modules kernel-wedge-2.77/modules/scsi-modules
--- kernel-wedge-2.77.orig/modules/scsi-modules	2011-03-12 19:38:58.0 +0100
+++ kernel-wedge-2.77/modules/scsi-modules	2011-07-11 20:03:03.0 +0200
@@ -26,3 +26,5 @@
 aic94xx ?
 stex ?
 xen-blkfront ?
+iscsi_tcp ?
+iscsi_ibft ?
diff -urN open-iscsi-2.0.871.3.orig/debian/control open-iscsi-2.0.871.3/debian/control
--- open-iscsi-2.0.871.3.orig/debian/control	2011-05-02 20:52:46.0 +0200
+++ open-iscsi-2.0.871.3/debian/control	2011-07-11 19:31:03.0 +0200
@@ -28,6 +28,15 @@
  The userspace component consists of a daemon, iscsid and a management
  utility, iscsiadm
 
+Package: open-iscsi-udeb
+Architecture: any
+Section: debian-installer
+XC-Package-Type: udeb
+Depends: ${shlibs:Depends}, ${misc:Depends}, scsi-modules, libnss-files-udeb 
+Description: Open-iSCSI initiator
+ .
+ For use by debian-installer.
+
 #Package: linux-iscsi-modules-source
 #Architecture: all
 #Depends: ${shlibs:Depends}, ${misc:Depends}, module-assistant, debhelper (= 4.0.0), bzip2
diff -urN open-iscsi-2.0.871.3.orig/debian/extra/initramfs.hook open-iscsi-2.0.871.3/debian/extra/initramfs.hook
--- open-iscsi-2.0.871.3.orig/debian/extra/initramfs.hook	2011-05-02 20:52:46.0 +0200
+++ open-iscsi-2.0.871.3/debian/extra/initramfs.hook	2011-07-13 01:02:57.0 +0200
@@ -26,6 +26,6 @@
 cp /etc/iscsi/initiatorname.iscsi $DESTDIR/etc
 cp /etc/iscsi/iscsi.initramfs $DESTDIR/etc
 
-for x in crc32c libcrc32c iscsi_tcp libiscsi scsi_transport_iscsi; do
+for x in crc32c libcrc32c iscsi_tcp iscsi_ibft libiscsi scsi_transport_iscsi; do
 	manual_add_modules ${x}
 done
diff -urN open-iscsi-2.0.871.3.orig/debian/open-iscsi-udeb.dirs open-iscsi-2.0.871.3/debian/open-iscsi-udeb.dirs
--- open-iscsi-2.0.871.3.orig/debian/open-iscsi-udeb.dirs	1970-01-01 01:00:00.0 +0100
+++ open-iscsi-2.0.871.3/debian/open-iscsi-udeb.dirs	2011-07-11 23:20:22.0 +0200
@@ -0,0 +1,5 @@
+usr/bin
+usr/sbin
+var/lib/open-iscsi
+usr/lib/finish-install.d
+etc/iscsi
diff -urN open-iscsi-2.0.871.3.orig/debian/open-iscsi

Bug#624740: python-omniorb: FTBFS without python2.5

[Floris Bruynooghe]

Hi

On 1 May 2011 06:37, Scott Kitterman deb...@kitterman.com wrote:
 Package: python-omniorb
 Version: 3.5-1
 Severity: serious
 Justification: fails to build from source

This has been fixed in r267 of
svn.debian.org/svn/pkg-corba/trunk/python-omniorb, so someone needs to
upload this now.  Usually Thomas Girard does this but I don't know how
much time he has (we don't tend to be the fastest team ;-)) so if this
is urgent for the transition then maybe someone else could upload this
after checking with him?

Regards
Floris

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#624680: python3-profiler: Bytecode compilation failure during install

[Floris Bruynooghe]

Package: python3-profiler
Version: 3.2-2
Severity: normal

Hi

Installing python3-profiles fails:

Setting up python3-profiler (3.2-2) ...
Traceback (most recent call last):
  File py_compile.py, line 201, in module
sys.exit(main())
  File py_compile.py, line 193, in main
compile(filename, doraise=True)
  File py_compile.py, line 131, in compile
encoding = read_encoding(file, utf-8)
  File py_compile.py, line 83, in read_encoding
f = open(file, rb)
IOError: [Errno 2] No such file or directory: 'profile.py'
dpkg: error processing python3-profiler (--configure):
 subprocess installed post-installation script returned error exit status 1

It appears the package only ships files in /usr/lib/python3.2/ but the
postinst script has a for v in 3.1 3.2 line which makes it attempt to
byte-compile files in /usr/lib/python3.1/, which don't exist.

I obviously have python3.1 installed too:
$ dpkg -l python3.1 python3.2
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
ii  python3.1  3.1.3-1An interactive high-level object-oriented la
ii  python3.2  3.2-1  An interactive high-level object-oriented la


Regards
Floris


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

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

Versions of packages python3-profiler depends on:
ii  python3   3.2-3  interactive high-level object-orie

python3-profiler recommends no packages.

Versions of packages python3-profiler suggests:
ii  python3-doc   3.2-3  documentation for the high-level o

-- 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#615600: BOOTIF= kernel commandline option does not work

[Floris Bos]

Hi,

On Tuesday, March 01, 2011 04:28:16 pm Marc Haber wrote:
 On Sun, Feb 27, 2011 at 04:22:28PM -0400, Joey Hess wrote:
  Thomas Mieslinger wrote:
   I try to install a HP DL180G6 fully automated. The Server has an
   addtional dualport NIC. kernel and initrd are loaded over the NIC
   labeled 0 on the Box, after the kernel has initialized all NICs the
   first Ethernet on the add in card is eth0.
   
   ~ # cat /proc/cmdline
   initrd=/boot/DEBIAN6_x8664/initrd.gz
   preseed/url=http://4.3.2.1/installation/profiles/1cc1deebab9e
   BOOTIF=01-1C-C1-DE-EB-AB-9E BOOT_DEBUG=2 DEBCONF_DEBUG=5 fb=false
  
  BOOTIF is a pxelinux boot parameter. It is supported by the Debian
  initramfs when pxe booting, but it is not supported by the Debian
  installer.
  
  Perhaps it should be. In the meantime, you can use the documented
  preseeding interface of booting with interface=eth1. I don't think
  netcfg allows specifying a interface by MAC though.
 
 I guess the following changes do kind of a job:
 etc/udev/rules.d/69-bootif.rules (inside the installer's initrd)
 ACTION==add, SUBSYSTEM==net, IMPORT{program}=bootif $attr{address}

The related Ubuntu bug has a patch as well: 
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/56679

(Matt already mentioned he doesn't like that patch, so it's not a permantent 
solution.
But if you are just looking for a quick fix for now, you can use it in your own 
build).


-- 
Yours sincerely,

Floris Bos



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

Bug#537271: closed by Matthew Palmer mpal...@debian.org

[Floris Bos]

On Monday, February 07, 2011 06:00:40 am Matthew Palmer wrote:
 Also, busybox patches should be put into a separate bug report which blocks
 this one, to keep things clear.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606654 - Busybox should 
include arping applet


Regarding IPv6:

I see there is already a bug for building a ndisc6-udeb: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611330

but it seems the idea is to put only rdisc6 in there:

==
I've now discovered that I need the rdisc6 tool as well as rdnssd, so the
attached patch now builds an ndisc6-udeb containing just the rdisc6 binary. 
==

Would it be possible to include the ndisc6 binary as well, and use that in the 
same way as arping?



-- 
Yours sincerely,

Floris Bos



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

Bug#562122: Improve preseeding of network device to use

[Floris Bos]

Bumping an old bug.

 I've preseeded netcfg/choose_interface to auto, to try and avoid the
 netcfg/choose_interface question being asked. What I suspect is the
 problem, is the wireless interface is showing link so the question still
 gets asked.
 
 My thoughts on how to extend this functionality was:
 
 allow preseeding the interface to use based on:
 
 1) vendor component of the MAC
 2) PCI ID
 3) some substring of the interface description
 
 because preseeding the specific interface by name is a non-starter, due to
 the way Linux can't consistently enumerate the interfaces.

I think that at least selection of the network interface by MAC-address 
instead of interface name should be possible.

There is currently a patch pending for Ubuntu:
 http://launchpadlibrarian.net/60443113/S31pxedust
(belonging to bug https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/56679 
)

Any chance of getting this into Debian as well?


-- 
Yours sincerely,

Floris Bos



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

Bug#590323: plotutils: new upstream package available

[Floris Bruynooghe]

Hello Roland

Sorry for the delay.  I've got an upload ready but only did so just as
the freeze was announced and didn't think it warranted an exception so
was waiting for the release before asking for uploading.  But if you
think we'd be better of uploading to experimental I'll adjust (and
check the package again, it's been a while) and ask for an upload
(I'll check with my regular uploader but if he's busy/agrees I don't
mind if you want to upload).

So let me know if you'd like to get this into experimental.

Regards
Floris


On 5 January 2011 21:10, Roland Stigge sti...@antcom.de wrote:
 Hi,

 On 06/08/10 00:16, Floris Bruynooghe wrote:
 On Sun, Jul 25, 2010 at 11:51:32PM +0200, Roland Stigge wrote:
 I'm maintaining pstoedit which depends on libplot from plotutils. The Debian
 bug #506086 should be fixed according to the pstoedit upstream maintainer by
 latest libplot 2.6. Therefore, I'm filing this bug as normal, not just
 wishlist.

 I've updated the package and the result is at http://devork.be/debian/
 (dget http://devork.be/debian/plotutils_2.6-1.dsc) if you'd like to
 check it out.

 I need to do some more install-upgrade-remove-... testing and will
 then ask my usual sponsor if he wants to upload.

 I'm just working with pstoedit's upstream on the new version and am
 wondering if we can fix #506086 with #590323 by uploading the new
 version of plotutils.

 I can upload the new version if you want.

 Just tell.

 Thanks,

 bye,
  Roland






-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#542441: #542441 Re: old LVM data is not erased

[Floris Bos]

Hi,

This old bug is still present in Squeeze, except that I have only seen it 
cause issues on systems with more than one disk.

If there is a LVM volume on the 2nd disk that has a group name that is the 
same Debian wants to use,  install fails with a red Volume group name already 
in use


To reproduce on a (virtual) system with 2 disks:

- install Debian.
- swap the disks cables, so that disk 1 becomes disk 2.
- try to install Debian again.


I think Debian should remove the labels from ALL disks if I specify partman-
lvm/device_remove_lvm.
Or as an alternate solution pick a random volume group name by default, so 
there are not any conflicts.


-- 
Yours sincerely,

Floris Bos



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

Bug#607847: ITP: php5-ioncube-nonfree -- Ioncube loader PHP module

[Floris Bos]

Package: wnpp
Severity: wishlist
Owner: Floris Bos b...@je-eigen-domein.nl

* Package name: php5-ioncube-nonfree
Version : 4.0.1
Upstream Author: Ioncube
* URL: http://www.ioncube.com/loaders.php
* License: Commercial
Description: 


Many commercial PHP web applications distribute their files as ionCube 
bytecode.
To be able to execute the bytecode, a loader has to be installed as PHP 
module.

The loader is available at: http://www.ioncube.com/loaders.php (binary only)

Its license allows redistribution:

==
[...]
2 DISTRIBUTION

2.1 The Loader may be freely distributed to third parties alone or as
part of a distribution containing other items provided that this license
is also included.

2.2 The Loader may under no circumstances be branded as another product,
whether distributed or not.

2.3 Distribution as part of a commercial product is permitted provided such
distribution is in accordance with clauses 2.1 and 2.2 with respect to the
Loader.
==


While I understand the issues some folks have with closed source software, 
this piece of software is just as essential for the average webhosting 
company, as for example the Flash plug-in is for the average desktop user.


-- 
Yours sincerely,

Floris Bos



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

Bug#537271: debian-installer: network may not be usable as soon as link is up

[Floris Bos]

On Thursday, July 16, 2009 05:39:24 pm you wrote:
 the debian-installer seems to assume that the network is usable as soon
 as the link comes up, which may not be the case if the 802.1d spanning
 tree protocol is in use, in which case it can be up to ~30 seconds
 before the switch port will forward ethernet frames.
 
 i've noticed that trying to preseed a network install on a machine
 attached to an STP-enabled switch usually fails since as soon as the
 network link is up, d-i attempts to perform a reverse DNS lookup and
 fetch the preseed.cfg file via HTTP, both of which timeout and fail
 before the switch port the machine is attached to enters the forwarding
 state.
 
 a nice strategy to detect if the network is usable might be to send ARP
 requests for the default gateway's IP address and consider the network
 up only after the default gateway is reachable.  it looks like there
 is a busybox version of the arping utility that could help accomplish
 this.

Quick  dirty workaround if enabling arping in busybox (or implementing the 
same in C in netcfg itself) is not an option, may also be to simply increase 
the number of ARP retries.

echo 60  /proc/sys/net/ipv4/neigh/eth0/mcast_solicit


-- 
Yours sincerely,

Floris Bos



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

Bug#606515: Preseed installation does not wait for network to be ready

[Floris Bos]

Hi,

Attached a patch to netcfg that waits for the link to come up before 
proceeding.
It times out after 10 seconds, so if link detection is broken for some reason 
it doesn't affect the install.


-- 
Yours sincerely,

Floris Bos
diff -ur netcfg.orig/Makefile netcfg/Makefile
--- netcfg.orig/Makefile	2009-10-28 21:37:37.0 +0100
+++ netcfg/Makefile	2010-12-11 20:51:10.362642461 +0100
@@ -26,7 +26,7 @@
 
 all: $(TARGETS)
 
-netcfg-static: netcfg-static.o static.o
+netcfg-static: netcfg-static.o static.o ethtool-lite.o
 netcfg: netcfg.o dhcp.o static.o ethtool-lite.o
 
 $(TARGETS): $(COMMON_OBJS)
diff -ur netcfg.orig/netcfg.h netcfg/netcfg.h
--- netcfg.orig/netcfg.h	2010-09-06 23:53:19.0 +0200
+++ netcfg/netcfg.h	2010-12-11 20:10:50.761351395 +0100
@@ -41,6 +41,9 @@
 ff02::1 ip6-allnodes\n \
 ff02::2 ip6-allrouters\n
 
+/* Maximum number of seconds to wait for network link to come up */
+#define LINK_TIMEOUT  10
+
 typedef enum { NOT_ASKED = 30, GO_BACK } response_t;
 typedef enum { DHCP, STATIC, DUNNO } method_t;
 typedef enum { ADHOC = 1, MANAGED = 2 } wifimode_t;
diff -ur netcfg.orig/static.c netcfg/static.c
--- netcfg.orig/static.c	2010-12-11 20:03:12.091975462 +0100
+++ netcfg/static.c	2010-12-11 20:49:30.851349894 +0100
@@ -269,10 +269,10 @@
 
 int netcfg_activate_static(struct debconfclient *client)
 {
-int rv = 0, masksize;
+int rv = 0, masksize, tries = 0;
 char buf[256];
 char ptr1[INET_ADDRSTRLEN];
-
+
 #ifdef __GNU__
 snprintf(buf, sizeof(buf),
  settrans -fgap /servers/socket/2 /hurd/pfinet --interface=%s --address=%s,
@@ -381,6 +381,16 @@
 debconf_capb(client, backup);
 return -1;
 }
+
+di_info(Waiting for the link of interface %s to come up, interface);
+
+do {
+usleep(10); /* sleep a tenth of a second */
+if (++tries  LINK_TIMEOUT*10) {
+di_info(Link did not come up, but timeout expired, continuing...);
+break;
+}
+} while ( ethtool_lite(interface) == 2 /*DISCONNECTED*/ );
 
 return 0;
 }

Bug#606636: Reverse DNS takes precedence over netcfg/get_hostname

[Floris Bos]

On Saturday, December 11, 2010 07:31:48 am Christian PERRIER wrote:
 Correct. Apparently, though, that behaviour didn't bother anybody
 enough to look at current netcfg code and propose the needed patch

Fair enough.

Attached a patch that introduces a new netcfg/hostname option that -if set- 
takes precedence over the RDNS/DHCP hostname 
magic.


This patch has a dependency on my other bug/patch: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606515 (Preseed 
installation does not wait for network to be ready)
Because if netcfg/hostname is set, the reverse DNS check is skipped, and the 
chance is higher that the installer attempts to fetch 
the kickstart file before the network link is up  running.


-- 
Yours sincerely,

Floris Bos
diff -ur netcfg.orig1/debian/netcfg-common.templates netcfg/debian/netcfg-common.templates
--- netcfg.orig1/debian/netcfg-common.templates	2009-09-12 16:13:23.0 +0200
+++ netcfg/debian/netcfg-common.templates	2010-12-11 17:20:01.361351304 +0100
@@ -105,6 +105,12 @@
  administrator. If you are setting up your own home network, you can make
  something up here.
 
+Template: netcfg/hostname
+Type: string
+Description: Hostname that can be preseeded.
+ .
+ If specified this disables the automatic detection of the hostname by netcfg.
+
 Template: netcfg/invalid_hostname
 Type: error
 # :sl2:
diff -ur netcfg.orig1/dhcp.c netcfg/dhcp.c
--- netcfg.orig1/dhcp.c	2010-08-06 23:49:44.0 +0200
+++ netcfg/dhcp.c	2010-12-11 23:18:25.841977721 +0100
@@ -473,12 +473,19 @@
 }
 
 /*
- * Default to the hostname returned via DHCP, if any,
+ * If the netcfg/hostname preseed value is set use that
+ * Otherwise default to the hostname returned via DHCP, if any,
  * otherwise to the requested DHCP hostname
  * otherwise to the hostname found in DNS for the IP address
  * of the interface
  */
-if (gethostname(buf, sizeof(buf)) == 0
+debconf_get(client, netcfg/hostname);
+if (!empty_str(client-value))
+{
+strncpy(buf, client-value, sizeof(buf));
+debconf_set(client, netcfg/get_hostname, buf);
+}
+else if (gethostname(buf, sizeof(buf)) == 0
  !empty_str(buf)
  strcmp(buf, (none))
  verify_hostname(buf) == 0
diff -ur netcfg.orig1/static.c netcfg/static.c
--- netcfg.orig1/static.c	2010-08-06 06:32:41.0 +0200
+++ netcfg/static.c	2010-12-12 00:12:44.691551386 +0100
@@ -454,9 +464,28 @@
 GET_GATEWAY : CONFIRM;
 break;
 case GET_HOSTNAME:
-seed_hostname_from_dns(client, ipaddress);
-state = (netcfg_get_hostname(client, netcfg/get_hostname, hostname, 1)) ?
-GET_NAMESERVERS : GET_DOMAIN;
+debconf_get(client, netcfg/hostname);
+if (!empty_str(client-value)) {
+/* Copy preseeded netcfg/hostname to hostname variable and netcfg/get_hostname */
+hostname = strdup(client-value);
+debconf_set(client, netcfg/get_hostname, hostname);
+
+/* FQDN? Then set domain */
+char *s = strchr(hostname, '.');
+if (s  s[1] != '\0') {
+domain = strdup(s + 1);
+debconf_set(client, netcfg/get_domain, domain);
+have_domain = 1;
+*s = '\0';
+}
+state = GET_DOMAIN;
+
+} else {
+seed_hostname_from_dns(client, ipaddress);
+state = (netcfg_get_hostname(client, netcfg/get_hostname, hostname, 1)) ?
+GET_NAMESERVERS : GET_DOMAIN;
+}
+
 break;
 case GET_DOMAIN:
 if (!have_domain) {

Bug#606636: Reverse DNS takes precedence over netcfg/get_hostname

[Floris Bos]

Package: netcfg
Version: 1.46

The value specified using netcfg/get_hostname seems to be ignored, if a 
reverse DNS entry is present for the IP-address of the server being installed.


Seems to be a bit similar to this bug: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=544513 (dhcp returned hostname take precedence on 
netcfg/get_hostname)
Except in my case it seems the reverse DNS hostname is used, instead of the 
DHCP hostname.


I think netcfg/get_hostname should take precendence over everything else.


Yours sincerely,

Floris Bos



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

Bug#606654: Busybox should include arping applet

[Floris Bos]

Package: busybox-udeb
Version: 1.10.2-2

I think the arping applet should be enabled in the Busybox build.
It helps a great deal in debugging general network issues and could be helpful 
to create a solution for some other bugs like:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537271 (network may not be 
usable as soon as link is up)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606515 (Preseed installation 
does not wait for network to be ready)


Yours sincerely,

Floris Bos
--- busybox-1.10.2/debian/config/config.udeb.orig	2010-12-10 16:13:59.0 +0100
+++ busybox-1.10.2/debian/config/config.udeb	2010-12-10 16:14:28.0 +0100
@@ -589,7 +589,7 @@
 # CONFIG_FEATURE_PREFER_IPV4_ADDRESS is not set
 # CONFIG_VERBOSE_RESOLUTION_ERRORS is not set
 # CONFIG_ARP is not set
-# CONFIG_ARPING is not set
+CONFIG_ARPING=y
 # CONFIG_BRCTL is not set
 # CONFIG_FEATURE_BRCTL_FANCY is not set
 # CONFIG_DNSD is not set

Bug#606654: Busybox should include arping applet

[Floris Bos]

Hi,

On Friday, December 10, 2010 05:12:39 pm Ferenc Wagner wrote:
 Floris Bos b...@je-eigen-domein.nl writes:
  I think the arping applet should be enabled in the Busybox build.
  It helps a great deal in debugging general network issues and could be
  helpful to create a solution for some other bugs like:
  
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537271 (network may not
  be usable as soon as link is up)
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606515 (Preseed
  installation does not wait for network to be ready)
 Please read
 http://wiki.debian.org/DebianInstaller/FAQ#Q.3AWhyispingnotavailableinthede
 bugshell
 
 Roughly the same applies to arping.  After all, you can cat /proc/net/arp
 to check whether the gateway has a complete entry.

But wouldn't you need to initiate network communication before an entry in 
/proc/net/arp for the gateway appears?


Right now PXE preseed installations are broken, making Debian unsuitable for 
use by dedicated server providers.
The Debian installer does not wait for the network link to come up (can take 
about 3 seconds on some NICs connected to a standard Gigabit switch),
nor does it take into account that it can take 30 seconds before network 
activity is possible in spanning tree configurations.

A simply 1-line fix if we had arping might be executing between netcfg and 
network-preseed:

arping -f -c 35 $GATEWAY_IP

(wait until you get an ARP reply from the gateway, timeout after 35 
seconds/tries).


I don't think calling wget 35 times, and grepping /proc/net/arp is a clean 
alternative, just to save 4 KB of space.


-- 
Yours sincerely,

Floris Bos



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

Bug#606636: Reverse DNS takes precedence over netcfg/get_hostname

[Floris Bos]

Hi,

On Friday, December 10, 2010 05:17:15 pm Ferenc Wagner wrote:
 Floris Bos b...@je-eigen-domein.nl writes:
  The value specified using netcfg/get_hostname seems to be ignored, if a
  reverse DNS entry is present for the IP-address of the server being
  installed. [...]
  I think netcfg/get_hostname should take precendence over everything else.
 
 Half of the current behaviour is documented in
 http://d-i.alioth.debian.org/manual/en.i386/apbs04.html#preseed-network
 Maybe the idea was to enable skipping the question without specifying a
 fixed name.

Well, if you think people rely on the current behavior because it's partial 
documented, then treat my bug report as a feature request for a preseed option 
to override this behavior.

Not everyone has the power to change their own reverse DNS entries, or it 
might take time to process (send a request to the upstream provider that is 
responsible for the IP block, wait for them to process it, and reload the 
nameserver zonefile).
And people like to be able to choose their own hostname.


-- 
Yours sincerely,

Floris Bos



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

Bug#606636: Reverse DNS takes precedence over netcfg/get_hostname

[Floris Bos]

On Friday, December 10, 2010 09:53:42 pm Ferenc Wagner wrote:
  Not everyone has the power to change their own reverse DNS entries, or it
  might take time to process (send a request to the upstream provider that
  is responsible for the IP block, wait for them to process it, and reload
  the nameserver zonefile).
  And people like to be able to choose their own hostname.
 
 Yeah.  Currently they can either
  1. not preseed it but type in during installation, or
  2. set it in the DNS records.
 Looks like it worked good enough till now.

Guess it wasn't good enough 5 years ago either. :-)
Seems my bug is a duplicate of: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343269


-- 
Yours sincerely,

Floris Bos



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

Bug#606515: Preseed installation does not wait for network to be ready

[Floris Bos]

Package: network-preseed
Version: 1.41


We are experiencing problems automatically installing Debian Lenny on a number 
of dedicated servers using PXE and preseed.
Our setup works correctly with some hardware configurations, while others give 
a Failed to retrieve the preconfiguration file error message.

If we manually press Continue and tell Debian installer to fetch the 
preconfiguration file a second time from the menu, installation does work 
properly.


I suspect the reason it does not work the first time is that Debian installer 
does not bother to wait before the network link is ready, before attempting to 
fetch the preconfiguration file.
When I press alt-F4 and look at the messages it shows:

==
23:15:29 main-menu[1624]: INFO: menu item 'network-preseed' selected
23:15:32 kernel: eth0: Link is up 1000 Mbps Full Duplex Flow control: none
==

So if I understand the messages correctly the network-preseed routine is 
executed 3 seconds before the link is actually up?



We assign a static network configuration to the servers using boot parameters  
like this:

==
kernel http://INSTALL-SERVER/main/installer-
amd64/current/images/netboot/debian-installer/amd64/linux 
netcfg/choose_interface=auto debian-installer/locale=en_US kbd-
chooser/method=us console-keymaps-at/keymap=us netcfg/disable_dhcp=true 
netcfg/get_ipaddress=$ip netcfg/get_netmask=$netmask 
netcfg/get_gateway=$gateway netcfg/get_nameservers=127.0.0.1 
netcfg/get_hostname=$hostname netcfg/get_domain= preseed/url=http://INSTALL-
SERVER/kickstart.php/debian-preseed

(where $ip $netmask $gateway and $hostname is filled in with the information of 
the server being provisioned)
==


KVM over IP screenshot of the error message: 
http://image.bayimg.com/gabigaade.jpg
Screenshot of the messages: http://image.bayimg.com/gabihaade.jpg



Yours sincerely,

Floris Bos



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

Bug#605273: ar5523 fails to compile

[Floris van Vugt]

Package: ar5523
Severity: normal


Hi,
I'm using a USB WLAN adaptor with AR5523 chipset.
I found this very useful description by GeoffSimmons:
http://wiki.debian.org/ar5523
But at step 4 I get an error message:

$ m-a a-i ar5523

(...)
# build module
/usr/bin/make -C /usr/src/modules/ar5523 
KSRC=/lib/modules/2.6.26-2-amd64/build

make[2]: Entering directory `/usr/src/modules/ar5523'
/usr/bin/make -C /lib/modules/2.6.26-2-amd64/build 
SUBDIRS=/usr/src/modules/ar5523 modules

make[3]: Entering directory `/usr/src/linux-headers-2.6.26-2-amd64'
CC [M] /usr/src/modules/ar5523/ar5523.o
/usr/src/modules/ar5523/ar5523.c: In function ‘ar5523_data_rx_cb’:
/usr/src/modules/ar5523/ar5523.c:580: error: implicit declaration of 
function ‘IEEE80211_SKB_RXCB’
/usr/src/modules/ar5523/ar5523.c:580: warning: passing argument 1 of 
‘__memcpy’ makes pointer from integer without a cast
/usr/src/modules/ar5523/ar5523.c:580: warning: passing argument 1 of 
‘__builtin_memcpy’ makes pointer from integer without a cast
/usr/src/modules/ar5523/ar5523.c:581: error: too few arguments to 
function ‘ieee80211_rx_irqsafe’

/usr/src/modules/ar5523/ar5523.c: In function ‘ar5523_data_tx_cb’:
/usr/src/modules/ar5523/ar5523.c:791: error: implicit declaration of 
function ‘IEEE80211_SKB_CB’
/usr/src/modules/ar5523/ar5523.c:791: warning: assignment makes pointer 
from integer without a cast
/usr/src/modules/ar5523/ar5523.c:794: error: dereferencing pointer to 
incomplete type
/usr/src/modules/ar5523/ar5523.c:794: error: ‘IEEE80211_TX_STAT_ACK’ 
undeclared (first use in this function)
/usr/src/modules/ar5523/ar5523.c:794: error: (Each undeclared identifier 
is reported only once
/usr/src/modules/ar5523/ar5523.c:794: error: for each function it 
appears in.)
/usr/src/modules/ar5523/ar5523.c:795: error: too few arguments to 
function ‘ieee80211_tx_status_irqsafe’

/usr/src/modules/ar5523/ar5523.c: In function ‘ar5523_bss_info_changed’:
/usr/src/modules/ar5523/ar5523.c:970: error: ‘BSS_CHANGED_BSSID’ 
undeclared (first use in this function)
/usr/src/modules/ar5523/ar5523.c:975: error: ‘struct ieee80211_bss_conf’ 
has no member named ‘bssid’
/usr/src/modules/ar5523/ar5523.c:975: error: ‘struct ieee80211_bss_conf’ 
has no member named ‘bssid’
/usr/src/modules/ar5523/ar5523.c:1003: error: ‘struct 
ieee80211_bss_conf’ has no member named ‘bssid’
/usr/src/modules/ar5523/ar5523.c:1003: error: ‘struct 
ieee80211_bss_conf’ has no member named ‘bssid’

/usr/src/modules/ar5523/ar5523.c: At top level:
/usr/src/modules/ar5523/ar5523.c:1035: warning: initialization from 
incompatible pointer type
/usr/src/modules/ar5523/ar5523.c:1037: warning: initialization from 
incompatible pointer type
/usr/src/modules/ar5523/ar5523.c:1038: warning: initialization from 
incompatible pointer type
/usr/src/modules/ar5523/ar5523.c:1039: warning: initialization from 
incompatible pointer type
/usr/src/modules/ar5523/ar5523.c:1041: warning: initialization from 
incompatible pointer type

/usr/src/modules/ar5523/ar5523.c: In function ‘ar5523_probe’:
/usr/src/modules/ar5523/ar5523.c:1511: error: ‘struct wiphy’ has no 
member named ‘interface_modes’

make[4]: *** [/usr/src/modules/ar5523/ar5523.o] Fehler 1
make[3]: *** [_module_/usr/src/modules/ar5523] Fehler 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.26-2-amd64'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/usr/src/modules/ar5523'
make[1]: *** [binary-modules] Fehler 2
make[1]: Leaving directory `/usr/src/modules/ar5523'
make: *** [kdist_build] Fehler 2



I'm not sure why this compilation fails.

I'm on Debian lenny and this is my c-compiler:

$ cc --version
cc (Debian 4.3.2-1.1) 4.3.2

Any help would be greatly appreciated!



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

Kernel: Linux 2.6.26-2-amd64 (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




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

Bug#605188: python-omniorb-doc: Use of PYTHONPATH env var in an insecure way

[Floris Bruynooghe]

severity #605188 minor
thanks

This is only in documentation, so I don't think it is RC.

Even then I'm not sure if it should be a bug at all, but I'll leave it
open for now so we can figure out what by the time we upload the next
version.

Regards
Floris

On 27 November 2010 22:45, Sandro Tosi mo...@debian.org wrote:
 Package: python-omniorb-doc
 Version: 3.3-1
 Severity: important
 Tags: security
 User: debian-pyt...@lists.debian.org
 Usertags: pythonpath

 Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
 an insecure way. Those packages do something like:

    PYTHONPATH=/spam/eggs:$PYTHONPATH

 This is wrong, because if PYTHONPATH were originally unset or empty,
 current working directory would be added to sys.path.

 [1] http://lists.debian.org/debian-python/2010/11/msg00045.html

 Your package turns out to ship vulnerable examples or contains
 insecure advices: you can find a complete log at [2].

 [2] http://people.debian.org/~morph/mbf/pythonpath.txt

 Some guidelines on how to fix these bugs: in the case given above, you
 can use something like

    PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}

 (If you don't known this construct, grep for Use Alternative Value
 in the bash/dash manpage.)

 Also, in cases like

   PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH

 or

   PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py

 you shouldn't need to touch PYTHONPATH at all.

 Feel free to contact debian-pyt...@lists.debian.org in case of
 help.







-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#570422: [Pkg-corba-devel] Bug#570422: please package omniorb 4.1.4

[Floris Bruynooghe]

Hi Sylvain

On 25 October 2010 17:12, Sylvain Joyeux sylvain.joy...@m4x.org wrote:
 Even though I'm the submitter, I did not get the followups. However, I can't
 find the package(s) on mentors.debian.net to try them out. Is there
 somewhere I can get them ?

It's ready in our svn repository, just not getting uploaded because
debian is in a freeze currently.  But if you check out the svn you
should be able to build the packages easily.

Regards
Floris


-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#590323: plotutils: new upstream package available

[Floris Bruynooghe]

On Sun, Jul 25, 2010 at 11:51:32PM +0200, Roland Stigge wrote:
 I'm maintaining pstoedit which depends on libplot from plotutils. The Debian
 bug #506086 should be fixed according to the pstoedit upstream maintainer by
 latest libplot 2.6. Therefore, I'm filing this bug as normal, not just
 wishlist.

I've updated the package and the result is at http://devork.be/debian/
(dget http://devork.be/debian/plotutils_2.6-1.dsc) if you'd like to
check it out.

I need to do some more install-upgrade-remove-... testing and will
then ask my usual sponsor if he wants to upload.

Regards
Floris

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#570422: [Pkg-corba-devel] Bug#570422: please package omniorb 4.1.4

[Floris Bruynooghe]

Hi

On Wed, Jun 16, 2010 at 09:03:39PM +0200, trophime wrote:
 Please find a tentative package for version 4.1.4 at
 http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;package=omniorb-dfsg

If you got commit access to our repo would you mind committing the
changes there?  You can always join the team if you'd like to help
out, I'm sure Thomas will gladly give you commit access if you would
like it.  See our alioth page on
https://alioth.debian.org/projects/pkg-corba/

Regards
Floris

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#578784: RM: omniorb -- ROM; Replaced by omniorb-dfsg

[Floris Bruynooghe]

Package: ftp.debian.org
Severity: normal

omniorb4 has been replaced by omniorb-dfsg and all it's binary
packages taken over.  Therefore it is no longer required.

Cheers
Floris



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

Bug#571417: omniorb4: superseded by omniorb-dfsg, should be removed?

[Floris Bruynooghe]

On Thu, Feb 25, 2010 at 02:11:35PM +0100, Lucas Nussbaum wrote:
 Shouldn't this package be removed from Debian? Looks like it is
 superseded by omniorb-dfsg.

omniorb-dfsg provides replacement packages for all of the binary
packages in omniorb4.  It is my understanding from [0] that this makes
omniorb4 an orphan and therefore an explicit request is not required.
But not having much experience with this I might be wrong, so let me
know if I should file an explicit removal request anyway.

Regards
Floris

[0] http://www.debian.org/doc/developers-reference/pkgs.html#removing-pkgs

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#558588: Description of libesd0 should mention alsa support

[Floris Bruynooghe]

Package: libesd0
Version: 0.2.41-6
Severity: wishlist

Hi

Since 0.2.41-6 libesd0 is compiled against alsa (on Linux) and
libesd0-alsa is no longer provided.  It would be nice if the
description of libesd0 mentioned it now uses alsa as I had to find the
changelog to know that I could safely remove libesd0-alsa.

Thanks
Floris


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

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

Versions of packages libesd0 depends on:
ii  esound-common 0.2.41-6   Enlightened Sound Daemon - Common 
ii  libasound21.0.21a-1  shared library for ALSA applicatio
ii  libaudiofile0 0.2.6-7Open-source version of SGI's audio
ii  libc6 2.10.1-7   GNU C Library: Shared libraries

libesd0 recommends no packages.

Versions of packages libesd0 suggests:
ii  esound-clients0.2.41-6   Enlightened Sound Daemon - clients
ii  pulseaudio-esound-compat [eso 0.9.19-2   PulseAudio ESD compatibility layer

-- 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#550629: python-pyorbit-omg and python-omniorb-omg: error when trying to install together

[Floris Bruynooghe]

On Sun, Oct 11, 2009 at 06:25:24PM +0200, Ralf Treinen wrote:
 This is a serious bug as it makes installation fail. Possible
 solutions are to have the two packages conflict, to rename the common
 file in one of the two packages, or to remove the file from one
 package and have this package depend on the other package. File
 diversions or a Replace relation are another possibility.

Looking at the contents of both packages I think they should conflict.
I will add this for the next version of python-omniorb-omg in our svn
repo, with a note in the package description explaining this.

Regards
Floris


-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#541249: [Pkg-corba-devel] Bug#541249: omnievents: Incorrect runlevels in init.d LSB header

[Floris Bruynooghe]

On Fri, Sep 18, 2009 at 06:48:40PM +0200, Petter Reinholdtsen wrote:
 Hi.  Any hope of having this fixed soon?  Let me know if I should not
 NMU to get a fix into the archive.

I've never worked on omnievents, but both me and Thomas seem to have
exceedingly little time to work on pkg-corba recently so I reckon an
NMU might be the best (with a delayed queue in case Thomas rejects
maybe).

Regards
Floris

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



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

Bug#545587: python-codespeak-lib: py.test manpage out of date

[Floris Bruynooghe]

Package: python-codespeak-lib
Version: 1.0.1-1
Severity: minor

Hello

The py.test manual page included is no longer accurate for the 1.0
verion.  Updating it from the --help output might be helpful.

Thanks
Floris


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

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

Versions of packages python-codespeak-lib depends on:
ii  python-support1.0.3  automated rebuilding support for P
ii  python2.4 2.4.6-2An interactive high-level object-o

python-codespeak-lib recommends no packages.

Versions of packages python-codespeak-lib suggests:
ii  ghostscript8.70~dfsg-2   The GPL Ghostscript PostScript/PDF
pn  graphviz   none(no description available)
ii  ps2eps 1.64-6convert PostScript to EPS (Encapsu
ii  rsync  3.0.6-1   fast remote file copy program (lik
ii  screen 4.0.3-14  terminal multiplexor with VT100/AN
ii  subversion 1.6.3dfsg-1   Advanced version control system
ii  texlive2007.dfsg.2-4 TeX Live: A decent selection of th

-- 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#505453: perl-tk: memory corruption, aborted

[Floris Jan Sicking]

Package: perl-tk
Version: 1:804.027-7
Severity: important



---
#!/usr/bin/perl

use Tk;
use strict;
use warnings;

my $mw = MainWindow-new;
my $f = $mw-Frame-pack;
my $ff = $f-Frame-pack;

$ff-Entry-pack;
$ff-Button-pack;

$mw-idletasks;
# $f-idletasks;
# $ff-idletasks;

MainLoop();


Program ends with:

*** glibc detected *** malloc(): memory corruption: 0x008edbf0 ***
Aborted

I know memory leaks in Tk are a known problem, but this program seems
so simple I thought it might help.

Kind regards,

Floris Jan Sicking

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)

Versions of packages perl-tk depends on:
ii  libc6  2.3.6.ds1-13etch7 GNU C Library: Shared libraries
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  libpng12-0 1.2.15~beta5-1PNG library - runtime
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  perl   5.8.8-7etch3  Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.8 5.8.8-7etch3  The Pathologically Eclectic Rubbis
ii  zlib1g 1:1.2.3-13compression library - runtime

perl-tk recommends no packages.

-- no debconf information



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