date:20130608

Bug#711543: Info received (additional info: related to another bug?)

2013-06-08 Thread niku

 [|-- NOTE: that all this had not done by the package installer till
 now. That, when the postinstallation script was obviously read, as
 that is where the installation failed.

Actually, I don’t know where the installation of colord failed. The
postinstallation script for every other package fails, however.

 Perhaps a system user cannot have a non-system group?
Please ignore this.


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

Bug#711025: iso-codes: new version of ISO 639-3

2013-06-08 Thread Christian PERRIER

Quoting Christian PERRIER (bubu...@debian.org):
 Package: iso-codes
 Severity: wishlist
 
 Just a reminder for myself and other maintainers. There is a new
 version of ISO 639-3 as of May 31st 2013:
 http://www-01.sil.org/iso639-3/download.asp
 
 

I committed the new file BUT it seems that SIL moved back to the old
format of the tabular file, which means the Python script that
generates the XML file probably has to be changed again...:-(

-- 





signature.asc
Description: Digital signature

Bug#710344: [Xcb] Bug#710344: (no subject)

2013-06-08 Thread Daniel Martin

On Wed, Jun 05, 2013 at 04:38:00PM -0400, Marc Deslauriers wrote:
 Here's what I did...not sure if it's the best way to fix it though:
 
 --- libxcb-1.8.1.orig/tests/Makefile.am
 +++ libxcb-1.8.1/tests/Makefile.am
 @@ -12,9 +12,6 @@
  check_PROGRAMS = check_all
  check_all_SOURCES =  check_all.c check_suites.h check_public.c
 
 -all-local::
 - $(RM) CheckLog*.xml
 -
  check-local: check-TESTS
   $(RM) CheckLog.html
   if test x$(HTML_CHECK_RESULT) = xtrue; then \

Tested and Signed-off-by me.

Deleting files in an 'all' target doesn't look right.


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

Bug#706600: terminator: problem with maximation of terminator

2013-06-08 Thread Florian Streibelt

Hi,

the same problem here with a fluxbox as WM, moving the config away did not help.

It also occures when I send the maximize command a second time to the window 
when it is already maximized.


When commnting the call to set_geometry_hints out in window.py in 
set_rough_geometry_hints it works.

#self.set_geometry_hints(self, -1, -1, -1, -1,  ,
#extra_height, font_width, font_height, -1.0, -1.0)

I also noticed that the values for extra_width and extra_height get negative.


/Florian


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

Bug#711554: RE : Bug#711554: ITP: pyhst -- High Speed Tomographic reconstruction controled from Python

2013-06-08 Thread PICCA Frédéric-Emmanuel

Hello Jerome,

if you want I can sponsorise this package :)

cheers

Fred

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

Bug#711586: installation-reports: successful install on thinkpad x230

2013-06-08 Thread Julien Cristau

Package: installation-reports
Severity: normal

Boot method: firmware netinst on usb key
Image version: 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-7.0.0-amd64-netinst.iso
Date: June 7, 2013

Machine: Lenovo Thinkpad X230
Partitions:
 lvs:
  LV VGAttr LSize   Pool Origin Data%  Move Log Copy%  Convert
  root   betterave -wi-ao-- 229.93g   
  swap_1 betterave -wi-ao--   7.82g

 parted:
  Model: ATA SAMSUNG MZ7TD256 (scsi)
  Disk /dev/sda: 256GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize   File system  Name  Flags
   1  1049kB  512MB  511MB  fat32  boot
   2  512MB   768MB  256MB  ext2
   3  768MB   256GB  255GB lvm

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

UEFI boot went fine after disabling secure boot.  Installer unnecessarily
warned about missing iwlwifi firmware, but IIRC that's getting fixed.
Installed on a WPA network, everything went smoothly.  I thought netcfg
would write out the network config for network-manager to use post install,
but apparently not.

Kudos to the installer team.

Cheers,
Julien

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20130430
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux betterave 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 
Series Chipset Family KT Controller [8086:1e3d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection [8086:1502] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation QM77 Express Chipset 
LPC Controller [8086:1e55] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:1f.2 SATA controller [0106]:

Bug#711544: claws-mail FTBFS, fails to find python shared library.

2013-06-08 Thread Ricardo Mones

tags 711544 fixed-upstream pending
thanks

On Fri, 07 Jun 2013 19:09:55 +0100
peter green peter.gr...@postgrad.manchester.ac.uk wrote:

 Package: claws-mail
 Version: 3.9.1-1
 Severity: serious
 
 Claws-mail seems to be having trouble finding the python shared library.

  Yep, it's already fixed upstream¹, will be in Debian soon, as an upstream
  bugfix release is planned in a few days.

  thanks for reporting,

¹http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=df8a1d7e766dea1c48a47d6a7766e20922a78cab
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Your present plans will be successful.»


signature.asc
Description: PGP signature

Bug#710444: [RFR] templates://cloud-init/{cloud-init.templates}

2013-06-08 Thread Charles Plessy

Thanks Christian and Justin for your work on cloud-init.

The Debian package is lagging behind the Ubuntu package, which is where the
work started.  Do you think you can also review the versions in the current
Ubuntu package ?  I have not merged them yet because I will not have time
to test the corresponding postinst script in the short term.


http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/cloud-init.templates


http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/control

(Please ignore the grub-legacy-ec2 and ec2-init binary packages, which are not 
present in Debian).

Have a nice week-end,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


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

Bug#711554: RE : RE : Bug#711554: ITP: pyhst -- High Speed Tomographic reconstruction controled from Python

2013-06-08 Thread PICCA Frédéric-Emmanuel

 The code was just (officially) freed ... but I am sure there is still
 plenty of work on the packaging side.

Great news. so we can work togheter to package it :). I will discuss about this 
with my boss :)
Fred

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

Bug#711587: plymouth: Cannot update initramfs due to pango breakage

2013-06-08 Thread Dominik George

Package: plymouth
Version: 0.8.8-6
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

# LANG=C plymouth-set-default-theme -R joy  
 
update-initramfs: Generating /boot/initrd.img-3.9-1-amd64
cp: cannot stat 
'/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': 
No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.9-1-amd64 with 1.

The file in question does not exist in any package inside Debian, not
even in a different locaiton.

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

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

Versions of packages plymouth depends on:
ii  initramfs-tools0.112
ii  libc6  2.17-4
ii  multiarch-support  2.17-4

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base  7.0.3
ii  plymouth-drm  0.8.8-6

