time_t 64 and KDE

[Miguel A. Vallejo]

Hello!

I know this list is KDE related but I'm pretty sure someone else is
suffering the same problems with the ongoing time_t 64 and KDE transition
in sid.

When I do an apt upgrade I get:

(...)
15 upgraded, 1 newly installed, 0 to remove and 466 not upgraded.

If I issue a dist-upgrade:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Error!
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:
plasma-workspace : Depends: gdb-minimal but it is not going to be installed
or
gdb
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
by held packages.


The interesting thing is GDB is installed:

gdb:
 Installed: 13.2-1
 Candidate: 13.2-1
 Version table:
*** 13.2-1 500
   500 http://deb.debian.org/debian unstable/main amd64 Packages
   100 /var/lib/dpkg/status


If I issue a dist-upgrade gdb I get:

(...)
452 upgraded, 167 newly installed, 236 to remove and 13 not upgraded.

And in those 236 packages to remove are a LOT of KDE / Plasma / Qt
packages... Also in the "automatically installed and are no longer
required" packages there are many KDE programs and a lot of libraries that
I feel are important to boot a KDE system.


The main issue is the system is barely usable now. For example I don't know
why but the latest kernels were installed without sources, and I need them
to run and compile things (like virtualbox). But I can't install kernel
sources without uninstalling hundreds of (needed) packages. The same occurs
if I try to install any other package.

Sid has been in this state for at least a pair of weeks for me...

Is there anything I can do? Waiting for another pair of weeks?

Thanks in advance.

Re: GTK themes in KDE

[Miguel A. Vallejo]

Bad news

After turning on the computer this evening, QT applications have white
cursor and GTK applications black cursors.

Something is broken in the GTK theming in KDE.

Re: GTK themes in KDE

[Miguel A. Vallejo]

Thank you for your advice.

After four or five reboots(*) and changing themes and cursors, all cursors
are white everywhere. I noticed that every time I change the theme, the
cursors resets, so the correct way to do it is to set the theme,
restart(*), set the cursors, restart(*) and check everything. If there are
still no white cursors everywhere, repeat.

* Logout/login seems to do the job and is faster.

Re: GTK themes in KDE

[Miguel A. Vallejo]

After spending some time changing themes back and forth I achieved
something funny in QT applications: white cursor over window title and
black cursor over window content. It seems something is messed up with KDE
themes, both in QT and GTK.

I left the black cursors for now... at least they are consistent everywhere.

Thank you for the suggestions

GTK themes in KDE

[Miguel A. Vallejo]

Hello!

Today I faced an interesting problem. After a clean KDE installation in
Debian Sid the default theme was Breeze, which is ok for me, but I changed
the cursor theme to Breeze light, just because I'm used to white cursors...

But soon I noticed the cursor changed to a black one over GTK applications
(for example Chrome)... so  I have white or black cursors depending on the
program I'm running.

In Settings --> Application Style --> GNOME/GTK Application Style the only
available options are Breeze, default and Emacs, but all of them produce
black cursors over GTK applications.

How Can I have a Breeze-light like cursors over GTK applications? A quick
search in Debian packages does not show anything like
breeze-light-gtk-theme-kde or even similar.

Thanks in advance.

Re: Dragging icons at desktop

[Miguel A. Vallejo]

> For the record this has been fixed in Qt5 version 5.15.8+dfsg-9 that already 
> reached bookworm.
> Patrick identified the upstream commit and Dmitry backported it to our 
> packages.

YES!

I can confirm it works fine now.

A big thank you to you all.

Re: Dragging icons at desktop

[Miguel A. Vallejo]

> Are there any solutions to this?

My search in bug trackers returned nothing, probably the bug is not
even reported yet. Now I'm on stable because of the font rendering
problem in konsole, so I will not suffer from it for a while, but I'm
agree with you: it is totally annoying.

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Hello!

> I used to see the issue too, but it disappeared since last time I checked.
>
> Maybe the fix for #103 [0] or some other fontconfig update fixed it for 
> me.
> Do you still see the issue with an up-to-date sid or testing ?

I can't confirm it, because now I'm on stable just to get work done
without eye strain so I will stay here some time.

Anyway, glad to see it seems to be solved.

Thank you

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Hello again!

I went the Stable route. After a clean installation of Debian Stable,
everything displayed fine... in KDE.

But GTK applications had colored edges. After tweaking fontconfig and
fontconfig-config with the same KDE settings GTK applications rendered
nice fonts... except the smaller ones, who still display colored
borders.

Other applications like Telegram also display colored font borders in
any font size... this is interesting because Telegram is a Qt program.

In resume: I thought font rendering issues were something from the
past but I was wrong. In 2023 it is still a serious issue affecting
*every* Linux distribution.

Anyway I will stay in Stable some time... My main applications are KDE
based ones and a clean and crisp Konsole is a must for me.

Thank you for all your tips.

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Hello!

I tested debian-live-11.6.0-amd64-kde.iso and font rendering is just
perfect, both in Konsole and the whole system.

I can't find a live testing kde iso, the only ones I found were based
on cinnamon.

I'm downloading a nightly build of kde neon, but download speed is
awful, so no tests until tomorrow.

The only bug somewhat related I found is this one

https://bugs.kde.org/show_bug.cgi?id=463024

But I'm not sure if we are talking about the same issue.

The main problem for me is I'm suffering eye strain because of all the
rainbow colors around texts, and because this does not seem to be
resolved anytime soon so I'm seriously thinking of migrating to stable
or any other distribution with more up to date packages. I can't take
this much longer.

Greetings

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

I have been testing some things trying to get the culprit package but
I didn't find anything.

The problem persists creating a new user and logging in with the new
user. I also tried different fonts in Konsole and some of them are
less affected than others but all of them have colored borders, making
the terminal a text rainbow.

 I have seen some recent font related bugs in KDE's bugtracker but
none of them seem to match my problem.

Nobody else noticed this problem?

Is it possible I have a missing package somewhere? I have installed
task-kde-desktop but I'm not sure this guarantees all needed packages
are installed.

Thanks in advance

Re: Dragging icons at desktop

[Miguel A. Vallejo]

Any progress with this bug?

A lot of plasma packages have been updated since I reported it and it
is still present... but worse: Now sometimes the icon does not get
drawn at all while moving, disappearing until I drop it.

Thanks in advance

Re: Plasma 5.27 beta (5.26.90) coming to unstable

[Miguel A. Vallejo]

Thank you, now I see it was in the subject. I was so anxious to test
it and see if it solves my problem with colored character borders...

Spoiler: No, it didn't :-(

Re: Plasma 5.27 beta (5.26.90) coming to unstable

[Miguel A. Vallejo]

Hello!

My apt only finds version 5.26.90-1

Am I doing something wrong?

~# apt-cache policy plasma-workspace
plasma-workspace:
 Installed: 4:5.26.90-1
 Candidate: 4:5.26.90-1
 Version table:
*** 4:5.26.90-1 500
   500 http://ftp.debian.org/debian unstable/main amd64 Packages
   100 /var/lib/dpkg/status

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Just for info, I managed to downgrade libfreetype6 and fontconfig to
2.11.1+dfsg-1 and the problem persists.

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Hello Sven!

I removed both simlinks but no effect at all, exactly the same rainbow
colored characters, most noticeable with dark background (Kterm)

Sven Joachim wrote:
>
> It is due to new settings in fontconfig-config, especially the symlinks
> 10-sub-pixel-rgb.conf and 10-yes-antialias.conf in /etc/fonts/conf.d.
> Try removing the first of these, and if you are still not satisfied with
> the result, the second as well.
>
> After that fonts should look the same as before, except that the default
> family is now Noto rather than DejaVu, see https://bugs.debian.org/1028643.
>
> Cheers,
>Sven

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

> Would you mind posting the package changes on your system for this date ?
> Maybe something will give us inspiration.

Here is the apt log for january 13 and 14
 Thnaks in advance

