Package: bugs.debian.org
Severity: normal

Dear Maintainer,

-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

   * What led up to the situation?
   This is a fresh Debian 10 install
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   I tried doing `firefox-esr >> firefox.out 2>&1` but the file comes back 
empty everytime. I also uninstalled firefox-esr and just tried launching the 
Debian Sensible Browser but it also mostly locks up the GUI
   * What outcome did you expect instead?
   Some useful out put to help me fix this issue or help me reporting a bug

When I launch either firefox-esr (with or without -safe-mode) or the
Debian Sensible Browser (what Xfce chooses for me once Firefox is
uninstalled) the GUI "mostly" locks up. For example the clock in my
upper right corner of the screen stops. But if I click on it it'll
update itself but still not work. Also the browser window (either one)
will show weird tearing and artifacts. It's very hard to describe this
but I can take screen caps or maybe even a video if this helps. Once
this is done the GUI stays like this even if I close the offending
browser. The only way to return the GUI to a working state is either
`systemctl reboot` or `systemctl isolate multi-user.target; systemctl
isolate graphical.target`. I tried scrolling through the Xorg logs in
/var/log but didn't see anything I thought looked like an error or
failure. I know this is hardly enough information to help but I'm at a
loss on how to troubleshoot this further. I normally use Slackware but
I have installed Debian 10 before; just recently I installed it on a
desktop without any issues so I'm not sure what went wrong here

Reply via email to