Bug#1034111: Data point: WLAN stable after bluetooth removal

[Steinar Bang]

I removed bluetooth support from the laptop on April 10 2023, and WLAN
provided by the Mediatek 7921 chip has been working flawlessly since
then for, at the time of writing, 28 days, with numerous suspends and
resumes. 

To me this strongly indicates that using bluetooth was the problem,
especially since it seems to be provided by the Mediatek 7921 chip as
well.

Note that I'm also running the Mx Master mouse, using the provided USB
plug instead of using bluetooth.  That also works flawlessly.

(Nevertheless: I have other bluetooth devices so it would be nice to get
bluetooth on this laptop, that doesn't make WiFi stop working)

I removed bluetooth support by removing all packages with "blue" in
their name, with the exception of libbluetooth3 (I initially uninstalled
that as well, but that pulled out network-manager as well, so I had to
put it back in).

These are the packages I "apt remove"'d:

apt remove bluez bluez-obexd gnome gnome-bluetooth gnome-core 
pulseaudio-module-bluetooth task-gnome-desktop \
 qml-module-org-kde-bluezqt:amd64 libkf5bluezqt6:amd64 libkf5bluezqt-data 
libgnome-bluetooth13:amd64 gir1.2-gnomebluetooth-1.0:amd64

Bug#1034111: The driver for the Mediatek 7921 chip

[Steinar Bang]

I think this is the driver for the WiFi part of the Mediatek 7921 chip:
 
https://github.com/torvalds/linux/tree/master/drivers/net/wireless/mediatek/mt76/mt7921

No idea if this also is the home of the bluetooth driver, but I suspect
it is, because I couldn't find any mention of the 7921 chip elsewhere.

Bug#1034111: linux-image-6.1.0-0.deb11.5-amd64: Using bluetooth makes wifi stop working after a while ("a while" may be hours or it may be days)

[Steinar Bang]

Package: src:linux
Version: 6.1.12-1~bpo11+1
Severity: normal
X-Debbugs-Cc: s...@dod.no

Dear Maintainer,

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

   * What led up to the situation?

I bought a Logitech MX Master 3S wireless mouse.
The mouse came with both an USB dongle and the possibility of using bluetooth.
I installed blueman with "apt install blueman".
A bluetooth icon appeared on the top menu bar on my MATE desktop, and I was
able to discover and use the MX Master mouse.

Everything worked find until the network suddenly disappeared.
The NIC still showed up on lspci, but the WLAN NIC was gone from "ifconfig"
output.

I was able to plug the laptop into a wired network and that worked perfectly,
but the WLAN NIC didn't work.

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

What I did that was ineffective:
1. restart the networking with "systemctl restart networking"
2. reboot the computer

For these nothing changed. I.e. the network was still gone.

What I did that was effective:
1. Shut the computer down and start it again

This worked: after reboot the wireless network came back.

Since the first time this happened I first tried stopping to use the mouse, but
leave the bluetooth support in place, and after a couple of days, the same
thing happened again: the wireless NIC died.

I then removed blueman "apt remove blueman" and that seemed to take much of the
bluetooth support away. And then the laptop ran for over a week without the
wireless NIC going away.

I reinstalled blueman and started using the mouse again and since then the
computer has run for a while before the wireless NIC dies. What I do then is
power the laptop down and power it back up, and then it runs for a new while
(hours to days) before the NIC goes away.

The reason I suspect a connection between bluetooth and wireless NIC is that
this didn't happen for the 7 months I've had the laptop until I started using
bluetooth, and because both bluetooth and WLAN is handled by the same MEDIATEK
Corp. MT7921 chip.


-- Package-specific info:
** Version:
Linux version 6.1.0-0.deb11.5-amd64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP PREEMPT_DYNAMIC Debian 6.1.12-1~bpo11+1 (2023-03-05)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-0.deb11.5-amd64 
root=UUID=9748403e-c93c-4785-b6bb-70be61aa3749 ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Acer
product_name: Aspire A515-45
product_version: V1.10
chassis_vendor: Chassis Manufacturer
chassis_version: Chassis Version
bios_vendor: INSYDE Corp.
bios_version: V1.10
board_vendor: LN
board_name: Calla_LC
board_version: V1.10

** Loaded modules:
usbhid
ctr
ccm
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
binfmt_misc
bnep
squashfs
nls_ascii
nls_cp437
loop
vfat
fat
mt7921e
intel_rapl_msr
mt7921_common
intel_rapl_common
btusb
edac_mce_amd
btrtl
mt76_connac_lib
btbcm
btintel
kvm_amd
btmtk
mt76
bluetooth
joydev
kvm
mac80211
irqbypass
snd_hda_codec_realtek
libarc4
jitterentropy_rng
snd_hda_codec_generic
ghash_clmulni_intel
ledtrig_audio
uvcvideo
sha512_ssse3
cfg80211
sha512_generic
videobuf2_vmalloc
snd_hda_codec_hdmi
videobuf2_memops
videobuf2_v4l2
drbg
videobuf2_common
snd_hda_intel
ansi_cprng
snd_intel_dspcfg
acer_wmi
snd_intel_sdw_acpi
videodev
ecdh_generic
snd_hda_codec
sparse_keymap
aesni_intel
snd_hda_core
snd_pci_acp6x
ecc
mc
snd_hwdep
crypto_simd
snd_pci_acp5x
cryptd
snd_pcm
rapl
wmi_bmof
snd_rn_pci_acp3x
snd_timer
snd_acp_config
ccp
snd_soc_acpi
snd
wdat_wdt
rfkill
sp5100_tco
k10temp
pcspkr
soundcore
snd_pci_acp3x
rng_core
watchdog
acer_wireless
acpi_cpufreq
ac
hid_multitouch
evdev
serio_raw
msr
parport_pc
ppdev
lp
parport
fuse
efi_pstore
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
amdgpu
gpu_sched
drm_buddy
i2c_algo_bit
drm_display_helper
nvme
cec
xhci_pci
rc_core
ahci
xhci_hcd
nvme_core
drm_ttm_helper
libahci
ttm
t10_pi
libata
drm_kms_helper
usbcore
r8169
crc64_rocksoft
crc64
crc_t10dif
realtek
crct10dif_generic
hid_generic
mdio_devres
crct10dif_pclmul
drm
scsi_mod
crc32_pclmul
crc32c_intel
libphy
i2c_piix4
scsi_common
usb_common
crct10dif_common
battery
i2c_hid_acpi
video
i2c_hid
hid
wmi
button

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel state 
DOWN group default qlen 1000
link/ether c0:18:50:91:da:3e brd ff:ff:ff:ff:ff:ff
3: wlp4s0:  mtu 1500 

Bug#1018265: Info received (Bug#1018265 closed by Brian Potkin (cups picks manual tray on HP Color LaserJet M252dw))

[Steinar Bang]

To summarize for a future googler that ends up here.

The printer in question is an HP Color LaserJet from 2014, with dual
sided printing and colour.  The printer has an onboard NIC and natively
supports PostScript and IPP.

Windows PCs and iDevices can print directly to this network printer and
do not need to use the CUPS printer, so there is no need to export the
printer from CUPS.

Tip: it might be an idea to lock the printer's MAC addres to a fixed
IPv4 address in your router's DHCP server (otherwise you may have to
reinstall the printer on windows machines, because windows printer
drivers are locked to a particular IP address and stops working if the
printer gets a new address).

With CUPS it is possible to use two drivers for this printer
 1. "driverless"[1] (part of the cups-filters-core-drivers package[2])
 2. "hplip"[3]

To summarize:
 1. The driverless driver sort, of, kind of works, but doesn't support
PostScript and sometimes picks the wrong tray (the manual feed
slot), and there is no way to select what tray to use. But colour
and dual sided printing both works
 2. The hplip driver works, lets you select the tray and prints dual
sided.  But the hplip printer doesn't print colour from a webkit
based browser (chromium and vivaldi on my debian system).  The hplip
printer prints colour fine from the Atril PDF viewer, from firefox
and from libreoffice 

The driverless driver builds and regenerates the PPD from the networked
printer itself.  So any edits you try to make to the PPD is overwritten
(I found an edit of the tray names in the PPD when googling for similar
problems and found out that the edit I tried to make just disappeared).

The driverless printer installs itself, sort of.  Or at least it
reinstalls itself when deleted, once installed.

On my computer the driverless printer shows up in printer dialogs, as:
 HP_Color_LaserJet_Pro_M252dw_501595_

The hplip driver shows up in printer dialogs, as:
 HP_Color_LaserJet_Pro_M252dw

The installation of the hplip printer was as follows:
 1. Clicked on "Find New Printer"
 2. 3 printers appeared:
1. Virtual Braille BRF Printer (CUPS-BRF)
2. Hewlett-Packard HP Color LaserJet Pro M252dw (Hewlett-Packard HP Color 
LaserJet Pro M252dw (driverless))
3. HP Color LaserJet Pro M252dw (HP Color LaserJet Pro M252dw)
 3. Clicked on "Add This Printer" next to "HP Color LaserJet Pro M252dw (HP 
Color LaserJet Pro M252dw)"
 4. Added name, description and location
 5. Under "Make" selected "HP" and clicked "Continue"
 6. Under "Model" there were 13 lines of "HP Color LaserJet PRO M252 Postscript 
(recommended) (en)"
 7. Selected the first to the 13 lines and clicked on "Add Printer"
 8. Changed "Printer Options" from
  | Media size | Letter|
  | Two-sided  | off   |
  | Paper feed | Automatic |
to
  | Media size | A4|
  | Two-sided  | Long-edge binding |
  | Paper feed | Automatic |
 9. Seleced the tab "Options Installed" and switched "Duplex Unit" to "on"
10. Clicked "Set Default Options"


References
 [1] 
 [2] 
 [3] 

Bug#1018265: closed by Brian Potkin (cups picks manual tray on HP Color LaserJet M252dw)

[Steinar Bang]

> "Debian Bug Tracking System" :

> The thread beginning at

>   https://lists.cups.org/pipermail/cups/2022-December/075172.html

> indicates that this issue is now resolved. Hence closing.

Personally I won't say that I see it as resolved, yet.

It won't be, until I get predictable behaviour, and I don't have that, yet.

Bug#1018265: cups picks manual tray on HP Color LaserJet M252dw

[Steinar Bang]

> Brian Potkin :

> Please take this issue upstream:

>   https://github.com/OpenPrinting/cups-filters/issues

> would be worth a try. A short explanation of the issue plus a link
> to the Debian bug report should be sufficient.

Ok done!

The cups-filters issue, is:
 https://github.com/OpenPrinting/cups-filters/issues/478

Bug#1018265: Tried fix from cups-filters issue #193, but it didn't work

[Steinar Bang]

I tried the fix in https://github.com/OpenPrinting/cups-filters/issues/193
but it didn't work.

What I did was:
 1. Edit /etc/cups/ppd/HP_Color_LaserJet_Pro_M252dw_501595_.ppd with the
following changes:

--- HP_Color_LaserJet_Pro_M252dw_501595_.ppd2022/08/28 10:29:57 1.1
+++ HP_Color_LaserJet_Pro_M252dw_501595_.ppd2022/08/28 10:47:19
@@ -144,8 +144,8 @@
 *DefaultInputSlot: Auto
 *InputSlot Auto/Automatic: "<>setpagedevice"
 *InputSlot Manual/Manual: "<>setpagedevice"
-*InputSlot Tray1/Tray 1: "<>setpagedevice"
-*InputSlot Tray2/Tray 2: "<>setpagedevice"
+*InputSlot Tray-1/Tray 1: "<>setpagedevice"
+*InputSlot Tray-2/Tray 2: "<>setpagedevice"
 *CloseUI: *InputSlot
 *% ColorModel from urf-supported
 *OpenUI *ColorModel/Print Color Mode: PickOne

 2. Restart cups with
 systemctl restart cups

 3. Try printing a testpage from the printers properties, with the
printer's media source set to "Automatic" (the default)

 4. The printer was waiting for the manual tray/slot to be fed, and "OK"
to be pressed on the front panel

 5. I fed the printer a sheet of paper and pressed "OK"

 6. I selected "Tray 2" as the media source and pressed "Apply"

 7. I tried printing a test page

 8. Again the printer was waiting for the manual tray/slot to be fed,
and "OK" to be pressed on the front panel

 9. I fed the printer a sheet of paper and pressed "OK"

10. I selected "Tray 1" as the media source and pressed "Apply" (just to
have tried it)

11. Again the printer was waiting for the manual tray/slot to be fed,
and "OK" to be pressed on the front panel

When I checked the diffs again after the experiment, I found that my
changes to /etc/cups/ppd/HP_Color_LaserJet_Pro_M252dw_501595_.ppd
had been overwritten.

Bug#1018265: Possibly related: debian bug 949315

[Steinar Bang]

Related bug info:

When I googled the problem I ended up in debian bug 949315, which is
closed and fixed, and as far as I can tell, was fixed in cups 2.3.3op1,
and bullseye is 2.3.3op2.

The way I found debian bug 949315, was:

I first found cups-filters issue 
https://github.com/OpenPrinting/cups-filters/issues/193

cups-filters issue 193 linked to a cups issue 
https://github.com/apple/cups/issues/5740

cups-filters #193 has a fix attached that was rejected, because there
was a fix in cups.

cups issue #5470 in turn, linked to a debian pull request 
https://github.com/OpenPrinting/cups/pull/23

pull request #23 refers to: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949315

And bug 949315 is closed as fixed.

The pull request had milestone v2.3.3op1 so that's why I'm guessing the
fix came in 2.3.3op1.

Bug#1018265: cups picks manual tray on HP Color LaserJet M252dw

[Steinar Bang]

Package: cups
Version: 2.3.3op2-3+deb11u2
Severity: important
X-Debbugs-Cc: s...@dod.no

Dear Maintainer,

When printing, the printer picks what it calls "Tray 1", which is a slot in the
front of the printer, where sheets can be fed one at a time. After feeding a
sheet in, I have to press "OK" on the printer's front panel display.

This has to be repeated for each sheet printed and makes it cumbersome to use
the printer.

I have opened "System->Administration->Print Settings" from the debian menu.

I have double clicked on the printer HP_Color_LaserJet_Pro_M252dw_501595_

In "Printer Properties"->"Print Options" there is the setting "Media source".

"Media source" is a dropdown with the values
 Automatic
 Manual
 Tray 1
 Tray 2

I have tried the settings "Automatic" (the default) and "Tray 1" and
"Tray 2" and all of them uses the manual tray, which the printer display
calls "Tray 1".

There was no change. The printer still printed from the manual tray

I had expected "Tray 2" and "Automatic" to pick "Tray 2", which is the regular
paper tray.

Cups report the printer as HP Color LaserJet Pro M252dw, driverless, cups-
filters 1.28.7 (so driverless.ppd is in use. This is a network printer with
PostScript).

I don't know when this behaviour started, but I can't remember needing to feed
paper manually in December/November 2021, when I printed the Christmas letters.

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

Kernel: Linux 5.18.0-0.deb11.3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client2.3.3op2-3+deb11u2
ii  cups-common2.3.3op2-3+deb11u2
ii  cups-core-drivers  2.3.3op2-3+deb11u2
ii  cups-daemon2.3.3op2-3+deb11u2
ii  cups-filters   1.28.7-1+deb11u1
ii  cups-ppdc  2.3.3op2-3+deb11u2
ii  cups-server-common 2.3.3op2-3+deb11u2
ii  debconf [debconf-2.0]  1.5.77
ii  ghostscript9.53.3~dfsg-7+deb11u2
ii  libavahi-client3   0.8-5
ii  libavahi-common3   0.8-5
ii  libc6  2.31-13+deb11u3
ii  libcups2   2.3.3op2-3+deb11u2
ii  libgcc-s1  10.2.1-6
ii  libstdc++6 10.2.1-6
ii  libusb-1.0-0   2:1.0.24-3
ii  poppler-utils  20.09.0-3.1
ii  procps 2:3.3.17-5

Versions of packages cups recommends:
ii  avahi-daemon  0.8-5
ii  colord1.4.5-3

Versions of packages cups suggests:
pn  cups-bsd   
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
pn  smbclient  
ii  udev   247.3-7

-- debconf information:
  cupsys/raw-print: true

Bug#1016570: bullseye on Acer Aspire 5 A515-45

[Steinar Bang]

Package: installation-reports

Boot method: Network
Image version: 
https://deb.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/netboot.tar.gz
Date: 2022-07-29 Fri 20:57

Machine: Acer Aspire 5 A515-45
Processor: AMD Ryzen 5 5500U
Memory: 16GB
Partitions: 
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   78161520   7816152   0% /dev
tmpfs  tmpfs  1578492 1532   1576960   1% /run
/dev/nvme0n1p2 ext4 467576360 15028116 428723248   4% /
tmpfs  tmpfs  7892448   174984   7717464   3% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
/dev/nvme0n1p1 vfat523248 3484519764   1% /boot/efi
tmpfs  tmpfs  1578488  104   1578384   1% /run/user/1000

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root 
Complex [1022:1630]
Subsystem: Acer Incorporated [ALI] Renoir Root Complex [1025:152b]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU 
[1022:1631]
Subsystem: Acer Incorporated [ALI] Renoir IOMMU [1025:152b]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP 
Bridge [1022:1633]
Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP 
Bridge [1022:1634]
Kernel driver in use: pcieport
00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP 
Bridge [1022:1634]
Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP 
Bridge [1022:1634]
Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal 
PCIe GPP Bridge to Bus [1022:1635]
Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal 
PCIe GPP Bridge to Bus [1022:1635]
Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 51)
Subsystem: Acer Incorporated [ALI] FCH SMBus Controller [1025:152b]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
[1022:790e] (rev 51)
Subsystem: Acer Incorporated [ALI] FCH LPC Bridge [1025:152b]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 0 [1022:1448]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 1 [1022:1449]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 2 [1022:144a]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 3 [1022:144b]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 4 [1022:144c]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 5 [1022:144d]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 6 [1022:144e]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 
24: Function 7 [1022:144f]
02:00.0 Non-Volatile memory controller [0108]: SK hynix Device [1c5c:174a]
Subsystem: SK hynix Device [1c5c:174a]
Kernel driver in use: nvme
Kernel modules: nvme
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Acer Incorporated [ALI] RTL8111/8168/8411 PCI Express 
Gigabit Ethernet Controller [1025:152b]
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7961]
Subsystem: Lite-On Communications Inc Device [11ad:3802]
Kernel driver in use: mt7921e
Kernel modules: mt7921e
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Lucienne [1002:164c] (rev c2)
Subsystem: Acer Incorporated [ALI] Device [1025:152b]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
05:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Acer Incorporated [ALI] Device [1025:152b]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
05:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 
17h (Models 10h-1fh) Platform 