Start-Date: 2023-01-13  13:13:44
Commandline: apt upgrade
Upgrade: libgdal32:amd64 (3.6.2+dfsg-1, 3.6.2+dfsg-1+b1),
libfreeimage3:amd64 (3.18.0+ds2-8, 3.18.0+ds2-8+b1),
libpoppler-qt5-1:amd64 (22.12.0
-2, 22.12.0-2+b1), cups-filters:amd64 (1.28.16-1+b2, 1.28.16-1+b3),
qt5-qmake-bin:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), libgeotiff5:amd64
(1.7
.1-2, 1.7.1-2+b1), qtbase5-dev-tools:amd64 (5.15.7+dfsg-2,
5.15.7+dfsg-3), libgphoto2-l10n:amd64 (2.5.29-1, 2.5.30-1),
qt5-image-formats-plugi
ns:amd64 (5.15.7-2, 5.15.7-3), gdal-plugins:amd64 (3.6.2+dfsg-1,
3.6.2+dfsg-1+b1), libqt5core5a:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
qt5-gtk-
platformtheme:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), liblzma5:amd64
(5.4.0-0.1, 5.4.1-0.0), liblzma5:i386 (5.4.0-0.1, 5.4.1-0.0),
imagemagick:a
md64 (8:6.9.11.60+dfsg-1.4, 8:6.9.11.60+dfsg-1.4+b1), libpocl2:amd64
(3.0-8, 3.1-1), gwenview:amd64 (4:22.12.1-1, 4:22.12.1-1+b1),
libtiff6:am
d64 (4.5.0-2, 4.5.0-3), libtiff6:i386 (4.5.0-2, 4.5.0-3),
libgs10:amd64 (10.0.0~dfsg-9, 10.0.0~dfsg-9+b1), libqt5network5:amd64
(5.15.7+dfsg-2
, 5.15.7+dfsg-3), libfreetype6:amd64 (2.12.1+dfsg-3, 2.12.1+dfsg-4),
libfreetype6:i386 (2.12.1+dfsg-3, 2.12.1+dfsg-4), libfontembed1:amd64
(1.
28.16-1+b2, 1.28.16-1+b3), libqt5concurrent5:amd64 (5.15.7+dfsg-2,
5.15.7+dfsg-3), fonts-wine:amd64 (8.0~rc1~repack-1, 8.0~rc2~repack-1),
libq
t5dbus5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), libpoppler-cpp0v5:amd64
(22.12.0-2, 22.12.0-2+b1), libimlib2:amd64 (1.10.0-4, 1.10.0-4+b1),
libg
egl-0.4-0:amd64 (1:0.4.40-1, 1:0.4.40-1+b1), xz-utils:amd64
(5.4.0-0.1, 5.4.1-0.0), libqt5test5:amd64 (5.15.7+dfsg-2,
5.15.7+dfsg-3), libmagic
k++-6.q16-8:amd64 (8:6.9.11.60+dfsg-1.4, 8:6.9.11.60+dfsg-1.4+b1),
libgraphicsmagick++-q16-12:amd64 (1.4+really1.3.39-2,
1.4+really1.3.39-2+b1
), libqt5widgets5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
cups-filters-core-drivers:amd64 (1.28.16-1+b2, 1.28.16-1+b3),
poppler-utils:amd64 (22.
12.0-2, 22.12.0-2+b1), libmagickcore-6.q16-6-extra:amd64
(8:6.9.11.60+dfsg-1.4, 8:6.9.11.60+dfsg-1.4+b1), python3-gdal:amd64
(3.6.2+dfsg-1, 3.
6.2+dfsg-1+b1), libqt5gui5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
ghostscript:amd64 (10.0.0~dfsg-9, 10.0.0~dfsg-9+b1),
libqt5printsupport5:amd6
4 (5.15.7+dfsg-2, 5.15.7+dfsg-3), libpoppler-glib8:amd64 (22.12.0-2,
22.12.0-2+b1), libqt5xml5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
libqt5ope
ngl5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), libmagickwand-6.q16-6:amd64
(8:6.9.11.60+dfsg-1.4, 8:6.9.11.60+dfsg-1.4+b1), libdjvulibre21:amd64
(
3.5.28-2, 3.5.28-2+b1), libgeoip1:amd64 (1.6.12-9, 1.6.12-10),
libpoppler126:amd64 (22.12.0-2, 22.12.0-2+b1), qtbase5-dev:amd64
(5.15.7+dfsg-2
, 5.15.7+dfsg-3), python3-pil.imagetk:amd64 (9.4.0-1, 9.4.0-1+b1),
libqt5sql5:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), cups-browsed:amd64
(1.28.1
6-1+b2, 1.28.16-1+b3), imagemagick-6.q16:amd64 (8:6.9.11.60+dfsg-1.4,
8:6.9.11.60+dfsg-1.4+b1), libunbound8:amd64 (1.17.0-1+b1, 1.17.1-1),
lib
pocl2-common:amd64 (3.0-8, 3.1-1), libmagickcore-6.q16-6:amd64
(8:6.9.11.60+dfsg-1.4, 8:6.9.11.60+dfsg-1.4+b1), python3-pil:amd64
(9.4.0-1, 9.
4.0-1+b1), libqt5opengl5-dev:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
libopenjp2-7:amd64 (2.5.0-1, 2.5.0-1+b1), libopenjp2-7:i386 (2.5.0-1,
2.5.0
-1+b1), libzmq5:amd64 (4.3.4-4, 4.3.4-5), libzmq5:i386 (4.3.4-4,
4.3.4-5), libgtk-4-1:amd64 (4.8.3+ds-1, 4.8.3+ds-1+b1),
libgraphicsmagick-q16
-3:amd64 (1.4+really1.3.39-2, 1.4+really1.3.39-2+b1),
libadwaita-1-0:amd64 (1.2.1-1, 1.2.1-2), pocl-opencl-icd:amd64 (3.0-8,
3.1-1), libqt5sql
5-sqlite:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3), qt5-qmake:amd64
(5.15.7+dfsg-2, 5.15.7+dfsg-3), libgtk-4-bin:amd64 (4.8.3+ds-1,
4.8.3+ds-1+b1),
libcupsfilters1:amd64 (1.28.16-1+b2, 1.28.16-1+b3),
libqt5sql5-mysql:amd64 (5.15.7+dfsg-2, 5.15.7+dfsg-3),
wine-binfmt:amd64 (8.0~rc1~repack-
1, 8.0~rc2~repack-1)
End-Date: 2023-01-13  13:14:12



Start-Date: 2023-01-13  13:14:16
Commandline: apt autoremove --purge
Purge: libgphoto2-l10n:amd64 (2.5.30-1)
End-Date: 2023-01-13  13:14:16



Start-Date: 2023-01-14  14:21:56
Commandline: apt upgrade
Upgrade: fontconfig:amd64 (2.13.1-4.5, 2.14.1-3),
libokular5core10:amd64 (4:22.12.1-1, 4:22.12.1-1+b1), libext2fs2:amd64
(1.46.6~rc1-1+b1, 1.4
6.6~rc1-1.1), readline-common:amd64 (8.2-1.2, 8.2-1.3),
python3-samba:amd64 (2:4.17.4+dfsg-2+b1, 2:4.17.4+dfsg-3),
libglx-mesa0:amd64 (22.3.2-
1, 22.3.3-1), sane-utils:amd64 (1.1.1-6+b1, 1.1.1-6+b2), libldb2:amd64
(2:2.6.1+samba4.17.4+dfsg-2+b1, 2:2.6.1+samba4.17.4+dfsg-3),
libldap-co
mmon:amd64 (2.5.13+dfsg-2, 2.5.13+dfsg-3), libwine:amd64
(8.0~rc1~repack-1, 8.0~rc2~repack-1), libwine:i386 (8.0~rc1~repack-1,
8.0~rc2~repack-
1), qml-module-qt-labs-settings:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2),
libgbm1:amd64 (22.3.2-1, 22.3.3-1), libgbm1:i386 (22.3.2-1, 22.3.3-1),
l
ibspandsp2:amd64 (0.0.6+dfsg-2, 0.0.6+dfsg-2+b1), libwbclient0:amd64

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

Until january 13th it rendered perfect. Crisp and clean but after an apt
upgrade the issue appeared.

I tried to tweak the settings but no one brings back the rendering quality
I had just three days ago. I always get rainbow-colored borders.

