Bug#557512: oxygen-icon-theme: At 16x16, icon actions/page-zoom looks the same as actions/zoom-out

2009-11-22 Thread Michael G. Hansen
Package: oxygen-icon-theme
Version: 4:4.3.2-1
Severity: normal

Look at /usr/share/icons/oxygen/16x16/actions/page-zoom.png and 
/usr/share/icons/oxygen/16x16/actions/zoom-out.png, they look the same. At 
other sizes, they do not.

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

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

-- no debconf information



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



Bug#557555: [Qt] Qt applications don't heed global QT_IM_MODULE

2009-11-22 Thread Kai Wasserbäch
Package: libqtcore4
Version: 4:4.5.3-4
Severity: normal

Dear Qt maintainers,
I've recently installed Debian for somebody needing support for entering
traditional Chinese characters. I chose iBus to allow that and works great so
far. To enable iBus at login time there is a small one-liner in the
.kde4/Autostart directory and three lines in the .bashrc, including
 export QT_IM_MODULE=ibus

And while Gtk+ or X applications honer the exported variable and allow iBus to
be activated for them, Qt applications don't.

A workaround for the time being is to start any Qt application from e.g.
terminal with
 QT_IM_MODULE=ibus [APPLICATION]
where [APPLICATION] is replaced by the application's name, e.g. kwrite.

This behaviour was observed with KWrite, Skype and some other Qt-based
applications. Gtk+-based applications like Pidgin or Iceweasel work as expected
(hitting Ctrl + space activates the iBus input method).

If you should need further information, please feel free to ask me, I'll run the
tests and return the information ASAP.

Kind regards,
Kai Wasserbäch

P.S.: Setting QT4_IM_MODULE doesn't help either.


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

Kernel: Linux 2.6.31.6-cabal
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libqtcore4 depends on:
ii  libc6  2.10.1-7  GNU C Library: Shared libraries
ii  libgcc11:4.4.1-4 GCC support library
ii  libglib2.0-0   2.22.2-2  The GLib library of C routines
ii  libstdc++6 4.4.1-4   The GNU Standard C++ Library v3
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

libqtcore4 recommends no packages.

libqtcore4 suggests no packages.

-- no debconf information



-- 

Kai Wasserbäch (Kai Wasserbaech)

E-Mail: deb...@carbon-project.org
Jabber (debianforum.de): Drizzt
URL: http://wiki.debian.org/C%C3%B9ran
GnuPG: 0xE1DE59D2  0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2
(http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2fingerprint=onhash=onop=vindex)



signature.asc
Description: OpenPGP digital signature


Bug#557555: [Qt] Qt applications don't heed global QT_IM_MODULE

2009-11-22 Thread Modestas Vainius
tags 557555 pending
thanks

Hello,

On sekmadienis 22 Lapkritis 2009 22:43:35 Kai Wasserbäch wrote:
 Dear Qt maintainers,
 I've recently installed Debian for somebody needing support for entering
 traditional Chinese characters. I chose iBus to allow that and works great
  so far. To enable iBus at login time there is a small one-liner in the
  .kde4/Autostart directory and three lines in the .bashrc, including
 
  export QT_IM_MODULE=ibus
 
 And while Gtk+ or X applications honer the exported variable and allow iBus
  to be activated for them, Qt applications don't.

.bashrc is just a wrong place to export environment variables for X sessions. 
Create a new file in /etc/X11/Xsession.d/ or use ~/.xsessionrc for that 
purpose.

I will close this likely not-a-bug in a few days or when you respond.

-- 
Modestas Vainius modes...@vainius.eu


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


Processed: Re: Bug#557555: [Qt] Qt applications don't heed global QT_IM_MODULE

2009-11-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 557555 pending
Bug #557555 [libqtcore4] [Qt] Qt applications don't heed global QT_IM_MODULE
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#553451: kde4libs: General update after the debconf review process

2009-11-22 Thread Christian Perrier
Dear Debian maintainer,

On Monday, October 12, 2009, I sent you a notification about the beginning of a 
review
action on debconf templates for kde4libs.

Then, I sent you a bug report with rewritten templates and announcing
the beginning of the second phase of this action: call for translation
updates.

