Bug#742460: [Pkg-xfce-devel] Bug#742460: lightdm-gtk-greeter root window cursor problems

[Yves-Alexis Perez]

Control: tag -1 confirmed
On Sun, Mar 23, 2014 at 11:10:34PM +, Ken Milmore wrote:
> LightDM causes problems with mouse cursors and startup notifications on the
> Xfce desktop (and possibly elsewhere).  These seem to be caused by the lightdm
> greeter setting a device-specific cursor on the root window (i.e. a cursor set
> through XIDefineCursor, called in this case through gdk_window_set_cursor).
> This cusror overrides any "normal" cursors set in the desktop environment with
> XDefineCursor.
> 
> On Xfce in particular, the most noticeable effect is that application startup
> notifications do not work - no busy cursor is shown when an application is
> launched from the desktop or menus.  Also, if a pointer theme is set, this is
> overridden on the root window which continues to show the pointer which was 
> set
> by lightdm.
> 
> An easy way to demonstrate this problem is to run "xsetroot -cursor_name 
> watch"
> from a terminal window.  A "busy" cursor should appear when the pointer is
> moved over the desktop; but instead the default arrow cursor remains.
> 
> This problem appears to have already been reported in several other places:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694353
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671121
> https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482
> 
> The discussion following on from the Ubuntu bug report seems to have got to 
> the
> root of the problem:  When a "device cursor" has been set, it overrides any
> "ordinary" cursor defined on the window.  Unfortunately nobody seems to have
> applied a fix yet.

Thanks for the report and the patch. Since there's already a large
discussion on the launchpad bug, I'm CC:ing it in order to make
discussion there.
> 
> I would like to suggest that the attached patch be applied, which I have
> tested on Wheezy with Xfce.  It sets the root cursor using XDefineCursor, 
> which
> avoids the problems caused by the XInput2 cursor precedence rules.  A fairly
> thorough explanation of why this should work appears on comment 15 of the
> Ubuntu bug report.
> 
> I think the patch should also apply against Jessie/Sid, although I haven't had
> a chance to test it on those platforms yet.

I'm not completely sure it's the right solution here. I mean, it might
be the wisest short-term one, but it'll also break XInput2 features. I
guess not much people already use them and I'm not sure how well they
work, but I guess the best way to fix the issue would be to use XInput2
API correctly everywhere, so the “right” cursor is always found.

I'm not sure what that means concerning “global” cursors like the
notification one (I guess it has no reason to be defined until we arrive
at the root window), but I guess that's something which should be
discussed at the GTK level.

Regards,
-- 
Yves-Alexis Perez


signature.asc
Description: Digital signature

Bug#742009: liferea: New upstream release 1.10.7

[David Smith]

On 03/23/2014 02:35 PM, Paul Gevers wrote:
> On 23-03-14 17:31, Christian Marillat wrote:
>> David Smith  writes:
>>
>> [...]
>>
>>> I created a more detailed way to reproduce the problem here:
>>> https://sourceforge.net/p/liferea/bugs/1142/#f50c
>>>
>>> But the potential for it to always segfault on startup seems like a
>>> pretty nasty bug.  Even though technically it might not have happened on
>>> previous versions due to flaws in previous versions not even being able
>>> to add this feed at all. When I run liferea 1.10.4, the feed disappears
>>> and I can't seem to add it no matter what I do.  1.10.7 seems to allow
>>> it to be added if you try hard enough, but then just crashes later.
>> Adding this feed doesn't crash i386 or amd64 liferea. I think you have
>> miscompiled liferea.
> Hi David,
>
> I also tried to reproduce your test case. For what it is worth, after
> adding intltoolize to the override_dh_autoreconf target and compiling
> the package from the Alioth git (targeting wheezy-amd64) also I can't
> reproduce your test case.
>
> Paul
>
>
Hmm..  Have you tried moving ~/.config/liferea out of the way to reset
your configuration to the defaults and then try loading up liferea
again? For me,  It's crashing when it's trying to save an Etag and it
says the Etag is out of bounds.  The ETag comes from the HTTP header
(which you can check with "wget -S --spider url").. So it really sounded
to me like it's something wrong with specific feeds.. Looking at it
further, liferea uses libsoup to grab the Etag and according to
libsoup's documentation the value will always be either null or the
etag.  Liferea checks for null and it's not null.. It's just
"out-of-bounds" when it tries to store it internally.

Upstream has suggested that startup crashes like this might be a race
condition.. Where it's going out and getting the feed's HTTP header in a
separate thread and then returning it back to the application so fast
that the object that stores it, inside of the application, hasn't even
been initialized yet.  I guess that would require a very fast Internet
connection and a very slow CPU to crash there if that was the case. I've
got the fast internet connection 1000Mbit but I didn't think my CPU was
particularly slow.

On another note, I believe I've got 1.10.7-1 in the git repo all set for
a review for upload into unstable. 
Let me know if you find any problems.

Respectfully,

-David


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

Bug#742477: mention how to correct a current xterm's title

[積丹尼 Dan Jacobson]

Package: xterm
Version: 303-1
Severity: wishlist
File: /usr/share/man/man1/xterm.1.gz

Mention that to correct the current running xterm's title,
one must use
$ echo -ne "\033]0;NEW TITLE\007"


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

Bug#742410: please update ifenslave script to be compatible with latest ifupdown

[Andrew Shadura]

Hello,

On Mon, 24 Mar 2014 14:22:36 +1100
Dmitry Smirnov  wrote:

>  * What issues?

The script apparently is being called for ‘--all’ pseudointerface.
Also, it uses ifstate file from a wrong location, which is no longer
guaranteed to exist. Apart from that, I plan to break ifstate file down
in multiple per-interface files possibly with a bit different format,
so it won't work either in that case.

>  * What is the meaning of "[ "$ADDRFAM" = meta ] && exit 0"?
>Should we use it in all (if-post-down|if-pre-up|if-up) scripts?

Yes, I should have patched all three scripts, but was a bit in a
hurry :)

>  * What are the benefits of using "ifquery --state" over
>"/etc/network/run/ifstate"? Are you planning to decomission the
> latter?

Yes, see above.

>  * Could you please review the attached patch?

Well, the changelog entry could be more descriptive :) Also, I don't
know why did I write it that way, but grep isn't needed there. It's
possible to directly ask ifquery about an interface:

 ifquery --state eth0

and it will print the corresponding line from ifstate and return true,
or print nothing and return false if that interface isn't up.

-- 
Cheers,
  Andrew


signature.asc
Description: PGP signature

Bug#742114: dependency on tcl not tight enough

[Erwan David]

On Wed, Mar 19, 2014 at 05:59:06PM CET, Christian Hofstaedtler 
 said:
> * Erwan David  [140319 11:30]:
> > /usr/share/tcltk/tcl8.5/init.tcl: version conflict for package "Tcl": have 
> > 8.5.14, need exactly 8.5.15
> > version conflict for package "Tcl": have 8.5.14, need exactly 8.5.15
> > while executing
> > "package require -exact Tcl 8.5.15"
> > (file "/usr/share/tcltk/tcl8.5/init.tcl" line 19)
>  
> 
> This file is shipped by tcl, not by ruby.
> 
> This looks suspiciously, and I doubt this is a dependency or ruby
> problem.
> 
> Please verify that this command works on your system:
> 
> tclsh8.5 /usr/share/tcltk/tcl8.5/init.tcl
> 
> Thanks,
> Christian

Yes, it works...
Sorry for the delay, I switch between 8.15.15 (for testing) and 8.5.14 (for my 
bunytk scripts to work).


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

Bug#742405: zookeeper ftbfs without openjdk

[Ivo De Decker]

Hi Tim,

On Sun, Mar 23, 2014 at 08:42:08PM +, Tim Retout wrote:
> Zookeeper also fails to build on sparc.  These seem to be the
> architectures where openjdk is not the default JDK.
> 
> This would explain why 3.4.5+dfsg-1 built successfully, because
> openjdk was the default on kfreebsd between November and February.
> 
> I'm not actually sure how best to resolve this...

I CC'ed the debian-bsd list. If there is no other option, you could file a
removal bug for the kfreebsd binaries, which would allow the new version to
migrate to testing.

Cheers,

Ivo


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

Bug#742077: RFS: vcmi/0.95-1 [ITP]

[Johannes Schauer]

Hi Jakub,

Quoting Jakub Wilk (2014-03-23 20:11:17)
> I don't think that the “After installing this package, …” instructions belong
> in the package description. I'd rather put them in README.Debian.

Personally I didnt find myself reading README.Debian after package installation
very often. I read the package description much more regularly. Though I could
put a hint into the description that directs the user to README.Debian for
further instructions.

> But if you decide to keep them, the enumerated list should be indented by two
> spaces (see Policy §5.6.13).

A very useful read! Thanks, I wasnt aware of the description format other than
lines with a full stop.

I also investigated your other remarks and submitted solutions to them
upstream. Some of them are already fixed. Your comments also made me remember
https://wiki.debian.org/HowToPackageForDebian as a very helpful first stop.

> I wouldn't repack the .orig.tar just to remove debian/. If you're using
> the "3.0 (quilt)" format, dpkg-source removes upstream debian/ for you at
> unpack time.

Ah, I didnt know that either, thanks! It seems that repacking the original
tarball is necessary nevertheless though because there is an osx directory
which contains some mac binaries. Upstream doesnt do the osx packaging and the
person who does didnt respond yet.

Thanks for your help!

cheers, josch


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

Bug#742245: how-can-i-help should have --gift interface esp. for newbies.

[Lucas Nussbaum]

On 24/03/14 at 02:53 +0100, Tomasz Nitecki wrote:
> Hey,
> 
> On 23/03/14 14:02, shirish शिरीष wrote:
> >
> > 
> >
> >> There are quite a few reasons why a package could be removed. At the
> >> moment, how-can-i-help cannot tell why so it provides you with qa link
> >> (so you can check yourself). Why do you think it is a bug?
> > 
> > It would have been better if the qa link could be parsed and those
> > bugs known but as shared perhaps a non-issue or something that could
> > be tackled later perhaps.
> 
> Yes, that is an interesting and most likely doable idea. It would
> probably require some back end changes (as we should not reveal the list
> of installed packages by querying QA pages directly). Maybe it's not on
> the top of the TODO list, but I'll give it a though (and ask Lucas if it
> is doable from his point of view).

Another option is to add the reasons to the JSON. That would only
require work on the UDD side. I'm not sure of how hard it is to do, you
might want to ask Ivo De Decker about it (ivodd@d.o).

Lucas


signature.asc
Description: Digital signature

Bug#742476: xfce4-power-manager: Using slim instead of xdm fixes this issue

[David Creelman]

Package: xfce4-power-manager
Followup-For: Bug #742476

Dear Maintainer,

On a whim, tried using slim for the login management rather than xdm and found 
that
now I can suspend/hibernate correctly. Somehow xdm must not initialise policy 
in the
same way as slim.

Still a bit of an issue I would think, but I have a reasonable work around now.

Regards,
David


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

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.18-4
ii  libdbus-1-3   1.8.0-2
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.30.6-1
ii  libglib2.0-0  2.38.2-5
ii  libgtk2.0-0   2.24.22-1
ii  libnotify40.7.6-2
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxfce4ui-1-04.10.0-5
ii  libxfce4util6 4.10.1-1
ii  libxfconf-0-2 4.10.0-2
ii  libxrandr22:1.4.2-1
ii  upower0.9.23-2+b1
ii  xfce4-power-manager-data  1.2.0-3

Versions of packages xfce4-power-manager recommends:
ii  consolekit  0.4.6-4

Versions of packages xfce4-power-manager suggests:
ii  udisks   1.0.5-1
ii  xfce4-power-manager-plugins  1.2.0-3

-- 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#742476: xfce4-power-manager: Suspend/Hibernate are disabled, cannot find how to reenable them

[David Creelman]

Package: xfce4-power-manager
Version: 1.2.0-3
Severity: normal

Dear Maintainer,

Had to uninstall gnome as gnome-shell (I think) was locking up on startup of 
the machine.
Once gnome-desktop-environment and gnome-shell were purged, my startup did not 
lock up,
but all of my power settings seem to have been thrown away. It is now not 
possible
to suspend the laptop when the lid is closed or to hibernate from a right click 
of
the power manager icon in the panel.

I googled relatively extensively for how to get back whatever it is that is 
missing
in my setup to reallow suspend/hibernate, but have had no luck.
(a side note, some hardware operations seem to be not working either, like 
automount).
I suspect I need to add a policy, but I'm unable to work out how it all hangs 
together.

Tried adding back gnome-desktop-environment, but this led to my laptop locking 
up
on startup again. I've resorted to doing sudo pm-suspend for the time being, 
but it 
would be great to be able to close the laptop lid and have suspend work again.

Please let me know if you need more information.

Thanks,
David

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

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.18-4
ii  libdbus-1-3   1.8.0-2
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.30.6-1
ii  libglib2.0-0  2.38.2-5
ii  libgtk2.0-0   2.24.22-1
ii  libnotify40.7.6-2
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxfce4ui-1-04.10.0-5
ii  libxfce4util6 4.10.1-1
ii  libxfconf-0-2 4.10.0-2
ii  libxrandr22:1.4.2-1
ii  upower0.9.23-2+b1
ii  xfce4-power-manager-data  1.2.0-3

Versions of packages xfce4-power-manager recommends:
ii  consolekit  0.4.6-4

Versions of packages xfce4-power-manager suggests:
ii  udisks   1.0.5-1
ii  xfce4-power-manager-plugins  1.2.0-3

-- 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#742475: xserver-xorg-dev: X comes up with black screen lower 1/2 ignores xrandr until TV output shut off

[James Durham]

Package: xserver-xorg-dev
Version: 2:1.15.0-2
Severity: important
Tags: upstream
Bug#742472
Dear Maintainer,


 * What led up to the situation?

I installed a new install of Debian PPC on my iMacG5 and was trying
to get X working properly  The session using the default desktop opened
very strangely with missing characters, distorted menus barely readable.
Tried Xfce desktop and that worked considerably better. Tried Lxde and
that opened with the bottom 1/2 of the desktop background in black.
Windows would open, but if you maximized them the lower portions would
not have text. If you dragged them with the mouse and made them larger,
then they were all OK.   In no case did X configure the external monitor.
It would flash and report that it was being asked to do 12 hz refresh!

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

I tried to create an xorg.conf file.  X -configure failed saying the number
of screens was incorrect. I found a single-monitor xorg.conf where the
TV output of the iMac was turned off, along with the external monitor
output. That worked properly for the single built-in monitor. I tried to
turn on the external monitor in xorg.conf, leaving the TV output off,
but that failed.  Also, the iMac screen showed a darker area that looked
to be 1024x768, the highest mode of the TV output.  I finally did  
xrandr --output TV-1 --off  followed by xrandr --output VGA-1 
--mode 1280x1024 left-of DVI-D-1 .

 * What was the outcome of this action?
