It's built now, please have a look if it fixes the issue now.
--
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/2038727
Title:
Chromium snap theme parsing error
Status in chrom
*** This bug is a duplicate of bug 1967632 ***
https://bugs.launchpad.net/bugs/1967632
Hi Pascal, not sure you receive notifications for the duplicate, but in
LP:1967632 I have released a tentative fix with a test case.
--
You received this bug notification because you are a member of Deskto
Public bug reported:
Duplicity 1.2.2-1 did not build from source due to new setuptools, thus
1.2.2-1ubuntu1 was uploaded.
1.2.2-2 no longer has that problem and closes the corresponding bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052878, so we can
synchronize with Debian now.
I attach
Public bug reported:
Builds successfully in Mantic.
** Affects: network-manager-applet (Ubuntu)
Importance: Wishlist
Status: Confirmed
** Patch added: "nma.diff"
https://bugs.launchpad.net/bugs/2039460/+attachment/5709932/+files/nma.diff
--
You received this bug notification b
Great! Thanks for testing. This will slowly flow into other channels.
--
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/2038727
Title:
Chromium snap theme parsing error
Status
I'm proposing changing the version number from 1:85.0.4183.83-0ubuntu3
to 2:1+snap, similar to what Firefox does.
** Description changed:
For Ubuntu >= Focal the transitional debs are frozen at the version
number 1:85...
- This might make one think[1] that it will install a critically outd
Hi Lukas, thanks for having a look!
> But I wonder if we should rather change the version number to
> "2:1snap1-0ubuntu1", in order to use a similar format as we have on
> Firefox (LP: #1892724)? What do you think?
So, my hunch reaction to that scheme is "god, are all those numbers
really meanin
> I don't see how this debate is apropos. Whether or not the passwords
are stored in the clear, or obscured with symmetric encryption using
hard coded parameters in chrome is irrelevant. Both of these scenarios
are entirely unacceptable.
You are right, but if a statement presented as a certainty a
Thanks for the report.
Cannot reproduce. The bookmark manager is chrome://bookmarks/, right?
Anyway, this would be most likely a ticket for upstream to tackle,
crbug.com.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
> Was able to reboot with strg+alt+F(x) sudo reboot
Once this happens again, can you please collect dmesg and journalctl
(some hundreds of lines are probably enough) before rebooting?
Instead of launching Chromium normally, use
chromium --enable-logging=stderr > chromium.log 2>&1
Also:
sna
Another possible hint to collect: Does this happen both in X11 and
Wayland?
--
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/2039701
Title:
chromium freezes gnome if hardware a
Parallel install is OK, I committed the fix for that weeks ago... In the
wrong branch. (:
Rebuilt now, with my limited connection I cannot donwload it to test it,
but I tested by making local changes by unsquashing and trying the snap.
Can you please give it another try and let me know? The revis
Hi Lucas, thanks for having a look.
> Just to understand a bit better, is this bug affecting just Jammy? Any
> other Ubuntu series? Please target the correct series in the bug.
No, it goes all the way to Focal. The mention to Jammy was because in
the upstream pull request the first version of
Can you ascertain if your smart card is supported by OpenSC?
--
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/1967632
Title:
[snap] apparmor denied when trying to load pkcs11 m
OK, hang on, the title claims that Gnome crashes if hardware
acceleration is activated. You are now reporting problems also with it
deactivated, right?
> If its turned off then it is ok. But it crashed anyway when the
indicator applet was showing incoming mail last time.
With hardware acceleratio
** Patch removed: "xdg-deskop-portal-gtk2.diff"
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+attachment/5709117/+files/xdg-deskop-portal-gtk2.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-d
I see the bug is addressed, but for what it's worth, one more data
point.
I just run into the issue today when doing
apt remove fonts-ubuntu*
What I didn't notice was that a replacement instead of a removal was
carried out
fonts-ubuntu (0.83-6ubuntu1 => 0.869-0ubuntu1)
After a while I turn
Workaround:
apt install fonts-ubuntu- fonts-ubuntu-classic
--
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/2019045
Title:
[snap] New Ubuntu font with normal weight displaye
The new font relies on some different mechanism to determine the style
of a given typeface, as each different style points to a same file. The
old font doesn't do that. Maybe that could be tripping the resolution.
--->
# ubuntu-fonts
lrwxrwxrwx 1 root root 20 jun 21 10:35 UbuntuMono-B.ttf ->
'
Bold renders fine given simple CSS:
Ubuntu.
Ubuntu bold.
This looks specific to Google Docs.
** Attachment added: "fonts.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5712423/+files/fonts.png
--
You received this bug notification because you
More information dump:
* It's easier to see the error Andreas mentioned with --enable-
logging=stderr:
--->
[246126:246235:1023/123348.818876:WARNING:obfuscated_file_util.cc(1323)] Failed
to get origin+type directory: { uri:
filesystem:https://docs.google.com/persistent/docs/fonts/4iCv6KVjbNBYl
Thanks for the report. Do you recognize your issue in LP:2007652?
If you right click and add to favorites, does the icon show on the dock?
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, w
For some reason some binaries are no longer making it into the snap. :|
I'm investigating...
--
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/1967632
Title:
[snap] apparmor den
*** This bug is a duplicate of bug 2007652 ***
https://bugs.launchpad.net/bugs/2007652
Yeah sorry about that, this is actually the way Gnome Shell interprets
sandboxed applications — other desktop environments have the desired
behavior.
** This bug has been marked a duplicate of bug 2007652
** Bug watch added: Mozilla Bugzilla #1849961
https://bugzilla.mozilla.org/show_bug.cgi?id=1849961
** Also affects: chromium-browser via
https://bugzilla.mozilla.org/show_bug.cgi?id=1849961
Importance: Unknown
Status: Unknown
** No longer affects: chromium-browser
** Also affects
** Attachment added: "Screenshot from 2023-10-31
10-47-43.png"
https://bugs.launchpad.net/bugs/2042077/+attachment/5714608/+files/Screenshot%20from%202023-10-31%0A%2010-47-43.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-
Public bug reported:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-editor,calculator,calendar},
which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-gen
ADW_COLOR_SCHEME_FORCE_DARK=. fixes it but only in a Gnome environment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2042077
Title:
Dark mode only works for some GTK windows
St
Thanks for having a look, Bryce.
I addressed your points; the build is [2].
Should I always propose the debdiff with the release name instead of
UNRELEASED even though it is unreleased at that given point? I'm used
not to, but maybe that's something particular of Gnome[1].
[1] https://wiki.deb
Thanks for your input Gunnar, that might be really playing a role in the
problem.
After all, it turns out the error Andreas reported is also present when
the behavior is correct, i.e. with ubuntu-fonts-classic I get
--->
Failed to get origin+type directory: { uri:
filesystem:https://docs.google.
No problem, Simon, thank you for responding and sponsoring!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2039460
Title:
Please merge network-manager-applet 1.34.0-1 f
> the same error.
Which one? If the one in DpkgHistoryLog.txt, it really looks like a
store/snapd bug, maybe follow up in the forum. Found this:
https://forum.snapcraft.io/t/cannot-performe-any-task-using-snap.
--
You received this bug notification because you are a member of Desktop
Packages, w
> the same error.
Which one? If the one in DpkgHistoryLog.txt, it really looks like a
store/snapd bug, maybe follow up in the forum. Found this:
https://forum.snapcraft.io/t/cannot-performe-any-task-using-snap.
--
You received this bug notification because you are a member of Desktop
Packages, w
New builds next week will have the hardware-observe slot; once it is
confirmed to fix the issue, I'll request automatic connection. Thanks!
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
The test snap does have the components I expected to be sufficient. I
don't know the reason of failure and haven't got the time to investigate
it in the short term, sorry.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because
The snap in edge channel already has the interface. Let me know if you
tried it and it fixed the issue.
--
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/1884759
Title:
[snap] U
Thanks for the background, let's use 2:1snap1-0ubuntu1 then.
** Patch added: "chromium.diff"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+attachment/5718905/+files/chromium.diff
--
You received this bug notification because you are a member of Desktop
Packages, wh
*** This bug is a duplicate of bug 2007652 ***
https://bugs.launchpad.net/bugs/2007652
** This bug has been marked a duplicate of bug 2007652
[snap] PWA don't launch as applications, just another chromium window
--
You received this bug notification because you are a member of Desktop
Pac
Thanks, Alex! Requested at https://forum.snapcraft.io/t/chromium-
hardware-observe-auto-connect-request.
--
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/1884759
Title:
[snap]
** 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/2038727
Title:
Chromium snap theme parsin
nassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu Jammy)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu Focal)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notifi
** 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/1884759
Title:
[snap] U2f yubikey not rec
** Also affects: chromium-browser (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu Lunar)
Importance: Undecided => Low
** Changed in: chromium-browser (Ubuntu Lunar)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Patch
Hi Athos, thanks for having a look.
> Would you mind filing the SRU paperwork as per the template at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?
I think I have already done that. It is admittedly very short but so is
the proposed change. Should I extend any section?
> Cou
That scheme already made its way into Noble. Will we then [1] submit a
new package with that native package scheme for Noble, [2] do the native
package scheme only for the SRUs or [3] do the SRUs with the non-native
scheme for consistency?
--
You received this bug notification because you are a m
Gnome Shell is supposed the last window state, either maximized or not,
and opens it accordingly. At least that is what I see when I
1. Open Chromium.
2. Make it {maximized, not maximized}.
3. Close it.
4. Open Chromium.
5. Verify that it is {maximized, not maximized}.
It also respects --start-m
What is 'type -a chromium' and 'lsb_release -a'? Do you use Gnome Shell
extensions? If you try some other window manager (e.g. icewm), does the
problem persist?
Am 05/12/2023 um 01:54 schrieb Mickael Reis:
> After I read your message, I tried to remove and purge chromium snap package
> and inst
** Changed in: gnome-control-center (Ubuntu)
Status: Expired => Confirmed
** Description changed:
I recently upgraded to Ubuntu 23.10.
- When I open settings (gnome-control-center) and click on a certain menu, it
creates about 8 transparent windows with the title 'OpenGL Randerer'.
+ Wh
Reproduced in Ubuntu 24.04.
Only thing in stderr is
--->
Gtk[47738]:CRITICAL: Unable to register the application:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected
from message bus without replying
<---
Graphics:
--->
$ lspci -k|egrep '3D|VGA' -A3
00:02.0 VGA comp
** Changed in: chromium-browser (Ubuntu Focal)
Status: In Progress => Incomplete
** Changed in: chromium-browser (Ubuntu Jammy)
Status: In Progress => Incomplete
** Changed in: chromium-browser (Ubuntu Lunar)
Status: In Progress => Incomplete
--
You received this bug notifi
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 ch
: (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
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 remov
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.
https://bugs.launchpad.net/bu
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 used
> 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 does
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
<&T as core::fmt::Debug>::fmt: error: undefined reference t
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 continu
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 case:
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
** Change
** 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.
https://bugs.l
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
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.
>
> Could
** 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.
https://bu
** 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 m
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: gnome-calend
** 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 wi
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
** 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
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.
https://bugs.launchpad.net/bugs/20548
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 is
** 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
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 pointed
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 un
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
--
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 receiv
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 chromium-b
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) => Nath
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]
https://gi
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)
S
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 Release
** 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
- MOZ_
> 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 sou
** 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 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
** 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
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 ba
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 chromium-browser
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 as
ial/amd64/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 (nteodo
> 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 comman
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
Ti
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 raising
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 assemblin
** 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
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: AppA
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"
https://bugs.la
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
T
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 compl
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
301 - 400 of 833 matches
Mail list logo
