Bug#1013896: qtbase-opensource-src: Use KDE Qt as upstream instead of qt.io

[Hillel Lubman]

On Wed, 13 Jul 2022 21:02:02 +0300 Dmitry Shachnev 
wrote:
>
> I expect users to complain if something doesn't work.
>
> Also note that now we get releases from Qt every couple of months, so
sooner
> or later we will get most of the patches this way (and it will be easier
to
> deal with the remaining ones).
>

Eventually yeah, but it can be a long while because a bunch of these
patches are
backports from Qt 6 by the KDE team and upstream Qt doesn't bother to
backport
to 5.x.

Shmerl.

Bug#939472: Further fixes?

[Hillel Lubman]

Falling back to gcc 8 is a workaround for this, but what is the
required fix for gcc 9 and further going forward?

Bug#928631:

[Hillel Lubman]

Hi.

20190502-1 is already outdated, since amdgpu firmware had some updates upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu

Does this problem still occur if you use latest upstream firmware?

By the way, it works well for me (Ryzen 7 2700X / Vega 56), but I'm running 
kernel 5.2.1
in Debian testing.

Best regards,
Hillel Lubman.

Bug#926825: faudio: FTBFS (Missing build-dependency on cmake)

[Hillel Lubman]

This also prevents i386 version from being built, which in turn blocks using 
newer 32-bit Wine which now depends on faudio.

Please re-upload the package with build-depends for cmake, and you can as well 
use the newest version:  19.04.

Regards,
Hillel Lubman.

Bug#916587: AppArmor breaks virtio-gpu + virgl

[Hillel Lubman]

How exactly do you see these logs?

I'm trying to start a Linux guest on Debian testing host, using virt-manager 
and user session.
I enabled OpenGL and 3D acceleration and it fails like this:

Error starting domain: internal error: qemu unexpectedly closed the monitor

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1400, in startup
self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor

When OpenGL isn't enabled, it starts fine.  I have libvirglrenderer0 installed. 
I wonder if it's related to the above apparmor issue.

Editing  /etc/apparmor.d/libvirt/TEMPLATE.qemu didn't help in my case either.

Regards,
Hillel Lubman.

Bug#898092: Status of this bug

[Hillel Lubman]

On Mon, 23 Jul 2018 10:30:06 -0300 Lisandro Damián Nicanor Pérez Meyer wrote:
> This has happened so far:
> 
> From the Debian side maxy added haveged as a sddm recommendation and as a 
> workaround.
> 

Should it better recommend rng-tools5? It's a better quality entropy generator 
that's
more suitable especially for hardware with rdrand CPU feature or TPM module.

Regards,
Hillel.

Bug#903919: plasma-browser-integration: Description shouldn't be limited to chromium

[Hillel Lubman]

Package: plasma-browser-integration
Version: 5.13.1-1
Severity: normal

Currently the description says: "Chromium integration for Plasma"

It's intended to be used with multiple browsers, including Firefox, so the
description should be more generic. Something like:

"Web browsers integration for the Plasma desktop".

See:

https://github.com/KDE/plasma-browser-integration
https://community.kde.org/Plasma/Browser_Integration



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

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

Versions of packages plasma-browser-integration depends on:
ii  kio   5.47.0-1
ii  kpackagetool5 5.47.0-1
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-9
ii  libkf5activities5 5.47.0-1
ii  libkf5completion5 5.47.0-1
ii  libkf5configcore5 5.47.0-1
ii  libkf5coreaddons5 5.47.0-1
ii  libkf5dbusaddons5 5.47.0-1
ii  libkf5i18n5   5.47.0-1
ii  libkf5jobwidgets5 5.47.0-1
ii  libkf5kiocore55.47.0-1
ii  libkf5kiowidgets5 5.47.0-1
ii  libkf5notifications5  5.47.0-1
ii  libkf5package55.47.0-1
ii  libkf5plasma5 5.47.0-1
ii  libkf5runner5 5.47.0-1
ii  libkf5service-bin 5.47.0-1
ii  libkf5service55.47.0-1
ii  libkf5widgetsaddons5  5.47.0-1
ii  libkf5windowsystem5   5.47.0-1
ii  libqt5concurrent5 5.10.1+dfsg-7
ii  libqt5core5a  5.10.1+dfsg-7
ii  libqt5dbus5   5.10.1+dfsg-7
ii  libqt5gui55.10.1+dfsg-7
ii  libqt5network55.10.1+dfsg-7
ii  libqt5widgets55.10.1+dfsg-7
ii  libstdc++68.1.0-9