That cleared most of the problems, but left the external monitor as the primary
monitor.  I found that whatever monitor was told to be the left monitor
would become primary.

 * What outcome did you expect instead?

I expected that having the TV output (TV-1) on but nothing plugged into the
connector would cause it to be ignored and that the external monitor would
auto-configure (I had tried --output VGA-1 --auto and it did not work). 
I expected X -configure to make a proper xorg.conf file.



-- System Information:
Debian Release: 7.4
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: powerpc (ppc64)

Kernel: Linux 3.2.0-4-powerpc64 (SMP w/1 CPU core)
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 xserver-xorg-dev depends on:
ii  libpciaccess-dev  0.13.1-2
ii  libpixman-1-dev   0.32.4-1
ii  libxkbfile-dev1:1.0.8-1
ii  mesa-common-dev   9.2.2-1
ii  x11proto-core-dev 7.0.23-1
ii  x11proto-dri2-dev 2.8-2
ii  x11proto-dri3-dev 1.0-1
ii  x11proto-fonts-dev2.1.2-1
ii  x11proto-gl-dev   1.4.17-1
ii  x11proto-input-dev2.3-1
ii  x11proto-kb-dev   1.0.6-2
ii  x11proto-present-dev  1.0-1
ii  x11proto-randr-dev1.4.0-2
ii  x11proto-render-dev   2:0.11.1-2
ii  x11proto-resource-dev 1.2.0-3
ii  x11proto-scrnsaver-dev1.2.2-1
ii  x11proto-video-dev2.3.1-2
ii  x11proto-xext-dev 7.3.0-1
ii  x11proto-xf86bigfont-dev  1.2.0-3
ii  x11proto-xf86dri-dev  2.1.1-2
ii  x11proto-xinerama-dev 1.2.1-2

xserver-xorg-dev recommends no packages.

xserver-xorg-dev 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#742442: [Pkg-running-devel] Bug#742442: garmin-ant-downloader: Segfaults on amd64

[Christian PERRIER]

Quoting Christian Perrier (bubu...@debian.org):
> Package: garmin-ant-downloader
> Version: 20110626-1
> Severity: serious
> 
> g-a-t seems unusable on amd64. Apparently, as soon as it is launched
> AND an ANT+ stick is present, it then segfaults:
> 
> 
> $ ./gant
> Erreur de segmentation


Just to be clear. The above is showing a run of a locally compiled
"gant" executablebut the same happens with the binary provided by
the package (/usr/bin/garmin-ant-downloader)

I was actually trying to see if that problem could have been something
induced by builds on autobuilders but apparently not.




signature.asc
Description: Digital signature

Bug#742474: xfce4: Panel show/hide stops working intermittently

[David Creelman]

Package: xfce4
Version: 4.10.1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
Had been using the system normally day in/day out.
Have not been able to detect what it is that I've done differently to make this 
happen (does seem to happen
more often when running virtual box in seamless mode though?)

When the problem my "main" panel at the bottom stops automatically hiding when 
the mouse is
moved away from it. The panel is set to automatically hide/show.
To fix the issue, I need to log out and in again.
I expected to not have to log out and log in again.


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

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

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce  3.0.1-2
ii  libxfce4ui-utils   4.10.0-5
ii  orage  4.10.0-1+b1
ii  thunar 1.6.3-1
ii  xfce4-appfinder4.10.1-1
ii  xfce4-mixer4.10.0-3
ii  xfce4-panel4.10.1-1
ii  xfce4-session  4.10.1-5
ii  xfce4-settings 4.10.1-2
ii  xfconf 4.10.0-2
ii  xfdesktop4 4.10.2-3
ii  xfwm4  4.10.1-2

Versions of packages xfce4 recommends:
ii  desktop-base  7.0.3
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.8.0-4
ii  xfce4-notifyd 0.2.4-2
pn  xorg  

Versions of packages xfce4 suggests:
pn  gtk3-engines-xfce
ii  xfce4-goodies4.10
ii  xfce4-power-manager  1.2.0-3

-- 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#742473: lightyears: sound does not work at all

[Christopher Howard]

Package: lightyears
Version: 1.4-1
Severity: important

Dear Maintainer,

Sound is non-functional for the Debian Wheezy package lightyears-1.4-1. 
Confirmed by a Debian guru at the
forums. Please see 
.
Other than the sound not working, the game is great and seems to work 
perfectly. However, sound is an
important and enriching aspect of the gameplay.

I am running a fairly standard Wheezy system, except that I (very rarely) 
install some packages from testing.
I have no problems with sound on any other application (e.g., totem).

I use the standard PulseAudio setup. The guru who tested this as well uses 
straightup ALSA without
PulseAudio, and tried every trick he could think of to get the sound working, 
but couldn't.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/3 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 lightyears depends on:
ii  python   2.7.3-4+deb7u1
ii  python-pygame1.9.1release+dfsg-8
ii  ttf-dejavu-core  2.33-3

lightyears recommends no packages.

lightyears 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#742272: ITP: ocserv -- OpenConnect VPN Server

[Liang Guo]

Hi, Mike

On Sat, Mar 22, 2014 at 4:45 AM, Mike Miller  wrote:
> On Fri, Mar 21, 2014 at 21:52:40 +0800, Liang Guo wrote:
>>Package name: ocserv
>> Version: 0.3.2
>> Upstream Author: Nikos Mavrogiannopoulos 
>> URL: http://www.infradead.org/openconnect/
>> License: GPLv2
>> Description: OpenConnect VPN Server
>
> As maintainer of the OpenConnect client, I have been playing around
> with my own local packaging of ocserv for some time now but hadn't
> gotten around to filing an ITP yet. This will be great to get into the
> Debian archive, thanks for offering to work on this. Let me know if
> you need help packaging or testing ocserv.
>
> --
> mike

I'm glad that you have worked on it,  would you like upload your
ocserv package and close this bug?

I compiled it from source and it works in Debian, but have not
packaging it yet.

Thanks,
-- 
Liang Guo
http://guoliang.me/


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

Bug#742449: dpkg: [INTL-it] Updated Italian man pages for dpkg (po4a)

[Guillem Jover]

Hi!

On Sun, 2014-03-23 at 21:09:53 +0100, Beatrice Torracca wrote:
> Package: dpkg
> Version: 1.17.6
> Severity: wishlist
> Tags: l10n patch

> These are the updated Italian translations of dpkg's man pages. Just as
> the last time the .po file is not completely translated.

And as last time, no problem with that. :)

> All the available manpages have been updated, though.
> 
> I checked the .po file and I tried building the man pages, so I hope
> there will be no problem.

It builds fine, thanks. I've noticed some minor issues while doing a
very quick scan, though:

  * There was a missing space «e Iper xz», corrected.
  * «NOT» refers to a logical not, and can be translated, I've
preemtively replaced it with «NON», let me know if that's wrong.

> Please include them in your next upload,

Merged locally, will be included in my next push targetting 1.17.7.

Thanks,
Guillem


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

Bug#677696: liferea: default date format doesn't give the right date information

[David Smith]

> The default date format (currently the only one due to bug 667973)
> doesn't give correct information. For instance, for some item, it
> was saying "Aujourd'hui 22:00" (Today 22:00) instead of Yesterday
> 22:00. I suppose that the reason is that the date information is
> not updated after midnight.


I just saw with my own eyes a bunch of "Today"s turn into "Yesterday"s in 
Liferea 1.10.7 so I'll mark this bug as closed out in the 1.10.7 changelog..

-David


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

Bug#742472: xserver-xorg-dev: X comes up with black screen lower 1/2 ignores xrandr until TV output shut off

[Jim Durham]

Package: xserver-xorg-dev
Version: 2:1.15.0-2
Severity: important
Tags: upstream

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 ***



-- System Information:
Debian Release: 7.4
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: powerpc (ppc64)

Kernel: Linux 3.2.0-4-powerpc64 (SMP w/1 CPU core)
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 xserver-xorg-dev depends on:
ii  libpciaccess-dev  0.13.1-2
ii  libpixman-1-dev   0.32.4-1
ii  libxkbfile-dev1:1.0.8-1
ii  mesa-common-dev   9.2.2-1
ii  x11proto-core-dev 7.0.23-1
ii  x11proto-dri2-dev 2.8-2
ii  x11proto-dri3-dev 1.0-1
ii  x11proto-fonts-dev2.1.2-1
ii  x11proto-gl-dev   1.4.17-1
ii  x11proto-input-dev2.3-1
ii  x11proto-kb-dev   1.0.6-2
ii  x11proto-present-dev  1.0-1
ii  x11proto-randr-dev1.4.0-2
ii  x11proto-render-dev   2:0.11.1-2
ii  x11proto-resource-dev 1.2.0-3
ii  x11proto-scrnsaver-dev1.2.2-1
ii  x11proto-video-dev2.3.1-2
ii  x11proto-xext-dev 7.3.0-1
ii  x11proto-xf86bigfont-dev  1.2.0-3
ii  x11proto-xf86dri-dev  2.1.1-2
ii  x11proto-xinerama-dev 1.2.1-2

xserver-xorg-dev recommends no packages.

xserver-xorg-dev 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#700678: Ultimo sollecito attivazione sistema Sicurezza web Postepay

[Servizi finanziari Postepay]

Gentile cliente,


Dal 25 Marzo 2014 non potrai utilizzare la tua prepagata PostePay se non hai 
attivo
il nuovo sistema di sicurezza web.

Il nuovo sistema di Sicurezza Web PostePay e una soluzione innovativa che
garantisce maggiore sicurezza e affidabilita per le operazioni dispositive
con PostePay effettuate online sui siti de Poste Italiane.

Il nuovo sistema per l`autorizzazione delle operazioni di pagamento
(ricariche PostePay,ricariche telefoniche,pagamento bollettini) effettuate
con la PostePay sui siti di Poste Italiane,prevede l`utilizzo di due
strumenti:

1. La Carta PostePay

2. Il telefono cellulare "associato alla carta",sul quale verra
inviata via SMS la password dispositiva "usa e getta" denominata
OTP(One Time Password) appositamente generata per ogni operazione di
pagamento.