Bug#881297: Summary: The state of the existing karaf debian package

[Steinar Bang]

Update to the state of the karaf-debian package:
 https://github.com/steinarb/karaf-debian

The following fixes/improvements have been made:
 1. I've run lintian with the following argument and fixed all of the
complaints:
 lintian -vIiE --pedantic --color=auto karaf*.changes 
karaf_4.1.4-10~9.30_all.deb

 2. I've corrected the ownership of /etc/karaf:
- The ownership has been changed from karaf.karaf to root.karaf
- The mode has been set to 2770 on /etc/karaf/ itself (karaf,
  running as user karaf, must be allowed to create new .cfg files in
  this directory)
- Set ownership root.karaf and mode 2750 on all files in /etc/karaf/
  except for the .cfg files and config.properties
- Set ownership karaf.karaf and mode 2770 on all of the .cfg files
  and config.properties, because karaf needs to be able to write to
  them

 3. Moved KARAF_HOME to /var/lib/karaf and let /usr/share/karaf/ have
ownership root.root.
$KARAF_HOME/bin, $KARAF_HOME/lib and $KARAF_HOME/system are all
symlinks to /usr/share/karaf/

 4. Added SYSV init.d files
Note: these are not extensively tested, because the only way I had
to test them was to build .deb packages with the systemd stuff
removed and try to install them and see that the daemon started, and
that was a lot of work

 5. Moved karaf.log from $KARAF_DATA/log/ to /var/log/karaf/

 6. Bumped the upstream karaf version from 4.1.4 to 4.1.5

Bug#881297: Summary: The state of the existing karaf debian package

[Steinar Bang]

>>>>> Steinar Bang <s...@dod.no>:

> I believe the following steps are needed to make this an official
> package:
>  1. Replace the remaining non-karaf boot jars with debian packages,
> these packages are:
> a. apache felix framework 5.6.10
>- Already a debian package, but currently in version 4.6.12 in
>  stretch, testing and unstable [3]

I've filed a bug to have this updated:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890143

> b. apache felix metatype 1.1.6 [4]

I've filed an RFP for this package:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890144

> c. apache felix configadmin 1.8.16 [5]

I've filed an RFP for this package:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890145

> d. apache felix file install 3.6.4 [6]

I've filed an RFP for this package:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890146

> e. OPS4J PAX URL Aether 2.5.3 [7]

I've filed an RFP for the parentt projec for this package:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890181

> f. OPS4J PAX Logging API 1.10.1 [8]
> g. OPS4J PAX Logging Log4J2 1.10.1 [9]

I've filed an RFP for the parent project for these two packages:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890182

Bug#890182: RFP: libpax-logging -- OSGi logging support

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: libpax-logging
  Version : 1.10.1
  Upstream Author : Alin Dreghiciu 
* URL : https://github.com/ops4j/org.ops4j.pax.logging
* License : Apache v. 2
  Programming Lang: Java
  Description : OSGi logging support

The logging support in the standard Log Service of the OSGi specification is
minimalistic and not entirely suitable for enterprise applications. This
project tries to address this by extending the standard interface with
additional interfaces and using a strong logging backend, the Apache Log4J. Pax
Logging defines its own API, but more importantly it supports the Log4J and
Jakarta Commons Logging APIs as well, making it easy to create bundles that use
these common APIs, either directly in new code or indirectly from inside 3rd
party libraries.

This library is a requirement for having a debian package of apache karaf.  See
this URL for details:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30

Bug#890181: RFP: libpax-url -- URL stream handlers for OSGi

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: libpax-url
  Version : 2.5.3
  Upstream Author : Alin Dreghiciu 
* URL : https://github.com/ops4j/org.ops4j.pax.url
* License : Apache v.2
  Programming Lang: Java
  Description : URL stream handlers for OSGi


OPS4J Pax URL is a set of URL handlers mainly targeting OSGi URL Handler
Service but which can be used in a standard Java environment.

This library is a requirement for a debian package for apache karaf.  See this
URL for details:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30

Bug#890146: RFP: libfelix-fileinstall -- File Install is a directory based OSGi management agent.

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: libfelix-fileinstall
  Version : 3.6.4
  Upstream Author : d...@felix.apache.org
* URL : http://felix.apache.org/documentation/subprojects/apache-
felix-file-install.html
* License : Apache v.2
  Programming Lang: Java
  Description : File Install is a directory based OSGi management agent.

File Install is a directory based OSGi management agent. It uses a directory in
the file system to install and start a bundle when it is first placed there. It
updates the bundle when you update the bundle file in the directory and, when
the file is deleted, it will stop and uninstall the bundle.

This java library is a requirement for creating a debian package of apache
karaf.  See this URL for details:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30

Bug#890145: RFP: libfelix-configadmin -- An implementation of the OSGi Componendium Configuration Admin Service

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: libfelix-configadmin
  Version : 1.8.16
  Upstream Author : d...@felix.apache.org
* URL : http://felix.apache.org/documentation/subprojects/apache-
felix-config-admin.html
* License : Apache v.2
  Programming Lang: Java
  Description : An implementation of the OSGi Componendium Configuration
Admin Service

The OSGi Componendium Configuration Admin Service specifies a service, which
allows for easy management of configuration data for configurable components.
Basicaly configuration is a list of name-value pairs. Configuration is managed
by management applications by asking the Configuration Admin Service for such
configuration. After updating the configuration, it is sent back to the
Configuration Admin Service. The Configuration Admin Service is like a central
hub, which cares for persisting this configuration and also for distributing
the configuration to interested parties. One class of such parties are the
components to be configured. These are registered as ManagedService services.
There is also a notion of ManagedServiceFactory, which allows for multiple
configurations of the same kind to be applied.

This Java library is a requirement for a debian package for apache karaf. See
this URL for details:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30

Bug#890144: RFP: libfelix-metatype -- An implementation of the OSGi metatype specification

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: libfelix-metatype
  Version : 1.1.6
  Upstream Author : d...@felix.apache.org
* URL : http://felix.apache.org/documentation/subprojects/apache-
felix-metatype-service.html
* License : Apache v.2
  Programming Lang: Java
  Description : An implementation of the OSGi metatype specification.

The OSGi Metatype specification provides a unified way to describe metadata
about services and a Java interface to retrieve and manipulate such
information. This information can optionally be localized, thus allowing the
developer to provide human-readable metadata descriptions in multiple
languages. The specification defines a rich dynamic typing system to describe
service attributes in a precise way, which makes it possible to dynamically
create user interfaces to configure services.

This package is a requirement for having an apache karaf debian package.  See
this URL for more information:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30

Bug#890143: felix-framework: apache karaf needs newer vesion of the felix framework

[Steinar Bang]

Source: felix-framework
Version: 4.6.1-2
Severity: normal

Dear Maintainer,

I'm working on a debian package for the apache karaf RFP

Apache Karaf 4.1.4 needs felix framework 5.6.10, and the debian package is
currently at 4.6.1.

See this link for details on the current state of the karaf package:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#30



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

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

Bug#881297: Summary: The state of the existing karaf debian package

[Steinar Bang]

My own karaf debian package[1] is now in a state where it does what I
need for my own use.  I'm serving the package from my own unofficial APT
repository (which I will discontinue if this RFP results in an official
karaf package).

I don't plan to do any more work on this packaging, except what is
needed to make new stable karaf releases run (ie. I will roll a new
version of the package when karaf 4.1.5 is out).

I'm leaving some notes on the current state of the packaging here
(ie. in the mailing list archives) in case someone wants to use this
package as a starter for an official package.  I will send a message to
the RFP with the same information.

The current state of the karaf debian package, is:
 1. The package is created using native debian packaging tools

 2. The package is built from the source tarball of karaf releases

 3. The source is built with maven and openjdk-8

 4. lintian no longer gives any warnings on the package (I have only run
lintian with "lintian karaf_xxx.deb", I haven't tried with any
arguments)

 5. The package creates a system user named karaf, with group karaf, and
home directory /var/lib/karaf

 6. A karaf service is added to systemd, running as user karaf and
logging to /var/log/syslog and using the following directories:
 KARAF_ETC = /etc/karaf/
 KARAF_HOME = /usr/share/karaf/
 KARAF_DATA = /var/lib/karaf/data/
all directories are owned by user karaf, group karaf

 7. The karaf package works with "apt-get dist-upgrade", config changes
in KARAF_ETC gets the usual APT dialog on modified config change
(ie. "user the package maintainer's version or the modified file
from the old version?), the karaf cache is flushed during an
upgrade, which means that all installed features are lost and must
be reinstalled, contents in KARAF_ETC not installed by the karaf
package is untouched

 8. Those karaf boot requirements that could be satisfied by current
debian stable (debian 9, stretch) uses debian dependencies:
 - Java 8 RE
 - OSGi core 6
 - libjna-java (not strictly needed, but part of the boot directory)
 - libjansi-java
   - This one can be used as a pattern for how to setup
 startup.properties dependencies, the changes are[2]
 a. Add a debian dependency to the control file
 b. Replace the jansi version number with "debian" in
$KARAF_ETC/startup.properties
 c. Remove jansi from the $KARAF_HOME/system maven repository
 d. Symlink the "debian" version from debian's maven repository
into the $KARAF_HOME/system repository
 
 9. The jar files that make up karaf are structured as a maven
repository under $KARAF_HOME/system

10. The initial boot is done from the jar files found in
$KARAF_HOME/lib/boot/ (I have replaced non-karaf dependencies here
with symlinks to the jar files of debian packages)

11. The jar files needed to boot to a state where karaf can start
downloading dependencies from maven central (or other maven
repositories), are listed in $KARAF_ETC/startup.properties

12. The $KARAF_HOME/system maven repository has been cleaned for files
not built by source that aren't needed for karaf boot.  The
non-karaf jar files currently in there are needed for boot, and
cannot be satisfied by existing debian java packages


I believe the following steps are needed to make this an official
package:
 1. Replace the remaining non-karaf boot jars with debian packages,
these packages are:
a. apache felix framework 5.6.10
   - Already a debian package, but currently in version 4.6.12 in
 stretch, testing and unstable [3]
b. apache felix metatype 1.1.6 [4]
c. apache felix configadmin 1.8.16 [5]
d. apache felix file install 3.6.4 [6]
e. OPS4J PAX URL Aether 2.5.3 [7]
f. OPS4J PAX Logging API 1.10.1 [8]
g. OPS4J PAX Logging Log4J2 1.10.1 [9]
 2. Restructure karaf into two packages, karaf and libkaraf-java, with
libkaraf-java containing the jar files structured like debian java
packages (ie. in /usr/share/maven-repo both with their actual
version and with the "debian" version).
IMO I'm not sure if this is worth the effort, because the karaf jar
files aren't really meaningful outside of karaf, or in a version
independent manner


Thanks in advance to anyone who will create an official debian package,
whether it is based on my package or not! :-)


- Steinar


References:
 [1] 
 [2] 

 [3] 
 [4] 

 [5] 

 [6] 

 [7] 

Bug#881297: An apache karaf debian package made with native debian packaging tools

[Steinar Bang]

I have written a new debian package that
 1. Uses native debian tools to create the package, instead of fpm
 2. Builds from an apache karaf source tarbal instead of from an apache
karaf binary tarball (like the fpm package mentioned earlier in this
issue does)

The new apache karaf debian package is here:
 https://github.com/steinarb/karaf-debian

Other improvements to the fpm package
 1. Simpler maintscripts written from scratch (I inherited the scripts
in the fpm package, from the package I forked on github, and just
modified them as needed)
 2. The new package works with "apt-get dist-upgrade", the fpm package
didn't (the fix was that I needed to remove the old karaf's OSGi
bundle cache during the upgrade)

I followed the plan outlined below and stopped at step 5 (where the
package became usable to me, as a replacement for the fpm package).



Here's the plan I worked after:
 1. Download the sources and build them with maven
 2. Create the directories that will receive the built karaf stuff:
 mkdir -p /etc/karaf
 mkdir -p /usr/share/karaf
 mkdir -p /var/lib/karaf
 3. Move the built stuff in unpacked-src/assemblies/apache-karaf/target/assembly