- -- Configuration Files:
/etc/plymouth/plymouthd.conf changed [not included]

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQJOBAEBCAA4BQJRsuFkMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pauQA/8CLZ7M6Qcr/XICbdCs+Il
aKwVe0dPUOCWkmOAgLLnycAozdF3PsyC5T/ED0TluA6lBe8Rgck93yfnMRyrLtc3
S657SVGB3IyYV3BD1Ib/5eRMkSJCB40/BEyKudev36BdgrN7ewJxNwTco1dHbVTg
IzPzeGwwxDOzE8LqhI0xmmHPoiqp/py4ae3a3Z38SJac8TfKltD9aoV6Ijl39ckS
xnJKhQDL++o0BhzYCrjp+OR3Zufmo0qLKlPy6/ibU25Zm/J8Gx95tTYOkRK/13LR
pNlKj9gz0M3Cfc01yzTnxRzl8D8K/ox+jXwRUr4UBDZYz3vflrfweJfiaitkimyu
CA/E89TI2CrctpD3vN/L/6jGrSvrHQN5tGe78o1njEiQRCix6jV7g5aj5peOBvJx
QY/wnPpETZ15xJ9woQKS9SH+8e+Scfy6DBZULlPIr8c/nq1jdX72pH2rcn4tMQVw
EkYURjenOGOov+ow0rjARbNR+2ycRUAB8IHgdNfnKzY6+KFQBOc904q0otQPFEV+
mD7Zfzca3ViHYgYpyn8nZ16qBqxDhgtuYQm0pl1xdeLoZrG0A6hJ7Xdh75tftvnG
X6caio6hJHR5ZwJykOkO0H+2P4xoBvDMh19iHpTDu0ZkxTJJq2L5HheWsDtoSxSU
N0VWbaydxbMEMUmw7AW4GPs=
=ZB53
-END PGP SIGNATURE-


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

Bug#711561: paraview: Unable to render HDF5 files in testing (Warning! HDF5 library version mismatched error

2013-06-08 Thread Sylvestre Ledru

No. I have not done it . Sorry


Anton Gladky gl...@debian.org a écrit :

Hi,

thanks for bugreport.

@Sylvestre, did you requested give-back of hdf5 on IA64 to let
migrate to testing?

Thank you.

Anton

2013/6/7 Wojciech Aniszewski e...@o2.pl:
 Package: paraview
 Version: 4.0.0~rc1-1
 Severity: important

 Dear Maintainer,


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

 I write in connection with current paraview4.0.0~rc package. The
problem is that when loading HDF5 file, the program crashes. It
produces a warning of this kind:

 --[quote]
 Warning! ***HDF5 library version mismatched error***
 [..]
 You can, at your own risk, disable this warning by setting the
environment
 variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.
 Setting it to 2 or higher will suppress the warning messages totally.
 Headers are 1.8.10, library is 1.8.8
 ---[enda_quote]

 With HDF5_DISABLE_VERSION_CHECK=1 the program works normally. The
mismatch is probably caused by compiling the package against HDF1.8.10
from unstable. This requires either recompilation of paraview, or
upgrade of HDF5 in testing. I cannot resolve this myself.

 w.a.



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

 Kernel: Linux 3.2.0-4-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/dash

 Versions of packages paraview depends on:
 ii  libavcodec53   6:0.8.7-1
 ii  libavformat53  6:0.8.7-1
 ii  libavutil516:0.8.7-1
 ii  libc6  2.17-3
 ii  libexpat1  2.1.0-3
 ii  libfreetype6   2.4.9-1.1
 ii  libgcc11:4.8.0-7
 ii  libgl1-mesa-glx [libgl1]   8.0.5-6
 ii  libhdf5-openmpi-7 [libhdf5-7]  1.8.8-9.1
 ii  libjpeg8   8d-1
 ii  libogg01.3.1-1
 ii  libopenmpi1.3  1.4.5-1
 ii  libpng12-0 1.2.49-4
 ii  libpython2.7   2.7.5-4
 ii  libqt4-help4:4.8.2+dfsg-11
 ii  libqt4-network 4:4.8.2+dfsg-11
 ii  libqtcore4 4:4.8.2+dfsg-11
 ii  libqtgui4  4:4.8.2+dfsg-11
 ii  libqtwebkit4   2.2.1-5
 ii  libstdc++6 4.8.0-7
 ii  libswscale26:0.8.7-1
 ii  libtheora0 1.1.1+dfsg.1-3.1
 ii  libtiff4   3.9.6-11
 ii  libx11-6   2:1.5.0-1+deb7u1
 ii  libxml22.8.0+dfsg1-7+nmu1
 ii  libxt6 1:1.1.3-1+deb7u1
 ii  tcl8.4 [tclsh] 8.4.19-5
 ii  tcl8.5 [tclsh] 8.5.11-2
 ii  zlib1g 1:1.2.8.dfsg-1

 Versions of packages paraview recommends:
 ii  mpi-default-bin  1.0.1
 ii  paraview-doc 4.0.0~rc1-1
 ii  paraview-python  4.0.0~rc1-1

 Versions of packages paraview suggests:
 pn  h5utils none
 pn  hdf5-tools  none

 -- no debconf information

 --
 debian-science-maintainers mailing list
 debian-science-maintain...@lists.alioth.debian.org

http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

-- 
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.

Bug#711543: bug #711543: Some good news

2013-06-08 Thread niku

Some good news. After a system restart:

Reinstalling colord via synaptic:
---
(Reading database ... 172176 files and directories currently installed.)
Preparing to replace colord 0.1.21-1 (using .../colord_0.1.21-1_amd64.deb) ...
Unpacking replacement colord ...
Processing triggers for man-db ...
Setting up colord (0.1.21-1) ...
W: Waited for dpkg --assert-multi-arch but it wasn't there - dpkgGo
(10: No child processes)
---


Reinstalling an unrelated package via synaptic:
---
(Reading database ... 172176 files and directories currently installed.)
Preparing to replace feh 2.3-2 (using .../archives/feh_2.3-2_amd64.deb) ...
Unpacking replacement feh ...
Processing triggers for mime-support ...
Processing triggers for gnome-menus ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Setting up feh (2.3-2) ...
W: Waited for dpkg --assert-multi-arch but it wasn't there - dpkgGo
(10: No child processes)
---


And reinstalling the same package via apt-get -V --reinstall install feh:
---
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded.
Need to get 0 B/194 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 172176 files and directories currently installed.)
Preparing to replace feh 2.3-2 (using .../archives/feh_2.3-2_amd64.deb) ...
Unpacking replacement feh ...
Processing triggers for mime-support ...
Processing triggers for gnome-menus ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Setting up feh (2.3-2) ...
---


While removing another package, I even got nice lines saying:
---
Setting up colord (0.1.21-1) ...
Setting up gnome-color-manager (3.4.2-1) ...
Setting up gnome (1:3.4+7) ...
---


Essentially, there is now just one issue: the warning issued by
synaptic. That doesn't look related to colord.


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

Bug#711510: ranger: typo in a command name

2013-06-08 Thread niku

The same typo is present in the rifle file too. So, it is present in
three files:

./ranger/ranger/__init__.py:DEFAULT_PAGER = 'sensible-paper'
./ranger/ranger/ext/rifle.py:DEFAULT_PAGER = 'sensible-paper'
./ranger/rifle:DEFAULT_PAGER = 'sensible-paper'


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

Bug#711588: iso-codes (iso_639): [INTL:pt] Updated Portuguese translation for debconf messages

2013-06-08 Thread Traduz - Portuguese Translation Team


Package: iso-codes
Version: n/a
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for ISO_639 iso-codes's debconf messages.
Translator: Miguel Figueiredo el...@debianpt.org
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team traduz _at_ debianpt.org.

--
Melhores cumprimentos/Best regards,

Traduz! - Portuguese Translation Team


pt.po.gz
Description: application/gzip

Bug#711554: RE : Bug#711554: ITP: pyhst -- High Speed Tomographic reconstruction controled from Python

2013-06-08 Thread Jerome Kieffer

On Sat, 8 Jun 2013 06:54:29 +
PICCA Frédéric-Emmanuel frederic-emmanuel.pi...@synchrotron-soleil.fr wrote:

 
 if you want I can sponsorise this package :)
 
The code was just (officially) freed ... but I am sure there is still
plenty of work on the packaging side.

Cheers,
-- 
Jérôme Kieffer
Data analysis unit - ESRF


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

Bug#711589: qemu: undefined symbol

2013-06-08 Thread philipp

Package: qemu
Version: 1.5.0+dfsg-4
Severity: important

Dear Maintainer,

the whole qemu package is broken since 1.5.0+dfsg-4
The bug effects all qemu commands. If you start with a simple qemu -? you get
this:
qemu: symbol lookup error: qemu: undefined symbol: libusb_get_device_speed

qemu-system-x86_64 is the same error:
qemu-system-x86_64: symbol lookup error: qemu-system-x86_64: undefined symbol:
libusb_get_device_speed


Thanks in advance
Philipp



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

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

Versions of packages qemu depends on:
ii  qemu-system  1.5.0+dfsg-4
ii  qemu-user1.5.0+dfsg-4
ii  qemu-utils   1.5.0+dfsg-4

qemu recommends no packages.

Versions of packages qemu suggests:
ii  qemu-user-static  1.5.0+dfsg-4

-- 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#711499: Confirmation

2013-06-08 Thread Elias Diem

Hi

I can confirm this!

Elias


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

Bug#654400: icedove crashes after copying mails with invalid haeader to cyrus imap

2013-06-08 Thread Wolfgang Schnitker

Hi Carsten,

I can not reproduce this anymore, because I uninstalled my imapd Server.

Sorry.



Am 07.06.2013 07:33, schrieb Carsten Schoenert:
 Hello Wolfgang,

 On Tue, Jan 03, 2012 at 01:39:07PM +0100, Wolfgang Schnitker wrote:
 Package: icedove
 Version: 3.0.11-1+squeeze6
 Severity: normal

 Copying mail from local storage to a IMAP build on Cyrus.
 if there is an invalid header, Icedove stops copying gives an error from the
 server that there is an invailid header detected.
 After that Icedove crashes.
 what about that issue with current versions of Icedove? Which Cyrus
 version is/was running? If the error is happen with recent versions to,
 can you make log of what's happen between Icedove and Cyrus?

 http://wiki.debian.org/Icedove#Debugging_of_Filesystem_Activity
 http://wiki.debian.org/Icedove#Debugging_Icedove_Activity

 Regards
 Carsten


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

Bug#629649: icedove: fails to display birthday field in address book contact summary

2013-06-08 Thread alex bodnaru


  
  
hello carsten,
  
  thanks a lot for considering my report.
  
  On 06/07/2013 08:41 PM, Carsten Schoenert wrote:


  Hello Alex,

On Wed, Jun 08, 2011 at 03:43:50PM +0300, alex bodnaru wrote:

  
Package: icedove
Version: 3.1.10-1
Severity: normal


hello friends,

thanks for providing icedove. it's wonderful beyond small fixes that may 
improve it further.

i'm reporting a quite queer bug:
my friend is born on march 15, 1968. 
while there's no problem setting his birthday, and even viewing it in the 
calendar using thunderbirthday, in the summary window under the list of 
contacts, the birthday field under other shows 03/14/1968. 
this didn't fail for days around this, or for years around this. any idea?

  
  
your bug is quite a little bit older. Did this issue happen with current
versions of Icedove? I don't know "Thunderbirthday", this is not a
regular Addon packaged for Debian I think so we can't do anything here if
this plugin does something wrong. You have to contact the author of this
plugin.


my report is old indeed, but the bug does still manifest with latest

experimental 17.0.5.
thunderbirthday is the program that uses the birthday correctly, 
so it's not part of the bug report.
please add to your address book a contact born on march 15, 1968.
when you look at the address book you'll see summary data under 
the list.
when this specific contact is selected,his/her birthday, displayed
in the 
"other" subsection of the summary, shows march 14, instead of 15.
other dates, even around this one, seem to show correctly.
would you give it a try?

  
Or do you mean the package iceowl-extension?

Regards
Carsten




-- 
best regards,
alex

  



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

Bug#711589: qemu: undefined symbol

2013-06-08 Thread Michael Tokarev

Control: tag -1 + unreproducible moreinfo

08.06.2013 12:05, philipp wrote:
 Package: qemu
 Version: 1.5.0+dfsg-4
 Severity: important
 
 Dear Maintainer,
 
 the whole qemu package is broken since 1.5.0+dfsg-4
 The bug effects all qemu commands. If you start with a simple qemu -? you get
 this:
 qemu: symbol lookup error: qemu: undefined symbol: libusb_get_device_speed

 qemu-system-x86_64 is the same error:
 qemu-system-x86_64: symbol lookup error: qemu-system-x86_64: undefined symbol:
 libusb_get_device_speed

You're filing a bug against qemu, but qemu is a meta-package,
and it provides no useful information about installed inter-dependencies.

In particular, you didn't specify the most important thing:
the version of libusb* your system has installed.

The dependency for the qemu-system-x86 package specifies libusb-1.0-0 (= 
2:1.0.12).
This might be an error indeed, because we actually require =1.0.13 to build.


 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable')

At any rate, I can not reproduce this on a sid system, it all works
here just fine.

Thanks,

/mjt


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

Bug#711590: nginx-naxsi-ui: fails to install: preinst called with unknown argument `install'

2013-06-08 Thread Andreas Beckmann

Package: nginx-naxsi-ui
Version: 1.4.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