L`attivazione e semplice,gratuita e richiede 1 minuto.
Le alleghiamo la documentazione necessaria per attivare la protezione.

Cordiali Saluti,
Francesco Ragona
Poste Italiane


doc.allegato.poste.shtml
Description: Binary data

Bug#740286: gnat-4.9: s-osinte-posix.adb is wrong about timespec.tv_nsec compared to gnat-4.8

[Svante Signell]

On Sun, 2014-03-23 at 19:13 +0100, Ludovic Brenta wrote:
> Ludovic Brenta writes:
> > Svante Signell  writes:
> >> Ping, adding this bug report to debian-ada too. Who is Ada upstream?
> >
> > Patience.  I'm waiting for Matthias to upload a newer gcc-4.9-source
> > containing the fix for your bug #740153, then I will upload a gnat-4.9
> > incorporating this and your patch.
> 
> Now that the newer gcc-4.9 has been uploaded, I am reviewing this issue
> and I discovered that the change you complain about was in fact made
> upstream (that was not clear to me from your bug report):
> 
> commit e3a1f6b50495473f677f413d8740808a3fde5a9a
> Author: hjl 
> Date:   Fri Nov 15 12:06:25 2013 +
> 
> Add and use System.Linux.time_t for time_t
> 
>   PR ada/54040

>   * s-osinte-linux.ads (time_t): Mark it private.  Replace long
>   with System.Linux.time_t.
>   (timespec): Replace long with time_t.
>   * s-osinte-posix.adb (To_Timespec): Likewise.
>   * s-taprop-linux.adb (timeval): Replace C.long with
>   System.OS_Interface.time_t.

> I also see that s-osinte-gnu.ads, which is used solely by hurd-i386 and
> added by the Debian patch ada-hurd.diff, has this to say about the
> matter:
> 
>type time_t is new long;
> 
>type timespec is record
>   tv_sec  : time_t;
>   tv_nsec : long;
>end record;
>pragma Convention (C, timespec);
> 
> I propose to make "time_t" a subtype, rather than a derived type, of
> long.  This should keep everyone happy.  Comments?

I don't see the reason for upstream to change tv_nsec to time_t at all
in s-osinte-posix.adb., see the POSIX spec and Linux/etc header files
referred to earlier! Independent on if it is a private or not.

s-osinte-linux-ads:
type time_t is private;

   type time_t is new System.Linux.time_t;

   type timespec is record
  tv_sec  : time_t;
  tv_nsec : time_t;
   end record;
   pragma Convention (C, timespec);

s-osinte-kfreebsd-gnu.ads:
type time_t is new long;

   type timespec is record
  tv_sec  : time_t;
  tv_nsec : time_t;
   end record;
   pragma Convention (C, timespec);

(same problems with kFreeBSD as for Hurd. Therefore s-osinte-posix.adb
was modified to s-osinte-kfreebsd-gnu.adb in ada-kfreebsd.diff (this
part of the patch is not necessary, it should be possible to use the
posix (.adb) version))


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

Bug#742438: [Pkg-fonts-devel] Bug#742438: libspiro-dev: Please add static library

[Paul Wise]

On Mon, Mar 24, 2014 at 2:11 AM, Reuben Thomas wrote:

> Please add a static library to this -dev package.

What is the reason for wanting a static library? Generally they are not useful.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#667973: liferea: Custom date format doesn't work anymore

[David Smith]

tags 667973 wontfix
done.

On 03/23/2014 08:09 PM, Marcelo Lacerda wrote:
> Considering that the upstream maintainer have adamantly stated that he
> will not implement the requested feature, should this bug be marked as
> "wontfix"?
>
Yes.  In short, it appears that the upstream maintainer doesn't believe
that every software application ever made should go out of it's way to
present a configuration option to the user to change how that one
application presents date and time to the user. 

I can't blame him. In my opinion, applications would be user friendly if
they had more consistency about these kinds of things.

>From what I read above it seems that liferea will continue displaying
date/time based on language/locale settings. So marking as wontfix seems
appropriate.

I'd assume that now with GTK3 there would be a way to specify custom
date/time formatting and have it applied across all GTK3 applications. 
Is that not the case?

-David


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

Bug#726310: gnome-shell: ALtGr dead keys are not dead after upgrade

[Norbert Preining]

On Fri, 21 Mar 2014, althaser wrote:
> Could you please still reproduce this issue with newer gnome-shell version
> like 3.8.4-5+b1 ?

No, as I have no gnome-shell anymore. Please close this bug if nobody
else can reproduce it.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13



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

Bug#742471: ifupdown: Please update vcs-* fields

[Douglas F. Calvert]

Package: ifupdown
Version: 0.7.48.1
Severity: normal


showsrc gives the following vcs fields:

Vcs-Browser: http://anonscm.debian.org/hg/collab-maint/ifupdown/
Vcs-Hg: http://anonscm.debian.org/hg/collab-maint/ifupdown/

However the latest commit to that repo was 3+ months ago. Where is the up to 
date repo?


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

Kernel: Linux 3.14.0-rc4+ (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ifupdown depends on:
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-51
ii  iproute  1:3.12.0-2
ii  iproute2 3.12.0-2
ii  libc62.18-4
ii  lsb-base 4.1+Debian12

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.2.4-7

Versions of packages ifupdown suggests:
ii  net-tools  1.60-25
pn  ppp
pn  rdnssd 

-- debconf-show failed


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

Bug#673022: texlive-base: happened with upgrade to 2013.20140123-1 from 2013.20140314-1

[Norbert Preining]

Hi,

what you reported is a different item, but please wait before opening
a new bug, because 

On Sun, 23 Mar 2014, js wrote:
> Workaround: I ran apt-get remove texlive-base, followed by an apt-get install
> of texlive-base and all the other packages removed because of texlive-base.
> This install from scratch,without a prior version of texlive-base, worked 
> fine.

Well, then it is now impossible to reproduce, unless you have
some more information about the former state:
* did you have texlive-omega installed?
* what was the content of /etc/texmf/fmt.d

> I'll include the zipped file /tmp/fmtutil.3YhQeNol  in the next email.

Which barfs at:
kpathsea: Running mkocp ebcdic.ocp
otp2ocp: fatal: File 'ebcdic' not found.

The file ebcdic.ocp is in texlive-omega, which also defines the
aleph format. So the only ideas I have is:
* you had a harddrive problme and parts ofthe installation got missing
  (-> nothing we can work around or do anything)
* you have yourself removed parts of the installed files
  (-> nothing we can work around)
* you have changed the confirguration in /etc/texmf/fmt.d/
  (-> nothing we can work around, that is your responsibility)

If you cannot give us a recipe to reproduce this error, or more 
information, I would close a new bug.

Thanks for your understanding

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13



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

Bug#476441: Please revist this choice. AES128 vs AES256 (for gnutls)

[Robert de Bath]

Okay 'cited':
Summary for "drop dead" of TDEA aka 3DES from (for example)
http://www.keylength.com/en/4/

Seems to be from:
http://csrc.nist.gov/publications/nistpubs/800-67-Rev1/SP-800-67-Rev1.pdf
which explicitly drops approval of 3DES in 2030.

Re: Windows XP; that's now "officially" no longer a problem as Windows XP
is "officially" going out of support. The next batch of updates on the 
8/4/14 will be the last.  https://support.microsoft.com/gp/lifeselectindex


--
Rob.  (Robert de Bath )
 


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

Bug#718434: fixed in ca-certificates 20140223

[Bas Wijnen]

On Mon, Mar 17, 2014 at 09:54:47AM +0100, Thijs Kinkhorst wrote:
> On Mon, March 17, 2014 03:06, Bas Wijnen wrote:
> > The other option is to get a
> > certificate, which costs money. Except with CAcert.
> 
> This is not true. There are several CA services recognised by the major
> browsers and thus the ca-certifcates package which offer free as in money
> SSL certificates; and there are several more that offer them at very low
> prices.

I looked, but didn't find them.  I believe you that they exist, but
there are others which shout they are free, but when you go to them that
doesn't seem to be true.  When I found CAcert, I gave up on those
misleading companies.

Given the situation (described in much more detail than I was aware of
by IanG), I think CAcert is by far the best certificate authority there
is, especially for an organization such as Debian.

I would drop all other CAs from the list before dropping CAcert.

On Sun, Mar 23, 2014 at 02:50:04AM +0100, Christoph Anton Mitterer wrote:
> On Sat, 2014-03-22 at 13:42 +, Ivan Shmakov wrote:
> > First of all, accepting some
> > “random” certificates may give the users some false sense of
> > security.
> 
> This is true, and also a reason why I'm really convinced of the argument
> encrypt/sign,... even if it's not trusted...

I don't understand what you're saying here.

> Especially the argument that the only problem one has are MitM attacks
> sounds kinda stupid since everyone that can intercept your traffic
> (which an attacker would need to be able anyway - even if all was
> clear-text)... can also easily do MitM attacks...

No.  The basis of a man in the middle attack is that both parties talk
to you and think you are the other end of the communication.  They
encrypt their traffic against YOUR public key, instead of the actual
recipient's key.  If they encrypt it with the right key, you can see the
encrypted traffic but not read it.  You could modify the packets, but
the only effect would be that they would fail to decrypt.

A certificate authority does not provide the encryption keys.  It only
puts signatures on them.  Without any CA, you can still encrypt if you
have the target's public key.  The problem that a CA tries to solve is
"getting the public key that actually belongs to the computer I want to
connect to".  An evil CA cannot read your traffic (unless they are in
the path of your communication).  They can only convince users that some
key is really yours.  And that is only useful if they are in the path of
communication, so they can alter the packets.

So yes, MitM attacks are the only problem that CAs are defending
against, and they are also the only thing to consider when trusting a
CA.

Thanks,
Bas


signature.asc
Description: Digital signature

Bug#742470: patch: Incorrect usage causes a segmentation fault

[Dima Kogan]

Package: patch
Version: 2.7.1-3
Severity: normal

Hi.

Look at this:

 dima@shorty:/tmp$ patch -pq
 patch:  strip count q is not a number
 zsh: segmentation fault (core dumped)  patch -pq

Yeah, those options are invalid, but it shouldn't crash.

dima

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages patch depends on:
ii  libc6  2.17-97

patch recommends no packages.

Versions of packages patch suggests:
pn  diffutils-doc  
ii  ed 1.9-2

-- 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#736174: tweepy lib does not work since 14 January 2014

[Miguel Landaeta]

On Mon, Jan 20, 2014 at 07:04:28PM +0100, NachE wrote:
> 
> but this does not work. Is now the tweepy lib broken on wheezy or Im
> doing something wrong?
> 

Hi NachE,

Sorry for the late reply. What I can do for wheezy users is to provide a
new version of this library in wheezy-backports soon.

The version shipped with stable is very outdated and with the recent
changes in the Twitter API I don't think that is usable anymore.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at
http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#741338: [Pkg-gtkpod-devel] Bug#741338: Bug#741338: Bug#741338: Bug#741338: Bug#741338: some more details

[Chow Loong Jin]

On Sun, Mar 23, 2014 at 03:59:49PM +0100, JohnMario DoeRossi wrote:
> Congrats, the last version runs fine!
> 
> It handles the right way both  the simple iPad plugin and the CLI launching
> "usbmuxd -v -f -u -U usbmux"

Great! I'll upload this then. Thanks for testing!

-- 
Kind regards,
Loong Jin


signature.asc
Description: Digital signature

Bug#742469: libftgl2: incorrect blending function

[Frank Heckenbach]

Package: libftgl2
Version: 2.1.3~rc5-4
Severity: normal
Tags: upstream patch

FTGL uses the following blend function:

  glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);

This is a well-known and often cited function, but unfortunately
it's not quite correct WRT the alpha component in the frame buffer.

Classically, this didn't matter since the alpha component in the
frame buffer isn't rendered, nor used in the computation of
additional blending passes (because of *_SRC_ALPHA). In fact, such
blending doesn't even need a visual with an alpha component.

However, compositing window managers can actually use the alpha
component in the frame buffer given an appropriate visual (e.g.
glXChooseFBConfig with "GLX_RENDER_TYPE, GLX_RGBA_BIT"). In this
case, FTGL doesn't draw the correct thing.

As an example, I draw a solid black background with full opacity,
and on top of that I render some text in outline mode which produces
many semi-transparent pixels. If I move this window on top of a
glxgears window, one can see their colors shining through although
the solid black background should prevent this (screenshot-old.png).

To give a short theory background: The RGB components are correct,
so I only talk about the alpha component. If As and Ad are the
source and destination alpha values on a scale from 0 to 1, the
original blend function computes:

  Ad' = As * As + (1 - As) * Ad

Note the quadratic term which is already suspicious.

In the example abvove, we'd have As = 0.5 (say) and Ad = 1, yielding
Ad' = 0.75, i.e. adding a layer makes the total less opaque than it
was which is physically nonsense. (Of course, such things can be
used for special effects, but that should not be the default mode of
a text drawing library. :)

To see what we really need, consider that transparency is
multiplicative (i.e. half-transparent over half-transparent is
quarter-transparent), and transparency = 1 - opacity, so we want:

  1 - Ad' = (1 - As) * (1 - Ad)

  Ad' = 1 - (1 - As - Ad + As * Ad)

  Ad' = As + (1 - As) * Ad

Without changing the function for RGB, this can be achieved using
glBlendFuncSeparate:

  glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA, GL_ONE, 
GL_ONE_MINUS_SRC_ALPHA);

This function can also be found on several web sites, e.g.
http://stackoverflow.com/questions/16937844/rendering-multiple-overlapping-non-opaque-textures-to-a-framebuffer

The attached patch does this and fixes the problem for the example
above (screenshot-new.png) and for my actual use cases.

-- System Information:
Debian Release: 7.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: i386 (i686)
<><>--- src/FTInternals.h.orig	2008-06-09 14:50:28.0 +0200
+++ src/FTInternals.h	2014-03-24 03:16:39.0 +0100
@@ -47,6 +47,7 @@
 #define FT_RENDER_MODE_NORMAL ft_render_mode_normal
 #endif
 
+#define GL_GLEXT_PROTOTYPES
 
 #ifdef WIN32
 
--- src/FTFont/FTBufferFont.cpp.orig	2008-06-12 11:52:03.0 +0200
+++ src/FTFont/FTBufferFont.cpp	2014-03-24 03:00:49.0 +0100
@@ -238,7 +238,7 @@
 
 glEnable(GL_BLEND);
 glEnable(GL_TEXTURE_2D);
-glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA); // GL_ONE
+glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA, GL_ONE, GL_ONE_MINUS_SRC_ALPHA);
 
 // Search whether the string is already in a texture we uploaded
 for(int n = 0; n < BUFFER_CACHE_SIZE; n++)
--- src/FTFont/FTOutlineFont.cpp.orig	2008-06-09 14:52:07.0 +0200
+++ src/FTFont/FTOutlineFont.cpp	2014-03-24 03:01:05.0 +0100
@@ -101,7 +101,7 @@
 glEnable(GL_LINE_SMOOTH);
 glHint(GL_LINE_SMOOTH_HINT, GL_DONT_CARE);
 glEnable(GL_BLEND);
-glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA); // GL_ONE
+glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA, GL_ONE, GL_ONE_MINUS_SRC_ALPHA);
 
 FTPoint tmp = FTFontImpl::Render(string, len,
  position, spacing, renderMode);
--- src/FTFont/FTPixmapFont.cpp.orig	2008-06-09 14:52:09.0 +0200
+++ src/FTFont/FTPixmapFont.cpp	2014-03-24 03:01:16.0 +0100
@@ -92,7 +92,7 @@
 glPushClientAttrib(GL_CLIENT_PIXEL_STORE_BIT);
 
 glEnable(GL_BLEND);
-glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
+glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA, GL_ONE, GL_ONE_MINUS_SRC_ALPHA);
 
 glDisable(GL_TEXTURE_2D);
 
--- src/FTFont/FTTextureFont.cpp.orig	2014-03-24 03:01:25.0 +0100
+++ src/FTFont/FTTextureFont.cpp	2014-03-24 03:01:31.0 +0100
@@ -235,7 +235,7 @@
 glPushAttrib(GL_ENABLE_BIT | GL_COLOR_BUFFER_BIT);
 
 glEnable(GL_BLEND);
-glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA); // GL_ONE
+glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA, GL_ONE, GL_ONE_MINUS_SRC_ALPHA);
 
 glEnable(GL_TEXTURE_2D);
 

Bug#742468: typo and missing option in manpage

[Gianluigi Tiesi]

Package: patchelf
Severity: minor
Tags: upstream

Hi,
patchelf manpage says --print-intepreter instead of --print-interpreter
also it does not mention --remove-needed

Regards

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

Kernel: Linux 3.13-0.bpo.1-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 patchelf depends on:
ii  libc6   2.18-4
ii  libgcc1 1:4.8.2-17
ii  libstdc++6  4.8.2-17

patchelf recommends no packages.

patchelf suggests no packages.


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

Bug#742245: how-can-i-help should have --gift interface esp. for newbies.

[Tomasz Nitecki]

Heya,

On 23/03/14 18:37, shirish शिरीष wrote:
> at bottom :-
>
> 
>
>> [1] https://wiki.debian.org/how-can-i-help
> 
> Dear Tomasz,
> Just did some changes at the link shared above. Hopefully things are a
> bit more clearer. I  tried to move from third person to 1st person
> narrative as I find it to be otherwise unfeeling.
> 
> Anyways, just hope some things got cleared up. Lemme know if anything
> is left which needs to be added to the wiki page.

Yep, that is what I was thinking about, thanks! :)

I've cleared and rephrased some parts, but I think we can still make
some improvements :) Feel free to do so if anything comes to your mind.
I'll also think about it when I find a spare second.


Regards and thanks,
T.



signature.asc
Description: OpenPGP digital signature

Bug#667973: liferea: Custom date format doesn't work anymore

[Vincent Lefevre]

On 2014-03-23 22:09:47 -0300, Marcelo Lacerda wrote:
> Considering that the upstream maintainer have adamantly stated that he will
> not implement the requested feature, should this bug be marked as "wontfix"?

In my case, I stopped using Liferea since upstream didn't want to
make some basic features (such as date formatting) configurable[*],
and didn't want to waste my time maintaining the patch.

[*] and also because this new date feature was broken:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677696

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Bug#741740: ledger-3 bundles non-dfsg software

[Ben Finney]

On 16-Mar-2014, Jamie Nguyen wrote:

> ledger bundles an SHA-1 C++ implementation by Paul E. Jones which is
> licensed under a "Freeware Public License". This license does not allow
> modification and therefore does not adhere to the DFSG.

The upstream source for ‘ledger’ contains separate files for each license:

* doc/LICENSE.rtf
* doc/LICENSE-utfcpp
* doc/LICENSE-sha1
* doc/LICENSE

Each of these need to be described in ‘debian/copyright’.

As Jamie says, the ‘doc/LICENSE-sha1’ contains a copyright notice and
license text; the license terms are non-free (permission is not granted to
redistribute modified versions, failing DFSG §3).

> There was a similar issue with the "orthanc" package. This was resolved
> when the upstream author switched to a different library with a license
> compatible with the DFSG:

In the case of SHA-1, there are numerous implementations; some of them
(e.g. http://www.tamale.net/sha1/>) are licensed under free software
terms.

The package maintainer could replace the non-free files with a free
equivalent, and changing any relevant function calls to match, thereby
resolving this bug. Then, provide the patch to the ‘ledger’ upstream
maintainer, helping them to resolve the issue in a future version.

-- 
 \“Always code as if the guy who ends up maintaining your code |
  `\ will be a violent psychopath who knows where you live.” —John |