to the appropriate places the final structure
a. mv unpacked-src/assemblies/apache-karaf/target/assembly/bin to 
/usr/share/karaf
b. mv unpacked-src/assemblies/apache-karaf/target/assembly/data to 
/var/lib/karaf
c. mv unpacked-src/assemblies/apache-karaf/target/assembly/deploy to 
/var/lib/karaf
d. mv unpacked-src/assemblies/apache-karaf/target/assembly/etc/* to 
/etc/karaf
e. mv unpacked-src/assemblies/apache-karaf/target/assembly/lib to 
/usr/share/karaf
f. mv unpacked-src/assemblies/apache-karaf/target/assembly/system to 
/usr/share/karaf
 4. Create a systemd config that sets up the appropriate environment variables 
before 
starting the karaf daemon
  KARAF_BASE=/usr/share/karaf
  KARAF_ETC=/etc/karaf
  KARAF_DATA=/var/lib/karaf/data
 5. Create postinst and postrm scripts that creates/removes a karaf user
(and group) and sets up and removes the systemd daemon
 6. Replace all of the non org.apache.karaf.*.jar needed for boot with
deb dependencies
 7. Move the org.apache.karaf.*.jar part of /usr/share/karaf/system to
/usr/share/maven-repository and use this as the system repo in karaf

Bug#881297: Notes on how karaf starts and what dependencies are needed

[Steinar Bang]

 1. Karaf boots from a small kernel and the rest are pulled in, and
started, using maven.  Maven initially looks to a maven repository
in the karaf distro (the "system" repository), if it doesn't find
what it looks for there, it moves on to maven central and a couple
of other maven repositories (the list of repositores can be modified
at runtime, using commands in the karaf console)

 2. Karaf is started by the karaf script
 
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf

 3. The script uses environment variables that could be set from the
outside (e.g. in a systemd control file or a sysv init script) to
make karaf use other directories:
 KARAF_ETC
 KARAF_DATA
 KARAF_HOME
there used to be a point in setting the KARAF_LOG directory as well
(in my own debian package I had it set to /var/log/karaf in the
4.0.x series of karaf), but logging is now handled by the pax
logging JUL (which I guess is "java.util.logging") handler, and in
debian with openjdk ends up in /var/log/syslog and KARAF_LOG is no
longer used in the karaf script
Suggested values for the environment variables:
 KARAF_HOME=/usr/share/karaf (or maybe /usr/share/java/karaf ?)
  - This is where the scripts should end up
  - The lib subdirectory is where the OSGi runtime finds its jar
files
  - The lib/boot directory is where the OSGi runtime boots from
- Could the jar files here be symlinks to jars installed by
  other debian packages?
  - This is also where the deploy directory is expected to be (the
directory where bundles can be dropped to be installed as
plugins) 
 KARAF_ETC=/etc/karaf
  - This is where the config files are
  - A problem: This directory will be written to and some files
modified on each karaf start/stop. Their md5 sum will not change
unless the config is changed, but their date will be changed
 KARAF_DATA=/var/lib/karaf
  - Will contain the persistent osgi runtime information (cached
bundles and their states)
  - Removing the contents of this directory will return karaf to its
pristine state (so "apt-get purge" should delete it)
  - Will contain the karaf tmp directory

 4. The script boots from a small CLASSPATH consisting of the contents
of the $KARAF_HOME/lib/boot directory
  
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf#L73
The contents of the lib/boot directory of karaf 4.1.4, is:
  -rw-r--r-- 1 sb sb 1440500 Dec 15 20:14 jna-4.5.0.jar
  -rw-r--r-- 1 sb sb 2324986 Dec 15 20:14 jna-platform-4.5.0.jar
  -rw-r--r-- 1 sb sb   31235 Dec 15 20:14 
org.apache.karaf.diagnostic.boot-4.1.4.jar
  -rw-r--r-- 1 sb sb   18181 Dec 15 20:14 
org.apache.karaf.jaas.boot-4.1.4.jar
  -rw-r--r-- 1 sb sb  150582 Dec 15 20:14 org.apache.karaf.main-4.1.4.jar
  -rw-r--r-- 1 sb sb  475256 Dec 15 20:14 org.osgi.core-6.0.0.jar

 5. The script adds a directory containing jar files to the
java.endorsed.dirs system properties
  
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf#L158
  
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf#L297
The contents of the lib/ext/ directory in karaf-4.1.4, is:
-rw-r--r-- 1 sb sb   26366 Dec 15 20:14 javax.annotation-api-1.2.jar
-rw-r--r-- 1 sb sb9598 Dec 15 20:14 
org.apache.karaf.exception-4.1.4.jar
-rw-r--r-- 1 sb sb 2952198 Dec 15 20:14 
org.apache.servicemix.bundles.xalan-2.7.2_3.jar
-rw-r--r-- 1 sb sb  284590 Dec 15 20:14 
org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
-rw-r--r-- 1 sb sb 1400520 Dec 15 20:14 
org.apache.servicemix.bundles.xerces-2.11.0_1.jar
-rw-r--r-- 1 sb sb   65653 Dec 15 20:14 
org.apache.servicemix.specs.activation-api-1.1-2.9.0.jar
-rw-r--r-- 1 sb sb  121045 Dec 15 20:14 
org.apache.servicemix.specs.jaxb-api-2.2-2.9.0.jar
-rw-r--r-- 1 sb sb  261001 Dec 15 20:14 
org.apache.servicemix.specs.jaxp-api-1.4-2.9.0.jar
-rw-r--r-- 1 sb sb   73842 Dec 15 20:14 
org.apache.servicemix.specs.jaxws-api-2.2-2.9.0.jar
-rw-r--r-- 1 sb sb   49355 Dec 15 20:14 
org.apache.servicemix.specs.saaj-api-1.3-2.9.0.jar
-rw-r--r-- 1 sb sb   48782 Dec 15 20:14 
org.apache.servicemix.specs.stax-api-1.2-2.9.0.jar

 6. The script adds a directory to the java.ext.dirs system properties
  
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf#L159
  
https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/filtered-resources/resources/bin/karaf#L298
The the lib/ext/ directory in karaf-4.1.4, is empty

 7. the 

Bug#881297: An example debian package

[Steinar Bang]

I currently use this self-packaged debian package:
 https://github.com/steinarb/karaf-deb-packaging

This debian package isn't built according to debian java standards so it
isn't immediately useful for a "real" karaf .deb package, but there may
be stuff in the installation scripts that could be borrowed.

I forked my github project from this project
 https://github.com/DemisR/karaf-deb-packaging
and did the following:
 1. Switched from Oracle Java SDK to openjdk
 2. Switched from using the proprietary karaf-wrapper to using the
included init scrips (and later systemd)
 3. Tried using /var/lib/karaf
 4. Updated the karaf version several times


This document describe (in Norwegian, unfortunately), how to build the
.deb package on a debian system and then start karaf (steps 1, 2 and 3),
and then ssh into karaf (step 5), add an extra maven repository (step 6)
and use maven to provision and start a web application (step 7):
 
https://github.com/steinarb/ukelonn#oppsett-av-webappen-på-en-server-med-debian-gnulinux

Bug#881297: Prior discussion about packing apache karaf

[Steinar Bang]

Back in September 2015 there were discussions about packaging karaf, but
it doesn't look like anything happened:
 https://lists.debian.org/debian-java/2015/09/threads.html#00086

Bug#881297: RFP: apache-karaf -- A small OSGi based application server provisioned from maven, and with an integrated SSH server.

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: apache-karaf
  Version : 4.1.3
  Upstream Author : d...@karaf.apache.org
* URL : http://karaf.apache.org/download.html
* License : Apache License v2
  Programming Lang: Java
  Description : A small OSGi based application server provisioned from 
maven, and with an integrated SSH server.

Karaf is a small and fast application server for OSGi based
application.

Karaf is provisioned using maven, so it is possible to start with a
clean karaf installation, log in using SSH to karaf's integrated SSH
server and from its command line, run commands that will pull in an
application and its dependencies.

Karaf is also convenient for development: karaf can be set up to
listen for new builds of SNAPSHOT versions in the local repository.
So this means that all you need to do to make karaf pick up new
versions of the code is run
 mvn install
in the module(s) you want karaf to pick up.

Together with remote debugging from eclipse this makes for easy
development and quick turnaround to try out code changes in the
appserver.

Karaf relies on OPS4J ("the pax stuff", e.g. pax-web, pax-jdbc) to
provide the infrastructure that makes up an application server.

Karaf introduces a concept called "features" that makes it resolve the
runtime dependencies of OSGi applications (runtime dependency
resolution have been the achilles heel of OSGi applications).  Karaf
also has a maven plugin that makes it possible to piggy back the
creation of karaf features when creating OSGi bundles.

Bug#875961: Workaround: use wireshark-gtk

[Steinar Bang]

I have found a workaround: I used wireshark-gtk

I installed wireshark-gtk with
 apt-get install wireshark-gtk

I can capture with wireshark-gtk both when I start the program as root,
and when I start the program as my own user, which is a member of the
group wireshark.

Bug#875961: wireshark: Capture is disabled and filter selection dropdown is red

[Steinar Bang]

Package: wireshark
Version: 2.2.6+g32dac6a-2
Severity: important

Dear Maintainer,


What led up to the situation:

Installing wireshark and trying to use it to capture tcp/ip traffic.


What exactly did I do:

1. Installed wireshark with "apt-get install wireshark"

2. Answered "Yes" to the question whether members of the wireshark group should
be allowed to run wireshark

3. Started wireshark as root, received the following warning dialog on startup:
Lua: error during loading
[string "/usr/share/wireshark/init.lua"]: 44: dofile has been disabled due to
running wireshark as superuser. See
https://wiki.wireshark.org/CaptureSetup/CapturePrivileges for help in running
wireshark as an unprivleged user

4. Clicked OK in the dialog

5. The menu entry Capture->Start was disabled

6. Selected menu entry Capture->Options...

7. The "Start" button was disabled

8. Selecting something in the filter dropdown caused the dropdown to turn red,
and the "Start" button was disabled

9. Clicked the "Manage Interfaces" button, all interfaces were selected in the
"Manage Interfaces (as superuser)" dialog

10. Stopped wireshark started as root

11. Added my regular user to the group wireshark with "adduser sb wireshark"

12. Started wireshark as my own user

13. The behaviour was the same as for root, ie. the menu "Capture->Start" was
disabled, the "Start" button was disabled in the dialog opened by
"Capture->Options...", and the filter selec dropdown turned red when a filter
was selected

14. Logged out of the MATE desktop and logged in again

15. Started wireshark as my own user

16. The behaviour was the same as before logging out and back in, ie. the menu
"Capture->Start" was disabled, the "Start" button was disabled in the dialog
opened by "Capture->Options...", and the filter selec dropdown turned red when
a filter was selected

17. Typed "newgroup wireshark" in a command line window running as my regular
user

18. Started wireshark from the window I had typed "newgroup" in

19. The behaviour was the same as in my previous attempts at starting
wireshark, ie. the menu "Capture->Start" was disabled, the "Start" button was
disabled in the dialog opened by "Capture->Options...", and the filter selec
dropdown turned red when a filter was selected


The outcome of the described action:

I was unable to capture tcp/ip traffic with wireshark


Expected outcome:

I had expected to be able to start wireshark, either as root or as my own user,
to be able to capture network traffic for debugging.




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

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

Versions of packages wireshark depends on:
ii  wireshark-qt  2.2.6+g32dac6a-2

wireshark recommends no packages.

wireshark suggests no packages.

-- no debconf information

Bug#849640: Screen still black after X starts with kernel 4.8.15-2~bpo8+2 and 4.9.2-2~bpo8+1

[Steinar Bang]

I have had two kernel upgrades since I reported this bug:
 linux-image-4.8.0-0.bpo.2-amd64  4.8.15-2~bpo8+2
 linux-image-4.9.0-0.bpo.1-amd64-unsigned 4.9.2-2~bpo8+1

Both kernels have had the same symptoms:
 - Get the display during boot, so that I can access the Grub menu and
   choose the 4.7 kernel (which works)
 - If I let the 4.8 or 4.9 kernel boot, the display becomes black when X starts
 - The computer is up and running and I can log in with ssh

Bug#849640: linux-image-4.8.0-0.bpo.2-amd64: The display comes up black with the 4.8.11 kernel on intel graphics, skylake processor

[Steinar Bang]

> Ben Hutchings :

> But this motherboard apparently doesn't have a DisplayPort.  Perhaps
> the driver is confused about this.

> Which type of connector is the monitor really plugged into?

A VGA connector.

Bug#849640: Acknowledgement (linux-image-4.8.0-0.bpo.2-amd64: The display comes up black with the 4.8.11 kernel on intel graphics, skylake processor)

[Steinar Bang]

Here is the /var/log/Xorg.0.log file from the black screen situation:

[ 4.620] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 4.620] X Protocol Version 11, Revision 0
[ 4.620] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 4.620] Current Operating System: Linux lorenzo 4.8.0-0.bpo.2-amd64 #1 SMP 
Debian 4.8.11-1~bpo8+1 (2016-12-14) x86_64
[ 4.620] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-0.bpo.2-amd64 
root=UUID=4f2282c8-852b-464d-8248-9de131d7494d ro quiet
[ 4.620] Build Date: 11 February 2015  12:32:02AM
[ 4.620] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[ 4.620] Current version of pixman: 0.32.6
[ 4.620]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4.620] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.620] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 29 09:36:49 
2016
[ 4.622] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4.624] (==) No Layout section.  Using the first Screen section.
[ 4.624] (==) No screen section available. Using defaults.
[ 4.624] (**) |-->Screen "Default Screen Section" (0)
[ 4.624] (**) |   |-->Monitor ""
[ 4.625] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4.625] (==) Automatically adding devices
[ 4.625] (==) Automatically enabling devices
[ 4.625] (==) Automatically adding GPU devices
[ 4.628] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 4.628]Entry deleted from font path.
[ 4.631] (==) 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
[ 4.631] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4.631] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 4.631] (II) Loader magic: 0x563c66f59d80
[ 4.631] (II) Module ABI versions:
[ 4.631]X.Org ANSI C Emulation: 0.4
[ 4.631]X.Org Video Driver: 18.0
[ 4.631]X.Org XInput driver : 21.0
[ 4.631]X.Org Server Extension : 8.0
[ 4.632] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4.756] (--) PCI:*(0:0:2:0) 8086:1912:1043:8694 rev 6, Mem @ 
0xde00/16777216, 0xc000/268435456, I/O @ 0xf000/64, BIOS @ 
0x/131072
[ 4.756] (II) LoadModule: "glx"
[ 4.759] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4.766] (II) Module glx: vendor="X.Org Foundation"
[ 4.766]compiled for 1.16.4, module version = 1.0.0
[ 4.766]ABI class: X.Org Server Extension, version 8.0
[ 4.766] (==) AIGLX enabled
[ 4.766] (==) Matched intel as autoconfigured driver 0
[ 4.766] (==) Matched intel as autoconfigured driver 1
[ 4.766] (==) Matched modesetting as autoconfigured driver 2
[ 4.766] (==) Matched fbdev as autoconfigured driver 3
[ 4.766] (==) Matched vesa as autoconfigured driver 4
[ 4.766] (==) Assigned the driver to the xf86ConfigLayout
[ 4.766] (II) LoadModule: "intel"
[ 4.766] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4.769] (II) Module intel: vendor="X.Org Foundation"
[ 4.769]compiled for 1.16.4, module version = 2.99.917
[ 4.769]Module class: X.Org Video Driver
[ 4.769]ABI class: X.Org Video Driver, version 18.0
[ 4.769] (II) LoadModule: "modesetting"
[ 4.769] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 4.770] (II) Module modesetting: vendor="X.Org Foundation"
[ 4.770]compiled for 1.16.4, module version = 0.9.0
[ 4.770]Module class: X.Org Video Driver
[ 4.770]ABI class: X.Org Video Driver, version 18.0
[ 4.770] (II) LoadModule: "fbdev"
[ 4.770] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 4.770] (II) Module fbdev: vendor="X.Org Foundation"
[ 4.770]compiled for 1.15.99.904, module version = 0.4.4
[ 4.770]Module class: X.Org Video Driver
[ 4.770]ABI class: X.Org Video Driver, version 18.0
[ 4.770] (II) LoadModule: "vesa"
[ 4.770] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 4.771] (II) Module vesa: vendor="X.Org Foundation"
[ 4.771]compiled for 1.15.99.904, module version = 2.3.3
[ 4.771]Module class: X.Org Video Driver
[ 4.771]ABI class: X.Org Video Driver, version 18.0
[ 4.771] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,

Bug#849640: linux-image-4.8.0-0.bpo.2-amd64: The display comes up black with the 4.8.11 kernel on intel graphics, skylake processor

[Steinar Bang]

Package: src:linux
Version: 4.8.11-1~bpo8+1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

"apt-get dist-upgrade" pulled in a new kernel and after the reboot the display 
was completely black.

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

I tried rebooting into the old kernel, i.e. 
linux-image-4.7.0-0.bpo.1-amd64-unsigned,
with version 4.7.8-1~bpo8+1.

   * What was the outcome of this action?

X started and I could log into the desktop.

   * What outcome did you expect instead?

I got the outcome I hoped for.

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


-- Package-specific info:
** Version:
Linux version 4.8.0-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.8.11-1~bpo8+1 (2016-12-14)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-0.bpo.2-amd64 
root=UUID=4f2282c8-852b-464d-8248-9de131d7494d ro quiet

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
[2.564155] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
[2.564176] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[2.564176] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[2.564177] usb usb2: Product: xHCI Host Controller
[2.564177] usb usb2: Manufacturer: Linux 4.8.0-0.bpo.2-amd64 xhci-hcd
[2.564178] usb usb2: SerialNumber: :00:14.0
[2.564435] hub 2-0:1.0: USB hub found
[2.56] hub 2-0:1.0: 8 ports detected
[2.569685] [drm] Memory usable by graphics device = 4096M
[2.569687] checking generic (c000 30) vs hw (c000 1000)
[2.569687] fb: switching to inteldrmfb from EFI VGA
[2.569707] Console: switching to colour dummy device 80x25
[2.569736] [drm] Replacing VGA console driver
[2.575857] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[2.575857] [drm] Driver supports precise vblank timestamp query.
[2.582474] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.584534] i915 :00:02.0: firmware: direct-loading firmware 
i915/skl_dmc_ver1_26.bin
[2.584902] [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)
[2.588583] [drm] GuC firmware load skipped
[2.591652] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[2.591712] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[2.596796] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[2.596800] [drm] Initialized i915 1.6.0 20160711 for :00:02.0 on minor 0
[2.600821] fbcon: inteldrmfb (fb0) is primary device
[2.888028] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[3.028324] usb 1-2: New USB device found, idVendor=0409, idProduct=005a
[3.028327] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[3.028996] hub 1-2:1.0: USB hub found
[3.029030] hub 1-2:1.0: 4 ports detected
[3.315635] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.326510] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.337380] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.348281] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.359139] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.36] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.380815] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many full retries, give up
[3.381017] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train 
DP, aborting
[3.439403] Console: switching to colour frame buffer device 200x75
[3.461040] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[3.478439] random: crng init done
[3.501332] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: 
(null)
[3.503152] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[3.503157] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[3.503161] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[3.503163] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[3.503166] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x0
[3.503168] snd_hda_codec_realtek hdaudioC0D0:inputs:
[3.503171] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[3.503174] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[3.503177] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[3.523842] systemd-journald[898]: Received 

Bug#844253: RFP: glsof -- Two graphical frontends to lsof (Filemonitor and Queries)

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: glsof
  Version : 2.4.1
  Upstream Author : Daniele Francesconi 
* URL : http://glsof.sourceforge.net
* License : GPL v3
  Programming Lang: Java
  Description : Two graphical frontends to lsof (Filemonitor and Queries)

Description from home page:

Glsof is two separate utilities (Queries & FileMonitor) to the command
line utility Lsof by Vic Abell.  Both applications are written in
Java.  Another fundamental requirement is the command line Lsof that
has to be installed on your system.  Lsof is supported by most of the
Unix/Linux systems including Mac Os X.

Filemonitor monitors the activity of files, processes and network
connections in ‘real time’ via lsof, returning them in a list.  One of
its main features is the possibility to control a remote system
running it as “client” (included Windows systems) and a separate
“server” on the target system.  More information here.

Queries manages multiple queries for Lsof, returning output in
different tables.  Please note that work on a new version is in
progress at the moment.  More information here.


Comment by issue reporter: The Filemonitor is the important part to package

I needed to look at a long lsof output today, and though "is there a
nice GUI for lsof?", googled and found this, which looks like a nice
and useful tool for a busy system manager or developer.

There was a package request for an earlier version of this program
that was written using C and GTk+ back in 2007, but that issue was
canceled since the program was undergoing a rewrite to Java.

The request to package for the C/GTk+ version of the program, is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413115

Bug#801324: linux-image-4.2.0-1-686-pae: System has frozen twice since upgrading to linux-image-4.2.0-1-686-pae

[Steinar Bang]

> Ben Hutchings :

> Which package and version were you previously using?

I don't know the exact package, but the kernel version was Linux 4.0.0-2-686-pae
(the one that had been up for 64 days in the uprecords output below):

 #   Uptime | System Boot up
+---
 1 0 days, 00:14:19 | Linux 4.1.0-2-686-pae Fri Oct  9 17:24:18 2015
 2 1 day , 07:50:47 | Linux 4.2.0-1-686-pae Wed Oct  7 07:26:05 2015
 3 2 days, 17:50:29 | Linux 4.2.0-1-686-pae Sun Oct  4 12:12:26 2015
->   464 days, 01:58:49 | Linux 4.0.0-2-686-pae Sat Aug  1 10:12:34 2015
 5   136 days, 13:56:37 | Linux 3.16.0-4-686-paeSun Feb 22 20:25:07 2015
 665 days, 10:49:07 | Linux 3.16.0-4-686-paeMon Dec 15 22:52:06 2014
 7 1 day , 01:24:37 | Linux 3.16.0-4-686-paeSun Dec 14 21:26:51 2014
 841 days, 07:06:39 | Linux 3.16-3-686-pae  Sat Nov  1 09:33:19 2014
 924 days, 16:45:00 | Linux 3.16-2-686-pae  Tue Oct  7 17:47:39 2014
10 4 days, 01:01:15 | Linux 3.16-2-686-pae  Fri Oct  3 16:45:46 2014

The currently installed 4.0.0 image, is:
 ii  linux-image-4.0.0-2-686-pae   4.0.8-2  
  i386 Linux 4.0 for modern PCs

(but I don't know for sure that this was the exact package version of
the kernel running at the time of reboot).

Bug#801324: linux-image-4.2.0-1-686-pae: System has frozen twice since upgrading to linux-image-4.2.0-1-686-pae

[Steinar Bang]

Package: src:linux
Version: 4.2.1-2
Severity: grave
Justification: renders package unusable

"apt-get dist-upgrade" installed the kernel
linux-image-4.2.0-1-686-pae (4.2.1-2) on Sun Oct  4 2015, 12:06:36.

Since then, the system has frozen twice.

When frozen, the system is completely unresponsive on both keyboard,
mouse and on the network (doesn't even respond to ping).

I need to hold in the power button for 5-10 seconds to let BIOS reboot
it.

I will try rebooting into the previous kernel, to see if that makes
the system stop crashing.


-- Package-specific info:
** Version:
Linux version 4.2.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-686-pae 
root=UUID=c666ea19-ecb5-4300-b375-d9e2c748e97a ro quiet

** Not tainted

** Kernel log:
[9.333445] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[   11.390628] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
[   11.555676] systemd[1]: systemd 226 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[   11.555935] systemd[1]: Detected architecture x86.
[   11.566829] systemd[1]: Set hostname to .
[   14.518789] systemd[1]: rpcbind.target: Dependency Before=rpcbind.target 
dropped
[   15.354010] systemd[1]: accounts-daemon.service: Cannot add dependency job, 
ignoring: Unit accounts-daemon.service is masked.
[   15.355465] systemd[1]: Listening on udev Control Socket.
[   15.355839] systemd[1]: Created slice System Slice.
[   15.356048] systemd[1]: Created slice User and Session Slice.
[   15.356088] systemd[1]: Reached target Encrypted Volumes.
[   15.357369] systemd[1]: Starting Increase datagram queue length...
[   15.357712] systemd[1]: Listening on Journal Socket.
[   15.359418] systemd[1]: Mounting Huge Pages File System...
[   15.361372] systemd[1]: Mounting POSIX Message Queue File System...
[   15.361763] systemd[1]: Started Dispatch Password Requests to Console 
Directory Watch.
[   15.363522] systemd[1]: Starting Create list of required static device nodes 
for the current kernel...
[   15.363744] systemd[1]: Listening on fsck to fsckd communication Socket.
[   15.365509] systemd[1]: Starting LSB: Set keymap...
[   15.366323] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[   15.366752] systemd[1]: Listening on Journal Audit Socket.
[   15.366827] systemd[1]: Reached target Slices.
[   15.366915] systemd[1]: Listening on Journal Socket (/dev/log).
[   15.367034] systemd[1]: Listening on udev Kernel Socket.
[   15.367167] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[   15.367257] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   15.435947] systemd[1]: Starting Load Kernel Modules...
[   15.436510] systemd[1]: Created slice system-getty.slice.
[   15.436583] systemd[1]: Reached target Remote File Systems (Pre).
[   15.445534] systemd[1]: Created slice system-postgresql.slice.
[   15.446836] systemd[1]: Mounting Debug File System...
[   15.672228] systemd[1]: Started Create list of required static device nodes 
for the current kernel.
[   15.674067] systemd[1]: Starting Create Static Device Nodes in /dev...
[   16.090486] systemd[1]: Mounted POSIX Message Queue File System.
[   16.090582] systemd[1]: Mounted Huge Pages File System.
[   16.090627] systemd[1]: Mounted Debug File System.
[   16.924627] lp: driver loaded but no devices found
[   17.047346] ppdev: user-space parallel port driver
[   17.092383] parport_pc 00:03: reported by Plug and Play ACPI
[   17.092476] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[   17.130410] systemd[1]: Started Create Static Device Nodes in /dev.
[   17.132446] systemd[1]: Starting udev Kernel Device Manager...
[   17.188289] lp0: using parport0 (interrupt-driven).
[   17.616267] loop: module loaded
[   17.617430] systemd[1]: Started Load Kernel Modules.
[   17.619178] systemd[1]: Starting Apply Kernel Variables...
[   18.041847] systemd[1]: Started Apply Kernel Variables.
[   18.211868] systemd[1]: Started Increase datagram queue length.
[   18.212331] systemd[1]: Listening on Syslog Socket.
[   18.214056] systemd[1]: Starting Journal Service...
[   18.468043] systemd[1]: Started Journal Service.
[   19.377783] EXT4-fs (sda1): warning: checktime reached, running e2fsck is 
recommended
[   19.445949] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   19.892125] systemd-journald[191]: Received request to flush runtime journal 
from PID 1
[   21.158117] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[   21.158134] ACPI: Power Button [PBTN]
[   21.158299] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[   21.158307] ACPI: Power Button [PWRF]
[   21.836891] 

Bug#801325: emacs24: Emacs crash

[Steinar Bang]

Package: emacs24
Version: 24.5+1-2
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I ran emacs as root under X.

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

>From an LXTerminal window in lxde, I did "/bin/su" and then started
emacs with "emacs&".

Then I did a dired to /var/log, opened kern.log and then I copied
kern.log to /tmp.

I then attempted to dired /tmp to change the read access to the copied
kern.log so that I could attach it to an email sent as a debian bug report.

   * What was the outcome of this action?

Emacs crashed, with the following written to the LXTerminal window I
had started emacs from:
Backtrace:
emacs[0x8138499]
emacs[0x8120036]
emacs[0x81372be]
emacs[0x81374bb]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7730bbc]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_widget_get_mapped+0x1d)[0xb70e025d]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_widget_size_allocate_with_baseline+0x63e)[0xb70e7fae]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_widget_size_allocate+0x1e)[0xb70e820e]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(+0x3605b1)[0xb70fa5b1]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOIDv+0x27)[0xb68ae897]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(+0xc392)[0xb68ab392]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(+0xddcf)[0xb68acdcf]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xb73)[0xb68c7b93]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x25)[0xb68c8175]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_container_check_resize+0x71)[0xb6edb241]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(+0x1412ad)[0xb6edb2ad]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOIDv+0x47)[0xb68ae8b7]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(+0xddcf)[0xb68acdcf]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xb73)[0xb68c7b93]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4c7)[0xb68c8647]
/usr/lib/i386-linux-gnu/libgdk-3.so.0(+0x2aacd)[0xb6cecacd]
/usr/lib/i386-linux-gnu/libgdk-3.so.0(+0x18dfc)[0xb6cdadfc]
/lib/i386-linux-gnu/libglib-2.0.so.0(+0x47901)[0xb67be901]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x14b)[0xb67bdd0b]
/lib/i386-linux-gnu/libglib-2.0.so.0(+0x470f9)[0xb67be0f9]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0xb67be1c4]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_main_iteration+0x20)[0xb6f98f80]
emacs[0x80f5501]
emacs[0x8126c6f]
emacs[0x8126655]
emacs[0x8128371]
emacs[0x81090e5]
emacs[0x818cfd8]
emacs[0x818d303]
emacs[0x818d0aa]
emacs[0x818d2b3]
emacs[0x818d0aa]
emacs[0x818d303]
emacs[0x818d0aa]
emacs[0x81905d7]
emacs[0x8120482]
...


   * What outcome did you expect instead?

To have "/tmp" open in a dired buffer in emacs

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


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.1.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-2
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-2
ii  libasound2 1.0.29-1
ii  libatk1.0-02.18.0-1
ii  libc6  2.19-22
ii  libcairo-gobject2  1.14.2-2
ii  libcairo2  1.14.2-2
ii  libdbus-1-31.10.0-3
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6-2
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.32.0-1
ii  libgif44.1.6-11
ii  libglib2.0-0   2.46.0-2
ii  libgnutls-deb0-28  3.3.18-1
ii  libgomp1   5.2.1-17
ii  libgpm21.20.4-6.1+b2
ii  libgtk-3-0 3.16.6-1
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.4.1-2
ii  libm17n-0  1.7.0-1
ii  libmagickcore-6.q16-2  8:6.8.9.9-6
ii  libmagickwand-6.q16-2  8:6.8.9.9-6
ii  libotf00.9.13-2
ii  libpango-1.0-0 1.38.0-3
ii  libpangocairo-1.0-01.38.0-3
ii  libpng12-0 1.2.50-2+b2
ii  librsvg2-2 2.40.10-1
ii  libselinux12.3-2+b1
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.5-1
ii  libtinfo5  6.0+20150810-1
ii  libx11-6   2:1.6.3-1
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.2+zdfsg1-4
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.8-1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.4+1-2

-- no debconf information

Bug#764377: The machine crashed again

[Steinar Bang]

New kernel installed by apt-get dist-upgrade on Nov 1 2014
(linux-image-3.2.0-4-686-pae 3.2.63-2+deb7u1), but looks like the same
crash (same stack trace).

This was in /var/log/kern.log and on the computer's console, after the
crash:
Nov 12 16:43:49 doohan kernel: [976755.030051] [ cut here 
]
Nov 12 16:43:49 doohan kernel: [976755.030142] WARNING: at 
/build/linux-ibu74Y/linux-3.2.63/kernel/timer.c:1015 del_timer_sync+0x22/0x33()
Nov 12 16:43:49 doohan kernel: [976755.030193] Modules linked in: parport_pc 
ppdev xt_tcpudp xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables dm_mod fuse 
ext3 jbd usb_storage lp ppa parport sg sr_mod cdrom uhci_hcd ehci_hcd usbcore 
psmouse 3c59x pcspkr usb_common evdev serio_raw tulip i2c_piix4 shpchp mii 
i2c_core ext2 mbcache sd_mod crc_t10dif ata_generic ata_piix libata scsi_mod
Nov 12 16:43:49 doohan kernel: [976755.030682] Pid: 0, comm: swapper/0 Not 
tainted 3.2.0-4-686-pae #1 Debian 3.2.63-2+deb7u1
Nov 12 16:43:49 doohan kernel: [976755.030728] Call Trace:
Nov 12 16:43:49 doohan kernel: [976755.030801]  [c10386fc] ? 
warn_slowpath_common+0x68/0x79
Nov 12 16:43:49 doohan kernel: [976755.030851]  [c1042574] ? 
del_timer_sync+0x22/0x33
Nov 12 16:43:49 doohan kernel: [976755.030900]  [c103871a] ? 
warn_slowpath_null+0xd/0x10
Nov 12 16:43:49 doohan kernel: [976755.030946]  [c1042574] ? 
del_timer_sync+0x22/0x33
Nov 12 16:43:49 doohan kernel: [976755.031023]  [c88da089] ? 
t21142_lnk_change+0x320/0x463 [tulip]
Nov 12 16:43:49 doohan kernel: [976755.031089]  [c88d6afe] ? 
tulip_interrupt+0x402/0x5c4 [tulip]
Nov 12 16:43:49 doohan kernel: [976755.031162]  [c11e88dd] ? 
add_interrupt_randomness+0x2d/0x12a
Nov 12 16:43:49 doohan kernel: [976755.031232]  [c1078018] ? 
handle_irq_event_percpu+0x47/0x155
Nov 12 16:43:49 doohan kernel: [976755.031299]  [c105de5d] ? 
arch_local_irq_save+0xf/0x14
Nov 12 16:43:49 doohan kernel: [976755.031354]  [c1079d28] ? 
cond_unmask_irq+0x1f/0x1f
Nov 12 16:43:49 doohan kernel: [976755.031414]  [c1078147] ? 
handle_irq_event+0x21/0x3a
Nov 12 16:43:49 doohan kernel: [976755.031473]  [c1079d28] ? 
cond_unmask_irq+0x1f/0x1f
Nov 12 16:43:49 doohan kernel: [976755.031531]  [c1079d72] ? 
handle_level_irq+0x4a/0x56
Nov 12 16:43:49 doohan kernel: [976755.031579]  IRQ  [c100c807] ? 
do_IRQ+0x2e/0x76
Nov 12 16:43:49 doohan kernel: [976755.031705]  [c12c9eb0] ? 
common_interrupt+0x30/0x38
Nov 12 16:43:49 doohan kernel: [976755.031779]  [c12000d8] ? 
spi_add_device+0x78/0x100
Nov 12 16:43:49 doohan kernel: [976755.031845]  [c10100e0] ? 
save_sched_clock_state+0x1/0x1a
Nov 12 16:43:49 doohan kernel: [976755.031935]  [c10244b4] ? 
native_safe_halt+0x2/0x3
Nov 12 16:43:49 doohan kernel: [976755.031995]  [c1010898] ? 
default_idle+0x40/0x6d
Nov 12 16:43:49 doohan kernel: [976755.032054]  [c100ac73] ? 
cpu_idle+0x95/0xaf
Nov 12 16:43:49 doohan kernel: [976755.032117]  [c141b6f8] ? 
start_kernel+0x325/0x32a
Nov 12 16:43:49 doohan kernel: [976755.032167] ---[ end trace f4c1ea900ec1eabc 
]---


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

Bug#764377: linux-image-3.2.0-4-686-pae: Kernel crash with tulip in the stack trace

[Steinar Bang]

Package: src:linux
Version: 3.2.60-1+deb7u3
Severity: normal

Dear Maintainer,
   * What led up to the situation?

The computer was running as a NAT bridge and firewall between the
internet and my home LAN.

The computer crashed with the following output in /var/log/kern.log and on the 
computers console:
Oct  7 05:53:29 doohan kernel: [5639460.859566] [ cut here 
]
Oct  7 05:53:29 doohan kernel: [5639460.859678] WARNING: at 
/build/linux-oDe0QO/linux-3.2.60/kernel/timer.c:1015 del_timer_sync+0x22/0x33()
Oct  7 05:53:29 doohan kernel: [5639460.859752] Modules linked in: parport_pc 
ppdev xt_tcpudp xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables dm_mod fuse 
ext3 jbd usb_storage lp ppa parport usblp sg sr_mod cdrom uhci_hcd 3c59x 
ehci_hcd psmouse i2c_piix4 pcspkr usbcore i2c_core usb_common tulip mii 
serio_raw shpchp evdev ext2 mbcache sd_mod crc_t10dif ata_generic ata_piix 
libata scsi_mod
Oct  7 05:53:29 doohan kernel: [5639460.860305] Pid: 0, comm: swapper/0 
Tainted: GW3.2.0-4-686-pae #1 Debian 3.2.60-1+deb7u3
Oct  7 05:53:29 doohan kernel: [5639460.860378] Call Trace:
Oct  7 05:53:29 doohan kernel: [5639460.860463]  [c1038680] ? 
warn_slowpath_common+0x68/0x79
Oct  7 05:53:29 doohan kernel: [5639460.860525]  [c10424f8] ? 
del_timer_sync+0x22/0x33
Oct  7 05:53:29 doohan kernel: [5639460.860586]  [c103869e] ? 
warn_slowpath_null+0xd/0x10
Oct  7 05:53:29 doohan kernel: [5639460.860645]  [c10424f8] ? 
del_timer_sync+0x22/0x33
Oct  7 05:53:29 doohan kernel: [5639460.860736]  [c88d5089] ? 
t21142_lnk_change+0x320/0x463 [tulip]
Oct  7 05:53:29 doohan kernel: [5639460.860815]  [c88d1afe] ? 
tulip_interrupt+0x402/0x5c4 [tulip]
Oct  7 05:53:29 doohan kernel: [5639460.860902]  [c11e8605] ? 
add_interrupt_randomness+0x2d/0x12a
Oct  7 05:53:29 doohan kernel: [5639460.860984]  [c1077ee8] ? 
handle_irq_event_percpu+0x47/0x155
Oct  7 05:53:29 doohan kernel: [5639460.861063]  [c105dd2d] ? 
arch_local_irq_save+0xf/0x14
Oct  7 05:53:29 doohan kernel: [5639460.861132]  [c1079bac] ? 
cond_unmask_irq+0x1f/0x1f
Oct  7 05:53:29 doohan kernel: [5639460.861191]  [c1078017] ? 
handle_irq_event+0x21/0x3a
Oct  7 05:53:29 doohan kernel: [5639460.861251]  [c1079bac] ? 
cond_unmask_irq+0x1f/0x1f
Oct  7 05:53:29 doohan kernel: [5639460.861310]  [c1079bf6] ? 
handle_level_irq+0x4a/0x56
Oct  7 05:53:29 doohan kernel: [5639460.861359]  IRQ  [c100c807] ? 
do_IRQ+0x2e/0x76
Oct  7 05:53:29 doohan kernel: [5639460.861484]  [c12c9af0] ? 
common_interrupt+0x30/0x38
Oct  7 05:53:29 doohan kernel: [5639460.861561]  [c12000d8] ? 
spi_register_master+0x8b/0xdc
Oct  7 05:53:29 doohan kernel: [5639460.861651]  [c10244b4] ? 
native_safe_halt+0x2/0x3
Oct  7 05:53:29 doohan kernel: [5639460.861720]  [c10108b4] ? 
default_idle+0x40/0x6d
Oct  7 05:53:29 doohan kernel: [5639460.861780]  [c100ac73] ? 
cpu_idle+0x95/0xaf
Oct  7 05:53:29 doohan kernel: [5639460.861844]  [c141b6f8] ? 
start_kernel+0x325/0x32a
Oct  7 05:53:29 doohan kernel: [5639460.861893] ---[ end trace 1221efb964543d7c 
]---


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

Switched off and on the computer's power switch.

   * What was the outcome of this action?

The computer booted.

   * What outcome did you expect instead?

This was the outcome I was hoping for.

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


-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3

** Command line:
auto BOOT_IMAGE=Linux ro root=UUID=0ec425dc-ed3d-4226-9670-14a9800e98b5

** Not tainted

** Kernel log:
[1.785969] Switching to clocksource tsc
[1.830529] ata2.00: ATAPI: TOSHIBA CD-ROM XM-6202B, 1110, max MWDMA2
[1.846111] ata2.00: configured for MWDMA2
[1.902233] ata1.00: ATA-3: QUANTUM FIREBALL SE6.4A, API.0C00, max UDMA/33
[1.902361] ata1.00: 12594960 sectors, multi 16: LBA 
[1.902865] ata1.01: ATA-6: ST340014A, 3.06, max UDMA/100
[1.902972] ata1.01: 78165360 sectors, multi 16: LBA48 
[1.918126] ata1.00: configured for UDMA/33
[1.934351] ata1.01: configured for UDMA/33
[1.935462] scsi 0:0:0:0: Direct-Access ATA  QUANTUM FIREBALL API. 
PQ: 0 ANSI: 5
[1.937364] scsi 0:0:1:0: Direct-Access ATA  ST340014A3.06 
PQ: 0 ANSI: 5
[1.942376] scsi 1:0:0:0: CD-ROMTOSHIBA  CD-ROM XM-6202B  1110 
PQ: 0 ANSI: 5
[2.050565] sd 0:0:0:0: [sda] 12594960 512-byte logical blocks: (6.44 
GB/6.00 GiB)
[2.051428] sd 0:0:0:0: [sda] Write Protect is off
[2.051539] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[2.051861] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[2.078483] sd 0:0:1:0: [sdb] 78165360 512-byte logical blocks: (40.0 
GB/37.2 GiB)
[2.097504]  sda: sda1 sda2  sda5 sda6 sda7 
[2.098203] sd 0:0:1:0: [sdb] 

Bug#763587: Still having problems

[Steinar Bang]

 Undefined User unknowuse...@gmail.com writes:

 I'm sorry, but I didn't understand. You say it is already fixed, but
 I'm still not able to upgrade the system (03-oct-2014). Do we have to
 wait for the fix to be uploaded to Debian servers?

The fix is on debian unstable, and will in time make its way to testing.

Until that is the case, you can get the unstable version of
five-or-more, with:
 apt-get install -t unstable five-or-more

This worked for me.


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

Bug#631859: cups: PDF files no longer prints

[Steinar Bang]

 Brian Potkin claremont...@gmail.com:
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Running /usr/bin/pdftops  -level3 
 -origpagesizes /var/spool/cups/tmp/pdftops.raZCfE -
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Running pstops '1670' 
 'tlf@DE-BE-20-52-41-53' 'Tilleggsopplysninger.pdf' '1' ' 
 document-name=Tilleggsopplysninger.pdf 
 job-uuid=urn:uuid:3e92a346-37ef-341e-6a2b-64f5b43eff46 
 job-originating-host-name=10.10.10.10'
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: May not be a PDF file 
 (continuing anyway)
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: PDF file is damaged - 
 attempting to reconstruct xref table...
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: Couldn't find trailer 
 dictionary
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: Couldn't read xref table
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Cannot process STDIN: Unknown 
 filetype.
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] Process is dying with Could not 
 print file STDIN
 D [26/Jun/2011:20:44:41 +0200] [Job 1670] , exit stat 2

 A problem within the cups filtering system at that time springs to
 mind.  Things have moved since then, so does the issue still occur on
 testing or unstable? Or perhaps the problem disappeared soon after you
 first observed it? Please let us know.

I haven't seen this issue for ages, but if it was fixed or it stopped
appearing because I started using evince to print PDFs instead of
acroread or xpdf, I don't know.

I know that evince was able to print PDFs at a point in time when
acroread and xpdf was failing on the same PDFs.

I also know that the people who have tried printing PDFs on the same
cups printer from windows haven't complained about problems for ages.

So I guess this particular issue is fixed (or at least no longer
reproducable). 

Thanks!


- Steinar


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

Bug#746760: cups: HP Color LaserJet 2550L has stopped printing Waiting for printer to become available

[Steinar Bang]

Package: cups
Version: 1.5.3-5+deb7u1
Severity: important

Dear Maintainer,

Answering the questions:
   Q: What led up to the situation?
   A: The HP Color LaserJet 2550L which had previously been working no longer 
prints

   Q: What did you do (or not do) that was effective (or ineffective)?
   A: Up until now I have:
- Checked the status on the http://10.10.10.1:631/printers/hpulf page (see 
below)
- Checked the /var/log/cups/ files (see the error_log file below)
- Googled for the error messages found in the /var/log/cups/error_log file
- I restarted the cups process with /etc/init.d/cups restart#
- I killed the 

   Q: What was the outcome of this action?
   A: I found some issues with the same error messages back in a bug resoled on 
testing in 2013:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638933
  Bug #638933 was resolved by installing ghostscript-cups (which I already 
have)

  After the restart the job first in the queue had the time of the reboot 
12:45.

  Cancelling the first job in the queue just left number two
  hanging with the waiting for printer to become available.
  message.

  The printer is connected to the CUPS server with USB.

   Q: What outcome did you expext instead?
   A: I had hoped both for the restart of cups, and cancelling of the
  job first in the queue to make the printer start working

Here is the content of http://10.10.10.1:631/printers/hpulf :
hpulf (Processing, Accepting Jobs, Shared, Server Default)
  Description:  HP Color LaserJet 2550L
Location:   Kjellerstue
Driver: HP Color LaserJet 2550 Foomatic/Postscript (recommended) (color, 
2-sided printing)
Connection: usb://HP/color%20LaserJet%202550%20series
Defaults:   job-sheets=none, none media=iso_a4_210x297mm sides=one-sided

Jobs

Search in hpulf:   
 

Showing 2 of 2 active jobs.▼ ID ▼   NameUserSizePages   State   
Control
hpulf-2332  Unknown Withheld210kUnknown  
processing since
Sat May 3 06:28:56 2014 
Waiting for printer to become available. 
hpulf-2333  Unknown Withheld330kUnknown pending 
since
Sat May 3 12:05:39 2014 


The /var/log/cups/error_log file was last written to on May 3 2014
06:28 (about the same date as the waiting printing job):
W [03/May/2014:06:28:38 +0200] Please move SystemGroup lpadmin on line 3 of 
/etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an 
error in a future release.
W [03/May/2014:06:28:38 +0200] No limit for Validate-Job defined in policy 
default and no suitable template found.
W [03/May/2014:06:28:38 +0200] No limit for Cancel-Jobs defined in policy 
default - using Pause-Printer's policy.
W [03/May/2014:06:28:38 +0200] No limit for Cancel-My-Jobs defined in policy 
default - using Send-Document's policy.
W [03/May/2014:06:28:38 +0200] No limit for Close-Job defined in policy default 
- using Send-Document's policy.
W [03/May/2014:06:28:38 +0200] No JobPrivateAccess defined in policy default - 
using defaults.
W [03/May/2014:06:28:38 +0200] No JobPrivateValues defined in policy default - 
using defaults.
W [03/May/2014:06:28:38 +0200] No SubscriptionPrivateAccess defined in policy 
default - using defaults.
W [03/May/2014:06:28:38 +0200] No SubscriptionPrivateValues defined in policy 
default - using defaults.
W [03/May/2014:06:28:38 +0200] No limit for Validate-Job defined in policy 
authenticated - using Print-Job's policy.
W [03/May/2014:06:28:38 +0200] No limit for Cancel-Jobs defined in policy 
authenticated - using Pause-Printer's policy.
W [03/May/2014:06:28:38 +0200] No limit for Cancel-My-Jobs defined in policy 
authenticated - using Send-Document's policy.
W [03/May/2014:06:28:38 +0200] No limit for Close-Job defined in policy 
authenticated - using Send-Document's policy.
W [03/May/2014:06:28:38 +0200] No JobPrivateAccess defined in policy 
authenticated - using defaults.
W [03/May/2014:06:28:38 +0200] No JobPrivateValues defined in policy 
authenticated - using defaults.
W [03/May/2014:06:28:38 +0200] No SubscriptionPrivateAccess defined in policy 
authenticated - using defaults.
W [03/May/2014:06:28:38 +0200] No SubscriptionPrivateValues defined in policy 
authenticated - using defaults.
E [03/May/2014:06:28:39 +0200] Filter hpgltops not found.
E [03/May/2014:06:28:39 +0200] Filter pstoraster not found.
E [03/May/2014:06:28:39 +0200] Filter pstoraster not found.
E [03/May/2014:06:28:39 +0200] Filter oopstops not found.
W [03/May/2014:06:28:40 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'hpulf-Gray..' already 
exists
W [03/May/2014:06:28:40 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'hpulf-RGB..' already 
exists
W [03/May/2014:06:28:40 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-hpulf' already exists
E [03/May/2014:06:28:40 +0200] 

Bug#746760: cups: HP Color LaserJet 2550L has stopped printing Waiting for printer to become available

[Steinar Bang]

A little more information: the cups server got a new kernel from
apt-get dist-upgrade on April 27 2014, and here are some messages from
/var/log/kern.log: 

Apr 27 21:45:33 doohan kernel: [   13.458593] usb 1-1: New USB device found, 
idVendor=03f0, idProduct=1c17
Apr 27 21:45:33 doohan kernel: [   13.458716] usb 1-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Apr 27 21:45:33 doohan kernel: [   13.458810] usb 1-1: Product: hp color 
LaserJet 2550 series
Apr 27 21:45:33 doohan kernel: [   13.458897] usb 1-1: Manufacturer: 
Hewlett-Packard
Apr 27 21:45:33 doohan kernel: [   13.458980] usb 1-1: SerialNumber: 
00CNHFD21527
Apr 27 21:45:33 doohan kernel: [   13.681474] sd 0:0:0:0: Attached scsi generic 
sg0 type 0
Apr 27 21:45:33 doohan kernel: [   13.682799] sd 0:0:1:0: Attached scsi generic 
sg1 type 0
Apr 27 21:45:33 doohan kernel: [   13.683667] sr 1:0:0:0: Attached scsi generic 
sg2 type 5
Apr 27 21:45:33 doohan kernel: [   13.893619] input: PS/2 Logitech Mouse as 
/devices/platform/i8042/serio1/input/input2
Apr 27 21:45:33 doohan kernel: [   13.903186] usblp0: USB Bidirectional printer 
dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1C17
Apr 27 21:45:33 doohan kernel: [   13.903498] usbcore: registered new interface 
driver usblp

and then later in the same file (last night, in fact):
May  2 22:35:14 doohan kernel: [435400.159065] usblp0: removed


Here is the output from lsusb:

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 03f0:1c17 Hewlett-Packard Color LaserJet 2550l


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

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

[Steinar Bang]

 Steinar Bang s...@dod.no:

 I then installed Bjørn's kernel with
  dpkg --install linux-image-3.2.0-4-686-pae_3.2.39-2a~test_i386.deb

 At the time of writing I have been running this kernel for 10 hours and
 40 minutes.

I have now been running a kernel with Bjørn's fix for 4 days and 2:58h,

The fix looks good to me.


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

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

[Steinar Bang]

 Bjørn Mork bj...@mork.no:

 I am attaching a proposed fix on top of the 655152 patch, which I have
 not tested at all on actual Debian kernel sources.  Might need context
 adjustments.  I'd appreciate it if anyone with crashing hardware could
 test it.

FYI: I have failing hardware and am in the process of testing Bjørn's
fix.

Bjørn had built a kernel against the latest unstable kernel sources
(3.2.39-2) so I first installed the newest unstable, using
 apt-get -t unstable install linux-image-3.2.0-4-686-pae

This kernel reproed the issue after 1 day, 12 hours, 27 minutes, when
waking it up from the sceen saver (the same situation it has failed in).

I then installed Bjørn's kernel with
 dpkg --install linux-image-3.2.0-4-686-pae_3.2.39-2a~test_i386.deb

At the time of writing I have been running this kernel for 10 hours and
40 minutes.


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

Bug#652172: Will this bug be fixed?

[Steinar Bang]

Will this bug be fixed?

I also see this issue, and have received emails from cron.daily for
nearly a year, saying:

 /etc/cron.daily/logrotate:
 error: skipping /var/log/couchdb/couch.log because parent directory has 
insecure permissions (It's world writable or writable by group which is not 
root) Set su directive in config file to tell logrotate which user/group 
should be used for rotation.

I am running testing/unstable (wheezy), and currently have the
following versions of couchdb and logrotate:

 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   Version  Architecture Description
 +++-==---==
 ii  couchdb1.2.0-1  i386 RESTful document oriented database
 ii  logrotate  3.8.1-4  i386 Log rotation utility


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

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

[Steinar Bang]

 Ben Hutchings b...@decadent.org.uk:

 Please send a readable photograph of this text.

The problem occurred for the third time, and I couldn't find the camera,
so I'm typing in what's shown on the console.

This time it had happened while the macine was sitting unmanned and I
can't say it had anything to do with the screen saver, unless someone
unintentionally have moved the mouse.

I also note that it says invalid opcode.  This machine has an Intel P4
CPU.  Is it too old for the current kernels?

Console text follows:
[523708.506472] [ cut here ]---
[523708.506472] kernel BUG at 
/build/build-linux_3.2.32-1-i386-Z3rOrf/linux-3.2.32/kernel/workqueue.c:1040!
[523708.506472] invalid opcode:  [#1] SMP
[523708.506472] Modules linked in: mperf speedstep_lib ip6table_filter 
ip6_tables cpufreq_powersave iptable_filter ip_tables cpufreq_stats 
cpufreq_conservative cpufreq_userspace ebtable_nat ebtables x_tables ppdev lp 
bnep rfcomm bluetooth rfkill crc16 binfmt_misc fuse nfsd nfs nfs_acl 
auth_rpcgss fscache lockd sunrpc loop snd_intel8x0 snd_ac97_codec i915 
snd_pcm_oss snd_mixer_oss snd_pcm video snd_page_alloc drm_kms_helper 
snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi snd_seq snd_seq_device 
snd_timer snd pcspkr drm i2c_i801 i2c_algo_bit soundcore ac97_bus i2c_core 
iTCO_wdt serio_raw evdev parport_pc iTCO_vendor_support parport processor 
thermal_sys rng_core button shpchp usbhid hid ext3 mbcache jbd dm_mod sg sd_mod 
sr_mod cdrom crc_t10dif ata_generic floppy ata_piix libata uhci_hcd ehci_hcd 
tg3 usbcore libphy scsi_mod usb_common [last unloaded: scsi_wait_scan]
[523708.506472] 
[523708.506472] Pid: 0, comm: swapper/0 Not tainted 3.2.0-4-686-pae #1 Debian 
3.2.32-1 Hewlett-Packard HP d530 CMT(DZ036T)/085Ch
[523708.506472] EIP: 0060:[c10494b1] EFLAGS: 00010013 CPU: 0
[523708.506472] EIP is at __queue_work+0x193/0x1f4
[523708.506472] EAX: f739e56c EBX: f708c800 ECX: 0020 EDX: f739e568
[523708.506472] ESI: c14b5240 EDI: 0010 EBP: 0046 ESP: f5809f60
[523708.506472]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[523708.506472] Process swapper/0 (pid: 0, ti=f5808000 task=c13defe0 
task.ti=c13d8000)
[523708.506472] Stack:
[523708.506472]  f739e568 f085fe80  f085fe80  0010 f7398000 
c1049555
[523708.506472]  f739e568 f739e000 f0871400 f85abe17 c11e601f 0c00a511 8000 
1930
[523708.506472]  f739e568 0006 f739e028 0046 0046 f71147c0 f58068d4 
0010
[523708.506472] Call Trace:
[523708.506472]  [c1049555] ? queue_work_on+0x25/0x30
[523708.506472]  [f85abe17] ? i8xx_irq_handler+0x6b/0x1dc [i915]
[523708.506472]  [c11e601f] ? add_interrupt_randomness+0x2d/0x12a
[523708.506472]  [c1077349] ? handle_irq_event_percpu+0x47/0x155
[523708.506472]  [c107909e] ? handle_level_irq+0x56/0x56
[523708.506472]  [c10774c3] ? handle_irq_event+0x21/0x3a
[523708.506472]  [c107909e] ? handle_level_irq+0x56/0x56
[523708.506472]  [c10790fe] ? handle_fasteoi_irq+0x60/0x85
[523708.506472]  IRQ
[523708.506472]  [c100c657] ? do_IRQ+0x2e/0x76
[523708.506472]  [c12c62b0] ? common_interrupt+0x30/0x38
[523708.506472]  [c120007b] ? __ps2_command+0x1eb/0x2d4
[523708.506472]  [c1010782] ? mwait_idle+0x65/0x8b
[523708.506472]  [c100aab7] ? cpu_idle+0x95/0xaf
[523708.506472]  [c14186fe] ? start_kernel+0x320/0x325
[523708.506472] Code: 41 c1 85 ff 74 17 8b 47 04 89 d9 ff 34 24 8b 54 24 0c ff 
17 83 c7 08 83 3f 00 58 eb e7 8b 04 24 8b 14 24 83 c0 04 39 42 04 74 02 0f 0b 
8b 7b 08 ff 44 bb 10 8b 43 50 c1 e7 04 39 43 4c 7d 8b
[523708.506472] EIP: [c10494b1] __queue_work+0x193/0x1f4 SS:ESP 0068: f5809f60
[523708.506472] Kernel panic - not syncing: Fatal exception in interrupt
[523708.506472] Pid: 0, comm: swapper/0 Tainted: G  D 3.2.0-4-686-pae 
#1 Debian 3.2.32-1
[523708.506472] Call Trace:
[523708.506472]  [c12bcb87] ? panic+0x4d/0x144
[523708.506472]  [c12c28ca] ? oops_end+0x8e/0x99
[523708.506472]  [c100bb19] ? do_bounds+0x4c/0x4c
[523708.506472]  [c100bb82] ? do_invalid_op+0x69/0x72
[523708.506472]  [c10494b1] ? __queue_work+0x193/0x1f4
[523708.506472]  [c1038d7b] ? vprintk+0x3ae/0x3df
[523708.506472]  [c12c229f] ? error_code+0x67/0x6c
[523708.506472]  [f85a00d8] ? cpufreq_governor_userspace+0x41/0x1aa 
[cpufreq_userspace]
[523708.506472]  [c10494b1] ? __queue_work+0x193/0x1f4
[523708.506472]  [c1049555] ? queue_work_on+0x25/0x30
[523708.506472]  [f85abe17] ? i8xx_irq_handler+0x6b/0x1dc [i915]
[523708.506472]  [c11e601f] ? add_interrupt_randomness+0x2d/0x12a
[523708.506472]  [c1077394] ? handle_irq_event_percpu+0x47/0x155
[523708.506472]  [c107909e] ? handle_level_irq+0x56/0x56
[523708.506472]  [c10774c3] ? handle_irq_event+0x21/0x3a
[523708.506472]  [c107909e] ? handle_level_irq+0x56/0x56
[523708.506472]  [c10790fe] ? handle_fasteoi_irq+0x60/0x85
[523708.506472]  IRQ  [c100c657] ? do_IRQ+0x2e/0x76
[523708.506472]  [c12c62b0] ? common_interrupt+0x30/0x38
[523708.506472]  [c120007b] ? __ps2_command+0x1eb/0x2d4
[523708.506472]  [c1010782] ? 

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

[Steinar Bang]

Package: src:linux
Version: 3.2.32-1
Severity: important

Dear Maintainer,

Twice, since apt-get dist-upgrade installed this kernel, the machine
has crashed when coming out of screen saver.  That's twice in a short
number of days.

What's shown is a screen of text, saying something about Panic
exiting to text console.  The text console is completely frozen, and
it's impossible to log in using ssh (it says no route to host, so
there is no NIC activity whatsoever.


-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae 
root=UUID=c666ea19-ecb5-4300-b375-d9e2c748e97a ro quiet

** Not tainted

** Kernel log:
[2.528064] usbhid: USB HID core driver
[9.563082] kjournald starting.  Commit interval 5 seconds
[9.563137] EXT3-fs (sda1): orphan cleanup on readonly fs
[9.563150] ext3_orphan_cleanup: deleting unreferenced inode 1668092
[9.563208] ext3_orphan_cleanup: deleting unreferenced inode 1668091
[9.563246] ext3_orphan_cleanup: deleting unreferenced inode 1668089
[9.563265] ext3_orphan_cleanup: deleting unreferenced inode 1668054
[9.563286] ext3_orphan_cleanup: deleting unreferenced inode 940679
[9.563338] ext3_orphan_cleanup: deleting unreferenced inode 1152881
[9.563399] ext3_orphan_cleanup: deleting unreferenced inode 1152877
[9.575816] ext3_orphan_cleanup: deleting unreferenced inode 2044806
[9.593114] ext3_orphan_cleanup: deleting unreferenced inode 1220093
[9.604490] ext3_orphan_cleanup: deleting unreferenced inode 1480359
[9.633665] ext3_orphan_cleanup: deleting unreferenced inode 1488402
[9.812769] ext3_orphan_cleanup: deleting unreferenced inode 1482056
[9.888574] ext3_orphan_cleanup: deleting unreferenced inode 1412005
[9.918634] ext3_orphan_cleanup: deleting unreferenced inode 1619427
[9.933923] ext3_orphan_cleanup: deleting unreferenced inode 1619388
[9.947425] ext3_orphan_cleanup: deleting unreferenced inode 1668333
[9.960237] ext3_orphan_cleanup: deleting unreferenced inode 1153304
[9.984888] ext3_orphan_cleanup: deleting unreferenced inode 1450785
[9.990478] ext3_orphan_cleanup: deleting unreferenced inode 1450784
[9.994799] ext3_orphan_cleanup: deleting unreferenced inode 1450783
[   10.002419] ext3_orphan_cleanup: deleting unreferenced inode 1450781
[   10.018490] ext3_orphan_cleanup: deleting unreferenced inode 625673
[   10.039288] ext3_orphan_cleanup: deleting unreferenced inode 1561846
[   10.053083] ext3_orphan_cleanup: deleting unreferenced inode 2044184
[   10.053108] ext3_orphan_cleanup: deleting unreferenced inode 2044180
[   10.053127] ext3_orphan_cleanup: deleting unreferenced inode 2044179
[   10.061189] ext3_orphan_cleanup: deleting unreferenced inode 2044158
[   10.061213] ext3_orphan_cleanup: deleting unreferenced inode 2044156
[   10.067485] ext3_orphan_cleanup: deleting unreferenced inode 2044108
[   10.087662] ext3_orphan_cleanup: deleting unreferenced inode 180228
[   10.087926] ext3_orphan_cleanup: deleting unreferenced inode 180219
[   10.088918] ext3_orphan_cleanup: deleting unreferenced inode 180187
[   10.088940] EXT3-fs (sda1): 32 orphan inodes deleted
[   10.088944] EXT3-fs (sda1): recovery complete
[   10.520446] EXT3-fs (sda1): mounted filesystem with ordered data mode
[   14.013863] udevd[299]: starting version 175
[   15.442165] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   15.592040] input: Power Button as 
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
[   15.592058] ACPI: Power Button [PBTN]
[   15.592212] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[   15.592221] ACPI: Power Button [PWRF]
[   15.835258] intel_rng: Firmware space is locked read-only. If you can't or
[   15.835262] intel_rng: don't want to disable this in firmware setup, and if
[   15.835264] intel_rng: you are certain that your system has a functional
[   15.835267] intel_rng: RNG, try using the 'no_fwh_detect' option.
[   16.322958] iTCO_vendor_support: vendor-support=0
[   16.323910] parport_pc 00:07: reported by Plug and Play ACPI
[   16.323969] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   16.593648] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   16.593808] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by 
hardware/BIOS
[   16.938308] [drm] Initialized drm 1.1.0 20060810
[   16.947553] input: PC Speaker as /devices/platform/pcspkr/input/input4
[   17.917435] i915 :00:02.0: setting latency timer to 64
[   17.932261] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   17.932268] [drm] Driver supports precise vblank timestamp query.
[   17.932339] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   17.951167] [drm] initialized overlay support
[   18.078328] fbcon: inteldrmfb (fb0) is primary 

Bug#602781: Is there any progress on packaging flightcrew?

[Steinar Bang]

This ITP is almost two years old now, and there is no package in any of
the archives?

If flightcrew won't be packaged by the current maintainer, perhaps
this bug should be closed?

An RFP from this summer was marked as done, because there already was an
ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678833


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

Bug#668314: calibre: Success with calibre from unstable

[Steinar Bang]

Package: calibre
Followup-For: Bug #668314

I installed the unstable version of calibre (0.8.51+dfsg-1) with
 apt-get install calibre/unstable calibre-bin/unstable

The resulting calibre installs and runs without a hitch.

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

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

Versions of packages calibre depends on:
ii  calibre-bin0.8.51+dfsg-1
ii  fonts-liberation [ttf-liberation]  1.07.2-2
ii  imagemagick8:6.7.4.0-5
ii  poppler-utils  0.16.7-3
ii  python-beautifulsoup   3.2.0-2
ii  python-chardet 2.0.1-2
ii  python-cherrypy3   3.2.2-2
ii  python-cssutils0.9.9-1
ii  python-dateutil1.5-1
ii  python-dbus0.84.0-3
ii  python-feedparser  5.0.1-1
ii  python-imaging 1.1.7-4
ii  python-lxml2.3.2-1
ii  python-mechanize   1:0.2.5-2
ii  python-pkg-resources   0.6.24-1
ii  python-pyparsing   1.5.2-2
ii  python-qt4 4.9.1-3
ii  python-routes  1.13-1
ii  python2.7  2.7.3~rc2-2.1
ii  ttf-liberation 1.07.2-2
ii  xdg-utils  1.1.0~rc1+git20111210-6

Versions of packages calibre recommends:
ii  python-dnspython  1.9.4-1

calibre suggests no packages.

-- no debconf information



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

Bug#668314: calibre: same issue seen after apt-get dist-upgrade

[Steinar Bang]

Package: calibre
Version: 0.8.49+dfsg-0.1
Followup-For: Bug #668314

Just saw this issue, after doing apt-get dist-upgrade.
For me, this is a grave issue.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

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

Versions of packages calibre depends on:
ii  calibre-bin0.8.49+dfsg-0.1
ii  fonts-liberation [ttf-liberation]  1.07.2-2
ii  imagemagick8:6.7.4.0-5
ii  poppler-utils  0.16.7-3
ii  python-beautifulsoup   3.2.0-2
ii  python-chardet 2.0.1-2
ii  python-cherrypy3   3.2.2-2
ii  python-cssutils0.9.9-1
ii  python-dateutil1.5-1
ii  python-dbus0.84.0-3
ii  python-feedparser  5.0.1-1
ii  python-imaging 1.1.7-4
ii  python-lxml2.3.2-1
ii  python-mechanize   1:0.2.5-2
ii  python-pkg-resources   0.6.24-1
ii  python-pyparsing   1.5.2-2
ii  python-qt4 4.9.1-3
ii  python-routes  1.13-1
ii  python2.7  2.7.3~rc2-2.1
ii  ttf-liberation 1.07.2-2
ii  xdg-utils  1.1.0~rc1+git20111210-6

Versions of packages calibre recommends:
ii  python-dnspython  1.9.4-1

calibre suggests no packages.

-- no debconf information



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

Bug#648348: xserver-xorg-video-intel: The system froze with last kernel.log message: [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

[Steinar Bang]

Package: xserver-xorg-video-intel
Version: 2:2.16.0-1
Severity: important

Dear Maintainer,

 * Upgraded with apt-get dist-upgrade
 * After a reboot, the regular gnome session looked very strange: a
   black background with white text menu bar on top, instead of the
   normal grey one
 * When I tried doing... well anything,... eg. clicking with the mouse
   on the top level bar, I was told something had crashed and was sent
   back to the login screen
 * When I tried using the Gnome fallback session type I got the same
   strange look, but at least it didn't crash
 * After being logged in and left logged for a couple of hours the
   screen was black, and the machine didn't respond to keyboard or
   mouse input, even though the fan was still running and the LEDs on
   the front panel were lit
 * The machine wasn't reachable with SSH, so I held the power button
   in to have the BIOS shut off power, and then switched the machine
   back on
 * When it came back up the behaviour was the same: ie. strange look
   on gnome, and using gnome immediately failed, and gnome fallback
   looked as strange as the other, but didn't fail

The last messages in /var/log/kernel.log before the messages from the
reboot, were:

Nov  8 22:23:37 edwards kernel: [  146.330195] [drm:intel_prepare_page_flip] 
*ERROR* Prepared flip multiple times
[Repeat log message 49245 times]
Nov  8 22:27:04 edwards kernel: [  353.227345] [drm:intel_prepare_page_flip] 
*ERROR* Prepared flip multiple times
Nov  8 22:27:10 edwards kernel: [  359.805520] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
Nov  8 22:27:10 edwards kernel: [  359.809502] render error detected, EIR: 
0x0010
Nov  8 22:27:10 edwards kernel: [  359.809502] [drm:i915_report_and_clear_eir] 
*ERROR* EIR stuck: 0x0010, masking
Nov  8 22:27:10 edwards kernel: [  359.809502] render error detected, EIR: 
0x0010



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jan  1  2010 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 2048200 Oct 20 19:32 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated 
Graphics Controller [8086:2572] (rev 02)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1077 Jan  1  2010 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type man xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout no
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
EndSection

Section Device
Identifier  Configured Video Device
EndSection

Section Monitor
Identifier  Configured Monitor
EndSection

Section Screen
Identifier  Default Screen
Monitor Configured Monitor
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 39069 Nov 10 16:34 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   400.728] 
X.Org X Server 1.11.1.901 (1.11.2 RC 1)
Release Date: 2011-10-14
[   400.728] X Protocol Version 11, Revision 0
[   400.728] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[   400.728] Current Operating System: Linux edwards 3.0.0-1-686-pae #1 SMP Sat 
Aug 27 16:41:03 UTC 2011 i686
[   400.729] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-686-pae 
root=UUID=c666ea19-ecb5-4300-b375-d9e2c748e97a ro quiet
[   400.729] Build Date: 20 October 2011  05:27:03PM
[   400.729] xorg-server 2:1.11.1.901-2 (Cyril Brulebois k...@debian.org) 
[   400.729] Current 

Bug#636577: etoys: eToys should be updated to the newest version (currently 4.1.1)

[Steinar Bang]

Package: etoys
Version: 4.0.2340-1
Severity: normal


The current version of eToys is 4.1.1 (dated October 14 2010)
 http://squeakland.org/download/

The etoys package should be updated to this version of the image, or
whatever is the most current stable at the time of packaging.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

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

Versions of packages etoys depends on:
ii  squeak-vm 1:4.0.3.2202-2 The Squeak Smalltalk System (virtu

Versions of packages etoys recommends:
ii  etoys-doc 4.0.2340-1 Documentation for etoys

etoys suggests no packages.

-- no debconf information



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

Bug#631859: cups: PDF files no longer prints

[Steinar Bang]

Package: cups
Version: 1.4.4-7
Severity: important

The http://somemachine:631/printers/hpulf page currently holds 9 jobs,
that are all PDF files, and all have the State:
 stopped 
 May not be a PDF file (continuing anyway)

All of them have been printed from Acroread in Windows Vista, using IPP.

The printer is an HP 2550L ColorLaserJet with PostScript (actually: 
ghostscript).

The /var/log/cups/error_log entries for the newest stopped PDF job, are:
...
E [26/Jun/2011:20:44:40 +0200] [Job 1670] May not be a PDF file (continuing 
anyway)
E [26/Jun/2011:20:44:40 +0200] [Job 1670] PDF file is damaged - attempting to 
reconstruct xref table...
E [26/Jun/2011:20:44:41 +0200] [Job 1670] Couldn't find trailer dictionary
E [26/Jun/2011:20:44:41 +0200] [Job 1670] Couldn't read xref table
E [26/Jun/2011:20:44:41 +0200] [Job 1670] Tom utskriftsfil!
E [26/Jun/2011:20:44:41 +0200] [Job 1670] Job stopped due to filter errors; 
please consult the error_log file for details.
D [26/Jun/2011:20:44:41 +0200] [Job 1670] The following messages were recorded 
from 20:44:35 to 20:44:41
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Adding start banner page none.
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Adding end banner page none.
D [26/Jun/2011:20:44:41 +0200] [Job 1670] File of type application/pdf queued 
by tlf@DE-BE-20-52-41-53.
D [26/Jun/2011:20:44:41 +0200] [Job 1670] hold_until=0
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Queued on hpulf by 
tlf@DE-BE-20-52-41-53.
D [26/Jun/2011:20:44:41 +0200] [Job 1670] job-sheets=none,none
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[0]=hpulf
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[1]=1670
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[2]=tlf@DE-BE-20-52-41-53
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[3]=Tilleggsopplysninger.pdf
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[4]=1
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
argv[5]=document-name=Tilleggsopplysninger.pdf 
job-uuid=urn:uuid:3e92a346-37ef-341e-6a2b-64f5b43eff46 
job-originating-host-name=10.10.10.10
D [26/Jun/2011:20:44:41 +0200] [Job 1670] argv[6]=/var/spool/cups/d01670-001
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[0]=CUPS_CACHEDIR=/var/cache/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[1]=CUPS_DATADIR=/usr/share/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[2]=CUPS_DOCROOT=/usr/share/cups/doc-root
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[3]=CUPS_FONTPATH=/usr/share/cups/fonts
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[4]=CUPS_REQUESTROOT=/var/spool/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[5]=CUPS_SERVERBIN=/usr/lib/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[6]=CUPS_SERVERROOT=/etc/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[7]=CUPS_STATEDIR=/var/run/cups
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[8]=HOME=/var/spool/cups/tmp
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[9]=PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[10]=SERVER_ADMIN=root@doohan
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[11]=SOFTWARE=CUPS/1.4.4
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[12]=TMPDIR=/var/spool/cups/tmp
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[13]=TZ=Europe/Oslo
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[14]=USER=root
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[15]=CUPS_SERVER=/var/run/cups/cups.sock
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[16]=CUPS_ENCRYPTION=IfRequested
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[17]=IPP_PORT=631
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[18]=CHARSET=utf-8
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[19]=LANG=no.UTF-8
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[20]=PPD=/etc/cups/ppd/hpulf.ppd
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[21]=RIP_MAX_CACHE=auto
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[22]=CONTENT_TYPE=application/pdf
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[23]=DEVICE_URI=usb://HP/color%20LaserJet%202550%20series
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[24]=PRINTER_INFO=HP Color 
LaserJet 2550L
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[25]=PRINTER_LOCATION=Kjellerstue
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[26]=PRINTER=hpulf
D [26/Jun/2011:20:44:41 +0200] [Job 1670] envp[27]=CUPS_FILETYPE=document
D [26/Jun/2011:20:44:41 +0200] [Job 1670] 
envp[28]=FINAL_CONTENT_TYPE=printer/hpulf
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Started filter 
/usr/lib/cups/filter/pdftopdf (PID 4074)
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Started filter 
/usr/lib/cups/filter/cpdftocps (PID 4075)
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Started filter 
/usr/lib/cups/filter/foomatic-rip (PID 4076)
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Started backend 
/usr/lib/cups/backend/usb (PID 4077)
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Getting input from file 
D [26/Jun/2011:20:44:41 +0200] [Job 1670] foomatic-rip version 4.0.5.223 
running...
D [26/Jun/2011:20:44:41 +0200] [Job 1670] Parsing PPD file ...

Bug#631708: openssh-server: ssh hangs on exit if X11 forwarding has been used

[Steinar Bang]

Package: openssh-server
Version: 1:5.5p1-6
Severity: normal

When I start an ssh session to my debian testing (Wheezy) computer,
with ssh -Y machinename, and start emacs, then exit emacs, and then
then log out, the ssh session hangs on logout.

This happens both when the client is my Ubuntu 10.10 netbook
(openssh-client 1:5.5p1-4ubuntu5), and from a Windows 7 laptop with
Xming, using putty as the SSH client (I don't have the Windows 7
laptop at hand so I am unsure of the exact version numbers).

The problem does not occur if I don't start any X11 applications
during the session.  Then the logout from the ssh session, does not
hang.

The problem does not occur if the machine I connect to is debian
stable.  If try to reproduce the issue with one of my debian stable
machines, ie. log in with ssh -Y, start an X11 application, stop the
X11 application, and then log out, the session terminates normally.

openssh-server on debian stable is currently at version 1:5.5p1-6.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

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

Versions of packages openssh-server depends on:
ii  adduser 3.113add and remove users and groups
ii  debconf [debconf-2.0]   1.5.39   Debian configuration management sy
ii  dpkg1.16.0.3 Debian package management system
ii  libc6   2.13-7   Embedded GNU C Library: Shared lib
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libgssapi-krb5-21.9.1+dfsg-1 MIT Kerberos runtime libraries - k
ii  libkrb5-3   1.9.1+dfsg-1 MIT Kerberos runtime libraries
ii  libpam-modules  1.1.3-1  Pluggable Authentication Modules f
ii  libpam-runtime  1.1.3-1  Runtime support for the PAM librar
ii  libpam0g1.1.3-1  Pluggable Authentication Modules l
ii  libselinux1 2.0.98-1+b1  SELinux runtime shared libraries
ii  libssl0.9.8 0.9.8o-7 SSL shared libraries
ii  libwrap07.6.q-19 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-27   Linux Standard Base 3.2 init scrip
ii  openssh-blacklist   0.4.1list of default blacklisted OpenSS
ii  openssh-client  1:5.5p1-6secure shell (SSH) client, for sec
ii  procps  1:3.2.8-10   /proc file system utilities
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages openssh-server recommends:
ii  openssh-blacklist-extra   0.4.1  list of non-default blacklisted Op
ii  xauth 1:1.0.6-1  X authentication utility

Versions of packages openssh-server suggests:
pn  molly-guard   none (no description available)
pn  rssh  none (no description available)
pn  ssh-askpass   none (no description available)
pn  ufw   none (no description available)

-- debconf information:
  ssh/vulnerable_host_keys:
  ssh/new_config: true
* ssh/use_old_init_script: true
  ssh/encrypted_host_key_but_no_keygen:
  ssh/disable_cr_auth: false



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

Bug#622873: xserver-xorg-video-intel: White screen striped with horizontal black lines after updating from 2:2.13.0-6 to 2:2.14.0-4

[Steinar Bang]

I see the same behaviour, on a debian testing (wheezy).

In addition to the horizontal black stripes on white backgrounds, I see
ghosts of the enlarge/minimize/close buttons on the window toolbars.

xserver-xorg-video-intel  2:2.14.0-4
linux-image-2.6.38-2-686  2.6.38-3

I've manually supplied the information of the original report, for the
stuff I knew how to provide.


X server symlink status:

lrwxrwxrwx 1 root root 13 Jan  1  2010 /etc/X11/X - /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics 
Controller (rev 02)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1077 Jan  1  2010 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type man xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout no
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
EndSection

Section Device
Identifier  Configured Video Device
EndSection

Section Monitor
Identifier  Configured Monitor
EndSection

Section Screen
Identifier  Default Screen
Monitor Configured Monitor
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 42432 Apr 24 18:42 /var/log/Xorg.0.log
-rw-r--r-- 1 root root 32463 Apr 24 18:26 /var/log/Xorg.0.log.old

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[26.550] 
X.Org X Server 1.9.5
Release Date: 2011-03-17
[26.550] X Protocol Version 11, Revision 0
[26.550] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[26.550] Current Operating System: Linux edwards 2.6.38-2-686 #1 SMP Thu 
Apr 7 05:24:21 UTC 2011 i686
[26.550] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 
root=UUID=c666ea19-ecb5-4300-b375-d9e2c748e97a ro quiet
[26.550] Build Date: 26 March 2011  07:50:38AM
[26.550] xorg-server 2:1.9.5-1 (Cyril Brulebois k...@debian.org) 
[26.550] Current version of pixman: 0.21.4
[26.550]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[26.550] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[26.550] (==) Log file: /var/log/Xorg.0.log, Time: Sun Apr 24 18:37:48 
2011
[26.756] (==) Using config file: /etc/X11/xorg.conf
[26.756] (==) Using system config directory /usr/share/X11/xorg.conf.d
[26.789] (==) No Layout section.  Using the first Screen section.
[26.789] (**) |--Screen Default Screen (0)
[26.789] (**) |   |--Monitor Configured Monitor
[26.802] (==) No device specified for screen Default Screen.
Using the first device section listed.
[26.802] (**) |   |--Device Configured Video Device
[26.802] (==) Automatically adding devices
[26.802] (==) Automatically enabling devices
[26.920] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[26.920]Entry deleted from font path.
[27.073] (==) 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,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[27.073] (==) ModulePath set to /usr/lib/xorg/modules
[27.073] (II) The server relies on udev to provide the 

Bug#616372: Calibre no longer failing after apt-get dist-upgrade (Was: Calibre: still failing (segfault at startup))

[Steinar Bang]

After apt-get dist-upgrade on my debian testing system yesterday, some
python packages, and in particular python-qt4, were installed.

So I decided to see if calibre would start, and it now starts normally. 

But perhaps there is a wrong dependency to python-qt4, since
 apt-get -t unstable install calibre
didn't pull it from unstable?

Here's the apt-get dist-upgrade that fixed the issue:

edwards:/root# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libqt4-declarative
The following packages will be upgraded:
  acpi-support-base libass4 libphonon4 libplist1 libsndfile1 libsoprano4 phonon 
phonon-backend-xine python-qt4 python-serial soprano-daemon
11 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,357 kB of archives.
After this operation, 5,599 kB of additional disk space will be used.
Do you want to continue [Y/n]? 
Get:1 http://ftp.no.debian.org/debian/ testing/main acpi-support-base i386 
0.138-9 [21.0 kB]
Get:2 http://ftp.no.debian.org/debian/ testing/main libphonon4 i386 
4:4.6.0really4.4.4-3 [157 kB]
Get:3 http://ftp.no.debian.org/debian/ testing/main phonon-backend-xine i386 
4:4.6.0really4.4.4-3 [171 kB]
Get:4 http://ftp.no.debian.org/debian/ testing/main libplist1 i386 1.4-1 [20.2 
kB]
Get:5 http://ftp.no.debian.org/debian/ testing/main libqt4-declarative i386 
4:4.7.2-3 [1,348 kB]
Get:6 http://ftp.no.debian.org/debian/ testing/main libsndfile1 i386 1.0.24-1 
[240 kB]
Get:7 http://ftp.no.debian.org/debian/ testing/main libsoprano4 i386 
2.6.0+dfsg.1-3 [616 kB]
Get:8 http://ftp.no.debian.org/debian/ testing/main soprano-daemon i386 
2.6.0+dfsg.1-3 [252 kB]
Get:9 http://ftp.no.debian.org/debian/ testing/main phonon i386 
4:4.6.0really4.4.4-3 [10.7 kB]
Get:10 http://ftp.no.debian.org/debian/ testing/main python-qt4 i386 4.8.3-2 
[5,384 kB]
Get:11 http://ftp.no.debian.org/debian/ testing/main python-serial i386 2.5-2 
[80.5 kB]   
 
Get:12 http://ftp.no.debian.org/debian/ testing/main libass4 i386 0.9.11-1 
[55.9 kB]   

Fetched 8,357 kB in 8s (1,013 kB/s) 

   
Preconfiguring packages ...
(Reading database ... 206452 files and directories currently installed.)
Preparing to replace acpi-support-base 0.138-8 (using 
.../acpi-support-base_0.138-9_i386.deb) ...
Unpacking replacement acpi-support-base ...
Preparing to replace libphonon4 4:4.6.0really4.4.2-1 (using 
.../libphonon4_4%3a4.6.0really4.4.4-3_i386.deb) ...
Unpacking replacement libphonon4 ...
Preparing to replace phonon-backend-xine 4:4.6.0really4.4.2-1 (using 
.../phonon-backend-xine_4%3a4.6.0really4.4.4-3_i386.deb) ...
Unpacking replacement phonon-backend-xine ...
Preparing to replace libplist1 1.3-2 (using .../libplist1_1.4-1_i386.deb) ...
Unpacking replacement libplist1 ...
Selecting previously deselected package libqt4-declarative.
Unpacking libqt4-declarative (from .../libqt4-declarative_4%3a4.7.2-3_i386.deb) 
...
Preparing to replace libsndfile1 1.0.23-1 (using 
.../libsndfile1_1.0.24-1_i386.deb) ...
Unpacking replacement libsndfile1 ...
Preparing to replace libsoprano4 2.5.0+dfsg.1-1 (using 
.../libsoprano4_2.6.0+dfsg.1-3_i386.deb) ...
Unpacking replacement libsoprano4 ...
Preparing to replace soprano-daemon 2.5.0+dfsg.1-1 (using 
.../soprano-daemon_2.6.0+dfsg.1-3_i386.deb) ...
Unpacking replacement soprano-daemon ...
Preparing to replace phonon 4:4.6.0really4.4.2-1 (using 
.../phonon_4%3a4.6.0really4.4.4-3_i386.deb) ...
Unpacking replacement phonon ...
Preparing to replace python-qt4 4.8.3-1 (using .../python-qt4_4.8.3-2_i386.deb) 
...
Unpacking replacement python-qt4 ...
Preparing to replace python-serial 2.3-1 (using 
.../python-serial_2.5-2_i386.deb) ...
Unpacking replacement python-serial ...
Preparing to replace libass4 0.9.9-1 (using .../libass4_0.9.11-1_i386.deb) ...
Unpacking replacement libass4 ...
Processing triggers for python-support ...
Setting up acpi-support-base (0.138-9) ...
Setting up libphonon4 (4:4.6.0really4.4.4-3) ...
Setting up phonon-backend-xine (4:4.6.0really4.4.4-3) ...
Setting up libplist1 (1.4-1) ...
Setting up libqt4-declarative (4:4.7.2-3) ...
Setting up libsndfile1 (1.0.24-1) ...
Setting up soprano-daemon (2.6.0+dfsg.1-3) ...
Setting up libsoprano4 (2.6.0+dfsg.1-3) ...
Setting up phonon (4:4.6.0really4.4.4-3) ...
Setting up python-qt4 (4.8.3-2) ...
Setting up python-serial (2.5-2) ...
Setting up libass4 (0.9.11-1) ...
Processing triggers for python-support ...



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

Bug#616372: Calibre: still failing (segfault at startup)

[Steinar Bang]

I had this error on an uptodate debian testing system:
sb@edwards:/tmp$ python /usr/bin/calibre
Traceback (most recent call last):
  File /usr/bin/calibre, line 19, in module
sys.exit(main())
  File /usr/lib/calibre/calibre/gui2/main.py, line 362, in main
app, opts, args, actions = init_qt(args)
  File /usr/lib/calibre/calibre/gui2/main.py, line 43, in init_qt
from calibre.gui2.ui import Main
  File /usr/lib/calibre/calibre/gui2/ui.py, line 30, in module
from calibre.gui2.widgets import ProgressIndicator
  File /usr/lib/calibre/calibre/gui2/widgets.py, line 24, in module
from calibre.gui2.progress_indicator import ProgressIndicator as 
_ProgressIndicator
  File /usr/lib/calibre/calibre/gui2/progress_indicator/__init__.py, line 15, 
in module
pi_error)
RuntimeError: Failed to load the Progress Indicator plugin: the sip module 
implements API v8.0 to v8.1 but the progress_indicator module requires API v7.1

I found this bug which said that the error was fixed

I pulled calibre 0.7.50+dfsg-1 and calibre-bin 0.7.50+dfsg-1 from
unstable with
 apt-get -t unstable install calibre

But calibre still wouldn't start.

When I tried running it from the command line, I got a segfault at
startup:
sb@edwards:/tmp$ python /usr/bin/calibre
Segmentation fault



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

Bug#518230: Would be nice to see NBC packaged for debian

[Steinar Bang]

Just took a quick google today to see if anyone have packaged NBC for
debian.  What I found was this one, which I guess is closed.

I would just like to record that there is at least one user for the
package if it's packaged, ie. me. :-)



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

Bug#609637: rkhunter says wrong hash for dpkg and dpkg-query after apt-get dist-upgrade

[Steinar Bang]

Package: rkhunter
Version: 1.3.2-6
Severity: normal



*** /tmp/reportbug-rkhunter-20110111-22751-5cBGw2
Subject: rkhunter says wrong hash for dpkg and dpkg-query after apt-get 
dist-upgrade
Package: rkhunter
Version: 1.3.2-6
Severity: normal

After the last apt-get dist-upgrade on my debian stable machine I get the 
following daily emails from rkhunter:
Warning: The file properties have changed:
 File: /usr/bin/dpkg
 Current hash: d478e79772b78b64cd5161a4d684b8f52f2e7f5e
 Stored hash : 3f790c813fb21d7f9161e9a8586858b4a5d8bb16
 Current inode: 270438Stored inode: 270423
 Current file modification time: 129405
 Stored file modification time : 1288522576
Warning: The file properties have changed:
 File: /usr/bin/dpkg-query
 Current inode: 270436Stored inode: 270421
 Current file modification time: 129405
 Stored file modification time : 1288522576


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

Kernel: Linux 2.6.32.26-kvm-i386-20101122 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages rkhunter depends on:
ii  binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  debconf [debconf-2. 1.5.24   Debian configuration management sy
ii  exim4-daemon-heavy  4.69-9+lenny1Exim MTA (v4) daemon with extended
ii  file4.26-1   Determines file type using magic
ii  net-tools   1.60-22  The NET-3 networking toolkit
ii  perl5.10.0-19lenny2  Larry Wall's Practical Extraction 

Versions of packages rkhunter recommends:
ii  iproute  20080725-2  networking and traffic control too
ii  libmd5-perl  2.03-1  backwards-compatible wrapper for D
pn  unhide   none  (no description available)
ii  wget 1.11.4-2+lenny2 retrieves files from the web

Versions of packages rkhunter suggests:
ii  bsd-mailx  8.1.2-0.20071201cvs-3 A simple mail user agent

-- debconf information:
  rkhunter/apt_autogen: false
  rkhunter/cron_daily_run:
  rkhunter/cron_db_update:


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

Kernel: Linux 2.6.32.26-kvm-i386-20101122 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages rkhunter depends on:
ii  binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  debconf [debconf-2. 1.5.24   Debian configuration management sy
ii  exim4-daemon-heavy  4.69-9+lenny1Exim MTA (v4) daemon with extended
ii  file4.26-1   Determines file type using magic
ii  net-tools   1.60-22  The NET-3 networking toolkit
ii  perl5.10.0-19lenny2  Larry Wall's Practical Extraction 

Versions of packages rkhunter recommends:
ii  iproute  20080725-2  networking and traffic control too
ii  libmd5-perl  2.03-1  backwards-compatible wrapper for D
pn  unhide   none  (no description available)
ii  wget 1.11.4-2+lenny2 retrieves files from the web

Versions of packages rkhunter suggests:
ii  bsd-mailx  8.1.2-0.20071201cvs-3 A simple mail user agent

-- debconf information:
  rkhunter/apt_autogen: false
  rkhunter/cron_daily_run:
  rkhunter/cron_db_update:



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

Bug#609637: rkhunter says wrong hash for dpkg and dpkg-query after apt-get dist-upgrade

[Steinar Bang]

 Julien Valroff jul...@debian.org:

 Have you run `rkhunter --propupd' after upgrading your system?

No, I haven't, but I will do so now.

Can this be automated as a part of an apt-get dist-upgrade?

 You can also disable the file properties check by adding 'attributes hashes'
 to the DISABLE_TESTS configuration option in rkhunter.conf.

Ok, thanks.  So far I've just been running with the default config.  I
suspect that will be much better than anything I can come up with.



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

Bug#607224: rkhunter complains about files from the unhide package

[Steinar Bang]

Package: rkhunter
Version: 1.3.2-6
Severity: normal

rkhunter keeps sending out emails with the following text:

Warning: The file '/usr/sbin/unhide' exists on the system, but it is
not present in the rkhunter.dat file.
Warning: The file '/usr/sbin/unhide-linux26' exists on the system, but
it is not present in the rkhunter.dat file.

These files are installed by the unhide-20100201-1 package
 http://packages.debian.org/squeeze/unhide

Unhide is a tool to find processes and ports hidden by rootkits, and
thus in the same line of business as rkhunter.

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

Kernel: Linux 2.6.32.26-kvm-i386-20101122 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages rkhunter depends on:
ii  binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  debconf [debconf-2. 1.5.24   Debian configuration management sy
ii  exim4-daemon-heavy  4.69-9+lenny1Exim MTA (v4) daemon with extended
ii  file4.26-1   Determines file type using magic
ii  net-tools   1.60-22  The NET-3 networking toolkit
ii  perl5.10.0-19lenny2  Larry Wall's Practical Extraction 

Versions of packages rkhunter recommends:
ii  iproute  20080725-2  networking and traffic control too
ii  libmd5-perl  2.03-1  backwards-compatible wrapper for D
ii  unhide   20080519-2  Forensic tool to find hidden proce
ii  wget 1.11.4-2+lenny2 retrieves files from the web

Versions of packages rkhunter suggests:
ii  bsd-mailx  8.1.2-0.20071201cvs-3 A simple mail user agent

-- debconf information:
  rkhunter/apt_autogen: false
  rkhunter/cron_daily_run:
  rkhunter/cron_db_update:



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

Bug#603443: Info received (Bug#603443: Acknowledgement (xscavenger has no .desktop file))

[Steinar Bang]

Forgot to say.  The location of the desktop file should be
/usr/share/applications/xscavenger.desktop to show up in the menu. 
(so you don't have to look it up... minimize the work of putting it
in...:-) ).



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

Bug#603443: xscavenger has no .desktop file

[Steinar Bang]

Package: xscavenger
Version: 1.4.4-7
Severity: normal

Since xscavenger has no .desktop file it won't appear in the Debian
Applications menu.

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

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

Versions of packages xscavenger depends on:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  libxext6  2:1.1.2-1  X11 miscellaneous extension librar

xscavenger recommends no packages.

xscavenger suggests no packages.

-- no debconf information



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

Bug#603443: Acknowledgement (xscavenger has no .desktop file)

[Steinar Bang]

Here's a sample .desktop file for xscavenger.

[Desktop Entry]
Name=Xscavenger
Exec=/usr/games/xscavenger
Icon=xscavenger-icon
Terminal=false
Type=Application
Categories=Game;ArcadeGame;
StartupNotify=true

Bug#563492: Ran into the same issue

[Steinar Bang]

I ran into the same issue on a stable lenny installation made in
june-july 2010.

I didn't use dpkg-reconfigure like the original reporter.  I just did
 chmod g+w /var/spool/sa-exim/tuplets
and that seemed to take care of the issue.  Tuplets are now created
(though I haven't yet verified that greylistclean will expire them).

I assumed user nobody group Debian-exim with write for both user and
group would be the right thing to have, since spamd would run as user
Debian-exim and the /etc/cron.d/greylistclean is running as nobody.

Versions of packages:
ii  exim4   4.69-9 metapackage 
to ease Exim MTA (v4) installati
ii  exim4-base  4.69-9 support 
files for all Exim MTA (v4) packages
ii  exim4-config4.69-9 
configuration for the Exim MTA (v4)
ii  exim4-daemon-heavy  4.69-9 Exim MTA 
(v4) daemon with extended features,
ii  exim4-doc-info  4.69-1 
documentation for the Exim MTA (v4) in info 
ii  geximon 0.7.7-1a monitor 
for the exim MTA
ii  sa-exim 4.2.1-11
ii  spamassassin3.2.5-2+lenny2 Perl-based 
spam filter using text analysis
ii  spamc   3.2.5-2+lenny2 Client for 
SpamAssassin spam filtering daemo



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

Bug#453186: cyrus-common-2.2: cvt_cyrusdb fail to convert deliver.db created by cyrus21

[Steinar Bang]

Package: cyrus-common-2.2
Version: 2.2.13-10
Severity: important

I tried upgrading from cyrus21 to cyrus-2.2 on my etch installation, using
the following command:
 apt-get install cyrus-common-2.2 cyrus-admin-2.2 cyrus-imapd-2.2 
libcyrus-imap-perl22

At the end of the install (which removed the cyrus21 packages), there
was a message telling me to convert the databases, using cvt_cyrusdb.

When trying to convert the databases of the old cyrus21 2.1.18-5.1
installation, cvt_cyrusdb fails with the message below.

This seems to be the exact same error as this Ubuntu bug (which
presumably uses a rebuilt version of the same package...?  It's the
only good google match at least).

https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd-2.2/+bug/53496

Here are the cvt_cyrusdb invocation with results, and the result of
running db4.2_dump.

[EMAIL PROTECTED]:/$ /usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db 
berkeley-hash-nosync /var/lib/cyrus/temp.db flat
Converting from /var/lib/cyrus/deliver.db (berkeley-hash-nosync) to 
/var/lib/cyrus/temp.db (flat)
fatal error: can't open old database
[EMAIL PROTECTED]:/$ db4.2_dump /var/lib/cyrus/deliver.dbVERSION=3
format=bytevalue
type=btree
db_pagesize=4096
HEADER=END
 
3c30303231303163383265623724363438396532373024363430626138633040706f72746162696c6c3e002e73622b2e73696576652e00
 3a524847
 
3c30303231303163383265623724363438396532373024363430626138633040706f72746162696c6c3e00757365722e73622e5350414d00
 3a524847
 
3c30303261303163383264666224326665643936343024363630626138633040706f72746162696c6c3e002e73622b2e73696576652e00
 55164747
 
3c30303261303163383264666224326665643936343024363630626138633040706f72746162696c6c3e00757365722e73622e5350414d00
 55164747
 
3c3030383231313636332e3031373334383735363130363238406a6273746563682e636f6d2e61753e002e73622b2e73696576652e00
 b6714847
 
3c3030383231313636332e3031373334383735363130363238406a6273746563682e636f6d2e61753e00757365722e73622e5350414d00
 b6714847
 
3c3230303731313233313735352e3438373436406d6172656b2e707269762e61743e002e73622b2e73696576652e00
 5b064747
 
3c3230303731313233313735352e3438373436406d6172656b2e707269762e61743e00757365722e73622e5350414d00
 5b064747
 
3c3230303731313234313430362e3031353339406d6172656b2e707269762e61743e002e73622b2e73696576652e00
 f5214847
 
3c3230303731313234313430362e3031353339406d6172656b2e707269762e61743e00757365722e73622e5350414d00
 f4214847
 
3c3230303731313234313934382e3432373331406d6172656b2e707269762e61743e002e73622b2e73696576652e00
 2f724847
 
3c3230303731313234313934382e3432373331406d6172656b2e707269762e61743e00757365722e73622e5350414d00
 2f724847
 
3c3230303731313235303431372e31393734302e66626540616c756e79732e636f6d3e002e73622b2e73696576652e00
 8fe94847
 
3c3230303731313235303431372e31393734302e66626540616c756e79732e636f6d3e00757365722e73622e5350414d00
 8fe94847
 
3c33653066303163383266366424663561663562373024623834386135363440657274656c74776f3e002e73622b2e73696576652e00
 dce44847
 
3c33653066303163383266366424663561663562373024623834386135363440657274656c74776f3e00757365722e73622e5350414d00
 dce44847
 
3c34373438314631442e3430323035303540676d61696c2e636f6d3e002e73622b2e73696576652e00
 9b1f4847
 
3c34373438314631442e3430323035303540676d61696c2e636f6d3e00757365722e73622e646f6400
 9b1f4847
 
3c34373438373031462e37303630373033406f6e6c696e652e6e6f3e002e73622b2e73696576652e00
 4d704847
 
3c34373438373031462e37303630373033406f6e6c696e652e6e6f3e00757365722e73622e646f6400
 4d704847
 
3c34373438373633372e34303530333033406f6e6c696e652e6e6f3e002e73622b2e73696576652e00
 6a764847
 
3c34373438373633372e34303530333033406f6e6c696e652e6e6f3e00757365722e73622e646f6400
 6a764847
 
3c34373438393231312e34303530323032406f6e6c696e652e6e6f3e002e73622b2e73696576652e00
 26924847
 
3c34373438393231312e34303530323032406f6e6c696e652e6e6f3e00757365722e73622e646f6400
 26924847
 
3c353438653031633832653132243337623039656230246462643263313665406e6f776f6e786d6c70697561793e002e73622b2e73696576652e00
 19874747
 
3c353438653031633832653132243337623039656230246462643263313665406e6f776f6e786d6c70697561793e00757365722e73622e5350414d00
 19874747
 
3c3536363337392e31353631332e716d4077656232363931322e6d61696c2e756b6c2e7961686f6f2e636f6d3e002e73622b2e73696576652e00
 5a774847
 
3c3536363337392e31353631332e716d4077656232363931322e6d61696c2e756b6c2e7961686f6f2e636f6d3e00757365722e73622e5350414d00
 5a774847
 
3c3539463030364345353834424633343142323345364644333534383731363645333439383946404d534730312e6e7965616875732e6e6f3e002e73622b2e73696576652e00
 faec4647
 
3c3539463030364345353834424633343142323345364644333534383731363645333439383946404d534730312e6e7965616875732e6e6f3e00757365722e73622e646f6400
 faec4647
 3c383731776166736c7a302e66736640646f642e6e6f3e002e73622b2e73696576652e00
 d8424847
 3c383731776166736c7a302e66736640646f642e6e6f3e00757365722e73622e646f6400
 d8424847
 3c383736337a73726b77672e66736640646f642e6e6f3e002e73622b2e73696576652e00
 84fe4747
 3c383736337a73726b77672e66736640646f642e6e6f3e00757365722e73622e646f6400
 

Bug#439520: linux-image-2.6.18-5-686: Unable to connect with VPNC from HOME LAN

[Steinar Bang]

 Bastian Blank [EMAIL PROTECTED]:

 No, it is usualy not the same. The Cisco client defaults to NAT
 traversal.

The client machine is a laptop with Ubuntu Feisty, which has vpnc
0.4.0.

vpnc -h gives me the following information on nat-t:
  ...
  --natt-mode natt/none/force-natt/cisco-udp
  NAT Traversal Mode natt/none/force-natt/cisco-udp
  Which NAT-Traversal Method to use:
   * natt -- NAT-T as defined in RFC3947
   * none -- disable use of any NAT-T method
   * force-natt -- always use NAT-T encapsulation even
   without presence of a NAT device
   (useful if the OS captures all ESP traffic)
   * cisco-udp -- Cisco proprietary UDP encapsulation, commonly over Port 10
000
  Note: cisco-tcp encapsulation is not yet supported
Default: natt

Which seems to indicate that nat-t is on by default here as well.

I've also been able to use this vpnc client from a different NAT'in
site (my father's home LAN, which has a WLAN AP/router with NAT'ing),
without any problems.

 When I sniff all NICs on the gateway using Wireshark, I see the
 following traffic when connecting with the Cisco client:

 You sniffed on the wrong interface, use the external.

If I sniff the external interface I see nothing when attempting to
sniff vpnc connect.  If I sniff all or the internal one, I see the
packet below.

What's wrong with sniffing all interfaces?  It seems to capture the
cisco client connect successfully?

 1. A 914 bytes ISAKMP package on UDP port 500, with source the client
 machine (with a 10.10.10.* address), and destination the VPN gw at
 the workplace

 10.10.10.* is not routable, either you missed to describe parts of your
 setup (a NAT box) or you have much more problems.

Not sure what you mean here...?

I have a home LAN with the 10.10.10.* private IP number range, that
gets its IP numbers from the DHCP client of dnsmasq on my gateway
machine, and the gateway NATs machines on the inside to the outside.
This is a setup I've had for years, and years, and should be pretty
straightforward...?

Differences from sarge is that I had to start using the DHCP client of
dnsmasq, because dnsmasq no longer cooperated with the ISC dhcp
daemon, and that I got a 2.6 kernel instead of a 2.4 kernel.  vpnc
connect to work, through this gateway, worked for me with sarge.

The iptables configuration was much simpler for me, when using sarge
(see below).  With etch the firewall configuration was handled by a
tool called ferm (see further below).

In sarge I had the following in /etc/networking/interfaces for the
outside interface:

auto eth1
iface eth1 inet dhcp
up /etc/rc.nat

The rc.nat file contain the following non-comment lines:

modprobe iptable_nat
iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
echo 1  /proc/sys/net/ipv4/ip_forward


My ferm.conf file in etch looks like this:

# -*- shell-script -*-
#
#  Configuration file for ferm(1).
#

def $DEV_PRIVATE = (eth0);
def $DEV_WORLD =  eth1;

def $NET_PRIVATE = 10.10.10.0/24;

table filter {
chain INPUT {
policy DROP;

# connection tracking
mod state state INVALID DROP;
mod state state (ESTABLISHED RELATED) ACCEPT;

# allow local connections
interface lo ACCEPT;

# respond to ping, but limit that
proto icmp {
icmp-type echo-request mod limit limit 10/s ACCEPT;
DROP;
}

# for IPsec
interface $DEV_WORLD {
proto udp dport 500 ACCEPT;
proto (esp ah) ACCEPT;
# VPNC needs port 4500 UDP open
proto udp dport 4500 ACCEPT;
}

# allow SSH connections from everywhere
proto tcp dport ssh ACCEPT;

# allow port 119 from everywhere
proto tcp dport nntp ACCEPT;

# allow secure IMAP from everywhere
proto tcp dport imaps ACCEPT;

# we provide DNS and SMTP services for the internal net
# allow everything from the internal net
interface eth0 ACCEPT;

# some IRC servers want that
interface $DEV_WORLD {
proto tcp dport auth ACCEPT;
proto tcp dport (8080 3128) REJECT;
}

# the rest is dropped by the above policy
}

# outgoing connections are not limited
chain OUTPUT policy ACCEPT;

chain FORWARD {
policy DROP;

# connection tracking
mod state state INVALID DROP;
mod state state (ESTABLISHED RELATED) ACCEPT;

# connections from the internal net to the internet or to other
# internal nets are allowed
interface $DEV_PRIVATE ACCEPT;

# the rest is dropped by the above policy
}
}

table nat {
chain POSTROUTING {
# masquerade private IP addresses
saddr $NET_PRIVATE outerface $DEV_WORLD MASQUERADE;
}
}


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

Bug#439520: linux-image-2.6.18-5-686: Unable to connect with VPNC from HOME LAN

[Steinar Bang]

Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13etch1
Severity: important

The debian machine functions as a gateway between my home LAN (using a
10.10.10.* private network), and the outside world.  When the gateway
was using sarge and a 2.4 kernel, VPNC from inside clients worked
without a hitch.

When I upgraded to etch, I was no longer able to connect to the work
LAN using vpnc clients in my home LAN.  I am able to connect when
plugging my VPNC client machine on the outside of the debian gateway.

I am also able to connect from the inside using Cisco's VPN client,
using the same protocol (the work VPN gateway is a Cisco box).

When I sniff all NICs on the gateway using Wireshark, I see the
following traffic when connecting with the Cisco client:

1. A 914 bytes ISAKMP package on UDP port 500, with source the client
   machine (with a 10.10.10.* address), and destination the VPN gw at
   the workplace

2. A 588 byes IP package with source my home network's gateway's external
  address, and destination the VPN gw at the work place

3. A 503 bytes ISAKMP package on UDP port 500, with the work VPN gw as
   source and my home network's gateway's external address as the
   destination 

4. A 503 bytes ISAKMP package on UDP port 500, with the work VPN gw as
   source, and the client machine's 10.10.10.* address as the
   destination

When I do the same sniffing on an VPNC attempted connect, all I see,
is: 

1. A 1330 bytes ISAKMP package on UDP port 500, with the client's
   10.10.10.* address as source, and the workplace VPN gw as
   destination 

and there it appearently stops...

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.18-5-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85h  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-5-686 recommends:
ii  libc6-i686 2.3.6.ds1-13etch2 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-5-686/postinst/create-kimage-link-2.6.18-5-686: true
  linux-image-2.6.18-5-686/postinst/old-system-map-link-2.6.18-5-686: true
  linux-image-2.6.18-5-686/preinst/elilo-initrd-2.6.18-5-686: true
  linux-image-2.6.18-5-686/postinst/bootloader-test-error-2.6.18-5-686:
  linux-image-2.6.18-5-686/postinst/depmod-error-2.6.18-5-686: false
  linux-image-2.6.18-5-686/preinst/already-running-this-2.6.18-5-686:
  linux-image-2.6.18-5-686/preinst/bootloader-initrd-2.6.18-5-686: true
  linux-image-2.6.18-5-686/postinst/old-dir-initrd-link-2.6.18-5-686: true
  linux-image-2.6.18-5-686/postinst/old-initrd-link-2.6.18-5-686: true
  linux-image-2.6.18-5-686/preinst/failed-to-move-modules-2.6.18-5-686:
  linux-image-2.6.18-5-686/preinst/abort-install-2.6.18-5-686:
  linux-image-2.6.18-5-686/prerm/would-invalidate-boot-loader-2.6.18-5-686: true
  linux-image-2.6.18-5-686/postinst/bootloader-error-2.6.18-5-686:
* linux-image-2.6.18-5-686/preinst/lilo-initrd-2.6.18-5-686: false
  linux-image-2.6.18-5-686/preinst/overwriting-modules-2.6.18-5-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-5-686/postinst/depmod-error-initrd-2.6.18-5-686: false
  linux-image-2.6.18-5-686/prerm/removing-running-kernel-2.6.18-5-686: true
  linux-image-2.6.18-5-686/preinst/initrd-2.6.18-5-686:
  linux-image-2.6.18-5-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-5-686/postinst/kimage-is-a-directory:
  linux-image-2.6.18-5-686/preinst/abort-overwrite-2.6.18-5-686:


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

Bug#335052: Current version is now 4.5

[Steinar Bang]

I was bit by this bug today.  I was trying to use code inside a
para, which has been there since DocBook 4.3.

The most current DocBook XML release, is 4.5:
 http://www.docbook.org/schemas/4x

A RNG version of the DocBook 4.5 schema can be picked up from the
above URL.


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