plasma-browser-integration recommends no packages.

plasma-browser-integration suggests no packages.

-- no debconf information

Bug#898210: fio: libaio engine isn't enabled on Linux

[Hillel Lubman]

Package: fio
Version: 3.5-1
Severity: normal

Despite specifying libaio-dev [!linux-any] in control file, somehow libaio-dev
fails to be installed during the package build, and becasue of that libaio
engine is disabled in currently packaged fio for Linux.

Please enable libaio during build for the engine to be included.



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

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

Versions of packages fio depends on:
ii  glusterfs-common 4.0.2-1
ii  init-system-helpers  1.51
ii  libaio1  0.3.111-1
ii  libc62.27-3
ii  libibverbs1  17.1-2
ii  libnuma1 2.0.11-2.2
ii  librados210.2.5-7.2
ii  librbd1  10.2.5-7.2
ii  librdmacm1   17.1-2
ii  python2.72.7.15-1
ii  zlib1g   1:1.2.11.dfsg-1

fio recommends no packages.

Versions of packages fio suggests:
pn  gfio  
pn  gnuplot   
pn  python-scipy  

-- no debconf information

Bug#813658: Further progress?

[Hillel Lubman]

Is there anything else needed to move this forward?

Regards,
Hillel Lubman.

Bug#804857: CONFIG_RCU_NOCB_CPU?

[Hillel Lubman]

On Thu, 12 Nov 2015 17:29:35 + Ben Hutchings  wrote:
>
> But for other configurations it is worse:
> 
> config NO_HZ_FULL
> bool "Full dynticks system (tickless)"
> ...
>  This is implemented at the expense of some overhead in user <-> 
> kernel
>  transitions: syscalls, exceptions and interrupts. Even when it's
>  dynamically off.
> 
>  Say N.
> 
> I think we should enable this for the rt featureset when it's next
> available, but not by default.
> 
> Ben.

What about CONFIG_RCU_NOCB_CPU? There is currently a nasty hardware freeze / 
reboot bug that
affects AMD Ryzen CPUs on Linux: 
https://bugzilla.kernel.org/show_bug.cgi?id=196683[1] 

Many report, that setting rcu-nocbs kernel parameter works around it at least 
partially, but it requires
the kernel to be built with CONFIG_RCU_NOCB_CPU=Y. Can it be enabled in Debian, 
or there are reasons
not to do it?

Thanks!
Hillel.


[1] https://bugzilla.kernel.org/show_bug.cgi?id=196683

Bug#890801: libc6-i386 conflicts with libc6-amd64:i386

[Hillel Lubman]

Package: libc6-i386
Version: 2.26-6
Severity: important

Dear Maintainer,

I tried cross compile 32-bit Mesa on 64-bit Debian (amd64), and I had to
install these packages in order to do it:

llvm-5.0-dev:i386 libclang-5.0-dev:i386 gcc-multilib g++-multilib

Unfortunately it failed, and I managed to narrow it down to the conflict
between libc6-i386 conflicts and libc6-amd64:i386:

sudo apt-get install libc6-amd64:i386 libc6-i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libc6-amd64:i386 : Conflicts: libc6-i386 but 2.26-6 is to be installed
 libc6-i386 : Conflicts: libc6-amd64:i386 but 2.26-6 is to be installed
E: Unable to correct problems, you have held broken packages.

How can this be resolved?



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

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

Versions of packages libc6-i386 depends on:
ii  libc6  2.26-6

libc6-i386 recommends no packages.

libc6-i386 suggests no packages.

Bug#890778: RFP: plasma-browser-integration -- Components necessary to integrate browsers into the Plasma Desktop.

[Hillel Lubman]

Package: wnpp
Severity: wishlist

* Package name: plasma-browser-integration
  Version : git/master
* URL : https://github.com/KDE/plasma-browser-integration
* License : GPLv3
  Programming Lang: C++
  Description : Components necessary to integrate browsers into the Plasma
Desktop.

Provides better browser integration with the KDE Plasma 5 desktop, including
Firefox which is otherwise integrated quite poorly.