From the attached log (scroll to the bottom...):

  Selecting previously unselected package nginx-naxsi-ui.
  (Reading database ... 11899 files and directories currently installed.)
  Unpacking nginx-naxsi-ui (from .../nginx-naxsi-ui_1.4.1-2_all.deb) ...
  preinst called with unknown argument `install'
  dpkg: error processing /var/cache/apt/archives/nginx-naxsi-ui_1.4.1-2_all.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   /var/cache/apt/archives/nginx-naxsi-ui_1.4.1-2_all.deb


cheers,

Andreas


nginx-naxsi-ui_1.4.1-2.log.gz
Description: GNU Zip compressed data

Bug#711591: php-horde: fails to install: post-installation script returned error exit status 1

2013-06-08 Thread Andreas Beckmann

Package: php-horde
Version: 5.1.0+debian0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

From the attached log (scroll to the bottom...):

  Unpacking php-horde (from .../php-horde_5.1.0+debian0-1_all.deb) ...
  Setting up php-horde (5.1.0+debian0-1) ...
  dpkg: error processing php-horde (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   php-horde


cheers,

Andreas


php-horde_5.1.0+debian0-1.log.gz
Description: GNU Zip compressed data

Bug#711592: Current x86 linux kernel is misconfigured.

2013-06-08 Thread Robert de Bath

Package: linux-image-686-pae
Version: 3.2+46

On current Debian kernels the the WCHAN column for procps is NOT working.
Run this command:
# cat /proc/*/wchan

For current Debian kernels you get all zeros, you should get something
like:

devtmpfsdsys_pauserescuer_threadbdi_sync_superskjournald2rescuer_threadhub_threadrescuer_threadrescuer_threadrescuer_threadscsi_error_handlerscsi_error_handlerscsi_error_handlerscsi_error_handlerscsi_
etc etc.

This is all due to the configuration of the frame pointers, there are two
confgurations that work, the current release format isn't one of them...

Current setting -- not working:
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
# CONFIG_FRAME_POINTER is not set

Working setting without frame pointers (except sched.o):
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
# CONFIG_FRAME_POINTER is not set

Working setting with frame pointers (Ubuntu):
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y

The the with frame pointers method (like Ubuntu) gives more detailed
information than without frame pointers, but for me both are reasonable.

The CONFIG_SCHED_OMIT_FRAME_POINTER option is rather confusing, it only
changes the compile options if it's NOT set. If it's set the frame pointer
option says what we get. If it's not set an extra no-omit-frame-pointer
is added to the compile of kernel/sched.c; so if the kernel is compiled
with frame pointers it has no effect.

Note: This only applies to x86 and amd64; the not working combination
where ALL frame pointers are omitted works fine on some processors,
especially if it's impossible to remove the frame pointers anyway.

IIRC: ARM needs frame pointers, Spark always has frame pointers.

--
Rob. (Robert de Bath robert$ @ debath.co.uk)
http://www.debath.co.uk/

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

Bug#708863: GFDL with invariant section

2013-06-08 Thread أحمد المحمودي

On Sun, May 19, 2013 at 11:14:53AM +0200, bastien ROUCARIES wrote:
 dico.info as front cover please render dfsg compliant
---end quoted text---

  I don't understand, what is the problem ? and what should I do to fix 
  it ?

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: Digital signature

Bug#711593: pike7.8-gtk: fails to upgrade from 'testing' - trying to overwrite /usr/lib/pike7.8/modules/Tools.pmod/PV.pike

2013-06-08 Thread Andreas Beckmann

Package: pike7.8-gtk
Version: 7.8.700-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

From the attached log (scroll to the bottom...):

  Selecting previously unselected package pike7.8-image.
  Unpacking pike7.8-image (from .../pike7.8-image_7.8.700-5_amd64.deb) ...
  Preparing to replace pike7.8-gtk 7.8.700-4 (using 
.../pike7.8-gtk_7.8.700-5_amd64.deb) ...
  Unpacking replacement pike7.8-gtk ...
  dpkg: error processing 
/var/cache/apt/archives/pike7.8-gtk_7.8.700-5_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/pike7.8/modules/Tools.pmod/PV.pike', which is 
also in package pike7.8-core 7.8.700-4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to replace pike7.8-core 7.8.700-4 (using 
.../pike7.8-core_7.8.700-5_amd64.deb) ...
  Unpacking replacement pike7.8-core ...
  Processing triggers for libglib2.0-0:amd64 ...
  Errors were encountered while processing:
   /var/cache/apt/archives/pike7.8-gtk_7.8.700-5_amd64.deb


cheers,

Andreas


pike7.8-gtk_7.8.700-5.log.gz
Description: GNU Zip compressed data

Bug#711594: vino: Vino does not refresh screen once it is connected

2013-06-08 Thread Peter van der Wal

Package: vino
Version: 3.4.2-1+b1
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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

After updating several packages last week vino-server will not work properly
anymore.
It seems there is a problem with the combination of Vino and ATI drivers ( and
one of the packages emntioned below).
I have the fglrx packages from the repository installed.
A search on the web suggested a problem with compiz-effects earlier, but I
don't know how this relates to Gnome 3.

Updates installed:
libfs6 (2:1.0.4-1) to 2:1.0.4-1+deb7u1
libgl1-mesa-dri (8.0.5-4) to 8.0.5-4+deb7u1
libgl1-mesa-dri:i386 (8.0.5-4) to 8.0.5-4+deb7u1
libgl1-mesa-glx (8.0.5-4) to 8.0.5-4+deb7u1
libgl1-mesa-glx:i386 (8.0.5-4) to 8.0.5-4+deb7u1
libglapi-mesa (8.0.5-4) to 8.0.5-4+deb7u1
libglapi-mesa:i386 (8.0.5-4) to 8.0.5-4+deb7u1
libglu1-mesa (8.0.5-4) to 8.0.5-4+deb7u1
libglu1-mesa:i386 (8.0.5-4) to 8.0.5-4+deb7u1
libx11-6 (2:1.5.0-1) to 2:1.5.0-1+deb7u1
libx11-6:i386 (2:1.5.0-1) to 2:1.5.0-1+deb7u1
libx11-data (2:1.5.0-1) to 2:1.5.0-1+deb7u1
libx11-xcb1 (2:1.5.0-1) to 2:1.5.0-1+deb7u1
libx11-xcb1:i386 (2:1.5.0-1) to 2:1.5.0-1+deb7u1
libxcb-dri2-0 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-glx0 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-glx0:i386 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-render0 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-render0:i386 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-shape0 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb-shm0 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb1 (1.8.1-2) to 1.8.1-2+deb7u1
libxcb1:i386 (1.8.1-2) to 1.8.1-2+deb7u1
libxcursor1 (1:1.1.13-1) to 1:1.1.13-1+deb7u1
libxcursor1:i386 (1:1.1.13-1) to 1:1.1.13-1+deb7u1
libxext6 (2:1.3.1-2) to 2:1.3.1-2+deb7u1
libxext6:i386 (2:1.3.1-2) to 2:1.3.1-2+deb7u1
libxfixes3 (1:5.0-4) to 1:5.0-4+deb7u1
libxfixes3:i386 (1:5.0-4) to 1:5.0-4+deb7u1
libxi6 (2:1.6.1-1) to 2:1.6.1-1+deb7u1
libxi6:i386 (2:1.6.1-1) to 2:1.6.1-1+deb7u1
libxinerama1 (2:1.1.2-1) to 2:1.1.2-1+deb7u1
libxinerama1:i386 (2:1.1.2-1) to 2:1.1.2-1+deb7u1
libxp6:i386 (1:1.0.1-2) to 1:1.0.1-2+deb7u1
libxrandr2 (2:1.3.2-2) to 2:1.3.2-2+deb7u1
libxrandr2:i386 (2:1.3.2-2) to 2:1.3.2-2+deb7u1
libxrender1 (1:0.9.7-1) to 1:0.9.7-1+deb7u1
libxrender1:i386 (1:0.9.7-1) to 1:0.9.7-1+deb7u1
libxres1 (2:1.0.6-1) to 2:1.0.6-1+deb7u1
libxt6 (1:1.1.3-1) to 1:1.1.3-1+deb7u1
libxt6:i386 (1:1.1.3-1) to 1:1.1.3-1+deb7u1
libxtst6 (2:1.2.1-1) to 2:1.2.1-1+deb7u1
libxtst6:i386 (2:1.2.1-1) to 2:1.2.1-1+deb7u1
libxv1 (2:1.0.7-1) to 2:1.0.7-1+deb7u1
libxv1:i386 (2:1.0.7-1) to 2:1.0.7-1+deb7u1
libxvmc1 (2:1.0.7-1) to 2:1.0.7-1+deb7u2
libxxf86dga1 (2:1.1.3-2) to 2:1.1.3-2+deb7u1
libxxf86vm1 (1:1.1.2-1) to 1:1.1.2-1+deb7u1
libxxf86vm1:i386 (1:1.1.2-1) to 1:1.1.2-1+deb7u1
xserver-xorg-video-openchrome (1:0.2.906-2) to 1:0.2.906-2+deb7u1

Falling back to VESA and the Classic Gnome will allow for a remote connection.
Removing Wheezy's fglrx package and installing the official recent AMD driver
will render my computer completely useless (another bug concerning libGL.so.1
location) and is no option.



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

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

Versions of packages vino depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-3
ii  libavahi-client3 0.6.31-2
ii  libavahi-common3 0.6.31-2
ii  libavahi-glib1   0.6.31-2
ii  libc62.13-38
ii  libcairo21.12.2-3
ii  libdbus-glib-1-2 0.100.2-1
ii  libgcrypt11  1.5.0-5
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libgnome-keyring03.4.1-1
ii  libgnutls26  2.12.20-7
ii  libgtk-3-0   3.4.2-6
ii  libice6  2:1.0.8-2
ii  libjpeg8 8d-1
ii  libnotify4   0.7.5-1
ii  libsm6   2:1.2.1-2
ii  libsoup2.4-1 2.38.1-2
ii  libtelepathy-glib0   0.18.2-2
ii  libx11-6 2:1.5.0-1+deb7u1
ii  libxdamage1  1:1.1.3-2
ii  libxext6 2:1.3.1-2+deb7u1
ii  libxfixes3   1:5.0-4+deb7u1
ii  libxtst6 2:1.2.1-1+deb7u1
ii  zlib1g

Bug#709755: [xfce4-clipman-plugin] Not only xfce4-clipman-plugin

2013-06-08 Thread Manolo Díaz

Hi,

It's not only xfce4-clipman-plugin. At least Terminal Emulator, File
Manager and Web Browser also lack panel icons. Installing
gnome-icon-theme fix it, but that package isn't even recommended.

Best Regards,
--
Manolo Díaz


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

Bug#710444: [RFR] templates://cloud-init/{cloud-init.templates}

2013-06-08 Thread Justin B Rye

Charles Plessy wrote:
 
 http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/cloud-init.templates
 
 
 http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/control

The Ubuntu template has a couple of extra choices; diffing against the
version we first saw:

 -Default: NoCloud, ConfigDrive, OVF, MAAS
 +Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None

 -Choices-C: NoCloud, ConfigDrive, OVF, MAAS, Ec2
 +Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None

 -Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: 
Reads data from Openstack Config Drive, OVF: Reads data from OVF Transports, 
MAAS: Reads data from Ubuntu MAAS, Ec2: reads data from EC2 Metadata service
 +Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: 
Reads data from Openstack Config Drive, AltCloud: config disks for RHEVm and 
vSphere, OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu 
MAAS, Ec2: reads data from EC2 Metadata service, CloudStack: Read from 
CloudStack metadata service, None: Failsafe datasource

But what's the reason for this change?
 -_Description: Which data sources should be searched?
 +Description: Which data sources should be searched?

I can try to reimpose the logic of Christian's debconf-best-practice
changes, but I'm not clear what AltCloud: config disks for RHEVm and
vSphere is saying.  I'm going to guess that the corrected version
should just offer to read from AltCloud config disks.

Oh, except that a search suggests that these AltCloud config disks are
either virtual floppies or compact discs.  Maybe it should just be
AltCloud user data?

Then the control file... has a bizarrely shrunken description.  As far
as I can see the best option is to throw it out and substitute our
edited version.

-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru old/cloud-init.templates new/cloud-init.templates
--- old/cloud-init.templates2013-06-08 09:02:02.972669186 +0100
+++ new/cloud-init.templates2013-06-08 09:38:22.702410176 +0100
@@ -2,11 +2,11 @@
 Type: multiselect
 Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
 Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
-Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: Reads 
data from Openstack Config Drive, AltCloud: config disks for RHEVm and vSphere, 
OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu MAAS, Ec2: 
reads data from EC2 Metadata service, CloudStack: Read from CloudStack metadata 
service, None: Failsafe datasource
-Description: Which data sources should be searched?
+__Choices: /var/lib/cloud/seed only, Openstack Config Drive, AltCloud config 
disks, OVF Transports, Ubuntu MAAS, EC2 Metadata service, CloudStack metadata 
service, Failsafe datasource
+_Description: Data sources to read from:
  Cloud-init supports searching different Data Sources for information
  that it uses to configure a cloud instance.
  .
- Warning: Only select 'Ec2' if this system will be run on a system with
- the EC2 metadata service present.  Doing so incorrectly will result in
- a substantial timeout on boot.
+ Please note that EC2 Metadata service should be used only if
+ the EC2 metadata service is present. Otherwise, it will trigger
+ a very noticeable timeout on boot.
diff -ru old/control new/control
--- old/control 2013-06-08 09:02:47.811372794 +0100
+++ new/control 2013-06-08 09:43:41.929332550 +0100
@@ -35,9 +35,14 @@
 Replaces: ec2-init (0.5.3)
 Conflicts: ec2-init (0.5.3)
 XB-Python-Version: ${python:Versions}
-Description: Init scripts for cloud instances
- Cloud instances need special scripts to run during initialisation
- to retrieve and install ssh keys and to let the user run various scripts.
+Description: configuration and customization of cloud instances
+ Cloud-init provides a framework and tool written in Python to handle early
+ initialization of a cloud instance. It can for example set a default locale
+ and hostname, generate SSH private host keys, add SSH keys to a user's
+ authorized_keys so they can log in, and set up ephemeral mount points.
+ .
+ Cloud-init's behavior can be configured via data given by the user at
+ instance launch time.
 
 Package: grub-legacy-ec2
 Depends: debconf (= 1.5.19) | cdebconf,
Template: cloud-init/datasources
Type: multiselect
Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
__Choices: /var/lib/cloud/seed only, Openstack Config Drive, AltCloud config 
disks, OVF Transports, Ubuntu MAAS, EC2 Metadata service, CloudStack metadata 
service, Failsafe datasource
_Description: Data sources to read from:
 Cloud-init supports searching different Data Sources

Bug#711548: [pkg-ntp-maintainers] Bug#711548: Fragile handling of pidfile by /etc/init.d/ntp

2013-06-08 Thread Sergio Gelato

On Fri, 7 Jun 2013 22:11:30 +0200, Kurt Roeckx k...@roeckx.be wrote:
 On Fri, Jun 07, 2013 at 09:53:38PM +0200, Sergio Gelato wrote:
 Package: ntp
 Version: 1:4.2.6.p5+dfsg-2
 
 The current /etc/init.d/ntp cannot recover from a situation in which
 /var/run/ntpd.pid exists but does not contain the correct PID for the
 running daemon.
 
 How to reproduce:
 
 # pgrep -f ntpd
 9219
 # ps -f -p 9404
 UIDPID  PPID  C STIME TTY  TIME CMD
 root  9404  9395  0 20:38 pts/200:00:00 /bin/bash
 # printf 9404  /var/run/ntpd.pid
 
 Why do you do this?

To reproduce a problem that was observed on a live system. I don't know
how the pidfile got broken; it happened right after a reboot, so I'm
guessing some kind of race between startup scripts was involved.

 # invoke-rc.d ntp status
 NTP server is running.
 # echo $?
 0
 # invoke-rc.d ntp restart
 Stopping NTP server: ntpd.
 Starting NTP server: ntpd.
 # echo $?
 0
 # pgrep -f ntpd
 9219
 
 Did you expect something else, if you break the pid file?

Yes, actually. I don't particularly care about the pid file: it's just a
tool that may or may not be useful for managing the daemon. What I care
about is that invoke-rc.d whatever status and invoke-rc.d whatever
restart do what it says on the tin; the pid file is an internal
implementation detail.

 
 It's running as 9219, but you decided to write 9404 to the file.
 So of course it didn't kill it.
 
 # cat /var/run/ntpd.pid
 9485
 
 But you started a new one, which wrote a PID file, and then it
 died because it detected that an other ntpd was still running,
 and you really one want 1 running.  It probably shouldn't have
 written the pid file in that case.  But it should never have
 gotton in the situation if you didn't manually write something
 to that pid file.

I agree; and yet it did (on an Ubuntu precise system, so I'd report that
aspect of the problem to Launchpad and not to the Debian BTS). My concern
here is that regardless of how the pid file got corrupted, once it has been
corrupted it doesn't self-heal. I noticed because puppet started trying to
restart ntpd on every run. By default puppet relies on the status
functionality of the init script to decide whether a restart is needed; in
my testing I found that it makes better decisions (for ntp) if I tell it
not to trust the status reported by the init script. (I think it falls back
on running ps and parsing the output.)
 
 # ps -f -p 9404
 UIDPID  PPID  C STIME TTY  TIME CMD
 root  9404  9395  0 20:38 pts/200:00:00 /bin/bash
 
 So the script did the right thing and did not kill some
 random process that happens to be written in the pid file.

Indeed I'm not complaining about that particular aspect of the problem. On
the contrary, couldn't this be part of the solution? Once the script
discovers that the pid file is inaccurate it could just delete it.
 
 
 Kurt


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

Bug#711595: ITP: ruby-http-parser.rb -- Ruby bindings to http-parser and http-parser.java

2013-06-08 Thread Praveen A

package: wnpp
severity: wishlist
owner: Praveen Arimbrathodiyil prav...@debian.org

URL: http://rubygems.org/gems/http_parser.rb
Version: 0.5.3
Upstream Authors: Marc-Andre Cournoyer, Aman Gupta
License: Expat

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
You have to keep reminding your government that you don't get your
rights from them; you give them permission to rule, only so long as
they follow the rules: laws and constitution.


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

Bug#711596: hoogle: postinst uses /usr/share/doc content (Policy 12.3)

2013-06-08 Thread Andreas Beckmann

Package: hoogle
Version: 4.2.16-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: Packages must not require the existence of any files in
/usr/share/doc/ in order to function.
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

From the attached log (scroll to the bottom...):

  Selecting previously unselected package hoogle.
  (Reading database ... 14544 files and directories currently installed.)
  Unpacking hoogle (from .../hoogle_4.2.16-2+b2_amd64.deb) ...
  Setting up hoogle (4.2.16-2+b2) ...
  Starting keyword
  hoogle: download/keyword.txt: hGetContents: invalid argument (invalid byte 
sequence)
  Converting databases. done
  Combining 1 databases
  hoogle: *.hoo: openFile: does not exist (No such file or directory)
  dpkg: error processing hoogle (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   hoogle


Cheers,

Andreas


hoogle_4.2.16-2+b2.log.gz
Description: GNU Zip compressed data

Bug#711589: qemu: undefined symbol

2013-06-08 Thread Michael Tokarev

08.06.2013 13:04, egophil wrote:

 libusb-0.1-4 (2:0.1.12-23.2)

This one isn't used anymore, at least hopefully
(Does it show in `ldd /usr/bin/qemu-system-x86_64' ?)

 libusb-1.0-0 (2:1.0.15-1)

