Thanks! Chromium is working fine, so no need to track this any further.
--César
On Wed, Apr 17, 2024 at 12:15 AM Nathan Teodosio <2061...@bugs.launchpad.net>
wrote:
> Hi, thanks for opening a report.
>
> > chrome started failing
>
> > chromium launches fine
>
> Ubuntu only maintains Chromium.
Running ubuntu-bug managed to open a Chrome window! (The one I am
typing from.) I will keep it alive as long as possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061936
Title:
Chrome starts
Public bug reported:
This started today. The chrome snap was automatically updated (updates
to chrome have been arriving fast). After the update, chrome started
failing:
* Clocking on the launcher succeeds, but nothing pops up to the screen.
The UI freezes (can't even updated htop on a term).
*
Getting this while building emacs/master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795901
Title:
libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h
To manage notifications about this bug go to:
I see similar symptoms running under VirtualBox 4.3.12r93733, on two
different laptops.
1. Minimizing firefox freezes the screen.
2. Exiting from gnome-terminal sometimes leaves the window mapped. Starting
another terminal makes the first window go away.
One of the laptops says this:
$ uname -
Just a heads up: The bug seems to be back in Saucy (32-bit install
running on a VirtualBox).
gcc at 4.8, clang at 3.3, same symptom. /usr/bin/cc->clang
/usr/bin/c++->clang++
To repeat, compile anything that includes . Then
fails to be found again.
The bits/c++config.h file is at /usr/includ
Public bug reported:
During upgrade via "do-release-upgrade -d", see
http://askubuntu.com/questions/203301/how-to-safely-upgrade-from-an-
older-ubuntu-version-to-a-newer-one, look for "Securely Upgrade 13.04 to
13.10 Using Command Prompt".
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package:
Public bug reported:
This is when upgrading 13.04 to 13.10 according to
http://askubuntu.com/questions/203301/how-to-safely-upgrade-from-an-
older-ubuntu-version-to-a-newer-one
See section "Securely Upgrade 13.04 to 13.10 Using Command Prompt"
ProblemType: Package
DistroRelease: Ubuntu 13.10
Pa