The problem is I can't find the responsible package to try to downgrade
it... or open a bug report against it. A web search for recent kde bugs or
problems didn't show anything.

It is quite unconfortable to work with a multicolored font everywhere but I
don't know what to do now.

Please if someone else noticed the problem please advice

Thank you in advance

Re: Coloured character borders in kterm

[Miguel A. Vallejo]

> Hi. What system are you running? Is it even Debian? What versions of
> KDE, packages, system? Can't help without info.

Sorry, I forgot the details because I always assume here everyone uses Sid.

Debian Sid, fully updated, as today no packages were kept back.

Konsole version 22.12.1
Plasma version 5.26.5
KDE frameworks version 5.101
QT version 5.15.8
Kernel 6.1.0-1 amd64 running under X11

The problem is also observed in desktop icons, Dolphin, etc (less
noticeable because of the colored background) and in some GTK
applications, like Chrome. It seems to be more noticeable with smaller
font sizes

Thanks in advance.

Coloured character borders in kterm

[Miguel A. Vallejo]

Hello!

After today's apt-upgrade I noticed all letters in kterm have a
coloured border as you can see in the attached image.

But I also noticed 78 packages have been kept back, so my question is:

Is this a new problem or only the symptom of an incomplete upgrade?

Anyone else noticed this?

Thanks in advance

Re: kded5 crashes

[Miguel A. Vallejo]

A small update:

Syslog is flooded with messages like this:

2023-01-06T00:56:11.901415+01:00 waterhole plasmashell[3567]:
[3604:3604:0106/005611.901154:ERROR:shared_image_factory.cc(575)]
Could not find SharedIm
ageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory

One every few seconds

Re: kded5 crashes

[Miguel A. Vallejo]

Hello!

Once I removed apper, plasmashell goes to 100% after login for about
30 seconds and then, everything goes ok, no extra CPU usage and
everything seems to work.

I guess it is ok for now.

Thank you!

Re: Dragging icons at desktop

[Miguel A. Vallejo]

Any progress with this issue?

After a few days using Wayland I returned to X. I do not feel Wayland
is ready for everyday use... at least not for me.

Greetings

Re: kded5 crashes

[Miguel A. Vallejo]

I'm still experiencing constant kded5 crashes, but after a few days of
googling I didn't find anything relevant... Is it a Debian Unstable
only issue?

Greetings

Re: Dragging icons at desktop

[Miguel A. Vallejo]

Thank you!

Let us know the assigned bug number to keep an eye on it.

Merry Christmas!

Re: Dragging icons at desktop

[Miguel A. Vallejo]

Yes! This is becoming quite interesting!

I made a small video showing the issue:

https://www.dropbox.com/s/rm98raxb4i55v1d/issue.mp4?dl=1

Questions:

> What happens if you try to suspend the compositor (SHIFT+Alt+F12)?

Problem solved, a white icon background but it moves perfectly!

> It would also be interesting to test under a Wayland session

No issues at all under Wayland. Just perfect!

So I guess I will use Wayland for now... The problem seems to be in
the compositor under X11.

If you need more info about my setup, just tell me.

Thank you all!

Re: Dragging icons at desktop

[Miguel A. Vallejo]

Interesting...

My system is running X on a Intel 530 HD Graphics card.

When I drag an icon, and move the mouse pointer slowly, the icon
follow the mouse pointer a few centimeters behind moving somewhat
irregularly

If I move the mouse at "medium" speed, the icon can be 15 or 20
centimeters behind the mouse cursor.

If I move the mouse cursor fast, the icon does not move at all until I
drop the icon, then it moves slowly from the old to the new position.

Otherwise, moving windows is as fast as usual, they move in real time
under the mouse pointer without any problem.

It happens with any icon, even with icons inside Dolphin or Ark.

I must admit I thought it was a new desktop effect.

I also noticed plasmashell CPU usage is quite high (around 60 - 65 %
CPU usage) while dragging icons. Xorg is also high CPU usage (35 -
40%) while dragging icons. In fact both plasmashell and Xorg CPU
usages added are always very close to 100%. They do not use as much
CPU moving windows (well under 10%).

I didn't see any suspicious problems both in syslog or .xsession-errors

Any ideas to find where the problem is?

Thanks in advance

Re: Dragging icons at desktop

[Miguel A. Vallejo]

El lun, 28 nov 2022 a las 23:34, Martin Steigerwald
() escribió:
>
> Miguel A. Vallejo - 28.11.22, 23:26:52 CET:
> > Recently I noticed when I drag an icon in the desktop (fully updated
> > Sid), the icon lags behind the mouse cursor instead of following the
> > mouse cursor under it as it always did.

After almost a month of usage I can't get used to this "feature", it
makes the desktop feel sluggish and unresponsive.

But I still haven't found where to disable it, so should I open a
bug? Against what package? At Debian or KDE?

Thanks in advance.

kded5 crashes

[Miguel A. Vallejo]

Since a few days ago I've been experiencing problems with KDE in a
fully upgraded Sid.

The symptoms are always the same: kded5 crashes a few minutes after
boot and then icons from no KDE programs (like Telegram) disappears
from the system tray.

A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself.
Any ideas?

Thanks in advance

The last crash:

2022-12-06T13:25:45.729082+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132545.728952:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:45.729818+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132545.729669:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RED_8,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:45.731194+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132545.731029:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:45.803791+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132545.803610:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RED_8,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:45.803996+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132545.803903:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:50.847114+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132550.846702:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RED_8,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:25:50.847224+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132550.846811:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:26:05.302141+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132605.301276:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RED_8,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:26:05.303077+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132605.301531:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
Gles2|Raster|DisplayRead|Scanout, format: RG_88,
share_between_threads: 0, gmb_type: shared_memory
2022-12-06T13:26:22.128639+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 39487, resource
id: 27263164, major code: 18 (ChangeProperty), minor code: 0
2022-12-06T13:26:22.321886+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 39750, resource
id: 27263165, major code: 18 (ChangeProperty), minor code: 0
2022-12-06T13:26:54.800549+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 42442, resource
id: 4194321, major code: 18 (ChangeProperty), minor code: 0
2022-12-06T13:27:20.532320+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132720.531753:ERROR:shared_image_factory.cc(575)]
Could not find SharedImageBackingFactory with params: usage:
DisplayRead|Scanout, format: YUV_420_BIPLANAR, share_between_threads:
0, gmb_type: platform
2022-12-06T13:27:20.535272+01:00 waterhole plasmashell[2298]:
[2335:2335:1206/132720.531880:ERROR:shared_image_stub.cc(147)]
SharedImageStub: Unable to create shared image
2022-12-06T13:27:21.810647+01:00 waterhole DiscoverNotifier[1717]:
packagekitqt.transaction: Unknown Transaction property: "Sender"
QVariant(QString, ":1.64")
2022-12-06T13:27:22.924224+01:00 waterhole PackageKit: refresh-cache
transaction /23315_ebeedecc from uid 1000 finished with success after
1057ms
2022-12-06T13:27:23.026302+01:00 waterhole kded5[1448]: apper.daemon:
System is not ready, application should conserve resources
2022-12-06T13:27:23.029435+01:00 waterhole kded5[1448]:
packagekitqt.transaction: Unknown Transaction property: "Sender"
QVariant(QString, ":1.39")
2022-12-06T13:27:23.035093+01:00 waterhole kded5[1448]:
packagekitqt.transaction: Unknown Transaction property: "Sender"
QVariant(QString, ":1.39")
2022-12-06T13:27:23.223099+01:00 waterhole DiscoverNotifier[1717]:
packagekitqt.transaction: Unknown Transaction property: "Sender"
QVariant(QString, ":1.64")
2022-12-06T13:27:24.726825+01:00 waterhole PackageKit: get-updates
transaction /23316_adadcabd from 

Dragging icons at desktop

[Miguel A. Vallejo]

Hi all!

Recently I noticed when I drag an icon in the desktop (fully updated Sid),
the icon lags behind the mouse cursor instead of following the mouse cursor
under it as it always did.

It seems to be intentional because of the "cute animation", but it is
terribly uncomfortable and breaks the workflow completely.

