Bug#990129: libqt5core5a: breaks work of some QtWebEngine based programs
Hi Dmitry, > Can you please test if the .deb file attached to this message fixes the bug > for you? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989744#37 > > In that file I reverted changes to src/corelib/mimetypes/qmimeprovider.cpp > from that commit. These changes were not related to the main purpose of that > commit, so this way we can still have the original bug fixed. I tested proposed package libqt5core5a_5.15.2+dfsg-7_amd64.deb and may confirm what it solves my problem with maps in QtWebEngine. Best regards, Boris
Bug#990129: libqt5core5a: breaks work of some QtWebEngine based programs
Package: libqt5core5a Version: 5.15.2+dfsg-6 Severity: important X-Debbugs-Cc: tehnic...@yandex.ru Hi, I use Debian 11 (Bullseye) on work PC to develop Qt based projects. All worked fine until update of Qt packages last week: one of our QML based application stopped showing maps without any errors in stdin/stdout. Today I spent few hours to find the root of problem. QtWebEngine is used for displaying maps and it is quite problematic itself, but I was surprised to find what problem was caused by update in QtCore library: libqt5core5a:amd64 (5.15.2+dfsg-5, 5.15.2+dfsg-6) And if I understand correctly here is the problematic patch: https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/5eaeb73 Could you revert it please? Best regards, Boris -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (700, 'testing'), (500, 'testing-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5core5a depends on: ii libc6 2.31-12 ii libdouble-conversion3 3.1.5-6.1 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii libicu67 67.1-6 ii libpcre2-16-0 10.36-2 ii libstdc++6 10.2.1-6 ii libzstd1 1.4.8+dfsg-2.1 ii shared-mime-info 2.0-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages libqt5core5a recommends: ii qttranslations5-l10n 5.15.2-2 Versions of packages libqt5core5a suggests: ii libthai0 0.1.28-3
Re: Locale Issue in bullseye
Hi, > I installed a new bullseye system. I added some accounts and changed the > locale (regional settings) to German. Worked well for > > - System settings > - Application starter menu > - Non-KDE Applications (e.g. firefox and libreoffice) > > Did not work for > - control panel > - all KDE Applications, e.g. > -- kate > -- kmail > -- konsole > -- ... > > Is this a bug or did I miss something? > > Any advice or hint is welcome. Please show output of commands: $ locale $ locale -a Have you tried to install special meta-packages task-german-desktop and task-german-kde-desktop? Best wishes, Boris
Re: Current status of KDE in Sid
Hi, > Dist-upgrade wants to remove 103 packages, many of them are programs I > use every day, like kate, dolphin, plasma-destop, virtualbox, okular, > etc... > > Full-upgrade wants to remove the same 103 essential packages > > It does not look good What apt says you if you try to update a single package from KDE+Plasma stack? For example: sudo apt install -V dolphin -- Boris
Re: Middle click functionality as paste in KDE
Hi, > Middle click indeed open links in new tabs in firefox.' > > So that means that middle button i guess are identified > at some level. But if you are correct i must search in > X config level to make it work? Could you show the output of commands: echo $XDG_SESSION_TYPE and dpkg -l | grep -i X | grep -i input Best wishes, Boris
Bug#942184: New stable version is available: 5.13.1
Package: qtwebkit-opensource-src Version: 5.212.0~alpha3-4 Severity: wishlist Hi, Please update QtWebkit to the latest stable version 5.13.1. Tarballs are available here: https://download.qt.io/snapshots/ci/qtwebkit/5.212/latest/src/submodules/ Best wishes, Boris
Re: Back to Amarok / building git on buster - built it
Hi, >>> Ok, I try the hard way, building it from git source. I am a bit >>> withlout knowledge, but lets try. >>> >>> Curerntly I hang at the MYSQL cmake task: >>> Could NOT find MySQL (missing: MYSQL_LIBRARIES MYSQL_INCLUDE_DIR) >>> >>> As buster uses mariadb, which cmake options do I have to enter? >>> >>> thanks. >>> >>> (or has anyone a decent guide howto compile amarok git version on >>> debian buster ?) >> >> You may like to ask on the Amarok upstream mailing list. >> >> https://amarok.kde.org/en/support >> >> https://mail.kde.org/mailman/listinfo/amarok >> >> Would be interested in your findings, i.e. whether it works at all. As >> far as I saw Laurent put some KDE 4 => 5 migration code into Amarok. > > Ok, I did built amarok git 22.08.2019 on debian buster. > It starts, it shows my collection, it shows my playlist and it plays > music as expected. > So far job done (as a start). > > (no wiki, no lyrics, but hey, it plays music). > > One note: it runs only from the directory it was built within. > Even after a make install (which ruins the instlled debian package, I would strongly recommend never do `make install` in your system. If you cannot make a correct debian packages, than just use checkinstall tool. It is very simple. Best wishes, Boris
Re: [Pkg-xmpp-devel] Qt/KDE XMPP/Jabber client with OMEMO
>> >> Then there is kaidan.im which is not packaged yet. >> >> I saw mentions of this project few times (in qxmpp related >> discussions) but have not looked on program yet. >> >> As I see there is related team on Salsa: >> https://salsa.debian.org/kaidan-team >> >> But I have no idea why these packages are not in Debian repos yet and >> why its maintainers have decided to maintain these packages outside >> of Debian XMPP Maintainers team. >> >> Probably Jonah may comment this. (CC-ing) > > We don't "have decided" to maintain it outside of debian, we just > didn't have an idea how to get it into debian. I mean outside of XMPP team in Debian, but not outside of Debian. Now git repos for your packages are in independent Salsa group: https://salsa.debian.org/kaidan-team and I have found them only because I was searching for kaidan mentions in Debian infrastructure. As for adding of kaidan into Debian repos, then joining to specialized Debian team usually simplify finding Debian Developers who are interested in checking and uploading of your packages into Debian. See this as an advertisement of our team: https://salsa.debian.org/xmpp-team =) > Kaidan is still in > development: the basic functionality is not implemented completely yet. And this is absolutely normal. Dino.im is not released yet and lucks some features too, but it is already available in Debian and may work fine for some not exacting users. > Also, we only recently became a KDE project, so we didn't have the > contact to the debian team. These are great news! Congratulations! And now you have a choice between Debian XMPP team and Debian Qt+KDE team: https://salsa.debian.org/qt-kde-team > However recently there were some mails about packaging Kaidan in debian > on the Qt/KDE-list, so I hope it can get into debian soon. Excellent! > OMEMO is on our roadmap and also PEP (a dependency of OMEMO) has been > implemented for QXmpp (still needs to be upstreamed). But don't expect > OMEMO earlier than in one year. And this is fine. We are not in a hurry to anywhere. Best wishes, Boris
Re: Qt/KDE XMPP/Jabber client with OMEMO
Hi Martin, >> Is there such a thing available in Debian? You may ask XMPP related questions in Debian XMPP Maintainers team mailing list: https://wiki.debian.org/Teams/pkg-xmpp >> Kopete 17.08 does not do it. Yes, IIRC Kopete has support only for GnuPG and OTR. >> PSI is said to have OMEMO, but does not appear to have it in Debian. Yes, unfortunately psi package in Debian is outdated and psi-plugins package is not in official repos yet. This is in my TODO list, but progress is slow... > I now also tried psi-plus. And found I missed two things before: > > There is a OMEMO plugin and I can activate. > > Messages send are still not encrypted as I can see in dino.im > > There is supposed to be a OMEMO plugin symbol in toolbar in chat window > but there is not, even tough it is supposed to be there according to > settings window. > > I leave it at that for today. Current version of Psi+ OMEMO plugin in Debian supports all necessary features: * e2e encryption in private chats * e2e encryption in group chats (all members of group chats should have enabled OMEMO plugins in their XMPP clients) * e2e encryption of files uploaded to XMPP server using HTTP Upload Plugin * etc. It is comprehensive tested with Gajim and Conversations. Please check: 1) Have you tried to restart application after enabling of OMEMO plugin? 2) Do you have OMEMO buttons on toolbars in chat windows? If not you may enable them in Psi+ Options dialog in Toolbars section. 3) In some rare cases you may face with broken databases. Try to remove files: ~/.local/share/psi+/profiles/default/omemo-*.sqlite and restart Psi+. Also there is no global option to enable OMEMO encryption in all chats of Psi+: you should explicitly enable encryption in each chat manually. > dino.im works out of the box. > >> Only working (!) XMPP client I found in Debian so far is: dino.im >> which is GTK based. Great! Martin (debacle) may be proud of his work! =) >> Gajim is supposed to be working, but gives a Python traceback on >> activating OMEMO. Its also GTK based. It is strange. Last time I have used Gajim for testing of OMEMO plugin in Psi+ it works fine. Except Gajim could not send OMEMO encrypted files to server. But is was able to decrypt such files sent from other XMPP clients! >> Apparently there more than a dozen XMPP clients for Linux, but none of >> them works as nicely as Conversations.im on Android for far. Conversations is not that perfect (it lucks support of some popular features), but it is really convenient and simple in usage by regular users, yes. >> Pidgin also does not do it. Pidgin is multi-protocol IM client and this significantly influences to its structure and development process. >> One thing to try still would be KDE Telepathy, as I read somewhere it >> would do OMEMO. But it appears to be similarly outdated as Kopete. And after news like this one: https://dot.kde.org/2019/02/20/kde-adding-matrix-its-im-framework I do not believe that any noticeable amount of KDE developers will be interested in development of XMPP client inside KDE project. Hope I am wrong here. >> Then there is kaidan.im which is not packaged yet. I saw mentions of this project few times (in qxmpp related discussions) but have not looked on program yet. As I see there is related team on Salsa: https://salsa.debian.org/kaidan-team But I have no idea why these packages are not in Debian repos yet and why its maintainers have decided to maintain these packages outside of Debian XMPP Maintainers team. Probably Jonah may comment this. (CC-ing) >> There are in part contradicting informations on which client can do it >> or not: >> >> https://omemo.top/ >> >> versus >> >> https://riseup.net/de/chat/clients >> >> for example. These tables are very useful in general, but they miss some information about OMEMO support. For example: in which versions of XMPP clients it was implemented. For example, Psi IM 2.0 with OMEMO support is not released yet. OMEMO plugin is currently available only in daily builds of Psi (from git master branch). Best wishes, Boris
Re: kde-gtk-config_5.13.5-1_source.changes ACCEPTED into unstable
Hi, > Let me suggest you a rule of thumb: if you are thinking in removing a > dependency version check first if the minimum required version is available in > stable. If it's not keep the relationship so backporters know from the start > that they also need to backport something else. Personally I use oldstable as bottom border for this. Best regards, Boris
Re: kde-gtk-config_5.13.5-1_source.changes ACCEPTED into unstable
>> Yep, I remember. But there were no reason to not update this version >> together >> with package update. Also debdiff says that two lines were changed in file >> "po/zh_CN/kde-gtk-config.po". ;-) > > Oh, I missed that, currently I'm checking the diff between upstream tags in > minor versions, I guess I should probably also need to check the tarballs. :( Yeah, two reasons among others why I don't like current KDE infrastructure: 1) They do not store translations in the same git repo where sources are, so you cannot easily get git snapshot with up to date localization files. 2) Their tarballs with releases of programs differ from sources in git tags. As far as points above are closely related they might be merged into one... =) >>> Are you really that much against adding a version dependency is no longer >>> in >>> the archive? > >> This is not strictly a matter of principle, but just a question of common >> sense. > > Ok, let's agree that common sense is subjective here, and we just want > something > team acceptable, maintainable. > > Personally, I prefer adding the version dependency as a way of showing the > upstream package requirements. That way the source package ends up being more > independant of the current Debian archive, we don't need to review all the > packages when some release is no longer being supported and if somebody wants > to do some crazy thing with the package, well, we are not working against > them. Ok. Best regards, Boris
Re: kde-gtk-config_5.13.5-1_source.changes ACCEPTED into unstable
Hi, > First of all, thanks for working in improving kde-gtk-config. > >>* New upstream release. > > As mentioned in a private mail, I try to avoid versions were the only change > is the version bump. Yep, I remember. But there were no reason to not update this version together with package update. Also debdiff says that two lines were changed in file "po/zh_CN/kde-gtk-config.po". ;-) >>* Bump Standards-Version to 4.2.1 (was 4.1.4): no changes required. > > Right, I haven't bumped any Standards-Version beyond 4.1.4, that's, a personal > decision based on a change introduced in 4.1.5. I'm not expecting anyone else > to follow suite. > > The Standards-Version 4.1.5 includes a change that I consider counter > productive, that is: > ... Ok, I see your point of view. Happily, this rule should not affect kde-gtk-config package because it is now among basic KDE applications. >>* Simplify debian/control: drop requirement of specific version of cmake >> (was >= 2.8.12), because even Debian Jessie has cmake version 3.0.2. > > The CMakeLists.txt states that it requires the version, why would the > debian/control show this requirement? > > I don't see a simplification here, also the version build dependency is added > by a script that parses the CMakeLists.txt shipped in the package in > particular: > cmake_minimum_required(VERSION 2.8.12) Obviously we use different tools and rules during maintaining of packages. And I just was not aware of your script. > So, the version dependency would be added in the next run of the script. I do not see a problem here. If you will add versioned dependency in a next upload, than let it be. Or you may manually edit file after automatic changes done by script. Or we may improve that magical script... This is co-maintained package. We just have to come to common decision and I will add a point in my notes for this package. > Are you really that much against adding a version dependency is no longer in > the archive? This is not strictly a matter of principle, but just a question of common sense. Best regards, Boris
Re: kio_sftp: "The host key for this server was not found, but another type of key exists."
Hi, > Network folders in Dolphin don't work for me anymore after some recent update. > I'm using a current unstable system. sftp on the commandline continues to work > as before. > > The error message I get in Dolphin is > >> The host key for this server was not found, but another type of key exists. >> An attacker might change the default server key to confuse your client into >> thinking the key does not exist. Please contact your system administrator. You need to remove the string with that host key from file ~/.ssh/known_hosts Or just delete file ~/.ssh/known_hosts completely. It will be filled again during your regular usage of ssh connections. Best wishes, Boris
Bug#897338: sddm: Cannot launch SDDM at boot time and from console
Hi, > Hi, I am on Debian Unstable on real hardware and I have the same problem, > SDDM launches but there is dark screen on TTY7 with only my mouse. Try instructions from Debian wiki [1]. They solved this problem for NVIDIA GeForce GTX 1050 Ti Mobile on my laptop. [1] https://wiki.debian.org/NvidiaGraphicsDrivers/Optimus Best wishes, Boris
Accepted qconf 2.4-3~bpo9+1 (source) into stretch-backports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Mar 2018 01:14:07 +0300 Source: qconf Binary: qconf Architecture: source Version: 2.4-3~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Qt extras Maintainers <debian-qt-kde@lists.debian.org> Changed-By: Boris Pek <tehn...@debian.org> Description: qconf - nice configure script for qmake-based projects Changes: qconf (2.4-3~bpo9+1) stretch-backports; urgency=medium . * Rebuild for stretch-backports. . qconf (2.4-3) unstable; urgency=medium . * Change Maintainer name to "Debian Qt extras Maintainers". . qconf (2.4-2) unstable; urgency=medium . * Set Debian KDE Extras Team as Maintainer; move myself to Uploaders. * Bump Standards-Version to 4.1.3 (was 4.1.2). * Bump debhelper version to 11 (was 9); update debian/compat. * Update Vcs-* fields in debian/control: moved from GitHub to Salsa. * Delete --parallel option from dh in debian/rules. * Update years and Format URL in debian/copyright. Checksums-Sha1: 1f8cb20dba41c7bc768be1d9cbf5ac92d8fdfddb 1936 qconf_2.4-3~bpo9+1.dsc 7ae5daade2ad5ef0951f0f70c7a9404c9ca1e110 97556 qconf_2.4.orig.tar.gz b58a14b7c7912a5bb933eff7be0884ec95ee3c48 3720 qconf_2.4-3~bpo9+1.debian.tar.xz Checksums-Sha256: 1e826a04438621eae194df6ebe826310a2b57d2d690bb54418989a063f1c6b59 1936 qconf_2.4-3~bpo9+1.dsc 8a486060d5481f5b62171b8ffe343d9a9dd49e3b3170a1f79314ee34ea9e8819 97556 qconf_2.4.orig.tar.gz 052c3f0e2e7258027745c6af809510e86003ef884a5e40a7439c75c91aa1 3720 qconf_2.4-3~bpo9+1.debian.tar.xz Files: 91ba10a0b38f385198a37bc3db7751fa 1936 devel optional qconf_2.4-3~bpo9+1.dsc b94644b73f3151db6def9e36b3207cbc 97556 devel optional qconf_2.4.orig.tar.gz bb61435c4d37e6256f7f369f331332fc 3720 devel optional qconf_2.4-3~bpo9+1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE74NZeBI5qRlNLX9Z0AFb0SjzkngFAlqjBzQTHHRlaG5pY2tA ZGViaWFuLm9yZwAKCRDQAVvRKPOSeJyDD/9XI9DmZkSWCLlHk2JwQdHHhAb2bgkt +F+D3EwvPERKMAYdfesPDfG7CqAF2Zh5h4Y40c50IAFRoClzNrwfcNU98L0woxD+ O5nvgg+1kRKUfj8xbUzS7BWmBzNZdqvmU3SKb+hLObWI+dNcsRFdXl6x1295C8mN 8GApXGtVxxkDZ/Jt7/rNurIo1mytRWk0i0+jAa8M83jHd3k5/zdWDfFpc77N8kY6 GZs2QnTIXZEU4JcoouremvX1sYFjRjHASiJAbtmmfMmf45syoLxe9eJa/Xl7h0ci rx7g9RVa635Wjd+QNZz7oN5YloKMa3HlM+iWLG2ndjbvnt8mvL7K6PZOoDLMKwGl 9nKU3f7s8JzUrgzVYEYWUCjbPNCk1oELw3ksAQbwBB+r/e6hlCT//NAUBjULA8+x 0kR5qQvAMI7p6nkU97DesC6cmrkWPzmOIhyM6qZuTyo5D2joQ46UcDWGPr3nWUeI 4vtXdJwYK22sQmsRGSEQ7pK3zJdEaZhUytTqaDoMvikx29g8X36ue5sbkgoxlwMF vQX4l/X0SZ/JLMFrStwu6F7qSbV4ezYUnH6ZJKFGIKwlwFZJ+WszEz1wtY64DQH1 N3QWN9tbhFXWaWYu3fSmI8dghTcJQB//T9AUlurH4c1yDq6NnE9WJTWK11mqgNLd PXrMpFaTd+96Wg== =Tywy -END PGP SIGNATURE-
Bug#884956: vlc: icons are too big
Hi, VLC 3.0.1 has been released recently. There is interesting note in its [changelog]: ... Qt Interface: * Improve scaling on HiDPI displays ... Try this new version of VLC please to check if the bug is still reproducible. [changelog] http://git.videolan.org/?p=vlc/vlc-3.0.git;a=blob;f=NEWS;hb=399713b542d29c81300d23a657fd2ec22bc927b6 Best wishes, Boris
Re: Need help testing qtbase with HiDPI monitors
Hi Lisandro, > Hi everyone! I would really *love* if some of you could help me with a > HiDPI issue we are tracking. > > Currently qtbase 5.9.1-11 added a patch that should improve HiDPI > usage for most use cases. I would like to know if it caused or not a > regression for any of you. VLC seems the right app to test with. > > It would also be really cool if you find that it breaks stuff if > starting vlc with QT_AUTO_SCREEN_SCALE_FACTOR=0 env variable set does > anything for you. > > Long story: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884956 I would like to help you, but I do not know which result is supposed to be after using of discussed setting. Could you describe it in more details? My main computer for hobby tasks is a laptop with 15.6" FullHD IPS screen. Its native resolution is 1920x1080, so DPI should be about 141.21. When I have bought this laptop I have tested screen scaling and other available settings... Unfortunately, all of them have looked ugly and were absolutely unusable. The most convenient configuration I have found (and am using now): scale factor 1 + font size 10pt + DPI 116. Also I would be grateful for any info if anything have been improved in 2017 and you have recommendations which settings should be convenient for my monitor now. Best wishes, Boris
Bug#879713: konsole: Konsole freezes for a minute when I press backspace in empty command line
Hi, > Since a few days (or weeks?) I experience a strange behavior in konsole. > When editing a command line, if I press backspace too many times finally > trying to delete a character from an empty line, konsole freezes for ca. > one minute. The CPU load is almost 0%, other programs in the X windows > session work corectly. Even other konsole windows work correctly. > > The interesting thing is that the problem occurs exactly ones in each > konsole window. It doesn't matter how many tabs I open. If I press backspace > in the empty command line for the first time in one of open tabs, the whole > window freezes. After it recovers, I can safely press backspace in all tabs > without any problems. Try to use [Tab] key from keyboard to complete the command or path when you are typing something. You will get exactly the same freeze. > In fact it looks like konsole gets blocked trying to connect to certain not > running network service. > > I don't know it it matters, but I use konsole in the MATE session. Yes, this is important. When program is launched directly in KDE session this bug is not reproducible. But this bug could but easily reproduced even in KDE session. If there are two users in your system (user1 and user2) and you have logged in as user1 then launch: $ ssh -C -X -p 22 user2@localhost konsole and you will be able to see a number of issues in launched KDE application. One of these issues is a bug described above. Best regards, Boris
Bug#877627: stretch-pu: package kde-gtk-config/5.8.6-1+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-CC: debian-qt-kde@lists.debian.org
Dear release team,
I would like to push a fix for src:kde-gtk-config package in stable. Without
this fix package kde-config-gtk-style lacks one very convenient feature
(previewing GTK+ 2.x and GTK+ 3.x themes before applying them) and package
kde-config-gtk-style-preview is absolutely useless (because binaries from it
cannot be used).
Proposed changes have been applied in package in unstable since 04 Aug 2017
(kde-gtk-config/4:5.10.4-1) and all works fine.
Please consider accepting this as a stretch-pu.
Thanks,
Boris
diff -Nru kde-gtk-config-5.8.6/debian/changelog kde-gtk-config-5.8.6/debian/changelog
--- kde-gtk-config-5.8.6/debian/changelog 2017-03-14 17:23:29.0 +0300
+++ kde-gtk-config-5.8.6/debian/changelog 2017-10-03 17:31:46.0 +0300
@@ -1,3 +1,15 @@
+kde-gtk-config (4:5.8.6-1+deb9u1) stable; urgency=medium
+
+ * Update debian/rules:
+set DATA_INSTALL_DIR variable in configuration options: it is required
+for correct search of preview.ui file in gtk*_preview programs.
+(These programs have not been working since version 4:5.1.95-0ubuntu1)
+ * Add patch fix-search-of-gtk-preview-executables.
+It is required for showing preview buttons in KDE-GTK-config UI.
+(These buttons have not been working since version 4:5.1.95-0ubuntu1)
+
+ -- Boris Pek <tehn...@debian.org> Tue, 03 Oct 2017 17:31:46 +0300
+
kde-gtk-config (4:5.8.6-1) unstable; urgency=medium
* New upstream release (5.8.6)
diff -Nru kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch
--- kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch 1970-01-01 03:00:00.0 +0300
+++ kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch 2017-08-04 17:00:50.0 +0300
@@ -0,0 +1,43 @@
+Forwarded: no
+Description: Fix search of gtk*_preview executables
+ Due to Debian multiarch support gtk_preview and gtk3_preview executables are
+ installed into non-standard path (/usr/lib/*/libexec/) which is out of
+ search scope of QStandardPaths::findExecutable() function.
+ .
+ This patch is required for showing preview buttons in KDE-GTK-config UI.
+Author: Boris Pek <tehnic...@yandex.ru>
+Last-Update: 2017-08-04
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -26,6 +26,8 @@
+
+ # Set KI18n translation domain
+ add_definitions(-DTRANSLATION_DOMAIN=\"kde-gtk-config\")
++add_definitions(-DCMAKE_INSTALL_PREFIX=\"${CMAKE_INSTALL_PREFIX}\")
++add_definitions(-DLIBEXEC_INSTALL_DIR=\"${LIBEXEC_INSTALL_DIR}\")
+
+ set(kcm_SRCS
+ src/iconthemesmodel.cpp
+diff --git a/src/gtkconfigkcmodule.cpp b/src/gtkconfigkcmodule.cpp
+--- a/src/gtkconfigkcmodule.cpp
b/src/gtkconfigkcmodule.cpp
+@@ -87,6 +87,17 @@
+ QString gtk2Preview = QStandardPaths::findExecutable("gtk_preview");
+ QString gtk3Preview = QStandardPaths::findExecutable("gtk3_preview");
+
++// KStandardDirs::findExe was replaced by QStandardPaths::findExecutable
++// in a wrong way. See for details:
++// https://community.kde.org/Frameworks/Porting_Notes/KStandardDirs
++static const QString searchPath = CMAKE_INSTALL_PREFIX "/" LIBEXEC_INSTALL_DIR;
++if(gtk2Preview.isEmpty()) {
++gtk2Preview = QStandardPaths::findExecutable("gtk_preview", QStringList() << searchPath);
++}
++if(gtk3Preview.isEmpty()) {
++gtk3Preview = QStandardPaths::findExecutable("gtk3_preview", QStringList() << searchPath);
++}
++
+ m_p2 = new KProcess(this);
+ m_p2->setEnv("GTK2_RC_FILES", m_tempGtk2Preview, true);
+ if(!gtk2Preview.isEmpty()) {
diff -Nru kde-gtk-config-5.8.6/debian/patches/series kde-gtk-config-5.8.6/debian/patches/series
--- kde-gtk-config-5.8.6/debian/patches/series 1970-01-01 03:00:00.0 +0300
+++ kde-gtk-config-5.8.6/debian/patches/series 2017-08-04 17:00:50.0 +0300
@@ -0,0 +1 @@
+fix-search-of-gtk-preview-executables.patch
diff -Nru kde-gtk-config-5.8.6/debian/rules kde-gtk-config-5.8.6/debian/rules
--- kde-gtk-config-5.8.6/debian/rules 2017-03-14 17:23:29.0 +0300
+++ kde-gtk-config-5.8.6/debian/rules 2017-10-03 17:29:35.0 +0300
@@ -2,6 +2,9 @@
include /usr/share/pkg-kde-tools/qt-kde-team/3/debian-qt-kde.mk
+override_dh_auto_configure:
+ dh_auto_configure -- -DDATA_INSTALL_DIR="/usr/share/"
+
override_dh_auto_test:
# Disable dh_auto_test at build time
:
Re: Qt 5.7.1 => 5.9.1
>> I have just rebuild plasma-integration with Qt 5.9.1 in my system and this >> have >> solved the problem for me. So when binNMU'ed packages will arrive archive >> the >> issue will gone. > > Boris, is that something I can do too? Do you have a recipe for the rebuild? In my system it was just: dget -d http://deb.debian.org/debian/pool/main/p/plasma-integration/plasma-integration_5.8.6-1.dsc sudo cowbuilder --update sudo cowbuilder --build plasma-integration_5.8.6-1.dsc | tee build.log sudo dpkg -i /opt/pbuilder/result/plasma-integration_5.8.6-1_amd64.deb If you really want to rebuild this package in your system you need to install and properly setup pbuilder or cowbuilder first. But I recommend you just wait until updated package (5.8.6-1+b1) will arrive into the mirror of Debian repo which you use. Best wishes, Boris
Re: Qt 5.7.1 => 5.9.1
I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken now in KDE applications from Sid, and because of it they look very ugly when launched outside plasmashell or via `ssh -X ..`. For example, dolphin lacks all file icons and icons at toolbar and menus. Plus it uses some strange theme (not breeze). >>> >>> Dolpin looks normal in my install. >> >> Have you tried to launch it in openbox session or via ssh? >> >> `export XDG_CURRENT_DESKTOP=KDE` for applying proper Qt settings does not >> work >> anymore. > > I have just found my old email [1] and looking at [2] I hope that this problem > will be fixed soon. > > [1] https://lists.debian.org/debian-kde/2016/06/msg00034.html > [2] > https://buildd.debian.org/status/package.php?p=plasma-integration=unstable I have just rebuild plasma-integration with Qt 5.9.1 in my system and this have solved the problem for me. So when binNMU'ed packages will arrive archive the issue will gone. Best wishes, Boris
Re: Qt 5.7.1 => 5.9.1
>>> I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken>>> now in KDE applications from Sid, and because of it they look very ugly when>>> launched outside plasmashell or via `ssh -X ..`.>> For example, dolphin lacks all file icons and icons at toolbar and menus.>>> Plus it uses some strange theme (not breeze). Dolpin looks normal in my install.>> Have you tried to launch it in openbox session or via ssh?>> `export XDG_CURRENT_DESKTOP=KDE` for applying proper Qt settings does not work> anymore. I have just found my old email [1] and looking at [2] I hope that this problemwill be fixed soon. [1] https://lists.debian.org/debian-kde/2016/06/msg00034.html[2] https://buildd.debian.org/status/package.php?p=plasma-integration=unstable Best wishes,Boris
Re: Qt 5.7.1 => 5.9.1
>> I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken>> now in KDE applications from Sid, and because of it they look very ugly when>> launched outside plasmashell or via `ssh -X ..`. For example, dolphin lacks all file icons and icons at toolbar and menus.>> Plus it uses some strange theme (not breeze).>> Dolpin looks normal in my install. Have you tried to launch it in openbox session or via ssh? `export XDG_CURRENT_DESKTOP=KDE` for applying proper Qt settings does now workanymore. Best wishes,Boris
Re: Qt 5.7.1 => 5.9.1
Hi, > Just did a safe-upgrade. Everything seems to be working ok (though something> is a little slow with Chrome unstable). The only issue I've noticed is widget> style is stuck on Breeze. Selecting any other styles seems to not be> respected. I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken nowin KDE applications from Sid, and because of it they look very ugly whenlaunched outside plasmashell or via `ssh -X ..`. I may add that usage of XDG_CURRENT_DESKTOP environment variable is brokennow in KDE applications from Sid, and because of it they look very ugly whenlaunched outside plasmashell or via `ssh -X ..`. For example, dolphin lacks all file icons and icons at toolbar and menus.Plus it uses some strange theme (not breeze). Best wishes,Boris
Re: No taskbar and no mouse rightclick
Hi, > Yesterday I performed a dist-upgrade after more than a month that my > Debian/unstable was not updated and BOOM, KDE is not working any more... > I can login but the plasmashell seems missing even if the process is running. > There is only a blank desktop and no right click on mouse. KDE itself takes a > lot of time to load, but this maybe related to the other problems. Please, > help me fix this, thank Try: sudo apt install -V libblockdev-fs2 libblockdev-part2 libblockdev-mdraid2 libblockdev-crypto2 libblockdev-loop2 libblockdev-swap2 gdisk sudo systemctl restart udisks2 It was discussed today: https://lists.debian.org/debian-kde/2017/08/msg00069.html Best wishes, Boris
Re: kde-gtk-config_5.10.4-1_source.changes ACCEPTED into unstable
Hi, > I've rebased some pending changes that I had in my local repos and uploaded> them to alioth. Great! Thanks for your work on this package. > About plasma in general, I'm still waiting for kf5 to be fully available in> experimental to upload plasma 5.10 to experimental.>> I guess that kde-gtk-config works fine as and independant upload, but this is> not the general case for other frameworks, plasma and apps uploads, Exactly. kde-gtk-config is not as strictly depends on KF5 as some other KDEpackages. It was built and worked fine with older KF5 packages, so there wereno reasons to not update its version in Sid. > so, if> possible, please let the rest of the team know that you are working on $foo (a> simple msg to the #debian-qt-kde irc channel works fine). I am not going to work on any other package related to "Debian/Kubuntu Qt/KDEMaintainers" team in foreseeable future. As for kde-gtk-config package: I have packaged it very long time ago when it wasin KDE playground section and when I was not DD. At that time it required a lotof time and work to achieve kde-gtk-config upload into Debian repos [0][1][2].And when the package was finally uploaded all worked fine. Next, kde-gtk-config package was hijacked/adopted by "Debian/Kubuntu Qt/KDEMaintainers" team when kde-gtk-config have become the part on KDE workspace.Package had been receiving updates regularly and was in a good shape, so Ithought that my involvement is not required. But recently I have suddenly found that preview functionality was broken. Moreover it had been broken during very long period of time (since 2015). I wasdisappointed enough to fix the problem myself. All other changes in the package are not important and were done just forcompany. You are free to revert any of them if it is required by team policy. Now I am going to send current or similar patch to upstream and prepare packagewith minimal patch to stable proposed updates. I hope that release team willaccept such update. As for kde-gtk-config package in unstable, I think you will continue to updateit in the future with all other packages from KDE Workspace. [0] https://lists.debian.org/debian-mentors/2012/05/threads.html#00115[1] https://lists.debian.org/debian-mentors/2012/06/threads.html#00023[2] https://lists.debian.org/debian-mentors/2012/06/threads.html#00216 Best regards,Boris
Re: Qt 5.7.1 => 5.9.1
Hi, >>> Hello.>> Qt 5.9.1 hits unstable.>> Please be careful to wait till its complete. Even though>> and>> >> still says "partial", it appears those packages do exist for AMD64,>> and upgrade seems possible, as of right now...>> Chris>> Except for some KDE stuff like akonadi, so depending on what you have> installed apt might want to remove stuff.>> We are working on it. Is there any progress with qtcreator package? This is the only obstacle toupdating my system now. But I have not found bug reports related to Qt5.7.1 => 5.9.1 transition for it. Best regards,Boris
Re: plasma-systray-legacy replacement?
Hi, > I've been monitoring the "big upgrade" thats been rolling out, and the only > thing that seems to be blocking it on my desktop is a missing plasma-systray- > legacy package. Is that going to make it to the new kde packages? or is it > being discontinued? > > I find it very useful as there are still plenty of irreplaceable apps that > still use the old systray interface. https://bugs.debian.org/824528#10 Best wishes, Boris
Re: Workaround XDG_CURRENT_DESKTOP=KDE is broken
> After recent update of KDE Plasma 5 in Debian Sid all KF5-based programs use > wrong Qt theme when they are launched in non-KDE environment or via SSH. > They look ugly and all icons from buttons, menus and list items are missing. > And previously working workaround [1] is completely broken. > > Any idea which package is responsible for this? > > [1] > https://wiki.archlinux.org/index.php/qt#Configuration_of_Qt5_apps_under_environments_other_than_KDE Installation of "plasma-integration" package fixed this problem as well as it fixed a problem with "huge fonts and window decorations" from another thread. Best wishes, Boris
Workaround XDG_CURRENT_DESKTOP=KDE is broken
Hi, After recent update of KDE Plasma 5 in Debian Sid all KF5-based programs use wrong Qt theme when they are launched in non-KDE environment or via SSH. They look ugly and all icons from buttons, menus and list items are missing. And previously working workaround [1] is completely broken. Any idea which package is responsible for this? [1] https://wiki.archlinux.org/index.php/qt#Configuration_of_Qt5_apps_under_environments_other_than_KDE Best regards, Boris
Re: huge fonts and window decorations
Hi, > upgrading testing today left me with some fonts and the window decorations > being disproportionally big. For example, the sub heading in the application > launcher are much bigger than the actual headings, see screenshot > > https://imgur.com/8z6DU2K I have the same problem. Especially with Oxygen kwin theme, which I prefer. > Does anyone have an idea how to fix that? Unfortunately I have not found time for investigating this bug yet. Best wishes, Boris
Re: Kdeconnect 9.0 in SID
Hi Miguel, > I have recently contacted kdeconnect people and they told me they already > released version 9.0 like two months ago, they recommended me to contact > directly with debian package manteiners. I have searched about and there is > no news since August15, any idea where i should continue searching for info? Yes, it looks that previous maintainer is not active since August [1]. Lisandro has wrote a week ago that he is going to update this package [2]. Probably this will happen quite soon. [1] http://search.gmane.org/?query==david.sephirot%40gmail.com=date [2] http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2016-January/002280.html Best wishes, Boris
Re: KDE Plasma 5.5.3 in Debian?
Hi, > Is there some plan to add the newest KDE Plasma desktop (5.5.3) to > unstable / testing (current one is still 5.4.3) or there are some issues > with it that delay it? As I see there is progress in this direction [1][2]. Probably plasma will be updated in unstable soon after all build dependencies will pass NEW queue [3]. [1] https://tracker.debian.org/news/743831 [2] https://buildd.debian.org/status/package.php?p=plasma-desktop=experimental [3] https://ftp-master.debian.org/new.html Best wishes, Boris
Re: [Solved] Re: App Icons in Task Bar
>> I have the same problem but it changes after the reboot. After one >> reboot they are gone with the next some are back again. It's like >> roulette but with icons in the taskbar :-/ > > I was sent a solution (off-list). Thanks to Chris Dow for this; > > -8X- > I recently had this same problem with generic icons. This can be fixed > with a setting in the task manager. Right click on the task manager and > go to 'Task Manager Settings'. Then, uncheck 'Use launcher icons for > running applications'. > > -Chris > > -8X- > > So far I've not rebooted my system, so I'm unsure whether it's a > permanent solution, but I'm hopeful. It works fine! Thanks, Boris
Re: App Icons in Task Bar
Hi, > It did, however, give me the idea to try another user. One that had >> > never been used before. That user suffers the same taskbar icon >> > issues. So, possibly not a userland issue. :-( >> >> I have the same problem but it changes after the reboot. After one >> reboot they are gone with the next some are back again. It's like >> roulette but with icons in the taskbar :-/ > > For me they are consistently missing, mostly Java programs such as Eclipse or > Android Studio. I constantly see such taskbar behavior with Chromium icon. -- Boris
Re: plasma5 timeout with bluetooth
Hi, >> It sounds like this bug: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 > > Yes, thank you. This eventually explains why the bluetooth service is not > starting. > > But it does not explain why plasma5 is waiting 50 s for this service. > XFCE and cinnamon are starting just fine. So i can not understand why plasma5 > behaves like that. https://bugs.kde.org/show_bug.cgi?id=354230 https://git.reviewboard.kde.org/r/125785/ https://quickgit.kde.org/?p=plasma-nm.git=commit=48a45eb Best wishes, Boris
plasma-systray-legacy package is currently available in Debian unstable
Hi Debian and Ubuntu KDE users, Thanks a lot to David Edmundson who began xembed-sni-proxy project [1]. This program allows users of KDE Plasma 5 to use applications which supports only legacy system tray icons as simple as applications which support the SNI specification. xembed-sni-proxy is currently available in Debian unstable in the package plasma-systray-legacy [2]. Probably it is too late to add this package into official Ubuntu archive before Ubuntu Wily is released [3]. But users of Ubuntu Vivid and Ubuntu Wily may install this package from a special PPA [4]. I hope it should simplify the migration from KDE 4 to KDE Plasma 5 for usual users who don't know the difference between legacy system tray protocol (XEmbed) and new StatusNotifierItem specification, but who might be disappointed when some of programs will suddenly disappear from a "system tray" area after update of their system. If you have some issues with this program please report bugs at [5]. [1] http://blog.davidedmundson.co.uk/blog/xembed_back [2] https://packages.debian.org/sid/plasma-systray-legacy [3] https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule [4] https://launchpad.net/~tehnick/+archive/ubuntu/xembed-sni-proxy [5] https://github.com/davidedmundson/xembed-sni-proxy/issues Best wishes, Boris
Re: Kmail2 display garbled (after a while)
Hi Tim, > since I installed kde5 I have a kmail2 issue. > > After a while the kmail2 display window becomes drawn unreadable. > See this screenshot: > https://drive.google.com/open?id=0B_loju3MX2rTZlNOdDRxblVTWDg > > Stopping and starting kmail does not help. > Stopping and starting kdm helps for a while (until it suddenly happens again). > > I can't see anything obvious in 'dmesg' or .xsession-errors. Well I see lot's > of 'BadDrawable' messages, but these are not limited to kmail. > > I am on Debian SID with latest dist-upgrade, have the problem with kernel 4.1 > and 4.2 (didn't test any older kernels). Grafix is internal Intel i3 (Sandy > Bridge). > > Any ideas how to work around that or how to pin the problem ? $ ldd /usr/bin/kmail | grep QtGui libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f984cbb) kmail is currently built with old Qt4 based KDE libs. It looks that you have faced with issue from #800698. Please try to launch kmail from terminal and show the output. Best regards, Boris
Bug#800698: Kmail2 display garbled (after a while)
Hi Tim, > since I installed kde5 I have a kmail2 issue. > > After a while the kmail2 display window becomes drawn unreadable. > See this screenshot: > https://drive.google.com/open?id=0B_loju3MX2rTZlNOdDRxblVTWDg > > Stopping and starting kmail does not help. > Stopping and starting kdm helps for a while (until it suddenly happens again). > > I can't see anything obvious in 'dmesg' or .xsession-errors. Well I see lot's > of 'BadDrawable' messages, but these are not limited to kmail. > > I am on Debian SID with latest dist-upgrade, have the problem with kernel 4.1 > and 4.2 (didn't test any older kernels). Grafix is internal Intel i3 (Sandy > Bridge). > > Any ideas how to work around that or how to pin the problem ? $ ldd /usr/bin/kmail | grep QtGui libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f984cbb) kmail is currently built with old Qt4 based KDE libs. It looks that you have faced with issue from #800698. Please try to launch kmail from terminal and show the output. Best regards, Boris
Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems
Hi, >> control: retitle 800698 libqtgui4: GUI applications become unusable when >> shared memory is exhausted > > With this title I'm even more convinced that this is not a bug ;) Please read > below. This is only an assumption which is based on found bug reports in other projects. >> >> but hey, why Qt5 based and Gtk+ >> >> based programs were working without any issues in the same conditions? >> > >> > I do have an idea. Where those java applications creating an icon in the >> > taskbar? >> > >> > The only change that *might* be causing the problem here is the addition >> > of a patch that allows the systray to use sni-qt. >> >> At first look I do not see anything related to shared memory usage in patch >> [1]. >> >> [1] >> >> http://anonscm.debian.org/cgit/pkg-kde/qt/qt4-x11.git/tree/debian/patches/plugin_system_for_systemtray.patch?h=debian/4.8.7%2bdfsg-3 >> > Did any of the Java created a taskbar icon? >> >> If you had in mind a notification area, then yes, the most complex of these >> Java based programs creates an icon in system tray. And this icon is >> blinking when some events inside program trigger it. > > The only source change between the versions you mentioned in the original bug > report is that patch. And I know Qt4 is using (X-11-related?) shared memory to > draw things because I remember having to fix some permissions issues in past > releases (for Wheezy IIRC). > > I don't know why GTK doesn't fails, and I *guess* that Qt5 might be using some > OpenGL-related stuff that might make things go without problems. Yes, it looks that Qt4 uses X11 rendering by default. I have checked [1] and [2]. In the first case GUI rendering is broken and unusable and there are a lot of repeated X11 error messages in console [3]. But in the second case program looks more or less fine (only font in the main menu and in context menus looks ugly because of font hinting does not work here). [1] okular --graphicssystem raster [2] okular --graphicssystem opengl [3] The beginning of log from stderr: QNativeImage: Unable to attach to shared memory segment. X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 56 (X_ChangeGC) Resource id: 0x0 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 ... > Are you running sni-qt? If so maybe the bug is there, or at least related. I have removed sni-qt package and after reboot bug is still present. >> The main question is what to do with Qt4 libraries? >> >> Other Debian users may face to this bug because package default-jdk depends >> from openjdk-7-jdk in Debian Stretch. > > Well, if the memory gets exhausted is no wonder that Qt4 fails. Now I hardly > doubt that this is a bug in Qt4 due to the amount of testing the current > version has, after all it's just bug fixes from stable, and not many linux- > related precisely. And the behavior started with just a patch for sni-qt. > > If you have sni-qt installed I would definitely take a look there first. sni-qt does not cause to this bug. The problem is somewhere else. Unfortunately, I do not have cowbuilder environment for amd64 now thus I cannot rebuild qt4-x11 package without discussed patch for testing, but I have force installed libqtgui4/4:4.8.7+dfsg-1 from Debian snapshots archive [4] (yes, only this one package and nothing more) and after reboot I can reproduce the bug. So the problem is definitely not in the plugin_system_for_systemtray.patch. Probably an update in completely anoter package have lead to this bug. [4] http://snapshot.debian.org/archive/debian/20150526T221958Z/pool/main/q/qt4-x11/libqtgui4_4.8.7%2Bdfsg-1_amd64.deb > I'll leave the bug open tagged as moreinfo in case you want to reassign it, > else I'll close it in a couple of weeks, as nothing shows this is really a Qt4 > bug. I do not have any experience in Java and I do not have enough time and interest for investigating the bug in openjdk-7 dipper. Also we can do nothing from Qt4 side. And there is a known workaround. So this bug report might be closed now. Best regards, Boris
Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems
control: retitle 800698 libqtgui4: GUI applications become unusable when shared memory is exhausted Hi Lisandro, >> Today I had some a bit time for searching of possible root of this bug. >> And I have found similar bug report [1] for one of Qt4 based applications. >> >> [1] https://github.com/git-cola/git-cola/issues/482 >> >> When I have killed all openjdk-7 applications, my problem was solved. >> Then I have replaced openjdk-7* packages to openjdk-8* packages and all >> is working fine during few hours. >> >> It looks that problem is in openjdk-7, > > It might probably be. > >> but hey, why Qt5 based and Gtk+ >> based programs were working without any issues in the same conditions? > > I do have an idea. Where those java applications creating an icon in the > taskbar? > > The only change that *might* be causing the problem here is the addition of a > patch that allows the systray to use sni-qt. At first look I do not see anything related to shared memory usage in patch [1]. [1] http://anonscm.debian.org/cgit/pkg-kde/qt/qt4-x11.git/tree/debian/patches/plugin_system_for_systemtray.patch?h=debian/4.8.7%2bdfsg-3 > Did any of the Java created a taskbar icon? If you had in mind a notification area, then yes, the most complex of these Java based programs creates an icon in system tray. And this icon is blinking when some events inside program trigger it. > The reason why openjdk-8 *might* be working is that they might be using the > new protocol for the taskbar. No, Java applications launched with openjdk-8 still use legacy system tray. Also I have tested openjdk-6 and in this case all Qt4 based applications worked fine too. So bug is present only when openjdk-7 is used for Java programs. (Though I haven't tested openjdk-9 from experimental yet.) The main question is what to do with Qt4 libraries? Other Debian users may face to this bug because package default-jdk depends from openjdk-7-jdk in Debian Stretch. Best regards, Boris
Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems
Hi, Today I had some a bit time for searching of possible root of this bug. And I have found similar bug report [1] for one of Qt4 based applications. [1] https://github.com/git-cola/git-cola/issues/482 When I have killed all openjdk-7 applications, my problem was solved. Then I have replaced openjdk-7* packages to openjdk-8* packages and all is working fine during few hours. It looks that problem is in openjdk-7, but hey, why Qt5 based and Gtk+ based programs were working without any issues in the same conditions? I do not know what to do with this bug report further. Any ideas? Best regards, Boris
Problem with dolphin package on buildd amd64 (brahms)
Hi everyone, As we can see at [1][2] something strange had happened during building of dolphin package on buildd amd64 (brahms). Could you look on this? [1] https://buildd.debian.org/status/package.php?p=dolphin=unstable [2] https://buildd.debian.org/status/fetch.php?pkg=dolphin=amd64=4%3A15.08.1-1=1442854331 Best regards, Boris
Issue with icons in KF5 based applications launched via ssh
Hi, After upgrading my remote host from KDE 4 to KDE Plasma 5 I have faced with strange behavior of programs built with KF5: all of them lose icons in menus, toolbars and other widgets when you connect via ssh 'ssh -X ...' and launch them in usual way. All applications based on KDE4 libs and Qt4, on pure Qt5, on Gtk+ 2.x and Gtk+ 3.x look fine. Any idea which is wrong in KF5 libraries and how it could be fixed? If bug report is required, which package it should point to? Best regards, Boris
Re: Problem with dolphin package on buildd amd64 (brahms)
Hi, >>> As we can see at [1][2] something strange had happened during building of >>> dolphin package on buildd amd64 (brahms). Could you look on this? >> >> It looks strange indeed, no idea what happened to the log. I gave >> it back, let's see what happens. > > It ran out of disk space. I've stopped brahms. And now this package is built successfully for amd64. Thanks a lot. Best regards, Boris
Re: Reinstall KDE completely
Hi, > The problem is that there is a lot of new config files on .local and .config > with kf5 on it, and kde-full only removes what was installed with the > metapackage. There are tons of kde5 packages laying around that removing > kde-full will not remove. Any ideas? sudo apt-get autoremove --purge Best wishes, Boris
Bug#799146: FTBFS on hurd
Source: sddm Version: 0.12.0-1 Severity: normal Hi, As we can see in logs[1] sddm/0.11.0 packages were built fine on hurd. But since sddm/0.12.0-1 these builds are broken. Please report bug to upstream. [1] https://buildd.debian.org/status/logs.php?pkg=sddm=hurd-i386 Best regards, Boris
Bug#799147: FTBFS on kfreebsd
Source: sddm Version: 0.12.0-1 Severity: normal Hi, As we can see in logs[1][2] sddm/0.11.0 packages were built fine on kfreebsd. But since sddm/0.12.0 these builds are broken. Please report bug to upstream. While Debian GNU/kFreeBSD is not officially supported[3] the severity of this issue is normal. But it would be nice to bring back the official support of kfreebsd in the next stable release of Debian. [1] https://buildd.debian.org/status/logs.php?pkg=sddm=kfreebsd-i386 [2] https://buildd.debian.org/status/logs.php?pkg=sddm=kfreebsd-amd64 [3] https://lists.debian.org/debian-devel-announce/2014/11/msg5.html Best regards, Boris
Bug#799142: sddm: fails to build architecture independent packages
Source: sddm Version: 0.12.0-3 Severity: serious Dear maintainer, Recently you have done source-only upload of sddm/0.12.0-3 package. Unfortunately this package is not yet ready for building of architecture independent packages separately[1], therefor sddm-theme-maui, sddm-theme-circles, sddm-theme-elarun and sddm-theme-maldives packages are currently unavailable in Debian unstable. [1] https://buildd.debian.org/status/fetch.php?pkg=sddm=all=0.12.0-3=1442259701 Please fix this FTBFS or upload package in usual way. You may test architecture independent builds using something like this: dpkg-buildpackage -rfakeroot -A Best regards, Boris
Re: Gimp
Hi. > I have 3 Sid systems 2 had gimp installed and one didn't, I was able to > get a full upgrade on the one without gimp and then install gimp. > > On the systems with gimp I was not able to get a full upgrade, so I > removed gimp and then did a full upgrade and then I was able to > reinstall gimp. I would recommend always upgrade your systems in two steps: sudo apt-get upgrade -V sudo apt-get dist-upgrade -V In most cases such update will be more smooth. Best wishes, Boris
Re: qdbus commands in 64-bit jessie?
Hi, >> I'm no expert on multi-arch but those could be reasons >> why running qdbus wants to use i386 version. > > This is a 64-bit system, so I am unclear why multi-arch is involved at all. > Any non-64-bit programs were put there by the debian upgrade procedure, not > by me. This is not true. See below. >> You can list all i386 packages with dpkg -l *:i386 > > > > [HN:~] dpkg -l *:i386 > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-===-==-==- > ... > ii acroread 9.5.5-dmo2 i386 Adobe > Acrobat Reader: Portable Document Format file viewer > ... > ii qtchooser 47-gd2b7997-2 i386 Wrapper > to select between Qt development binary versions > ... > ii skype 4.2.0.11-1 i386 Wherever > you are, wherever they are > ... > ii wine-bin 1.6.2-20 i386 Windows > API implementation - binaries > ii wine32 1.6.2-20 i386 Windows > API implementation - 32-bit binary loader > ... You have installed these 32-bit packages manually. And these few packages have pulled all other packages with 32-libraries which they are depend on. Best wishes, Boris
Re: qdbus commands in 64-bit jessie?
> It is true. But we are being dragged down a rabbit hole, and I don't see the > point of arguing how various things got on my system. qdbus worked prior to > the upgrade, and now it doesn't, so the question remains: > What do I need to do to get my qdbus commands working again? > > The upgrade obviously broke something related to qdbus, but I don't understand > at all how to fix it. $ ls -alp `which qdbus` $ dpkg -l | grep qtchooser $ sudo apt-get install qtchooser:amd64 $ dpkg -l | grep qtchooser $ qdbus org.kde.yakuake /yakuake/sessions runCommandInTerminal $SESSION_ID "tmux" Best wishes, Boris
Re: black icons after kde upgrade
Hi, > Yes the background is also black. > I try to change the background image but nothing happend. 1) Try to set OpenGL 2.0 or XRender for Desktop Effects in System Settings. 2) Try to disable Desktop Effects: Shift + Alt + F12. -- Boris
Re: Systray plasma 5
Hi everyone, An other subject, I have hp toolbox complaining about the lake of systray in plasma5. I have seen some blog post's explaining the new plasma status model, but only kde/plasma apps are adopting that... Is there any solution to have the bad and ugly old solution to make old application or not kde/plasma apps to work ? According to http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/ the wmsystemtray application could provide an XEmbed based systemtray. As for me wmsystemtray and stalonetray looks quite ugly. I would recommend to try lxpanel. It may be even used instead of plasma panel. Personally I use plasma panel + lxpanel [1][2] with own plasma theme [3]. [1] http://kde-look.org/CONTENT/content-pre1/112767-1.png [2] http://kde-look.org/CONTENT/content-pre2/112767-2.png [3] http://kde-look.org/content/show.php/Serious?content=112767 Plasmoids were added on desktop only for screenshots. Unfortunately they are currently unusable due to too high CPU usage (about 30-50% of each CPU core). Hope this helps. Best wishes, Boris -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1856061438676...@web22g.yandex.ru
Re: Install on stretch : feedback
Hi, - no possibility to have different virtual desktops I verify this. But the Pager Widget *is there*. You can find it in the widget list (Add Widgets - Pager). When you drag it on the panel, however, nothing happens. This looks like a bug. It looks like you have only one virtual desktop. So just add yet one or more in System Settings. Also I think that previous sender had in mind completely another issue. Best wishes, Boris -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/726681438692...@web10o.yandex.ru
Bug#767352: qtbase-opensource-src: keyboard shortcuts don't work in multi-language mode
Source: qtbase-opensource-src Version: 5.3.2+dfsg-4 Severity: normal Tags: upstream fixed-upstream Hi, Keyboard shortcuts don't work in multi-language mode and it is quite inconvenient to use Qt5-based applications in Debian now. For example, Qt Creator. Bug report in upstream: https://bugreports.qt-project.org/browse/QTBUG-32274 This problem was fixed in 5.4 branch of qtbase git repo: https://qt.gitorious.org/qt/qtbase/commit/2b666d9 Is it possible to apply this fix in Qt5 packages before Jessy release? Best regards, Boris -- 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/1501691414671...@web2m.yandex.ru
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
control: tags 719064 + patch Hi, Please read the whole discussion about this patch: https://codereview.qt-project.org/#change,64283 https://codereview.qt-project.org/#patch,all_unified,64283,1 Upstream does not have objections about this (trivial) patch itself. (This is just a revert of destructive commit which was done earlier.) Upstream only calls for more detailed commit message. So why do we need to wait until this commit message will be rewritten? Because if I apply the patch and it causes problems, I need to go to upstream. And then upstream will tell me this patch hasn't been accepted yet, you are on yourself. That's the reason. I understand how this rule is useful in common practice. But not in this specific case. On the other hand, we the Debian Qt/KDE team do not want people not listed in Uploaders pushing stuff to our repos, except if a team member explicitely allows it. Moreover, we try to avoid topic branches for fixes like this. Next time please attach a patch. I have just deleted the branch in the repo. Ok. See attachment. ACK, but please don't override a maintainer decision without asking first. This same patch has not been accepted upstream yet, so we don't have an available patch yet. I'm thus unttaging the bug as with available patch. https://qt.gitorious.org/qt/qt/commit/0c03af0 Best regards, Boris -- 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/44291379054...@web20h.yandex.ru
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
https://qt.gitorious.org/qt/qt/commit/0c03af0 Updated patch is in attachment. Origin field was changed: now it points to the commit in primary Git repo. Best regards, Boris From bc1e27e7224f5b4faff7a60ba756d3209f74e172 Mon Sep 17 00:00:00 2001 From: Boris Pek tehnic...@yandex.ru Date: Sun, 1 Sep 2013 19:18:54 +0300 Subject: [PATCH] Add fix-keyboard-shortcuts-in-multi-language-mode.patch --- .../fix-keyboard-shortcuts-in-multi-language-mode.patch | 17 + debian/patches/series | 1 + 2 files changed, 18 insertions(+) create mode 100644 debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch diff --git a/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch b/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch new file mode 100644 index 000..b88ed86 --- /dev/null +++ b/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch @@ -0,0 +1,17 @@ +Description: fix keyboard shortcuts in multi-language mode +Origin: https://qt.gitorious.org/qt/qt/commit/0c03af0 +Bug: https://bugreports.qt-project.org/browse/QTBUG-32908 +Bug-Debian: http://bugs.debian.org/719064 + +diff --git a/src/gui/kernel/qkeymapper_x11.cpp b/src/gui/kernel/qkeymapper_x11.cpp +--- a/src/gui/kernel/qkeymapper_x11.cpp b/src/gui/kernel/qkeymapper_x11.cpp +@@ -287,7 +287,7 @@ + // See https://bugreports.qt-project.org/browse/QTBUG-15319 . + KeySym baseKeySym; + uint consumedModifiers; +-if (!XkbLookupKeySym(X11-display, xkeycode, (xmodifiers (0xff00 | LockMask | qt_num_lock_mask)), ++if (!XkbLookupKeySym(X11-display, xkeycode, (xmodifiers (LockMask | qt_num_lock_mask)), + consumedModifiers, baseKeySym)) + return QListint(); + diff --git a/debian/patches/series b/debian/patches/series index 286d023..98fb068 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -44,3 +44,4 @@ no_libicu_message.diff QTBUG-25324_assistant_segfault_on_start_with_gcc_4.7.patch qt-everywhere-opensource-src-4.8.5-QTBUG-22829.patch qtdoc-build-offline-docs.patch +fix-keyboard-shortcuts-in-multi-language-mode.patch -- 1.8.4.rc3
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
control: tags 719064 + patch Hi, As long as upstream does not ACK the patches we will not apply them in Debian. Looking at https://codereview.qt-project.org/#change,64283 it seems that the patch has been not accepted. If you are interested in this fix, please work with upstream to solve it. I will happily apply it once upstream positively acknowledges it. Please read the whole discussion about this patch: https://codereview.qt-project.org/#change,64283 https://codereview.qt-project.org/#patch,all_unified,64283,1 Upstream does not have objections about this (trivial) patch itself. (This is just a revert of destructive commit which was done earlier.) Upstream only calls for more detailed commit message. So why do we need to wait until this commit message will be rewritten? On the other hand, we the Debian Qt/KDE team do not want people not listed in Uploaders pushing stuff to our repos, except if a team member explicitely allows it. Moreover, we try to avoid topic branches for fixes like this. Next time please attach a patch. I have just deleted the branch in the repo. Ok. See attachment. Best regards, Boris From bc1e27e7224f5b4faff7a60ba756d3209f74e172 Mon Sep 17 00:00:00 2001 From: Boris Pek tehnic...@yandex.ru Date: Sun, 1 Sep 2013 19:18:54 +0300 Subject: [PATCH] Add fix-keyboard-shortcuts-in-multi-language-mode.patch --- .../fix-keyboard-shortcuts-in-multi-language-mode.patch | 17 + debian/patches/series | 1 + 2 files changed, 18 insertions(+) create mode 100644 debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch diff --git a/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch b/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch new file mode 100644 index 000..b88ed86 --- /dev/null +++ b/debian/patches/fix-keyboard-shortcuts-in-multi-language-mode.patch @@ -0,0 +1,17 @@ +Description: fix keyboard shortcuts in multi-language mode +Origin: https://codereview.qt-project.org/#change,64283 +Bug: https://bugreports.qt-project.org/browse/QTBUG-32908 +Bug-Debian: http://bugs.debian.org/719064 + +diff --git a/src/gui/kernel/qkeymapper_x11.cpp b/src/gui/kernel/qkeymapper_x11.cpp +--- a/src/gui/kernel/qkeymapper_x11.cpp b/src/gui/kernel/qkeymapper_x11.cpp +@@ -287,7 +287,7 @@ + // See https://bugreports.qt-project.org/browse/QTBUG-15319 . + KeySym baseKeySym; + uint consumedModifiers; +-if (!XkbLookupKeySym(X11-display, xkeycode, (xmodifiers (0xff00 | LockMask | qt_num_lock_mask)), ++if (!XkbLookupKeySym(X11-display, xkeycode, (xmodifiers (LockMask | qt_num_lock_mask)), + consumedModifiers, baseKeySym)) + return QListint(); + diff --git a/debian/patches/series b/debian/patches/series index 286d023..98fb068 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -44,3 +44,4 @@ no_libicu_message.diff QTBUG-25324_assistant_segfault_on_start_with_gcc_4.7.patch qt-everywhere-opensource-src-4.8.5-QTBUG-22829.patch qtdoc-build-offline-docs.patch +fix-keyboard-shortcuts-in-multi-language-mode.patch -- 1.8.4.rc3
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
control: tags 719064 + patch Hi, I have prepared the patch for the package [1]. Please, consider applying it. This bug is extremely annoying... [1] http://anonscm.debian.org/gitweb/?p=pkg-kde/qt/qt4-x11.git;a=commitdiff;h= I am not sure that you will accept this patch, so I pushed it into temporary Git branch fix-shortcuts. Best regards, Boris -- 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/256251378065...@web14m.yandex.ru
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
Sorry. Here is the correct link: http://anonscm.debian.org/gitweb/?p=pkg-kde/qt/qt4-x11.git;a=commitdiff;h=bc1e27e -- 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/263781378066...@web14m.yandex.ru
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
control: tags 719064 + upstream control: forwarded 719064 https://bugreports.qt-project.org/browse/QTBUG-32908 QTBUG-32274 was for Qt 5.x series. Here is a separate bug for Qt 4.x: https://bugreports.qt-project.org/browse/QTBUG-32908 -- 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/41001377083...@web19g.yandex.ru
Bug#719064: qt4-x11: keyboard shortcuts don't work in multi-language mode
Source: qt4-x11 Version: 4:4.8.5+dfsg-2 Severity: normal Hi, Keyboard shortcuts don't work in multi-language mode. It is extremely inconvenient to use KDE and Qt applications now. Bug was introduced in Qt 4.8.5. Related links: https://bugs.kde.org/show_bug.cgi?id=309193 https://bugreports.qt-project.org/browse/QTBUG-32274 Please add the patch to the package when it is available. Best regards, Boris -- 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/153681375945...@web6g.yandex.ru
Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy
Hi, To me there's two issues/fixes: 1) make KDM correctly handle the case where the selected theme is gone That should already be covered. We have a palceholder, namely Theme=@@@ToBeReplacedByDesktopBase@@@ in /etc/kde4/kdm/kdmrc (Boris could you check that?) which is substituted by kdm's init.d script. The setting is replaced with values from /etc/default/kdm.d/10_desktop-base. So it might have failed in this case. I've added Boris to CC so he actually has a chance to check. Unfortunately, I deleted testing system from VirtualBox. Now I can check only on my laptops. Here are some results: $ grep Theme= /etc/kde4/kdm/kdmrc Theme=/usr/share/kde4/apps/kdm/themes/joy UseTheme=true $ grep ToBeReplacedByDesktopBase /etc/kde4/kdm/kdmrc | wc -l 0 $ ls /etc/default/kdm.d/ 10_desktop-base 20_debian-edu $ cat /etc/default/kdm.d/10_desktop-base USETHEME=true THEME=/usr/share/kde4/apps/kdm/themes/joy WALLPAPER=/usr/share/kde4/apps/kdm/themes/joy/background.png $ cat /etc/default/kdm.d/20_debian-edu USETHEME=true THEME=/usr/share/kde4/apps/kdm/themes/debian-edu USEBACKGROUND=true WALLPAPER=/usr/share/wallpapers/debian-edu-wallpaper01_1600x1200.png Did I miss anything? So you always should end up with the theme currently installed, since the setting and kdm theme come from the same package (desktop-base). I have more KDM themes than there are available in package desktop-base: $ ls /usr/share/kde4/apps/kdm/themes/ ariya circles debian-edu horos joy oxygen oxygen-air Any theme from this list could be chosen in KDE System Settings dialog. And if after regular system update such theme will be removed from system KDM will fails to start. I believe it should be anyhow prevented. I admit that the whole process is a bit messy and I probably miss something, since this all was set before I was involved. Can you at least try to reproduce the issue? Yes, sure. Regards, Boris
Bug#694011: desktop-base: problem after updating from Squeeze to Wheezy
$ grep Theme= /etc/kde4/kdm/kdmrc Theme=/usr/share/kde4/apps/kdm/themes/joy This shouldn't be there. Did you manually change this? It should be Theme=@@@ToBeReplacedByDesktopBase@@@. I am not sure that you call manually. I do not use text editor to change that theme, but use standard program KDE System Settings. And it updates related configuration files. Do you think this bug should be reassigned to package systemsettings? I still believe that KDM should check if current theme exist. If it is not found KDM may be launched with default theme. Any objections? But now KDM just fails to run with a message that theme is not exist. And user should repair his system from command line. It is not hard, but it can be avoided. It seems, that you have the debian-edu-artwork package installed, maybe the issue is realated to the squeeze version of it? Yes I used themes from Debian Edu some time ago. But new theme Joy looks better and it is selected now. But this is far from the topic above. That would explain why this bugreport has not been filed earlier. This does not explain why bug can be reproduced in clean install. There was no package debian-edu-artwork there. Regards, Boris
Bug#673684: kde-l10n: Translations for zanshin are missed
Package: kde-l10n Version: 4:4.7.4-2 Severity: normal Tags: l10n Hi, As I see translations for zanshin are not in kde-l10n-* packages yet [1]. But they already available in KDE subversion repository. For example, Russian translation is complete [2][3]. Could you add available translations into your packages? Best regards, Boris [1] http://packages.debian.org/search?suite=wheezysection=allarch=anysearchon=contentskeywords=zanshin [2] http://websvn.kde.org/trunk/l10n-kde4/ru/messages/playground-pim/zanshin.po?view=markup [3] http://websvn.kde.org/trunk/l10n-kde4/ru/messages/playground-pim/desktop_playground-pim_zanshin.po?view=markup