See also add-on which is needed to be used in the browser in conjunction:
https://addons.mozilla.org/en-US/firefox/addon/plasma-integration/

Bug#813658: Further progress?

[Hillel Lubman]

On Fri, 19 Jan 2018 09:24:48 +0300 Michael Tokarev <m...@tls.msk.ru> wrote:
> Can someone please tell me what _is_ virglrenderer?
> 
> Is it useful on its own with, eg, spice, and/or libvirt,
> without local UI frontends like GTK or SDL?
> 
> What it provides?

The actual project is described here:  https://virgil3d.github.io[1] 
>From the description it appears to be made for Qemu specifically.

Here is another description:

/The virgil3d rendering library is a library used by qemu to implement/
/3D GPU support for the virtio GPU./

but I'm not an expert on it, so not sure whether it can be somehow useful on 
its own.

Looking at how other distros package things, for example Arch provides two 
packages

https://www.archlinux.org/packages/extra/x86_64/qemu/[2] 
https://www.archlinux.org/packages/extra/x86_64/qemu-headless/[3] 

Regular one depends on virglrenderer, while the headless one doesn't. I suppose
they were trying to solve the same issue.

Regards,
Hillel Lubman.






[1] https://virgil3d.github.io
[2] https://www.archlinux.org/packages/extra/x86_64/qemu/
[3] https://www.archlinux.org/packages/extra/x86_64/qemu-headless/

Bug#884466: Is this still an issue?

[Hillel Lubman]

Original bug reporter didn't get back to confirm the bug, and others report it 
as working
fine now. May be severity should be lowered at least until it's confirmed?

Regards,
Hillel Lubman.

Bug#813658: Further progress?

[Hillel Lubman]

Now Debian already ships spice 0.14.0, so with this dependency issue out of the 
way, what else is needed
to enable virgl support in qemu? Should packages be split in some way to 
provide a headless variant for
those who only care about server side qemu usage and don't want many 
dependencies?

Regards,
Hillel Lubman.

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Hillel Lubman]

On Fri, Sep 29, 2017 at 07:21:42AM +0200, Dominik Kupschke wrote::
> This issue affects all of my steam games (> 100), so the migration of the 
> packet to testing could be bad for a lot of people.

Could it be a problem with Steam runtime? Their bundling is known to be messy, 
like conflicting libstdc++ which clashes with
libgl1-mesa-dri (radeonsi_dri.so is using libstdc++, and if Steam runtime 
bundles it, it can easily break C++ ABI compatibility). Similar stuff can
happen to other libraries.

Basically, can you run any game without Steam runtime? Try some of the same 
games from GOG, which come without Steam runtime,
or figure out how to run such game directly without Steam client and full 
runtime LD_LIBRARY_PATH. Since you you saying a lot
of games are broken in the similar way, it's very likely Steam runtime is the 
culprit. If that is indeed the case, it's not really
Mesa's or Debian's problem, and Steam runtime itself needs fixing.

Regards,
Hillel Lubman.

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Hillel Lubman]

Should such bugs be a blocker? Other games work fine with this Mesa. 
This stalls
migration of the package to testing for a lot of people. Just for the 
reference,
if you need a specific Mesa, you can always use older one locally 
(without touching

the system wide package) and run some game with it.

I don't think it's good to stall the package because of this for 
everyone else.

The severity here should be probably important, not grave.

Regards,
Hillel Lubman.

Bug#855173: ITP status?

[Hillel Lubman]

On Thu, 10 Aug 2017 06:37:58 -0400 Julian Andres Klode  wrote:

> I basically prepared the debian/copyright list of things to
> add / change, but did not actually update it yet.

Hi Julian.

Do you still plan to package it? It would really be nice to finally see 
keepassxc in Debian (unstable and testing).
Thanks!

Hillel Lubman.

Bug#864529: irmware-amd-graphics: missing firmware for AMD Radeon RX 560,570,580

[Hillel Lubman]

