Note that the issue is that the file is not highlighted. It always
opened the correct directory.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887195
Title:
[snap] "Show
I still see the same issue on the latest chromium snap on 20.04 with
unity. Is this dependent on the desktop environment?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887195
I tried the kde neon live cd yesterday, and it worked as expected there.
Could it be a nautilus issue since it seems to work fine with dolphin ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
web.whatsapp.com rejects the chromium snap browser, possibly based on
the user agent string. My current user agent is "Mozilla/5.0 (X11; Linux
x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap
Chromium/83.0.4103.116 Chrome/83.0.4103.116 Safari/537.36". There used
to be
Public bug reported:
In the chromium snap (Version 83.0.4103.116 on focal at the moment),
after downloading files, navigating to the downloaded file doesn't work.
Clicking on "Show in folder" only opens nautilus, but doesn't actually
highlight the file. This works as expected on chrome and older
After spending some more time with this, I can confirm that this is
definitely a regression. Both nouveau and the old bbswitch based method
in 16.04 were able to power off the nvidia card successfully when not in
use. The current implementation of prime-select in 18.04 doesn't do
that. It may be
@Alberto, with prime-select intel as well as with bbswitch off, powertop
shows the nvidia tunable as "good". Still, the battery's discharge rate
on idle remains pretty high (around 20W) on prime-select intel. With
bbswitch off, it drops to 13W or thereabouts. Do you need any more
information ?
--
Attached powertop images. I'm not sure how accurate powertop's values
and distributions are. With prime-select intel, the total estimated
power remains high although it doesn't attribute it to nvidia. bbswitch
also stays on. I've also attached a bbswitch off capture after prime-
select intel. That
Thinkpad w530. Still looks like the nvidia gpu isn't turning off.
bionic+lightdm+unity7. Log attached.
prime-select query
intel
cat /proc/acpi/bbswitch
:01:00.0 ON
** Attachment added: "gpu-manager.log"
Yes, this is working fine right now. For the past two releases, it would
break whenever the chrome version was newer than chromium.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This is again broken with chromium 66 on 16.04. chrome is on v67 though.
Some discussion about this:
https://forums.gentoo.org/viewtopic-p-8217026.html?sid=b64f0e093db635a0dd3ceafcae15c57b
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Chrome has set the global policy for flash to "ask first" for a while.
Yet, chromium will always play flash content without user consent if the
adobe-flashplugin package is installed on the system.
Test: Visit http://get.adobe.com/flashplayer/about/ on chrome and
chromium.
Relevant issue for a potential fix: https://github.com/saiarcot895
/chromium-ubuntu-build/issues/18
** Bug watch added: github.com/saiarcot895/chromium-ubuntu-build/issues #18
https://github.com/saiarcot895/chromium-ubuntu-build/issues/18
--
You received this bug notification because you are
Thank you. I've been testing the ppa version, and it works fine. The two
noticeable issues are that chromecast doesn't work anymore (known
upstream issue I guess), and flash's behaviour isn't the same as chrome.
--
You received this bug notification because you are a member of Desktop
Packages,
It looks like chromium 57 has been pushed to the ppa. I tried it on
trusty, and it works. I noticed one difference compared to chrome 57.
Flash has been deprecated in chrome 57, and set to on-demand only.
Ironically, chromium runs flash by default. The on-demand setting
doesn't exist on chromium
Public bug reported:
As of Feb 13 2017, the chromium version on trusty is 53.x which is at
least a couple of versions behind chrome-stable. Gmail displays this
message, "This version of Chrome is no longer supported. Please upgrade
to asupported browser." Core functionality in gmail works fine,
I got it to work following the steps stated above. However, the screen
tears in this chromium build. It doesn't on chrome. I have an nvidia
card. So that might have something to do with it too, although I haven't
seen tearing issues on this machine in a long time.
--
You received this bug
It turns out that the ppa linked above has problems with hardware
acceleration. Hence the tearing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1371274
Title:
Unable to
18 matches
Mail list logo
