Public bug reported:
when trying to install chromium in 20.04 in a lxc container to fails to install
with the following:
root@python:~# apt-get install chromium-browser
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
I do not think this is the same problem.
1532508 is supsend issue.
This does not require supsend.
Just do nothing for the amount of time it takes to cause the screen to lock
because of being idle.
then
The pinning is holding me back for moving from current version to 20.04.
So far the only option I see is to use the beta you pointed me to or switch
to google-chrome which looks like there still create debs.
Not being able to pin things and not being able to choose when the snap upgrade
is a
that fixes the --no-sandbox but still needs the
QT_X11_NO_MITSHM=1
also the --no-xshm works now.
This whole bug report shows my big problem with snaps.
In production I have a pin a version of chromium that works so that I can use
webdriver to access a number of site that I need to submit data
it need the no-sandbox to work.
On 6/11/20 10:57 AM, Olivier Tilloy wrote:
> Thanks for the upstream report Mike. I see it has been marked as a
> duplicate of
> https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and
> comment #19 there suggests the following:
>
> tldr; manually turn
I have reported the bug.
Here is the url.
https://bugs.chromium.org/p/chromium/issues/detail?id=1085136
On 5/20/20 8:24 AM, Olivier Tilloy wrote:
> Indeed, it appears to be the same problem. I think an actual bug report
> (as opposed to a support thread) would be useful if we want upstream
>
It look like
https://support.google.com/chrome/thread/41722791?hl=en
On 5/19/20 8:48 AM, Olivier Tilloy wrote:
> Ack, thanks Mike. In light of this information, I have removed the
> duplicate status.
>
> Is there an upstream bug report for the crash? If not, would you mind
> filing one at
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
Sorry about last comment. (ignore last comment)
The workaround in bug 18752 fixes the blank screen. (This is also my bug report)
export QT_X11_NO_MITSHM=1
export _X11_NO_MITSHM=1
export _MITSHM=0
This
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
Can no long test this bug as chromium has moved on to 81.0.4044.132 and
now has a different set of problems.
Thing crash on on gpu problems.
Look at Bug 1877173.
On 5/15/20 7:58 AM, Olivier Tilloy wrote:
*** This bug is a duplicate of bug 1857252 ***
https://bugs.launchpad.net/bugs/1857252
This is not the same problem.
The --use-gl=swiftshader work for chrome before 81.0.4044.138. Without the
--use-gl option it only had a blank (gray) screen but did not crash.
On 81.0.4044.138 it crashes
That did work for both 18.04 and 16.04
Any idea what i lose by not having the sandbox ?
On 5/7/20 4:38 AM, Sebastien Bacher wrote:
> Seems similar to https://support.google.com/chrome/thread/41722791?hl=en
> , does it work if you use --no-sandbox ?
>
--
You received this bug notification
Public bug reported:
Chromium crash on a ssh x forwarding connection
It crashes on both 18.04 and 16.04 with the same message.
The X forwarding is working for other programs just fine.
It was working until last update.
Here is the message from the console on the crash
1 hit the 3 dots in upper conner
2 Hit the Privcay and Security
3 hit authorities tab
4 hit the import button
Then I get:
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
I just try the import now and it worked.
I assume the problem was fixed
Public bug reported:
When I try to add Server Cert to chromium-browser I get the following message
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
This worked on 18.04 but not 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package:
Public bug reported:
Using any vnc viewer it takes 30 seconds before the display comes up. I have
tried with remmina and
vinagre as the viewer.
The only thing in syslog is the following:
Dec 22 15:18:58 mike-desktop dbus-daemon[10399]: [session uid=0 pid=10397]
Activating service
Public bug reported:
Chromium 78 worked and things broke in version 79.
With chromium 79 when using the remote display (ssh for x forward) I get
the display forward but only a blank (white) window. Chromiumn does not
render anything into the window.
If I am at the console then every thing work
Public bug reported:
In both the subject line and list of emails when there is a graphic displayed
it is too large
and in the case of panel with the list of emails it cover a a number of email
before and after
the email with the problem.
This problem start just after upgraded from 16.04 to
The problem still exists
I needed to patch saned.c:
I needed to change SANE_TRUE to SANE_FALSE
at line 1830:
reply.status =
sane_get_devices ((const SANE_Device ***) _list,
SANE_FALSE);
** Attachment added: "Here is the patch I need to get saned
Public bug reported:
When running scanimage -L on a remove system no scanner are found.
when running scanimage -L on local system (where saned is run) finds the
scanners.
when running scaned in deubg mode I can see the remote system request a list of
scanner
but no list is returned to scanimge
Why is this marked Incomplete ?
Is there anything you need from me ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1261255
Title:
[ThinkPad T530, Realtek ALC269VC, Speaker,
send email to the author if sound not working on your T530
who is should I be sending a email to about the sound not working ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
The sound did work for a while on 13.10.
It stop working after a reboot and have not had sound comming from the
speakers. I hear a poping nose comming from
the right speaker and can mute the poping nose only by pressing the speak mute
button on the laptop.
I have looked
This T530 only has 2 speakers that I known about.
I do not have the dock for the t530.
Are you asking me to rebuild the sound driver ?
Is there something I can try and see if that is the problem without
having to rebuild stuff ?
I do not have kernel bugtrack account to look at the first url.
23 matches
Mail list logo
