hard:)

[Raphael]

Don't be like that...:)

 soon meet u  1<$digit> pm  now surf soon 

Best regards,
 Raphael


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

Bug#394144: v3.38 is here

[Raphael]

Hi,

Is there any progress on this feature?


Sincerely,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Say NO to Microsoft Office broken standard.
See http://www.noooxml.org/petition


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

Bug#394144: Partially fixed

[Raphael]

On 30/07/07, Ana Guerrero <[EMAIL PROTECTED]> wrote:
>
> tags 394144 -patch
> On Wed, Jun 27, 2007 at 08:51:37PM -0500, Raphael wrote:
> > retitle 394144 kword: formulas aren't displayed
> > thanks
> >
> > Just to notify:
> >
> > Kword doesn't crash anymore, but it doesn't display the formulas.
> >
>
> This patch is already applied in koffice 1.6.3. Raphael, maybe you could
> submit your problem again to upstream?

Oops, just sent a message to this bug report instead of an other one.
Anyways, I'll try to open a bug report tomorrow (if nobody else does
it before I do =) ) on bugs.kde.org.

>
> Ana
> >
>


-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Say NO to Microsoft Office broken standard.
See http://www.noooxml.org/petition


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

Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too

[Raphael Hertzog]

Control: tag -1 + moreinfo

Hello Markus & Merlin,

you reported that you were affected by Debian bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747637

Maximiliano believes that the latest update 1.13.0-1 should
fix the db upgrade problems (see below). Can you confirm this
so that we can close this bug ?

On Tue, 19 Aug 2014, Maximiliano Curia wrote:
> I think the new uploaded akonadi version (1.13.0-1) fixes more db upgrade
> cases, but I haven't had any issues with the previous upgrades so it's hard
> for me to be sure. Could you please confirm if it fixes the issues you had
> with the 1.12.1 version?
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141126104048.ga3...@home.ouaza.com

Bug#772318: kmix: bashism in /bin/sh script

[Raphael Geissert]

Package: kmix
Severity: important
Version: 4:4.14.0-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hi,

I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".

checkbashisms' output:
> possible bashism in ./usr/bin/kmixremote line 10 ('function' is useless):
> function usage
> possible bashism in ./usr/bin/kmixremote line 21 ('function' is useless):
> function exit_with_error
> possible bashism in ./usr/bin/kmixremote line 30 ('function' is useless):
> function listMixers
> possible bashism in ./usr/bin/kmixremote line 40 ('function' is useless):
> function listControls


Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.

Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.

Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh

Thanks in advance,
Raphael Geissert


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2146137.aUySKWDNpM@eee

Bug#772316: kdevplatform8-libs: bashism in /bin/sh script

[Raphael Geissert]

Package: kdevplatform8-libs
Severity: important
Version: 1.7.0-2
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hi,

I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".

