.2-1
g++ | 4:8.2.0-2
git | 1:2.20.1-1
kate-data | 4:4.14.3-5
subversion| 1.10.3-1+b1
valgrind | 1:3.14.0-2
--
Johannes Zarl-Zierl
FSFE local group Linz, Team Austria
https://wiki.fsfe.org/LocalGroups/Linz_en/
Hello Bernhard,
Am Montag, 7. Jänner 2019, 01:00:13 CET schrieb Bernhard Übelacker:
> thanks for your fast respone.
You're welcome.
> Can you repeat that gdb command with following additional
> dbgsym packages installed, to complete the backtraces:
>
> libxcb1-dbgsym libqt5gui5-dbgsym libqt
Hello Bernhard,
Am Mittwoch, 9. Jänner 2019, 19:19:04 CET schrieb Bernhard Übelacker:
> I fear I cannot help on this issue any deeper.
Thanks for your help! You enabled me to find a workaround for the immediate
issue, making the bug only a minor nuisance for me.
Cheers,
Johannes
signature.a
.2.0-2
git | 1:2.20.1-1
kate-data | 4:4.14.3-5
subversion | 1.10.3-1+b1
valgrind | 1:3.14.0-2
--
Johannes Zarl-Zierl
FSFE local group Linz, Team Austria
https://wiki.fsfe.org/LocalGroups/Linz_en/{noformat}
Qt 5.11.3 (x86_64-l
Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
Pérez Meyer:
> Can you tell us which exactly was? In this way:
>
> - other users reading the report might benefit from it
> - we might end up finding a proper solution
Sorry, I thought that was clear from the context. With
Am Donnerstag, 10. Jänner 2019, 21:23:55 CET schrieb Lisandro Damián Nicanor
Pérez Meyer:
> El miércoles, 9 de enero de 2019 20:06:33 -03 Johannes Zarl-Zierl escribió:
> > Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
> >
> > Pérez Meyer:
> &
Am Freitag, 11. Jänner 2019, 22:17:29 CET schrieb Lisandro Damián Nicanor
Pérez Meyer:
> > Note: This is the same machine as mentioned in bug #918410, so everything
> > said
> > there applies here as well.
>
> If this still true with the other bug solved?
Yes.
On Friday 02 October 2015 16:13:24 Lisandro Damián Nicanor Pérez Meyer wrote:
> This really happens because qtcreator is using the QtQucik2 aka
> "declarative" stuff. The QtQuick1 stuff is being kept only for old
> not-yet-ported stuff.
Thanks for the explanation.
In this case it would be nice i
Hi Maximiliano,
On Freitag, 11. November 2016 11:01:02 CET Maximiliano Curia wrote:
> I think that xdm and lxdm don't support this, you'll need lightdm or gdm3
> for starting a new session.
Using lightdm I could reproduce this. Actually, lightdm's reaction is a lot
worse than sddm (lightdm ends
Package: sddm
Version: 0.13.0-1
Severity: normal
--- Please enter the report below this line. ---
On my system, sddm crashes when I open a second login session, thus closing/
killing my original session and active programs.
Steps to reproduce:
1. Start a plasma session as user A
2. Lock screen
3.
By request, I'm also including the information gathered by reportbug:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_
Package: qtquick1-5-dev
Version: 5.4.2-2
Severity: normal
--- Please enter the report below this line. ---
I had installed qtquick1-5-dev, thinking this ought to be the correct package
to use qtquick in a qtcreator project.
However, trying to build the qtcreator qtquick template left me with the
Package: libmarble-dev
Version: 4:24.12.3-2
Severity: normal
X-Debbugs-Cc: johan...@zarl-zierl.at
Dear Maintainer,
libmarble-dev is missing a dependency on qt6-5compat-dev.
E.g. having installed libmarble-dev, but not qt6-5compat-dev, marble is
not found by cmake:
CMake Warning at
/usr/sh
13 matches
Mail list logo
