Bug#876375: closed by Ben Hutchings (Re: Bug#876375: linux-headers-amd64: metapackage references nonexistent linux-headers-4.12.0-1-amd64 on buster)

[Claudio Moretti]

Hi Ben,

I'm using "deb http://http.debian.net/debian/ testing main contrib
non-free" which redirects to "http://cdn-fastly.deb.debian.org/debian/";,
but please note that this is also shown on packages.debian.org (
https://packages.debian.org/buster/linux-headers-amd64).

If I do an apt-cache search linux-headers I can see
linux-headers-4.12.0-2-amd64 available, but the linux-headers-amd64
metapackage references linux-headers-4.12.0-1-amd64 (0-1 instead of 0-2),
and linux-image-amd64 still tries to install 4.12.0-1 (instead of the
available 4.12.0-2)..

This is from
http://ftp.debian.org/debian/dists/testing/main/binary-amd64/Packages.xz

Package: linux-headers-amd64
Source: linux-latest (84)
Version: 4.12+84
Installed-Size: 12
Maintainer: Debian Kernel Team 
Architecture: amd64
Depends: linux-headers-4.12.0-1-amd64
Description: Header files for Linux amd64 configuration (meta-package)
Description-md5: c3bd37fd9656f71f4133642896829a35
Section: kernel
Priority: optional
Filename: pool/main/l/linux-latest/linux-headers-amd64_4.12+84_amd64.deb
Size: 5926
MD5sum: 380d0c64d622d67dd4abd64063c5d647
SHA256: ffb0ce6a11ea7d3c762a490da4280c59dfb5d490bd0eb1709bcc2f76cefadcf0

Understood that it was fixed in sid, but I'm on buster, and this is
effectively breaking, at least, dkms.

Claudio

On Thu, Sep 21, 2017 at 10:36 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the linux-headers-amd64 package:
>
> #876375: linux-headers-amd64: metapackage references nonexistent
> linux-headers-4.12.0-1-amd64 on buster
>
> It has been closed by Ben Hutchings .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings <
> b...@decadent.org.uk> by
> replying to this email.
>
>
> --
> 876375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876375
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Ben Hutchings 
> To: 876375-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 21 Sep 2017 22:33:30 +0100
> Subject: Re: Bug#876375: linux-headers-amd64: metapackage references
> nonexistent linux-headers-4.12.0-1-amd64 on buster
> Version: 4.12+85
>
> This was fixed a few days ago, but your mirror might not have caught up
> yet.
>
> Ben.
>
> --
> Ben Hutchings
> Design a system any fool can use, and only a fool will want to use it.
>
>
>
> -- Forwarded message --
> From: Claudio Moretti 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 21 Sep 2017 14:30:43 +0100
> Subject: linux-headers-amd64: metapackage references nonexistent
> linux-headers-4.12.0-1-amd64 on buster
> Package: linux-headers-amd64
> Version: 4.11+82
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
>  During a regular system upgrade, dkms rejected a build due to missing
>  kernel headers.
>  I checked for the presence of kernel headers against the current
>  kernel version (linux-image); the running kernel was
> linux-image-4.12.0-2,
>  the headers linux-headers-4.11.0-1
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  I tried to force the installation of linux-headers-amd64, but the
>  linux-headers-4.12.0-1-amd64 dependency could no be met due to the
>  package not being present in the repository.
>  Double checking
>  https://packages.debian.org/buster/linux-headers-amd64
>  confirms that "dep: linux-headers-4.12.0-1-amd64
>  Package not available"
>  The package does not appear to be available for i386 either
>
>   * What was the outcome of this action?
>  root@Not-Ubuntu:~# apt-get install linux-headers-amd64
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Some packages could not be installed. This may mean that you have
>  requested an impossible situation or if you are using the unstable
>  distribution that some required packages have not yet been created
>  or been moved out of Incoming.
>  The following information may help to resolve the situation:
>
>  The following packages have unmet dependencies:
>   linux-headers-amd64 : Depends: linux-headers-4.12.0-1-amd64 but it
>   is not installable
>   E: Unable to correct problems, you have held broken packages.
>
>* What outcome did you expect instead?
>  Successful installation of the ker

Bug#876375: linux-headers-amd64: metapackage references nonexistent linux-headers-4.12.0-1-amd64 on buster

[Claudio Moretti]

Package: linux-headers-amd64
Version: 4.11+82
Severity: important

Dear Maintainer,

   * What led up to the situation?
 During a regular system upgrade, dkms rejected a build due to missing
 kernel headers.
 I checked for the presence of kernel headers against the current
 kernel version (linux-image); the running kernel was linux-image-4.12.0-2,
 the headers linux-headers-4.11.0-1

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I tried to force the installation of linux-headers-amd64, but the
 linux-headers-4.12.0-1-amd64 dependency could no be met due to the
 package not being present in the repository.
 Double checking
 https://packages.debian.org/buster/linux-headers-amd64
 confirms that "dep: linux-headers-4.12.0-1-amd64
 Package not available"
 The package does not appear to be available for i386 either

  * What was the outcome of this action?
 root@Not-Ubuntu:~# apt-get install linux-headers-amd64
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  linux-headers-amd64 : Depends: linux-headers-4.12.0-1-amd64 but it
  is not installable
  E: Unable to correct problems, you have held broken packages.

   * What outcome did you expect instead?
 Successful installation of the kernel headers matching the current
 linux-image

Finally, please note that the info provided by reportbug is not current,
as it was collected after a system reboot. I'm not sure why it states
that linux-headers-amd64 depends on 4.11.0-1, as that's installed and
not what's causing the issue (see reported outcome above).

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

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

Versions of packages linux-headers-amd64 depends on:
ii  linux-headers-4.11.0-1-amd64  4.11.6-1

linux-headers-amd64 recommends no packages.

linux-headers-amd64 suggests no packages.

-- no debconf information

Bug#776747: iceweasel: cannot reproduce

[Claudio Moretti]

Control: severity -1 important

Hi,

I've installed Iceweasel 35.0.1-1 this morning, and so far I didn't get a 
single crash.
I believe the severity of this should be downgraded to, at least 
"important" (as it doesn't affect everyone).

Please be aware that this bug shows up from apt-listbugs when upgrading 
Iceweasel (hence my request of lowering the severity).

Thanks,

Claudio
Control: severity -1 importantHi,I've installed Iceweasel 35.0.1-1 this morning, and so far I didn't get a single crash.I believe the severity of this should be downgraded to, at least "important" (as it doesn't affect everyone).Please be aware that this bug shows up from apt-listbugs when upgrading Iceweasel (hence my request of lowering the severity).Thanks,Claudio


signature.asc
Description: Digital signature

Bug#760214:

[Claudio Moretti]

On Tue, 09 Sep 2014 20:50:59 +0400 ValdikSS  wrote:
> I can confirm this bug. This probably happened after networkmanager
> update. It seems like networkmanager intercepts route too late.
>
> Here are two workarounds:
> 1) add "route-delay 1" to your openvpn configuration file.
> 2) use route-nopull and redirect-gateway (without def1).
>

Thanks! I used #2 and it did the trick.
My route now seems more route-appropriate (if such a term exists)

claudio@Chuck:~$ ip ro
default via 10.4.0.5 dev tun0
10.4.0.5 dev tun0  proto kernel  scope link  src 10.4.0.6
169.254.0.0/16 dev wlan0  scope link  metric 1000
XXX.XXX.XXX.XXX via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16

I'll wait to see where this goes :)

Thanks again,

Claudio

Bug#760214: openvpn: fails to execute /sbin/ip route add 0.0.0.0/1 via

[Claudio Moretti]

Package: openvpn
Version: 2.3.2-9
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I was connecting through a VPN and realized that some website recognized
my VPN IP address, while some displayed my real IP.

The output of 'ip route' displayed my default gateway as my router,
instead of my VPN endpoint.

I have re-run openvpn and, in the output, I can see the following
command/entry:

Mon Sep  1 22:33:19 2014 /sbin/ip route add 0.0.0.0/1 via 10.4.0.5

But when I inspect ip route there is no record of it (removed my
endpoint IP)

root@Chuck:/home/claudio# ip ro
default via 192.168.1.1 dev wlan0  proto static  metric 1024 
10.4.0.1 via 10.4.0.5 dev tun0  proto static  metric 20 
10.4.0.5 dev tun0  proto kernel  scope link  src 10.4.0.6 
128.0.0.0/1 via 10.4.0.5 dev tun0  proto static  metric 20 
169.254.0.0/16 dev wlan0  scope link  metric 1000 
XXX.XXX.XXX.XXX via 192.168.1.1 dev wlan0 
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16


If I manually run 
/sbin/ip route add 0.0.0.0/1 via 10.4.0.5

then everything works fine.

All the other entries are present.
This are the last entries of the log (removed my MAC address); this did
not work even before I added bypass-dhcp to my VPN server config, so
it's safe to assume that's not the issue.

Mon Sep  1 22:33:19 2014 PUSH: Received control message:
'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS
8.8.8.8,route 10.4.0.1,topology net30,ping 10,ping-restart 120,ifconfig
10.4.0.6 10.4.0.5'
Mon Sep  1 22:33:19 2014 OPTIONS IMPORT: timers and/or timeouts modified
Mon Sep  1 22:33:19 2014 OPTIONS IMPORT: --ifconfig/up options modified
Mon Sep  1 22:33:19 2014 OPTIONS IMPORT: route options modified
Mon Sep  1 22:33:19 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option
options modified
Mon Sep  1 22:33:19 2014 ROUTE_GATEWAY 192.168.1.1/255.255.255.0
IFACE=wlan0 HWADDR=XX:XX:XX:XX:XX:XX
Mon Sep  1 22:33:19 2014 TUN/TAP device tun0 opened
Mon Sep  1 22:33:19 2014 TUN/TAP TX queue length set to 100
Mon Sep  1 22:33:19 2014 do_ifconfig, tt->ipv6=0,
tt->did_ifconfig_ipv6_setup=0
Mon Sep  1 22:33:19 2014 /sbin/ip link set dev tun0 up mtu 1500
Mon Sep  1 22:33:19 2014 /sbin/ip addr add dev tun0 local 10.4.0.6 peer
10.4.0.5
Mon Sep  1 22:33:19 2014 /sbin/ip route add 178.63.125.170/32 via
192.168.1.1
Mon Sep  1 22:33:19 2014 /sbin/ip route add 0.0.0.0/1 via 10.4.0.5
Mon Sep  1 22:33:19 2014 /sbin/ip route add 128.0.0.0/1 via 10.4.0.5
Mon Sep  1 22:33:19 2014 /sbin/ip route add 10.4.0.1/32 via 10.4.0.5
Mon Sep  1 22:33:19 2014 Initialization Sequence Completed


Let me know if there's any additional information I can provide.

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

Kernel: Linux 3.14-2-amd64 (SMP w/8 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 openvpn depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  initscripts2.88dsf-53.4
ii  iproute2   3.16.0-1
ii  libc6  2.19-10
ii  liblzo2-2  2.08-1
ii  libpam0g   1.1.8-3.1
ii  libpkcs11-helper1  1.11-1
ii  libssl1.0.01.0.1i-2

Versions of packages openvpn recommends:
ii  easy-rsa  2.2.2-1

Versions of packages openvpn suggests:
ii  openssl 1.0.1i-2
pn  resolvconf  

- -- Configuration Files:
/etc/default/openvpn changed:
AUTOSTART="none"
OPTARGS=""
OMIT_SENDSIGS=0


- -- debconf information:
  openvpn/create_tun: false

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQE6VAACgkQZ0Gi6TDJB+cmfACgk/LVgDSb0kskgQQ8n1IqJ3cl
6+wAnA3wklpE5e6/CsAIBssjmWxHDEYT
=jLHZ
-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#741479: [Bash-completion-devel] Bug#741479: bash-completion: Fails with bash: words: bad array subscript

[Claudio Moretti]

sid/unstable has bash 4.3-2, so I believe this is the right fix for that.

Probably not for bash < 4.3 (testing, stable, etc.) but should be ok for
sid :)

Claudio


On Thu, Mar 13, 2014 at 12:03 PM, Ville Skyttä  wrote:

> Looks like this occurs with bash >= 4.3 only, will need to find out if
> this is the correct fix for it.
>

Bug#741479: bash-completion: Fails with bash: words: bad array subscript

[Claudio Moretti]

Package: bash-completion
Version: 1:2.1-2
Severity: important
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

when "double tabbing" on a newly opened shell, an error is printed on
the console (instead of the list of files)

claudio@Chuck:/etc/bash_completion.d$ bash: words: bad array subscript

This bug was reported also on Launchpad[1] for Ubuntu, and from there I
retrieved the fix, which is changing line 710 of
/usr/share/bash-completion/bash_completion
from

[[ $cword -eq 0 ]] && return 1

to 

[[ $cword -le 0 ]] && return 1

I've attached my patch.

Thanks,

Claudio

[1] https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1289597

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

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

Versions of packages bash-completion depends on:
ii  bash  4.3-2
ii  dpkg  1.17.6

bash-completion recommends no packages.

bash-completion suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlMg0T8ACgkQZ0Gi6TDJB+fDSACgorxDZAxfqL5677jaHXO6zemD
LZQAn2Xgj4cvdAjJnJNlbShqZHNl0U5f
=djIY
-END PGP SIGNATURE-
--- /tmp/bash_completion	2014-03-12 21:20:18.961413462 +
+++ /usr/share/bash-completion/bash_completion	2014-03-12 21:20:50.361596183 +
@@ -707,7 +707,7 @@
 fi
 done
 
-[[ $cword -eq 0 ]] && return 1
+[[ $cword -le 0 ]] && return 1
 prev=${words[cword-1]}
 
 [[ ${split-} ]] && _split_longopt && split=true

Bug#722509: Still not working correctly

[Claudio Moretti]

Hi Jonas,

first of all, thanks for adding this option!

I am still encountering some issue, though: prechecks are failing at boot
time, because blkid does not recognize neither /dev/sda nor /dev/sda1 as
truecrypt disks (those are tcrypt-system disks).
I can "cheat" by adding "precheck=/bin/true", but even when passing those I
can't unlock my disk.

I was trying to patch the cryptdisks.functions file to add support for
"tcryptsystem", which IMHO/AFAIK is just

209,212d208
< tcryptsystem)
< USETCRYPT="yes"
< TCRYPTPARAMS="$TCRYPTPARAMS --tcrypt-system"
< ;;