I have searched in Preferences but I do not see anything about "drag
animations" or any related effect.

Anyone know how to disable it and go back to the old behaviour?

Thanks in advance

Re: Plasma 5.24 coming to unstable

[Miguel A. Vallejo]

The question is:

Why is APT not smart enough to see that the proposed upgrade will fail?

It always starts to install packages and at some point fails because
some package needs another package with a specific version. Why does
it not detect these cases after starting upgrading packages? It knows
the versions available for every package so it should prevent these
problems.

Is it a bug or a missing APT feature?

Re: Plasma 5.24 coming to unstable

[Miguel A. Vallejo]

Thanks for the advice, but too late for me: my KDE is broken now.

You should ideally warn one or two days before packages are uploaded.

> we've just uploaded Plasma 5.24.2 to unstable. The first packages should
> be arriving in a couple of hours.
>
> As always, be careful when you upgrade and make sure that you upgrade
> the entire Plasma stack at once to avoid mixing 5.23 and 5.24.

Re: Broken KDE in Sid/Unstable

[Miguel A. Vallejo]

> I somehow disagree. Since I started packaging KDE/plasma with 5.18 or
> so, I have been tracking every single minor and major release within a
> few days, and I never have seen any considerable change in
> layout/design.
>
> So I am really surprised about your experience.

I am really surprised your experience is not the same if we are
running the same KDE.

One or two months ago the main menu changed drastically. Now the
taskbar is a only icons version, another drastic change. What is the
secret to keep KDE the same across updates? I would love to hear from
you.

Greetings

Re: Broken KDE in Sid/Unstable

[Miguel A. Vallejo]

The main drawback I see every time KDE gets updated is that everything
changes. Few weeks ago the main menu changed to a ugly one with too
big icons... and no way to get back the old one. Today the taskbar
reappeared with an "only icons" version. Once I changed the widget to
the traditional one I just have too much text in taskbar items...

KDE is a constant fight between the user keeping things like he wants
and the developers changing everything to a worse / uglier version.

Re: Broken KDE in Sid/Unstable

[Miguel A. Vallejo]

I didn't notice anything weird, so I went with the upgrade...  I guess
I missed something.

After some time I found some missing packages so I could log in but no
taskbar was visible.

Removing ~/.config/plasma-org.kde.plasma.desktop-appletsrc and relogin
did the trick, but lost all the personalization.

Some minutes reconfiguring KDE and everything seems to be Ok again.

Thank you!

Broken KDE in Sid/Unstable

[Miguel A. Vallejo]

Hi!

This morning an apt update broke my kde. I can log in, but only to get into
a black screen with the mouse's cursor, even using a newly created user.

I can't see any obvious error in syslog, but there is something in
.xsession-errors :

Kapplymousetheme ("breeze_cursors","24") exited with user code 255

