Your message dated Fri, 11 Mar 2011 01:17:07 +0000
with message-id <e1pxqyz-0006x4...@franck.debian.org>
and subject line Bug#586617: fixed in bzr-builddeb 2.7
has caused the Debian Bug report #586617,
regarding plasma-widget-networkmanagement: significant usability problems on
high DPI display
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
G'day. This is an upstream bug, which I am happy to take there if that is
more appropriate — if you would be kind enough to point me to the upstream
BTS; I looked, but failed to find it.
My system has a comparatively high DPI display:
daniel@krosp:~$ xdpyinfo | grep -B1 resolution
dimensions: 1920x1200 pixels (332x210 millimeters)
resolution: 147x145 dots per inch
I still use appropriately scaled fonts on it, which is nice, but sometimes
leads to issues with GUI applications that assume a lower DPI display and
consequently have some issues.
This is common enough in the Plasma world, where fonts end up overflowing the
space allocated in the widget; in plasma-widget-networkmanagement this
actually results in some reasonable usability issues.
The biggest is that when you click on a network interface it jumps to the
display of the traffic graph and details; if this is done on the "eth0"
interface, the button to return to the main display is pushed under the
right-hand side panel and can't be triggered.
That makes it impossible to return to the main display if I click through
there and all.
The widget has a bunch of similar display scale issues, though: it has too
little vertical space for the checkboxes on the main display, too little
horizontal space for the network interface list, and too little space for the
"Show More" and "Manage Connections" buttons in general.
Finally, most of the indicators — the icons next to the listed entries in
"Connections", and the "Disconnect" button especially — are so small as to be
almost invisible on this system. It would be great if they scaled based on
the platform DPI to ensure usability.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages plasma-widget-networkmanagement depends on:
ii knm-runtime 0.1~svn1133205-1 KDE NetworkManagement infrastructu
ii libc6 2.11.2-1 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.4.4-5 GCC support library
ii libkdecore5 4:4.4.4-1 the KDE Platform Core Library
ii libkdeui5 4:4.4.4-1 the KDE Platform User Interface Li
ii libkio5 4:4.4.4-1 the Network-enabled File Managemen
ii libkutils4 4:4.4.4-1 various utility classes for the KD
ii libplasma3 4:4.4.4-1 the Plasma Library for the KDE Pla
ii libqt4-dbus 4:4.6.3-1 Qt 4 D-Bus module
ii libqt4-network 4:4.6.3-1 Qt 4 network module
ii libqt4-svg 4:4.6.3-1 Qt 4 SVG module
ii libqt4-xml 4:4.6.3-1 Qt 4 XML module
ii libqtcore4 4:4.6.3-1 Qt 4 core module
ii libqtgui4 4:4.6.3-1 Qt 4 GUI module
ii libsolid4 4:4.4.4-1 Solid Library for KDE Platform
ii libsolidcontrol4 4:4.4.4-1 library for Solid based network ma
ii libstdc++6 4.4.4-5 The GNU Standard C++ Library v3
plasma-widget-networkmanagement recommends no packages.
Versions of packages plasma-widget-networkmanagement suggests:
ii kdebase-workspace-bin 4:4.4.4-1 core binaries for the KDE 4 base w
-- no debconf information
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is fixed in the latest version of
bzr-builddeb, which is due to be installed in the Debian FTP archive:
A summary of the changes between this version and the previous one is
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 586...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Jelmer Vernooij <jel...@debian.org> (supplier of updated bzr-builddeb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Date: Mon, 07 Mar 2011 12:28:08 +0100
Architecture: source all
Maintainer: Debian Bazaar Maintainers <pkg-bazaar-ma...@lists.alioth.debian.org>
Changed-By: Jelmer Vernooij <jel...@debian.org>
bzr-builddeb - bzr plugin for Debian package management
Closes: 517867 552893 586617 616752 676456 701244
bzr-builddeb (2.7) unstable; urgency=low
[ James Westby ]
* Accept None as a valid previous_version value in merge_upstream().
[ Jelmer Vernooij ]
* Support 'bzr tags --sort=debversion'. Closes: #701244.
* When adding a changelog entry, support git and svn snapshots.
* Automatically use debian/source/format if package is native. Closes:
* Fix "bzr builddeb" if last upload was not to a Ubuntu release pocket.
* If possible use uscan to find the latest upstream version string.
* Add --snapshot option to merge-upstream.
* 'bzr merge-upstream' now also works in merge mode, and will simply
add a new entry for new upstream versions.
* merge-upstream will now keep epochs around. LP: #622678
* 'bzr builddeb' now searches for directories relative to the working
tree rather than relative to the branch. Closes: #676456
* Use enums for build types, and a priority scheme to figure out the
build type. LP: #655277
* Fix finding upstream tarball when get-orig-source is not available.
* merge-upstream now looks at the package source format to see what
kind of compression is supported on tarballs. LP: #627718
* Support upstream version strings containing dashes. Patch by Stefano
Rivera. LP: #711826
* Run test suite unless nocheck is set (consistent with policy).
* Fix build dependencies for test suite.
* Support unversioned debian/ symlink in working tree when finding
changelog and larstiq mode. LP: #619295
* The deb: directory service has been renamed to apt: to avoid
* When building with distribution set to UNRELEASED, it is now assumed
the build is targetted at the same distribution as the build before.
* A hook for 'bzr merge-upstream' has been added. LP: #657501
* Support running the test suite in parallel during package build.
* Pristine tarballs are now automatically created when merging upstream
from a branch. Closes: #517867
[ Max Bowsher ]
* Add devscripts to Build-Depends-Indep, the test suite runs dch.
[ Jelmer Vernooij ]
* The 'export-upstream' configuration option is now deprecated in
favour of 'upstream-branch'. LP: #730293
* Switch to dh_python2. Closes: #616752
3f03da67272456347ace05e70d9b75493a5be117 1224 bzr-builddeb_2.7.dsc
5574a68556369276749cc1be045bd3e8e0894668 161065 bzr-builddeb_2.7.tar.gz
ce3d27aa9370026a2d263fc5e28e7b1b32a4bb7e 147928 bzr-builddeb_2.7_all.deb
977a7633aa9ed49ae21d5d1e3b743987 1224 vcs optional bzr-builddeb_2.7.dsc
02745de26ca6fd7ff096474e41260582 161065 vcs optional bzr-builddeb_2.7.tar.gz
2247a3185122f57f7d98cd1cda3a679d 147928 vcs optional bzr-builddeb_2.7_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
--- End Message ---
pkg-kde-extras mailing list