I just installed fresh Debian testing, and was bitten by this bug. The system 
hangs on boot because of it.
(I'm using AMD RX 560). It took me some time to figure out what's going on and 
find this report.

Please add the missing firmware - it's quite a major system breaking bug for 
users of AMD RX 5xxx,
and it should be higher severity than important. 

Thanks,
Hillel Lubman.

Bug#869400: wayland-protocols: Package newer version (1.9) from upstream

[Hillel Lubman]

Package: wayland-protocols
Version: 1.7-1
Severity: wishlist

Dear Maintainer,

Recent Mesa master started requring wayland-protocol 1.8 or higher to build,
so it's not building on Debian anymore as is. Please package the newest version.

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#852765: Workaround for netcat-opebsd issue

[Hillel Lubman]

Hi.

I encountered this issue recently on Debian testing as well, and found this 
bug. Uninstalling netcat-openbsd didn't sound
like a good idea, so I found this issue opened for it: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849192[1] 

Basically, nc -q behaves differently and can hang now. Replacing it with nc -N 
can work around it. nc is used in
/usr/share/playonlinux/lib/setupwindow.lib

Replace nc -q with nc -N there, and POL will work fine with netcat-openbsd as 
well.

I attach a patch with that fix.

Regards,
Hillel Lubman.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849192
--- setupwindow.lib	2017-02-08 21:55:43.0 -0500
+++ setupwindow.lib_fixed	2017-02-08 21:52:49.0 -0500
@@ -39,7 +39,7 @@
 	if [ "$POL_OS" = "Mac" -o "$(POL_Config_Read FORCE_LEGACY_NETCAT)" = "TRUE" ]; then
 		nc "$@"
 	else
-		nc -q -1 "$@" 2> /dev/null || nc "$@"
+		nc -N -1 "$@" 2> /dev/null || nc "$@"
 		# Differents possibilities
 	fi
 }

Bug#813658: Now getting: This QEMU doesn't support spice OpenGL

[Hillel Lubman]

Hi.

I'm on current Debian testing, and have:

qemu-*: 1:2.8+dfsg-1
libvirt0: 2.5.0-3 
libvirglrenderer0: 0.5.0-1
virt-manager: 1:1.4.0-5
libspice-server1: 0.13.3-1 (installed from: 
https://github.com/adlererik/spice-virgl/releases ).

And I set in my VM configuration:


  
  

...

  
  


When starting the VM from virt-manager, I however get:

Error starting domain: unsupported configuration: This QEMU doesn't support 
spice OpenGL

The strange thing is, until recent update of libvirt*, it was starting, but 
initialization of virgl didn't work for some reason (I didn't yet figure out 
why, it was falling back to llvmpipe). Now it doesn't even start at all. What 
am I doing wrong, or there are some changes to libvirt now that have to be 
addressed?

Thanks!

Bug#848076: openconnect 7.07 fails to connect to latest Pulse / Juniper VPN

[Hillel Lubman]

On Sat, 24 Dec 2016 11:11:58 -0800 Mike Miller wrote:
> Can you please test with 7.08-1 which will be available in the archive
> soon? Does 7.08-1 fix the problem you were having with 7.07-1?

I just tested it with 7.08-1 from unstable, and it fixes the problem.

Thanks!
Hillel.

Bug#848076: openconnect 7.07 fails to connect to latest Pulse / Juniper VPN

[Hillel Lubman]

Package: openconnect
Version: 7.07-1
Severity: important

openconnect 7.07 stopped working with latest release of Pulse/Juniper VPN.
See http://lists.infradead.org/pipermail/openconnect-
devel/2016-November/004052.html

This is fixed in 7.08 which was released recently. Please update it in Debian
to the latest release to fix this bug.

Thanks!



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

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openconnect depends on:
ii  libc62.24-7
ii  libgnutls30  3.5.6-7
ii  libopenconnect5  7.07-1
ii  libproxy1v5  0.4.13-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  vpnc-scripts 0.1~git20160829-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information

Bug#813658: virglrenderer support before the freeze?

[Hillel Lubman]

On Thu, 3 Nov 2016 08:14:18 +0300 Michael Tokarev  wrote:

> The prob is that currently, with sdl1, virglrenderer doesn't quite
> work. It works with sdl2 or gtk frontends, sdl1 support is very
> limited.
>
> So in order for virglrenderer to be useful, other changes are needed.
> Which I'm currently evaluating.  The prob is that I tried to switch
> to sdl2 before already, users complained about missing features which
> were found in sdl1 support.