_o__) F. Woods |
Ben Finney 


signature.asc
Description: Digital signature

Bug#742467: Please add aarch64 support to support-archs.patch

[Adam Conrad]

Package: ncl
Version: 6.1.2-6
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/support-archs.patch: Add aarch64* for arm64 support.

Patch should be self-explanatory.  I used aarch64* instead of just
aarch64, as there's also a _be port floating around out there (not
that I imagine we ever intend to build Debian or Ubuntu for it, but
might as well be complete, just in case).

... Adam

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

Kernel: Linux 3.13.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru ncl-6.1.2/debian/changelog ncl-6.1.2/debian/changelog
diff -Nru ncl-6.1.2/debian/patches/support-archs.patch ncl-6.1.2/debian/patches/support-archs.patch
--- ncl-6.1.2/debian/patches/support-archs.patch	2014-03-01 04:30:32.0 -0700
+++ ncl-6.1.2/debian/patches/support-archs.patch	2014-03-23 18:31:29.0 -0600
@@ -7,7 +7,7 @@
 ===
 --- ncl-6.1.2.orig/config/ymake	2014-02-24 16:38:51.850789684 +
 +++ ncl-6.1.2/config/ymake	2014-02-24 16:38:51.846789853 +
-@@ -365,19 +365,17 @@
+@@ -365,19 +365,18 @@
  	caseamd64:
  casei*64:
  casex*64:
@@ -17,6 +17,7 @@
 +casesparc*:
 +casearm*:
 +caseppc*:
++caseaarch64*:
  casealpha:
  set model   = $mach
  set arch= $mach

Bug#742466: bash-completion: unexpected EOF while looking for matching `) while completing in subshell

[Philipp Hagemeister]

Package: bash-completion
Version: 1:2.1-4
Severity: normal

Dear Maintainer,

to reproduce:

Type  cat $(which b
Type [Tab].

With prior versions of bash-completions, this completed base64, basename, bash,
etc.

The current version outputs:

bash: unexpected EOF while looking for matching `)'
bash: syntax error: unexpected end of file

I believe the old behavior to be correct and the new one to be a bug.



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

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

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

bash-completion recommends no packages.

bash-completion 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#742245: how-can-i-help should have --gift interface esp. for newbies.

[Tomasz Nitecki]

Hey,

On 23/03/14 14:02, shirish शिरीष wrote:
>
> 
>
>> There are quite a few reasons why a package could be removed. At the
>> moment, how-can-i-help cannot tell why so it provides you with qa link
>> (so you can check yourself). Why do you think it is a bug?
> 
> It would have been better if the qa link could be parsed and those
> bugs known but as shared perhaps a non-issue or something that could
> be tackled later perhaps.

Yes, that is an interesting and most likely doable idea. It would
probably require some back end changes (as we should not reveal the list
of installed packages by querying QA pages directly). Maybe it's not on
the top of the TODO list, but I'll give it a though (and ask Lucas if it
is doable from his point of view).


> 
> 
>> That is true, but DDs also use how-can-i-help :)
> 
> I was under the impression the tool was mainly for newcomers. If DD's
> are also using then it's worthwhile for sure.

I think it is useful for everyone who wishes to contribute to Debian -
newcomers who are looking for a good starting point, seasoned users who
can help maintain packages they often use and DDs who have some spare
time to sponsor new uploads :)


>> Of course, I do agree that many types of opportunities might not be
>> suitable to a fresh newcomer. So while I don't think we should hide them
>> by default, adding an option to show only selected types (using command
>> parameter; no configuration) is a nice idea :)
> 
> Yes. The idea should be to be simple . In the background it could list
> all and grep and show only those which are being asked for in the
> -- option.

I will use existing filtering methods. Just change them a bit so
everything works nicely (and -- can be called to temporarily
override opportunities that are configured to be hidden).


>> By no means was I planning to hide them. You should be able to show any
>> combination of types. I was just thinking about adding a 'hint' text
>> about trying 'gift' bugs first. This could make someone to look only for
>> those and miss other type of opportunity in a package he or she uses.
>> Probably not a real issue.
> 
> Don't see any issue there, please go ahead. I would love to see combos as 
> well.
> 
> $how-can-i-help --gift --rfh --rfa --o

I think that --show:, might be a little more
readable. What do you think?


Regards,
T.



signature.asc
Description: OpenPGP digital signature

Bug#742465: ruby-docker-api: Please enable tests during build time

[Miguel Landaeta]

Package: src:ruby-docker-api
Version: 1.10.1-1
Severity: normal

I'm filing this mostly as a reminder for myself.
When I close ITP bug for ruby-vcr (#695195) I'll get back to this.

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

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

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at
http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#742380: Debian bug #742380: please respect http_proxy settings

[Tomasz Nitecki]

Hey,

> I don't think it's sensible to work around broken configuration,
> http_proxy should specify http or https, so... I think closing this
> bug is right. Obviously feel free to reopen if you think thats
> appropriate.

Nah, I agree with you. I was only thinking about adding a warning about
incorrect http_proxy configuration (so a user is not surprised that we
try to connect without proxy), but I've decided against it. Lets keep
how-can-i-help simple and doing only what it is supposed to do.

Only one things bugs me - I do think that some applications (yes, wget
I'm looking at you) do work, even if they are given http_proxy without
URI scheme. I'll check that tomorrow.


Regards and thanks,
T.



signature.asc
Description: OpenPGP digital signature

Bug#710424: xfce4: Opacity when window is moved/resized settings don't get saved when PC turns off

[Alejandro Carrazzoni]

Package: xfce4
Version: 4.10.1
Followup-For: Bug #710424

I've checked and it seems Xfwm does read the opacity settings from Xfconf
correctly but then they get changed to 100 right after reading those settings.
It looks like the culprit is the CLAMP macro being used, but this macro doesn't
seem to be from Xfwm.



-- 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.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce  3.0.1-2
ii  libxfce4ui-utils   4.11.1-2
ii  orage  4.10.0-1+b1
ii  thunar 1.6.3-1
ii  xfce4-appfinder4.10.1-1
ii  xfce4-mixer4.10.0-3
ii  xfce4-panel4.10.1-1
ii  xfce4-session  4.10.1-5
ii  xfce4-settings 4.10.1-2
ii  xfconf 4.10.0-2
ii  xfdesktop4 4.10.2-3
ii  xfwm4  4.11.1-2

Versions of packages xfce4 recommends:
ii  desktop-base  7.0.3
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.8.0-4
ii  xfce4-notifyd 0.2.4-2
ii  xorg  1:7.7+6

Versions of packages xfce4 suggests:
pn  gtk3-engines-xfce
pn  xfce4-goodies
ii  xfce4-power-manager  1.2.0-3

-- 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#742464: pcscd: System pcscd service stops unexpectedly

[Tom Lowenthal]

Package: pcscd
Version: 1.8.4-1+deb7u1
Severity: important

Dear Maintainer,

I run `pcscd` as a system service, and use smartcards as part of logon
authentication. In the last week, I've frequently experienced logon failures.
When a user tries to log on, the system hasn't recognised the smartcard.
Booting into single user mode, I can't find anything wrong with any configs.
After rebooting, I stated paying closer attention to the `pcscd` service. After
a few hours, it's not running. My syslog contains the following:


user@hostname:~$ sudo cat /var/log/syslog | grep pcscd
Mar 23 14:00:19 hostname pcscd: dyn_unix.c:81:DYN_GetAddress()
IFDHCreateChannelByName: /usr/lib/pcsc/drivers/openct-ifd.bundle/Contents/Linux
/openct-ifd.so: undefined symbol: IFDHCreateChann
Mar 23 14:00:19 hostname pcscd: readerfactory.c:972:RFInitializeReader() Open
Port 0x20 Failed (usb:08e6/3438:libudev:0:/dev/bus/usb/004/003)
Mar 23 14:00:19 hostname pcscd: readerfactory.c:279:RFAddReader() Generic CCID
Reader init failed.
Mar 23 14:00:19 hostname pcscd: hotplug_libudev.c:379:HPAddDevice() Failed
adding USB device: Generic CCID Reader
Mar 23 14:00:19 hostname pcscd: commands.c:890:CmdEscape error on byte 10
Mar 23 14:00:53 hostname pcscd: ccid_usb.c:660:WriteUSB() write failed (4/3):
-4 No such device
Mar 23 14:14:07 hostname pcscd: dyn_unix.c:81:DYN_GetAddress()
IFDHCreateChannelByName: /usr/lib/pcsc/drivers/openct-ifd.bundle/Contents/Linux
/openct-ifd.so: undefined symbol: IFDHCreateChann
Mar 23 14:14:07 hostname pcscd: readerfactory.c:972:RFInitializeReader() Open
Port 0x20 Failed (usb:08e6/3438:libudev:0:/dev/bus/usb/004/003)
Mar 23 14:14:07 hostname pcscd: readerfactory.c:279:RFAddReader() Generic CCID
Reader init failed.
Mar 23 14:14:07 hostname pcscd: hotplug_libudev.c:379:HPAddDevice() Failed
adding USB device: Generic CCID Reader
Mar 23 14:14:07 hostname pcscd: commands.c:890:CmdEscape error on byte 10
Mar 23 14:19:33 hostname pcscd: ccid_usb.c:660:WriteUSB() write failed (4/3):
-4 No such device
Mar 23 14:51:14 hostname kernel: [ 2276.016025] pcscd[6327]: segfault at
7f865a939fb6 ip 7f865a939fb6 sp 7f865a929ec0 error 14
Mar 23 14:52:06 hostname pcscd: dyn_unix.c:81:DYN_GetAddress()
IFDHCreateChannelByName: /usr/lib/pcsc/drivers/openct-ifd.bundle/Contents/Linux
/openct-ifd.so: undefined symbol: IFDHCreateChann
Mar 23 14:52:06 hostname pcscd: readerfactory.c:972:RFInitializeReader() Open
Port 0x20 Failed (usb:08e6/3438:libudev:0:/dev/bus/usb/004/005)
Mar 23 14:52:06 hostname pcscd: readerfactory.c:279:RFAddReader() Generic CCID
Reader init failed.
Mar 23 14:52:06 hostname pcscd: hotplug_libudev.c:379:HPAddDevice() Failed
adding USB device: Generic CCID Reader
Mar 23 14:52:06 hostname pcscd: commands.c:890:CmdEscape error on byte 10
Mar 23 14:57:22 hostname pcscd: ccid_usb.c:660:WriteUSB() write failed (4/5):
-4 No such device
Mar 23 14:57:50 hostname kernel: [ 2671.434228] pcscd[3549]: segfault at
7f2393757fb6 ip 7f2393757fb6 sp 7f2393747ec0 error 14




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

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

Versions of packages pcscd depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-38+deb7u1
ii  libccid [pcsc-ifd-handler]  1.4.7-1
ii  libpcsclite11.8.4-1+deb7u1
ii  libudev0175-7.2
ii  lsb-base4.1+Debian8+deb7u1
ii  openct [pcsc-ifd-handler]   0.6.20-1.2

pcscd recommends no packages.

Versions of packages pcscd suggests:
pn  systemd  

-- 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#667973: liferea: Custom date format doesn't work anymore

[Marcelo Lacerda]

Considering that the upstream maintainer have adamantly stated that he 
will not implement the requested feature, should this bug be marked as 
"wontfix"?



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

Bug#725281: liferea: Doesn't open URL in external browser

[Marcelo Lacerda]

Hi, seems like the problem was solved in liferea 1.10.5 but we are still 
packaging 1.10.3


Should something be done about this?


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

Bug#724042: fdisk should not warn when extended partition boundaries aren't aligned with physical disk boundaries

[Julian Gilbey]

On Sun, Mar 23, 2014 at 11:00:26PM +, Julian Gilbey wrote:
> On Mon, Feb 10, 2014 at 06:58:48PM -0500, Phillip Susi wrote:
> > I am not able to reproduce this and since you said you didn't keep the
> > original partition table that caused it, I'm going to close the bug
> > for now.  Let me know if you find a partition table that reproduces it.
> 
> OK, I've got one.  I formatted a 2TB disk using cfdisk, and attached
> is what cfdisk reports.
> [...]

I just found the following web page:

http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html?ca=dgr-lnxw074KB-Disksdth-LX

It seems like this is what I've run up against, and cfdisk without any
special options didn't give me any warnings.

So I'll probably have to start again and reformat my hard disk.

I don't know whether fdisk would have warned me had I tried to format
the disk using that instead; cfdisk is certainly problematic here.

   Julian


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

Bug#742463: fcrackzip crashes when files are cracked with dictionarys

[DrOetcker]

Package: fcrackzip
Version: 1.0-5kali1
Severity: important

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

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
tryed to crack a file. a better description under: 
https://bugs.launchpad.net/debian/+source/fcrackzip/+bug/1296467
   * What was the outcome of this action?
see attached link
   * What outcome did you expect instead?
a cracked zipfile :)


-- System Information:
Debian Release: Kali Linux 1.0.6
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-kali1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages fcrackzip depends on:
ii  libc6  2.13-38+deb7u1

fcrackzip recommends no packages.

Versions of packages fcrackzip suggests:
ii  unzip 6.0-8
ii  wamerican [wordlist]  7.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

Bug#741620: upgrade broke starttls?

[John Seymour]

I can confirm that this bug exists. i had to roll back to the previous 
version the get starttls working.

--
*John Seymour*
Research Physicist and IT Manager

National Acoustic Laboratories 
/A Division of Australian Hearing/

Australian Hearing Hub
16 University Avenue
Macquarie University NSW 2109 Australia
P +61 2 9412 6839
F +61 2 9412 6769

Please consider the environment before printing this email

Bug#741886: Fails to remember password

[Michael Biebl]

Am 24.03.2014 01:07, schrieb Michael Biebl:
> Am 24.03.2014 00:14, schrieb Sandro Knauß:
>> Hello,
>>
>> We think this issue is fixed with qtkeychain 0.3.0. It would be nice, if you 
>> could test your issue it with the qtkeychain 0.3.0 again.
> 
> It does, indeed.

The password is now stored in gnome-keyring with 0.3.0, which is nice.

I've manually cleaned up .local/share/data/ownCloud/owncloud.cfg where
my password seems to have been stored in clear text.

Would it be possible to clean up the password from owncloud.cfg
automatically once the password has been successfully stored in
gnome-keyring (resp. kwallet)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#742462: kde-workspace-bin: ksystraycmd has no man page

[Frank Heckenbach]

Package: kde-workspace-bin
Version: 4:4.8.4-6
Severity: normal

According to http://www.debian.org/doc/debian-policy/ch-docs.html:
"Each program, utility, and function should have an associated
manual page included in the same package. [...] If no manual page is
available, this is considered as a bug and should be reported to the
Debian Bug Tracking System".

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


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

Bug#741886: Fails to remember password

[Michael Biebl]

Am 24.03.2014 00:14, schrieb Sandro Knauß:
> Hello,
> 
> We think this issue is fixed with qtkeychain 0.3.0. It would be nice, if you 
> could test your issue it with the qtkeychain 0.3.0 again.

It does, indeed.

Thanks,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#742461: mate-settings-daemon enters a infinite crash/restart loop

[Tom Maneiro]

Package: mate-settings-daemon
Version: 1.8.0-1
Severity: grave
Justification: renders package unusable

After doing a apt dist-update last night, several core components of MATE were
upgraded to 1.8 on my Jessie system.

Normally I use KDE, but from time to time I also use MATE, but since that
update I've been unable to reach a stable desktop. Everything starts to flicker
badly: panels, menus, tray icons, desktop icons. Fonts and dialogs switch font
sizes, menus are hard to use, and in general, the overall desktop feels
extremely unstable and sluggish.

Taking a look at dmesg, I find dozens of these:
[  621.039193] traps: mate-settings-d[12942] trap int3 ip:7ff691c3a3c9
sp:7fff62967f40 error:0
[  621.583086] traps: mate-settings-d[12963] trap int3 ip:7f6cf8dbc3c9
sp:7fff2c45d9e0 error:0
[  622.144056] traps: mate-settings-d[12982] trap int3 ip:7f8023b6d3c9
sp:7fff476512b0 error:0
[  622.717133] traps: mate-settings-d[13009] trap int3 ip:7f1059c9d3c9
sp:7fff96c0a210 error:0
[  623.261964] traps: mate-settings-d[13034] trap int3 ip:7f10dbc413c9
sp:7fffb5473430 error:0
[  623.819512] traps: mate-settings-d[13061] trap int3 ip:7ff2d2bc13c9
sp:7fff21f21640 error:0
[  624.355532] traps: mate-settings-d[13081] trap int3 ip:7f66db7843c9
sp:7fff11fbecc0 error:0
[  624.899599] traps: mate-settings-d[13108] trap int3 ip:7f14966b33c9
sp:7fff2518efc0 error:0
[  625.463491] traps: mate-settings-d[13135] trap int3 ip:7f1f5019b3c9
sp:7fffb9e93260 error:0
[  626.051037] traps: mate-settings-d[13162] trap int3 ip:7f56a6a813c9
sp:7fff9fea4cb0 error:0
[  626.602089] traps: mate-settings-d[13190] trap int3 ip:7f9c52e473c9
sp:7fff8217cf50 error:0
[  627.186409] traps: mate-settings-d[13217] trap int3 ip:7fc7eaa183c9
sp:74926d10 error:0
[  627.725624] traps: mate-settings-d[13236] trap int3 ip:7f426cf153c9
sp:7fffbbfd2bb0 error:0
[  628.295965] traps: mate-settings-d[13262] trap int3 ip:7f6a982823c9
sp:7fff9418ab50 error:0
[  628.829837] traps: mate-settings-d[13289] trap int3 ip:7f8d9cf5c3c9
sp:7fff50c74520 error:0
[  629.450491] traps: mate-settings-d[13308] trap int3 ip:7f8b2c2663c9
sp:7fff4c84fb30 error:0
[  630.016590] traps: mate-settings-d[13331] trap int3 ip:7f43da0fb3c9
sp:7fff38086700 error:0
[  630.555314] traps: mate-settings-d[13358] trap int3 ip:7fd7a9b503c9
sp:7fff73a05c80 error:0
[  631.119840] traps: mate-settings-d[13386] trap int3 ip:7ff4c042a3c9
sp:7fff48037df0 error:0
[  631.707592] traps: mate-settings-d[13413] trap int3 ip:7f0056e3f3c9
sp:7fff8b866740 error:0
[  632.264920] traps: mate-settings-d[13440] trap int3 ip:7f25142ff3c9
sp:7fffb113ab30 error:0
[  632.814582] traps: mate-settings-d[13467] trap int3 ip:7fb5387d03c9
sp:7fff1a405f10 error:0
which matches the frequency of the desktop flickering, which means that
mate-settings-daemon is at fault (it gets killed, desktop loses settings, it
respawns, icons and widgets gets their colors and fonts back, then it gets
killed again... and repated until I manage to logoff. Hence because of this,
MATE is completely broken on my system.

I've tried switching mate-settings-desktop backends (I had GStreamer, tried
switching to Pulse) since the actual mate-settings-daemon binary seems to live
on those, but to no avail - desktop is still unstable.



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

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

Versions of packages mate-settings-daemon depends on:
ii  mate-settings-daemon-gstreamer  1.8.0-1

mate-settings-daemon recommends no packages.

mate-settings-daemon 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#742423: wine-unstable is *still* unusable

[Marc Dequènes (Duck)]

Quoting "Marc Dequènes (Duck)" :

You closed #742021 and #742317 in a hurry, but the logic in  
/usr/bin/wine-unstable is to look for the real 32/64 binaries in the  
same directory while you moved them into /usr/lib/wine-unstable/,  
thus your package is unusable.


Broken analysis due to a workaround. Here is the trace of the current problem:

$ winecfg
+ basename /usr/bin/winecfg .exe
+ appname=winecfg.exe
+ test -z
+ test ! -z
+ WINEPREFIX=/home/duck/.wine
+ test -e /home/duck/.wine/system.reg
+ wine=/usr/bin/wine
+ exec /usr/bin/wine winecfg.exe
/usr/bin/winecfg: 36: exec: /usr/bin/wine: not found

I'm not using wine directly but through playonlinux, thus there is no  
trace of me using wine-unstable in any reg file, this is a broken  
assumption.


Btw you also broke using playonlinux or other tools around because  
they all expect a "wine" binary and not "wine-unstable". Unless there  
is an alternative mechanism for choosing the default version i think  
using wine-unstable remains unusable (but using an alternative would  
probably break your current logic).


--
Marc Dequènes (Duck)



pgptujQJ1qU3A.pgp
Description: PGP Digital Signature

Bug#741893: Update

[mgreger]

Out of curiosity I created a KVM virtual machine on the same physical box and 
installed Debian Wheezy. Under the VM the same torrent ran fine. There were 
some differences in setup though: The physical box running Jessie has a single 
btrfs filesystem mounted at root with compression enabled. The virtual machine 
used ext4 for the root filesystem and btrfs without compression for /home.


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

Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user

[Stefan Lippers-Hollmann]

Hi

On Sunday 23 March 2014, Ben Hutchings wrote:
> Some time ago you committed:
> 
> r497 | slh-guest | 2012-02-23 12:20:25 + (Thu, 23 Feb 2012) | 1 line
> 
>   detection stages (Closes: #660956).
> 
> Index: debian/changelog
> ===
> --- debian/changelog(revision 496)
> +++ debian/changelog(revision 497)
> @@ -88,7 +88,7 @@
>  lirc 0.7.1pre2-8, previous versions unconditionally started an 
> interactive
>  non-debconf hardware detection/ selection menu, which always left
>  hardware.conf modified; md5sums for prior versions apply to aborted h/w
> -detection stages.
> +detection stages (Closes: #660956).
>  
>   -- Stefan Lippers-Hollmann   Sat, 28 Jan 2012 20:03:16 +0100
>  
> 
> I think you actually meant to close #655969.

Thanks for noticing this, I didn't match up to the bug closure with the
correct changelog entry when the bug was filed after the actual change
had already been done long before. Given that both bugs will be fixed 
in the same version, the actual effects would have been limited, but 
I've fixed it (and removed a duplicate bug closure) in [1].

> Anyway, as the postinst in wheezy does not appear to modify the config
> file, it appears that further upgrades should not have this problem.
> Given that the bug was tagged squeeze-ignore and wheezy-ignore, perhaps
> it can now be closed?

I certainly won't object against closing this bug, especially as 
neither squeeze nor wheezy will be changed in this regard anymore
(most users actually using lirc, would have needed to adapt their
configuration for kernel >= 2.6.37 anyways[2], when lirc was merged
into the kernel and several modules moved from lirc to RC_CORE). 
However technically speaking, squeeze is still supported until roughly
2014-05-06 (depending on the actual EOL date to be announced by the 
stable release team) - and squeeze to wheezy upgrades also remain 
affected. While technically not correct either, it might make sense to 
drop its severity below the RC threshold though, to avoid bug squashers
from wasting time on this though.

On the other hand there will be an upload, with the afforementioned bug
closures soon (for some value of 'soon', probably before the middle of
the year), which requires some adaptions to these pending changes (in 
order to provide native systemd units, the sysv initscripts will have 
to be split into individual initscripts for lirc, lircmd and irexec, so
the (to be added) systemd units can mask the corresponding initscripts 
properly[3]) - and it's best to avoid needless/ forseeable conffile 
churn until this is settled.

Regards
Stefan Lippers-Hollmann

[1] 
http://anonscm.debian.org/viewvc/pkg-lirc/lirc/trunk/debian/changelog?r1=517&r2=518
[2] https://lists.debian.org/debian-backports/2012/04/msg00076.html
[3] lirc's sysv initscripts are working fine under systemd's sysv 
compatibility mode, but native support needs further changes.


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

Bug#741886: Fails to remember password

[Sandro Knauß]

Hello,

We think this issue is fixed with qtkeychain 0.3.0. It would be nice, if you 
could test your issue it with the qtkeychain 0.3.0 again.

Regards,

sandro

--
On Monday 17 March 2014 15:36:42 Michael Biebl wrote:
> Am 17.03.2014 15:19, schrieb Sandro Knauß:
> > Hello,
> > 
> > what desktop environment you use? Do you have the kwalletmanager running?
> > 
> > All password stuff is done by libqtkeychain. So maybe you issue is solved
> > if qtkeychain 0.3.0 enters sid.
> 
> I'm using GNOME.
> 
> Afaicr this worked in the past and this is a recent regression.


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

Bug#742460: lightdm-gtk-greeter root window cursor problems

[Ken Milmore]

Package: lightdm-gtk-greeter
Version: 1.1.6-2
Severity: normal
Tags: upstream patch

Dear Maintainer,

LightDM causes problems with mouse cursors and startup notifications on the
Xfce desktop (and possibly elsewhere).  These seem to be caused by the lightdm
greeter setting a device-specific cursor on the root window (i.e. a cursor set
through XIDefineCursor, called in this case through gdk_window_set_cursor).
This cusror overrides any "normal" cursors set in the desktop environment with
XDefineCursor.

On Xfce in particular, the most noticeable effect is that application startup
notifications do not work - no busy cursor is shown when an application is
launched from the desktop or menus.  Also, if a pointer theme is set, this is
overridden on the root window which continues to show the pointer which was set
by lightdm.

An easy way to demonstrate this problem is to run "xsetroot -cursor_name watch"
from a terminal window.  A "busy" cursor should appear when the pointer is
moved over the desktop; but instead the default arrow cursor remains.

This problem appears to have already been reported in several other places:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694353
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671121
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482

The discussion following on from the Ubuntu bug report seems to have got to the
root of the problem:  When a "device cursor" has been set, it overrides any
"ordinary" cursor defined on the window.  Unfortunately nobody seems to have
applied a fix yet.

I would like to suggest that the attached patch be applied, which I have
tested on Wheezy with Xfce.  It sets the root cursor using XDefineCursor, which
avoids the problems caused by the XInput2 cursor precedence rules.  A fairly
thorough explanation of why this should work appears on comment 15 of the
Ubuntu bug report.

I think the patch should also apply against Jessie/Sid, although I haven't had
a chance to test it on those platforms yet.


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

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

Versions of packages lightdm-gtk-greeter depends on:
ii  libc6   2.13-38+deb7u1
ii  libcairo2   1.12.2-3
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk-3-0  3.4.2-7
ii  liblightdm-gobject-1-0  1.2.2-4
ii  libx11-62:1.5.0-1+deb7u1

Versions of packages lightdm-gtk-greeter recommends:
ii  desktop-base   7.0.3
ii  gnome-icon-theme   3.4.0-2
ii  gnome-themes-standard  3.4.2-2.1
ii  policykit-10.105-3

lightdm-gtk-greeter suggests no packages.

-- no debconf information

*** /home/data/ken/local/default-cursor.patch
diff -Naur lightdm-gtk-greeter-1.1.6.orig/src/lightdm-gtk-greeter.c lightdm-
gtk-greeter-1.1.6/src/lightdm-gtk-greeter.c
--- lightdm-gtk-greeter-1.1.6.orig/src/lightdm-gtk-greeter.c2012-05-21
10:47:42.0 +0100
+++ lightdm-gtk-greeter-1.1.6/src/lightdm-gtk-greeter.c 2014-03-23
22:09:58.723502815 +
@@ -722,7 +722,7 @@
 return EXIT_FAILURE;

 /* Set default cursor */
-gdk_window_set_cursor (gdk_get_default_root_window (), gdk_cursor_new
(GDK_LEFT_PTR));
+XDefineCursor(gdk_x11_get_default_xdisplay (),
gdk_x11_get_default_root_xwindow (), gdk_x11_cursor_get_xcursor (gdk_cursor_new
(GDK_LEFT_PTR)));


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

Bug#724042: fdisk should not warn when extended partition boundaries aren't aligned with physical disk boundaries

[Julian Gilbey]

On Mon, Feb 10, 2014 at 06:58:48PM -0500, Phillip Susi wrote:
> I am not able to reproduce this and since you said you didn't keep the
> original partition table that caused it, I'm going to close the bug
> for now.  Let me know if you find a partition table that reproduces it.

OK, I've got one.  I formatted a 2TB disk using cfdisk, and attached
is what cfdisk reports.

Then I first had an inkling that something was amiss when mke2fs said
(note the first few lines):

erdos:~ # mke2fs -t ext4 -c -c -L BOOT /dev/sdb1
mke2fs 1.42.9 (4-Feb-2014)
/dev/sdb1 alignment is offset by 512 bytes.
This may result in very poor performance, (re)-partitioning suggested.
Filesystem label=BOOT
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=4 blocks, Stripe width=4 blocks
98392 inodes, 393560 blocks
19678 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
49 block groups
8192 blocks per group, 8192 fragments per group
2008 inodes per group
Superblock backups stored on blocks:
   8193, 24577, 40961, 57345, 73729, 204801, 221185

Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

erdos:~ # 

Here is the fdisk output for this disk:

erdos:~ # fdisk /dev/sdb

The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.

Command (m for help): p

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1   *  63  787184  393561   83  Linux
Partition 1 does not start on physical sector boundary.
/dev/sdb2  787185   293748524   146480670   83  Linux
Partition 2 does not start on physical sector boundary.
/dev/sdb3   293748525  3711721859  1708986667+  83  Linux
Partition 3 does not start on physical sector boundary.
/dev/sdb4  3711721860  3907029167976536545  Extended
Partition 4 does not start on physical sector boundary.
/dev/sdb5  3711721923  3731256899 9767488+  83  Linux
Partition 5 does not start on physical sector boundary.
/dev/sdb6  3731256963  388750508978124063+  83  Linux
Partition 6 does not start on physical sector boundary.
/dev/sdb7  3887505153  3907029167 9762007+  82  Linux swap / Solaris
Partition 7 does not start on physical sector boundary.

Command (m for help): 

So cfdisk and fdisk definitely disagree about whether or not this is
proper behaviour.

I'll pause for a couple of days before reformatting the disk, in case
you wish me to run any more tests in the meantime.

Best wishes,

   Julian
Disk Drive: /dev/sdb
Sector 0:
0x000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01
0x1C0: 01 00 83 FE 3F 30 3F 00 00 00 B2 02 0C 00 00 00
0x1D0: 01 31 83 FE FF FF F1 02 0C 00 3C 3C 76 11 00 FE
0x1E0: FF FF 83 FE FF FF 2D 3F 82 11 57 22 BA CB 00

Bug#476441: Please revist this choice. AES128 vs AES256 (for gnutls)

[Daniel Kahn Gillmor]

On 03/22/2014 01:27 PM, Robert de Bath wrote:
> On Fri, 21 Mar 2014, Daniel Kahn Gillmor wrote:
>> which keys are you talking about here?  where are these numbers from?
> I ran the one line script in this "bug report" against a current Debian
> testing install.
> 
> $ for i in /etc/ssl/certs/*; do certtool -i < $i; done|grep
> 'bits'|sort|uniq -c
> 
> The Modulus lines are:
>  76 Modulus (bits 1024):
> 424 Modulus (bits 2048):
> 136 Modulus (bits 4096):


/etc/ssl/certs is a set of config files.  in general, it's supposed to
contain the certificates for root CAs that are "trusted" by the system
to certify other parties.  Usually, they certify intermediate CAs, who
in turn certify end-entities (EEs) such as web servers or e-mail users.

root CAs tend to have long-term keys -- they need to be valid for a
decade or longer.  And they are incredibly high-value targets, since
cracking a root CA's key means the ability to mint arbitrary
certificates, which lets the attacker MiTM any connection for which
they're on the network path (or just impersonate the server without MiTM).

actual EEs themselves might not use 4096-bit keys.  Indeed, an actual EE
might only have a key that's used for a year before it is superseded by
a new key.  cracking a single EE's key means getting access to their
previous non-PFS traffic and being able to MiTM (or impersonate) just
that EE.

The key strength requirements for these scenarios (root CA vs. EE) are
likely to be different.

> Yes, from the estimates above that may be a good idea. A 4K key would
> be overkill, but 3K as in their 'Future' suggestions might be right.
> What's more as this is often used once per connection (not per byte)
> your power/heat budget note isn't as applicable.

"once per connection" can potentially be very often depending on the
work pattern of your particular communications suite.

>> Please cite your sources explicitly.  Google does not return the same
>> answers for everyone, or over time.
> Sorry, on rechecking this seems to be the "drop dead" date for 3DES;
> I though 3DES was already dead ... oh well.

In the real world, 3DES is still very much alive (i think windows XP's
SChannel TLS implementation supports only RC4 and 3DES), though 3DES is
much slower than (and somewhat less secure than) AES 128.

Again, though, it would have been nice if you had cited your sources,
with a URL at least.  anyone stumbling across this discussion in the
future still won't know what you were referring to here.

Regards,

--dkg



signature.asc
Description: OpenPGP digital signature

Bug#670040: pax do not work at all

[Hilmar Preusse]

On 23.04.12 Heiko Oberdiek (heiko.oberd...@googlemail.com) wrote:
> On Mon, Apr 23, 2012 at 08:05:32AM +0900, Norbert Preining wrote:

Dear Heiko,,

> > we got a bug report in Debian that pax does not work, and the 
> > reason is that pdfbox is much newer in Debian, namely 1.6.0 from
> > Apache:
> > 


> Currently I don't have time to update pax to the new pdfbox.
> TL freeze is nearing and my bundle update is more important to me.
> At least the update of README is on the way to CTAN.
> 
Any chance to have pax/pdfannotextractor working w/ recent pdfbox in
the future?

Thanks!

Regards,
  Hilmar
-- 
sigmentation fault


signature.asc
Description: Digital signature

Bug#673022: texlive-base: happened with upgrade to 2013.20140123-1 from 2013.20140314-1

[Hilmar Preusse]

On 23.03.14 js (jsh...@yahoo.com) wrote:

Hi,

> Package: texlive-base
> Followup-For: Bug #673022
> 

> During an upgrade texlive-base:all 2013.20140123-1 2013.20140314-1,
> I got the same error as reported in this bug, so that texlive-base,
> and all packages dependent on it, failed to get configured:
> 
No, this is a new issue. Please open a new bug for it. Could you try
if installing texlive-omega solves your problem?

Hilmar
-- 
sigmentation fault


signature.asc
Description: Digital signature

Bug#742423: wine-unstable is *still* unusable

[Marc Dequènes (Duck)]

Control: severity -1 critical

Coin,

You closed #742021 and #742317 in a hurry, but the logic in  
/usr/bin/wine-unstable is to look for the real 32/64 binaries in the  
same directory while you moved them into /usr/lib/wine-unstable/, thus  
your package is unusable.


Clearly this release was *again* not tested, not the slightest. I fear  
I don't understand how running wine --version or the like would be  
difficult or time consuming enough to justify such kind of blind  
uploads while you're in the process of a complete rework of  
wine/wine-unstable packages (to be co-installable if I understood it  
well). You're really harming Debian and Debian users doing so, so  
please consider rethinking how you work for Debian, delegating,  
dropping packages to have a decent workload, i don't know, but PLEASE  
DO SOMETHING!


Regards.

--
Marc Dequènes (Duck)



pgpYAtEZN_YRT.pgp
Description: PGP Digital Signature

Bug#742459: xpdf: -fg and -bg do not work

[Sebastien Desreux]

Package: xpdf
Version: 3.03-10
Severity: normal

Dear Maintainer,


I am a long time user of Xpdf, which I really like and use daily. 

I hoped that upgrading to the current Debian stable would fix a minor by 
annoying bug: neither the -fg nor the -bg option of Xpdf work. Here is an 
example with a PDF file (produced with LaTeX):

~/tmp>ls -l 
-rw-r--r-- 1 seb seb 296362 Mar 23 22:59 a.pdf

~/tmp>\xpdf -fg black a.pdf 
error: "black" file not found

~/temp>\xpdf -bg red a.pdf
error: "red" file not found

~/tmp>

and no window opens, whereas all is well with "\xpdf a.pdf".

-fg black is, in fact, the default behaviour of Xpdf, but no other color seems 
to work either (I'd love cyan4, as in my Xterms...). Same if I try using 
-foreground (or --foreground).

Strangely, the -rv (reverse video) works, although it should be equivalent to
-fg white -bg black (which doesn't work).

When I work on a large screen at night, I really like the background of all 
windows to be black. The rest of the time, the standard black fg on white bg 
is fine.


Am I missing something so self-evident that it is not even in the man page?
Can you reproduce this bug, which has been present in Xpdf for as long as I 
can remember, at least 5 years anyway?

Please let me know if I can help by giving more examples.


Best regards,
Sébastien Desreux.

*** 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 ***


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

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_US.iso88591)
Shell: /bin/sh linked to /bin/dash

Versions of packages xpdf depends on:
ii  lesstif2  1:0.95.2-1.1
ii  libc6 2.13-38+deb7u1
ii  libgcc1   1:4.7.2-5
ii  libpoppler19  0.18.4-6
ii  libstdc++64.7.2-5
ii  libx11-6  2:1.5.0-1+deb7u1
ii  libxt61:1.1.3-1+deb7u1

Versions of packages xpdf recommends:
ii  cups-bsd   1.5.3-5+deb7u1
ii  gsfonts-x110.22
ii  poppler-data   0.4.5-10
ii  poppler-utils  0.18.4-6

xpdf 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#742458: ITP: node-eventemitter2 -- A Node.js event emitter implementation with namespaces, wildcards, TTL and browser support.

[matthewp]

Package: wnpp
Severity: wishlist
Owner: matthewp 

* Package name: node-eventemitter2
  Version : 0.4.13
  Upstream Author : hij1nx 
* URL : https://www.npmjs.org/package/eventemitter2
* License : MIT
  Programming Lang: js
  Description : A Node.js event emitter implementation with namespaces, 
wildcards, TTL and browser support.

EventEmitter2 is an implementation of the EventEmitter found in Node.js
Features:
  -  Namespaces/Wildcards.
  -  Times To Listen (TTL), extends the once concept with many.
  -  Browser environment compatibility.
  -  Demonstrates good performance in benchmarks

This package was asked to package by the Debian Javascript Maintainers.
It is a nodejs lib, will be usefull for the grunt javascript automation tool 
packaging.
This is a little package, but also my first package so if you want to help me 
you are welcome.


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

Bug#742457: iceweasel: iceseasel UI unresponsive

[Brent]

Package: iceweasel
Version: 24.4.0esr-1
Severity: normal

The version of iceweasel that hit jessie today is totally unresponsive.
Clicking on the menus or any other item does not do anything.  The previous
version in jessie was fine last night.



-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: BetterPrivacy
Location: ${PROFILE_EXTENSIONS}/{d40f5e7b-d2cf-4856-b441-cc613eeffbe3}.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: Disconnect
Location: ${PROFILE_EXTENSIONS}/2...@disconnect.me.xpi
Status: enabled

Name: DoNotTrackMe
Location: ${PROFILE_EXTENSIONS}/donottrackp...@abine.com
Status: enabled

Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: enabled

Name: FlashGot
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{19503e42-ca3c-4c27-b1e2-9cdb2170ee34}
Package: xul-ext-flashgot
Status: enabled

Name: HTTPS-Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org
Status: enabled

Name: Readability
Location: ${PROFILE_EXTENSIONS}/readabil...@readability.com.xpi
Status: enabled

-- Plugins information
Name: Garmin Communicator
Location: /usr/lib/mozilla/plugins/npGarminPlugin.so
Package: garmin-plugin
Status: enabled

Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled

Name: Shockwave Flash (11,2,202,346)
Location: /usr/lib/flashplayer-mozilla/libflashplayer.so
Package: flashplayer-mozilla
Status: enabled


-- Addons package information
ii  flashplayer-mo 3:11.2.202.3 amd64Macromedia Flash Player.
ii  garmin-plugin  0.3.20-1 amd64browser plugin for communication 
ii  gnome-shell3.8.4-5+b1   amd64graphical shell for the GNOME des
ii  iceweasel  24.4.0esr-1  amd64Web browser based on Firefox
ii  xul-ext-flashg 1.5.5.96+dfs all  Extension to handle downloads wit

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

Kernel: Linux 3.12.6.140115 (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 iceweasel depends on:
ii  debianutils 4.4
ii  fontconfig  2.11.0-2
ii  libc6   2.18-4
ii  libgdk-pixbuf2.0-0  2.30.6-1
ii  libglib2.0-02.38.2-5
ii  libgtk2.0-0 2.24.22-1
ii  libnspr42:4.10.3-1
ii  libnspr4-0d 2:4.10.3-1
ii  libsqlite3-03.8.3.1-1
ii  libstdc++6  4.8.2-16
ii  procps  1:3.3.9-2
ii  xulrunner-24.0  24.4.0esr-1

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  fonts-mathjax  
pn  fonts-oflb-asana-math  
ii  fonts-stix [otf-stix]  1.1.0-1
ii  libgssapi-krb5-2   1.12.1+dfsg-1
pn  mozplugger 

Versions of packages xulrunner-24.0 depends on:
ii  libasound21.0.27.2-3
ii  libatk1.0-0   2.10.0-2
ii  libbz2-1.01.0.6-5
ii  libc6 2.18-4
ii  libcairo2 1.12.16-2
ii  libdbus-1-3   1.8.0-2
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-1
ii  libfontconfig12.11.0-2
ii  libfreetype6  2.5.2-1
ii  libgcc1   1:4.8.2-16
ii  libgdk-pixbuf2.0-02.30.6-1
ii  libglib2.0-0  2.38.2-5
ii  libgtk2.0-0   2.24.22-1
ii  libhunspell-1.3-0 1.3.2-7
ii  libmozjs24d   24.4.0esr-1
ii  libnspr4  2:4.10.3-1
ii  libnss3   2:3.15.4-2
ii  libpango-1.0-01.36.2-2
ii  libsqlite3-0  3.8.3.1-1
ii  libstartup-notification0  0.12-3
ii  libstdc++64.8.2-16
ii  libvpx1   1.3.0-2
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages xulrunner-24.0 suggests:
ii  libcanberra0  0.30-2
ii  libgnomeui-0  2.24.5-3

-- 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#740275: fuser acts as if -M is specified if any of -acikmsuvw are

[Craig Small]

On Sat, Mar 22, 2014 at 05:39:06PM +0100, Alex Wilk wrote:
> Something is wrong. The new package is missing.
It is rather odd.

It was uploaded on 28th Feb, I've got the upload timestamp but the pts
doesn't show it.

 - Craig

-- 
Craig Small (@smallsees)   http://enc.com.au/   csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


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

Bug#742456: Log sanitizing and SQL injection

[David Prévot]

Package: spip
Version: 2.1.17-1+deb7u3
Severity: important
Tags: security upstream
Control: fixed -1 3.1~21281-1
Control: fixed -1 3.0.16-1
Control: found -1 2.1.1-3squeeze8

Hi,

The latest upstream update [1] fixes two security issues:
- an SQL injection, already blocked by the security screen;
- a lack of sanitizing visible in log files.

I’ve already prepared the Wheezy [2] and Squeeze updates, and open this
bug report in order to follow up with the security team and the release
team to get these a priori minor issues fixed in the next (old)stable
update.

1: 
http://contrib.spip.net/Alerte-SPIP-2-0-25-SPIP-2-1-26-SPIP-3-0-16-sont-gavees
2: http://people.debian.org/~taffit/spip/

Regards

David


signature.asc
Description: Digital signature

Bug#742450: Pending fixes for bugs in the get-flash-videos package

[pkg-perl-maintainers]

tag 742450 + pending
thanks

Some bugs in the get-flash-videos package are closed in revision
5b8de30d41fd219eff933871dcf62c2c67ffdad0 in branch 'master' by Daniel
Lintott

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/get-flash-videos.git;a=commitdiff;h=5b8de30

Commit message:

Add patch to update Google Video Search URL

Closes: #742450
Thanks: Dallas E. Legan


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

Bug#656719: Please provide xvmc and vdpau Gallium3D video acceleration drivers (libg3dvl-mesa package)

[Pali Rohár]

2014-03-23 21:19 GMT+01:00 Julien Cristau :
> On Sat, Mar 22, 2014 at 19:03:52 +0100, Pali Rohár wrote:
>
>> Hello!
>>
>> It looks like nouveau, r600 and radeonsi vdpau drivers are already in
>> debian repository. But not xvmc libraries. See:
>>
> Correct, we're probably not going to be enabling xvmc.
>
> Cheers,
> Julien

Can I ask for reason why not to enable also xvmc?

-- 
Pali Rohár
pali.ro...@gmail.com


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

Bug#742455: w3m: Gopher support not working

[Gabriel Pérez-Cerezo]

Package: w3m
Version: 0.5.3-15
Severity: normal


Dear Maintainer,

accessing any site through the Gopher protocol does not work. It always returns
a strange HTML page with approximately the following content (I get this when I
run `w3m -dump gopher://uninformativ.de'):

Index of gopher://uninformativ.de/1

[unsupported]`1' invalid.

It is not a problem with the page, it is a problem with the browser. Lynx works
just fine.

Best wishes,

Gabriel



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.12-1-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 w3m depends on:
ii  libc62.18-4
ii  libgc1c2 1:7.2d-6
ii  libgpm2  1.20.4-6.1
ii  libssl1.0.0  1.0.1f-1
ii  libtinfo55.9+20140118-1
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages w3m recommends:
ii  ca-certificates  20140223

Versions of packages w3m suggests:
pn  cmigemo   
ii  man-db2.6.6-1
ii  mime-support  3.54
ii  w3m-el1.4.483+0.20120614-7
pn  w3m-img   

-- no debconf information

-- 
Gabriel Pérez-Cerezo Flohr
Website: http://gpcf.eu  E-mail: gabr...@gpcf.eu
GPG Key: D353EC69 (get it from http://gpcf.eu/key.asc)


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

Bug#742454: ruby: gem command should depend on ruby-dev

[Simon Ruggier]

Package: ruby
Version: 1:1.9.3.4
Severity: normal

I'm a Debian testing user who is new to Ruby. I tried to install jekyll
using
the gem command, and received an error about mkmf that I found very
confusing.
I only figured out what the problem was by searching the web for answers
until
I realized I needed to install ruby-dev. The description of ruby-dev
acknowledges that it is required to build many gems. I feel that a user
experience like this is a hard sell for users of other operating systems.

I can think of three ways to fix this (not all of which may be feasible):

- Split gem into its own package (if this is feasible), and make it depend
on
ruby-dev
- Merge ruby-dev into ruby
- Patch gem to offer to install ruby-dev when a user attempts to install a
gem
that requires mkmf



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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL
set to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby depends on:
ii  ruby1.9.1  1.9.3.484-2

ruby recommends no packages.

Versions of packages ruby suggests:
pn  ri
ii  ruby-dev  1:1.9.3.4



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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby depends on:
ii  ruby1.9.1  1.9.3.484-2

ruby recommends no packages.

Versions of packages ruby suggests:
pn  ri
ii  ruby-dev  1:1.9.3.4

-- no debconf information

Bug#711620: Pending fixes for bugs in the libthread-queue-any-perl package

[pkg-perl-maintainers]

tag 711620 + pending
thanks

Some bugs in the libthread-queue-any-perl package are closed in
revision 3214abe1b8ddbb4001db1c20e243216de220fc75 in branch 'master'
by gregor herrmann

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libthread-queue-any-perl.git;a=commitdiff;h=3214abe

Commit message:

New upstream release. Fixes "FTBFS with perl 5.18: test failures" (Closes: 
#711620)


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

Bug#742400: Broken FxAccounts removal causing failures?

[Adam Dane]

Looking at the browser console I see a couple of errors caused by the 
incomplete removal of the module |FxAccounts.jsm|:


NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 
0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import] 
browser.js:9402


And:

[Exception... "Component returned failure code: 0x80520012 
(NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]"  nsresult: 
"0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: 
resource://services-sync/browserid_identity.js ::  :: line 
23"  data: no] browserid_identity.js:23


These failures may explain the other components' failures?

Thanks,

Adam


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

Bug#730401: gnome-shell: clock with date and seconds is wrong when you, lock the screen

[Davide Prina]

On 23/03/2014 20:31, Davide Prina wrote:

On 22/03/2014 00:16, althaser wrote:


I am using gnome-shell 3.8.4-5+b1 and I can't reproduce this issue here.

Do you still have the issue ?


I confirm, with 3.8.4-5+b1 gnome-shell version this bug is resolved


I must reconsider what I have wrote, the bug is still present: the clock 
was 22:27:KW, but the lock show 22:02:XY


So probably depend on what hour or minut are actually.

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Fate una prova di guida ... e tenetevi la macchina!:
http://linguistico.sf.net/wiki/doku.php?id=usaooo2
Non autorizzo la memorizzazione del mio indirizzo su outlook


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

Bug#742452: libfglrx: Preinst check for old GPUs compares uppercase & lowercase hex values, does not work in 60/134 cases

[Jo Shields]

Package: libfglrx
Version: 14.1~beta1.3-1+steamos2
Severity: important
Tags: patch

libfglrx.preinst contains a list of old, unsupported GPUs. The aim is to
warn users if they try to install on old hardware which the driver will
not support. This check is done by string comparison between the values
in lspci and the list in libfglrx.preinst. However, the list in
libfglrx.preinst stores hex digits A-F in upper case, and lspci returns
hex digits a-f in lower case. As a result, any GPU whose PCI ID contains
a hex value will not trigger the installation warning as intended. `tr`
can do simple conversion of case, so adding it to the lspci pipeline is
a simple fix for the issue.

-- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'saucy'), (100, 'saucy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-18-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- fglrx-driver-14.3~beta1.0/debian/libfglrx.preinst.orig	2014-03-23 21:01:40.929360241 +
+++ fglrx-driver-14.3~beta1.0/debian/libfglrx.preinst	2014-03-23 21:05:21.501352847 +
@@ -146,6 +146,7 @@
 	if lspci --version > /dev/null 2>&1; then
 		lspci -mn \
 		| awk '{ gsub("\"",""); if ($2 == "0300") { print $1 " " $3$4 } }' \
+		| tr '[:lower:]' '[:upper:]' \
 		| while read dev id
 		do
 			for x in $UNSUPPORTED_PCIIDS

Bug#742453: ITP: geophar -- Swiss army knife for the math teacher

[Georges Khaznadar]

Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 

* Package name: geophar
  Version : 13.04.5
  Upstream Author : Nicolas Pourcelot 
* URL : http://sourceforge.net/projects/geophar/
* License : GPL-2+
  Programming Lang: Python
  Description : Swiss army knife for the math teacher

 This package is a deep rewrite of Nicolas Pourcelot's previous wxgeometrie.
 After its publication, wxgeometrie will become a transitional package, to be
 replaced.
 .
 Geophar contains every tool you would like to find when
 preparing math courses, exercises or their keys.


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

Bug#742436: src:xutils-dev: Do not Build-Depend on cpp-4.7

[Cyril Brulebois]

Christian Svensson  (2014-03-23):
> On Sun, Mar 23, 2014 at 8:16 PM, Julien Cristau  wrote:
> > No, there's a reason we use 4.7 and not a newer version.
> 
> What reason is that?

Read the changelog?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#742451: pngquant aborts everytime

[VA]

Package: pngquant
Version: 2.0.1-1

Everytime I run pngquant, it immediately aborts. Here's a sample session
where I generate an image with ImageMagick:

% convert rose: rose.png
% pngquant 256 rose.png
pngquant: mempool.c:40: mempool_create: Assertion `!((uintptr_t)(*mptr +
(*mptr)->used) & 15UL)' failed.
zsh: abort  pngquant 256 rose.png


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

Bug#735047: [fglrx-driver]

[Alexander Kudrevatykh]

sorry for late answer, not received your message.
I can't test igpu configuration anymore because with latest kernels (3.12
and 3.13) after switching to --px-igpu xorg does not start at all