checkbashisms' output:
> possible bashism in ./usr/bin/kdev_format_source line 61 (should be 'b =
> a'):
> while ! [ "$(pwd)" == "/" ]; do


Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.

Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.

Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh

Thanks in advance,
Raphael Geissert


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3785328.sSULWaUYVz@eee

Bug#772315: kdesdk-scripts: bashism in /bin/sh script

[Raphael Geissert]

Package: kdesdk-scripts
Severity: important
Version: 4:4.14.1-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hi,

I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".

checkbashisms' output:
> possible bashism in ./usr/bin/cvsaddcurrentdir line 20 (should be 'b = 
a'):
> if [ "$answer" == "y" ]; then cvs add $file; fi
> possible bashism in ./usr/bin/build-progress.sh line 8 (echo -e):
>   echo -ne "\033]0;$1\007"


Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.

Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.

Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh

Thanks in advance,
Raphael Geissert


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1617388.4bOG8vHQTa@eee

Bug#881333: qtbase5-dev: Rebuild qtbase with OpenGL ES support for arm64

[Raphael Hertzog]

Control: reopen -1 hert...@debian.org

Hello,

On Mon, 13 Nov 2017, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Could you please rebuild qtbase with OpenGL ES acceleration on ARM64
> > instead so as to provide a better user experience on these devices?
> 
> As discussed on IRC, it means beaking ABI and also arm64 is likely to
> have DesktopOpenGL support as per
> https://nullr0ute.com/2017/09/the-state-of-open-source-accelerated-graphics-on-arm-devices/
> 
> So for the moment is a non-go.

I asked on IRC and mitya57 told me that we can revisit this decision.

I'm not an expert in this topic but in Kali we have quite some experience
in providing Kali images for specific ARM devices. Right now we are
working on getting Kali working in the Gemini PDA and this bug is a
blocker:
https://store.planetcom.co.uk/products/gemini-pda-1

I asked a few questions to the person working on this project. My questions
were those:
> Can we reasonably say that most arm64 boards have OpenGL ES but no
> regular OpenGL? Can you provide a somewhat up-to-date list to back up
> this fact?
> Can a QT compiled for OpenGL ES still benefit from some hardware
> acceleration on a board with full OpenGL support?

Here's the answer that I got from Re4son:

> I haven't come across any arm64 chipset with an OpenGL enabled GPU apart
> from 2 NVIDIA's CUDA based platforms. I've heard about the idea but they
> were merely academic and nothing seems to have come out of it.  Quite
> the opposite - everybody seem to toy with the idea of moving to Vulkan
> rather than GL.
> The core principle is to provide packages that match the GPU's attached
> to the architecture and according to the following stats, all but 2 of
> the GPU's attached to arm support only GLES:
> 
> https://www.khronos.org/conformance/adopters/conformant-products/opengles
> https://www.khronos.org/conformance/adopters/conformant-products/opengl
> 
> I haven't experimented with it, but according to the specifications
> OpenGL GPU's are capable of running GLES applications albeit not to the
> full potential of the hardware. The only scenario where I could see that
> being an issue is when someone puts a GL enabled GPU in an arm64 server
> and I cannot imagine that they are craving top shelf 3D acceleration of
> their qt applications.
> More objectively, Ubuntu did that switch two years ago and there have
> been no issues reported in launchpad as a result of it.

He wanted to get some confirmation of all this but he did not manage to
get any response from the experts he tried to contact.

Based on all this, it seems to me that we would better served by using OpenGL
ES on arm64. If we don't do this, we should likely be providing conflicting
packages to support both QT with OpenGL and QT with OpenGL ES but I can see
that becoming rather hard to handle.

And the fact that Ubuntu made the switch is reassuring: it can be done and it's
likely the most useful choice right now. I'm ccing the Ubuntu developer who
made the switch in case he can add something useful to this discussion (the
change happened in qtbase-opensource-src (5.5.1+dfsg-17ubuntu2~2 in yakkety
in 2016).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/


signature.asc
Description: PGP signature

Bug#881333: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

[Raphael Hertzog]

Hello Lisandro,

TLDR: thank you for starting this discussion, it was required as it's not
an easy decision to take as there is no realistic perfect solution, but I
believe you took the wrong decision. Please consider deferring the
decision to the technical committe by seeking his advice (point 6.1.3
of the constitution https://www.debian.org/devel/constitution.en.html#item-6).

On Sun, 25 Nov 2018, Lisandro Damián Nicanor Pérez Meyer wrote:
> It seems now clear that the general consensus seems to expect:
> = Qt available for both Desktop and ES OpenGL flavours
> = If no change is possible, keep arm64 with Desktop OpenGL support

I'm not pleased with how this discussion was handled. First of all,
you did not leave enough time for all stakeholders to participate in
the discussion (started on November 22th, closed November 25th, 3 days,
that's not a reasonable timeframe in particular when 2 of the 3 days
were in the week-end). I was aware of the discussion but did not
had the time to chime in, yet I was the person who re-opened the bug
#881333 in the first place.

I also invited someone else who is working on a concrete project involving
Kali Linux (Debian derivative) and off-the-shelf arm64 hardware available
now but he also did not have the time to contribute to the discussion.

Then I have read the whole discussion and I don't have the feeling that
any consensus has been reached. It was largely driven by Andy Simpkins
who explained his "gut feeling" as a tinkerer of arm* boards/devices and
Bret Curtis who contributes to some applications with very specific OpenGL
needs. While I value their contribution to the discussion, they both
represent very specific classes of users.

What I remember from this discussion is that the Windows build of Qt
use GLES 2 by default. It would have been interesting to find out the
rationale for this... because maybe the right decision for us would be
to switch to GLES 2 by default as well (on all architectures as jcristau
suggested). Someone else who likely also tried to ensure Qt for Windows is
usable on most hardware made that choice.

We got confirmation from many persons that almost all cards benefitting
from Desktop OpenGL would also work with OpenGL ES. So in terms of
hardware support, picking OpenGL ES is the right choice. In terms of
sofware support, it looks like that Desktop OpenGL is better as there
are a few applications that only work with Desktop OpenGL.

Software can be fixed/improved to also work with OpenGL ES. However
hardware, once bought, cannot be fixed to support Desktop OpenGL
when it has been designed for OpenGL ES only.

When taking all this into account, I believe that the right solution is
to use OpenGL ES on all architectures. This will provide the required
incentives for application developers who stick only to Desktop OpenGL
to support OpenGL ES (even it it's at the cost of using some intermediary
layer like https://github.com/p3/regal) and would maximize hardware
support on all architectures.

That said, I'm fine with a decision to change only arm64 since that's
an architecture were devices that support only OpenGL ES are in the
majority.

This is not a easy decision to make but we have a dedicated body to help
maintainers find the best technical decision when there are pros/cons
in both solutions, it's called the technical committee. Please consider
seeking their advice before taking your decision.

> Both Dmitry and I just learned that the RPI has the VC4 driver which enables 
> it to do hardware acceleration for Desktop OpenGL, we must admit that this is 
> a game changer in many ways, even if we are talking on just one board (but 
> quite an ubiquitous one). People wanting Qt+GLES on arm64 can always use 
> Ubuntu.

I don't see why this affects the decision in any way. AFAIK the VC4 driver
also enables hardware acceleration for OpenGL ES. And this is only
relevant for the RPI3 which is the only arm64 hardware.

Bret Curtis clearly explained that we do get good performances on older
RPI (armhf-based) precisely because of the VC4 driver being able to
leverage OpenGL ES too.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/


signature.asc
Description: PGP signature

Re: Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Raphael Hertzog]

Hi,

On Sat, 12 Jan 2019, Adrian Bunk wrote:
> pyside2 is now built without patchelf on mips64el.
> 
> Doing the same for mips and mipsel should fix the problem for pivy.

Yeah, but this is not going in the right direction. This means that
pyside will be built with the embedded patchelf. The embedded patchelf is
outdated. But it will build and do its work...

Really, if the test suite failure can't be fixed quickly, it would be
better to ignore the failure on the broken architectures and let the
package build anyway. It's unlikely that the tool is entirely broken...
and it's just a pity to ask pyside to deal with a varying set of
architectures for patchelf.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Re: Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

[Raphael Hertzog]

Hi,

On Sun, 13 Jan 2019, Adrian Bunk wrote:
> Test cases that passed in patchelf 0.8 fail since 0.9,
> and segmentation fault on things like setting rpath
> might be close enough to "entirely broken".

In that case, it would certainly help upstream if someone
(maintainer/porter) could try to "git bisect" the issue so that we can
better identify the issue.

And maybe we want to revert to the former patchelf in Debian
(i.e. 0.9+really0.8) if it lasts too long.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Raphael Geissert]

Hi Lisandro!

On Tue, 27 Oct 2015 15:30:42 -0300 Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Hi everyone! We possibly have two issues here.
>
> The first one is the reported one, which should be fixed.
>
> Now the second one might most probably be because qtx11extras migrated to
> testing when it shouldn't have. This is the first time it happens for us.

Doesn't that sound like there's a missing dependency, somewhere?
It sounds like a person using a testing-unstable mix would also be affected.


/me who also got hit by it
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

Bug#943709: Pyside2 package dependencies do not reflect Python module dependencies

[Raphael Hertzog]

Hi,

On Mon, 28 Oct 2019, Mark Weyer wrote:
> Package: python3-pyside2.qtgui
> Version: 5.11.2-3+rpi1
> Severity: normal
> 
> This bug is reported against an example package but is more general. Thus it
> pertains to more binary packages built from the same source package pyside2

Can you be a bit more explicit?

What sample dependencies are missing? Where do you see what you call "Python
module dependencies"?

Are you just basing this on the analysis of "import" statements or
something else?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Re: pyside2: Python2 removal in sid/bullseye

[Raphael Hertzog]

Version: 5.13.2-1

On Sat, 16 Nov 2019, Sandro Tosi wrote:
> On Fri, 30 Aug 2019 07:35:29 + Matthias Klose  wrote:
> > Package: src:pyside2
> > Version: 5.11.2-3
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> 
> version 5.13.2-1 changelog says "Remove almost all of Python 2 binary
> packages" but i dont see any python2 packages left in pyside2: can we
> close this bug then?

Yes, we can. Doing so now.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Various issues with pyside2

[Raphael Hertzog]

(Please CC me on reply)

Hello,

we need your help to support pyside2 on mipsel and mips64el.

mips64el test failures
--

First on mips64el we had this report of failing tests:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945421

But after a while the package managed to build:
https://buildd.debian.org/status/logs.php?pkg=pyside2&arch=mips64el

And we closed it thinking it was an issue with Qt that got fixed.
But the last NMU is failing again. So the failure seems to be
buildd-specific:

It fails to build om mipsel-aql-03 but it got built on eberlin.
Why?

Is this something to report to upstream?

mipsel build failure


On mipsel, the last NMU is failing to build but the previous upload built
fine but almost nothing changed in the package...

https://buildd.debian.org/status/logs.php?pkg=pyside2&arch=mipsel

The error is this one:

> CMake Error at /usr/lib/mipsel-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 
> (message):
>   The imported target "Qt5::Gui" references the file
> "/usr/lib/mipsel-linux-gnu/libEGL.so"
>   but this file does not exist.

Do you know of any recent Qt related regression related to this?

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Bug#951041: kde-standard: kde plasma upper right corner menu does not open any more after opening any application

[Raphael Langerhorst]

Package: kde-standard
Version: 5:104
Severity: important
Tags: upstream

Dear Maintainer,

I installed bullseye testing at first with xfce only and later added 
kde-standard
via apt-get install kde-standard. I believe the issue is not hardware dependent
but I used an AMD64 (intel celeron) based ACER laptop (Acer TravelMate B).

When logging in to kde plasma the menu at the top right corner opens normaly
(any number of times), but as soon as any application is started (through a
desktop icon or the K menu) the menu at the upper right corner of the desktop
does not respond anymore (does not open when left-clicking with mouse).

Logging out and in of the desktop (without restarting the computer)
makes the menu available again up to the point that any application is started,
which is the same behaviour as the first log in after computer startup.

It appears to be independent of an internet connection being available or not.

Closing all application does not make the menu available again (only logging
out and in of the desktop makes it available until again an application is
started).

I think it is an important usability issue as this menu is supposed to work
through the whole session and may be an apparent bug to a large audience.

Note that this bug may be applied to kde-plasma-desktop rather than kde-standard
meta-package but I cannot be sure on this so I chose kde-standard for reporting.

Thank you,
Raphael


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-standard depends on:
ii  akregator  4:19.08.3-1
ii  ark4:19.12.0-1
ii  dragonplayer   4:19.12.1-1
ii  gwenview   4:19.12.0-1+b1
ii  juk4:19.12.0-1
ii  kaddressbook   4:19.08.3-1
ii  kate   4:19.12.0-1
ii  kcalc  4:19.12.1-1
ii  kde-plasma-desktop 5:104
ii  kde-spectacle  19.12.0-2
ii  khelpcenter4:18.04.0-1+b1
ii  kmail  4:19.08.3-1
ii  knotes 4:19.08.3-1
ii  korganizer 4:19.08.3-1
ii  kwalletmanager 4:18.04.1-1+b1
ii  okular 4:17.12.2-2.2+b2
ii  plasma-dataengines-addons  4:5.14.5.1-2+b2
ii  plasma-pa  4:5.14.5-1+b2
ii  plasma-runners-addons  4:5.14.5.1-2+b2
ii  plasma-wallpapers-addons   4:5.14.5.1-2+b2
ii  plasma-widgets-addons  4:5.14.5.1-2+b2
ii  polkit-kde-agent-1 4:5.14.5-1+b1
ii  sweeper4:18.04.1-1+b1

Versions of packages kde-standard recommends:
ii  konq-plugins  4:19.08.2-2+b1
ii  plasma-nm 4:5.14.5-2+b2

Versions of packages kde-standard suggests:
pn  kopete
pn  skanlite  

-- no debconf information

Wheezy update of kde4libs?

[Raphael Hertzog]

Hello Maximiliano and other KDE maintainer(s),

The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of kde4libs:
https://security-tracker.debian.org/tracker/source-package/kde4libs

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of kde4libs updates
for the LTS releases.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Re: RFP: pyside2 -- Python bindings for Qt5

[Raphael Hertzog]

Control: retitle -1 ITP: pyside2 -- Qt for Python
Control: owner -1 sop...@freexian.com

On Sat, 14 Apr 2018 10:09:38 +0200 Francesco Poli  
wrote:
> Moreover, if I read the [announcement] correctly, it seems that PySide2
> is going to be renamed as "Qt for Python" and adopted as official Qt
> bindings for Python...
> 
> [announcement]: 
> 
> 
> I really hope someone with good Python Debian packaging skills will
> soon package pyside2 for inclusion in Debian!

Sophie and me are working to bring pyside2 into Debian. We would like to
put it in pkg-kde-extras. I requested access to the salsa group for this.

Should it go in "Qt" or "Qt extras"? It's going to be something official by
the upstream Qt project so I think that "Qt" might be good.

Currently the code is split among two git repositories upstream:
https://code.qt.io/cgit/pyside/pyside-setup.git/
https://code.qt.io/cgit/pyside/pyside-tools.git/

pyside-setup contains PySide2 and Shiboken2 (and pyside2-tools as
submodule).

I think we will want to name the source package and the git repository
"pyside2" anyway. And we possibly want to integrate pyside-tools
in the .orig.tar.gz as well.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Re: RFP: pyside2 -- Python bindings for Qt5

[Raphael Hertzog]

Hi,

On Fri, 11 May 2018, Maximiliano Curia wrote:
> > Sophie and me are working to bring pyside2 into Debian. We would like to
> > put it in pkg-kde-extras. I requested access to the salsa group for this.
> 
> Welcome to the team!

Thank you. Note that you granted me "developer" access which doesn't let
me create new repositories, so I will need one of you to create the
repository and also to add sophie (sbrun-guest) as member of the
pyside2 repository.

> Right, but please take into account that the packages maintained under the
> qt tree use a debian directory only packaging branch, and in general, they
> use all the same packaging structure (no dpm, no upstream branches or tags
> in the public repos, etc). This set of rules is more relaxed in qt-extras
> and kde-extras.

Are the rules documented somewhere?

At this point, there are no (versioned) upstream tarball releases so it
might be better to be able to have full sources in the git repository and
generate the .orig.tar.gz out of it.

> Also, I don't see in the bug log any comment about the current pyside
> maintenance, are the pyside maintainers ok with moving the new version of
> the project to a different repository in a different team?

There are no Uploaders left in debian/control both for pyside and
shiboken:
https://salsa.debian.org/python-team/modules/shiboken/blob/master/debian/control
https://salsa.debian.org/python-team/modules/pyside/blob/master/debian/control

On Fri, 11 May 2018, Dmitry Shachnev wrote:
> It looks like pyside2 will use the same release cycle as Qt uses, so we
> will most likely have to update it together with the other Qt modules.

And at least the version embedded in the code matches the Qt version, yes.

> As far as I know, there are no current pyside 1.x maintainers. So there is
> nobody who can complain about this move.

Indeed.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Re: Bug#877871: RFP: pyside2 -- Python bindings for Qt5

[Raphael Hertzog]

Control: tag -1 pending

Hello all,

we have made good progress on the pyside2 packaging. Yesterday we
had working packages built against Qt 5.10 that we managed to use to
rebuild freecad and the application was working.

We worked in our own repository at the start:
https://salsa.debian.org/freexian-team/pyside2

But I just pushed this to the team's official repository. You are more
than welcome to review the package. The upstream build system is based
on Python's setup.py but it then executes lots of custom code relying on
cmake to build everything.

We use pybuild because it does the right thing to build against the
various Python versions but the upstream installation procedure is not
really able to cope with the logic of building the same thing for
different python versions and then installing the different set of file.

So we just used dh_install (and not pybuild's install procedure) to install
the files out of some intermediate directories used by upstream. We
used dh-exec to be able to install in multi-arch directories via
dh_install.

I hope the package will continue to build once the Qt 5.11 transition is
over, right now it doesn't because unstable is in flux with the transition
that just started. It might build against experimental, I haven't tried.

On Fri, 11 May 2018, Lisandro Damián Nicanor Pérez Meyer wrote:
> It is worth to note that pyside2 will probably use some Qt's private headers.

We do depend on qtbase5-private-dev, right.

> - If Pyside2 uses private headers it will end up depending in qt-abi-x-y-
> z, that's the way we track packages using private headers (which includes qt 
> submodules) and allows us to do very smooth transitions whenever possible. 
> That only means that it will need to get rebuilt whenever we ship a new 
> upstream version.

Some of the generated packages depend on "qtdeclarative-abi-x-y-z". That's
the only occurrence of this pattern.

> All that being said, if the package is kept under qt/ following our repo 
> style 
> it's easier for us to jump in in case it's needed (for example, if we are 

That's definitely the goal here. I have no long term interest here. The
initial packaging of pyside has been funded by a customer who is using
freecad and wanted to keep the package in Debian. We will continue
to help for as long as the customer is willing to pay our work but
we definitely want the package to be under the team's umbrella so that
it survives our efforts.

On Sat, 12 May 2018, Maximiliano Curia wrote:
> I've created: https://salsa.debian.org/qt-kde-team/qt/pyside2

Pushed our work here.

> They are somewhat documented in http://pkg-kde.alioth.debian.org/, I would
> say: http://pkg-kde.alioth.debian.org/gitguidelines.html -> but the tagging

This moved here:
https://qt-kde-team.pages.debian.net/
https://qt-kde-team.pages.debian.net/gitguidelines.html

I honestly find those policies very counter-productive with a high
setup cost and lots of divergence compared to usual practices in most
other teams. Anyway, I can stick to them for this package but right
now I'm maintaining pyside2 with git-buildpackage in a usual
merged-with-upstream branch and I will just cherry-pick my changes
to the debian-only branch pushed to your repository.

BTW, the policy of requiring a changelog entry in each commit goes very
much again the stated goal of "reduce conflicts in debian/changelog when
cherry-picking and merging between branches".

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#657191: kopete: multiple crashes in the wlm protocol code

[Raphael Geissert]

Hi,

On 31 May 2013 14:58, Pali Rohár  wrote:
> Hello Raphael,
>
> are these wlm patches on debian bug #657191 still valid? Btw in
> future, please send kopete patches to kopete-devel mailinglist or
> to kde reviewboard.

Last I checked the bugs were not yet fixed, so I guess they are still valid.

--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caa7hugechqtutdcn4elqv8m+qpkdy2wmopxag6qtztax6ih...@mail.gmail.com

Bug#711317: libkdcraw: CVE-2013-2126: double free

[Raphael Geissert]

Source: libkdcraw
Severity: grave
Tags: security patch

Hi,

There's a double free in the embedded copy of libraw included in your package.
If possible, please use the system copy instead.

For more info:
http://www.openwall.com/lists/oss-security/2013/05/29/7
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710353#17

Could you please prepare fixed packages for oldstable and stable, to
be included in point releases?

Thanks.

Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caa7hughm8xdth3eysx0vks8xqxusozf1j73rym2cbyvkphk...@mail.gmail.com

Re: desktop-base: Integration with KDE's plasma-desktop seems to no longer work with current version

[Raphael Hertzog]

On Tue, 19 Jul 2016, Sune Vuorela wrote:
> > $ cat kde-wallpaper/10-desktop-base.js
> > // Placed in /usr/share/kde4/apps/plasma-desktop/init/
> 
> yeah. that looks kind of old.
> 
> > (This has been identified on a Kali Linux system but I have all the
> > reasons to believe that it also applies to a Debian testing system)
> 
> Without having investigated a single thing, I also have all the reasons to 
> believe it doesn't work in a current Debian testing/unstable Plasma 
> installation.

Unlike the average package, I believe that desktop-base has no active
maintainer that is going to take care of this, it's more one of those
packages where contributors from each desktop team are supposed to handle
things related to their desktop.

So is there anyone from the KDE team who is willing to investigate and
update the required integration? (Or at least provide initial guidance in
this bug report so that others can pick it up)

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Re: desktop-base: Integration with KDE's plasma-desktop seems to no longer work with current version

[Raphael Hertzog]

Hi,

On Wed, 20 Jul 2016, Raphael Hertzog wrote:
> So is there anyone from the KDE team who is willing to investigate and
> update the required integration? (Or at least provide initial guidance in
> this bug report so that others can pick it up)

I looked further into this issue but I quickly got stuck and had to ask
help upstream:
https://mail.kde.org/pipermail/plasma-devel/2016-July/056598.html

I just got two answers which lead me to some possible solutions.

It looks like that the script
/usr/share/plasma/shells/org.kde.plasma.desktop/contents/layout.js is
executed when the user runs plasma for the first time. Unfortunately
that script does not offer any way to run other scripts at the same
time. Maybe we could patch it to allow this... but I don't know how easy
this is.

There's an other solution that we can use though: all scripts in
/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/ are
executed once for each user and they are also executed when plasma runs
for the first time. On the downside, it means that someone who has
customized his wallpaper and that will upgrade desktop-base will have its
wallpaper reset by the update script. Maybe we can improve the script to
detect this case and not do anything in that case... but again I don't
know how to do this right now.

That said I found the correct syntax to get the script working,
you can see this commit in my Kali upload:
http://git.kali.org/gitweb/?p=packages/desktop-base.git;a=commitdiff;h=1d846a74c9f0f78d175514c193890ddd791dbef3

The only other thing that we need to change for Debian is the line

  d[i].writeConfig('Image', 'kali')

that you would change into:

  d[i].writeConfig('Image', 
'file:///usr/share/images/desktop-base/desktop-background')

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#598300: qtcreator: CVE-2010-3374: insecure library loading

[Raphael Geissert]

Package: qtcreator
Version: 1.3.1-2
Severity: grave
Tags: security
User: t...@security.debian.org
Usertags: ldpath

Hello,

During a review of the Debian archive, I've found your package to
contain a script that can be abused by an attacker to execute arbitrary
code.

The vulnerability is introduced by an insecure change to
LD_LIBRARY_PATH, and environment variable used by ld.so(8) to look for
libraries on a directory other than the standard paths.

Vulnerable code follows:

/usr/bin/qtcreator line 34:
LD_LIBRARY_PATH="${libdir}/qtcreator:${LD_LIBRARY_PATH}"

When there's an empty item on the colon-separated list of
LD_LIBRARY_PATH, ld.so treats it as '.' (i.e. CWD/$PWD.)
If the given script is executed from a directory where a potential,
local, attacker can write files to, there's a chance to exploit this
bug.

This vulnerability has been assigned the CVE id CVE-2010-3374. Please make sure
you mention it when fixing. Upstream is already aware of this issue.

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3374
[1] http://security-tracker.debian.org/tracker/CVE-2010-3374

Sincerely,
Raphael Geissert



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1p0ri9-0006t2...@alioth.debian.org

Bug#394144: Fwd: Bug#394144 closed by Eckhart Wörner ()

[Raphael Geissert]

notfixed 394144 1:2.2.1-4
reopen 394144
thanks


> -- Forwarded message --
> From: Eckhart Wörner 
> To: 394144-d...@bugs.debian.org
> Date: Sun, 05 Dec 2010 23:06:45 +0100
> Subject:
> Version: 1:2.2.1-4
>
> No response from the submitter for 4 weeks, closing.

That's not the right way to go. The reproducer is attached to my
original report, if you can open it and see the formulas then it's all
fixed.

-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinwwyr7snr+wj15qr3wpauaf9oxj17xvmreg...@mail.gmail.com

Bug#455689: nspluginviewer crashes since the last update of flash

[Raphael Geissert]

I can confirm the problem.
$ dpkg-query -W konqueror-nsplugins
konqueror-nsplugins 4:3.5.8.dfsg.1-2
$ dpkg-query -W flashplugin-nonfree
flashplugin-nonfree 9.0.115.0.1

I'm attaching the backtrace.

-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb682c6c0 (LWP 28578)]
[New Thread 0xb3a8bb90 (LWP 28583)]
[New Thread 0xb4352b90 (LWP 28582)]
[KCrash handler]
#6  0xb7b9daf7 in XtRemoveTimeOut () from /usr/lib/libXt.so.6
#7  0xb5c79db1 in ?? ()
   from /usr/lib/mozilla-firefox/plugins/libflashplayer.so
#8  0xb5c6f338 in ?? ()
   from /usr/lib/mozilla-firefox/plugins/libflashplayer.so
#9  0xb5c68181 in ?? ()
   from /usr/lib/mozilla-firefox/plugins/libflashplayer.so
#10 0xb5c6c937 in ?? ()
   from /usr/lib/mozilla-firefox/plugins/libflashplayer.so
#11 0x080e2110 in ?? ()
#12 0xbfb3a9c8 in ?? ()
#13 0xbfb3a998 in ?? ()
#14 0xb7b43e41 in operator delete () from /usr/lib/libstdc++.so.6
#15 0x0805b655 in NSPluginInstance::destroy (this=0x80c1f30)
at /tmp/buildd/kdebase-3.5.8.dfsg.1/./nsplugins/viewer/nsplugin.cpp:710
#16 0x0805d7fd in ~NSPluginInstance (this=0x80c1f30)
at /tmp/buildd/kdebase-3.5.8.dfsg.1/./nsplugins/viewer/nsplugin.cpp:672
#17 0xb70d9838 in QGList::remove (this=0x80a6c88, d=0x80c1f30)
at tools/qglist.cpp:542
#18 0x080564cf in NSPluginClass::timer (this=0x80a6bb0)
at /usr/share/qt3/include/qptrlist.h:85
#19 0x08056571 in NSPluginInstance::shutdown (this=0x80c1f30)
at /tmp/buildd/kdebase-3.5.8.dfsg.1/./nsplugins/viewer/nsplugin.cpp:740
#20 0x080592d9 in NSPluginInstanceIface::process (this=0x80c205c, 
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED]) at NSPluginClassIface_skel.cpp:172
#21 0xb72d8f50 in DCOPClient::receive (this=0x80acf38, [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED])
at /build/buildd/kdelibs-3.5.8.dfsg.1/./dcop/dcopclient.cpp:1643
#22 0xb72dd9f4 in DCOPProcessInternal (d=0x809e1e8, opcode=2, key=322, 
[EMAIL PROTECTED], canPost=true)
at /build/buildd/kdelibs-3.5.8.dfsg.1/./dcop/dcopclient.cpp:520
#23 0xb72de3e3 in DCOPProcessMessage (iceConn=0x8099878, 
clientObject=0x809e1e8, opcode=2, length=78, replyWait=0x0, 
replyWaitRet=0xbfb3ae34)
at /build/buildd/kdelibs-3.5.8.dfsg.1/./dcop/dcopclient.cpp:432
#24 0xb72ea7d0 in KDE_IceProcessMessages (iceConn=0x8099878, replyWait=0x0, 
replyReadyRet=0x0)
at /build/buildd/kdelibs-3.5.8.dfsg.1/./dcop/KDE-ICE/process.c:326
#25 0xb72d1356 in DCOPClient::processSocketData (this=0x80acf38, fd=9)
at /build/buildd/kdelibs-3.5.8.dfsg.1/./dcop/dcopclient.cpp:2014
#26 0xb72de0f8 in DCOPClient::qt_invoke (this=0x80acf38, _id=2, _o=0xbfb3afb0)
at ./dcopclient.moc:176
#27 0xb6ddcb10 in QObject::activate_signal (this=0x80ad690, clist=0x80a0e80, 
o=0xbfb3afb0) at kernel/qobject.cpp:2356
#28 0xb6ddd45d in QObject::activate_signal (this=0x80ad690, signal=2, param=9)
at kernel/qobject.cpp:2449
#29 0xb716d40d in QSocketNotifier::activated (this=0x80ad690, t0=9)
at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#30 0xb6dfecda in QSocketNotifier::event (this=0x80ad690, e=0xbfb3b2e8)
at kernel/qsocketnotifier.cpp:258
#31 0xb6d7136a in QApplication::internalNotify (this=0xbfb3b3b4, 
receiver=0x80ad690, e=0xbfb3b2e8) at kernel/qapplication.cpp:2635
#32 0xb6d73193 in QApplication::notify (this=0xbfb3b3b4, receiver=0x80ad690, 
e=0xbfb3b2e8) at kernel/qapplication.cpp:2358
#33 0xb74b8622 in KApplication::notify (this=0xbfb3b3b4, receiver=0x80ad690, 
event=0xbfb3b2e8)
at /build/buildd/kdelibs-3.5.8.dfsg.1/./kdecore/kapplication.cpp:550
#34 0xb6d026c9 in QApplication::sendEvent (receiver=0x80ad690, 
event=0xbfb3b2e8) at ../include/qapplication.h:520
#35 0xb6d631e2 in QEventLoop::activateSocketNotifiers (this=0xbfb3b4d0)
at kernel/qeventloop_unix.cpp:578
#36 0x08055787 in QXtEventLoop::processEvents (this=0xbfb3b4d0, 
flags=)
at /tmp/buildd/kdebase-3.5.8.dfsg.1/./nsplugins/viewer/qxteventloop.cpp:462
#37 0xb6d8c6e4 in QEventLoop::enterLoop (this=0xbfb3b4d0)
at kernel/qeventloop.cpp:198
#38 0xb6d8c3e2 in QEventLoop::exec (this=0xbfb3b4d0)
at kernel/qeventloop.cpp:145
#39 0xb6d72f13 in QApplication::exec (this=0xbfb3b3b4)
at kernel/qapplication.cpp:2758
#40 0x0805a73c in main (argc=134619088, argv=0x0)
at /tmp/buildd/kdebase-3.5.8.dfsg.1/./nsplugins/viewer/viewer.cpp:305