Translators have been working hard and here is now the result of their efforts.

Please consider using it EVEN if you committed files to your
development tree as long as they were reported.

The attached tarball contains:

- debian/changelog with the list of changes
- debian/control with rewrites of packages' descriptions
- debian/templates with all the rewritten templates file(s)
- debian/po/*.po with all PO files (existing ones and new ones)

As said, please use *at least* the PO files as provided here,
preferrably over those sent by translators in their bug reports. All
of them have been checked and reformatted. In some cases, formatting
errors have been corrected.

The patch.rfr file contains a patch for the templates and control
file(s) alone.

Please note that this patch applies to the templates and control
file(s) of your package as of Monday, October 12, 2009. If your package was 
updated
in the meantime, I may have updated my reference copybut I also
may have missed that. This is indeed why I suggested you do not
modified such files while the review process was running,
remember..:-)

It is now safe to upload a new package version with these changes.

Please notify me of your intents with regards to this. 

There is of course no hurry to update your package but feel free to
contact me in case you would need sponsoring or any other action to
fix this.



-- 




patch.tar.gz
Description: Binary data
--- kde4libs.old/debian/kdelibs5.templates  2009-10-08 14:48:45.0 
+0200
+++ kde4libs/debian/kdelibs5.templates  2009-10-31 14:36:58.326506058 +0100
@@ -1,3 +1,12 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: kdelibs5/upgrade_kdehome_running_title
 Type: title
 _Description: Upgrading kdelibs5 while KDE 4 is running
@@ -5,28 +14,19 @@
 Template: kdelibs5/upgrade_kdehome_running
 Type: boolean
 Default: true
-_Description: Stop possible unsafe upgrade of KDE4 with running sessions?
- You are about to upgrade to the new version of the kdelibs5 package which
- introduces a major configuration change. Newly started KDE 4 applications
- will use ~/.kde directory to store user settings and data (also known as
- KDEHOME) by default while currently running KDE 4 applications use ~/.kde4.
- KDE 3 applications have always used (and will continue to use) ~/.kde. It
- seems that there are a few KDE 4 applications running on your system at the
- moment. To avoid potential setting/data loss, you should:
- .
- 1) Answer Yes, terminate all KDE applications and KDE sessions and try
- upgrading again.
- .
- or 2) Answer No to continue upgrading. You should make sure that no new
- KDE 4 applications are started before you migrate your KDE 4 settings and
- data.  Beware, that clean termination of the old KDE 4 session might not be
- safe..
+_Description: Stop unsafe KDE 4 upgrade?
+ You are about to upgrade to the new version of the kdelibs5 package, which
+ introduces a major configuration change - details are given in
+ /usr/share/doc/kdelibs5/README.Debian (in short: user settings are moved
+ from ~/.kde4 to ~/.kde). However, some KDE 4 applications are currently
+ running: ${apps}
  .
- Once upgrade is complete, login to KDE as usual or you may use Kaboom wizard
- (package name: kaboom) to migrate your user settings and data before starting
- any KDE 4 application.
+ It is recommended to abort the upgrade of kdelibs5, terminate all KDE
+ applications and KDE sessions, and try upgrading again.
  .
- Currently running KDE 4 applications: ${apps}
+ If you choose to continue the upgrade, you should make sure that no new
+ KDE 4 applications are started before KDE 4 settings and data are migrated.
+ A clean termination of the old KDE 4 session might not be safe.
 
 Template: kdelibs5/upgrade_kdehome_info_title
 Type: title
@@ -35,12 +35,11 @@
 Template: kdelibs5/upgrade_kdehome_info
 Type: note
 _Description: New user settings directory (KDEHOME) for KDE 4 applications
- Once this package is upgraded, KDE 4 applications will use ~/.kde directory to
- store user settings and data (also known as KDEHOME) by default.  Currently,
- KDE 4 applications use ~/.kde4. KDE 3 applications has always used (and will
+ Once this package is upgraded, KDE 4 applications will use ~/.kde as the 
default
+ directory to store user settings and data in (also known as KDEHOME). 
Currently,
+ KDE 4 applications use ~/.kde4. KDE 3