Re: Postpone update
Am Mittwoch, 12. April 2023, 13:18:46 CEST schrieb Martin Steigerwald: > 2) Krunner segfaults, thus neither Alt-Space and in case still configure > Alt-F2 will work. > > There may be other issues. For the record: nheko is also segfaulting... Cheers, Johannes
Re: Future of "his" packages in Debian
Hi, > > Who is this clown again? > > I respect Norbert for the work he did on Plasma/KF/Application packages. > > I do not think it is fair to speak of him (or anyone else) as clown. > > From what I have perceived he contributed a lot to make timely releases > of packages happen. > > I don't know what is going on here… what this demotion thing about, so I > do not comment directly on it. > > I never had any issues with Norbert. Full ACK. Let's always keep discussions civil and in good faith... Gentle regards, Johannes
Re: Status of Plasma 5.18/5.19?
Hi Marco, On Montag, 29. Juni 2020 13:30:31 CEST Marco Valli wrote: > In data lunedì 29 giugno 2020 13:12:28 CEST, Norbert Preining ha scritto: > > Another great contribution that lines up perfectly with the rest! > > "I remain politely silent about your comments" > > https://imgflip.com/i/12zl00 May I suggest you stick to constructive forms of communication? Yes, Norbert could have answered your assertion that Christian Marillat is no longer remembered or no longer active in Debian in a more verbose form. Yet, what was your contribution to the debate when you sent "facepalm", twice? Cheers, Johannes
Re: Correction of a Kmail-Akonadi Bug
Hi, Sorry for only picking a minor question from your mail and not addressing the rest. But that's the only part I have the resemblance of an informed opinion: On Montag, 22. Juni 2020 18:51:49 CEST MERLIN Philippe wrote: > This version 4: 20.04: 1-1 is also that of the Debian testing version and I > am surprised that there are no more reports on this Bug, are very few > people using Kmail and Pop3? POP3 has been actively discouraged for the better part of the last 20 years, so I assume that you are indeed one of very few people that are still stuck with POP3 for one reason or another. As for kmail: I'm using kmail and I think (hope?) that there still is a sizeable user-base. Even after years of mostly akonadi-related woes it still is a great mail user agent (when it works)... Cheers, Johannes
Bug#918853: [qtcreator] ClangRefactoring impacts code model and causes crash on exit
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.
Bug#918410: [qtcreator] qtcreator freezes during startup
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: > > > 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 QT_XCB_NO_MITSHM=1, > > qtcreator does not freeze for me. > > And no ssh forwarding / X2Go, right? No ssh forwarding, and no X2Go. Everything runs local. I also tested just now (in case qtcreator tries to communicate with ssh-agent anyways) in a shell with SSH_AUTH_SOCK unset that the bug still appears. > > P.S.: I did read your other mail regarding testing without clang-related > > plugins under another user. Disabling those plugins under the same user > > does not change anything. I hope I can test with a fresh user tomorrow… > Please do. I can't reproduce the issue, so this will probably give us a > better idea. I just tested with a fresh user, and surprise: the bug does not appear! This is with ClangCodeModel and ClangTools enabled (as per default), without the QT_XCB_NO_MITSHM workaround. This prompted me to move ~/.config/QtProject out of the way on my regular account. This also worked. I then tried copying QtCreator.ini and QtCreator.db back into the QtProject directory, and everything still works. I also tried copying the toolchains/profiles/qtversion files back, but at that point I realized that to do this correctly I would need more knowledge about the internals than I have. So, in summary: 1. *Something* in my ~/.config/QtProject folder caused the problem. 2. Starting with a fresh QtProject folder, the problem disappears. 3. I could salvage my QtCreator.ini without apparent problems (recreating my kits is acceptable for me). I guess this can be attributed to some cruft accumulating in my QtProject folders over the years? If so, I guess it is fair to close this bug as invalid/worksforme/whatever… Thanks again, Johannes signature.asc Description: This is a digitally signed message part.
Bug#918410: [qtcreator] qtcreator freezes during startup
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 QT_XCB_NO_MITSHM=1, qtcreator does not freeze for me. Johannes P.S.: I did read your other mail regarding testing without clang-related plugins under another user. Disabling those plugins under the same user does not change anything. I hope I can test with a fresh user tomorrow… signature.asc Description: This is a digitally signed message part.
Bug#918853: [qtcreator] ClangRefactoring impacts code model and causes crash on exit
Package: qtcreator
Version: 4.8.0-1
Severity: normal
--- Please enter the report below this line. ---
When starting qtcreator with the ClangRefactoring plugin enabled, the code
model seems to get confused (Pressing F2 to jump to the implementation of a
method, as well as showing uses of a symbol does not work anymore).
Also, when the plugin is enabled, I get a segfault on exit.
If the plugin is not loaded, both problems disappear.
Note: This is the same machine as mentioned in bug #918410, so everything said
there applies here as well.
Attachments:
system_information.txt: System information as shown in Help|System information
gdb-qtcreator_*.log: Backtrace obtained using the following command:
QT_XCB_NO_MITSHM=1 gdb -q -ex 'set pagination off' -ex 'set width 0' --args
qtcreator -load ClangRefactoring
Kind regards,
Johannes
--- System information. ---
Architecture:
Kernel: Linux 4.19.0-1-amd64
Debian Release: buster/sid
500 unstable-debug debug.mirrors.debian.org
500 unstableftp.at.debian.org
--- Package information. ---
Depends(Version) | Installed
-+-
=
libqt5sql5-sqlite| 5.11.3+dfsg-2
qml-module-qtqml-models2 | 5.11.3-2
qml-module-qtquick-controls (>= 5.5.0~) | 5.11.3-2
qml-module-qtquick2 (>= 5.5.0~) | 5.11.3-2
qtchooser| 66-1
qtcreator-data (= 4.8.0-1) | 4.8.0-1
libbotan-2-5 | 2.6.0-3
libc6 (>= 2.28) |
libclang1-7 (>= 1:7~svn334604-1~exp1+0~) |
libgcc1 (>= 1:3.0) |
libgl1 |
libllvm7 (>= 1:7~svn298832-1~) |
libqbscore1.12 (>= 1.12.0) |
libqbsqtprofilesetup1.12 (>= 1.2.1) |
libqt5concurrent5(>= 5.6.2~) |
libqt5core5a (>= 5.11.0~rc1) |
libqt5designer5 (>= 5.6.2~) |
libqt5designercomponents5(>= 5.6.2~) |
libqt5gui5(>= 5.8.0) |
libqt5help5 (>= 5.9.0) |
libqt5network5 (>= 5.6.2~) |
libqt5printsupport5 (>= 5.6.2~) |
libqt5qml5(>= 5.1.0) |
libqt5quick5 (>= 5.9.0~beta) |
libqt5quickwidgets5 (>= 5.11.0) |
libqt5script5(>= 5.6.0~beta) |
libqt5serialport5 (>= 5.9.0) |
libqt5sql5 (>= 5.6.2~) |
libqt5widgets5 (>= 5.11.0~rc1) |
libqt5xml5 (>= 5.6.2~) |
libstdc++6(>= 7) |
qtbase-abi-5-11-3|
qtdeclarative-abi-5-11-2 |
Recommends(Version) | Installed
===-+-===
clang | 1:7.0-47
gdb | 8.2-1
make| 4.2.1-1.2
qmlscene| 5.11.3-2
qt5-doc | 5.11.3-1
qt5-qmltooling-plugins | 5.11.3-2
qtbase5-dev-tools | 5.11.3+dfsg-2
qtcreator-doc | 4.8.0-1
qtdeclarative5-dev-tools| 5.11.3-2
qttools5-dev-tools | 5.11.3-2
qttranslations5-l10n| 5.11.3-2
qtxmlpatterns5-dev-tools| 5.11.3-2
xterm | 341-1
OR x-terminal-emulator |
Suggests(Version) | Installed
=-+-===
clazy |
cmake | 3.13.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/{noformat}
Qt 5.11.3 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC
8.2.0) on "xcb"
OS: Debian GNU/Linux buster/sid [linux version 4.19.0-1-amd64]
Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1
Environment:
QT
Bug#918410: [qtcreator] qtcreator freezes during startup
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.asc Description: This is a digitally signed message part.
Bug#918410: [qtcreator] qtcreator freezes during startup
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 libqt5widgets5-dbgsym libqt5gui5-dbgsym
> libqt5dbus5-dbgsym libqt5core5a-dbgsym libglib2.0-0-dbgsym
> libgl1-mesa-dri-dbgsym libqt5qml5-dbgsym
Of course. See the attached log.
> If it shows up just sometimes you probably can describe your
> cpu and number of cores?
It's an Intel core 2 quad core processor. (See attached cpuinfo)
> Is it hanging too, if you start qtcreator with following command:
>
> taskset -c 0 qtcreator
Yes.
Cheers,
Johannes
Attaching to process 6830
[New LWP 6838]
[New LWP 6839]
[New LWP 6840]
[New LWP 6841]
[New LWP 6842]
[New LWP 6843]
[New LWP 6850]
[New LWP 6851]
[New LWP 6852]
[New LWP 6853]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f30b472bbe9 in __GI___poll (fds=fds@entry=0x7ffe6eb51908, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
29 ../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden.
Thread 11 (Thread 0x7f3071ab4700 (LWP 6853)):
#0 0x7f30b472bbe9 in __GI___poll (fds=0x7f3064003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret =
#1 0x7f30b38cf016 in g_main_context_poll (priority=, n_fds=1, fds=0x7f3064003ce0, timeout=, context=0x7f3064000bf0) at ../../../glib/gmain.c:4221
ret =
errsv =
poll_func = 0x7f30b38de730
poll_func =
ret =
errsv =
#2 g_main_context_iterate (context=context@entry=0x7f3064000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3915
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 1
allocated_nfds = 1
fds = 0x7f3064003ce0
#3 0x7f30b38cf13c in g_main_context_iteration (context=0x7f3064000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
retval =
#4 0x7f30b4e92153 in QEventDispatcherGlib::processEvents (this=0x7f3064000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422
d = 0x7f3064000b40
canWait = true
savedFlags = {i = 0}
result =
#5 0x7f30b4e3f14b in QEventLoop::exec (this=this@entry=0x7f3071ab3e00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
d = 0x7f3064004770
locker = {val = 93913471330160}
ref = {d = 0x7f3064004770, locker = @0x7f3071ab3d88, exceptionCaught = true}
app =
#6 0x7f30b4c8e106 in QThread::exec (this=this@entry=0x5569ef192670) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
d = 0x5569ef192700
locker = {val = 93913471330160}
eventLoop = { = {_vptr.QObject = 0x7f30b50c63c8 , static staticMetaObject = {d = {superdata = 0x0, stringdata = 0x7f30b4fc04e0 , data = 0x7f30b4fc03c0 , static_metacall = 0x7f30b4e70840 , relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x7f3064004770}, static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f30b4fc32a0 , data = 0x7f30b4fc0600 , static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = 0x7f30b50bea40 , stringdata = 0x7f30b4fbaf80 , data = 0x7f30b4fbaf20 , static_metacall = 0x7f30b4e3ee70 , relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode =
#7 0x7f30b44e8375 in QQmlThreadPrivate::run (this=0x5569ef192670) at qml/ftw/qqmlthread.cpp:148
No locals.
#8 0x7f30b4c97cd7 in QThreadPrivate::start (arg=0x5569ef192670) at thread/qthread_unix.cpp:367
thr = 0x5569ef192670
data =
eventDispatcher =
__clframe = {__cancel_routine = 0x7f30b4c97200 , __cancel_arg = 0x5569ef192670, __do_it = 1, __cancel_type = }
#9 0x7f30b4b27fa3 in start_thread (arg=) at pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139846042208000, 5836240979638185000, 140730755782894, 140730755782895, 139846042208000, 0, -5864076587482649560, -5863942509390238680}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#10 0x7f30b473689f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 10 (Thread 0x7f3072ffd700 (LWP 6852)):
#0 0x7f30b472bbe9 in __GI___poll (fds=0x7f306c004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret =
#1 0x7f30b38cf016 in g_main_context_poll (priority=, n_fds=1, fds=0x7f306c004a00, timeout=,
Bug#918410: [qtcreator] qtcreator freezes during startup
Package: qtcreator Version: 4.8.0-1 Severity: normal --- Please enter the report below this line. --- After upgrading to qtcreator 4.8.0-1, I experience qtcreator reproducibly "freezing" during startup. Starting qtcreator using "qtcreator -profile" revealed that the "Help" module is the last one that is loaded so I tried starting qtcreator with "-noload Help" and it starts correctly. In that case I do get a segfault later on when I quit qtcreator, but that's probably unrelated. I also use some of the Clang related plugins (just mentioning this in case it might be relevant). Cheers, Johannes --- System information. --- Architecture: Kernel: Linux 4.19.0-1-amd64 Debian Release: buster/sid 500 unstableftp.at.debian.org --- Package information. --- Depends(Version) | Installed -+- = libqt5sql5-sqlite| 5.11.3+dfsg-2 qml-module-qtqml-models2 | 5.11.3-2 qml-module-qtquick-controls (>= 5.5.0~) | 5.11.3-2 qml-module-qtquick2 (>= 5.5.0~) | 5.11.3-2 qtchooser| 66-1 qtcreator-data (= 4.8.0-1) | 4.8.0-1 libbotan-2-5 | 2.6.0-3 libc6 (>= 2.28) | libclang1-7 (>= 1:7~svn334604-1~exp1+0~) | libgcc1 (>= 1:3.0) | libgl1 | libllvm7 (>= 1:7~svn298832-1~) | libqbscore1.12 (>= 1.12.0) | libqbsqtprofilesetup1.12 (>= 1.2.1) | libqt5concurrent5(>= 5.6.2~) | libqt5core5a (>= 5.11.0~rc1) | libqt5designer5 (>= 5.6.2~) | libqt5designercomponents5(>= 5.6.2~) | libqt5gui5(>= 5.8.0) | libqt5help5 (>= 5.9.0) | libqt5network5 (>= 5.6.2~) | libqt5printsupport5 (>= 5.6.2~) | libqt5qml5(>= 5.1.0) | libqt5quick5 (>= 5.9.0~beta) | libqt5quickwidgets5 (>= 5.11.0) | libqt5script5(>= 5.6.0~beta) | libqt5serialport5 (>= 5.9.0) | libqt5sql5 (>= 5.6.2~) | libqt5widgets5 (>= 5.11.0~rc1) | libqt5xml5 (>= 5.6.2~) | libstdc++6(>= 7) | qtbase-abi-5-11-3| qtdeclarative-abi-5-11-2 | Recommends(Version) | Installed ===-+-=== clang | 1:7.0-47 gdb | 8.2-1 make| 4.2.1-1.2 qmlscene| 5.11.3-2 qt5-doc | 5.11.3-1 qt5-qmltooling-plugins | 5.11.3-2 qtbase5-dev-tools | 5.11.3+dfsg-2 qtcreator-doc | 4.8.0-1 qtdeclarative5-dev-tools| 5.11.3-2 qttools5-dev-tools | 5.11.3-2 qttranslations5-l10n| 5.11.3-2 qtxmlpatterns5-dev-tools| 5.11.3-2 xterm | 341-1 OR x-terminal-emulator | Suggests(Version) | Installed =-+-=== clazy | cmake | 3.13.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/
Re: kdeconnect clipboard passwords security
Hi, Am Donnerstag, 18. Oktober 2018, 18:57:06 CEST schrieb Sandro Knauß: > I can follow the reasons why it is a good idea to do this. Nevertheless this > is not a Debian packaging issue, so please get in contact with kdeconnect > team and discuss this with them (upstream). If it is fixed upstream, we can > look further, how we get it into Debian: > https://community.kde.org/KDEConnect#Development Just for reference, these bugs seem to be relevant: https://bugs.kde.org/show_bug.cgi?id=386568 https://bugs.kde.org/show_bug.cgi?id=392164 Cheers, Johannes
Re: Akregator in KDEPIM 18.08 crashes very often
Am Mittwoch, 10. Oktober 2018, 23:29:08 CEST schrieb Martin Steigerwald: > Hi! > > Often when clicking on a link. > > I had three or four crashes in just five minutes. Do you use nouveau by any chance? Just guessing, but this sounds like this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886428 Cheers, Johannes
Re: kdeconnect doesn't
Am Freitag, 28. September 2018, 20:39:01 CEST schrieb Gary Dale: > This shouldn't be an issue but I have also had 3 different routers since > I first tried to use kdeconnect. It didn't work with any of them handing > out IP addresses It may very well be an issue. Some routers provide firewalling and isolation between hosts on the same network. If you use a pre-configured router by your ISP, they might have configured some isolation between the hosts. (And if all threee routers have been from the same ISP, they should be configured the same). By any chance, do your Linux PCs use a wired connection? The fact that the PCs can talk to each other, but not to the phone(s) could be caused by the router isolating wired network ports from wireless ones. Johannes
Re: Akonadi Database maintenance
Hi Martin, On Donnerstag, 17. August 2017 22:23:54 CEST Martin Steigerwald wrote: > Johannes Zarl-Zierl - 17.08.17, 21:16: > > This doesn't work for me, either (tested on two sid machines): > > > > $ mysql_upgrade --socket=~/.local/share/akonadi/socket-mani > > You gave the directory instead of the "mysql.socket" socket file inside that > directory. You're right, but it doesn't make a difference :( I also tried it with the exact socket parameter mysqld was started with (and now also with the mysql.socket file in above directory) to no avail. Interestingly enough, mysql_upgrade shows the same error, whether the socket exists or not :| I verified like this: $ cd ~/.local/share/akonadi/socket-mani/ $ ls -l insgesamt 0 srwxr-xr-x 1 zing zing 0 Aug 17 23:00 akonadiserver.socket srwxrwxrwx 1 zing zing 0 Aug 17 21:02 mysql.socket $ mysql_upgrade --socket mysql.socket Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed Cheers, Johannes
Re: Akonadi Database maintenance
Hi, This doesn't work for me, either (tested on two sid machines): $ mysql_upgrade --socket=~/.local/share/akonadi/socket-mani Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed On Mittwoch, 16. August 2017 13:05:02 CEST Martin Steigerwald wrote: > You are running mysql_upgrade as the user Akonadi is running in? I can't talk for anxiousmac, but I do run it as the same user, within my desktop session. > Is MySQL/MariaDB, well Akonadi, running? MySQL/MariaDB needs to run for the > command to be able to contact it. Mysql is running: 3068 ?Sl 0:12 /usr/sbin/mysqld --defaults-file=/home/zing/.local/ share/akonadi/mysql.conf --datadir=/home/zing/.local/share/akonadi/db_data/ -- socket=/tmp/akonadi-zing.F1xri4/mysql.socket Using the socket file directly (instead of the symlink, as shown above) does not make a difference. I also tried adding the "--defaults-file" option to mysql_upgrade, but that is not recognised (even though the man page says otherwise). > What does mysql.err log say? Nothing at all. I've got the startup messages and the obvious "Native table XYZ has the wrong structure" messages, but after the version/socket line there are no messages. Johannes
Bug#842174: [sddm] sddm crashes when second session is started
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 up in an endless loop and prevents me from accessing a text console due to the whole VT switching). So I guess that makes Xorg or nvidia-legacy-340xx-driver the main suspects? > I've produced a patch that handles reading an empty displaynumber (which > means that the file was closed), sadly I can't test it, as I would need an X > video driver that can't handle more than one display. > > I'm attaching it, please let me know if you can test this. I'll look into "apt-get source" and dpkg-buildpackage so that I can test this... > I'll forward this information upstream. Thanks. Cheers, Johannes
Bug#842174: Acknowledgement ([sddm] sddm crashes when second session is started)
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_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-5 ii libgcc1 1:6.2.0-9 ii libpam0g1.1.8-3.3 ii libqt5core5a5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5network5 5.6.1+dfsg-3+b1 ii libqt5qml5 5.6.1-11 ii libqt5quick55.6.1-11 ii libstdc++6 6.2.0-9 ii libsystemd0 231-9 ii libxcb-xkb1 1.12-1 ii libxcb1 1.12-1 ii qml-module-qtquick2 5.6.1-11 ii sddm-theme-breeze [sddm-theme] 4:5.8.2-1 Versions of packages sddm recommends: ii libpam-systemd 231-9 Versions of packages sddm suggests: ii libpam-kwallet5 5.8.2-1 -- debconf information: * shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm
Bug#842174: [sddm] sddm crashes when second session is started
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. Choose "Start new session" on screen lock
-> The sddm login session is shown
4. Start a session as user B
5. At this point "ps -flu A" shows that the first session is already dead
The interesting snippet from journalctl:
Okt 25 23:22:27 mani sddm[4650]: Adding new display on vt 8 ...
Okt 25 23:22:27 mani sddm[4650]: Display server starting...
Okt 25 23:22:27 mani sddm[4650]: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{b0c48caa-23a6-4e2c-9061-51f0f945afa8} -background none -noreset
-displayfd 19 vt8
Okt 25 23:22:28 mani sddm[4650]: Running display setup script
"/usr/share/sddm/scripts/Xsetup"
Okt 25 23:22:28 mani sddm[4650]: Display server started.
Okt 25 23:22:28 mani sddm[4650]: Socket server starting...
Okt 25 23:22:28 mani sddm[4650]: Socket server started.
Okt 25 23:22:28 mani sddm[4650]: Greeter starting...
Okt 25 23:22:28 mani sddm[4650]: Adding cookie to
"/var/run/sddm/{b0c48caa-23a6-4e2c-9061-51f0f945afa8}"
Okt 25 23:22:28 mani sddm[4650]: /usr/bin/xauth: (stdin):1: bad "remove"
command line
Okt 25 23:22:28 mani kernel: sddm[4650]: segfault at 0 ip 7fe10bfceb63
sp 7ffe7a5fb120 error 4 in libQt5Core.so.5.6.1[7fe10bd16000+4c6000]
Okt 25 23:22:28 mani sddm[4650]: /usr/bin/xauth: (stdin):2: bad "add"
command line
Okt 25 23:22:28 mani sddm[4650]: Display server stopped.
Okt 25 23:22:28 mani sddm[4650]: Running display stop script
"/usr/share/sddm/scripts/Xstop"
Okt 25 23:22:28 mani sddm[4650]: Socket server stopping...
Okt 25 23:22:28 mani sddm[4650]: Socket server stopped.
Okt 25 23:22:28 mani sddm[4650]: Removing display "" ...
Okt 25 23:22:28 mani sddm[4650]: QProcess: Destroyed while process
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Okt 25 23:22:28 mani systemd[1]: sddm.service: Main process exited,
code=killed, status=11/SEGV
Okt 25 23:22:28 mani org.kde.kpasswdserver[5397]: The X11 connection broke
(error 1). Did the X11 server die?
Okt 25 23:22:28 mani org.kde.KScreen[5397]: The X11 connection broke (error
1). Did the X11 server die?
Okt 25 23:22:28 mani polkitd(authority=local)[658]: Unregistered
Authentication Agent for unix-session:19 (system bus name :1.158, object path
/org/kde/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8) (disconnected from
bus)
Okt 25 23:22:28 mani org.a11y.Bus[5397]: Activating service
name='org.a11y.atspi.Registry'
Okt 25 23:22:28 mani org.kde.kglobalaccel[5397]: The X11 connection broke
(error 1). Did the X11 server die?
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Checking for pam module
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Got pam-login param
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: Waiting for hash on 15-
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: waitingForEnvironment on: 18
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: client connected
Okt 25 23:22:28 mani sddm[4650]: kwalletd5: client disconnected
--- System information. ---
Architecture: amd64
Kernel: Linux 4.7.0-1-amd64
Debian Release: stretch/sid
500 unstableftp.at.debian.org
--- Package information. ---
Depends (Version) | Installed
=-+-==
adduser | 3.115
qml-module-qtquick2 | 5.6.1-11
sddm-theme-breeze | 4:5.8.2-1
OR sddm-theme|
debconf (>= 0.5) | 1.5.59
OR debconf-2.0 |
libc6 (>= 2.14) |
libgcc1(>= 1:3.0) |
libpam0g(>= 0.99.7.1) |
libqt5core5a (>= 5.5.0) |
libqt5dbus5(>= 5.0.2) |
libqt5gui5 (>= 5.4.0) |
libqt5network5 (>= 5.0.2) |
libqt5qml5 (>= 5.0.2) |
libqt5quick5 (>= 5.0.2) |
libstdc++6 (>= 5.2) |
libsystemd0 |
libxcb-xkb1 |
libxcb1 |
Recommends (Version) | Installed
=-+-===
libpam-systemd| 231-9
Suggests (Version) | Installed
==-+-===
libpam-kwallet5| 5.8.2-1
Bug#797765: (no subject)
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 if the package would at least show up in a search for qtquick. Is it possible to change the package description of qtdeclarative5-dev to something like this: >> This package contains the header development files for building some >> >> >> Qt 5 applications using Qt 5 declarative (aka QtQuick2) headers. Another way to make the situation more transparent to users would be to add something like this to the package description of qtquick1-5-dev: >> In order to build Qt Quick 2 applications on Qt5, you need to install the >> package qtdeclarative5-dev, instead. Cheers, Johannes
Re: Possible disagreement between emacs and plasma in handling .desktop files - which one is right?
Hi, > Which I would read as suggesting that a singular [Desktop Entry] is > intended, but it's not explicitly clear and I'm not familiar with the spec. > > Does anyone have any idea which is the correct approach? Reading the spec, this seems to be a bug in the emacs desktop file: "Multiple groups may not have the same name." [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s02.html#group-header] Cheers, Johannes
Re: qdbus commands in 64-bit jessie?
On Thursday 03 September 2015 18:28:35 D. R. Evans wrote: > The reference to i386 is a bit puzzling, since this is a 64-bit system. > Anyway, I discovered that all attempts to execute qdbus commands from the > command line produce the same error :-( To me this seems like a problem with qtchooser. Maybe you've got a configuration file pointing it to the i386 qt4 version of qdbus? > > What do I need to do to get my qdbus commands working again? If my analysis is correct, you need to find the problematic config file and remove(or fix) it. Good places to start are: $HOME/.config/qtchooser/default.conf /etc/xdg/qtchooser/default.conf /usr/lib/*-linux-gnu/qtchooser/default.conf Cheers, Johannes signature.asc Description: This is a digitally signed message part.
Bug#797765: [qtquick1-5-dev] qtquick1-5-dev is not enough to create qtquick applications
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 following error: $ /usr/lib/x86_64-linux-gnu/qt5/bin/qmake qtquick-videotest.pro Project ERROR: Unknown module(s) in QT: qml quick Additionally installing qtdeclarative5-dev fixed compilation for me (but it is not immediately obvious that qtdeclarative is necessary to enable the qt modules qml and quick). Would it be possible to add a dependency on qtdeclarative5-dev to qtquick1-5- dev? --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 990 testing ftp.at.debian.org 1001 unstablesnapshot.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
