Sorry, we don't support Google Chrome.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
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/2064118
Title:
Possible duplicate of LP:2062330.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because
I think the same fix[1] that was committed to address the related bug
will apply here. Quoting from there:
> Please re-test on snapd edge tomorrow
[1] https://github.com/snapcore/snapd/pull/13853
--
You received this bug notification because you are a member of Desktop
Packages, which is
Great! Just a question, does
> ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be
preloaded (failed to map segment from shared object): ignored.
still show when launching Chromium? I'm assuming the following "cannot
update snap namespace" line went away.
** Also affects: snapd
Hi, this looks strikingly similar to LP:2061981, but here you have a
standard /home layout.
Can you please do
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
and report back?
--
You received this bug notification because you are a
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
** Changed in: snapd (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks!
As a note for self, I diffed snapd 2.61.2 and 2.62 and found in
cmd/snap-update-ns/user.go:
--->
+func isPlausibleHome(path string) error {
+ if path == "" {
+ return fmt.Errorf("cannot allow empty path")
+ }
+ if path != filepath.Clean(path) {
+
omium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification becaus
Thank you for the additional information.
enaira05, you can disconnect them with
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
wouterd, glad to hear that solves your problem.
The interface has been present for a long time. The Chromium
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
What is 'snap connections chromium | grep personal-files'? If you
disconnect the dot-local-share ones, does Chromium start?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks, I'll look into the issue, for now you can use `snap revert
chromium` to use the previous version.
** This bug is no longer a duplicate of bug 1620771
when /home is somewhere else, snaps don't work
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
If there is more than one user available, both are highlighted in gray,
although only one is highlighted with a orange border.
Ubuntu 24.04, gdm 46.0-2ubuntu1.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "gdm3-user.jpg"
*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
** This bug has been marked a duplicate of bug 1620771
when /home is somewhere else, snaps don't work
--
You received this bug notification because you are a member of Desktop
Packages, which is
ing that
it has been pressed, and the program exits immediately.
- Observed: The reload button becomes dark for a brief moment, indicating that
it has been pressed, and the program starts updating the cache.
** Affects: software-properties (Ubuntu)
Importance: Low
Assignee: Nathan Teodo
Hi, thanks for opening a report.
> chrome started failing
> chromium launches fine
Ubuntu only maintains Chromium. Chrome is proprietary software provided
directly by Google so you need to file a report with them.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You
Public bug reported:
In Ubuntu Noble, I install authd 0.2.1, switch to a different TTY and
try to log in.
I enter my user name and I am asked
> Select your provider
>
> 1: local
I click and am asked for the password. After entering it I
expect to eventually get a shell, but after installing
This is unlikely to be a problem in Gnome Keyring, as SDDM has no
problem unlocking in on log-in. I'm therefore adding here GDM3.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** No longer
OK, I was also missing gstreamer1.0-packagekit.
Summary is:
For reproducing that exact error, have neither gstreamer1.0-libav nor
gstreamer-1.0-plugins-bad nor gstreamer-1.0-packagekit.
To fix the error, one needs both gstreamer1.0-packagekit and gnome-
software, then hitting "Find in Software"
If I install gnome-software and try again, I get a prompt:
> Unable to play the file
>
> MPEG-4 AAC decoder, H.264 (High Profile) decoder are required to play the
> file, but are not installed
With a button to "Find in Software". Clicking it does nothing though.
And even before clicking
Aha, had to remove gstreamer1.0-libav as well, then:
--->
** (totem:195768): WARNING **: 11:00:53.910: atk-bridge: GetRegisteredEvents
returned message with unknown signature
** Message: 11:00:53.953: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC
decoder|decoder-audio/mpeg, mpegversion=(int)4,
Cannot reproduce it here, but despite no gstreamer-bad the video plays
normally. Maybe I have another package that satisfies that, I'll
investigate further.
--->
% systemctl status packagekit.service
○ packagekit.service - PackageKit Daemon
Loaded: loaded
** Patch added: "chr.diff"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061075/+attachment/5764073/+files/chr.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
We will change the browsers' deb description so as to not invite a
removal. LP:2061075.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2060898
Title:
Trying to install
firefox is now replaced by the firefox snap.
So I suggest we change it.
** Affects: chromium-browser (Ubuntu)
Importance: Low
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
MikeV, can you describe more precisely what you mean with "not working"
in the duplicate bug report? How did you ascertain this? Were all or
only a handful of cookies still present after restarting Chromium?
Can you start Chromium in the command line with 'chromium --enable-
logging=stderr &>
** Patch added: "freerdp2.diff"
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/2060976/+attachment/5763791/+files/freerdp2.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
Public bug reported:
Ran successfully with autopkgtest -B . -- schroot noble-amd64.
** Affects: freerdp2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
** Patch removed: "freerdp3.diff"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2057842/+attachment/5759842/+files/freerdp3.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
Public bug reported:
Reproduction case:
Add the attached source file to /etc/apt/sources.list.d/. You don't need
to 'apt update' for this test.
Open software-properties-gtk.
Issue:
All the comments at the top of the file are displayed, flooding the
interface.
Limiting the number of comment
Corrado, the released fix was only for the consumer (gnome-initial-
setup).
I think that, if you chose to send system information to Canonical and
it failed, which is at the moment guaranteed to happen because the
service is not up yet, ubuntu-report schedules a new attempt to send the
report.
** Changed in: gnome-initial-setup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/2050884
Title:
Ubuntu Metrics server is
** Changed in: gnome-initial-setup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2049670
Title:
noble:
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2060094
Title:
Packaging: Provide
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
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/1719572
Title:
chromedriver can't click
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
** Changed in: rustc (Ubuntu)
Status: New => Incomplete
** Changed in: rustc (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Public bug reported:
https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble-
amd64.giflib_5.2.2-1_BUILDING.txt.gz
Upstream bug: https://sourceforge.net/p/giflib/bugs/170/
** Affects: giflib (Ubuntu)
Importance: Undecided
Status: Triaged
--
You received this bug
** Patch added: "giflib.diff"
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+attachment/5761636/+files/giflib.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
** Bug watch added: Debian Bug tracker #1068438
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438
** Also affects: giflib (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438
Importance: Unknown
Status: Unknown
--
You received this bug notification
This seems not to be an issue any more. Feel free to reset the status if
otherwise.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6:
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2017011
Title:
[snap] unable to read
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/2017011
Title:
[snap] unable to read
** Patch added: "chr.diff"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2060094/+attachment/5761408/+files/chr.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
Debian provides the Chromium browser in the chromium package; we, in
chromium-browser package.
A package that depends on 'chromium' was autosynced. So this provides
for it.
** Affects: chromium-browser (Ubuntu)
Importance: Low
Assignee: Nathan Teodosio (nteodosio
I'm changing the logging period from 10 minutes to 10 days, as in this
case it's better not to suppress the error entirely as the information
in those files might be used for something more substantial in the
future.
I pushed the changes to beta and edge, the latter of which is currently
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ch
*** This bug is a duplicate of bug 2017011 ***
https://bugs.launchpad.net/bugs/2017011
** Changed in: chromium-browser (Ubuntu)
Importance: Wishlist => Low
** Tags added: log-noise
** This bug has been marked a duplicate of bug 2017011
[snap] unable to read
ftware-properties (Ubuntu)
Importance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Description changed:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: in
The fix is in Snapd beta and should be in stable in the next month or
so.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
** Changed in: firefox (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a
https://salsa.debian.org/gnome-team/gnome-initial-
setup/-/merge_requests/23
** Changed in: gnome-initial-setup (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-initial-setup (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received th
Public bug reported:
Downstream Update-style-to-the-same-than-flutter-installer.patch[1] is
reverting a great deal of gis-apps-page.{c,ui} that are introduced by
(also downstream controlled) 0001-Add-Ubuntu-mode-with-special-
pages.patch[2].
I think that makes maintaining those patches more
Actually please hold that for a moment, I had forgotten to enable other
architectures in the PPA and a test is failing in Armhf.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
The following debdiff enables the build tests and runs them as
autopkgtests, which as per [1] run successfully.
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-nteodosio-
rebuilds/noble/amd64/f/freerdp3/20240326_213622_91f66@/log.gz
** Patch added: "freerdp3.diff"
Opened merge request for Snapd:
https://github.com/snapcore/snapd/pull/13757.
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6:
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notificatio
I reproduced that now.
Do you observe any problem or hindrance as a result of those denials?
I had a look at the source code and it seems that it doesn't actually
use that information for load balancing or anything of the sorts, but
actually only for informational purposes, namely for
Hi Gunter, thanks for the report. From what I understand Plasma 6 is not
(and will not be) available in Ubuntu 24.04, did you get it in by
building it from source or by using some PPA? I ask because it would be
nice to reproduce your observations before incorporating a fix.
Many thanks for
Hello, do you have a reproduction case? I don't get this when I launch
Chromium, does it try that when on heavy load?
--
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/2058881
> the issue is still present
Then I'm marking this as fixed and restricting its scope to just the
missing amdgpu.ids. The actual rendering issue is already tracked in
LP:2004532.
> with the below errors
Those are expected warnings, they don't relate to the reported issue.
> The following
s/software-properties/20240301_100314_9e242@/log.gz
** Affects: software-properties (Ubuntu)
Importance: Low
Assignee: Nathan Teodosio (nteodosio)
Status: In Progress
** Affects: software-properties (Ubuntu Xenial)
Importance: High
Assignee: Nathan Teodosio (nteodosio)
You raise very valid concerns.
However, at this point in time a maintainer of the snap can choose
either to not install the Cups snap and have half of its users
frustrated that printing does not work or to install the snap with no
questions asked and frustrate a tiny fraction of that number. So
The log still says
> Unable to reach the snap store
Can you please try again once you can reach it?
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
For Chromium users:
Can you verify if either of
snap remove chromium
snap install --beta chromium
or
snap remove chromium
snap install --channel internal-libdrm chromium
fixes the issue?
Note: A refresh will *not* work for the first case, it really needs to
be removed and installed
** Description changed:
+ Related: LP:2004532.
+
The chromium snap package has a bunch of graphical glitches that makes
the program unusable. This appears to be caused by the snap package
being unable to access the libdrm directory. Below is the output I get
when launching the program. I
I can reproduce the issue if I refresh instead of really reinstalling
the snap, so a bug in Snapd.
Please try
snap remove chromium
snap install --beta chromium
Does the amdgpu.ids error go away now?
If that still doesn't solve the graphical bugs and you have time, it
would also be very
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Confirmed
--
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/2004532
Title:
Hardware acceleration broken
> I still have the issue after switching to the beta version
123.0.6312.22
Hum... Do you still get the error about the missing file in stderr? Can
you confirm
snap run --shell chromium
ls -l /usr/share/libdrm
lists amdgpu.ids now?
I also built the snap with Libdrm provided by Chromium's
** Description changed:
- Possible, proposed solutions
-
-
- Option 1: Please install from these channels and report back with
- success or failure.
-
- snap refresh --channel candidate/core22 firefox
-
- Option 2:
-
- chromium --ozone-platform=wayland
-
It looks like this regressed in Chromium (probably when Chromium
switched to core22) judging by LP:2054887. The fix for the lack of
/usr/share/libdrm/amdgpu.ids is currently released on beta and will be
soon in other channels too.
** Changed in: chromium-browser (Ubuntu)
Status: Fix
Maybe it was perception error, because today I can confirm
/usr/share/libdrm/amdgpu.ids is present in the beta snap. Could you
please confirm the bug (or at least the error message) goes away by
switching to it?
sudo snap refresh --beta chromium
** Changed in: chromium-browser (Ubuntu)
Either the workaround[1] didn't work for Chromium or I managed to botch
my copy of it[2], for /usr/share/libdrm is still empty in the Chromium
beta snap.
[1]
https://git.launchpad.net/~mozilla-snaps/firefox-snap/+git/firefox-snap/commit/?id=00059b6a9aea8e4ce5a239bd9e649f60736dd947
[2]
And Firefox has a work around, which I'm copying to Chromium beta. Once
the fix is confirmed, will be released to other chnnaels.
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Te
This might be a bug in Snapd: LP:2055273.
--
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/2054887
Title:
Grahpical bugs caused by unable to access libdrm
Status in
Happy to hear that!
Would you mind confirming if the log from 3 no longer has references to
crashed GPU process? Because if it still does, then I know for future
debugging that that could be a red herring.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You
2. Thank you for the willingness to test that! Unfortunately, the snap
store makes snap branches expire after 30 days of their publication
(LP:2019554). So if you try installing that snap, you'll end with the
normal, stable snap. I just edited the comment there.
3. It has repeated instances of
Correction: Command in 3 should be 'chromium --enable-logging=stderr
--v=1 >chr.log 2>&1'.
--
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/2055040
Title:
Software rendering
Thanks for clarifying.
> If I launch Chromium with the --ozone-platform-hint=wayland or
--ozone-platform-hint=auto (as specified in the snap's starter script)
1. Just to confirm, this means that if you just launch the Chromium snap
normally, the described behavior happens? Because, as you
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
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/2055040
Title:
Software rendering under Wayland mode
What is 'snap info chromium|grep tracking'?
> When omitting the parameter or setting it to "X11", HW rendering gets
> correctly detected and activated.
How did you determine that, was it in about:gpu?
--
You received this bug notification because you are a member of Desktop
Packages, which
Looks like GPU indeed, can you confirm with --disable-gpu?
What is 'snap list|grep ^gnome' and 'snap connections chromium'?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2054941
Title:
Chromium does not print out, although printer is
Thanks for the report, glad to know it's not an issue any more. If it
comes back, feel free to open the bug again.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
For about one month my Google Calendar won't synchronize any more with
Google, despite I having my account set up. As such it won't alert me of
new events and will keep me alerting of deleted recurring events.
+
+ "Synchronize calendars" does nothing.
+
+ The log
Public bug reported:
For about one month my Google Calendar won't synchronize any more with
Google, despite I having my account set up. As such it won't alert me of
new events and will keep me alerting of deleted recurring events.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package:
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
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/2049625
Title:
CVE-2024-0519: Out of bounds
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
** Tags added: hwacc
** Tags removed: hwacc
** Tags added: kivu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Sure.
And in case you are interested, you can always test "after-build time"
changes such as this using snap try[1]. Chromium's launcher script would
be in bin/chromium.launcher.
[1] https://snapcraft.io/docs/snap-try
Am 07/02/2024 um 17:53 schrieb Kevin Keijzer:
> Sure, no problem.
>
>
Thanks for bringing that to our attention.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Committed
--
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/2052624
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Assigning critical importance as 121 reached stable.
** Summary changed:
- Newer rustc version needed in jammy to build chromium updates
+ rustc 1.71 version needed in jammy to build chromium updates for ARM
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
**
Just for completeness:
> I still do not understand why manually removing the -Z flags failed.
Actually that had failed on the 32-bit ARMv7. ARMv8 had failed because
of connection and I didn't care to trigger it again so I assumed it
would fail for the same reason.
Turns out that is not the
ARMv8 built alright with your proposed RUSTC_BOOTSTRAP strategy.
I still do not understand why manually removing the -Z flags failed.
Could it be that those undefined references were to unstable functions?
But that is just out of curiosity.
For the purposes of this report, please kindly
The build with the manual removal of the -Z flags failed[1] with
multiple undefined references such as
--->
obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function
< as core::fmt::Debug>::fmt: error: undefined reference to
> Normally, it is not. Rust compilers, even in the stable channel, include
> the complete logic of a nightly compiler. The logic is disabled by
> default during the runtime when the compiler is in the stable channel.
It is reassuring to learn that.
> I hope my explanation makes sense.
It
Thanks for that suggestion, looks like just what I needed.
I looked it up and found this:
> The build system sets RUSTC_BOOTSTRAP=1. This special variable means
to break the stability guarantees of rust: Allow using #![feature(...)]
with a compiler that's not nightly. This should never be
OK, feel free to reset the bug if the problem re-appears.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
The build failed[1] with
error: the option `Z` is only accepted on the nightly compiler
In the ideal world that nightly Rustc would be used, but given the
nature of deb packaging I suppose it is not doable.
Since I encountered the same error before and was able to overcome it by
manually
: (unassigned) => Nathan Teodosio (nteodosio)
--
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/2049493
Title:
Newer rustc version needed in jammy to build chromium updates
Sta
Thanks for the report, do you have a reproduction recipe?
--
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/2049236
Title:
Chromium queuing my application requests
Status in
1 - 100 of 715 matches
Mail list logo