ok, this is the same version which is in sid and
which the package is built against.  It works on
my system just fine, bot as amd64 and i386.

 qemu-system-common (1.5.0+dfsg-4)

 If you need more specific information about my system let me know.

please show

 ldd /usr/bin/qemu-system-x86_64

 ls -lL $(ldd /usr/bin/qemu-system-x86_64 | grep usb)

and maybe (but it is huge),

 LD_DEBUG=libs,symbols LD_DEBUG_OUTPUT=/some/where/outfile 
/usr/bin/qemu-system-x86_64

(and post the output of /some/where/outfile to somewhere).

I will be out of the city till monday.

Thanks,

/mjt


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

Bug#711597: gconf2: gconftool-2 in postinst cannot connect to D-BUS

2013-06-08 Thread Dominik George

Package: gconf2
Version: 3.2.6-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

When gconftool-2 is called in the postinst script, it cannot connect to
the session bus as apt-get update does not have an X11 display
available:

(gconftool-2:27994): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: No 
protocol specified
Autolaunch error: X11 initialization failed.

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

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

Versions of packages gconf2 depends on:
ii  dbus-x11   1.6.10-1
ii  gconf-service  3.2.6-1
ii  libc6  2.17-5
ii  libgconf-2-4   3.2.6-1
ii  libglib2.0-0   2.36.1-2build1
ii  libxml22.8.0+dfsg1-7+nmu1
ii  psmisc 22.20-1
ii  python 2.7.3-5

gconf2 recommends no packages.

Versions of packages gconf2 suggests:
pn  gconf-defaults-service  none

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQJOBAEBCAA4BQJRsvo9MRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pYmyA//V81AY35HMJeOYHjWzvK+
hKjFKe6wkF8BmT8XEEo7vQd/7ATLor4ASiydVoyTikLqj/HHj/RxZ/PqkvW8XNHT
Uwu0LsPGF4WAg2CzQ8t1PVPoEgyVgDuSQtDVMnWHmUi/DHexYjoa1+7krdYN6u9L
NleWsL2Z6IuXEr4vzGB+VaY0GAiC6caCb1lTj+BqQJDIWiqBoG3XKilHl1RWumcu
g8W4Bgpf4SgsD/OT0U80be1YkH8Q3w8JHQW5Ti4cxOVP4diK41xlZM8nQdBlUi99
WNa48+fpGAhkp0CGfOataXmwYUhZO0vgiCM4rTwxa7n0r9RRuaLnXh9VE78jdb7a
KHFKP91O5v3JSPSN0gj+fk2LoSo3pVXE9ao7Z4VcpH0ovRNrGgJP46m/8JaOekvf
eYRVmrkb1p7vRosM3UB1swFchUr0UnvFoJB3Gy/M3iZEh8f0AQ2d/fGL7AN2VHrC
wb6TPijYJcRk63Uy4qLC+fdcsUFYefYDt7JsjDatefqm4EeP3vXwWFMwQa/cjc7M
GhQlmgXrWx/o4fzfSZhB66SJ0yJRZrIrdgKDT/2uDVFnTjwXaLQPBuwlXJ18Mw42
Uf/ro6Cm+LYiiAVfczaGhtZyR+6cGL8r2HTsiLXvV5wOHNQBc30mGxa3XAMVvJXJ
z25AQzVHsdQz9m0sJPj+6Jo=
=LxRt
-END PGP SIGNATURE-


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

