Processed: Re: Bug#752394: cups installation hangs in triggers

2014-06-24 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 important
Bug #752394 [cups] cups installation hangs in triggers
Severity set to 'important' from 'grave'

-- 
752394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#752394: cups installation hangs in triggers

2014-06-24 Thread Didier 'OdyX' Raboud
Control: severity -1 important

Le mardi, 24 juin 2014 02.13:10, vous avez écrit :
 On 2014-06-23 19:02:50 +0200, Didier 'OdyX' Raboud wrote:
  Can you reproduce this problem or was it a one-off problem?
 
 I tried to reproduce the problem by doing a reinstall on the cups
 related packages. I even did:
 (…)
 which corresponds to the upgrade, but again, everything is fine.

Well, if neither you or me are able to reproduce this problem (and noone 
else if experiencing it), I don't see how we'll be able to solve it; I'm 
therefore hereby downgrading this bug to important.

 Could you eventually attach your /etc/cups/cupsd.conf file?
 
 Attached, but AFAIK, that's the default file.

Indeed.

 I've looked at the /var/log/syslog messages, and here are the messages
 that occurred during the upgrade. They seem to be normal.
 
 [...]
 Jun 23 13:03:49 ypig PackageKit: daemon quit
 (…)
 Jun 23 13:07:52 ypig dbus[1959]: [system]
 Activating service name='org.freedesktop.PackageKit' (using
 servicehelper)
 Jun 23 13:07:52 ypig PackageKit: daemon start
 Jun 23 13:07:52 ypig dbus[1959]: [system] Successfully activated
 service 'org.freedesktop.PackageKit' [...]
 
 The messages at 13:04:53 and 13:06:53 correspond to ssh to the
 machine (since I did the upgrade remotely).
 
 I suspect that
 
   Jun 23 13:03:49 ypig PackageKit: daemon quit
 
 is related to the upgrade. I also got it when I retested the upgrade.

Indeed. It should work™.

Other things that come to mind are indeed PackageKit conflict, apparmor 
or SELinux configurations; do you have something custom in these areas?

Could you also find the /var/log/cups/error_log lines from the upgrade 
time, maybe?

Cheers,
OdyX


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



Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Vincent Lefevre
Package: cups
Version: 1.7.3-3
Severity: grave
Justification: renders package unusable

During an upgrade, I got:

[...]
Processing triggers for cups (1.7.3-3) ...

Then, nothing for 3 minutes. A ps output showed:

UIDPID  PPID  C STIME TTY  TIME CMD
root 20661 20645  0 13:03 pts/100:00:00 lpstat -h 
/var/run/cups/cups.sock -r

(thus started 3 minutes ago). I couldn't kill it from the terminal
with Ctrl-C or Ctrl-\. I had to start another terminal and do a
kill -9 on it.

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

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

Versions of packages cups depends on:
ii  cups-client1.7.3-3
ii  cups-common1.7.3-3
ii  cups-core-drivers  1.7.3-3
ii  cups-daemon1.7.3-3
ii  cups-filters   1.0.54-2
ii  cups-ppdc  1.7.3-3
ii  cups-server-common 1.7.3-3
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.05~dfsg-8.1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.19-3
ii  libc6  2.19-3
ii  libcups2   1.7.3-3
ii  libcupscgi11.7.3-3
ii  libcupsimage2  1.7.3-3
ii  libcupsmime1   1.7.3-3
ii  libcupsppdc1   1.7.3-3
ii  libgcc11:4.9.0-7
ii  libstdc++6 4.9.0-7
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13
ii  poppler-utils  0.24.5-4
ii  procps 1:3.3.9-5

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.2.1-1
ii  cups-filters [ghostscript-cups]  1.0.54-2
ii  printer-driver-gutenprint5.2.10-2

Versions of packages cups suggests:
ii  cups-bsd   1.7.3-3
pn  cups-pdf   none
ii  foomatic-db20140325-1
ii  hplip  3.14.6-1
ii  printer-driver-hpcups  3.14.6-1
pn  smbclient  none
ii  udev   204-10

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true


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