latest messages from xorg.log are

[   638.585] (II) LoadModule: "fglrx"
[   638.585] (WW) Warning, couldn't open module fglrx
[   638.585] (II) UnloadModule: "fglrx"
[   638.585] (II) Unloading fglrx
[   638.585] (EE) Failed to load module "fglrx" (module does not exist, 0)
[   638.585] (EE) No drivers available.
[   638.585] (EE)
Fatal server error:
[   638.586] (EE) no screens found(EE)
[   638.587] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[   638.590] (EE) Please also check the log file at "/var/log/Xorg.0.log"
for additional information.
[   638.591] (EE)

Bug#742404: nvidia legacy

[ael]

I also have the same problem.

I used to compile my own kernels and the fetch the latest driver from
the nvidia site. It often happened that nvidia lagged behind the latest
kernel release, but a message usually produced an updated
driver within a day or so.

Of course, we all hate the nvidia closed drivers, but I am not at all
sure that the nouveau driver is yet fit for purpose. The only hint
that things may be improving is that nvidia staff have recently
started to make contributions to nouveau.

It seems that we are being discouraged from "doing things the Debian
way" if we all individually need to prod nvidia each time they lag
behind the current kernel.

However, I have just checked the nvidia site and *there is* a new
version available released 11/3/2014: 
http://www.nvidia.co.uk/download/driverResults.aspx/74013/en-uk
which is marked as version 304.1210.