when I came across cryptsetup's man page, which states that keyfiles in
truecrypt are different than LUKS keyfiles, and therefore cannot be used in
the same way.
However, even if I set "none" in crypttab's line, when I invoke
cryptdisks_start I get a "Failed to open key file" even if I put the
correct password in.

root@Chuck:/lib/cryptsetup# cryptdisks_start truecrypt
[] Starting crypto disk...[info] truecrypt (starting)...
Unlocking the disk /dev/sda (truecrypt)
Enter passphrase: Failed to open key file.
Unlocking the disk /dev/sda (truecrypt)
Enter passphrase: Failed to open key file.
Unlocking the disk /dev/sda (truecrypt)
[FAIL passphrase: truecrypt (failed)...failed.


Could you please take a look when you have the time?
I should also point out - even if it's probably unrelated - that trying to
unlock my disk manually even if the disk is not in use tells me that it is.
tcrypt-system disks like mine require you to use the whole disk as a device
(i.e. /dev/sda, not a partition like /dev/sdaX) so probably that's why this
happens:

root@Chuck:/home/claudio# cryptsetup open --type=tcrypt --tcrypt-system
/dev/sda truecrypt
Enter passphrase:
Cannot use device /dev/sda which is in use (already mapped or mounted).

I can (weirdly) make it work by using cryptsetup 1.7.0-git from a local
folder
root@Chuck:/home/claudio# ./projects/cryptsetup/src/cryptsetup open
--type=tcrypt --tcrypt-system /dev/sda truecrypt
Enter passphrase:
root@Chuck:/home/claudio# ls /dev/mapper/truecrypt
/dev/mapper/truecrypt


I don't know if this will have any impact on treucrypt unlocking at boot
time, though.

Thanks!

Claudio

P.S., FYI, I'm not sure, but I think that
 tcrypthidden)