Processed: Re: Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 +moreinfo
Bug #752394 [cups] cups installation hangs in triggers
Added tag(s) moreinfo.

-- 
752394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Didier 'OdyX' Raboud
Control: tags -1 +moreinfo

Le lundi, 23 juin 2014, 13.13:12 Vincent Lefevre a écrit :
 During an upgrade, I got:
 
 [...]
 Processing triggers for cups (1.7.3-3) ...
 
 Then, nothing for 3 minutes. A ps output showed:
 
 UIDPID  PPID  C STIME TTY  TIME CMD
 root 20661 20645  0 13:03 pts/100:00:00 lpstat -h
 /var/run/cups/cups.sock -r
 
 (thus started 3 minutes ago). I couldn't kill it from the terminal
 with Ctrl-C or Ctrl-\. I had to start another terminal and do a
 kill -9 on it.

Apparently it waits on this line:

http://anonscm.debian.org/gitweb/?p=printing/cups.git;a=blob;f=debian/cups.postinst;hb=debian/1.7.3-3#l131

What does the lpstat -h /var/run/cups/cups.sock -r command give to 
you?

TIA, cheers,

OdyX

signature.asc
Description: This is a digitally signed message part.


Processed: Re: Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 +unreproducible
Bug #752394 [cups] cups installation hangs in triggers
Added tag(s) unreproducible.

-- 
752394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Didier 'OdyX' Raboud
Control: tags -1 +unreproducible

Hi again,

thanks for your time.

Le lundi, 23 juin 2014, 15.10:35 Vincent Lefevre a écrit :
 But sorry, I didn't give enough information about the upgrade.
 Actually, if I read correctly, the cups package wasn't installed
 in this upgrade, but it is its trigger that hangs.
 
 I'm copy-pasting the output I obtained in the terminal:

Nothing eyebrow-rising here…

 # service cups-browsed stop
 [ ok ] Stopping CUPS Bonjour daemon: cups-browsed.
 # lpstat -h /var/run/cups/cups.sock -r
 scheduler is running
 #
 
 No problems here. So, the problem could be due to something else.

Can you reproduce this problem or was it a one-off problem?

If so, could you increase the CUPS debug level to debug2 and send what 
is written to /var/log/cups/error_log when lpstat hangs?

What init system are you using?

Could you eventually attach your /etc/cups/cupsd.conf file?

Thanks in advance, cheers,
OdyX


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



Bug#752394: cups installation hangs in triggers

2014-06-23 Thread Vincent Lefevre
On 2014-06-23 19:02:50 +0200, Didier 'OdyX' Raboud wrote:
 Can you reproduce this problem or was it a one-off problem?

I tried to reproduce the problem by doing a reinstall on the cups
related packages. I even did:

  apt-get install --reinstall libslang2:amd64 libboost-iostreams1.54.0:amd64 
libboost-system1.54.0:amd64 libboost-chrono1.54.0:amd64 
libboost-program-options1.54.0:amd64 libboost-thread1.54.0:amd64 clang-3.4 
libclang-common-3.4-dev libllvm3.4:amd64 libclang1-3.4:amd64 libcupsfilters-dev 
libtiff5-dev:amd64 libtiffxx5:amd64 libtiff5:amd64 libcupsfilters1:amd64 
libfontembed1:amd64 fuse libfuse2:amd64 libibus-1.0-5:amd64 libicu52-dbg 
libicu-dev:amd64 icu-devtools libicu52:amd64 libimobiledevice4:amd64 
libsoundtouch0-dbg:amd64 libsoundtouch0:amd64 clang-3.4-doc clang-format-3.4 
gcc-doc-base gcc-4.9-doc cpp-4.9-doc cpp-doc cups-browsed 
cups-filters-core-drivers cups-filters flashplugin-nonfree gcc-doc 
gir1.2-ibus-1.0 liblist-allutils-perl libdatetime-timezone-perl 
libdevel-symdump-perl libgraphicsmagick3 libgraphicsmagick++3 
telepathy-mission-control-5 libmission-control-plugins0 libneon27-gnutls-dbg 
libneon27-gnutls libnet-dns-perl libnet-idn-encode-perl libperlio-gzip-perl 
libyaml-perl llvm-3.4-dev llvm-3.4 llvm-3.4-runtime llvm-3.4-doc perl-tk 
unicode-data xpp xserver-xorg-video-qxl libclang1-3.4-dbg libllvm3.4-dbg:amd64