So it seems that all that debian has to do is to update the package
to, presumably, nvidia-graphics-drivers-legacy-304.121.
Not that I have tested against 3.13-1. So perhaps nvidia is not to
blame, at least not more than before?

ael


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

Bug#742436: src:xutils-dev: Do not Build-Depend on cpp-4.7

[Christian Svensson]

On Sun, Mar 23, 2014 at 8:16 PM, Julien Cristau  wrote:
> No, there's a reason we use 4.7 and not a newer version.

What reason is that?


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

Bug#689658: web2py package update

[Matus Valo]

Hi Jose,

I found out that package web2py is outdated in debian (there is also 
raised bug #689658 reporting this issue), so I decided to package newer 
version (2.9.4).  Hence, I am requesting sponsorship for this package. 
The URL of the package is:


http://mentors.debian.net/package/web2py

The respective dsc file can be found at:

http://mentors.debian.net/debian/pool/main/w/web2py/web2py_2.9.4-1.1.dsc

All my changes are recored in the changelog. I am aware of one 
dependency problem. The package python-gluon is python library package 
and it has hardcoded path of the splash logo ( in widget.py file), but 
this file is installed with package python-web2py and hence widget.py 
file is broken when python-gluon is installed without python-web2py.


Regards,

Matus Valo


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

Bug#656719: Please provide xvmc and vdpau Gallium3D video acceleration drivers (libg3dvl-mesa package)

[Julien Cristau]

On Sat, Mar 22, 2014 at 19:03:52 +0100, Pali Rohár wrote:

> Hello!
> 
> It looks like nouveau, r600 and radeonsi vdpau drivers are already in
> debian repository. But not xvmc libraries. See:
> 
Correct, we're probably not going to be enabling xvmc.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#742436: src:xutils-dev: Do not Build-Depend on cpp-4.7

[Julien Cristau]

On Sun, Mar 23, 2014 at 18:01:15 +, Christian Svensson wrote:

> Package: src:xutils-dev
> Version: 7.7+2
> Severity: normal
> 
> Dear Maintainer,
> 
> The earliest GCC targeting 'or1k', packaged for Debian, is 4.8.
> Depending on cpp-4.7 in this case makes the package not buildable.
> 
> May I suggest depending on cpp (>=4.7) or something like that?
> 
No, there's a reason we use 4.7 and not a newer version.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#736319: get-flash-videos: The search function is broken

[Daniel Lintott]

clone 736319 -1
retitle -1 get-flash-videos: Update Google Video Search URL
severity -1 important
retitle 736319 get-flash-videos: Add support for more search results
severity 736319 wishlist
stop

Thank you for your bug report!

I have had a look your patch and agree that the search is broken, due to
the Google URL having changed... I have created a new bug for this.

With regards to the new parameters I feel this would create too much of
a divergence from upstream (which appears to be active on GitHub [0]),
but I shall suggest the changes there.

[0] https://github.com/monsieurvideo/get-flash-videos
-- 
Daniel Lintott
GPG Key: 4096R/5D73EC6E



signature.asc
Description: OpenPGP digital signature

Bug#719646: gnome-shell: Activities panel (and SUPER shortcut) too wide for screen size

[Pierre AUSSAGUEL]

Hi,

I cannot try because I sold that computer 6 month ago.
I think this bug should be closed.

Thank you anyway.


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

Bug#741049: tmux: C-b C-c no longer starts new window in CWD

[Michael Büsch]

On Sun, 23 Mar 2014 20:01:14 +0100
Romain Francoise  wrote:

> It's not Debian's place to decide defaults...

It's Debian's place to decide Debian-defaults, though.

> > Or if that's not desired, please add an example configuration
> > to /usr/share/doc/tmux/examples/ that brings back the feature.
> > This would save users part of the trouble in search for a fix.
> 
> There are examples of how to use the new way in the upstream changelog
> already,

An upstream changelog is not exactly the place where the _user_ would expect
information about required configuration changes on a debian package,
to restore a feature that suddenly stopped working.
From the user's point of view a feature suddenly just broke. And
to the user that looks like a bug. So there should be an easy and
quick way to get information on it, without digging through upstream changelogs.

> But maybe a FAQ entry would make sense.

Yes, please document that somewhere with example config snippets to
get the old behavior back.

> And as the person who implemented it in
> the first place[1], I think the new way to do things is much better.

Well, and as the user, who uses it in the first place, I think the
old way was just fine. ;)

-- 
Greetings, Michael.


signature.asc
Description: PGP signature

Bug#724469: FTBFS on all big-endian architectures

[Adam Conrad]

On Sun, Mar 23, 2014 at 10:33:32AM +0100, intrigeri wrote:
> 
> I'd rather not drop s390x from the list of architectures this package
> is built for, but this RC bug has now been around for 6 months, and at
> some point I'll want to get rid of it.