And some lines below a lot of unrecognized keysims from kwin_xkbcommon, a
NULL argument for networkIdsList, a failed to parse kaccess.desktop, many
other errors ( sorry, I'm typing on phone) until a broken connection to the
X11 server brings back the login screen.

Any ideas?

Thanks in advance.

Re: Dolphin search does not work

[Miguel A. Vallejo]

Indexing the content of files is nice when you have only a few dozen
files. When you have thousands and thousands of PDF files content
indexing is just a nightmare, a big cpu/memory/disk waste and does not
work at all. Baloo should be completely optional and never be
activated by default. Same thing for Akonadi. My only gripe with KDE
is it is full of "utilities" and "features" enabled by default that
produce more problems than benefits. One you disable / uninstall all
of them, KDE works like a charm.

Of course it is just my opinion.

Re: Dolphin search does not work

[Miguel A. Vallejo]

Hello.

Yes, Baloo was activated. I disabled it and now everything works perfectly.

Thank you for the tip.

Re: Dolphin search does not work

[Miguel A. Vallejo]

Thank you

El mié, 23 dic 2020 a las 23:22, Norbert Preining
() escribió:
>
> On Wed, 23 Dec 2020, Miguel A. Vallejo wrote:
> > After installing the new KDE in unstable I noticed the find function
> > in Dolphin does not work: Enter in a directory full of files, press
> > Ctrl-F, type your search string and no matter what you type nothing is
> > found.
>
> Indeed. I will check with upstream.
>
>
> Norbert
>
> --
> PREINING Norbert  https://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Dolphin search does not work

[Miguel A. Vallejo]

After installing the new KDE in unstable I noticed the find function
in Dolphin does not work: Enter in a directory full of files, press
Ctrl-F, type your search string and no matter what you type nothing is
found.

It is a bug or am I missing some package(s)?

Thank you in advance

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

luca wrote:

> is kdegraphics-thumbnailers installed ?

No, it was not installed.

I installed it and checked. Now I have previews of PDF files, but the
number of thumbnail.so processes skyrocket as before, both in
directories with a few and in directories with thousands of PDF files,
so I will keep previews for image files only.

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

Norbert Preining wote:

> Does the same happen with a directory of say 5 PDF files?

Yes, I entered in a directory with 8 pdf files and the count of
thumbnail.so processes increased by 6

> And are thumbnails generated in a directory with say 5 PDF files?

No, as I told before I have never seen a pdf previsualization in
dolphin, just the typical pdf icon.

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

This evening I played a bit with the issue and I noticed the real root
of the problem.

I noticed I only need to open my PDF directory in Dolphin to see how
the number of thumbnail.so instances increase without control. The
directory has around 8000 PDF files and just moving the scroll bars in
dolphin to see the different PDF files produces an incredible number
of new instances of thumbnail.so. No need to erase any file, just
browsing the directory.

So I guess thumbnail.so fails producing PDF previews, leaving a lot of
zombie instances. In fact... to be honest I've never seen a PDF
preview in Dolphin...

I configured Dolphin to disable every preview except for image files
(jpg, png, etc) and the problem is solved. No more zombie processes
laying in background and no need to run a killall every 5 minutes.

I hope this helps to track down the bug.





El mar, 24 nov 2020 a las 14:16, Miguel A. Vallejo
() escribió:
>
> > Hmmm, at least with Plasma 5.20 I can't reproduce this problem here.
>
> I can reproduce it very easily every time working on a directory full
> of PDF files.
>
> Select a PDF file in Dolphin
>
> Erase the PDF (not moving to trash can)
>
> Automatically a new "thumbnail.so [kdeinit5] thumbnail" process
> appears in state S (interruptible sleep (waiting for an event to
> complete) according to ps) and a new "Qt Selection Owner for
> thumbnail.so" entry in xrestop. When these entries reach 256, X stops
> to open new windows.
>
> I'm running a killall -9 thumbnail.so every 5 minutes but this far from 
> optimal

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

> Hmmm, at least with Plasma 5.20 I can't reproduce this problem here.

I can reproduce it very easily every time working on a directory full
of PDF files.

Select a PDF file in Dolphin

Erase the PDF (not moving to trash can)

Automatically a new "thumbnail.so [kdeinit5] thumbnail" process
appears in state S (interruptible sleep (waiting for an event to
complete) according to ps) and a new "Qt Selection Owner for
thumbnail.so" entry in xrestop. When these entries reach 256, X stops
to open new windows.

I'm running a killall -9 thumbnail.so every 5 minutes but this far from optimal

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

Hello

I noticed the new KDE in unstable still contains the bug with
thumbnail.so: So many sleeping instances that when they reach 256, X
stops opening new programs.

Has anyone also noticed this problem?

Re: Re: Current status of KDE in Sid

[Miguel A. Vallejo]

Hello Hector.

YES!

Your proposal worked like a charm! Everything was updated without any problem.

Thank you!

Re: Current status of KDE in Sid

[Miguel A. Vallejo]

Norbert Preining wrote:

> Could it be that you have some packages from experimental or somewhere
> else installed?
>
> Can you send the outputs of the following two commands:
>  aptitude search -F "%p %v" '~S~i~Aexper'
>  aptitude search -F "%p %v" '~S~i~Aexper'

No experimental packages, both commands return nothing.

Re: Current status of KDE in Sid

[Miguel A. Vallejo]

This is really weird. Continuing with the example of dolphin:



apt install -V dolphin
Reading package lists... Done
Building dependency tree
Reading state information... Done
dolphin is already the newest version (4:20.08.2-1).
0 upgraded, 0 newly installed, 0 to remove and 182 not upgraded.


But and apt full-upgrade want to uninstall a lot of packages,
including dolphin, so I don't understand anything:



apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer re
quired:
 accountsservice akonadi-backend-mysql akonadi-contacts-data
 akonadi-mime-data akonadi-server apper-data appstream
 apt-config-icons apt-config-icons-hidpi apt-config-icons-large
 apt-config-icons-large-hidpi baloo-kf5 bluez-obexd
 breeze-cursor-theme breeze-gtk-theme cdparanoia cdrdao
 cracklib-runtime cups-pk-helper default-mysql-client-core
 default-mysql-server-core dnsmasq-base drkonqi dvd+rw-tools
 fonts-hack fonts-noto-hinted frameworkintegration freeglut3
 gdal-data genisoimage geoclue-2.0 gir1.2-notify-0.7
 gir1.2-packagekitglib-1.0 gir1.2-secret-1 growisofs ieee-data
 k3b-data kamera kate5-data kde-cli-tools-data kde-config-gtk-style
 kde-config-mailtransport kde-config-sddm kde-style-breeze
 kdeaccessibility kdepim-runtime kdepim-themeeditors
 kdeplasma-addons-data kf5-kdepim-apps-libs-data kf5-messagelib-data
 kgamma5 khotkeys khotkeys-data kimageformat-plugins kio-ldap kmag
 kmenuedit kmousetool kmouth kross ksysguard-data ksysguardd
 kuserfeedback-doc kwin-data kwin-style-breeze kwrited
 libaccounts-glib0 libaccounts-qt5-1 libaccountsservice0 libao-common
 libao4 libappstream4 libappstreamqt2 libarmadillo10 libaudio2
 libbluetooth3 libboost-atomic1.71-dev libboost-atomic1.71.0
 libboost-chrono1.71-dev libboost-container1.71-dev
 libboost-container1.71.0 libboost-context1.71-dev
 libboost-context1.71.0 libboost-coroutine1.71-dev
 libboost-coroutine1.71.0 libboost-date-time1.71-dev
 libboost-exception1.71-dev libboost-fiber1.71-dev
 libboost-fiber1.71.0 libboost-filesystem1.71-dev
 libboost-graph1.71-dev libboost-graph1.71.0
 libboost-iostreams1.71-dev libboost-locale1.71-dev
 libboost-log1.71-dev libboost-log1.71.0 libboost-math1.71-dev
 libboost-math1.71.0 libboost-numpy1.71-dev libboost-numpy1.71.0
 libboost-program-options1.71-dev libboost-python1.71-dev
 libboost-python1.71.0 libboost-random1.71-dev libboost-random1.71.0
 libboost-regex1.71-dev libboost-serialization1.71-dev
 libboost-stacktrace1.71-dev libboost-stacktrace1.71.0
 libboost-system1.71-dev libboost-system1.71.0 libboost-test1.71-dev
 libboost-test1.71.0 libboost-thread1.71-dev libboost-timer1.71-dev
 libboost-timer1.71.0 libboost-type-erasure1.71-dev
 libboost-type-erasure1.71.0 libboost-wave1.71-dev
 libboost-wave1.71.0 libboost1.71-dev libcharls2 libcppunit-1.15-0
 libcppunit-dev libcrack2 libdap25 libdapclient6v5 libdmtx0b
 libdolphinvcs5 libepsilon1 libfakekey0 libfreexl1 libfyba0 libgdal27
 libgeos-3.8.1 libgeos-c1v5 libgeotiff5 libglfw3 libglib2.0-bin
 libgmp-dev libgmpxx4ldbl libgnuradio-channels3.8.2
 libgnuradio-dtv3.8.2 libgnuradio-fec3.8.2 libgnuradio-trellis3.8.2
 libgnuradio-video-sdl3.8.2 libgnuradio-vocoder3.8.2
 libgnuradio-wavelet3.8.2 libgnuradio-zeromq3.8.2 libgps26
 libgsm1-dev libhdf4-0-alt libhdf5-hl-100 libibus-1.0-5 libical3
 libiso9660-11 libjim0.79 libkaccounts2 libkdecorations2private6
 libkf5akonadi-data libkf5akonadiagentbase5
 libkf5akonadicalendar-data libkf5akonadicalendar5abi1
 libkf5akonadicontact5 libkf5akonadicore5abi2 libkf5akonadimime5
 libkf5akonadinotes5 libkf5akonadiprivate5abi2
 libkf5akonadisearch-bin libkf5akonadisearch-data
 libkf5akonadisearchcore5 libkf5akonadisearchdebug5
 libkf5akonadisearchpim5 libkf5akonadisearchxapian5
 libkf5akonadiwidgets5abi1 libkf5alarmcalendar-data
 libkf5alarmcalendar5abi1 libkf5auth5 libkf5baloo5 libkf5balooengine5
 libkf5baloowidgets-bin libkf5baloowidgets5 libkf5bluezqt-data
 libkf5bluezqt6 libkf5calendarcore5abi2 libkf5calendarevents5
 libkf5calendarsupport-data libkf5calendarsupport5abi1
 libkf5calendarutils5 libkf5cddb5 libkf5contacteditor5
 libkf5contacts-data libkf5contacts5 libkf5dav-data libkf5dav5
 libkf5declarative-data libkf5declarative5 libkf5emoticons-bin
 libkf5emoticons-data libkf5emoticons5 libkf5eventviews-data
 libkf5eventviews5abi1 libkf5grantleetheme-plugins
 libkf5grantleetheme5 libkf5gravatar-data libkf5gravatar5abi2
 libkf5holidays-data libkf5holidays5 libkf5identitymanagement5
 libkf5imap-data libkf5imap5 libkf5incidenceeditor-data
 libkf5itemmodels5 libkf5kaddressbookgrantlee5
 libkf5kaddressbookimportexport5 libkf5kcmutils-data libkf5kdcraw5
 libkf5kdelibs4support-data libkf5kdelibs4support5
 libkf5kdelibs4support5-bin libkf5kexiv2-15.0.0 libkf5kipi-data
 libkf5kipi32.0.0 libkf5kmanagesieve5 libkf5konq6
 libkf5kontactinterface-data libkf5kontactinterface5 libkf5krosscore5
 libkf5krossui5 libkf5ksieve-data 

Re: Current status of KDE in Sid

[Miguel A. Vallejo]

Boris Pek wrote:

> What apt says you if you try to update a single package from KDE+Plasma stack?
> For example:
>
> sudo apt install -V dolphin

It says: dolphin is already the newest version (4:20.08.2-1).

And my sources.list points to the principal debian repository:

deb http://ftp.debian.org/debian/ unstable main contrib non-free

Any ideas?

Re: Current status of KDE in Sid

[Miguel A. Vallejo]

Thom Castermans () wrote:
>
> Hi Miguel,
>
> As I just wrote in another thread, you may need to `apt full-upgrade`
> instead of only `apt upgrade` to get the new KDE.
>
> Best,
> Thom

Hello Tom.

No luck, apt update keeps back almost 200 packages.

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

Current status of KDE in Sid

[Miguel A. Vallejo]

Hello.

Since a week ago (+/-) both apt upgrade and dist-upgrade want to keep
back / remove a TON of packages, most of them QT / KDE related. Since
I do not want to break the system, when will be safe to upgrade the
system?

I tried to upgrade only some programs because I use them regularly but
because they are QT based the effect is the same: apt wants to remove
a ton of packages and libraries, packages like dolphin,
kde-plasma-desktop, kmail or knotes. It doesn't seem to be the best
option right now.

What must I do? Wait some days more?

Thanks in advance

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

> https://bugs.kde.org/show_bug.cgi?id=404652
>
> is related?
>

Probably... because another thing I noticed recently is some file
extensions do not appear with an icon in Dolphin, just blank.

Re: KDE Stops opening new programs

[Miguel A. Vallejo]

Luca wrote:

> maybe this way you can find the culprit:
>
> $ lsof -U +c 15 | cut -f1 -d' ' | sort | uniq -c | sort -rn | head -3
>
And the winner is: thumbnail.so

I found the way to reproduce the problem.

In Dolphin, select a file. Right click and select delete. Press Ok in
confirmation dialog.

When pressing Ok a new "thumbnail.so [kdeinit5] thumbnail" process appears
in state S (interruptible sleep (waiting for an event to complete)
according to ps) and a new "Qt Selection Owner for thumbnail.so" entry in
xrestop. When entries reach 256, X stops to open new windows.

Fortunately a simple killall -9 thumbnail.so solves the problem.

Looking in debian packages there are two packages with a thumbnail.so file
in it: Imagemagick and kio-extras. I suspect the one bugging me is
kio-extras. Is it time to file a new bug against kio-extras?

KDE Stops opening new programs

[Miguel A. Vallejo]

Hello

I'm experiencing a weird behaviour from KDE for a few days with an
up to date debian unstable. From time to time it stops opening new
programs, and programs already opened are unable to display dialogs. I
suspect it is unable to open any new window.

Keeping a terminal open I tried to launch new programs when the problem
appears and I get this error:

"Maximum number of clients reached Error: cannot open display: :0"

Tried xrestop and it is full of entries with PID as ? and Identifier ""Qt
Selection Owner for thumbnail.so"

Log out / in does not solve the problem, a system reboot is needed to
return to normality (for a while)

Any ideas?

Thanks in advance

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

Hi John and thanks for the information.

I never imagined that so many programs depend on Firefox. If you use
Firefox regularly, it's not a problem, but for people like me who
rarely open it, it can be a headache.

Why are all these programs based on Firefox certificates and not on
/etc certificates? This creates a hidden dependency that can turn into
hell, just as it has been for me.

Anyway, my Okular it's working fine again. From now I'll be more
careful with the .mozilla directory.

Bug#966174: okular

[Miguel A. Vallejo]

After a small investigation in Debian's KDE mailing list we found the
affected PDF files were those digitally signed, and a simple
workaround was also found:

1.- Delete the .mozilla directory in your home directory

2.- Run Firefox. A new .mozilla directory should appear.

Now okular works just fine with these PDF files.

It has to be something related to poppler or libpoppler looking for
certificates in the .mozilla directory.

Also it is a case of an unexpected dependency of okular / poppler /
libpoppler with firefox that can affect no-firefox users, like me.
Okular doesn't work with digitally signed PDF unless you have a
working .mozilla directory, and this is only possible, as long as I
know, if you run firefox at least once.

Hope this helps.

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

> The strange thing is that here in "sid" okular works correctly.

I checked those packages and the only difference is I also have
okular-extra-backends. I tried to remove it but okular still crashes
opening those PDF files. It worked fine some weeks ago but an upgrade
must have broken it

> However I can reproduce the error if I run okular from a homedir without 
> .mozilla (where it seems to look for some certs)

Tested with and without .mozilla directory. But my .mozilla directory
does not seem to have any kind of certificates, only firefox related
files.

But...

I deleted the .mozilla directory, ran firefox to create it again and
now okular and pdfsig work just fine with the signed PDF.

I don't understand anything. Does Okular depend on firefox?

Anyway thank you for the clues. Now it is working.

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

Thank you for your advice. I reverted the packages to the ones
available in sid. Now waiting for okular to upgrade I really miss
it when working with these PDF files

Thank you

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

Upgraded poppler and libpoppler from experimental. Now pdfsig works,
but okular still crash

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

luca.pedrielli wrote:

> $ pdfsig your_signed.pdf
>
> is working?

No, it is not

~$ pdfsig BOE-A-2018-5704.pdf
Digital Signature Info of: BOE-A-2018-5704.pdf
Segmentation fault

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

> https://bugs.kde.org/show_bug.cgi?id=407369

It does not make sense... Those PDF files worked for me up to some
weeks ago. The PDF files seem to open normally right now on testing. I
think it is a different buf.

Bug#966174: okular: none

[Miguel A. Vallejo]

Package: okular
Version: 4:20.04.2-1
Severity: normal
X-Debbugs-Cc: none

Dear Maintainer,

Recently, Okular crashes opening certain PDF files that worked fine
just some weeks ago.

For example this PDF file:

https://www.boe.es/boe/dias/2018/04/26/pdfs/BOE-A-2018-5704.pdf

Opening with Okular produces

KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 8098
KCrash: Arguments: /usr/bin/okular BOE-A-2018-5704.pdf
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[1]+  Stopped okular BOE-A-2018-5704.pdf


Backtrace:

Application: Okular (okular), signal: Segmentation fault

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

[Current thread is 1 (Thread 0x7faa2242b840 (LWP 8098))]


Thread 7 (Thread 0x7faa0b2cf700 (LWP 8104)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55ef29fc4508) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ef29fc44b8, cond=0x55ef29fc44e0) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55ef29fc44e0, mutex=0x55ef29fc44b8) at
pthread_cond_wait.c:638

