New answers tagged debugging
Core dumping is disabled by default in Ubuntu by setting the maximum dumping file size to 0 for all users. You can check this by: ulimit -c By default it would show 0. Now to enable core dumping, set the size to the value you want (or unlimited). For example, setting the maximum dumping file size as 4 KB: ulimit -c 8 -c takes block numbers with each ...
You can change it from settings. Go to System settings -> Appearance -> Behavior. There you will see an option "Show the menus for a window", and there are two choices. Either in the menu bar or in the window's title bar. Try both and use whichever you like. PS: Please see the figure below.
You can also use systemctl status to look at the tail of the logs, plus any other information that systemd has about that service: systemctl status snapd.refresh.service For example: $ systemctl status lightdm.service ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled) ...
To show systemd logs for the snapd.refresh.service unit, use: journalctl -u snapd.refresh.service
A backtrace shows a list of an applications active functions. As functions are nested within each other when they are called the application must record where it left one function to get into another within it. This is done on the stack, we then dump the stack for the backtrace. Preparation In order to prepare your system for doing one, you must first ...
I don't use gnome-shell so I'm sorta guessing but the following is true isn csh, bash and bash. Set the ulimit -c 5000. This will allow a core dump. The number set the maximum size of the dump. You might have to vary the number so that the command will work. If the gnome-shell window closes, the ulimit command MUST be re-entered. Ubuntu should really ...
Top 50 recent answers are included