which corresponds to the upgrade, but again, everything is fine.

 What init system are you using?

sysvinit

 Could you eventually attach your /etc/cups/cupsd.conf file?

Attached, but AFAIK, that's the default file.

I've looked at the /var/log/syslog messages, and here are the messages
that occurred during the upgrade. They seem to be normal.

[...]
Jun 23 13:00:35 ypig sensord:   temp1: 49.0 C
Jun 23 13:00:35 ypig sensord:   temp2: 42.0 C
Jun 23 13:00:35 ypig sensord:   temp3: 31.0 C
Jun 23 13:00:35 ypig sensord:   temp4: -128.0 C
Jun 23 13:03:49 ypig PackageKit: daemon quit
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: Ignoring 
non-user session 10 (class greeter)
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: (mostly) ignoring tty session '288' since it's not graphical
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: 
AcUserManager: (mostly) ignoring session '288' since it's not graphical
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: ActUser: 
adding session 288
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: sessions changed (user vlefevre) num=0
Jun 23 13:04:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: added session for user vlefevre
Jun 23 13:04:53 ypig gnome-session[32213]: DEBUG(+): GsmSystemd: received 
logind signal: SessionNew
Jun 23 13:04:53 ypig gnome-session[32213]: DEBUG(+): GsmSystemd: ignoring 
SessionNew signal
Jun 23 13:04:55 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: user vlefevre changed
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: Ignoring 
non-user session 10 (class greeter)
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: (mostly) ignoring tty session '289' since it's not graphical
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: 
AcUserManager: (mostly) ignoring session '289' since it's not graphical
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: ActUser: 
adding session 289
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: sessions changed (user vlefevre) num=0
Jun 23 13:06:53 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: added session for user vlefevre
Jun 23 13:06:53 ypig gnome-session[32213]: DEBUG(+): GsmSystemd: received 
logind signal: SessionNew
Jun 23 13:06:53 ypig gnome-session[32213]: DEBUG(+): GsmSystemd: ignoring 
SessionNew signal
Jun 23 13:06:55 ypig gdm-launch-environment][32210]: AccountsService: 
ActUserManager: user vlefevre changed
Jun 23 13:07:28 ypig console-kit-daemon[7849]: GLib-CRITICAL: Source ID 839 was 
not found when attempting to remove it
Jun 23 13:07:36 ypig kernel: [434502.405305] traps: ld-linux-x32.so[21737] 
general protection ip:fcbd sp:ff9986e8 error:0 in ld-2.19.so[f7761000+2]
Jun 23 13:07:37 ypig kernel: [434502.532327] traps: ld-linux-x32.so[21760] 
general protection ip:f7798cbd sp:fffa8cc8 error:0 in ld-2.19.so[f7782000+2]
Jun 23 13:07:37 ypig kernel: [434502.564322] traps: ld-linux-x32.so[21773] 
general protection ip:f77a5cbd sp:ffe63498 error:0 in ld-2.19.so[f778f000+2]
Jun 23 13:07:37 ypig kernel: [434502.592359] traps: ld-linux-x32.so[21786] 
general protection ip:f7797cbd sp:ffa36308 error:0 in ld-2.19.so[f7781000+2]
Jun 23 13:07:37 ypig kernel: [434503.020568] traps: ld-linux-x32.so[21833] 
general protection ip:f772dcbd sp:ffb84a08 error:0 in ld-2.19.so[f7717000+2]
Jun 23 13:07:37 ypig kernel: