Dear Maintainer,

When i try to start falkon it crash.
I currently use i3 as DE.

I provide a log file generated with :
strace falkon &>> falkon.log

I can provide more if needed.

Hello Bardot Jerome,
I am just looking at some random bug reports with crashes.

The last page of the strace output might point into the
direction of the graphic driver, you are using the free
nouveau driver?

For more information you might consider adding the dbgsym
repositories to your system like described here:

https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Then the following packages would be needed:

    gdb falkon-dbgsym libgl1-mesa-dri-dbgsym

And then start in an terminal window falkon with this command:

    script -a ~/gdb-falkon_$(date +%Y-%m-%d_%H-%M-%S).log -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run' -ex 'info reg' -ex 'display/i \$pc' -ex 'bt' -ex 'info share' -ex 'bt full' -ex detach -ex quit --args falkon"

That should create a gdb-galkon_*.log text file in your
home directory, that you could forward to this bug.

Kind regards,
Bernhard

Hello,

First thx because you make a clear response to my email.
With clear step even if i m not even advance developer & debian power
user to understand all the command line.

For next time i just add 2 LC_ALL=C.

And the command line become :

LC_ALL=C script -a ~/gdb-falkon_$(date +%Y-%m-%d_%H-%M-%S).log -c
"LC_ALL=C gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run'
-ex 'info reg' -ex 'display/i \$pc' -ex 'bt' -ex 'info share' -ex 'bt
full' -ex detach -ex quit --args falkon"

To your question about graphic driver yes i always try to use Free
Drivers. It’s a little non sense to use a free distro with non free stuff.


Let me know if you need more information

Jerome

Le 28/05/2019 à 18:08, Bernhard Übelacker a écrit :

Hello Bardot Jerome,
unfortunately the debug information did not yet cover
all functions in the backtrace.
The backtrace would be perfect if libdrm-nouveau2-dbgsym
would be installed.

But from the visible parts, following issues seem simliar,
at least the "Assertion `kref' failed." seems equal:


https://bugs.debian.org/927954
https://bugs.freedesktop.org/show_bug.cgi?id=91632


You might also want to look through "dmesg -T" output
if there is anything related to nouveau in the given time.
That might also be helpful for the maintainer.

The output of "lspci -nn | grep VGA" might be helpful too.


This bug might then also be forwarded to libdrm-nouveau2.

Kind regards,
Bernhard

Le 29/05/2019 à 21:14, Bernhard Übelacker a écrit :

Done, i regenerate the execution log file. And add it.

Maybe should i talk about the fact i use a splitter to use 2 screen with
my video card.
I add the output for previous execution (there is 2 minutes between
falkon log and dmesg log because first time i didn’t had LC_ALL=C ) and
re add previous log for libdrm-nouveau
add it to

How can i do that ? add the bug number@bugs.debian.org is enought ?
Let me know if it missing something else.

Control: tag -1 moreinfo

This bug is quite old and it would be useful to know whether the issue
still exists.

I looked at your dmesg log and I'd recommend to update your BIOS and
make sure you have the latest intel-microcode package installed.

- BIOS A19 05/17/2016
You were running BIOS A19 (2016-05-27) and according to [1] there's now
an A28 version from 2019-07-15.

Once you've done that you can check the 'health' of your system with
the following commands:
- dmesg --level emerg,alert,crit
- dmesg --level emerg,alert,crit,err
- dmesg --level emerg,alert,crit,err,warn

Doing it in that sequence allows you to focus on the most important issues
first before looking into the 'minor' ones.
Getting results on the 1st command is pretty bad. On the last one is to
some extend expected, but may be worth looking into nonetheless.

HTH

[1] https://www.dell.com/support/home/en-us/product-support/product/precision-t1700-workstation/drivers