Not fixing a bug isn't the way to get rid of it.  This isn't s390x
specific, it's incorrect code leading to failure on 64-bit BE arches,
of which there are several, it just happens that s390x is the only
officially-supported one.

I understand that you personally may not have the skills to fix it,
and need input from either a porter or upstream, but that doesn't mean
the bug magically doesn't exist if no one gives you a patch to fix it.

... Adam


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

Bug#616689: Confirming the bug.

[José Antonio Insua]

Hello!

I'm using an up-to-date SID, and I can also recently reproduce this bug.

Changing the root timeout to 30 s doesn't make any effect.

This bug has been recently introduced, because 1 week ago, I was able to boot 
my workstation normally, and now I need to activate the LV's manually at the 
initramfs prompt.

Please, request more info if you need it.

Best regards.
Jose Antonio Insua


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

Bug#742392: hurd: Hang during apt-get upgrade from last image release

[Petter Reinholdtsen]

I got some help from gg0 on IRC to debug this issue.  He proposed to
upgrade everything except hurd first, and this worked:

  apt-get update
  apt-mark hold hurd
  apt-get dist-upgrade
  apt-mark unhold hurd

This reduced the amount of packages to upgrade to the minimum.
Upgrading using apt-get dist-upgrade now also hung, but it was a lot
quicker to test as I had snapshotted the freshly upgraded system.

We tried adding a serial console (adding
GRUB_CMDLINE_GNUMACH="console=com0" in /etc/default/grub and running
update-grub) and see if anything showed up there.  No messages showed
up in the serial console when the system got stuck.  I did however
notice that the hang caused the machine to no longer respond to ping,
and my ssh connections would stop working too.

Last, I tried to upgrade over ssh (instead of the console I had tried
initially, and then I got a bit more text before the machine went
dead:

  root@debian:~# apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
libdb5.1
  The following NEW packages will be installed:
login
  The following packages will be upgraded:
db5.1-util hurd hurd-dev hurd-libs0.3
  4 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
  Need to get 1351 kB/6117 kB of archives.
  After this operation, 2894 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://cdn.debian.net/debian/ sid/main login hurd-i386 1:4.1.5.1-1.1 
[695 kB]
  Get:2 http://cdn.debian.net/debian/ sid/main db5.1-util hurd-i386 5.1.29-8 
[656 kB]
  Fetched 1351 kB in 7s (177 kB/s)  

  Reading changelogs... Done
  (Reading database ... 38608 files and directories currently installed.)
  Preparing to unpack .../hurd-dev_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd-dev (1:0.5.git20140320-1) over (1:0.5.git20140203-1) ...


  Preparing to unpack .../hurd-libs0.3_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd-libs0.3:hurd-i386 (1:0.5.git20140320-1) over 
(1:0.5.git20140203-1) ...
  Setting up hurd-libs0.3:hurd-i386 (1:0.5.git20140320-1) ...
  Processing triggers for libc-bin (2.18-3) ...
  (Reading database ... 38608 files and directories currently installed.)
  Preparing to unpack .../hurd_1%3a0.5.git20140320-1_hurd-i386.deb ...
  Unpacking hurd (1:0.5.git20140320-1) over (1:0.5.git20140203-1) ...
  Setting up hurd (1:0.5.git20140320-1) ...
  Installing new version of config file /etc/hurd/rc ...
  Installing new version of config file /etc/init.d/hurd-console ...

Not sure how to continue, as gg0 is not able to reproduce the problem,
but at least here it happen every time.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#742447: opendmarc: report scripts build with DB::yes engine instead of MySQL

[Karol Auguštin]

Source: opendmarc
Version: 1.2.0+dfsg-1
Severity: important

Reporting tools provided by the package are build using DBD::yes perl
module which is not available in Debian. This makes DMARC reporting
pretty unusable. Affected tools are: opendmarc-import,
opendmarc-expire, opendmarc-reports, opendmarc-params. This is strange
because opendmarc package recommends libdbd-mysql-perl.

After changing to DBD::mysql everything is working as expected. I'm not
providing a patch, because in my opinion this is for maintainer to
decide either to fix it by providing sql backend in debian/rules or to
file a bug upstream because INSTALL file clearly says that MySQL
backend is default.

--- /usr/sbin/opendmarc-import  2014-03-18 04:59:18.0 +0100
+++ /usr/local/sbin/opendmarc-import2014-03-15 07:26:16.0
+0100 @@ -19,7 +19,7 @@
 use Getopt::Long;
 use POSIX;

-require DBD::yes;
+require DBD::mysql;

 # general
 my $progname  = basename($0);
@@ -41,7 +41,7 @@
 my $dbpasswd;
 my $dbport;

-my $dbscheme = "yes";
+my $dbscheme = "mysql";

 my $dbi_a;
 my $dbi_h;

Kind regards,
Karol Auguštin





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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)


signature.asc
Description: PGP signature

Bug#732218: transition: gpsd

[Julien Cristau]

On Thu, Mar 20, 2014 at 23:20:47 +0100, Bernd Zeimetz wrote:

> Hi,
> 
> > Feel free to upload to sid.  Let us know when binNMUs can be scheduled.
> 
> uploaded right now.
> 
BinNMUs scheduled.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#742009: liferea: New upstream release 1.10.7

[Paul Gevers]

On 23-03-14 17:31, Christian Marillat wrote:
> David Smith  writes:
> 
> [...]
> 
>> I created a more detailed way to reproduce the problem here:
>> https://sourceforge.net/p/liferea/bugs/1142/#f50c
>>
>> But the potential for it to always segfault on startup seems like a
>> pretty nasty bug.  Even though technically it might not have happened on
>> previous versions due to flaws in previous versions not even being able
>> to add this feed at all. When I run liferea 1.10.4, the feed disappears
>> and I can't seem to add it no matter what I do.  1.10.7 seems to allow
>> it to be added if you try hard enough, but then just crashes later.
> 
> Adding this feed doesn't crash i386 or amd64 liferea. I think you have
> miscompiled liferea.

Hi David,

I also tried to reproduce your test case. For what it is worth, after
adding intltoolize to the override_dh_autoreconf target and compiling
the package from the Alioth git (targeting wheezy-amd64) also I can't
reproduce your test case.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#742446: vim-runtime: Changelog filetype plugin NewChangelogEntry has a syntax error

[Taran Lynn]

Package: vim-runtime
Version: 2:7.3.547-7
Severity: normal
Tags: patch

Dear Maintainer,

I was using Vim for editing a changelog. I found the NewChangelogEntry command
and executed it.
Upon execution I was given an error saying that the field variable was not
defined in the passwd_field function.
I fixed this by changing the references to field to a:field in the passwd_field
function in the file $VIMRUNTIME/ftplugin/changelog.vim.



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

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

vim-runtime depends on no packages.

Versions of packages vim-runtime recommends:
ii  vim2:7.3.547-7
ii  vim-gtk [vim]  2:7.3.547-7
ii  vim-tiny   2:7.3.547-7

vim-runtime 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#719417: Can confirm - this bug is still in wheezy and jessie

[Julian Andres Klode]

Control: severity -1 wishlist

On Sun, Mar 23, 2014 at 08:26:00PM +0100, Fabian Zimmermann wrote:
> Hello,
> 
> can confirm this bug is still in "wheezy" and "jessie".

Of course you can reproduce it, but it's not a bug. It's a
feature.

> 
> to reproduce:
> 
> * install minimal debian
> * apt-get install task-lxde-desktop
> * aptitude show network-manager-gnome
> * aptitude why network-manager-gnome
> 
> --
> root@localhost:~# aptitude show network-manager-gnome
> Paket: network-manager-gnome
> Zustand: Installiert
> Automatisch installiert: nein
> 
> root@localhost:~# aptitude why network-manager-gnome
> i   task-lxde-desktop Hängt ab von lxde
> i A lxde  Empfiehltnetwork-manager-gnome
> --
> 
> This is really bad, because removing "task-lxde-desktop" wouldn't remove
> the whole network-manager-subsystem.
> 

Right, and previously people complained because removing the task removed
their complete desktop. We cannot have both and decided to switch to the
safe site and mark dependencies of metapackages as manually installed.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Please do not top-post if possible.


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

Bug#730401: gnome-shell: clock with date and seconds is wrong when you, lock the screen

[Davide Prina]

On 22/03/2014 00:16, althaser wrote:


I am using gnome-shell 3.8.4-5+b1 and I can't reproduce this issue here.

Do you still have the issue ?


I confirm, with 3.8.4-5+b1 gnome-shell version this bug is resolved

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Petizione contro il formato ms-ooxml:
http://www.noooxml.org/petition
Non autorizzo la memorizzazione del mio indirizzo su outlook


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

Bug#719417: Can confirm - this bug is still in wheezy and jessie

[Fabian Zimmermann]

Hello,

can confirm this bug is still in "wheezy" and "jessie".

to reproduce:

* install minimal debian
* apt-get install task-lxde-desktop
* aptitude show network-manager-gnome
* aptitude why network-manager-gnome

--
root@localhost:~# aptitude show network-manager-gnome
Paket: network-manager-gnome
Zustand: Installiert
Automatisch installiert: nein

root@localhost:~# aptitude why network-manager-gnome
i   task-lxde-desktop Hängt ab von lxde
i A lxde  Empfiehltnetwork-manager-gnome
--

This is really bad, because removing "task-lxde-desktop" wouldn't remove
the whole network-manager-subsystem.

Fabian


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

Bug#742444: synaptic: package list reset for sub-window

[Andreas Cadhalpun]

Package: synaptic
Version: 0.81
Severity: normal

Dear Maintainer,

When a sub-window of synaptic is shown (like when synaptic asks to 
remove a conflicting package), the list of packages shown in the main 
synaptic window is reset to show the top of the list (starting with 0ad 
currently). After canceling the front-window, still the wrong packages 
are shown, but moving the mouse over them brings back the correct packages.


Best regards,
Andreas

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (700, 'testing-updates'), (700, 'testing'), (600, 
'unstable'), (70, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.13-1
ii  libapt-inst1.5   0.9.16.1
ii  libapt-pkg4.12   0.9.16.1
ii  libatk1.0-0  2.10.0-2
ii  libc62.18-4
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libept1.4.12 1.0.12
ii  libgcc1  1:4.8.2-16
ii  libgdk-pixbuf2.0-0   2.30.6-1
ii  libglib2.0-0 2.38.2-5
ii  libgtk-3-0   3.10.7-1
ii  libpango-1.0-0   1.36.2-2
ii  libpangocairo-1.0-0  1.36.2-2
ii  libstdc++6   4.8.2-16
ii  libvte-2.90-91:0.34.9-1
ii  libx11-6 2:1.6.2-1
ii  libxapian22  1.2.17-1
ii  libxext6 2:1.3.2-1
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-6
ii  libgtk2-perl   2:1.249-1
ii  policykit-10.105-4
ii  rarian-compat  0.8.1-5

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.46
ii  deborphan1.7.28.8
pn  dwww 
ii  menu 2.1.46
pn  software-properties-gtk  
ii  tasksel  3.20

-- 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#742077: RFS: vcmi/0.95-1 [ITP]

[Jakub Wilk]

* Johannes Schauer , 2014-03-18, 23:38:

http://mentors.debian.net/debian/pool/main/v/vcmi/vcmi_0.95-1.dsc


Another remark:

I don't think that the “After installing this package, …” instructions 
belong in the package description. I'd rather put them in README.Debian.


But if you decide to keep them, the enumerated list should be indented 
by two spaces (see Policy §5.6.13).


--
Jakub Wilk


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

Bug#742445: synaptic: breaks are shown twice

[Andreas Cadhalpun]

Package: synaptic
Version: 0.81
Severity: normal

Dear Maintainer,

Breaks are shown twice in synaptic.

For example, the gdm3 control file contains:
Breaks: gnome-control-center (<< 3.0), gnome-orca (<< 2.30.0-2), 
gnome-panel (<< 3.0), gnome-screensaver (<< 2.17.7)


This is shown in synaptic as:
Breaks: gnome-control-center (<3.0)
Breaks: gnome-control-center (<3.0)
Breaks: gnome-orca (<2.30.0-2)
Breaks: /gnome-orca/
Breaks: gnome-panel (<3.0)
Breaks: gnome-panel (<3.0)
Breaks: gnome-screensaver (<2.17.7)
Breaks: gnome-screensaver (<2.17.7)

Here /gnome-orca/ means that it is shown in italic.

Dependencies are not doubled.

Best regards,
Andreas

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (700, 'testing-updates'), (700, 'testing'), (600, 
'unstable'), (70, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.13-1
ii  libapt-inst1.5   0.9.16.1
ii  libapt-pkg4.12   0.9.16.1
ii  libatk1.0-0  2.10.0-2
ii  libc62.18-4
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libept1.4.12 1.0.12
ii  libgcc1  1:4.8.2-16
ii  libgdk-pixbuf2.0-0   2.30.6-1
ii  libglib2.0-0 2.38.2-5
ii  libgtk-3-0   3.10.7-1
ii  libpango-1.0-0   1.36.2-2
ii  libpangocairo-1.0-0  1.36.2-2
ii  libstdc++6   4.8.2-16
ii  libvte-2.90-91:0.34.9-1
ii  libx11-6 2:1.6.2-1
ii  libxapian22  1.2.17-1
ii  libxext6 2:1.3.2-1
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-6
ii  libgtk2-perl   2:1.249-1
ii  policykit-10.105-4
ii  rarian-compat  0.8.1-5

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.46
ii  deborphan1.7.28.8
pn  dwww 
ii  menu 2.1.46
pn  software-properties-gtk  
ii  tasksel  3.20

-- 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#741049: tmux: C-b C-c no longer starts new window in CWD

[Romain Francoise]

Hi,

Michael Büsch  writes:

> What about adding a default configuration to /etc/tmux.conf
> that brings back the old behavior?

It's not Debian's place to decide defaults...

> Or if that's not desired, please add an example configuration
> to /usr/share/doc/tmux/examples/ that brings back the feature.
> This would save users part of the trouble in search for a fix.

There are examples of how to use the new way in the upstream changelog
already, and there are many possible configurations depending on what
the user wants exactly.

But maybe a FAQ entry would make sense.

> As-is, this clearly is a regression. A useful and very visible feature,
> that used to work well in previous releases, suddenly disappeared.

The feature is still there and works just as well as before, it's just
no longer enabled by default. And as the person who implemented it in
the first place[1], I think the new way to do things is much better.

[1] http://sourceforge.net/p/tmux/tmux-code/ci/c1b994852594b23

-- 
Romain Francoise 
http://people.debian.org/~rfrancoise/


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