Bug#929818: sddm crashes after VT switch (but switching works fine without sddm)

[J. Pfennig]

Package: sddm
Version: 0.18.0-1
Severity: important

Concurrent X-Sessions can be started on other VTs (without sddm, just
xinit) and you can switch between these without any problem.

When switching back to the sddm VT (number 7) sddm crashes and so the
session is lost.

This behaviour is 100% reproducible on various notbooks.

(1) pam modification: the pam groups module now works fine with
sddm (pam was fixed since stretch, sddm was not usable with
stretch anyhow).

(2) here the trivial xinitrc used with startx to do testing:

#!/bin/sh
. /etc/X11/Xsession
if [ -x /usr/bin/startkde ] ; then
startkde
elif [ -x /usr/bin/twm ] ; then
twm &
xclock -g 130x130+900+10 &
xterm -g 120x35+10+10 -sb
fi

(3) Kernal taint: is virtual box, but the mentioned tests were
run on a real machine.

---

Thanks for your attention and your Debian engagement
Jürgen

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)

Versions of packages sddm depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.71
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libpam0g1.3.1-5
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5dbus5 5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-1
ii  libqt5network5  5.11.3+dfsg1-1
ii  libqt5qml5  5.11.3-4
ii  libqt5quick55.11.3-4
ii  libstdc++6  8.3.0-6
ii  libsystemd0 241-3
ii  libxcb-xkb1 1.13.1-2
ii  libxcb1 1.13.1-2
ii  qml-module-qtquick2 5.11.3-4
ii  x11-common  1:7.7+19
ii  xnest [xserver] 2:1.20.3-1
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  haveged1.9.1-7
ii  libpam-systemd 241-3
ii  sddm-theme-breeze [sddm-theme] 4:5.14.5.1-1
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.14.5.1-1
ii  sddm-theme-debian-elarun [sddm-theme]  0.18.0-1
ii  sddm-theme-debian-maui [sddm-theme]0.18.0-1

Versions of packages sddm suggests:
pn  libpam-kwallet5   
pn  qtvirtualkeyboard-plugin  

-- Configuration Files:
/etc/pam.d/sddm changed:
authrequisite   pam_nologin.so
authrequiredpam_succeed_if.so user != root quiet_success
@include common-auth
auth   optional   pam_group.so
-auth   optionalpam_gnome_keyring.so
-auth   optionalpam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
session optionalpam_keyinit.so force revoke
session requiredpam_limits.so
session requiredpam_loginuid.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
-session optional   pam_gnome_keyring.so auto_start
-session optional   pam_kwallet5.so auto_start
@include common-password
session requiredpam_env.so
session requiredpam_env.so envfile=/etc/default/locale user_readenv=1


-- no debconf information

Re: Mapbox GL plugin in QtLocation package

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El vie., 31 may. 2019 16:19, rinigus  escribió:

> Hi Dmitry and Lisandro:
>
> MapboxGL included into QtLocation is a special branch of that library:
> https://github.com/mapbox/mapbox-gl-native/tree/qt-staging . Let's keep
> that in mind during the discussion related to QtLocation, but we can extend
> it to the master branch as well, if needed.
>

So a special branch. Why that? For me it's just one more reason to keep
stuff like it is, or ask someone to package mapbox.


Re JSON license: From the code I in the master and qt-staging branch, I was
> able to find only one reference to the code from JSON.org and it was JSON
> checker included via https://github.com/Tencent/rapidjson as a submodule.
> Regarding that code there is a statement in the LICENSE specifying that it
> is only in
> https://github.com/Tencent/rapidjson/tree/master/bin/jsonchecker and can
> be skipped if not used. I wonder how to handle that case specifically, you
> probably know the coarse of action regarding it well.
>
> In addition, in qt-staging, rapidjson is not used, as far as I know. All
> corresponding functionality should be provided via Qt, as in
> https://github.com/mapbox/mapbox-gl-native/tree/qt-staging/platform/qt
>
> Re bundled software: from looking into
> https://github.com/mapbox/mapbox-gl-native/tree/qt-staging, it is clear
> that there are no more submodules in use. It seems that only
> https://github.com/mapbox/mapbox-gl-native/tree/qt-staging/vendor/nunicode
> is included as a third-party code.
>
>
> If we package qmapboxgl separately, is it known how to bundle it with
> QtLocation that way that it can be loaded as a module?
>

It probably needs to be worked out, but definitely preferred over embedding.

My interest stems from the fact that I use MapboxGL for rendering of the
> maps in Pure Maps (https://github.com/rinigus/pure-maps). Ironically, I
> am not using QtLocation plugin for it, but QMapboxGL directly through its
> unofficial QML bindings (ttps://github.com/rinigus/mapbox-gl-qml). This
> started for historical reasons (Sailfish has still rather old Qt which
> doesn't include MapboxGL) and seems to be continued since the unofficial
> bindings are quite convenient to use. There is also at least one aspect
> that is missing in official bindings that I use.
>
> So, in this respect having QMapboxGL separate and linked to QtLocation
> would be great. Then I could ask for help to get mapbox-gl-qml packaged as
> well to make the way for Pure Maps in Debian :)
>

Considering the size of mapbox I strongly think it should be packaged
separately, with a dedicated maintainer.

>

Re: Mapbox GL plugin in QtLocation package

[rinigus]

Hi Dmitry and Lisandro:

MapboxGL included into QtLocation is a special branch of that library:
https://github.com/mapbox/mapbox-gl-native/tree/qt-staging . Let's keep
that in mind during the discussion related to QtLocation, but we can extend
it to the master branch as well, if needed.

Re JSON license: From the code I in the master and qt-staging branch, I was
able to find only one reference to the code from JSON.org and it was JSON
checker included via https://github.com/Tencent/rapidjson as a submodule.
Regarding that code there is a statement in the LICENSE specifying that it
is only in https://github.com/Tencent/rapidjson/tree/master/bin/jsonchecker
and can be skipped if not used. I wonder how to handle that case
specifically, you probably know the coarse of action regarding it well.

In addition, in qt-staging, rapidjson is not used, as far as I know. All
corresponding functionality should be provided via Qt, as in
https://github.com/mapbox/mapbox-gl-native/tree/qt-staging/platform/qt

Re bundled software: from looking into
https://github.com/mapbox/mapbox-gl-native/tree/qt-staging, it is clear
that there are no more submodules in use. It seems that only
https://github.com/mapbox/mapbox-gl-native/tree/qt-staging/vendor/nunicode
is included as a third-party code.


If we package qmapboxgl separately, is it known how to bundle it with
QtLocation that way that it can be loaded as a module?

My interest stems from the fact that I use MapboxGL for rendering of the
maps in Pure Maps (https://github.com/rinigus/pure-maps). Ironically, I am
not using QtLocation plugin for it, but QMapboxGL directly through its
unofficial QML bindings (ttps://github.com/rinigus/mapbox-gl-qml). This
started for historical reasons (Sailfish has still rather old Qt which
doesn't include MapboxGL) and seems to be continued since the unofficial
bindings are quite convenient to use. There is also at least one aspect
that is missing in official bindings that I use.

So, in this respect having QMapboxGL separate and linked to QtLocation
would be great. Then I could ask for help to get mapbox-gl-qml packaged as
well to make the way for Pure Maps in Debian :).

Cheers,

Rinigus

On Fri, May 31, 2019 at 8:54 PM Dmitry Shachnev  wrote:

> Hi all,
>
> On Fri, May 31, 2019 at 02:45:29PM -0300, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > Hi Rinigus!
> >
> > On Thu, 23 May 2019 at 17:09, rinigus  wrote:
> > >
> > > Hi,
> > >
> > > I wonder whether it is possible to enable MapboxGL plugin in
> QtLocation?
> > > Or the state is still the same as in 2017, when the plugin got
> disabled?
> >
> > It seems it had lots of copyright issues, so removed form the tarball.
> >
> > Dmitry: do you remmeber which where the issues? it's not stated in the
> > changelog nor in the commit.
>
> The state is the same as in 2017. I described it briefly in
> .
>
> Mapbox is a much larger codebase than Qt Location so I would prefer it
> to be packaged separately.
>
> --
> Dmitry Shachnev
>

Re: Mapbox GL plugin in QtLocation package

[Lisandro Damián Nicanor Pérez Meyer]

Hi Rinigus!

On Thu, 23 May 2019 at 17:09, rinigus  wrote:
>
> Hi,
>
> I wonder whether it is possible to enable MapboxGL plugin in QtLocation? Or 
> the state is still the same as in 2017, when the plugin got disabled?

It seems it had lots of copyright issues, so removed form the tarball.

Dmitry: do you remmeber which where the issues? it's not stated in the
changelog nor in the commit.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#927014: qtcreator: Menu disapear

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo unreproducible

Hi bruno!

On Sat, 13 Apr 2019 at 12:39, bruno volpi  wrote:
>
> Package: qtcreator
> Version: 4.8.2-1
> Severity: normal
>
> Dear Maintainer,
>
> with KDE :
> application menu on global menu dashboard :
> disapear in change to another application and doesn't commes back
> application menu on title bar :
> disapear as soon i use Edition of ui
> application menu on menubar under title bar:
> sub menu transparency at 100% -> can't see it
> with Gnome :
> It works well

Sorry, I can't make sense of this. Can you try being more verbose?
Maybe using a translation service if necessary.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Re: trimage QT5 support

[Lisandro Damián Nicanor Pérez Meyer]

Hi Killian!

On Wed, 24 Apr 2019 at 10:18, Kilian Valkhof  wrote:
>
> Hi,
>
> Trimage is listed under `Apps using python-qt4, bugs not yet filed` on
> https://wiki.debian.org/Qt4Removal We've release a new version however,
> using python3 and python-qt5:
> https://github.com/Kilian/Trimage/releases/tag/1.0.6

You should really contact trimage's maintainer.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#929511: marked as done (qtcreator: Segfault on start)

[Debian Bug Tracking System]

Your message dated Fri, 31 May 2019 14:38:44 -0300
with message-id 

and subject line Re: Bug#929511: qtcreator: Segfault on start
has caused the Debian Bug report #929511,
regarding qtcreator: Segfault on start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
929511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtcreator
Version: 4.8.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable

This is what I get when I try to start qtcreator:

Program received signal SIGSEGV, Segmentation fault.
0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) ()
from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1

Complete backtrace, as from gdb:

#0  0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#1  0x7fffe6091ff3 in llvm::SmallPtrSetImplBase::insert_imp(void const*) () 
from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#2  0x7fffe6060d24 in llvm::cl::OptionCategory::registerCategory() () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#3  0x7fffd7602082 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#4  0x77fe439a in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7fffe498, env=env@entry=0x7fffe4a8)
at dl-init.c:72
#5  0x77fe4496 in call_init (env=0x7fffe4a8, argv=0x7fffe498, 
argc=1, l=) at dl-init.c:30
#6  _dl_init (main_map=main_map@entry=0x55909600, argc=1, 
argv=0x7fffe498, env=0x7fffe4a8) at dl-init.c:119
#7  0x77fe8303 in dl_open_worker (a=a@entry=0x7fffda10) at 
dl-open.c:517
#8  0x76447f8f in __GI__dl_catch_exception (exception=, 
operate=, args=) at dl-error-skeleton.c:196
#9  0x77fe7bea in _dl_open (file=0x55909538 
"/usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangTools.so",
mode=-2147479551, caller_dlopen=0x76ceffac, nsid=, 
argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-open.c:599
#10 0x7630f256 in dlopen_doit (a=a@entry=0x7fffdc30) at dlopen.c:66
#11 0x76447f8f in __GI__dl_catch_exception 
(exception=exception@entry=0x7fffdbd0, operate=,
args=)
at dl-error-skeleton.c:196
#12 0x7644801f in __GI__dl_catch_error (objname=0x5558cd00, 
errstring=0x5558cd08, mallocedp=0x5558ccf8,
operate=, args=) at
dl-error-skeleton.c:215
#13 0x7630f975 in _dlerror_run (operate=operate@entry=0x7630f200 
,
args=args@entry=0x7fffdc30) at dlerror.c:163
#14 0x7630f2e6 in __dlopen (file=, mode=) 
at dlopen.c:87
#15 0x76ceffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x76ce9c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x76cea1d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x77fad5dc in 
ExtensionSystem::Internal::PluginSpecPrivate::loadLibrary() ()
from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#19 0x77fa54cd in 
ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*,
ExtensionSystem::PluginSpec::State) () from 
/usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#20 0x77fa6650 in 
ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() ()
from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#21 0xeeb6 in ?? ()
#22 0x7633709b in __libc_start_main (main=0xca40, argc=1, 
argv=0x7fffe498, init=, fini=,
rtld_fini=, stack_end=0x7fffe488) at 
../csu/libc-start.c:308
#23 0xf50a in ?? ()

I tried the crude hack renaming the lib and symlinking to a newer
version, but that made things even worse. Besides, other programs
will be affected, too.


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages qtcreator depends on:
ii  libbotan-2-9   2.9.0-2
ii  libc6  2.28-1
ii  libclang1-71:7.0.1-8
ii  libgcc11:8.3.0-7
ii  libgl1-mesa-glx [libgl1]   13.0.6-1+b2
ii  libllvm7   1:7.0.1-8
ii  libqbscore1.12 

Processed: Re: Bug#927014: qtcreator: Menu disapear

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo unreproducible
Bug #927014 [qtcreator] qtcreator: Menu disapear
Added tag(s) unreproducible and moreinfo.

-- 
927014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#929785: kmail - deleted mails appear again

[Hans-J. Ullrich]

Package: kmail
Version: 4:18.08.3-1
Severity: important

Dear Maintainer,

I would like to inform you of the following behavior:

Mails, which are put into "trash" and are then deleted by "empty trash", appear 
after some days again in the trash folder. Among them there are mails, which 
are deleted several times, but appear again and again. Other older and already 
deleted mails suddenly appear again.

This is not also annoying, it is a security hole. Because when mails are 
deleted, then it often has a reason: In my case there are sometimes sensitive 
datas content.

This means: mails, which are deleted, shall be SURELY deleted and not appear 
again.

This bug exists almost from the beginning, but from time to time, from version 
to version, 
things get worse. So I set this bugreport to "important" although "critical" 
would be name it better.

Personally I believe, it all started with the implementation of akonadi. Maybe 
kmail should change to another database...

Thank you for reading this mail - and sorry, but ignoring this bug for such a 
long time gets me really "not amused".

Best regards

Hans
 

 

-e System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-5
ii  kdepim-runtime   4:18.08.3-4
ii  kio  5.54.1-1
ii  libc62.28-10
ii  libgcc1  1:8.3.0-6
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-5
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-5
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-5
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-2
ii  libkf5messagecore5abi1   4:18.08.3-2
ii  libkf5messagelist5abi1   4:18.08.3-2
ii  libkf5messageviewer5abi1 4:18.08.3-2
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-2
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-2
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-2
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a