Hello Md,
not involved in packaging or development I was just trying
to collect more information about the crash for the maintainer.
I guess reassigning might not be a bad idea and might
give some feedback.
Another option would be to open an issue in the upstream
bug tracker (please put links here
Dear Bernhard,
As to what happens with nomodeset, I posted another bug report against gdm3:
http://bugs.debian.org/950504. There, we probably won't have to deal with a
gnome-shell segfault and Mesa issues that we have to deal with here.
Best regards,
Md Ayquassar
I added nomodeset as described in https://askubuntu.com/a/38834 . Then, the boot
process displayed some error concerning UMS and radeon early in the process, and
the screen resolution is different. The boot process still gets stuck, and
switching with Ctrl+Alt+F1 followed by Ctrl+Alt+F2 makes it c
In the attachment you find /var/log/Xorg.0.log. It contains some error message.
Concerning nomodeset: can I add it during boot process when the grub screen pops
up?
[37.930]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[37.931] Build Operating System: Linux 4.9.0-8-amd64 i686 D
Hello Md Ayquassar,
Am 31.01.20 um 02:23 schrieb Md Ayquassar:
> Second, is a reassignment to some Mesa package required?
I guess mesa maintainer would have more insight if
that function pointer is allowed to be NULL, there
possibly yes.
I wonder if the content of /var/log/Xorg.0.log* would
re
First, thanks for a quick response.
Second, is a reassignment to some Mesa package required?
Third, is there anything else I can do as a user to help the developers to
bugfix
this? Bug at line 1017 is strange: if there is a NULL dereference there, there
should also probably be one in line 1016 un
Hello Md Ayquassar,
sorry, I did not recognize that you
seem to have a usrmerge'd system.
Then I get following backtraces from your
core dump, with and without debug symbols.
It looks like a function pointer gets called
unconditionally, while containing NULL.
Seems to be graphics driver related.
Dear Bernhard:
In the attachment you find the output again and file generated, namely,
/tmp/reportbug-gnome-shell-backup-20200130-3154-vovyhuqk. (I think the
attachments might be easier to view due to line breaks at proper places.)
Best regards,
Md Ayquassar
reportbug-gnome-shell-backup-202001
Below you find the output of
guest@T42-LAPTOP:~$ reportbug --template gnome-shell
1>>/tmp/reportbug_output.log
2>&1
copied and pasted from the file repotbug_output.log:
Warning: no reportbug configuration found. Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale
Hello Md Ayquassar,
could you please additionally run following and attach the
output to this bug:
reportbug --template gnome-shell
I am asking because trying to open the coredump shows
following warning inside a minimal uptodate Buster/stable
VM, which could point to a incompatibility of some
Hello Md Ayquassar,
I am not involved in packaging gnome-shell, but may have
some pointers to gather some more informations for the
maintainer.
You could try to install the package systemd-coredump.
That way the output of 'journalctl --no-pager' should give
some information where the crash happene
11 matches
Mail list logo