#3 0x7faa12b1375b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7faa12b13377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7faa255f8ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7faa260bcdaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 6 (Thread 0x7faa03fff700 (LWP 8103)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55ef29fc4508) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ef29fc44b8, cond=0x55ef29fc44e0) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55ef29fc44e0, mutex=0x55ef29fc44b8) at
pthread_cond_wait.c:638

#3 0x7faa12b1375b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7faa12b13377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7faa255f8ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7faa260bcdaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 5 (Thread 0x7faa0bad0700 (LWP 8102)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55ef29fc4508) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ef29fc44b8, cond=0x55ef29fc44e0) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55ef29fc44e0, mutex=0x55ef29fc44b8) at
pthread_cond_wait.c:638

#3 0x7faa12b1375b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7faa12b13377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7faa255f8ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7faa260bcdaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 4 (Thread 0x7faa0c2d1700 (LWP 8101)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55ef29fc4508) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ef29fc44b8, cond=0x55ef29fc44e0) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55ef29fc44e0, mutex=0x55ef29fc44b8) at
pthread_cond_wait.c:638

#3 0x7faa12b1375b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7faa12b13377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7faa255f8ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7faa260bcdaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 3 (Thread 0x7faa1b896700 (LWP 8100)):

#0 0x7faa24b597d4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#1 0x7faa24b0cd61 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#2 0x7faa24b0d71b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

#3 0x7faa24b0d90f in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#4 0x7faa2664790b in
QEventDispatcherGlib::processEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5

#5 0x7faa265ef89b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5

#6 0x7faa2641a8be in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5

#7 0x7faa26898507 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5

#8 0x7faa2641b988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5

#9 0x7faa255f8ea7 in start_thread (arg=) at
pthread_create.c:477

#10 0x7faa260bcdaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 2 (Thread 0x7faa2192b700 (LWP 8099)):

#0 0x7faa260b23bf in __GI___poll (fds=0x7faa2192ac68, nfds=1,
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

#1 0x7faa25886d02 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1

#2 0x7faa2588898a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1

#3 0x7faa22304dc0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

> maybe it's related to pdf digitally signed?

Probably yes

> libnss3 is involved?
>
> https://forum.kde.org/viewtopic.php?f=309=160361

My libnss3 hasn't been upgraded since I reinstalled the system last
February, so I'm not sure

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

After playing to downgrade all the Okular dependencies I can't
determine what package makes Okular to crash opening certain PDF
files. It's true I couldn't downgrade all packages without breaking
the whole system, but the ones I was able to downgrade are not the
culprits. I guess my only option now is to file a bug report.

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

Grzegorz Szymaszek wrote:
>
> Hi,
>
> I have reproduced the crash on the same version of Okular. Here is the
> backtrace of the main thread with dbgsyms installed:

Thank you. Although your backtrace seems a little different than
mine... any idea about the culprit package? It is clear to me it is
not okular itself.

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

> it's working here in testing(daily updated) with okular 4:20.04.2-1.

Yes, it is the same version I have in unstable, so the problem must be
elsewhere... probably in the graphic stack?

Thank you

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

> I can open it without any problem with okular in a Buster distro. Did
> you make any upgrade of graphics driver, or change or whatever about
> graphic drivers?
>
> Leopold