TCRYPTPARAMS="$TCRYPTPARAMS --tcrypt-hidden"
;;

is missing USETCRYPT="yes"

Bug#738909: apt: Can not reproduce

[Claudio Moretti]

Package: apt
Followup-For: Bug #738909

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I cannot reproduce this bug.

I held apt before a dist-upgrade because of this bug; after reading it,
I unheld it and installed it.

I was not asked to remove anything; "apt-get install apt" and "apt-get
dist-upgrade" went perfectly fine.

IMHO, the reporter added experimental sources (like I did) and pinned
them in some way that prioritizes experimental over unstable (or lower).

Therefore, probably not a bug?

Unless somebody is able to reproduce it and/or the reporter gives more
details, I propose this bug report is closed, because it may scare
people into not upgrading while the problem is user-specific.

Cheers,

Claudio


- -- Package-specific info:

- -- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^kfreebsd-image.*";
APT::NeverAutoRemove:: "^gnumach$";
APT::NeverAutoRemove:: "^gnumach-image.*";
APT::NeverAutoRemove:: "^linux-image-3.12-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3.12-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3.12-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3.12-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3.12-1-amd64$";
APT::NeverAutoRemove:: "^postgresql-";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "[ ! -f /var/run/dbus/system_bus_socket ] || 
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt 
org.debian.apt.CacheChanged || true";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "4";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "5";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-9";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";
APT::Compressor::lzma::UncompressArg:: "-d";
APT::CompressorName "";
APT::CompressorExtension ".";
APT::CompressorBinary "";
APT::CompressorCost "100";
APT::CompressorCompressArg "";
APT::CompressorCompressArg:: "-9";
APT::CompressorUncompressArg "";
APT::CompressorUncompressArg:: "-d";
Dir "/";
Dir::State "var/lib/apt/";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::mirrors "mirrors/";
Dir::State::extended_states "extended_states";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt/";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcac

Bug#737350: gnome-shell: Plantronics D100A USB breaks system functionalities

[Claudio Moretti]

Package: gnome-shell
Version: 3.8.4-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I recently connected my Plantronics D100A USB dongle to my computer, to
have the associated headset working on the system.

When connected, the system "half-froze": the pointer was working in
Iceweasel, but not on the Desktop or on any icon on the Panel. Clicking
had no effect, unless (for example) I was switching tabs in the browser.

The overlay was not available, but Alt-Tab was. This is what dmesg
showed:

[29984.508953] usb 2-2: new full-speed USB device number 2 using
xhci_hcd
[29984.606288] usb 2-2: New USB device found, idVendor=047f,
idProduct=ab01
[29984.606297] usb 2-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[29984.606301] usb 2-2: Product: Plantronics D100
[29984.606304] usb 2-2: Manufacturer: Plantronics
[29984.635369] 2:1:1: cannot get freq at ep 0x4
[29984.649301] 2:2:1: cannot get freq at ep 0x84
[29985.081323] input: Plantronics Plantronics D100 as
/devices/pci:00/:00:1c.3/:04:00.0/usb2/2-2/2-2:1.3/input/input20
[29985.081814] hid-generic 0003:047F:AB01.0003: input,hiddev0,hidraw0:
USB HID v1.11 Device [Plantronics Plantronics D100] on
usb-:04:00.0-2/input3
[29985.115053] 2:2:1: cannot get freq at ep 0x84
[29985.121192] 2:2:1: cannot get freq at ep 0x84
[29985.148095] 2:1:1: cannot get freq at ep 0x4
[29985.154177] 2:1:1: cannot get freq at ep 0x4
[29985.166145] 2:2:1: cannot get freq at ep 0x84
[29985.173179] 2:2:1: cannot get freq at ep 0x84
[29985.199111] 2:1:1: cannot get freq at ep 0x4
[29985.208147] 2:1:1: cannot get freq at ep 0x4
[29985.226136] 2:2:1: cannot get freq at ep 0x84
[29985.232128] 2:2:1: cannot get freq at ep 0x84


Unplugging the USB dongle immediately restored all functionalities in
the system.

A similar bug (probably the same issue) was reported for Fedora 18
(different headset/dongle, same outcome), which is available at 

https://bugzilla.redhat.com/show_bug.cgi?id=912859

but it's bound to be marked as WONTFIX as Fedora 18 is approaching EOL.

