On Tue, 07 May 2024 11:30:41 +0200 antonio wrote:
Dear Maintainer,
when I try to add a online account (Systemsettings->Pesonalization->Online
Accounts->Add new account... button) I get this error:
Thread 1 "systemsettings" received signal SIGSEGV, Segmentation fault.
0x7fffc40f8765 in
On Fri, 1 Dec 2023 00:26:27 +0100 Lucy wrote:
#3 0x7fbe9c25afd0 __restore_rt (libc.so.6 + 0x3bfd0)
#4 0x557d83358770 n/a (baloo_file + 0x13770)
#5 0x557d8335885d n/a (baloo_file + 0x1385d)
#6 0x557d83365bf1 n/a (baloo_file + 0x20bf1)
#7 0x7fbe9cadd6f0
Hello,
I tried to reproduce this inside a minimal stable/bookworm VM
and received a qmlcachegen crash.
See attached file for details.
The resulting backtrace is quite similar to that found in:
https://bugreports.qt.io/browse/QTBUG-117361
Might avoid the crash, but cannot say if this would
Dear Maintainer,
I tried to reproduce this issue and found a difference between
a minimal Bookworm VM with just running jwm window manager and my
regular Plasma desktop.
In the minimal VM a `kstart5 kcalc` returns immediately,
while at my regular Plasma desktop it blocks until the started
Stack trace of thread 67345:
#0 0x7f8daa6a9ccc n/a (libc.so.6 + 0x8accc)
#1 0x7f8daa65aef2 raise (libc.so.6 + 0x3bef2)
#2 0x7f8dabf4c83d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x583d)
#3
Am 24.01.23 um 00:30 schrieb piorunz:
On 23/01/2023 22:46, Bernhard Übelacker wrote:
https://bugs.debian.org/1028197
On Mon, 23 Jan 2023 21:48:23 + piorunz wrote:
On 23/01/2023 13:35, Bernhard Übelacker wrote:
journalctl --user --since="2023-01-08 12:10" --until="20
https://bugs.debian.org/1028197
On Mon, 23 Jan 2023 21:48:23 + piorunz wrote:
On 23/01/2023 13:35, Bernhard Übelacker wrote:
journalctl --user --since="2023-01-08 12:10" --until="2023-01-08 12:12"
-- No entries --
Then please try something like this:
journalctl
Am 23.01.23 um 23:07 schrieb piorunz:
On 23/01/2023 21:59, Bernhard Übelacker wrote:
Hello Piotr,
if it is not clear it would be possible to take
the bug number from the email addresses and open
the bug page e.g. https://bugs.debian.org/1028208.
This was just about the plasma-discover crash
Am 23.01.23 um 22:48 schrieb piorunz:
On 23/01/2023 13:35, Bernhard Übelacker wrote:
(gdb) bt
#0 0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x7fbffe79dbe1 in KCrash::defaultCrashHandler(int
(gdb) bt
...
#4
#5 0x7f54b82563fb in QQuickItem::~QQuickItem() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6 0x7f54b83d0045 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7 0x7f54b66dd53f in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8
(gdb) bt
#0 0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x7fbffe79dbe1 in KCrash::defaultCrashHandler(int) () from
/lib/x86_64-linux-gnu/libKF5Crash.so.5
#3
#4 0x7fbffc2a9ccc in ?? ()
Am 22.01.23 um 14:19 schrieb Gregor Riepl:
FYI: My kded core dumps also contained something about a closed DBus
connection in a different thread's stack trace. Perhaps this is related?
I am not able to exclude it to be related, maybe it is the start of the
row of events. When debugging
On Fri, 06 Jan 2023 16:50:02 +0100 Gregor Riepl wrote:
...
#14 0x7f9c8c26f6ed in QObject::connect<...> (...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:268
#15 TransactionJob::TransactionJob (...) at ./apperd/TransactionJob.cpp:47
#16 0x7f9c8c271648 in
On Fri, 30 Dec 2022 09:46:49 -0300 craudio wrote:
#8 0x7f2ba43e5b99 n/a (kded_apperd.so + 0xeb99)
#9 0x7f2becae8fcf n/a (libQt5Core.so.5 + 0x2e8fcf)
#10 0x7f2ba4323095
_ZN10PackageKit6Daemon22transactionListChangedERK11QStringList
(libpackagekitqt5.so.1 + 0xe095)
Hello,
this
Short addition:
I tried to bring this to the attention of packagekit-qt
developers in this bug report:
https://github.com/PackageKit/PackageKit-Qt/issues/42
Kind regards,
Bernhard
Dear Maintainer,
I was able to reproduce this issue inside a minimal
amd64 qemu VM running Bookworm/testing.
By editing the kded service unit [1] I could get valgrind have a look
at this issue and it produced a matching use-after-free [2].
By further editing the service unit I was also able to
Dear Maintainer,
I retested this inside a minimal Bookworm/testing VM now because
the last plasma package updates seem to have settled a bit.
Unfortunately the black background
and the 30 seconds splash are still visible.
At least in this bug report at least the black
default wallpaper gets
On Tue, 13 Dec 2022 01:28:39 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
Dear Maintainer,
I experienced since about a month ago sometimes crashes in applications
running in fullscreen, when doing display configuration changes
or lately when waking up the screen from power saving.
(See
Package: plasma-workspace
Version: 4:5.26.4.1-1
Severity: normal
X-Debbugs-Cc: bernha...@mailbox.org
Dear Maintainer,
I noticed since a week or so a change in behaviour of a plasma desktop.
If i install in a minimal VM the package task-kde-desktop after logging
into the desktop no wallpaper is
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=463052
Dear Maintainer,
I tried to have a look if I can find some more information,
and opened an issue upstream here:
https://bugs.kde.org/show_bug.cgi?id=463052
It looks like a double free because a pointer is hold in two lists.
Hello,
that will still not be enough for further investigation,
but the given byte sequence in conjunction the package from
snapshot.d.o including the dbgsym package points to this location:
0x...cfb in QThreadStorageData::get() const at thread/qthreadstorage.cpp:122
@piorunz: a first step
Package: libqt5core5a
Version: 5.15.6+dfsg-2
Severity: wishlist
X-Debbugs-Cc: bernha...@mailbox.org
Dear Maintainer,
I experienced since about a month ago sometimes crashes in applications
running in fullscreen, when doing display configuration changes
or lately when waking up the screen from
plasma panel sometimes hangs, becomes irresponsive. this is preceded by
some notification appearing in the notification area, that becomes stuck
in the corner of the windows and cannot be dismissed. at the same time
all the panel becomes irresponsive to mouse clicks.
my only workaround is
On Fri, 09 Sep 2022 11:25:50 + Christian Buhtz wrote:
installed "kde-config-cron" without having a full KDE desktop environment
enabled. I am using XFCE here but would like to have cron gui front-end.
After installation I can not find a binary for "kde-config-cron".
It seems to me that
Hello Bob,
On Wed, 20 Oct 2021 15:33:47 +0800 Bob Wong wrote:
Hello, I am unable to downgrade the kdecoration, if I try to downgrade
kdecoration, the apt will remove the whole kde desktop. So the only choice
for me is to upgrade. When will the new version of the kdecoration be
available in
Control: merge -1 996859
Hello Achim,
I hope it is ok to try to merge those two bugs #996859 and #996860,
BTS takes some time to confirm creating a bug ...
Have you updated lately libkdecorations2-5v5 to 4:5.23.0-2 ?
Then you probably hit this bug #996726,
where a workaround is described by
Hello Francisco, hello Albert,
this might be the same as in bug #996726
and not directly related to the nvidia driver.
I hit a crash in kwin_x11 with an AMD graphics card
and could workaround by installing
libkdecorations2-5v5_5.21.5-2_amd64.deb like
mentioned in #996726.
Kind regards,
Bernhard
Hello Patrick,
I guess this is the same as described in bug #996726.
And I was able to workaround by installing
libkdecorations2-5v5_5.21.5-2_amd64.deb.
Kind regards,
Bernhard
Core was generated by `/usr/bin/kwin_x11 --replace'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0
Hello Torbjørn Birch Moltu,
I tried to reproduce this issue inside a virtual machine.
But there the menu opens without the issue.
Does this happen to you if you startup without the wacom input attached?
Next thing you could try is to startup krita this way:
export MALLOC_CHECK_=3
krita
Hello Russel,
thank you for the detailed backtraces.
Unfortunately they point into Qt's javascript module,
finally trying to copy memory to a null pointer.
I have not found a hint to similar crashes in
upstream bug tracker.
Could you please provide which theme you are using,
or if there are
Hello Russel,
thanks for the fast answer, unfortunately the
backtrace is not yet enough expressive.
Maybe you could also install the following debug symbol packages?
libqt5qml5-dbgsym libqt5core5a-dbgsym libqt5widgets5-dbgsym libqt5gui5-dbgsym
kwin-common-dbgsym kwin-x11-dbgsym
These are
Hello Silvério,
Reading symbols from /usr/bin/kwin_wayland...
(No debugging symbols found in /usr/bin/kwin_wayland)
BFD: warning: /tmp/user/1000/coredump-ySV5m6 is truncated: expected core file
size >= 2365169664, found: 2147483648
it looks like for some reason the kwin_wayland exceeds
the
Hello Russell,
could you still see this issue?
Stack trace of thread 120123:
#0 0x7f49c3823ce1 n/a (/lib/x86_64-linux-gnu/libc-2.31.so
(deleted) + 0x3bce1)
Were there more lines following in the "Stack trace of thread 120123"?
And as
Hello Silvério,
Am 31.03.21 um 20:42 schrieb Silvério Santos:
Hallo Bernhard,
Here is it:
Mär 31 20:11:25 systemname kernel: kwin_wayland[1834]: segfault at e8 ip
7fe70ba08268 sp 7ffc9bbf64d0 error 4 in
libKWaylandServer.so.5.20.5[7fe70b9b+b6000]
Mär 31 20:11:25 systemname
Hello Santos,
I tried to reproduce this issue but did not see it inside a minimal VM.
Therefore tried to some more information from the Code bytes printed in
you journal/dmesg.
This should point to this instruction:
0x7f6e16bd5268
Hello everyone,
I added it, and now I got one:
Tue 2021-03-23 20:20:40 CET2000 109 115 11 present
/usr/bin/sddm-greeter
If I extract it, I get:
Executable: /usr/bin/sddm-greeter
...
#9 0x7fe7b41f5def __clone (libc.so.6 + 0xfddef)
With this "coredumpctl
Am 20.03.21 um 21:44 schrieb Helge Kreutzmann:
If I should install a -dbg version or something else please
inform me.
Thank you for the additional information.
There might really be something more. If you have not, is it possible
to install the package "systemd-coredump".
If then a crash
Hello Helge,
do you still see these messages in your logging?
If yes could you maybe add the surrounding logging
of one such fault? E.g. by something like this:
journalctl | grep "traps:" -C20
Kind regards,
Bernhard
Hello Helge,
do you still see these messages in your logging?
If yes could you maybe add the surrounding logging
of one such fault? E.g. by something like this:
journalctl | grep "traps:" -C20
Kind regards,
Bernhard
Hello Sandro, hello Norbert,
this sounds like the feature "Highlight lines coming into view" [1].
There is an option that looks like it could be disabled in:
Profiles - Scrollbars - "Highlight the lines coming into view"
Kind regards,
Bernhard
Hello Joe,
this information might not be sufficient for the maintainer.
Could you try following to collect some more informations?
- install packages:
gdb psmisc konqueror-dbgsym
- stop all running instances of konqueror:
killall konqueror
- then start konqueror inside a debugger:
Dear Maintainer,
I could reproduce it with the state of Debian testing at 2020-07-24.
Upstream bugs seem to be these:
https://bugs.kde.org/show_bug.cgi?id=407338
https://gitlab.freedesktop.org/poppler/poppler/-/issues/766
The issue seems to be resolved since poppler 0.77 and above.
Kind
Package: kmix
Version: 4:20.08.0-1
Severity: normal
Forwarded: https://bugs.kde.org/show_bug.cgi?id=425469
Tags: upstream fixed-upstream
Dear Maintainer,
I found several kmix cores lately and investigated a bit.
It crashes when attempting to do some cleanup on process exit.
There unfortunately
Hello Sarah,
I am sorry, but the given information might not be enough
for the maintainers to solve the crash.
Usually when a segfault happens in 'dmesg' output should
appear two lines about this event. Maybe you could forward
these to the report too.
If it is possible to install
Hello Jan,
please leave the bugs email in the recipients or cc list to
have all information attached to the bug e.g. by using "reply all".
Nice to hear it works.
You can close a bug by just changing the email recipient from
'950...@bugs.debian.org' to '950537-d...@bugs.debian.org'.
Kind regards,
Hello Jan,
your issue might originate not from the terminal but from su itself.
This might be an interesting read:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904988#20
But in short, is instead of 'su' using 'su -' working
for you like expected?
Kind regards,
Bernhard
Control: found -1 plasma-workspace/4:5.14.5.1-5
Dear Maintainer,
I found today another device affected by this issue.
It got switched a few days ago from stable to current testing.
It shows the same 30 second splash screen.
A package build with the given patch did show the
splash just 14
Dear Maintainer,
I got today the same crash as the submitter.
It happened short after disconnecting one android device,
connecting another and opening/retrying the MTP connection.
This upstream bug looks related:
https://bugs.kde.org/show_bug.cgi?id=415693
(Seems to be also from buster due to
Control: notfound -1 4:18.04.1-1
Control: found -1 4:19.08.1-1
Control: tags -1 unreproducible moreinfo
Hello Hans,
I tried to reproduce inside a minimal plasma testing VM.
But I could not see a noticeable amount of messages in
.xsession_errors while playing kpat.
If this is still visible on
Control: tags -1 - upstream
Hello Felix,
maybe the information from following bug is
relevant in this case too.
https://bugs.debian.org/942860
Kind regards,
Bernhard
Hello Karl,
I am not involved in the packaging of phonon, but
still a few questions.
Have you any Qt4 applications installed?
Because src:phonon in version 4:4.10.3-2 was the last
version that built the Qt4 parts.
Since src:phonon 4:4.10.3-3 just the Qt5 packages
get build anymore.
And
Package: libkf5kiocore5
Version: 5.54.1-1
Severity: normal
Tags: patch upstream
Dear Maintainer,
in the last year I hit a few crashes with kate,
without knowing how to reproduce the crash.
Today I found this upstream reports [1] and several
duplicates. With that information it was easy to
Dear Maintainer,
I guess the actual segmentation fault is fixed since kamoso 3.2.4-1.
Instead it should print this message:
The webcam controller was unable to find or load wrappercamerabinsrc plugin;
please make sure all required gstreamer plugins are installed.
The last question would
Control: tags -1 - moreinfo
Dear Maintainer,
I think the top frames with debug symbols would look like this:
(gdb) bt
#0 memcpy () in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7feaa926d05d in Baloo::PostingCodec::decode () at
./src/codecs/postingcodec.cpp:42
#2
Hello Leoš Pohl,
thanks for the additional information.
Please use the reply-all in your email program, to have
the ...@bugs.debian.org recipient in every answer, so
the debian bug tracker receives the messages too.
Just for future crashes (or if the Mainainter will requests it),
if you install
Weitergeleitete Nachricht
Datum: Wed, 7 Aug 2019 15:44:44 -0400
Von:Leoš Pohl
Hello Bernhard,
since I could not find a way to forward the report directly
to this bug, please find screenshots here
https://snag.gy/mpTyWe.jpg and here https://snag.gy/lUKpRc.jpg
and the
Control: tags -1 + moreinfo
Hello Leos Pohl,
you write when you execute "balooctl enable" you receive
some lines starting with "KCrash: ...".
When this happened, is there a small sad smiley [1] in the
system tray (normally at the bottom, left of the clock)?
If yes, you should receive by
Hello David,
that was not the link I sent in my mail,
I sent a plain link to bugs.debian.org.
Maybe you are viewing my mail via google webmail client,
and that is adding something unwanted?
Kind regards,
Bernhard
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-77017
Dear Maintainer,
I created an upstream bug report and forward this bug to it.
Kind regards,
Bernhard
Hello David,
I could find an issue with konsole freezing
and reported it in this bug:
https://bugs.debian.org/931844
Maybe you want to have a look if you find your issue there.
Kind regards,
Bernhard
Package: libqt5gui5
Version: 5.11.3+dfsg1-1
Severity: wishlist
Tags: upstream
Affects: konsole orca
Dear Maintainer,
I noted some recent additions to bug #594506 which I guess
describe a different problem. I did some investigations and
tripped on the issue with following steps:
- Installed in a
Hello Francis Laniel,
I am just looking at some crashes in some random packages,
and found this nouveau issue familiar.
I guess __pthread_cond_wait_common should be able to
handle a NULL for abstime - e.g. should "Block without a timeout".
Hello David,
I am not involved in packaging, just tried to collect some more
information to this old bug.
I guess your issue migth not be that one discussed in this bug.
At least you might be able to provide the output of 'dmesg',
if in your case konsole really crashes.
Or after installing the
Control: tags 928710 + upstream
Control: forwarded 928710 https://bugs.kde.org/show_bug.cgi?id=381644
Dear Maintainer,
above the upstream bug of this issue.
Kind regards,
Bernhard
Hello Joe Ma,
On Sun, 20 Jan 2019 19:59:27 +0800 Joe Ma wrote:
> Hello Bernhard,
> For your question, I do execute your gdb command in the console by a shell
> script when kate freeze. What information do you want me to add? I will
> reply asap.
sorry for the late reply, I did not notice your
Control: tags 886692 + unreproducible moreinfo
Hello Alberto,
I just tried to get some more information from this crash.
I assume this is not caused by the length of the current directory.
Instead I think this is caused by this file:
Control: reassign 927954 libdrm-nouveau2 2.4.97-1
Control: affects 927954 + konqueror
Hello Osama Nasr,
> I'm so sorry for that,
> I just reinstalled KDE and every thing works fine,
> I'm sorry if that a waste of your time.
Glad to hear that it is working.
But as this might be a threading
Hello Osama Nasr,
> oh, this system is running in a VM, that
> might be important information.
>
> But I'm runing it as my main OS, I mean I'm not runnig on VM.
>
> BTW, when using Budgie, the problem disappear...
What output gives this command:
lspci -nn | grep VGA
Kind regards,
Hello Osama Nasr,
> glxinfo -B
> name of display: :0
> display: :0 screen: 0
> direct rendering: Yes
> Extended renderer info (GLX_MESA_query_renderer):
> Vendor: VMware, Inc. (0x)
> Device: llvmpipe (LLVM 7.0, 256 bits) (0x)
oh, this system is running in a VM, that
Hello Adrian,
so unfortunately it has still no clear error.
In your .xsession-errors is tcosmonitor mentioned.
As this package got 2016 removed [1] from debian - do you
have still installed tcosmonitor or tcosmonitor-common?
If yes, maybe that might cause some troubles?
If no, which file tries
Hello Adrian,
> Using a console login and startx, everything works fine though.
>
> Logging in into amiwm works fine though!
>
> I also can't use a session created through xdm or a login manager
> because a lot of GNOME and GTK complain or even seqfault and won't
> start after creating a
Hello Osama Nasr,
> Thanks a lot for your help, but actually i don't need that app, I just
> was reporting this bug.
I am also not involved in packaging konqueror, just tried to collect
some more information, for the maintainers to work with.
> Do you need me to install proprietary drivers
Hello Osama Nasr,
> By the way, I've installed GIMP, although there was a bug
> (libmypaint-common #906144).
> I don't know if that have a relation or not.
On a short look I guess this is not related.
> konqueror: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion
> `kref'
Hello Osama Nasr,
please use the "reply all" to answer - that way the information
is automatically stored also in the bugs web site:
https://bugs.debian.org/927954
Kind regards,
Bernhard
Am 25.04.19 um 18:19 schrieb Osama Nasr:
> By the way, I've installed GIMP, although there was a bug
Control: retitle 927940 [Windows Subsystem for Linux] Applications cannot find
libQt5Core.so.5
Hello Ryo,
> I encountered this problem with my WSL environment.Not quite the usual kernel
> ... ;-)
A google search leads to this information [1]
and this bug [2].
There a workaround is provided
Hello Osama Nasr,
I tried to reproduce this issue in a minimal Unstable VM
with plasma-desktop and konqueror installed.
But could not reproduce it.
Could you try to start it from a konsole and forward
the output you get there after you hit this bug?
And have you configured something non-default
Hello Ryo IGARASHI,
I just trying to triage this bug, and have in a minimal
Buster amd64 VM installed just paraview installed and
could not reproduce the issue.
Could you please check the output in your system for any
differences to the outputs below:
dpkg -l | grep -E
Hello Dave Kitchen,
I am not involved in packaging kate, just trying to collect
some more information.
You wrote you open via nautilus - so you are running a
Gnome/Wayland desktop session?
I tried to reproduce the issue in a Gnome/Wayland session
but could not find a problem. In kate the native
Hello Adrian,
> I don't have any of those old GNOME applications installed, you mentioned.
Then these files should not be there I guess like e.g.:
/usr/share/glib-2.0/schemas/org.gnome.EasyTAG.gschema.xml
On a system where e.g. easytag is installed a 'dpkg -S' returns this:
$ dpkg -S
Dear Maintainer,
so both issues have the same root and upstream commited this,
to open the dbus interface as soon as possible.
https://cgit.kde.org/plasma-workspace.git/commit/?id=9a4bb220c162f031b4d45ed04f9e156b6d0b852e
Kind regards,
Bernhard
Control: tags 924402 + upstream
Hello Dimitry,
thanks for your quick response.
> Can I ask you to submit your patch upstream to [1], either as a pull
> request or as a simple issue?
I just created this pull request:
https://github.com/annulen/webkit/pull/803
Kind regards,
Bernhard
Hello Everyone,
I think the same issue manifested in bug #924402.
To me it looks like the problem started when -fpermissive
got added to get the i386 build working again.
Without that a compiler error "invalid conversion" got hit,
because a derived class missed the attribute fastcall.
In bug
Control: tags 924402 + patch
Hello Everyone,
I continued to look into the "invalid conversion" and think
the problem is member JSImageConstructor::construct is
missing the __attribute__((fastcall)) aka JSC_HOST_CALL.
Attached patch to qtwebkit-opensource-src-5.212.0~alpha2
removes the
reassign 923720 libappstreamqt2 0.10.6-2
Control: reassign 923720 libappstreamqt2/0.10.6-2
Control: affects 923720 plasma-discover
Control: fixed 923720 libappstreamqt2/0.11.3-1
Control: fixed 923720 plasma-discover/5.10.5-1
Control: tags 923720 + upstream fixed-upstream patch
Hello Everyone,
tried to get some more information from
Control: tags 920139 + unreproducible moreinfo
Hello Adrian Immanuel,
I am sorry for the late reply.
First a question: Do you still observe this fault?
I took a look today inside the md5sums you supplied
and tried to reproduce this setup inside a VM.
Unfortunately I found following old
Package: plasma-workspace
Version: 4:5.14.5.1-1
Severity: normal
Tags: patch upstream
Dear Maintainer,
I found that the splash screen takes longer than some month ago and did
some investigations that led to following two upstream bugs I reported.
Bug 405444 - ksplashqml hits its hard timeout
Hello Sandro,
Am 05.03.19 um 00:43 schrieb Sandro Knauß:
> Btw. please use the bugnumber-qu...@bugs.debian.org rarely, because than
> maintainers like me don't gets any mails, that's why I missed your
> conversation.
Sorry for using -quiet - Pino Toscano made me already
aware to avoid -quiet.
Hello Adrian,
maybe one of the installed source files lead
to a bad gschemas.compiled file?
Could you create a file with the md5sums of all
the xml files that seem to get combined into that
gschemas.compiled file.
md5sum /usr/share/glib-2.0/schemas/* >
Control: tags 920139 + moreinfo
Hello Adrian,
Am 03.02.19 um 09:24 schrieb Adrian Immanuel Kiess:
> The bug is, like I see it, that the applications cannot find the
> gsettings schema directory.
>From my point of view it might be more the file gschemas.compiled
inside that directory. Does that
Hello Rokas,
I just tried to collect some more information and
could reproduce the crash with Qt 5.11.1+dfsg-8.
With version 5.11.2+dfsg-3 and current 5.11.3+dfsg-2
I was not able anymore to reproduce.
Can you confirm that the bug is not visible
anymore on your installation?
Kind regards,
Hello Adrian Immanuel Kiess,
I tried to search the net about this message:
"GLib-GIO-ERROR: No GSettings schemas are installed on the system"
And found results pointing to .../share/glib-2.0/schemas/.
Therefore renamed following file:
/usr/share/glib-2.0/schemas/gschemas.compiled
And
Hello Francois Marier,
this looks like a duplicate of bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919765
Kind regards,
Bernhard
Hello André Isidoro Fernandes Esteves,
one more possibly useful thing to consider:
If you could install a core dump collector like package
systemd-coredump, then the system would store a file of
each crash for later inspections.
Also it would already print a backtrace in the system journal.
Control: tags -1 + moreinfo
Hello Daniel Sutil,
just got to this bug report.
Do you still get this crash?
If it got solved for you, you could close this bug by sending
an email to 904094-d...@bugs.debian.org
If you still get it, you could follow these steps:
- install package gdb
- open a
Control: forward -1 https://bugs.kde.org/show_bug.cgi?id=359664
Control: tags -1 upstream fixed-upstream
Control: fixed -1 plasma-workspace/4:5.12.0-2
Dear Maintainer, hello Michael Meier,
from the segfault line I would suspect that this
crash happened in sniproxy.cpp, line 273.
There image may
Hello Pino,
On Sun, 20 Jan 2019 15:28:44 +0100 Pino Toscano wrote:
> What is the reason why you send the messages to nnn-quiet@, instead
> of nnn@? -quiet means that the maintainer does *not* get any
> notification, so none of your emails reach the maintainer mailing list.
> Also, if the user
Hello Steve,
I suspect this lookup error is because you have
knewstuff packages in version 5.54.0-1 installed,
which is not yet in testing (and barely in unstable).
Could reproduce it with packages below installed:
Hello Lisandro,
> Do we have an upstream bug number?
Mateus Barbosa mentioned this one already when opening the bug:
https://bugreports.qt.io/browse/QTBUG-72488
Kind regards,
Bernhard
signature.asc
Description: OpenPGP digital signature
Control: affects 919607 + krita
Dear Maintainer, hello Mateus Barbosa,
there is another debian bug report that looks similar [1].
As far as I see this is a Qt upstream bug, but not yet resolved.
Krita upstream has two commits [2] to workaround that issue
until a fixed Qt version gets available.
1 - 100 of 140 matches
Mail list logo