Bug#460809: superkaramba: Please add a Replaces: karamba

[Raphael Geissert]

Package: superkaramba
Version: 4:3.5.8-1
Severity: wishlist

karamba has been removed from unstable some days ago.
In order to make people's life easier it would be nice if 
superkaramba 'Replaces: karamba'.

Sincerely,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html


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

Bug#464999: kdesdk-scripts: bashism in /bin/sh script

[Raphael Geissert]

Package: kdesdk-scripts
Severity: important
Version: 3.5.8-1
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing several /bin/sh scripts making 
use of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/create_svnignore line 28 (trap with signal
> numbers): trap "rm svnignore.tmp" 1 2 15
> possible bashism in ./usr/bin/create_svnignore line 52
> (${parm/?/pat[/str]}): addignore ${ui/.ui/.h}
> possible bashism in ./usr/bin/create_svnignore line 53
> (${parm/?/pat[/str]}): addignore ${ui/.ui/.cpp}
> possible bashism in ./usr/bin/svnaddcurrentdir line 20 (should be 'b = a'):
> if [ "$answer" == "y" ]; then svn add $file; fi
> possible bashism in ./usr/bin/adddebug line 13 (echo -e):
> *) echo -e "Usage: adddebug [-k] [-r] [-n]\n  -k: keep optimizations
> (removed by default)\n  -r: recursive (process all subdirectories)\n  -n:
> compile without NDEBUG and NO_DEBUG being defined (makes kdDebug calls
> work)"; exit 1;;