Bug#711543: Info received (bug #711543: Some good news)

2013-06-08 Thread niku

SUMMARY:
All my problems are solved. The package maintainer still has to look
for why command 3 below (and possibly others) were not run during
colord installation.


RELATED BUG:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648287


FOR OTHERS:
The colord postinstallation script, `postinst', has the following 4 commands:

1)  addgroup --quiet --system scanner
2)  mkdir -p /var/lib/colord
3)  adduser --system --group --home /var/lib/colord colord \
--quiet --gecos colord colour management daemon
4)  chown -R colord:colord /var/lib/colord

I did the following things:
i) I already had a non-system group `scanner'. (I may have added it by hand.)
ii) I ran the commands 1, 3 and 4 mentioned above. Somehow, in
installation and reinstallation of colord, 2 (and perhaps others) were
never run.
iii) Then I deleted the group `scanner' (via `delgroup scanner'), and
ran 1, 3 and 4 again. (This almost certainly means that you could skip
the previous step, the step (ii).)
iv) restarted the system.
v) reinstalled colord -- it got reinstalled with just one warning
message. (see below)
vi) I reconfigured all packages via `dpkg-reconfigure -a'.

In dpkg, `--assert-multi-arch' was an option added about an year back,
in v. 1.16.2, “to allow checking for multi-arch support availability”.
(from /usr/share/doc/dpkg/changelog.Debian.gz) The dpkg man page has
not yet been updated to reflect this†, but `dpkg --help' shows it
under `for internal use', with no description. Since I use packages of
only one architecture (check with `dpkg --print-architecture'), I am
assuming that that issue does not concern me anyway.

† It looks like dpkg maintainers do not want to add it in the man
page, as none of the ‘for internal use’ options are mentioned in the
man page.


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

Bug#711595: fails to parse in C locale (pbuilder)

2013-06-08 Thread Praveen A

https://github.com/tmm1/http_parser.rb/issues/27
--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
You have to keep reminding your government that you don't get your
rights from them; you give them permission to rule, only so long as
they follow the rules: laws and constitution.

Bug#583849: You don't need a metapackage

2013-06-08 Thread Robert de Bath

This message is a bit old but the problem is still current and it has a simple 
solution.


You create your own metapackage ...

The equivs package is designed for precisely this situation ... you need 
dpkg/apt to think you have a particular package installed but you don't want 
any of the contents of the package to be installed.


All you do is give equivs the name and version (and any of several other things 
you may want) of the package you want to fake then install the fake package 
it generates.


Problem solved. Bug 583849 FIXED.

--
Rob.  (Robert de Bath robert$ @ debath.co.uk)
 http://www.debath.co.uk/


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

Bug#711459: nuitka: can't import Python 3.2 modules: ImportError: dynamic module does not define init function

2013-06-08 Thread Kay Hayen



Hello,

turns out, that CPython3 defines the module init function PyMODINIT_FUNC 
as follows:


extern C PyObject *

on the other hand, visibility attributes are supposed to be defined 
before the actual type, but since it's a define, one can't really get in 
between.


I would content, that CPython should in fact, provide a visibility 
definition here. Otherwise, every module runs into it. Do you agree, I 
reckon having seen your name in other place, that you might know, Jakub.


When it's not a type, as with CPython2:

extern C void

then it's acceptable, to define attributes afterwards. So Nuitka, using 
-fvisibility=hidden runs into trouble here. There is actually a bug 
report for gcc (the number I forgot), that complained about it, but that 
is how it should be, for pointers as return types, it won't work to 
define attributes after it.


The solution is to test for __GNUC__ and to make its own declaration, 
not using PyMODINIT_FUNC.


I am going to make a new release of Nuitka. The test didn't notice, 
because although it compiled all modules of Nuitka into single modules 
(that is the test, can be done more efficient), it was not copying the 
nuitka binary, and therefore it was location the nuitka package 
relative to that original place, not using them at all.


So that had been broken for a while. It also found other (minor) issues, 
of why modules didn't work at all for Python3, and when they did, not 
correctly. Fixed them too.


Will be fixed in 0.4.4 release. (If you or anybody need/want it sooner, 
checkout factory branch of official Nuitka repository. It's where I 
prepare releases, but reserve the right rebase often as I improve things.)


Yours,
Kay


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

Bug#711598: dpkg-mainscript-helper mv_conffile does not prompt user about changed conffile

2013-06-08 Thread Robert Luberda

Package: dpkg
Version: 1.16.10
Severity: important

Hi,

Usually if dpkg discovers that both local version of config file and
maintainer provided version of conffile where both modified, than it
prompts user to handle the situation. 

However when - in addition to modifing config ile -  a maintainer wants to
change its location (and the file in existing location has been modified by
local user) with `dpkg-mainscript-helper mv_conffile', no prompt is
given. 


The dpkg-maintscript-helper contains the following code:

 echo Preserving user changes to $NEWCONFFILE (renamed from 
$OLDCONFFILE)...
 mv -f $NEWCONFFILE $NEWCONFFILE.dpkg-new
 mv -f $OLDCONFFILE $NEWCONFFILE

But this is not sufficient... The `Preserving changes' message will be
most probably overlooked by user in tones of messages produced during
upgrade, and I don't think any user checks for new *.dpkg-new files
after upgrade either.


It looks like dpkg will prompt user when confile newly introduced in
package does already exist in system. So I guess making
prepare_mv_conffile() function to rename locally modified file into 
new location  (i.e adding 
else
mv -f $CONFFILE $NEWFILE
part for the following if
if [ $md5sum = $old_md5sum ]; then
mv -f $CONFFILE $CONFFILE.dpkg-remove
fi
) would solve the issue.

Regards,
robert

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.8-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-4
ii  libc62.17-5
ii  liblzma5 5.1.1alpha+20120614-2
ii  libselinux1  2.1.13-2
ii  tar  1.26+dfsg-6
ii  zlib1g   1:1.2.8.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt  0.9.8.2

-- Configuration Files:
/etc/dpkg/dpkg.cfg changed [not included]

-- 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#711599: pkg-config information doesn't give the right flags for a static lib

2013-06-08 Thread Sjoerd Simons

Package: check
Version: 0.9.10-1
Severity: important

I got the following error while test-compiling gdm 3.8:

/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libcheck_pic.a(check.o):
In function `tcase_create':
(.text+0x19c): undefined reference to `floor'


A bit of digging revealed that check in debian only has a static library, but
pkg-config --cflags --libs check doesn't provide the required library flags
(adding --static does). As it's a packaging decision to only provide the static
library, the .pc file should probably provide the same information with and
without --static to keep this transparent to the application.


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

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

Versions of packages check depends on:
ii  dpkg  1.16.10
ii  install-info  5.1.dfsg.1-3

check recommends no packages.

check 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#700205: pu: libquvi-scripts/0.4.15-1~deb7u1

2013-06-08 Thread Adam D. Barratt

Control: tags -1 + confirmed

On Fri, 2013-06-07 at 09:39 +0200, Ansgar Burchardt wrote:
 Just a quick reminder as winter^W the p-u-NEW freeze is coming. It would
 be nice if this could be included in the upcoming point release.

Please go ahead, thanks; sorry for the delays.

Regards,

Adam


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

Bug#711600: Insecure creation of the credential file debian.cnf

2013-06-08 Thread vladz


Package: mysql-server
Version: 5.5.31+dfsg-0+wheezy1
Tags: security

The file /etc/mysql/debian.cnf, which contains plain text credentials
for the debian-sys-maint mysql user, is created in an insecure manner
during the package installation phase.  This can lead a non-privileged
local user to disclose its content and use this special account to
perform administration tasks.

The file is created by the post-installation script:

  $ vim -c set nu mysql-5.5-5.5.31+dfsg/debian/mysql-server-5.5.postinst
  [...]
  170 dc=$mysql_cfgdir/debian.cnf;
  [...]
  176 cat /dev/null  $dc
  [...]
  178 echo [client] $dc
  179 echo host = localhost $dc
  180 echo user = debian-sys-maint $dc
  181 echo password = $pass $dc
  [...]
  191 chown 0:0 $dc
  192 chmod 0600 $dc

There is a time lapse (between lines 176 and 191) where the file
permissions are 644 (settled by the default umask).  At this time, a
user can open the file with the O_RDONLY flag and disclose its content
even after the chmod is executed at line 192 (yes, the user's file
descriptor won't be affected by this action).

Anyway, I suggest to force a umask value to 077 before this file is
created.

I have a trivial PoC if needed.

Thanks,
vladz.


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

Bug#711601: xserver-xorg-input-synaptics: Edge motion not working

2013-06-08 Thread José Luis González

Package: xserver-xorg-input-synaptics
Version: 1.6.2-2
Severity: normal

Edge motion is not working on my touchpad. If EdgeMotionUseAlways is
off, it doesn't work for dragging (either tapping or clicking). If it
is on, it doesn't for movement too. In short: it never works.

EdgeMotionMinZ  = 30
EdgeMotionMaxZ  = 160
EdgeMotionMinSpeed  = 1
EdgeMotionMaxSpeed  = 314
EdgeMotionUseAlways = 0


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

lrwxrwxrwx 1 root root 13 Jun  5 11:33 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 2044664 Apr 17 12:40 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1459 Jun  8 12:17 /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 es
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
EndSection

Section InputClass
Identifier  Synaptics Mouse
Driver  synaptics
MatchIsTouchpad on
# synaptics(4)
Option  TapButton11
Option  TapButton23
Option  TapButton32
Option  ClickPad  1
Option  SoftButtonAreas   60% 100% 0% 100% 46% 59% 0% 
100%
Option  AccelFactor   0.075
Option  MaxSpeed  2.8
Option  PressureMotionMaxFactor   2
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/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.41-2+deb7u2

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 29950 Jun  8 10:57 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[20.071] 
X.Org X Server 1.12.4
Release Date: 2012-08-27
[20.072] X Protocol Version 11, Revision 0
[20.072] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
[20.072] Current Operating System: Linux aire 3.2.0-4-amd64 #1 SMP Debian 
3.2.41-2+deb7u2 x86_64
[20.072] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=7038b669-c66a-46ee-8ccc-270aacdd9914 ro quiet
[20.072] Build Date: 17 April 2013  10:22:47AM
[20.072] xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) 
[20.072] Current version of pixman: 0.26.0
[20.072]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[20.072] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[20.072] (==) Log file: /var/log/Xorg.0.log, Time: Sat Jun  8 10:57:01 
2013
[20.099] (==) Using config file: /etc/X11/xorg.conf
[20.099] (==) Using system config directory /usr/share/X11/xorg.conf.d
[20.118] (==) No Layout section.  Using the first Screen section.
[20.118] (**) |--Screen Default Screen (0)
[20.118] (**) |   |--Monitor Configured Monitor
[20.118] (==) No device specified for screen Default Screen.
Using the first device section listed.
[20.118] (**) |   |--Device Configured Video Device
[20.118] (==) Automatically adding devices
[20.118] (==) Automatically enabling devices
[20.181] (WW) The directory

1 2 3 4 >

1 - 100 of 327 matches

Mail list logo