Probably... I run apt update/upgrade every few days and probably
something changed, but I do not know what. From Dr Konqi traceback I
can see problems in iris_dri.so, so maybe it is an Intel Graphics
issue? a Mesa issue? Until now Okular is the only program where I
noticed problems.

Re: Okular crashes opening some PDFs

[Miguel A. Vallejo]

John Scott wrote:

> Do you have one you're comfortable sharing (possibly off-list)?

Yes, for example this one:

https://www.boe.es/boe/dias/2018/04/26/pdfs/BOE-A-2018-5704.pdf

Just download it to your hard disk.

I have consulted it regularly since 2018 but since a few days it makes
okular to crash. It opens fine in other readers, for example in
Chrome.

eoz@waterhole:~$ okular BOE-A-2018-5704.pdf
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 3924
KCrash: Arguments: /usr/bin/okular BOE-A-2018-5704.pdf
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi



>From Dr Konqi:

Application: Okular (okular), signal: Segmentation fault

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

[Current thread is 1 (Thread 0x7f010dc97840 (LWP 3924))]


Thread 7 (Thread 0x7f00f5fc2700 (LWP 3930)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at
pthread_cond_wait.c:638

#3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7f0110e64ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7f0111928dcf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 6 (Thread 0x7f00f67c3700 (LWP 3929)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at
pthread_cond_wait.c:638

#3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7f0110e64ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7f0111928dcf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 5 (Thread 0x7f00f6fc4700 (LWP 3928)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at
pthread_cond_wait.c:638

#3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7f0110e64ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7f0111928dcf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 4 (Thread 0x7f00f77c5700 (LWP 3927)):

#0 futex_wait_cancelable (private=0, expected=0,
futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183

#1 __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508

#2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at
pthread_cond_wait.c:638

#3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so

#5 0x7f0110e64ea7 in start_thread (arg=) at
pthread_create.c:477

#6 0x7f0111928dcf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 3 (Thread 0x7f0106d32700 (LWP 3926)):

#0 __GI___libc_read (nbytes=16, buf=0x7f0106d31b20, fd=7) at
../sysdeps/unix/sysv/linux/read.c:26

#1 __GI___libc_read (fd=7, buf=0x7f0106d31b20, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24

#2 0x7f01103c0f4f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

#3 0x7f011037933e in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#4 0x7f0110379792 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

#5 0x7f011037990f in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#6 0x7f0111eb390b in
QEventDispatcherGlib::processEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5

#7 0x7f0111e5b89b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5

#8 0x7f0111c868be in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5

#9 0x7f0112104507 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5

#10 0x7f0111c87988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5

#11 0x7f0110e64ea7 in start_thread (arg=) at
pthread_create.c:477

#12 0x7f0111928dcf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 2 (Thread 0x7f010ceb1700 (LWP 3925)):

#0 0x7f011191e3df in __GI___poll (fds=0x7f010ceb0c68, nfds=1,
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

#1 

Okular crashes opening some PDFs

[Miguel A. Vallejo]

Hello. I noticed Okular now crashes opening some PDFs that worked
without problems a few days ago.

For example:

eoz@waterhole:~$ okular 2017.pdf
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 2251
KCrash: Arguments: /usr/bin/okular CNAF 2017.pdf
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

At first I thought of a recent Okular update, but it is version
4:20.04.2-1 and has not been upgraded since last March, so it must be
another package who has broken it.

Does anyone experience the same problem?

Re: phonon-backend-gstreamer-common has been kept back

[Miguel A. Vallejo]

Well, removed Kopete, some QT4 libs and KDE broke. Fortunately I was
able to restore it with some few apt-get install/remove

Everything seems to work now. I didn't realize the problem was QT4.

Thank you!

Re: phonon-backend-gstreamer-common has been kept back

[Miguel A. Vallejo]

> What if you manually do:
>
> apt-get install phonon-backend-gstreamer-common phonon phonon-backend-vlc
> ?

~# apt-get install phonon-backend-gstreamer-common phonon
phonon4qt5-backend-vlc
Reading package lists... Done
Building dependency tree
Reading state information... Done
phonon4qt5-backend-vlc is already the newest version (0.11.1-1).
phonon is already the newest version (4:4.10.3-2).
phonon set to manually installed.
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:
 phonon-backend-gstreamer : Depends: phonon-backend-gstreamer-common
(= 4:4.9.1-1) but 4:4.10.0-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.


> In any case it's just removing a few Qt4 applications and libraries, which you
> don't need anyway (apart maybe from kopete).

Removed Kopete and some programs, but still there are problems:



apt-get install phonon-backend-gstreamer-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
 espeak-ng-data festival festival-freebsoft-utils festlex-cmu
festlex-poslex festvox-kallpc16k icoutils kate-data katepart
kde-runtime-data kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools
kmouth libattica0.4 libdbusmenu-qt2 libdotconf0 libespeak-ng1
libestools2.5 libgpgme++2v5 libilmbase23 libkactivities6
libkatepartinterfaces4 libkcmutils4 libkde3support4 libkdeclarative5
libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4
libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4
libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpty4
libkrosscore4 libktexteditor4 libntrack-qt4-1 libntrack0 libopenexr23
libpcaudio0 libphonon4 libplasma3 libpolkit-qt-1-1 libqca2
libqca2-plugins libqt4-opengl libqt4-qt3support libqtwebkit4 libsolid4
libsonic0 libspeechd2 libthreadweaver4 libutempter0
ntrack-module-libnl-0 oxygen-icon-theme plasma-scriptengine-javascript
sound-icons speech-dispatcher speech-dispatcher-audio-plugins
speech-dispatcher-espeak-ng speech-dispatcher-festival
Use 'apt autoremove' to remove them.
Suggested packages:
 phonon-backend-gstreamer phonon4qt5-backend-gstreamer
The following packages will be REMOVED:
 jovie kde-runtime phonon phonon-backend-gstreamer
The following packages will be upgraded:
 phonon-backend-gstreamer-common
1 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Need to get 13.9 kB of archives.
After this operation, 12.2 MB disk space will be freed.
Do you want to continue? [Y/n]


He wants to remove kde-runtime and phonon itself.

Re: phonon-backend-gstreamer-common has been kept back

[Miguel A. Vallejo]

> Try to install phonon-backend-vlc, and then upgrade.

It's already installed

Re: phonon-backend-gstreamer-common has been kept back

[Miguel A. Vallejo]

Hi

> I don't have that problem on my Sid box.
> Can you share the output/result of
> "aptitude safe-upgrade phonon-backend-gstreamer-common" ?

Here it is:

~# aptitude safe-upgrade phonon-backend-gstreamer-common
Resolving dependencies...
The following packages have been kept back:
 phonon-backend-gstreamer-common{a}
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

> and if it's any different also from "full-upgrade"?

Yes, quite different:

~# aptitude full-upgrade phonon-backend-gstreamer-common
The following packages will be REMOVED:
 phonon-backend-gstreamer-common{u}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 38.9 kB will be freed.
The following packages have unmet dependencies:
phonon-backend-gstreamer : Depends: phonon-backend-gstreamer-common (=
4:4.9.1-1) but it is not going to be installed
The following actions will resolve these dependencies:

Remove the following packages:
1) jovie [4:16.08.0-1+b1 (now)]
2) kde-runtime [4:17.08.3-2.1 (now)]
3) kopete [4:17.08.3-2.1 (now)]
4) phonon [4:4.10.3-2 (now)]
5) phonon-backend-gstreamer [4:4.9.1-1 (now)]

Leave the following dependencies unresolved:
6) kdelibs5-plugins recommends kde-runtime
7) libkopete4 recommends kopete (= 4:17.08.3-2.1)



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

Keep the following packages at their current version:
1) phonon-backend-gstreamer-common [4:4.9.1-1 (now)]



Accept this solution? [Y/n/q/?] n

*** No more solutions available ***


And this is the apt output:

~# apt install phonon-backend-gstreamer-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
 espeak-ng-data festival festival-freebsoft-utils festlex-cmu