Not using bash as /bin/sh would lead to errors. Please be aware that although 
bash is currently the default /bin/sh there's a release goal for Lenny to 
make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#465001: kexi: bashism in /bin/sh script

[Raphael Geissert]

Package: kexi
Severity: important
Version: 1.6.3-4
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing several /bin/sh scripts making 
use of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/kexi_add_column_gui line 23 ('function' is
> useless): function setup_messages {
> possible bashism in ./usr/bin/kexi_delete_column line 21 ('function' is
> useless): function usage {
> possible bashism in ./usr/bin/kexi_delete_column line 38 ('function' is
> useless): function exit_with_error {
> possible bashism in ./usr/bin/kexi_delete_column line 45 ('function' is
> useless): function check {
> possible bashism in ./usr/bin/kexi_delete_column line 65 ('function' is
> useless): function prepare_new_create_table_statement {
> possible bashism in ./usr/bin/kexi_delete_column line 82 ('function' is
> useless): function get_sql_column_names {
> possible bashism in ./usr/bin/kexi_delete_column_gui line 23 ('function' is
> useless): function setup_messages {
> possible bashism in ./usr/bin/kexi_add_column line 21 ('function' is
> useless): function usage {
> possible bashism in ./usr/bin/kexi_add_column line 42 ('function' is
> useless): function exit_with_error {
> possible bashism in ./usr/bin/kexi_add_column line 49 ('function' is
> useless): function check {


Not using bash as /bin/sh would lead to errors. Please be aware that although 
bash is currently the default /bin/sh there's a release goal for Lenny to 
make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#473459: juic: bashism in /bin/sh script

[Raphael Geissert]

Package: juic
Severity: important
Version: 3.5.9-1
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing a /bin/sh script making 
use of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/juic line 19 (pushd):
> pushd `dirname ${ls##* }` >/dev/null
> possible bashism in ./usr/bin/juic line 21 (popd):
> popd >/dev/null

Not using bash (or a Debian Policy conformant shell interpreter which doesn't 
provide such an extra feature) as /bin/sh is likely to lead to errors or 
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a 
release goal for Lenny to make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information please refer to the Debian Policy section 10.4 supporting 
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#479377: Can't install kdm in parallel to gdm when using dependency based boot

[Raphael Geissert]

Sune Vuorela wrote:

> On Sunday 04 May 2008 15:59:25 Daniel Hess wrote:
>> Package: kdm
>> Version: 4:3.5.9.dfsg.1-2+b1
>> Severity: important
>>
>> When installing kdm while gdm is already installed insserv fails
> because
>> more than on init-script provides the `x-display-manager' service.
> 
> Hi!  what happens if you install them in the other order?

It won't make a difference.

The problem is that kdm's and gdm's init scripts are 'enabled' (they have
symlinks in rcX.d/); so whenever insserv tries to recalculate the boot
order it finds two init scripts providing the same service.

The way around this issue is removing the rc2.d symlink of either gdm or
kdm, the one that is not going to be used.

I know this is not pretty, but that's how insserv works, as that's the only
information it knows about (send feedback to Petter Reinholdtsen).

> 
> As both gdm and kdm are a display manager, it seems approprate that
> they both provide the service, but my knowledge of insserv is very
> limited. And I don't have a insserv using system.
> 
> /Sune

Cheers,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html




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

Bug#479377: Can't install kdm in parallel to gdm when using dependency based boot

[Raphael Geissert]

Sune Vuorela wrote:

> On Monday 05 May 2008, Daniel Hess wrote:
>> We have had a short discussion on #debian-edu channel on irc. Petter
>> suggested that maybe x-display-manager can be dropped from both.
> 
> Or maybe insserv should accept several providers of the same function?

IMHO insserv should have a hints file, so one can indicate which *dm should
be preferred. In that case insserv could ask the user which one should be
picked via a debconf (or similar) prompt when it finds such a conflict.
And in case it can't ask the user (e.g. non interactive installation) it
could simply not alter the current init scripts order instead of aborting
the installation.

> 
>> When no other packages or init-scripts need a running display-manager
>> this could also be a workaround.
> 
> I don't know how insserv works, but what ensures that all installed
> display manager initscripts are run ?
> (all display managers tests wether they are the default according to the
> debconf conifguration - and if not, the initscripts does nothing)

I believe there's no feasible way to make insserv aware of that
(IANAinsservD/M). But let's see what Peter (CC'ed) says :)

> 
> /Sune
> 

Cheers,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html




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

Bug#480604: ksmserver: bashism in /bin/sh script

[Raphael Geissert]

Package: ksmserver
Severity: important
Version: 4:3.5.9.dfsg.1-2+b1
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing one or more /bin/sh scripts making 
use of bashisms.

checkbashisms' output:
> possible bashism in ./usr/bin/startkde line 344 ($UID should be "id -ru"):
> KDE_SESSION_UID=$UID

Not using bash (or a Debian Policy conformant shell interpreter which does 
provide such an extra feature) as /bin/sh is likely to lead to errors or 
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a 
release goal for Lenny to make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information please refer to the Debian Policy section 10.4 supporting 
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#480603: kexi: bashism in /bin/sh script

[Raphael Geissert]

Package: kexi
Severity: important
Version: 1:1.6.3-5+b1
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing one or more /bin/sh scripts making 
use of bashisms.

checkbashisms' output:
> possible bashism in ./usr/bin/kexi_delete_column_gui line 72 (should be
> '.', not 'source'): 
> column_name=`source $command_file || exit 1` 

Not using bash (or a Debian Policy conformant shell interpreter which does 
provide such an extra feature) as /bin/sh is likely to lead to errors or 
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a 
release goal for Lenny to make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information please refer to the Debian Policy section 10.4 supporting 
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#486038: kdesdk-scripts: bashism in /bin/sh script

[Raphael Geissert]

Package: kdesdk-scripts
Severity: important
Version: 4:3.5.9-1
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing one or more /bin/sh scripts making 
use of bashisms.

checkbashisms' output:
> possible bashism in ./usr/bin/build-progress.sh line 8 (echo -e):
>   echo -ne "\033]0;$1\007"

Not using bash (or a Debian Policy conformant shell interpreter which does 
provide such an extra feature) as /bin/sh is likely to lead to errors or 
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a 
release goal for Lenny to make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information please refer to the Debian Policy section 10.4 supporting 
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Bug#488567: kopete: crashes at startup because of oscar

[Raphael Geissert]

Package: kopete
Version: 4:3.5.9-2

For slightly more than a week kopete sometimes crashes when it starts (not to 
mention that it takes a _while_ to finally appear on the tasks bar, and right 
before it does it, I think, freezes several applications because of DCOP for 
a couple of seconds).

It happens right after a couple of yh! IM conversation windows appear (spam), 
although from the backtrace I can see it is oscar the one causing the crash.

Please tell me if there's anything else I can do to track this down, because 
like I said, it doesn't crash all the time. And IIRC once the main window 
appears it hasn't crashed because of oscar.

Regards,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb60dd6c0 (LWP 4606)]
[KCrash handler]
#6  Connection::rootTask (this=0x8bdcaf0)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/connection.cpp:162
#7  0xb5044853 in Client::qt_invoke (this=0x8bdcaf0, _id=3, _o=0xbf807fc4)
at ./client.moc:626
#8  0xb725df6d in QObject::activate_signal (this=0x8cdead0, clist=0x89f5528, 
o=0xbf807fc4) at kernel/qobject.cpp:2359
#9  0xb725eaed in QObject::activate_signal (this=0x8cdead0, signal=2)
at kernel/qobject.cpp:2328
#10 0xb500e6b9 in Task::finished (this=0x8cdead0) at ./task.moc:88
#11 0xb50356d8 in Task::done (this=0x8cdead0)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/task.cpp:217
#12 0xb5036077 in Task::setSuccess (this=0x8cdead0, code=0, [EMAIL PROTECTED])
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/task.cpp:191
#13 0xb50368ee in StageOneLoginTask::closeTaskFinished (this=0x8cdead0)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/logintask.cpp:98
#14 0xb5036933 in StageOneLoginTask::qt_invoke (this=0x8cdead0, _id=4, 
_o=0xbf808104) at ./logintask.moc:84
#15 0xb725df6d in QObject::activate_signal (this=0x8f46218, clist=0x881fad8, 
o=0xbf808104) at kernel/qobject.cpp:2359
#16 0xb725eaed in QObject::activate_signal (this=0x8f46218, signal=2)
at kernel/qobject.cpp:2328
#17 0xb500e6b9 in Task::finished (this=0x8f46218) at ./task.moc:88
#18 0xb50356d8 in Task::done (this=0x8f46218)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/task.cpp:217
#19 0xb5036077 in Task::setSuccess (this=0x8f46218, code=0, [EMAIL PROTECTED])
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/task.cpp:191
#20 0xb504e843 in CloseConnectionTask::take (this=0x8f46218, 
transfer=0x9e687f8)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/closeconnectiontask.cpp:127
#21 0xb5010462 in Task::take (this=0x8dba920, transfer=0x9e687f8)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/task.cpp:141
#22 0xb5007e01 in Connection::distribute (this=0x88e5640, transfer=0x9e687f8)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/connection.cpp:217
#23 0xb5007e54 in Connection::streamReadyRead (this=0x88e5640)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/connection.cpp:234
#24 0xb502e020 in Connection::qt_invoke (this=0x88e5640, _id=3, _o=0xbf808364)
at ./connection.moc:141
#25 0xb725df6d in QObject::activate_signal (this=0x8f46648, clist=0x91a9c78, 
o=0xbf808364) at kernel/qobject.cpp:2359
#26 0xb725eaed in QObject::activate_signal (this=0x8f46648, signal=4)
at kernel/qobject.cpp:2328
#27 0xb500c08c in Stream::readyRead (this=0x8f46648) at ./stream.moc:103
#28 0xb500c0bd in ClientStream::doReadyRead (this=0x8f46648)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/oscarclientstream.cpp:404
#29 0xb500f73f in ClientStream::cp_incomingData (this=0x8f46648)
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/oscarclientstream.cpp:321
#30 0xb50342eb in ClientStream::qt_invoke (this=0x8f46648, _id=6, 
_o=0xbf808464) at ./oscarclientstream.moc:157
#31 0xb725df6d in QObject::activate_signal (this=0x8b35ee4, clist=0x89bd0b0, 
o=0xbf808464) at kernel/qobject.cpp:2359
#32 0xb725eaed in QObject::activate_signal (this=0x8b35ee4, signal=3)
at kernel/qobject.cpp:2328
#33 0xb500cc0c in CoreProtocol::incomingData (this=0x8b35ee4)
at ./coreprotocol.moc:110
#34 0xb5033f5d in CoreProtocol::wireToTransfer (this=0x8b35ee4, 
[EMAIL PROTECTED])
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/coreprotocol.cpp:226
#35 0xb503409f in CoreProtocol::addIncomingData (this=0x8b35ee4, 
[EMAIL PROTECTED])
at 
/build/buildd/kdenetwork-3.5.9/./kopete/protocols/oscar/liboscar/coreprotocol.cpp:108
#36 0xb50341d9 in ClientStream::bs_readyRead (this=0x8f46648)
at 
/build/buildd/kdenetwork-3.5.9/./kopete

Bug#523748: [kopete] msn protocol disappeared

[Raphael Geissert]

reopen 523748
reassign 523748 kopete,kaboom
retitle 523748 please migrate accounts from the msn to the wlm plugin
thanks

Yesterday a friend of mine, after reading this bug report as I pointed him to, 
asked me if I knew how to migrate his msn accounts to wlm without losing the 
chat logs, meta contacts, etc. It would be great if either kopete or kaboom 
did it (I'd prefer if kopete did it, as it is more or less unrelated to 
kaboom.)

The necessary steps are:
sed -i 's/MSNProtocol/WlmProtocol/g' .kde/share/config/kopeterc 
.kde/share/apps/kopete/contactlist.xml
mv .kde/share/apps/kopete/logs/MSNProtocol 
.kde/share/apps/kopete/logs/WlmProtocol

Although the contact pictures can also be migrated:
(shell code plus some php code to get the raw sha1 hash)
mkdir .kde/share/apps/kopete/wlmpictures
for pic in .kde/share/apps/kopete/msnpictures/*; do
  nn=$(php -nr 'echo str_replace("/", "_", base64_encode(sha1_file("'$pic'", 
true)));')
  mv $pic .kde/share/apps/kopete/wlmpictures/$nn
done

Cheers,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net



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

Bug#530114: kdesdk-scripts: bashism in /bin/sh script

[Raphael Geissert]

Package: kdesdk-scripts
Severity: important
Version: 4:4.2.2-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/build-progress.sh line 8 (echo -e):
>   echo -ne "\033]0;$1\007"
> possible bashism in ./usr/bin/cvsaddcurrentdir line 20 (should be 'b = a'):
> if [ "$answer" == "y" ]; then cvs add $file; fi


Not using bash (or a Debian Policy conformant shell interpreter which doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information supporting this goal please refer to Debian Policy,
section 10.4, at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



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

Bug#530109: kdebase-workspace-bin: bashism in /bin/sh script

[Raphael Geissert]

Package: kdebase-workspace-bin
Severity: important
Version: 4:4.2.2-2
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/startkde line 370 ($UID should be "$(id
> -ru)"):
> KDE_SESSION_UID=$UID


Not using bash (or a Debian Policy conformant shell interpreter which doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information supporting this goal please refer to Debian Policy,
section 10.4, at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



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

Bug#530108: kde-l10n-nn: bashism in /bin/sh script

[Raphael Geissert]

Package: kde-l10n-nn
Severity: important
Version: 4:4.2.2-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.

checkbashisms' output:
> possible bashism in ./usr/share/locale/nn/LC_SCRIPTS/kdelibs4/oppdater.sh
> line 37 (echo -e):
> echo -e '\n\n'
> possible bashism in ./usr/share/locale/nn/LC_SCRIPTS/kdelibs4/oppdater.sh
> line 44 (should be 'b = a'):
>   if [ "$tooold" == 0 ]


Not using bash (or a Debian Policy conformant shell interpreter which doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information supporting this goal please refer to Debian Policy,
section 10.4, at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



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

Bug#530114: kdesdk-scripts: bashism in /bin/sh script

[Raphael Geissert]

Hello maintainer,

Another one.

checkbashisms' output:
> possible bashism in ./usr/bin/cvsaddcurrentdir line 18 (read with option
> other than -r):
> read -p "Add file $file to cvs ? (y/n) " answer rest

Thank you,
Raphael Geissert



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

Bug#530979: kopete: bashism in /bin/sh script

[Raphael Geissert]

Package: kopete
Severity: important
Version: 4:4.2.2-1
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/kopete_latexconvert.sh line 30 (should be
> '.', not 'source'):
> source ~/.tex2imrc


Not using bash (or a Debian Policy conformant shell interpreter which doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information supporting this goal please refer to Debian Policy,
section 10.4, at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



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

Bug#530977: kexi: bashism in /bin/sh script

[Raphael Geissert]

Package: kexi
Severity: important
Version: 1:1.6.3-8
User: debian-rele...@lists.debian.org
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making use
of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/kexi_delete_column_gui line 32 (should be
> '.', not 'source'):
> source "$transl_file"
> possible bashism in ./usr/bin/kexi_delete_column_gui line 41 (should be
> '.', not 'source'):
> if [ -f "$transl_file" ] ; then source "$transl_file"; else
> transl_file=; fi
> possible bashism in ./usr/bin/kexi_add_column_gui line 32 (should be '.',
> not 'source'):
> source "$transl_file"
> possible bashism in ./usr/bin/kexi_add_column_gui line 41 (should be '.',
> not 'source'):
> if [ ! -f "$transl_file" ] ; then   source
> "$transl_file"; else transl_file=; fi


Not using bash (or a Debian Policy conformant shell interpreter which doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html

For more information supporting this goal please refer to Debian Policy,
section 10.4, at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



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

Bug#647683: kdm: preloadkde is executed even if option is commented out

[Raphael Geissert]

Package: kdm
Version: 4:4.6.5-2
Forwarded: https://bugs.kde.org/show_bug.cgi?id=277521

Hi,

I noticed and reported to upstream that kdm was executing preloadkde even if 
Preloader is commented out in kdmrc.

As you can read in the upstream bug report the use of genkdmrc is causing this 
unexpected behaviour. From what Oswald Buddenhagen says it seems that the use 
of genkdmrc, it could be possible that other "unexpected" changes are made 
(either now or in the future.)

I don't know what the reason for using genkdmrc is, but this bug seems like it 
was introduced by the Debian packaging. Please fix it.

Thanks in advance.

Regards,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20050148.28446.geiss...@debian.org

Bug#657191: kopete: multiple crashes in the wlm protocol code

[Raphael Geissert]

Package: kopete
Version: 4:4.6.5-3
Severity: important
Tags: patch upstream

Hi,

There are a few recently-introduced bugs in the wlm protocol support code in 
kopete. I'm not reporting this bug to upstream's bugzilla because it will get 
ignored like my other reports and somebody will eventually notice the bug (but 
never the bug report) and write another patch and fix it.

So, attached are three patches, each explaining what they fix. Only the first 
one is not a crash bug, but it prevents the creation of connections that will 
never be used by kopete.

P.S. back when I wrote the patches all the bugs were still present in the 
latest version in the VCS.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
From 1670f6607c5c688aa3a89cdb5aba903cf95529f2 Mon Sep 17 00:00:00 2001
From: Raphael Geissert 
Date: Wed, 2 Nov 2011 19:38:21 -0600
Subject: [PATCH 1/3] Avoid multiple switchboard requests while waiting for one to finish

If the user attempts to send more than one message a new sb is requested
every time unless we received one in the mean time and the other client
has already joined. Those extra switchboard connections could be left
unused and hanging around until terminated by an event.
---
 wlmchatsession.cpp |9 -
 wlmchatsession.h   |1 +
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/wlmchatsession.cpp b/wlmchatsession.cpp
index 0dfdd71..0c75f34 100644
--- a/wlmchatsession.cpp
+++ b/wlmchatsession.cpp
@@ -75,6 +75,7 @@ Kopete::ChatSession (user, others, protocol),
 m_chatService (conn),
 m_downloadDisplayPicture (false),
 m_sendNudge (false),
+m_chatServiceRequested (false),
 m_tries (0),
 m_oimid (1),
 m_sessionID(1)
@@ -893,7 +894,7 @@ WlmChatSession::requestChatService ()
 WlmProtocol::protocol ()->wlmOffline)
 return false;
 
-if (!isReady () && account ()->isConnected () && !isConnecting ())
+if (!isReady () && account ()->isConnected () && !isConnecting () && !m_chatServiceRequested)
 {
 const std::string rcpt_ = members().first()->contactId().toLatin1().constData();
 const std::string msg_ = "";
@@ -901,6 +902,10 @@ WlmChatSession::requestChatService ()
 // request a new switchboard connection
 static_cast (account ())->server ()->cb.mainConnection->requestSwitchboardConnection (ctx);
 QTimer::singleShot (30 * 1000, this, SLOT (switchboardConnectionTimeout ()));
+// if the user attempts to send more than one message a new sb
+// is requested every time unless we received one in the mean
+// time and the other client has already joined
+m_chatServiceRequested = true;
 return true;
 }
 // probably we are about to connect
@@ -912,6 +917,8 @@ WlmChatSession::switchboardConnectionTimeout ()
 {
 if (!isReady ())
 {
+// allow a new chat service request
+m_chatServiceRequested = false;
 // try 3 times
 if (m_tries < 3)
 {
diff --git a/wlmchatsession.h b/wlmchatsession.h
index 91c4b83..3480c65 100644
--- a/wlmchatsession.h
+++ b/wlmchatsession.h
@@ -110,6 +110,7 @@ class WlmChatSession: public Kopete::ChatSession
 MSN::SwitchboardServerConnection * m_chatService;
 bool m_downloadDisplayPicture;
 bool m_sendNudge;
+bool m_chatServiceRequested;
 int m_tries;
 int m_oimid;
 int m_sessionID;
-- 
1.7.4.1

From 47aa25082f487a137889deeb2d3dada89282f41d Mon Sep 17 00:00:00 2001
From: Raphael Geissert 
Date: Fri, 4 Nov 2011 14:54:38 -0600
Subject: [PATCH 2/3] Fix a crash when receiving a custom emoticon

The mutable iterator needs to be destroyed before the connection is
removed from the pendingMessages map.
---
 wlmchatmanager.cpp |   16 +---
 1 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/wlmchatmanager.cpp b/wlmchatmanager.cpp
index 5444a50..4b202c2 100644
--- a/wlmchatmanager.cpp
+++ b/wlmchatmanager.cpp
@@ -618,15 +618,17 @@ WlmChatManager::slotGotEmoticonFile(MSN::SwitchboardServerConnection * conn,
 if(pendingMessages.value(conn).isEmpty())
 return;
 
-QMutableLinkedListIterator it(pendingMessages[conn]);
-while (it.hasNext())
 {
-PendingMessage pendingMsg = it.next();
-if (fillEmoticons(chat, pendingMsg.message))
+QMutableLinkedListIterator it(pendingMessages[conn]);
+while (it.hasNext())
 {
-chat->appendMessage(*pendingMsg.message);
-it.remove();
-delete pendingMsg.message;
+PendingMessage pendingMsg = it.next();
+if (fillEmoticons(chat, pendingMsg.message))
+{
+chat->appendMessage(*pendingMsg.message);
+it.remove();
+delete pendingMsg.message;
+}
 }
 }
 
-- 
1.7.4.1

From 628a622bf5498ae8c325abb61e6c3f75483af2fb Mon Sep 17 00:00:00 

Bug#532585: konqueror: please add dependency on install-info

[Raphael Hertzog]

On Sun, 21 Jun 2009, Sune Vuorela wrote:
> Please also make sure that kdebase takes quite some time to build on most 
> architectures, so uploading it just for a fix of a bug of severity: normal is 
> often a waste of everybodys time.

The bug will be serious as soon as we upload dpkg with the Breaks: field
against all info-browsers that do not depend on install-info.

Currently i have put Breaks: konqueror (<< 4:4.2.4-2) so please ensure
next upload has the dependency. And do not wait too long, please.

See http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo for details.

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/



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

Bug#565193: knode segfault

[Raphael Geissert]

Package: knode
Version: 4:4.3.4-1

Hi,

After clicking on "stop network" while a group is still being loaded
and switching to another group knode crashes.
Here's the backtrace:

Application: KNode (knode), signal: Segmentation fault
[KCrash Handler]
#6  0x in ?? ()
#7  0xb7433541 in KNJobData::cancel (this=0x95d74a0) at
../../knode/knjobdata.cpp:109
#8  0xb7431d11 in KNode::Scheduler::cancelJobs (this=0x8399018,
type=0, item=0x0) at ../../knode/scheduler.cpp:160
#9  0xb74c2757 in KNMainWidget::slotNetCancel (this=0x829e060) at
../../knode/knmainwidget.cpp:1971
#10 0xb74c4851 in KNMainWidget::qt_metacall (this=0x829e060,
_c=QMetaObject::InvokeMetaMethod, _id=85, _a=0xbfecf87c) at
./knmainwidget.moc:293
#11 0xb6c6f303 in QMetaObject::activate (sender=0x84eb078,
from_signal_index=5, to_signal_index=6, argv=0xbfecf87c) at
kernel/qobject.cpp:3112
#12 0xb6c6f720 in QMetaObject::activate (sender=0x84eb078,
m=0xb6af21c8, from_local_signal_index=1, to_local_signal_index=2,
argv=0xbfecf87c) at kernel/qobject.cpp:3206
#13 0xb6293591 in QAction::triggered (this=0x84eb078, _t1=false) at
.moc/release-shared/moc_qaction.cpp:236
#14 0xb6294adf in QAction::activate (this=0x84eb078,
event=QAction::Trigger) at kernel/qaction.cpp:1167
#15 0xb672d012 in QAction::trigger (this=0x861dc0c) at
../../include/QtGui/../../src/gui/kernel/qaction.h:203
#16 QToolButton::nextCheckState (this=0x861dc0c) at widgets/qtoolbutton.cpp:1135
#17 0xb6648543 in QAbstractButtonPrivate::click (this=0x859f840) at
widgets/qabstractbutton.cpp:525
#18 0xb6648816 in QAbstractButton::mouseReleaseEvent (this=0x8451fa0,
e=0xbfecff4c) at widgets/qabstractbutton.cpp:1115
#19 0xb672d50c in QToolButton::mouseReleaseEvent (this=0x8451fa0,
e=0xbfecff4c) at widgets/qtoolbutton.cpp:709
#20 0xb62ef9fb in QWidget::event (this=0x8451fa0, event=0xbfecff4c) at
kernel/qwidget.cpp:7554
#21 0xb66467fe in QAbstractButton::event (this=0x8451fa0,
e=0xbfecff4c) at widgets/qabstractbutton.cpp:1077
#22 0xb672feba in QToolButton::event (this=0x8451fa0,
event=0xbfecff4c) at widgets/qtoolbutton.cpp:1151
#23 0xb6299a94 in QApplicationPrivate::notify_helper (this=0x8154a70,
receiver=0x8451fa0, e=0xbfecff4c) at kernel/qapplication.cpp:4065
#24 0xb62a2551 in QApplication::notify (this=0xbfed17b4,
receiver=0x8451fa0, e=0xbfecff4c) at kernel/qapplication.cpp:3767
#25 0xb6f1f62d in KApplication::notify (this=0xbfed17b4,
receiver=0x8451fa0, event=0xbfecff4c) at
../../kdeui/kernel/kapplication.cpp:302
#26 0xb6c5a1eb in QCoreApplication::notifyInternal (this=0xbfed17b4,
receiver=0x8451fa0, event=0xbfecff4c) at
kernel/qcoreapplication.cpp:610
#27 0xb62a15de in QCoreApplication::sendSpontaneousEvent
(receiver=0x8451fa0, event=0xbfecff4c, alienWidget=0x8451fa0,
nativeWidget=0x856dfd8, buttonDown=0xb6b10580, lastMouseReceiver=...)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#28 QApplicationPrivate::sendMouseEvent (receiver=0x8451fa0,
event=0xbfecff4c, alienWidget=0x8451fa0, nativeWidget=0x856dfd8,
buttonDown=0xb6b10580, lastMouseReceiver=...)
at kernel/qapplication.cpp:2924
#29 0xb6310175 in QETWidget::translateMouseEvent (this=0x856dfd8,
event=0xbfed14fc) at kernel/qapplication_x11.cpp:4411
#30 0xb630f646 in QApplication::x11ProcessEvent (this=0xbfed17b4,
event=0xbfed14fc) at kernel/qapplication_x11.cpp:3430
#31 0xb6339bc2 in x11EventSourceDispatch (s=0x8157840, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#32 0xb48d7f28 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0xb48db6b3 in ?? () from /lib/libglib-2.0.so.0
#34 0xb48db838 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0xb6c85041 in QEventDispatcherGlib::processEvents (this=0x81346e8,
flags=...) at kernel/qeventdispatcher_glib.cpp:407
#36 0xb6339305 in QGuiEventDispatcherGlib::processEvents
(this=0x81346e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#37 0xb6c5883a in QEventLoop::processEvents (this=0xbfed1760,
flags=...) at kernel/qeventloop.cpp:149
#38 0xb6c58c82 in QEventLoop::exec (this=0xbfed1760, flags=...) at
kernel/qeventloop.cpp:201
#39 0xb6c5b0d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#40 0xb6299917 in QApplication::exec () at kernel/qapplication.cpp:3525
#41 0x0804e93b in main (argc=1, argv=0xbfed18a4) at ../../knode/main.cpp:41

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



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

Raphael

[Raphael Bowman]

Good afternoon,
Bowman
Bye



Bowman
Bowman
Bowman
Bowman
Bowman
Bowman
Bowman
Bowman
Bowman
Bowman


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

Bug#398735: ktouch: Many keyboard layouts missing

[Raphael Hertzog]

Package: ktouch
Version: Many keyboard layouts missing
Severity: important

The latest upstream release, rather than fixing the allegedly broken
keyboard layouts, simply removed them from the build process (see
keyboard_DATA in ./kdeedu-3.5.5/ktouch/keyboards/Makefile.in and
corresponding ChangeLog entry).

As a result, ktouch is not usable on severak keyboard layout including
french, which is not broken in Debian's kdeedu since you applied a
specific patch (see #347850).

I suggest sending this patch upstream so that it can be reenabled.
Furthermore with etch to be released soon, I'd rather have a keyboard
layout with some wrong colors rather than nothing.

Of course, if they can be fixed in time it's even better.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)


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

Re: [Bug 233674] kipi-plugins: unknown-locale-code hne i8n

[Raphael Geissert]

Mark Purcell wrote:

> On Friday 09 April 2010 08:30:14 Albert Astals Cid wrote:
>> hm? eh? what? why would we remove a perfectly valid translation to a
>> language spoken by 11 million people?
> 
> Albert,
> 
> I don't think the issue is the removal of the translations, rather the
> fact that the locale-code hne isn't defined in ISO 639-1 & ISO 639-2.
> 
> My reading of Chhattisgarhi_language[1] shows that the ISO 639-3 code is
> "hne", whilst the ISO 639-2 code for this family is "inc".
> 
> I am raising this as an inconsistency. If we are accepting ISO 639-3
> locales then that is fine too and we will fix lintian.
> 

Right, but the first faulty package is isoquery. The isoquery program is not 
able to display the ISO 639-3 codes:
> TODO for Isoquery
> =
> 
> - allow use of ISO 639-3

The reason I assume is that there's no (given the nature of the ISO 639-3 
standard) translation table between ISO 639-3 and ISO 639-2 codes.

So I guess the most we can do is just inject the 639-3 codes and hope for 
the best (i.e. hope people is going to use the best and most appropriate ISO 
639-1..3 code.)

Sorry for not noticing ISO 639-3 codes were being used back when I 
implemented the checks. I verified some of the cases that would trigger the 
warning but they were all true positives.

And like Russ said, switching to the "inc" code would be incorrect.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bbe9167.9f15f10a.4bd2.2...@mx.google.com

Re: [Bug 233674] kipi-plugins: unknown-locale-code hne i8n

[Raphael Geissert]

On 9 April 2010 00:16, Christian PERRIER  wrote:
> Jumping in that thread (you would have guessed I would, right? :-))
>

:-)

> There are even some locales that correspond to *no* ISO-639-3 code
> /usr/share/i18n/locales/ber_DZ: Berber (Algeria)
> /usr/share/i18n/locales/ber_MA: Berber (Morocco)

(for lintian's current purposes, the country code is ignored; FWIW)

> Maybe, if possible, check that a locale exists for the said language.
>
> We can quite safely assume that, if a locale exists with a given
> ISO-639-3 code, then it has been carefully though by glibc maintainers
> (either upstream or Debian/Ubuntu maintainers).

I considered using /usr/share/i18n/SUPPORTED as the source of
information but it is far from being complete.

> So, maybe lintian could check that, if foo_BAR.po file exists in a
> package, there is at least one foo_* file in /usr/share/i18n/locales

Am I missing something or wouldn't adding the 639-3 codes to the list
of known and valid codes be enough?

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/y2he9fb436d1004082325m81f94ec3qf0a5d78f65bc6...@mail.gmail.com

Re: [Bug 233674] kipi-plugins: unknown-locale-code hne i8n

[Raphael Geissert]

, if I compare that list with the codes of ISO 639-1..3
(excluding anything after [...@_.-] -- similar to lintian's check):

Locale 'bist' is not supported
Locale 'C' is not supported
Locale 'cn' is not supported
Locale 'cz' is not supported
Locale 'dk' is not supported
Locale 'gr' is not supported
Locale 'jp' is not supported
Locale 'malkovich' is not supported
Locale 'md' is not supported
Locale 'pseudo' is not supported
Locale 'racv' is not supported
Locale 'sh' is not supported
Locale 'sp' is not supported
Locale 'ua' is not supported
Locale 'x' is not supported
Locale 'xx' is not supported
Total: 16

So, we have 67 - 16 = 51 locales that are not supported by glibc but
that we ship translations for. Great.

Something needs to be done.

> I'm not sure, though, that it is really a good idea to check PO files
> against supported locales, for "upstream" translations (ie non-debconf
> ones) with lintian. The only case where it's relevant to lintian,
> imho, is the case where the package is native (so "upstream" is
> Debian).

In fact, what lintian checks is the name of subdirectories of
/usr/share/locale. It doesn't check po files.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/r2oe9fb436d1004091421s95ac736auf160598d124af...@mail.gmail.com

Bug#582463: kdebase-runtime: nepomukserver is started even if disabled in systemsettings

[Raphael Geissert]

Package: kdebase-runtime
Version: 4:4.4.3-1

Hi,

Even if the "Enable Nepomuk Semantic Desktop" checkbox in systemsettings is 
unchecked, nepomukserver is started after login.


Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201818.41007.geiss...@debian.org

Bug#582464: kmail: composer window freezes when trying to send an email without akonadi

[Raphael Geissert]

Package: kmail
Version:4:4.4.3-1

Hi,

If no akonadi resource exists and akonadi is not running either, kmail's email 
composer window freezes when trying to send an email.

Whenever that happens, one  has to kill kmail, losing the email draft.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201824.54790.geiss...@debian.org

Bug#582465: plasma-desktop: plasma-desktop crashes when upgrading to 4:4.4.3-1 while logged in

[Raphael Geissert]

Package: plasma-desktop
Version: 4:4.3.4-5

Hi,

When upgrading to version 4:4.4.3-1 while a user is logged in, the plasma-
desktop process crashes. Any attempt to bring it back is futile as the 
libraries it needs are gone by then.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201830.38969.geiss...@debian.org

Bug#582466: kde-window-manager: kwin crashes when upgrading to 4:4.4.3-1 while logged in

[Raphael Geissert]

Package: kde-window-manager
Version: 4:4.3.4-5

Hi,

When upgrading to version 4:4.4.3-1 while a user is logged in, the kwin 
process crashes. Any attempt to bring it back is futile as the libraries it 
needs are gone by then.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201830.37499.geiss...@debian.org

Bug#582467: kdebase-workspace-bin: krunner's window has black corners if compositing is disabled

[Raphael Geissert]

Package: kdebase-workspace-bin
Version: 4:4.4.3-1
Severity: minor

Hi,

If compositing is disabled, krunner's window has black, square, corners, 
instead of being round. It was fine with 4.3.

This happens, at least, when using the Oxygen style with the Air theme.

Attached is a portion of a screenshot where the bug is visible.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
<>

Bug#582468: kopete: window is not focused when "restoring" it via the systray icon

[Raphael Geissert]

Package: kopete
Version: 4:4.4.3-2
Severity: minor

Hi,

If the main (contacts list) window is hidden (e.g. by clicking on the systray 
icon,) another window is on focus, and kopete's systray icon is clicked, the 
window is "restored" but without focus.

It is annoying when one just wants to take a look at who's online and later 
alt+f4 the window but you end up accidentally closing some other window.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201901.20286.geiss...@debian.org

Bug#582469: kopete: statistics plugin makes kopete freeze at startup

[Raphael Geissert]

Package: kopete
Version: 4:4.4.3-2

Hi,

Kopete freezes (some sort of infinite loop in one of the sub-processes it
seems) during startup making it consume all the CPU resources of one
core if the statistics plugin is enabled.

The strace goes like this:

stat64(".../.kde/share/apps/kopete/kopete_statistics-0.1.db", 
{st_mode=S_IFREG|0644, st_size=14167040, ...}) = 0
open(".../.kde/share/apps/kopete/kopete_statistics-0.1.db", O_RDWR|O_CREAT|
O_LARGEFILE, 0644) = 13
fcntl64(13, F_GETFD)  = 0
fcntl64(13, F_SETFD, FD_CLOEXEC)  = 0
fstat64(13, {st_mode=S_IFREG|0644, st_size=14167040, ...}) = 0
dup(13)   = 14
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=1}, 
0xbffb9e40) = 0
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|
MAP_STACK, -1, 0) = 0xb07e7000
mprotect(0xb07e7000, 4096, PROT_NONE) = 0
clone(child_stack=0xb0fe7454, flags=CLONE_VM|CLONE_FS|CLONE_FILES|
CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|
CLONE_PARENT_SET
TID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb0fe7bd8, {entry_number:6, 
base_addr:0xb0fe7b70, limit:1048575, seg_32bit:1, contents:0, read_exec_o
nly:0, limit_in_pages:1, seg_not_present:0, useable:1}, 
child_tidptr=0xb0fe7bd8) = 13742
futex(0xb0fe7bd8, FUTEX_WAIT, 13742, NULL 
13742 set_robust_list(0xb0fe7be0, 0xc)  = 0
13742 fcntl64(14, F_GETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=1, 
pid=0}) = 0
13742 _exit(0)  = ?
<... futex resumed> ) = 0
close(14) = 0
_llseek(13, 0, [0], SEEK_SET) = 0
read(13, "SQLite format 3\0\4\0\1\1\0@  \0\3\221\260\0\0\0\0"..., 100) = 100
times({tms_utime=414, tms_stime=32, tms_cutime=0, tms_cstime=0}) = 1719009302
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb99f8) = 0
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741826, 
len=510}, 0xbffb99f8) = 0
fcntl64(13, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb99f8) = 0
access(".../.kde/share/apps/kopete/kopete_statistics-0.1.db-journal", F_OK) = 
-1 ENOENT (No such file or directory)
fstat64(13, {st_mode=S_IFREG|0644, st_size=14167040, ...}) = 0
_llseek(13, 0, [0], SEEK_SET) = 0
read(13, "SQLite format 3\0\4\0\1\1\0@  \0\3\221\260\0\0\0\0"..., 1024) = 1024
fcntl64(13, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 
0xbffb9488) = 0
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb9a98) = 0
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741826, 
len=510}, 0xbffb9a98) = 0
fcntl64(13, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb9a98) = 0
access(".../.kde/share/apps/kopete/kopete_statistics-0.1.db-journal", F_OK) = 
-1 ENOENT (No such file or directory)
fstat64(13, {st_mode=S_IFREG|0644, st_size=14167040, ...}) = 0
_llseek(13, 24, [24], SEEK_SET)   = 0
read(13, "\0\3\221\260\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 16
fcntl64(13, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 
0xbffb9af8) = 0
gettimeofday({1274147326, 241579}, NULL) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1604, ...}) = 0
times({tms_utime=414, tms_stime=32, tms_cutime=0, tms_cstime=0}) = 1719009302
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb9918) = 0
fcntl64(13, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741826, 
len=510}, 0xbffb9918) = 0
fcntl64(13, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=1073741824, 
len=1}, 0xbffb9918) = 0
access(".../.kde/share/apps/kopete/kopete_statistics-0.1.db-journal", F_OK) = 
-1 ENOENT (No such file or directory)
fstat64(13, {st_mode=S_IFREG|0644, st_size=14167040, ...}) = 0
_llseek(13, 24, [24], SEEK_SET)   = 0
read(13, "\0\3\221\260\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 16
_llseek(13, 3072, [3072], SEEK_SET) = 0
read(13, ..., 1024) = 1024

And then it starts read(2)ing and _llseek(2)ing over and over again (the
offsets passed to _llseek(2) _do_ change from call to call).

I've removed the pid from the lines of the same process to make it a bit
more readable (same goes to the path.)

Removing the existing database doesn't help.

The only workaround is disabling the plugin by editing the config file
with an editor because the main window never comes up.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005201902.29227.geiss...@debian.org

Bug#582464: kmail: composer window freezes when trying to send an email without akonadi

[Raphael Geissert]

On Friday 21 May 2010 01:39:14 Sune Vuorela wrote:
> 
> "System is broken so stuff doesn't work". No bugs in kmail here.

So, if akonadi dies and is later unable to start (and you can't deny there 
have not been such reports,) I can't even assume the email draft is saved?

The GUI was being redraw/refreshed but none of the buttons nor any other GUI 
element/widget was working. That means that at least one thread was alive and 
it could have saved a backup of the draft.

Shall I reopen (and retitle if you wish) the br then?

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005210938.58474.geiss...@debian.org

Bug#582465: plasma-desktop: plasma-desktop crashes when upgrading to 4:4.4.3-1 while logged in

[Raphael Geissert]

On Friday 21 May 2010 01:43:05 Modestas Vainius wrote:
> Hello,
> 
> On penktadienis 21 Gegužė 2010 02:30:38 Raphael Geissert wrote:
> > When upgrading to version 4:4.4.3-1 while a user is logged in, the
> > plasma- desktop process crashes. Any attempt to bring it back is futile
> > as the libraries it needs are gone by then.
> 
> Upgrades (especially major) when KDE is running are not supported upstream.
> If nothing crashes, it is pure luck. I don't understand how can you except
> something different.

I refuse to believe that. How are non-technical users supposed to upgrade 
then?
You may say a smart upgrade manager should be used so that it installs the 
major version once all users are logged out if you wish, but it doesn't exist 
yet.

No surprise Debian and Ubuntu use GNOME by default.

Regards,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005210947.40349.geiss...@debian.org

Bug#582469: kopete: statistics plugin makes kopete freeze at startup

[Raphael Geissert]

On Friday 21 May 2010 00:58:56 Sune Vuorela wrote:
> Please provide the same system information as if you had filed the bug
> report with reportbug.
> Especially the installation status of libqt4-sql*

Sorry for that, here it is:

Versions of packages kopete depends on:
ii  kdebase-runtime 4:4.4.3-1runtime components from the offici
ii  kdepim-runtime  4:4.4.3-1Runtime components for akonadi-
kde
ii  libc6   2.10.2-6 Embedded GNU C Library: Shared 
lib
ii  libexpat1   2.0.1-7  XML parsing C library - runtime 
li
ii  libgadu31:1.9.0~rc2-1Gadu-Gadu protocol library - 
runti
ii  libgif4 4.1.6-9  library for GIF images (library)
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libidn111.15-2   GNU Libidn library, 
implementation
ii  libkabc44:4.4.3-1library for handling address book
ii  libkde3support4 4:4.4.3-1the KDE 3 Support Library for the
ii  libkdecore5 4:4.4.3-1the KDE Platform Core Library
ii  libkdeui5   4:4.4.3-1the KDE Platform User Interface 
Li
ii  libkdnssd4  4:4.4.3-1the DNS-SD Protocol Library for 
th
ii  libkhtml5   4:4.4.3-1the KHTML Web Content Rendering 
En
ii  libkio5 4:4.4.3-1the Network-enabled File 
Managemen
ii  libkmime4   4:4.4.3-1library for handling MIME data
ii  libknewstuff2-4 4:4.4.3-1the "Get Hot New Stuff" v2 Library
ii  libknotifyconfig4   4:4.4.3-1library for configuring KDE Notifi
ii  libkopete4  4:4.4.3-2main Kopete library
ii  libkparts4  4:4.4.3-1the Framework for the KDE 
Platform
ii  libkpimidentities4  4:4.4.3-1library for managing user 
identiti
ii  libkutils4  4:4.4.3-1various utility classes for the 
KD
ii  libmeanwhile1   1.0.2-3  open implementation of the Lotus 
S
ii  libmediastreamer0   3.2.1-2  linphone web phone's media 
library
ii  libmsn0.3   4.1-1.2  high-level C++ library for MSN 
Mes
ii  libortp83.2.1-2  Real-time Transport Protocol 
stack
ii  libotr2 3.2.0-2  Off-the-Record Messaging library
ii  libphonon4  4:4.6.0really4.4.1-2 the core library of the Phonon 
mul
ii  libqca2 2.0.2-1  libraries for the Qt 
Cryptographic
ii  libqimageblitz4 1:0.0.4-4QImageBlitz image effects library
ii  libqt4-dbus 4:4.6.2-4Qt 4 D-Bus module
ii  libqt4-network  4:4.6.2-4Qt 4 network module
ii  libqt4-qt3support   4:4.6.2-4Qt 3 compatibility library for Qt
ii  libqt4-sql  4:4.6.2-4Qt 4 SQL module
ii  libqt4-xml  4:4.6.2-4Qt 4 XML module
ii  libqtcore4  4:4.6.2-4Qt 4 core module
ii  libqtgui4   4:4.6.2-4Qt 4 GUI module
ii  libsolid4   4:4.4.3-1Solid Library for KDE Platform
ii  libssl0.9.8 0.9.8n-1 SSL shared libraries
ii  libstdc++6  4.4.4-1  The GNU Standard C++ Library v3
ii  libv4l-00.6.4-1  Collection of video4linux support
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxml2 2.7.7.dfsg-2 GNOME XML library
ii  libxslt1.1  1.1.26-3 XSLT processing library - runtime
ii  phonon  4:4.6.0really4.4.1-2 metapackage for the Phonon 
multime
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages kopete recommends:
ii  libqca2-plugin-ossl   0.1~20070904-4 QCA OSSL plugin for libqca2
ii  libqt4-sql-sqlite 4:4.6.2-4  Qt 4 SQLite 3 database driver

Versions of packages kopete suggests:
ii  kdeartwork-emoticons  4:4.4.3-1  emoticon collections for KDE chat
ii  khelpcenter4  4:4.4.3-1  Help Center for KDE 4
pn  texlive-latex-base (no description available)

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005210943.56452.geiss...@debian.org

Bug#583904: krunner: segfault after waiting for matches to be displayed and after lunching an app

[Raphael Geissert]

g12-0  1.2.43-1 PNG library - runtime
ii  libprocesscore4a4:4.4.3-1library for ksysguard based proces
ii  libprocessui4a  4:4.4.3-1library for ksysguard process user
ii  libqimageblitz4 1:0.0.4-4QImageBlitz image effects library
ii  libqt4-dbus 4:4.6.2-4Qt 4 D-Bus module
ii  libqt4-network  4:4.6.2-4Qt 4 network module
ii  libqt4-qt3support   4:4.6.2-4Qt 3 compatibility library for Qt
ii  libqt4-script   4:4.6.2-4Qt 4 script module
ii  libqt4-sql  4:4.6.2-4Qt 4 SQL module
ii  libqt4-xml  4:4.6.2-4Qt 4 XML module
ii  libqtcore4  4:4.6.2-4Qt 4 core module
ii  libqtgui4   4:4.6.2-4Qt 4 GUI module
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libsolid4   4:4.4.3-2Solid Library for KDE Platform
ii  libsolidcontrol44:4.4.3-1library for Solid based network ma
ii  libsolidcontrolifac 4:4.4.3-1library for Solid based network in
ii  libsoprano4 2.4.3+dfsg.1-1   libraries for the Soprano RDF fram
ii  libstdc++6  4.4.4-1  The GNU Standard C++ Library v3
ii  libstreamanalyzer0  0.7.2-1  streamanalyzer library for Strigi
ii  libusb-0.1-42:0.1.12-14  userspace USB programming library
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxau6 1:1.0.5-2X11 authorisation library
ii  libxcursor1 1:1.1.10-2   X cursor management library
ii  libxext62:1.1.1-3X11 miscellaneous extension librar
ii  libxfixes3  1:4.0.4-2X11 miscellaneous 'fixes' extensio
ii  libxft2 2.1.14-2 FreeType-based font drawing librar
ii  libxi6  2:1.3-4  X11 Input extension library
ii  libxinerama12:1.1-3  X11 Xinerama extension library
ii  libxklavier16   5.0-2X Keyboard Extension high-level AP
ii  libxrandr2  2:1.3.0-3X11 RandR extension library
ii  libxrender1 1:0.9.5-2X Rendering Extension client libra
ii  libxss1 1:1.2.0-2X11 Screen Saver extension library
ii  libxtst62:1.1.0-2X11 Testing -- Resource extension
ii  phonon  4:4.6.0really4.4.1-2 metapackage for the Phonon multime
ii  plasma-desktop  4:4.4.3-1The KDE Plasma workspace for deskt
ii  x11-utils   7.5+3X11 utilities
ii  x11-xserver-utils   7.5+1+b1 X server utilities

Versions of packages kdebase-workspace-bin recommends:
pn  plasma-scriptengines   (no description available)
pn  polkit-kde-1 | policykit-1-gn  (no description available)

Versions of packages kdebase-workspace-bin suggests:
ii  x11-xkb-utils 7.5+2  X11 XKB utilities

-- no debconf information

P.S. the -dbg package could probably depend on libglib2.0-0-dbg.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005310924.35919.geiss...@debian.org

Bug#587711: libqt4-network: infinite loop in QSslSocketBackendPrivate::transmit()

[Raphael Geissert]

Package: libqt4-network
Version: 4:4.6.3-1
Severity: grave
Tags: security

Hi,

The following vulnerability has been reported in libqt4-network.

From [1]:
> The part of the network library which handles the SSL connection can be
> tricked into an endless loop that freezes the whole application with
> CPU at 100%.
> 
> The problem is located in the QSslSocketBackendPrivate::transmit()
> function in src_network_ssl_qsslsocket_openssl.cpp that never exits
> from the main "while" loop.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry, if one is assigned by then.

There's no known patch at the moment and an exploit is linked by the advisory.

[1]http://aluigi.altervista.org/adv/qtsslame-adv.txt

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201006302108.24939.geiss...@debian.org

Bug#951041: further test case for menu not working

[Raphael Langerhorst (GRACETECH e.U.)]

Opening the upper right menu after login and choosing Refresh Desktop
results in the same behaviour (the menu does not open anymore), maybe this
is one of the shortest ways to test.