Still, the issue is present in Debian and I'm not so sure it's a X.Org
issue as much as a gnome-shell one (but feel free to prove me wrong, I
don't have any proof to support this).

Thanks in advance!

Claudio



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  evolution-data-server3.8.5-3
ii  gdm3 3.8.4-6
ii  gir1.2-accountsservice-1.0   0.6.34-2
ii  gir1.2-caribou-1.0   0.4.12-1
ii  gir1.2-clutter-1.0   1.14.4-3
ii  gir1.2-freedesktop   1.36.0-2+b1
ii  gir1.2-gcr-3 3.8.2-4
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.36.0-2+b1
ii  gir1.2-gmenu-3.0 3.8.0-2
ii  gir1.2-gnomebluetooth-1.03.8.1-2
ii  gir1.2-gnomedesktop-3.0  3.8.4-2
ii  gir1.2-gtk-3.0   3.8.6-1
ii  gir1.2-ibus-1.0  1.5.4-1
ii  gir1.2-mutter-3.03.8.4-2
ii  gir1.2-networkmanager-1.00.9.8.0-5
ii  gir1.2-nmgtk-1.0 0.9.8.4-1
ii  gir1.2-pango-1.0 1.36.0-1+b1
ii  gir1.2-polkit-1.00.105-4
ii  gir1.2-soup-2.4  2.44.2-1
ii  gir1.2-telepathyglib-0.120.22.0-1
ii  gir1.2-telepathylogger-0.2   0.8.0-2
ii  gir1.2-upowerglib-1.00.9.23-2+b1
ii  gjs  1.36.1-2
ii  gnome-bluetooth  3.8.1-2
ii  gnome-icon-theme-symbolic3.10.1-1
ii  gnome-settings-daemon3.8.5-2
ii  gnome-shell-common   3.8.4-5
ii  gnome-themes-standard3.8.4-1
ii  gsettings-desktop-schemas3.8.2-2
ii  libatk-bridge2.0-0   2.10.2-2
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-97
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcamel-1.2-43  3.8.5-3
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libclutter-1.0-0 1.14.4-3
ii  libcogl-pango12 

Bug#731569: Beep

[Claudio Moretti]

Might I add that my system annoyingly beeps every time PackageKit spams a
message?

It scared the hell out of me the first few time (now I got it, but it's
still annoying :/ )

Bug#724739: gnome-shell: Overview does not respect desktop background

[Claudio Moretti]

Package: gnome-shell
Version: 3.8.4-5
Followup-For: Bug #724739

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I can confirm that this bug still happens using 3.8.4-5

I have a custom XML file that I use to change the desktop background
every 10 minutes. What happens is that when the desktop background
changes, the background of the overview doesn't. Moreover, the
background of the workspace overview is different from the one of the
overview itself.

They appear to randomly change, at some point, but with no apparent
trigger.

In these two images you can see what I am experiencing:

http://imageshack.com/a/img689/5695/7sdy.png
http://imageshack.com/a/img853/5889/y8ll.png

Is there any way to fix this? I haven't tried, but shouldn't this be
happening also with the default Adwaita XML changes-during-the-day
background?

Logout and login fixes it, but as soon as the first BG change happens,
the problem reappears.

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  evolution-data-server3.8.5-3
ii  gdm3 3.8.4-6
ii  gir1.2-accountsservice-1.0   0.6.34-2
ii  gir1.2-caribou-1.0   0.4.12-1
ii  gir1.2-clutter-1.0   1.14.4-3
ii  gir1.2-freedesktop   1.36.0-2+b1
ii  gir1.2-gcr-3 3.8.2-4
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.36.0-2+b1
ii  gir1.2-gmenu-3.0 3.8.0-2
ii  gir1.2-gnomebluetooth-1.03.8.1-2
ii  gir1.2-gnomedesktop-3.0  3.8.4-2
ii  gir1.2-gtk-3.0   3.8.6-1
ii  gir1.2-ibus-1.0  1.5.4-1
ii  gir1.2-mutter-3.03.8.4-2
ii  gir1.2-networkmanager-1.00.9.8.0-5
ii  gir1.2-nmgtk-1.0 0.9.8.4-1
ii  gir1.2-pango-1.0 1.36.0-1+b1
ii  gir1.2-polkit-1.00.105-4
ii  gir1.2-soup-2.4  2.44.2-1
ii  gir1.2-telepathyglib-0.120.22.0-1
ii  gir1.2-telepathylogger-0.2   0.8.0-2
ii  gir1.2-upowerglib-1.00.9.23-2+b1
ii  gjs  1.36.1-2
ii  gnome-bluetooth  3.8.1-2
ii  gnome-icon-theme-symbolic3.10.1-1
ii  gnome-settings-daemon3.8.5-2
ii  gnome-shell-common   3.8.4-5
ii  gnome-themes-standard3.8.4-1
ii  gsettings-desktop-schemas3.8.2-2
ii  libatk-bridge2.0-0   2.10.0-1+b1
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-97
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcamel-1.2-43  3.8.5-3
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libclutter-1.0-0 1.14.4-3
ii  libcogl-pango12  1.14.0-3
ii  libcogl121.14.0-3
ii  libcroco30.6.8-2
ii  libdbus-1-3  1.6.18-2
ii  libdbus-glib-1-2 0.100.2-1
ii  libecal-1.2-15   3.8.5-3
ii  libedataserver-1.2-173.8.5-3
ii  libegl1-mesa [libegl1-x11]   9.2.2-1
ii  libgck-1-0   3.8.2-4
ii  libgcr-base-3-1  3.8.2-4
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libgirepository-1.0-11.36.0-2+b1
ii  libgjs0c [libgjs0-libmozjs185-1.0]   1.36.1-2
ii  libglib2.0-0 2.36.4-1
ii  libgnome-menu-3-03.8.0-2
ii  libgstreamer1.0-01.2.1-1
ii  libgtk-3-0   3.8.6-1
ii  libical0 0.48-2
ii  libjson-glib-1.0-0   0.16.2-1
ii  libmozjs185-1.0  1.8.5-1.0.0+dfsg-4+b1
ii  libmutter0b  3.8.4-2
ii  libnm-glib4  0.9.8.0-5
ii  libnm-gtk0   0.9.8.4-1
ii  libnm-util2   

Bug#724586: tinyca: Mixed up when OU has a whitespace in it

[Claudio Moretti]

Package: tinyca
Version: 0.7.5-4
Followup-For: Bug #724586

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I believe this also happens when the OU field is filled in with a string
that contains a whitespace.

When generating a certificate, I wanted to input 'My Organization'
(without quotes) in the OU field. I was getting a "Can't find the request" 
error. This was
because openssl failed to create a request using the MDC2 algorithm.
- From the debug (stripped from sensitive data):

claudio@Chuck:~/.TinyCA/tmp$ tinyca2 
defined(@array) is deprecated at /usr/share/tinyca/GUI.pm line 1252.
(Maybe you should just omit the defined()?)
defined(@array) is deprecated at /usr/share/tinyca/GUI.pm line
1300.
(Maybe you should just omit the defined()?)
DEBUG call: /usr/bin/openssl req -new -keyform PEM
-outform PEM -passin env:SSLPASS -config
/home/claudio/.TinyCA/My_CA/openssl.cnf -out

/home/claudio/.TinyCA/My_CA/req/Z2l0LmNtb3JldHRpLml0Omhvc3RtYXN0ZXJAY21vcmV0dGkuaXQ6R2l0TGFiIFNlcnZlcjpjbW9yZXR0aS5pdDogOkl0YWx5OklU.pem
-key

/home/claudio/.TinyCA/My_CA/keys/Z2l0LmNtb3JldHRpLml0Omhvc3RtYXN0ZXJAY21vcmV0dGkuaXQ6R2l0TGFiIFNlcnZlcjpjbW9yZXR0aS5pdDogOkl0YWx5OklU.pem
-mdc2
DEBUG: add to dn: IT
DEBUG: add to dn: Italy
DEBUG: add to dn: .
DEBUG: add to dn: example.org
DEBUG: add to dn: My Organization<-- THIS IS THE OU 
field
DEBUG: add to dn: subdomain.example.org
DEBUG: add to dn: hostmas...@example.org
DEBUG: add to dn: 
DEBUG: add to dn: 
DEBUG return: /usr/bin/openssl req -new -keyform PEM
-outform PEM -passin env:SSLPASS -config
/home/claudio/.TinyCA/My_CA/openssl.cnf -out

/home/claudio/.TinyCA/My_CA/req/Z2l0LmNtb3JldHRpLml0Omhvc3RtYXN0ZXJAY21vcmV0dGkuaXQ6R2l0TGFiIFNlcnZlcjpjbW9yZXR0aS5pdDogOkl0YWx5OklU.pem
-key

/home/claudio/.TinyCA/My_CA/keys/Z2l0LmNtb3JldHRpLml0Omhvc3RtYXN0ZXJAY21vcmV0dGkuaXQ6R2l0TGFiIFNlcnZlcjpjbW9yZXR0aS5pdDogOkl0YWx5OklU.pem
-mdc2

unknown option -mdc2
req [options] outfile
where options  are
[stripped the rest]

Also, in the Key Generation windows, a DSA key was created, but I
specified I wanted an RSA key.

After lots of retries, I tried to input the OU field with quotes: "My
Organization". It worked perfectly.

I believe that this is what caused the "radio fields" problem in the
first place. Please correct me if I'm wrong.

Thanks,

Claudio


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

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

Versions of packages tinyca depends on:
ii  libgtk2-perl2:1.248-1
ii  liblocale-gettext-perl  1.05-7+b2
ii  openssl 1.0.1e-4

Versions of packages tinyca recommends:
ii  zip  3.0-8

tinyca suggests no packages.

- -- no debconf information

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

iEYEARECAAYFAlJ/nMYACgkQZ0Gi6TDJB+dtPQCZAQ3o0ULEl4397+ShdlNPy3VH
gJcAoObOk2qyqkEpzMWYzwImJ/h4nCBw
=6NeO
-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#722509: cryptsetup: crypttab/cryptdisks_start does not recognize tcrypt and tcrypt-system. Reports bad variable name

[Claudio Moretti]

Package: cryptsetup
Version: 2:1.6.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I am trying to unlock and mount, at boot time, a truecrypt (AES)
partition.

Since cryptsetup v1.6.0, support was added for unlocking truecrypt
(normal and system-encrypted) partitions and, using cryptsetup from CLI,
I am able to unlock said partition.

My entry in /etc/crypttab reads

> truecrypt /dev/sda /etc/tcrypt.key tcrypt-system

And should unlock the disk. Instead, I am receiving this error (manually
generated invoking 'cryptdisks_start truecrypt' from root)

> [] Starting crypto disk.../usr/sbin/cryptdisks_start: 1: export:
> CRYPTTAB_OPTION_tcrypt-system: bad variable name

Installing cryptsetup v1.7.0-git from directly compiled sources did not
solve the problem.

A current, possible workaround is to invoke cryptsetup from
/etc/rc.local followed by mount -a (if there are the correspondent fstab
entries) or by a series of 'mount' commands, specific to the unlocked
disk.

This should not be necessary, though; can this error be fixed?

(Also, unrelated, cryptsetup 1.6.2 is available, so this could be fixed
when updating; 1.6.1 has some issues with handling truecrypt devices,
which, to my understanding, were fixed in 1.6.2)

Tnanks,

Claudio Moretti


- -- Package-specific info:
- -- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10-2-amd64 root=UUID=9ca591a4-1e0d-4057-a9d0-cbbbdc4b9dfb 
ro quiet

- -- /etc/crypttab
sda3_crypt UUID=c98d85cc-213c-4f21-ba91-71c90f3d2ae5 none luks
sda4_crypt UUID=59e0cb59-3bfd-44ec-9077-b0d953f927e3 /etc/sda4.key luks
truecrypt /dev/sda /etc/tcrypt.key tcrypt-system

- -- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
proc/proc   procdefaults0   0
/dev/mapper/sda3_crypt /   ext4errors=remount-ro,acl,user_xattr 
0   1
# /boot was on /dev/sda2 during installation
UUID=feacb7ce-366e-45bf-9c7d-3490f89a8957 /boot   ext2defaults  
  0   2
# Home filesystem
/dev/mapper/sda4_crypt  /home   ext4defaults0   2
# Windows 7
#/dev/mapper/truecrypt  /media/disk ntfs-3g rw,uid=1000 0   0
# Windows 7 folders
#/media/disk/Users/Claudio/Videos/ /home/claudio/Videos/ none bind 0 0
#/media/disk/Users/Claudio/Music/ /home/claudio/Music/ none bind 0 0
#/media/disk/Users/Claudio/Desktop/Uni/ /home/claudio/Desktop/Uni/ none bind 0  
   0
# Others
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
#/dev/sdb1   /media/usb0 autorw,user,noauto  0   0
#/dev/sdc1   /media/usb1 autorw,user,noauto  0   0
#/dev/sdc2   /media/usb2 autorw,user,noauto  0   0

- -- lsmod
Module  Size  Used by
blowfish_generic   12464  0 
blowfish_x86_6421132  0 
blowfish_common16487  2 blowfish_generic,blowfish_x86_64
ecb12737  0 
des_generic20851  0 
cast5_generic  20813  0 
cast_common12313  1 cast5_generic
cbc12696  0 
twofish_generic16569  0 
twofish_avx_x86_64 46079  0 
twofish_x86_64_3way25556  1 twofish_avx_x86_64
twofish_x86_64 12541  2 twofish_avx_x86_64,twofish_x86_64_3way
twofish_common 20585  4 
twofish_generic,twofish_avx_x86_64,twofish_x86_64_3way,twofish_x86_64
serpent_avx_x86_64 46241  0 
serpent_sse2_x86_6450185  0 
serpent_generic25044  2 serpent_sse2_x86_64,serpent_avx_x86_64
xts12722  2 serpent_sse2_x86_64,twofish_x86_64_3way
algif_skcipher 13118  0 
af_alg 12988  1 algif_skcipher
ip6table_filter12540  0 
ip6_tables 22050  1 ip6table_filter
iptable_filter 12536  0 
ip_tables  22036  1 iptable_filter
ebtable_nat12580  0 
ebtables   26253  1 ebtable_nat
x_tables   19041  5 
ip6table_filter,ip_tables,iptable_filter,ebtables,ip6_tables
parport_pc 22409  0 
bnep   17535  2 
ppdev  12763  0 
rfcomm 33471  0 
lp 13025  0 
parport31901  3 lp,ppdev,parport_pc
bluetooth 170002  10 bnep,rfcomm
cpufreq_userspace  12576  0 
cpufreq_stats  12866  0 
cpufreq_conservative14184  0 
cpufreq_powersave  12454  0 
bbswitch   12866  0 
binfmt_misc12925  1 
uinput 17439  1 
ext2   59601  1 
loop   22869  0 
fuse   67503  3 
snd_hda_codec_hdmi 31720  1 
snd_hda_codec_realtek32712  1 
iTCO_wdt   12831  0 
iTCO_vendor_support12704  1 iTCO_wdt
joydev

Bug#511896: Still happening

[Claudio Moretti]

Still happening, to the best of my knowledge.
I was trying to set up an encrypted partition where a previous (also
encrypted) partition was, without changing the partition scheme, but it
kept coming back to the partitioning screen.

After trying for 3 times (three different reboots) I decided to delete the
partition (not because of this, but because I was lacking a swap partition
and I thought that might be the issue) and after creating two separate
partitions, the installation proceeded.

Image: debian-testing-amd64-netinst.iso
Downloaded today from the daily builds.

Greetings,

Claudio

Bug#709002:

[Claudio Moretti]

2.2.2 works fine for me too on Debian sid.

Is it possible to update the repo? The only requirement mentioned on the
project webpage is JVM >= 1.6

Thanks!

Claudio

Bug#709002: Can confirm on repository version

[Claudio Moretti]

I'm having the same problem with the in-repo version.

root@Chuck:/home/claudio# apt-cache policy pdfsam
pdfsam:
  Installed: 1.1.4-2
  Candidate: 1.1.4-2
  Version table:
 1.1.4-2 0
   1001 http://ftp.debian.org/debian/ sid/main amd64 Packages

I'm currently downloading the source files for 2.2.2, so I can confirm that
that version is working.

Cheers,

Claudio

Bug#706268: net-tools: ifconfig does not detect interfaces at boot even after Required-Start: $network network-manager

[Claudio Moretti]

Package: net-tools
Version: 1.60-24.2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

ifconfig is unable to detect interfaces on a system at boot time, thus
making dependent scripts fail.
I noticed this after reporting #680212 because the output of
ifconfig during the bind9 initscript was empty.

I believed that it was related to the mounting of external filesystems
in /etc/fstab (ntfs-3g and several folders mounted with -o bind) because
removing them allowed me to see the output of ifconfig; when I retried
this afternoon, remoing those entries had no effect.

For the record, I edited the bind9 initscript in the check_network()
function, adding a couple of echo and output redirections.

Below is the output of today's testing:

===
Sat Apr 27 14:11:11 CEST 2013
You are user root
Output of /sbin/ifconfig is:

===
Sat Apr 27 14:14:07 CEST 2013
You are user root
Booting without binding NTFS folders in fstab
Output of /sbin/ifconfig is:

===
Sat Apr 27 14:17:29 CEST 2013
Booting without mounting NTFS drive in /etc/fstab
You are user root
Output of /sbin/ifconfig is:

===
Sat Apr 27 14:18:58 CEST 2013
Booting without mounting NTFS drive in /etc/fstab
You are user root
Output of /sbin/ifconfig is:

and my check_network() function is

=
check_network() {
if [ -x /usr/bin/uname ] && [ "X$(/usr/bin/uname -o)" = XSolaris ];
then
IFCONFIG_OPTS="-au"
else
IFCONFIG_OPTS=""
fi
if [ -z "$(/sbin/ifconfig $IFCONFIG_OPTS)" ]; then
   #log_action_msg "No networks configured."
   echo "===" >>
/var/log/claudio-boot.log
   echo $(/bin/date) >> /var/log/claudio-boot.log
   echo "Booting without mounting NTFS drive in /etc/fstab" >>
/var/log/claudio-boot.log
   echo "You are user $(/usr/bin/whoami)" >>
/var/log/claudio-boot.log
   echo "Output of /sbin/ifconfig is:" >> /var/log/claudio-boot.log
   echo $(/sbin/ifconfig) >> /var/log/claudio-boot.log
   return 1
fi
return 0
}
=

This prevents BIND9 from starting (thus my decision about the severity)
but it could affect every other package that is supposed to start when
$network is started.

Thanks,

Claudio

- -- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (1001, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages net-tools depends on:
ii  libc6  2.13-38

net-tools recommends no packages.

net-tools suggests no packages.

- -- no debconf information

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

iEYEARECAAYFAlF7yVAACgkQZ0Gi6TDJB+fuhwCg3LLOIB58Ngcp6OugTJh4iIBn
IPkAniH9tWkYVG/oefXb59IhRdG6Od3t
=3LyA
-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#702802: amarok: [experimental] Amarok 2.7.0-1 missing /usr/lib/libamarok_service_lastfm_shared.so

[Claudio Moretti]

Package: amarok
Version: 2.7.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

   * What led up to the situation?
   Trying to edit Last.FM configuration options, I was presented with a
   "Missing library" message
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I tried to open Settings > Configure Amarok > Plugins > Last.FM
 configuration
   * What was the outcome of this action?
   Error message about missing library
   * What outcome did you expect instead?
   The configuration options window shown

   I have managed to solve this issue by manually downloading
   amarok_2.7.0-1_amd64.deb from the Ubuntu repository, dpkg --extract
   it and copying libamarok_service_lastfm_shared.so in /usr/lib.

   I did not have even to restart Amarok: it worked right away.

   Can Amarok be rebuilt or repackaged with this library included?

   Cheers,

   Claudio

   P.S.
   I don't exactly know how this works for experimental packages; I just
   hope that filing a bug was the right way, but if it is necessary I
   can subscribe to the correct mailing list and report it there.



- -- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (1001, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages amarok depends on:
ii  amarok-common 2.7.0-1
ii  amarok-utils  2.7.0-1
ii  kde-runtime   4:4.8.4-2
ii  libaio1   0.3.109-3
ii  libavcodec-extra-53   6:0.8.5-1
ii  libavformat53 6:0.8.5-1
ii  libavutil51   6:0.8.5-1
ii  libc6 2.13-38
ii  libcurl3-gnutls   7.29.0-1
ii  libgcc1   1:4.7.2-5
ii  libgcrypt11   1.5.0-5
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgpod4  0.8.2-7
ii  libkcmutils4  4:4.8.4-4
ii  libkdecore5   4:4.8.4-4
ii  libkdeui5 4:4.8.4-4
ii  libkdewebkit5 4:4.8.4-4
ii  libkdnssd44:4.8.4-4
ii  libkfile4 4:4.8.4-4
ii  libkio5   4:4.8.4-4
ii  libknewstuff3-4   4:4.8.4-4
ii  liblastfm11.0.7-1
ii  libloudmouth1-0   1.4.3-9
ii  libmtp9   1.1.3-35-g0ece104-5
ii  libmysqlclient18  5.5.29+dfsg-1
ii  libofa0   0.9.3-5
ii  libphonon44:4.6.0.0-3
ii  libplasma34:4.8.4-4
ii  libqjson0 0.7.1-7
ii  libqt4-dbus   4:4.8.2+dfsg-11
ii  libqt4-network4:4.8.2+dfsg-11
ii  libqt4-script 4:4.8.2+dfsg-11
ii  libqt4-sql4:4.8.2+dfsg-11
ii  libqt4-svg4:4.8.2+dfsg-11
ii  libqt4-xml4:4.8.2+dfsg-11
ii  libqtcore44:4.8.2+dfsg-11
ii  libqtgui4 4:4.8.2+dfsg-11
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.2.1-5
ii  libsolid4 4:4.8.4-4
ii  libstdc++64.7.2-5
ii  libtag-extras11.0.1-3
ii  libtag1c2a1.8-1
ii  libthreadweaver4  4:4.8.4-4
ii  libx11-6  2:1.5.0-1
ii  libxml2   2.8.0+dfsg1-7+nmu1
ii  phonon4:4.6.0.0-3
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages amarok recommends:
ii  clamz  0.5-1
ii  kdemultimedia-kio-plugins  4:4.8.4-2

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.2+dfsg-11
pn  libqt4-sql-psql
pn  libqt4-sql-sqlite  
pn  moodbar

Versions of packages amarok-common depends on:
ii  perl  5.14.2-20

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-gstreamer [phonon-backend]  4:4.6.0.0-2
ii  phonon-backend-vlc [phonon-backend]0.6.0-1

- -- no debconf information

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

iEYEARECAAYFAlE+CqYACgkQZ0Gi6TDJB+cgOwCdH8lJQDgEvBDSfczuuLCw0SO2
CpgAoMTUnlqANTZBr27NEf2p+IjbA+Ku
=Iss6
-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#680212: Updates

[Claudio Moretti]

I have edited /etc/init.d/bind9 to write the output of /sbin/ifconfig in a
logfile
Here's the edited version:

==
if [ -z "$(/sbin/ifconfig $IFCONFIG_OPTS)" ]; then
   #log_action_msg "No networks configured."
   echo "You are user $(/usr/bin/whoami)" >> /var/log/claudio-boot.log
   echo "Output of /sbin/ifconfig is" >> /var/log/claudio-boot.log
   echo $(/sbin/ifconfig) >> /var/log/claudio-boot.log
   return 1
fi
==

And that's the output:

==
You are user root
Output of /sbin/ifconfig is

==

The blank row is in the logfile, meaning that I actually have a blank
output from /sbin/ifconfig

That prevents bind9 from starting at boot time, and I think it may be a
serious problem.

Here't the contents of /etc/network/interfaces

==
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
==

Can somebody help me?

Thanks,

Claudio

Bug#534644: os-prober: ignores separate boot partition when mounted

[Claudio Moretti]

Package: os-prober
Version: 1.56
Followup-For: Bug #534644


I had this problem for a while: os-prober does not recognize Windows
(any version) when the Windows partition is mounted. And this is really
annoying for someone who wants to share their files between two
different OSes.

I hope I am not wrong, but I think that this bug severity should be
raised to "important", because anyone who needs os-prober
(regardless of the fact that it comes by default with GRUB) because they
have a dual boot system is likely to mount the other partition at some
point.
In that moment, if grub-update is launched (or triggered by APT - which
is more likely), the OS in the mounted partition will disappear from the
boot list (at least until update-grub is launched/triggered again with
the OS partition not mounted.).

I was able to reproduce this bug by launching os-prober from root with
the mounted partitions, obtaining no output. After manually unmounting
the partitions, os-prober returns the correct list. 

Then, I have mounted the partitions again (see below) and re-launched
os-prober:

claudio@Chuck:~$ sudo os-prober 
[sudo] password for claudio: 
/dev/sda1:Windows 8 (loader):Windows:chain
claudio@Chuck:~$ sudo mount -a
claudio@Chuck:~$ sudo os-prober 
claudio@Chuck:~$ 

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (1001, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages os-prober depends on:
ii  libc6  2.13-37

os-prober recommends no packages.

os-prober 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#680212: Started happening again

[Claudio Moretti]

A few weeks ago, I started to experience this issue again, even if BIND
starts after network manager.

root@Chuck:/home/claudio# /etc/init.d/bind9 status
[FAIL] bind9 is not running ... failed!
root@Chuck:/home/claudio# /etc/init.d/bind9 start
[ ok ] Starting domain name service...: bind9.
root@Chuck:/home/claudio# /etc/init.d/bind9 status
[ ok ] bind9 is running.

root@Chuck:/home/claudio# ls /etc/rc2.d/
README   S20acpi-support   S21bluetooth S24isc-dhcp-server
S01motd   S20anacron S21cpufrequtils S24kerneloops
S01nvidia-kernel   S20apmd S21network-manager  S24rsync
S16rpcbind   S20atd S23bind9 S24samba
S17nfs-common   S20dbus S23cups S25minissdpd
S19acpi-fakekeyS20lastfmsubmitd  S23gdm3 S25rc.local
S19binfmt-support  S20loadcpufreqS23pulseaudio S25rmnologin
S19hostapd   S20ntp S23saned S25stop-bootlogd
S19rsyslog   S20openbsd-inetd  S24bootlogs
S19sudo   S20ssh S24bumblebeed
S20acpid   S21avahi-daemon   S24cron

root@Chuck:/home/claudio# head -n 14 /etc/init.d/bind9
#!/bin/sh -e

### BEGIN INIT INFO
# Provides:  bind9
# Required-Start:$remote_fs
# Required-Stop: $remote_fs
# Should-Start:  $network $syslog network-manager
# Should-Stop:   $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: Start and stop bind9
# Description:   bind9 is a Domain Name Server (DNS)
#which translates ip addresses to and from internet names
### END INIT INFO

If you need any other information, just ask :)

Thanks!

Claudio

Bug#690023: Also happening here

[Claudio Moretti]

I can confirm this: after trying to update my OpenWRT repository, I get the
same error and I'm unable to continue.

claudio@Chuck:~/projects/openwrt$ svn up
Updating '.':
Utools/Makefile
svn: E235000: In file
'/tmp/buildd/subversion-1.7.5/subversion/libsvn_wc/update_editor.c' line
1583: assertion failed (action == svn_wc_conflict_action_edit || action ==
svn_wc_conflict_action_delete || action == svn_wc_conflict_action_replace)
Aborted

claudio@Chuck:~/projects/openwrt$ svn --version
svn, version 1.7.5 (r1336830)
   compiled Jun 17 2012, 07:52:38

Copyright (C) 2012 The Apache Software Foundation.
This software consists of contributions made by many people; see the NOTICE
file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using
Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
  - handles 'http' scheme
  - handles 'https' scheme

Bug#680212: Partially worked for me

[Claudio Moretti]

I tried it both on my laptop and on my work computer.. It worked on my
laptop, it didn't on my work PC.
But maybe it'll work after another reboot (which I won't be able to try
until the end of August)

Bug#680212: bind9 fails to start at boot: /sbin/ipconfig fails, reports "no networks configured"

[Claudio Moretti]

Package: bind9
Version: 1:9.8.1.dfsg.P1-4.1
Severity: important

Dear Maintainer,
A couple of weeks ago, after an upgrade, when I rebooted my computer
bind9 did not start. During system loading, it failed and reported "No
networks configured".
I can't copy the exact message as I wasn't able to find those messages
in /var/log

I tried to remove, and then purge, bind9 and its related packages
(avahi-daemon bind9 bind9-host bind9utils dlint dnsutils gnome-nettool
gnome-user-share host libapache2-mod-dnssd libnss-mdns
pulseaudio-module-zeroconf telepathy-salut)

and after that removing the contents of /usr/share/bind9, /etc/bind and
/var/cache/bind, along with the three folders.

I cleaned APT cache, reinstalled bind9 (and all the other packages) but
when I rebooted, bind9 gave the same error.

The strange thing is that if I start BIND manually (sudo
/etc/init.d/bind9 start) it gives no errors.

The issue seems to origin in the init.d script, because it fails the
check_network() function.

Perhaps $network should be a Required-Start for a DNS server? (I know
that even Should-Start should do, but I believe networking is a required
feature for a DNS server, not an optional one) I tried to manually edit
the /etc/init.d/bind9 file, but insserv keeps giving it a S20 priority,
while network-manager is S21.

The "edited" file attached below, was edited but then restored to its
original settings.

Below, I attached the contents of my /etc/init.d/ and /etc/rc2.d/

Thanks,
Claudio

claudio@Chuck:~$ ls -1 /etc/init.d/
acpid
acpi-fakekey
acpi-support
alsa-utils
anacron
apmd
atd
avahi-daemon
bind9
binfmt-support
bluetooth
bootlogd
bootmisc.sh
bumblebeed
checkfs.sh
checkroot-bootclean.sh
checkroot.sh
console-setup
cpufrequtils
cron
cryptdisks
cryptdisks-early
cups
dbus
gdm3
halt
hdparm
hostapd
hostname.sh
hwclock.sh
ifupdown
ifupdown-clean
jetty
kbd
kerneloops
keyboard-setup
killprocs
kmod
loadcpufreq
minissdpd
motd
mountall-bootclean.sh
mountall.sh
mountdevsubfs.sh
mountkernfs.sh
mountnfs-bootclean.sh
mountnfs.sh
mtab.sh
networking
network-manager
nfs-common
ntp
nvidia-kernel
openvpn
pppd-dns
procps
pulseaudio
qemu-kvm
rc
rc.local
rcS
README
reboot
rmnologin
rpcbind
rsync
rsyslog
samba
saned
screen-cleanup
sendsigs
setkey
single
skeleton
ssh
stop-bootlogd
stop-bootlogd-single
sudo
timidity
udev
udev-mtab
umountfs
umountnfs.sh
umountroot
unattended-upgrades
urandom
webcamstudio
x11-common

claudio@Chuck:~$ ls -1 /etc/rc2.d/
README
S01motd
S01nvidia-kernel
S16rpcbind
S17nfs-common
S19acpi-fakekey
S19binfmt-support
S19hostapd
S19rsyslog
S19sudo
S20acpid
S20acpi-support
S20anacron
S20apmd
S20atd
S20bind9
S20dbus
S20loadcpufreq
S20ntp
S20ssh
S21avahi-daemon
S21bluetooth
S21cpufrequtils
S21cron
S21jetty
S21kerneloops
S21network-manager
S21rsync
S22openvpn
S23cups
S23gdm3
S23pulseaudio
S23saned
S24bumblebeed
S24samba
S25minissdpd
S25rc.local
S25rmnologin
S25stop-bootlogd

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

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

Versions of packages bind9 depends on:
ii  adduser3.113+nmu3
ii  bind9utils 1:9.8.1.dfsg.P1-4.1
ii  debconf [debconf-2.0]  1.5.44
ii  libbind9-801:9.8.1.dfsg.P1-4.1
ii  libc6  2.13-34
ii  libcap21:2.22-1.1
ii  libdns81   1:9.8.1.dfsg.P1-4.1
ii  libgssapi-krb5-2   1.10.1+dfsg-1
ii  libisc83   1:9.8.1.dfsg.P1-4.1
ii  libisccc80 1:9.8.1.dfsg.P1-4.1
ii  libisccfg821:9.8.1.dfsg.P1-4.1
ii  liblwres80 1:9.8.1.dfsg.P1-4.1
ii  libssl1.0.01.0.1c-3
ii  lsb-base   4.1+Debian7
ii  net-tools  1.60-24.1
ii  netbase5.0

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind9-doc   
ii  dnsutils1:9.8.1.dfsg.P1-4.1
pn  resolvconf  
pn  ufw 

-- Configuration Files:
/etc/init.d/bind9 changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
OPTIONS=""
RESOLVCONF=no
test -f /etc/default/bind9 && . /etc/default/bind9
test -x /usr/sbin/rndc || exit 0
.. /lib/lsb/init-functions
PIDFILE=/var/run/named/named.pid
check_network() {
if [ -x /usr/bin/uname ] && [ "X$(/usr/bin/uname -o)" = XSolaris ]; then
IFCONFIG_OPTS="-au"
else
IFCONFIG_OPTS=""
fi
if [ -z "$(/sbin/ifconfig $IFCONFIG_OPTS)" ]; then
   #log_action_msg "No networks configured."
   return 1
fi
return 0
}
case "$1" in
start)
log_daemon_msg "Starting domain name service..." "bind9"
modprobe capability >/dev/null 2>&1 || true
# dirs under /var/run can go away on reboots.
mkdir -p /var/run/named
chmod 775 /var/run/named
chown root:bind /var/run/named >/dev/null 2>&1 || true
if [ ! -x /usr/sbin/named ]; then
log_action_msg "named bin

Bug#671887: gnome-shell breaks itself via gir1.2-gconf-2.0

[Claudio Moretti]

Package: gnome-shell
Version: 3.2.2.1-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

   * What led up to the situation?
   gnome-shell was removed with a dist-upgrade because it requires
   gir1.2-glib-2.0 which explicitly breaks gnome-shell
   claudio@Chuck:~$ apt-cache depends gnome-shell
gnome-shell
  [snip..]  
  Depends: gir1.2-glib-2.0
  [snip..]
   claudio@Chuck:~$ apt-cache depends gir1.2-glib-2.0
gir1.2-glib-2.0
  [snip..]
  Breaks: gnome-shell
  [snip..]
   
   Also, gnome-shell complains about not being able to install libcogl5,
   but  this seems to be impossible

root@Chuck:~# apt-get install -s libcogl5 gnome-shell
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnome-shell : Depends: gir1.2-clutter-1.0 but it is not going to be
installed
   Depends: gir1.2-coglpango-1.0 but it is not going to be
installed
   Depends: gir1.2-mutter-3.0 (>= 3.2) but it is not going
to be installed
   Depends: libclutter-1.0-0 (>= 1.7.6) but it is not going
to be installed
   Depends: libcogl-pango0 (>= 1.7.4) but it is not going to
be installed
   Depends: libmutter0 (>= 3.2) but it is not going to be
installed
   Depends: libmutter0 (< 3.3) but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 When I rebooted, my system was in fallback mode and I didn't have
 gnome-shell, so I tried to reinstall gnome-shell by forcing libcogl5 
installation, but it didn't work

   * What was the outcome of this action?
 (see simulation above)

   * What outcome did you expect instead?
 gnome-shell installed and working


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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-1
ii  gconf-service3.2.5-1
ii  gir1.2-accountsservice-1.0   0.6.15-4
ii  gir1.2-atk-1.0   2.4.0-2
ii  gir1.2-caribou-1.0   0.4.2-2
ii  gir1.2-clutter-1.0   1.10.4-3
ii  gir1.2-cogl-1.0  1.10.2-3
ii  gir1.2-coglpango-1.0 1.10.2-3
ii  gir1.2-folks-0.6 0.6.8-2
ii  gir1.2-freedesktop   1.32.1-1
ii  gir1.2-gconf-2.0 3.2.5-1
ii  gir1.2-gdkpixbuf-2.0 2.26.1-1
ii  gir1.2-gee-1.0   0.6.4-1
ii  gir1.2-gkbd-3.0  3.4.0.2-1
ii  gir1.2-glib-2.0  1.32.1-1
ii  gir1.2-gmenu-3.0 3.2.0.1-2
ii  gir1.2-gnomebluetooth-1.03.2.2-1
ii  gir1.2-gtk-3.0   3.4.1-2
ii  gir1.2-json-1.0  0.14.2-1
ii  gir1.2-mutter-3.03.2.2-3
ii  gir1.2-networkmanager-1.00.9.4.0-3
ii  gir1.2-pango-1.0 1.30.0-1
ii  gir1.2-polkit-1.00.105-1
ii  gir1.2-soup-2.4  2.38.1-2
ii  gir1.2-telepathyglib-0.120.18.1-2
ii  gir1.2-telepathylogger-0.2   0.4.0-1
ii  gir1.2-upowerglib-1.00.9.16-2
ii  gjs  1.32.0-2
ii  gnome-bluetooth  3.2.2-1
ii  gnome-icon-theme-symbolic3.4.0-2
ii  gnome-settings-daemon3.2.2-3
ii  gnome-shell-common   3.2.2.1-4
ii  gsettings-desktop-schemas3.4.1-2
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-32
ii  libcairo-gobject21.12.2-1
ii  libcairo21.12.2-1
ii  libcamel-1.2-29  3.2.2-3
ii  libcanberra0 0.28-4
ii  libclutter-1.0-0 1.10.4-3
ii  libcogl-pango0   1.10.2-3
ii  libcogl5 
ii  libcroc

Bug#662757: katepart is missing in sid, breaks kdelibs5-plugins

[Claudio Moretti]

Package: katepart
Severity: normal

Dear Maintainer,

I tried to run Amarok, today, and found out that it was uninstalled.
Long story short, I traced it back to the absence of katepart in the apt
repository; this breaks the support for kdebase-runtime, on my system,
which is the core of KDE.

I'm using GNOME, so that doesn't entirely affect my system, unless I try
to install KDE related packages.

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

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



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

Bug#653719: amarok: Amarok is not recognized as a multimedia player

[Claudio Moretti]

Package: amarok
Version: 2.5.0-1
Severity: normal

   * What led up to the situation?

* What exactly did you do (or not do) that was effective (or
 ineffective)?
 I tried to use multimedia keys to control Amarok and tried to add
 it to the activity launcher via right-click -> add to favorites
   
   * What was the outcome of this action?
 The multimedia keys did not respond: a notification with a
 "forbidden" mark was shown and the state of the media player did
 not change. (see http://img402.imageshack.us/img402/1221/forbiddenr.png)
 Right-clicking the Amarok icon in the launcher, did not show the
 option to keep it as a favorite (see 
http://img406.imageshack.us/img406/854/noopots.png)
   
   * What outcome did you expect instead?
 The songs to change and the ability to add Amarok to the "favorites" list

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

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

Versions of packages amarok depends on:
ii  amarok-common 2.5.0-1
ii  amarok-utils  2.5.0-1
ii  kdebase-runtime   4:4.6.5-1+b1
ii  libavcodec53  4:0.7.3-2
ii  libavformat53 4:0.7.3-2
ii  libc6 2.13-24
ii  libcurl3-gnutls   7.23.1-3
ii  libgcc1   1:4.6.2-9
ii  libgcrypt11   1.5.0-3
ii  libgdk-pixbuf2.0-02.24.0-2
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libglib2.0-0  2.30.2-4
ii  libgpod4  0.8.2-4
ii  libkcmutils4  4:4.6.5-2+b1
ii  libkdecore5   4:4.6.5-2+b1
ii  libkdeui5 4:4.6.5-2+b1
ii  libkdewebkit5 4:4.6.5-2+b1
ii  libkdnssd44:4.6.5-2+b1
ii  libkfile4 4:4.6.5-2+b1
ii  libkio5   4:4.6.5-2+b1
ii  libknewstuff3-4   4:4.6.5-2+b1
ii  liblastfm00.4.0~git20090710-1
ii  libloudmouth1-0   1.4.3-7
ii  libmtp9   1.1.1-1
ii  libmysqlclient16  5.1.58-1
ii  libofa0   0.9.3-4
ii  libphonon44:4.6.0really4.5.1-1
ii  libplasma34:4.6.5-2+b1
ii  libqjson0 0.7.1-6
ii  libqt4-dbus   4:4.7.4-1
ii  libqt4-network4:4.7.4-1
ii  libqt4-opengl 4:4.7.4-1
ii  libqt4-script 4:4.7.4-1
ii  libqt4-sql4:4.7.4-1
ii  libqt4-svg4:4.7.4-1
ii  libqt4-xml4:4.7.4-1
ii  libqtcore44:4.7.4-1
ii  libqtgui4 4:4.7.4-1
ii  libqtscript4-core 0.1.0+git20101026+8b191fbc-2
ii  libqtscript4-gui  0.1.0+git20101026+8b191fbc-2
ii  libqtscript4-network  0.1.0+git20101026+8b191fbc-2
ii  libqtscript4-sql  0.1.0+git20101026+8b191fbc-2
ii  libqtscript4-uitools  0.1.0+git20101026+8b191fbc-2
ii  libqtscript4-xml  0.1.0+git20101026+8b191fbc-2
ii  libqtwebkit4  2.2.0-2
ii  libsolid4 4:4.6.5-2+b1
ii  libstdc++64.6.2-9
ii  libtag-extras11.0.1-3
ii  libtag1c2a1.7-1
ii  libthreadweaver4  4:4.6.5-2+b1
ii  libx11-6  2:1.4.4-4
ii  libxml2   2.7.8.dfsg-5
ii  phonon4:4.6.0really4.5.1-1
ii  zlib1g1:1.2.3.4.dfsg-3

Versions of packages amarok recommends:
ii  kdemultimedia-kio-plugins  4:4.6.5-3

Versions of packages amarok suggests:
pn  libqt4-sql-mysql   4:4.7.4-1
pn  libqt4-sql-psql
pn  libqt4-sql-sqlite  
pn  libxine1-ffmpeg
pn  moodbar

Versions of packages amarok-common depends on:
ii  perl  5.14.2-6

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-gstreamer [phonon-backend]  4:4.6.0really4.5.1-1
ii  phonon-backend-vlc [phonon-backend]0.4.1-1

-- no debconf information



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