festlex-poslex festvox-kallpc16k icoutils kate-data katepart
kde-runtime-data kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools
kmouth libattica0.4 libbctoolbox1 libbzrtp0 libdbusmenu-qt2
libdotconf0 libespeak-ng1 libestools2.5 libgadu3 libgpgme++2v5
libilmbase23 libkabc4 libkactivities6 libkatepartinterfaces4
libkcmutils4 libkde3support4 libkdeclarative5 libkdesu5 libkdeui5
libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkio5
libkjsapi4 libkjsembed4 libkldap4 libkmediaplayer4 libkmime4
libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkopete4
libkparts4 libkpimidentities4 libkpimtextedit4 libkpimutils4 libkpty4
libkresources4 libkrosscore4 libktexteditor4 libmeanwhile1
libmediastreamer-base10 libmediastreamer-voip10 libntrack-qt4-1
libntrack0 libopenexr23 libortp13 libotr5 libpcaudio0 libphonon4
libplasma3 libpolkit-qt-1-1 libqca2 libqca2-plugins libqimageblitz4
libqjson0 libqt4-opengl libqt4-qt3support libqtwebkit4 libsolid4
libsonic0 libspeechd2 libthreadweaver4 libutempter0
ntrack-module-libnl-0 oxygen-icon-theme plasma-scriptengine-javascript
sound-icons speech-dispatcher speech-dispatcher-audio-plugins
speech-dispatcher-espeak-ng speech-dispatcher-festival
Use 'apt autoremove' to remove them.
Suggested packages:
 phonon-backend-gstreamer phonon4qt5-backend-gstreamer
The following packages will be REMOVED:
 jovie kde-runtime kopete phonon phonon-backend-gstreamer
The following packages will be upgraded:
 phonon-backend-gstreamer-common
1 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
Need to get 13.9 kB of archives.
After this operation, 32.2 MB disk space will be freed.
Do you want to continue? [Y/n]

I hope all these info helps

Thank you.

phonon-backend-gstreamer-common has been kept back

[Miguel A. Vallejo]

Hi

I noticed that phonon-backend-gstreamer-common have been keep back
since several weeks ago in Sid. If I try to update it manually apt
wants to remove the entire KDE.

Did I miss something?

Thanks in advance

Re: Hanging plasmashell

[Miguel A. Vallejo]

Yes, apt-listbugs didn't alert me neither.

If you have the bad luck to upgrade/update before someone open the
bug, you will eat it without any warning. apt-listbugs is not
bullet-proof, only helpful. Anyway I will stay in stable some time, I
need to get some job done.

Re: Hanging plasmashell

[Miguel A. Vallejo]

> Hi all,

> since some days I experience arbitrary hangs of plasmashell. When this
> happens, neither the application menu, the task bar nor any systray
> application respond to any mouse click. Alt+F2 doesn't work either and
> there is nothing else than "killall plasmashell && kstart plasmashell"
> to fix the problem. This is Debian/Sid, all packages up-to-date.

> Does anybody else experience similar problems?

Yes, same problem here. plasmashell hangs just opening the main menu,
clicking on the taskbar or even only hovering the mouse over the taskbar.

I looked in logs and I could not find any related error message. The only
way to get the system back again is to run killall plasmashell &&  kstart
plasmashell.

The problem is so annoying and frequent I moved (temporarily?) to stable
just to get work done.

Re: Request for cherry-picking konsole: Support for ECMA-48 REP

[Miguel A. Vallejo]

Same here. Everything is working again just fine.

A big thank you!

Re: Request for cherry-picking konsole: Support for ECMA-48 REP

[Miguel A. Vallejo]

Frank Mehnert  wrote:

>>> Would it be possible to cherry-pick that change for the current konsole
>>> package in Sid? IMHO that would make sense as it fixes a bug which is now
>>> triggered with the ncurses update from 20170729.

That would be nice. gpsmon and wavemon are also affected.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

> I think you should open a Qt bug on it. But add details on your font
> configuration, not just fontconfig but which fonts you are using (especially
> that toolbar/label font that renders wrong.

How can I get my particular font configuration? I can tell you how I
have configured libfreetype, how I have configured fontconfig, how I
have configured KDE and how I configured .Xresources to have a
consistent look across all programs but nothing more. Everything works
fine except that text labels in Qt applications. The problem seems to
be bold text is rendered without any hinting at all, so it is rendered
broken but I can't go further neither I can confirm this is exactly
what is happening. It's only my guessing.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

Thanks Martin, but I told some time ago that change broken totally the
rendering. I must set the system variable to get again version 35
render and everything went just fine until Qt 5.9 arrived.

With Qt 5.9 only that particular labels in Qt programs are rendered
wrong. Everything else is rendered just fine.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

> What Qt 5.9 does is setting the freetype property cff:no-stem-darkening to 0,
> where it normally defaults to 1. You can try adding "cff:no-stem-darkening=1"
> to FREETYPE_PROPERTIES, but I am no sure the environment variable will win.

cff:no-stem-darkening=1 makes no difference in Qt programs.



> if that does nothing, you could debug the issue for me by instead adding 
> "cff:no-
> stem-darkening=0" to FREETYPE_PROPERTIES and see if that makes non-Qt
> application exhibit the same rendering issue.

No. No changes. GTK programs render all fonts just right with this
setting set to 0.

In summary, I notice no changes setting this variable neither to 0 or
1. Neither in GTK or Qt programs.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

> Which is why I asked if you had upgraded that recently.

Thank for your comments Allan

I noticed the problem in the very first boot with Qt 5.9.1, as soon as
I opened Dolphin. I don't know if freetype was also upgraded or not at
that moment. I remember an upgrade to libfreetype6 some weeks ago that
also broke my font rendering. I solved it adding
FREETYPE_PROPERTIES="truetype:interpreter-version=35" as commented in
this bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866685

It worked nice and fonts were rendered again as they should be but
with Qt 5.9.1 I noticed those particular texts in Qt programs (which
seems have bold property enabled) are rendered in a bad form.
Everything else in Qt programs is rendered as expected. GTK programs
are not affected at all.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

> It was also be good to know if the issue goes away if you enable antialiasing.

Yes, enabling antialiasing solves the problem. It is just bold text,
rendered fine. But I must turn antialising off. Fuzzy and blurry fonts
produce me headache and visual fatigue.

Re: Warning! Current udisks2 in Sid is broken

[Miguel A. Vallejo]

> It's now available, at least on my mirror.

It is available in my mirror but:

The following packages have unmet dependencies:
udisks2 : Depends: libblockdev-part2 but it is not going to be installed

The following packages have unmet dependencies:
libblockdev-part2 : Depends: sgdisk (>= 0.8.6) but it is not installable

Package sgdisk is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'sgdisk' has no installation candidate

It is still broken.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

> Maybe something like "lsof | egrep '.ttf|.otf'" would enable you to spot
> usage in the picker of a font style that is bold by default, and changing
> your configured fonts or uninstalling that font would solve this.
>
> What fonts are configured in KDE's font settings?

No, I checked this the first day I saw it. The only font these
programs load is SegoeUI, the only one I have selected in KDE.

As experiment, I configured KDE to use bold SegoeUI, and it displays
perfect everywhere, including the places where it is rendered wrong
now.

I think those text widgets has a particular setting that makes the
font rendering broken under Qt 5.9.1, but this is only my guess.

Re: Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

>>> I can't even reproduce it :-(

Maybe my current font configuration helps:





 
  rgb
 


 
  true
 


 
  hintfull
 


 
  false
 



KDE settings is use system settings. I suspect it is trying to draw
that particular labels with another kind of hinting or even aliased
but I don't know how to debug it.

Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

Hello.

Since the last upgrade in Sid to Qt 5.9.1 I have noticed some fonts
rendered incorrectly in Qt applications, like Dolphin, VLC and some
other ones.

The rendered font seems to be some bolded text, but it is rendered
broken, see attached image.

Any ideas?

Thanks in advance.

Some fonts rendered incorrectly since upgrade to Qt 5.9.1

[Miguel A. Vallejo]

Hello.

Since the last upgrade in Sid to Qt 5.9.1 I have noticed some fonts
rendered incorrectly in Qt applications, like Dolphin, VLC and some other
ones.

The rendered font seems to be some bolded text, but it is rendered broken,
see attached image.

Any ideas?

Thanks in advance.



​