What features did users complain about? May be today it's not relevant anymore. 
And SDL1 eventually should get deprecated
(especially since it won't work with Wayland), so users should eventually stop 
relying on it. I'm not sure it's even supported upstream
today. I'd say now more and more would complain that virgl isn't supported 
because of sticking to SDL1, so you'd need to consider
what's more important.

But if you can figure support for both SDL1 and SDL2 at the same time as a 
runtime choice, that would be of course ideal including legacy  cases.

Best regards,
Hillel Lubman.

Bug#813658: virglrenderer support before the freeze?

[Hillel Lubman]

Hi. 

Do you plan to add --enable-virglrenderer to the qemu build? Freeze is
very close, and it would be good to have this feature in before it. 

Thanks, 

Hillel Lubman.

  

Bug#833466: Update before the freeze?

[Hillel Lubman]

Dear maintainer,

do you plan to fix this and upload the newest version of openconnect before the 
upcoming Debian freeze?

Thanks,
Hillel.

Bug#833466: openconnect 7.06 fails to parse KMP message with recent Junos VPN

[Hillel Lubman]

Package: openconnect
Version: 7.06-2+b2
Severity: normal

Dear Maintainer,

Openconnect 7.06 became incompatible with new Pulse (Junos) VPN (--juniper
option). It fails to connect to it with such error:

Failed to parse KMP message

See http://lists.infradead.org/pipermail/openconnect-
devel/2016-February/003495.html

This is already fixed in openconnect 7.07 and later. Please package the more
recent version.



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openconnect depends on:
ii  libc62.23-4
ii  libgnutls30  3.5.2-2
ii  libopenconnect5  7.06-2+b2
ii  libproxy1v5  0.4.11-5
ii  libxml2  2.9.4+dfsg1-1
ii  vpnc-scripts 0.1~git20150318-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information

Bug#693399: KeePassX 2.0 release is out

[Hillel Lubman]

 

Version 2.0 proper was released recently:
https://www.keepassx.org/news/2015/12/533 

Do you plan push it to Sid and testing? 

Thanks, 

Hillel Lubman. 
  

Bug#731634: xz-utils new upstream version: 5.2.1

[Hillel Lubman]

 

Does anyone still plan to do it? It's been a really long time since the
new parallelized version came out. 

Hillel. 
  

Bug#802970: firmware-iwlwifi: iwlwifi-7260-15.ucode is missing and fails to load

[Hillel Lubman]

Package: firmware-iwlwifi
Version: 20151018-2
Severity: normal

Dear Maintainer,

After firmware-iwlwifi was updated to 20151018-2 on my Debian testing, it
started complaining that it can't load iwlwifi-7260-15.ucode. (Before it was
complaining even more, but now about 7260-15 only).

Here is what dmesg shows:

[   11.924696] iwlwifi :04:00.0: firmware: failed to load
iwlwifi-7260-15.ucode (-2)
[   11.925142] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-7260-15.ucode failed with error -2
[   12.202996] iwlwifi :04:00.0: firmware: direct-loading firmware
iwlwifi-7260-14.ucode
[   12.203192] iwlwifi :04:00.0: loaded firmware version 25.30.14.0 op_mode
iwlmvm
[   12.572352] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC
7260, REV=0x144

Should iwlwifi-7260-15.ucode be present in the package, or it can be ignored?



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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.120

-- no debconf information

Bug#797149: konsole: no longer possible to re-order tabs

[Hillel Lubman]

This bug is now fixed upstream: 
https://bugs.kde.org/show_bug.cgi?id=347094 [1]


Until this will come to Debian, you can use a keyboard shortcut 
workaround. Ctrl+Shift+LeftArrow / Ctrl+Shift+RightArrow.



Links:
--
[1] https://bugs.kde.org/show_bug.cgi?id=347094

Bug#731634: xz-utils new upstream version: 5.2.1

[Hillel Lubman]

On Fri, 22 May 2015 17:31:37 +0200 (CEST) Fabio Pedretti fabio@libero.it 
wrote:
 Hi, is there any news on upgrading xz-utils?
 
 Thanks!

I second this. The latest version supports both multithreaded compression and 
decompression which is very valuable and can save a lot of time when using with 
huge files. Are there any plans to package this. This feature was out last year 
and it's still not in Debian.

Thanks.

Bug#794419: sddm doesn't source /etc/profile and $HOME/.profile

[Hillel Lubman]

I see that sddm contains /usr/share/sddm/scripts/Xsession with those includes,
but apparently in my case it didn't help including /etc/profile and 
$HOME/.profile
(my shell is bash, and I have $HOME/.profile and no $HOME/.bash_profile).

I tested, and sddm does include $HOME/.xsessionrc however.


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

Bug#794419: sddm doesn't source /etc/profile and $HOME/.profile

[Hillel Lubman]

Package: sddm
Version: 0.11.0-3
Severity: important

Dear Maintainer,

After upgrading Debian testing to KDE Plasma 5, things which rely on
/etc/profile being sourced became broken because sddm doesn't source it unlike
kdm did (it also doesn't source $HOME/.profile unlike kdm, so if anything
relied on that it would be broken too).

For example, /etc/profile adds /usr/games to the PATH, and minetest and a
number of other Debian games rely on this. With sddm + Plasma 5 their launchers
became broken in Debian.

I filed the bug upstream: https://github.com/sddm/sddm/issues/448 and sddm
developers commented that profiles aren't supposed to be sourced by the display
manager, so there should be some other way of handling this in such case.



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

Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sddm depends on:
ii  adduser 3.113+nmu3
ii  debconf [debconf-2.0]   1.5.57
ii  libc6   2.19-19
ii  libgcc1 1:5.1.1-14
ii  libpam0g1.1.8-3.1
ii  libqt5core5a5.4.2+dfsg-5
ii  libqt5dbus5 5.4.2+dfsg-5
ii  libqt5gui5  5.4.2+dfsg-5
ii  libqt5network5  5.4.2+dfsg-5
ii  libqt5qml5  5.4.2-4
ii  libqt5quick55.4.2-4
ii  libstdc++6  5.1.1-14
ii  libsystemd0 222-2
ii  libxcb-xkb1 1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  qml-module-qtquick2 5.4.2-4
ii  sddm-theme-breeze [sddm-theme]  4:5.3.2-4

sddm recommends no packages.

sddm suggests no packages.

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm


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

Bug#766432: apper: Apper updater plasmoid is not showing updates in the system tray

[Hillel Lubman]

Package: apper
Version: 0.9.1-1
Severity: normal

In current Apper in Debian testing updater plasmoid stopped showing updates in
the system tray. With plasma-desktop run from the terminal, such errors related
to the updater can be seen:

file:///usr/share/kde4/apps/plasma/plasmoids/org.packagekit.updater/contents/ui/main.qml:201:
Error: Unable to determine callable overload.  Candidates are:
status(PackageKit::Transaction::Status)
status(PackageKit::Transaction::Status,uint)
status(PackageKit::Transaction::Status,uint,qulonglong)
void PackageModel::finished() QObject(0x0)  QObject(0x0)
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML
Row: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML
Row: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/org.packagekit.updater/contents/ui/main.qml:201:
Error: Unable to determine callable overload.  Candidates are:
status(PackageKit::Transaction::Status)
status(PackageKit::Transaction::Status,uint)
status(PackageKit::Transaction::Status,uint,qulonglong)
file:///usr/share/kde4/apps/plasma/plasmoids/org.packagekit.updater/contents/ui/main.qml:200:
Error: Unknown method parameter type: PackageKit::Transaction::Role
file:///usr/share/kde4/apps/plasma/plasmoids/org.packagekit.updater/contents/ui/Transaction.qml:67:
Error: Unable to determine callable overload.  Candidates are:
status(PackageKit::Transaction::Status)
status(PackageKit::Transaction::Status,uint)
status(PackageKit::Transaction::Status,uint,qulonglong)

This apparently was already fixed upstream:

https://projects.kde.org/projects/extragear/sysadmin/apper/repository/revisions/75b3d7d1587d4fe66ea8d157efc022f20d853dc1

(Related discussion: https://forum.kde.org/viewtopic.php?f=225t=123044 ).

Can you please backport this fix into the Debian package? The next release of
Apper might be in a while, and it would be good to have this in working state
in Jessie.

Thanks.

Hillel Lubman.



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

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

Versions of packages apper depends on:
ii  apper-data   0.9.1-1
ii  kde-runtime  4:4.14.1-1+b1
ii  libappstream10.7.3-1
ii  libc62.19-11
ii  libdebconf-kde0  0.3-1
ii  libgcc1  1:4.9.1-16
ii  libgee-0.8-2 0.14.0-3
ii  libglib2.0-0 2.42.0-2
ii  libkcmutils4 4:4.14.1-1+b1
ii  libkdecore5  4:4.14.1-1+b1
ii  libkdeui54:4.14.1-1+b1
ii  libkemoticons4   4:4.14.1-1+b1
ii  libkidletime44:4.14.1-1+b1
ii  libkio5  4:4.14.1-1+b1
ii  libkprintutils4  4:4.14.1-1+b1
ii  libkutils4   4:4.14.1-1+b1
ii  libkworkspace4abi2   4:4.11.12-2+b1
ii  liblistaller-glib0   0.5.9-4
ii  libpackagekitqt4-0   0.9.5-1
ii  libqt4-dbus  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-declarative   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-network   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-sql   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-svg   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xmlpatterns   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libsolid44:4.14.1-1+b1
ii  libstdc++6   4.9.1-16
ii  packagekit   1.0.0-3
ii  policykit-1-gnome0.105-2
ii  polkit-kde-1 0.99.1-1
ii  software-properties-kde  0.92.25debian1

Versions of packages apper recommends:
ii  appstream-index  0.7.3-1

Versions of packages apper suggests:
pn  debconf-kde-helper  none
ii  listaller   0.5.9-4


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

Bug#756253: This upgrade removes the entry set by efibootmgr before

[Hillel Lubman]

Hi.

I was also affected by this bug with recent Debian testing update.

Before the upgrade I had these files created:

/boot/efi/EFI/debian/grubx64.efi
/boot/efi/EFI/boot/bootx64.efi

bootx64.efi was the identical copy of grubx64.efi which I made manually to 
allow booting the system before creating the entry for Debian with  efibootmgr. 
Then I made the entry with efibootmgr and actual boot was happening with 
/boot/efi/EFI/debian/grubx64.efi.

After this upgrade, /boot/efi/EFI/debian/grubx64.efi was updated, and 
/boot/efi/EFI/boot/bootx64.efi naturally remained the older one. However the 
entry for Debian was removed from EFI somehow (that's the actual bug), so at 
boot it tried to load the default (outdated) /boot/efi/EFI/boot/bootx64.efi and 
obviously failed. To fix it, I accessed the HDD using another system and simply 
copied new /boot/efi/EFI/debian/grubx64.efi to /boot/efi/EFI/boot/bootx64.efi. 
That allowed it to boot. Then I could restore the Debian entry with running:

sudo efibootmgr -c -l \\EFI\\debian\\grubx64.efi -L Debian

So, to summarize, something went wrong during the package upgrade, that wiped 
the Debian entry from EFI memory.

Regards,

Hillel Lubman.


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

Bug#746702: libappstream0: Changes in libappstream0 ABI broke apper [KDE]

[Hillel Lubman]

Package: libappstream0
Version: 0.6-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

 libappstream0 was updated in Debian testing from 0.5-1 to 0.6-1, while apper
remained version 0.8.1-1.

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

Upgrade was performed with apt-get update  apt-get dist-upgrade

   * What was the outcome of this action?

Apper crashes when trying to show a list of installed packages, producing an
error when run from a terminal:

apper: symbol lookup error: /usr/lib/apper/libapper.so: undefined symbol:
appstream_database_new

Same problem causes plasma-desktop to crash periodically, if system updates
(from apper) are enabled in the system tray settings. When run from the
terminal, plasma-desktop shows the same error before disappearing:

plasma-desktop: symbol lookup error: /usr/lib/apper/libapper.so: undefined
symbol: appstream_database_new

   * What outcome did you expect instead?

Apper and plasma-desktop had to work without crashing. To avoid that,
libappstream0 probably had to be updated together with apper that could support
new ABI.



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

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

Versions of packages libappstream0 depends on:
ii  libc6  2.18-4
ii  libgcc11:4.8.2-16
ii  libglib2.0-0   2.40.0-2
ii  libstdc++6 4.8.2-16
ii  libxapian221.2.17-1
ii  libxml22.9.1+dfsg1-3
ii  multiarch-support  2.18-4

Versions of packages libappstream0 recommends:
ii  appstream-index  0.6-1

libappstream0 suggests no packages.

-- no debconf information


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

Bug#746702: Modify severity to normal

[Hillel Lubman]

Control: severity -1 normal


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