There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: libqrtr-glib (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you a
There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: opensc (Ubuntu)
Status: Incomplete => Invalid
** Changed in: pcsc-lite (Ubuntu)
Status: Incomplet
There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: flatpak (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
Thanks for the clarification Matthew and Heitor - first I'll re-set the state
of the devel release then.
As it isn't completely fixed there.
** Changed in: tracker-miners (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: tracker-miners (Ubuntu Lunar)
Status: Fix Released =>
This in your changelog is a Debian keyword
Closes: #2014954
To work on launchpad that needs to be
LP: #2014954
I hope that helps and gives you a few minor things to fix.
I feel too much out of my comfort zone to fully sponsor this anyway :-/
But I wondered about one more thing to ask you, giv
I can see why you do the purge forgetting the old state to enable them as if
they were freshly installed.
I'm not sure how SRUable that will be afterwards as it is affecting behavior if
someone has set something else than the default. But for now, going forward to
mantic I agree that it will hel
Some things just do not fit together.
You write
"... to update from default.target.wants to gnome-session.target.wants. ..."
But while 3.4.3-1ubuntu1 does:
+ [Install]
+-WantedBy=default.target
++WantedBy=gnome-session.target
Then later 3.4.3-1ubuntu2 does
+-[Install]
+-WantedBy=default.target
++#
This is now the third revision of the change (3.4.3-1ubuntu1 + 3.4.3-1ubuntu2 +
this) and by identifying that this also needs to go to -devel I wonder if you
should not also use the chance to submit the outstanding Delta to Debian. That
will help them directly and mid-term ease maintenance.
3.4.
Then the most recent applied patch says:
...
Since this is a helper service that is meant to be controlled by
"tracker-miner-fs", the install section shouldn't exist, as it allows
the service to enabled, meaning that its execution would be
controlled by systemd.
But I can't see where/how:
root@m:
If it would be an MP I'd set it to needs-information, but this is a debdiff in
a bug.
I hope my questions and confusion was clear so that you can iterate and clarify.
I'll remove ubuntu-sponsors which I'll ask you to add back once this is
ready for review again.
--
You received this bug notific
Nautilus Problem, möglich.
Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich.
Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider
keine weiterhelfen kann.
Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird
leider nichts mehr passieren.
P.S. Ic
Final state check:
- FFE was approved as well.
- MIR approved
- Per [2] it seems was consciously (freeze) accepted 15h ago.
- All dependencies are already in main (could have changed)
- Seen in component mismatches due to [2]
- The needed exclude needed is in place [1]
Only one version in noble
m
Thanks for the great debug work so far already, I think it is "apparmor
or kernel" enough that we should add those packages and subscribe a few
folks we know dealing with those details - I'd start with jjohansen as
he'd be the best to map us to either knowledge or a known case.
** Also affects: ap
Hey Ravi,
thanks for driving this!
We see progress on the meta packages \o/.
Furthermore I was able to process many but not all of the related removals.
Therefore it might be time to re-check, summarize and double down on the
few tasks that are left to make it in time for beta freeze?
--
You re
I see the same on Jammy, like the others it is reproducible easily by hitting
the meta key and exiting from there in any way (hit ESC, select anything to
start, ...).
Sadly setting fixed workspaces (10) did not work around the issues for me, like
it did for others.
Occasionally (seems to depend
FYI: Since the signature of bug 2035016 is quite similar I checked, but
I already have the mutter components on 45.0-2ubuntu1.
--
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/2000644
Considering it impossible to work with a system hanging every few hours
I debugged this over the weekend a few times, but sadly to no further
insight. Eventually I've given up and re-deployed Mantic on the system
trying to either "help by verifying the issue still exists" or "getting
out of it".
I
FYI Undocked with just the laptop screen it does not trigger the issue.
But docking the running system to initialize all additional screens
makes it trigger up again once I leave into the activities screen (as
described before).
--
You received this bug notification because you are a member of D
I can confirm the same, neither importing nor adding a VPN via the gui works.
You clock "add" after importing or configuring one, click add and then ... as
if nothing had happened.
I ran `gnome-control-center` directly and followed journal, no related
error message shows up.
It is not just visua
The seeding [1] of it is also quite clear on why it is still there.
"""
# This stack is no more very relevant, but was in the early days of internet
# dialin. This stack is a candidate for demotion, but OTOH received no
# bugs/CVEs over the last years and therefore can stay as-is for now.
# ppp it
Hi,
this was overlooked for too long but came up in bug 2046470 again which made me
see this for the first time.
I'd wish we'd have had that even a bit earlier e.g. to release it with
mantic and not half way through noble, but still now is the time to
still change the next LTS.
I needed to make
# Integration and maintenance
Despite some saying it is for the past only, it is regularly updated
and has multiple releases per year throughout all the time [4]. Those
updates flow well into Debian and Ubuntu - so it is not a classic "old
and outdated" case. And while not much changes in those up
# Referred Arguments
An argument that might not have been so strong more than a decade ago
but is much more today is power savings and that is an aspect that comes up
over and over.
It also had reports of conflicts with power saving [10] and e.g. dynamically
disabling/enabling cores which is much
# Actions by Others
Times have changes, as mentioned above the kernel learned many new tricks.
More new I/O hardware virtual or physical appeared that tries to be smart
and thereby sometimes conflict with what irqbalance does.
Some are mostly based on the links referred above, the Debian disucssi
# Summary
This discussion was seeminly easier to make the more dedicated to a singluar
use case you are - as then you have less "but what if" cases to consider.
That wide usage is great for Ubuntu but sometimes delays decisions.
List of reasons to remove it from the default dependencies:
- Seems
I subscribed a few people directly to get their input.
@Steve
I've subscribed you after trying to find, refer and summarize all of the past
to allow you and anyone else to read into this in one go. I think I'll need
your input as Architect and as participant of these discussions right from when
After all the history I was looking at where we are right now:
- irqbalance already is not in ubuntu-cloud-minimal images
- irqbalance is in normal cloud images and installed systems via the dep from
ubuntu-server
--
You received this bug notification because you are a member of Desktop
Packages
Libqmi (which is what pulls in libqrtr-glib) is ready except for this
component mismatch.
While qmi is in proposed adding the depend libqrtr is only in noble-
release atm
libqrtr-glib | 1.2.2-1ubuntu2 | noble/universe | source
libqmi | 1.32.4-2ubuntu1 | noble| source
libq
Hi Steve,
> I see a lot of strong opinions ... I would want any decision to remove
> irqbalance from the desktop to be based on evidence, not conjecture.
I agree that there is plenty of opinion (often backing up each other with cyclic
links) and not much data. Hence my compilation of the history
Hi Ethanay
> All I can find is a recommendation not to use it on CPUs with 2 or fewer
> cores as the overhead is said to be too high
This isn't a real problem anyway, the service will stop immediately if only
running on one core - even if running on multiple cores with the same
cache (as the inten
Hi Mike
> SUSE ... says that the first step to get there is to disable
irqbalance
I've read the same, IMHO that is just "if you want to manually tune, disable
it" which does not imply that it is bad to have it. But this is how I read
it, I have not talked to the authors to get their underlaying r
Hi Paride
> Back in the day I asked upstream their take on irqbalance usefulness with
> newer kernels, here is their reply:
> https://github.com/Irqbalance/irqbalance/issues/151
Thanks for this and the other extra pointers.
The Debian bug was referenced before, AFAIC it is mostly around
a) the ke
I want to try to avoid that this becomes too stale, so I wondered
what we can do from here. Two things came to my mind.
On one hand I will try to use some indirect relations to pull in some
HW manufacturer experts. They often have large performance teams tracking
things like that against different
Hi Dough
> If irqbalance is to be included by default, then there should be due
> diligence to demonstrate a clear benefit.
You are right that we should have that as well.
But this would be even more ture if this would be about "making it the default
when it was not before".
Right now (purely opi
Pings done, in a perfect world (if all reply) that would cover more than
we ever need, but then there is 0% guarantee they even have time or care
about this at the moment :-)
If anyone has connections as well, please ask them to participate too.
--
You received this bug notification because you
Hi Etanay,
I realize I maybe wrote too much :-/
So I start with a TL;DR:
AFAICS you are right in all you say, but I think there can not be "one right
answer" anyway. Hence I'm trying to leave all parties their freedom of defining
what is important to them and try to learn from them what impact i
Since the discussion is no more only covering Desktop I updated the
title (thanks Seb128 for suggesting)
** Summary changed:
- Consider removing irqbalance from default install on desktop images
+ Please consider no more having irqbalance enabled by default (per
image/use-case/TBD)
--
You rece
FYI, multiple parties and people promised me more input, but so far none
has arrived over the last weeks.
--
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/1833322
Title:
Please cons
It was nice to have LXD around and ready for many test/dev workloads,
and I feel it was worth it back then.
But we already replaced it with lxd-installer in minimal environments and it
was fine there too.
I never heard someone complaining that LXD takes a bit there, but every second
of boot time
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.
I was already leaning that way and thank you for adding the data.
I agree to not to pre
Hey Henry, thanks for chiming in and I agree in general that tech moved on.
Myself and others said similar before, thanks for adding more details and
voices - that is what such a discussion is about.
> they just don't go ping-ponging around between
In particular on this aspect, so much has happe
Interesting, that is more towards irqbalance than I heard so far.
thanks Fabio!
So we might end up needing to go like "Generally disabled except this
list of places [...] where it stays enabled".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
While there was sadly neither enough time not enough resources to do all
the deep dive analysis that could have been done, we succeeded by
reaching out to many more parties and got their input as well. Thank you
all!
Since Noble feature freeze is coming we need to make a call either way.
I propose
Steve was so kind reviewing and approving my proposal.
Doing that now is also helpful as it should make sure it still has quite some
exposure and thereby chances for people to report issues (vs if we'd land it
much later like after beta freeze).
Changes will:
- change the seeds in regard to irqb
FYI: Seed change landed
--
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/1833322
Title:
Please consider no more having irqbalance enabled by default (per
image/use-case/TBD)
Stat
FYI: updated ubuntu-meta, now in noble-proposed as version 1.532
--
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/1833322
Title:
Please consider no more having irqbalance enabled by
I've added a section to the release notes summing this up and linking
back here and to some of the past links.
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Agreed as pre-discussed.
Thanks for the paperwork here.
Removing packages from noble-proposed:
libmail-dkim-perl 1.20240124-1 in noble
libmail-dkim-perl 1.20240124-1 in noble amd64
libmail-dkim-perl 1.20240124-1 in noble arm64
libmail-dkim-pe
MIR Team approval to replace freerdp2 with freerdp3 in main.
Both stay in the archive, only one will be released with noble being in main.
This comes with the discussed requirement of giving this chance a try to add at
least some QA.
Right now tests are disabled at build and no autopkgtest is pre
** Changed in: cups-filters (Ubuntu)
Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/2003259
Title:
[MIR] libcupsf
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1647285
Title:
SSL trust not system-wide
Status in ca-certificates package in Ubuntu:
Conf
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
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/1967593
Title:
kernel modules goi
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2000739
Title:
Window actions (like maximize) no more work
** Changed in: pcsc-lite (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1892559
Title:
[MIR] ccid opensc pcsc-lite
Status in ccid package
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom ubuntu-22.04.
vijayam (Ubuntu)
Status: New => Fix Released
** Changed in: fonts-teluguvijayam (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-teluguvij
FYI: As mentioned int he MIR Team meeting, since doko had to run I've
sent a mail to vorlon asking if foundations is going to adopt it.
** Changed in: xxhash (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Desktop
xxhash was a code split from a package already in main and already promoted in
Disco/Eoan.
It came back now as dependency for rsync and (thanks Steve) Foundations is
subscribed to cover it.
Can be promoted to main in groovy
** Changed in: xxhash (Ubuntu)
Status: Incomplete => In Progress
There was a fix suggested on https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=975242 and I tried that. It works great.
I've let the Debian postgresql-maintainer know and there might be an NMU
that would then allow to make this package a sync again.
--
You received this bug notification because
Synced the fix after Christoph uploaded it
=> https://launchpad.net/ubuntu/+source/openjade/1.4devel1-22
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openjade in Ubuntu.
https://bugs.launchpad.net/bugs/1869734
Title:
openjade segfau
** Changed in: lua5.4 (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to opencc in Ubuntu.
https://bugs.launchpad.net/bugs/1909665
Title:
[MIR] ibus-libpinyin dependencies
Status in lua5.4
Public bug reported:
Hi,
due to this ML on devel-discuss [1] I realized that there is a new version that
should be merged for Ubuntu 21.04 - and probably later [2] be
considered/discussed for an SRU
That new version is in Debian now [3] and I think it would be great to get that
merged/synced.
@ddstret - any update how to proceed?
If you have no time yet, then the MPs to ignore the fail until we have a new
version are up - just ack them and I guess the SRU Team will follow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2
[15:17] ddstreet: any updates on 1892358?
[15:18] @paelzer sorry not yet, i'll have systemd ready for upload
next week including fixing the autopkgtests
[15:21] ok
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
htt
Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the
subtest "tests-in-lxd" would be related to some fstab issues in those issues.
But recently all architectures, but s390x recovered. I assume that the fstab
issue is fixed but something else surfaces now.
groovy
Thanks rbalint for pointing me to the other bug for the s390x fail we see now.
I'll continue there and consider the Groovy portion of this one closed again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.l
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
autopkgtest success rate dropped inhibiting prop
** Changed in: pcsc-lite (Ubuntu)
Assignee: Seth Arnold (seth-arnold) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1892559
Title:
[
Focal test hint was accepted tonight and things moved there.
@Kelsey - Steve denied the hint as a reset since recently a few results were
good.
Maybe you want to submit the same as force-badtest and bring it up like that
for X&B?
The results for xenial really look similarly bad ...
xenial
amd
The problem with Xenial is that there it isn't just flaky "systemd-
fsckd" much more seems to be broken. I'll revise my Bionic MP, but for
Xenial I'd like to hear from ddstreet/rbalint how they think we should
go on there ...
--
You received this bug notification because you are a member of Deskt
And on Bionic we only need to do so for amd64&i386.
Here is a new MP for Bionic:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793
** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable-
systemd-v2
--
You received this bug notification be
Sorry, I forgot to update one section for pcsc-lite on packaging:
- important open bugs (crashers, etc) in Debian or Ubuntu
There are quite some:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bugs?field.searchtext=crash&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_W
s (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: pcsc-lite (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
** Bug watch
Public bug reported:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just started app seems fine
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just sta
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just sta
Trying hard reset of my config via:
$ mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd
.metacity .config/dconf; do mv $f ~/.backup-gnome-config/; done
$ gnome-tweaks
# then reset to defaults
--
You received this bug notification because you are a member of Desktop
Pac
On backup I had:
mv: cannot stat '.gnome2': No such file or directory
mv: cannot stat '.gconfd': No such file or directory
mv: cannot stat '.metacity': No such file or directory
but worked for the rest
Also disabled all extensions (didn't have any active, but can't hurt)
Restarting into that now .
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just sta
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just sta
** Summary changed:
- Overlays do not refresh anymore and get the desktop stuck
+ GTK Overlays do not refresh/exit and get the desktop stuck
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just sta
Hi Daniel, I'm on it ... :-)
Video just completed - I already wrote that I'll attach one.
And I separated the "potentially related, but other issues" into an
extra section for exactly the reason of keeping this bug to one issue,
but at the same time I want/need to provide all info that might be
w
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412105/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
Now the description is complete in regard to all things worth to try that came
to my mind.
Also the apport data as well as the video is attached.
Setting back to new for re-review by the Desktop Team.
P.S. is the overlay an application on it's own that I could try to kill from a
console?
P.P.S
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412104/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412102/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412106/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412103/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bug
The video shows:
00:09 - opening the "Show Applications" overlay works fine at first.
00:14 - searching an application in there works
00:16 - I open gedit and would expect to get back onto the desktop.
But I can't it sticks within the overlay.
I tried to hit the "Escape" key, clicking on wi
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412107/+files/monitors.xml.txt
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search a
There were no extensions in:
'/home/paelzer/.local/share/gnome-shell/extensions': No such file or directory
I already disabled them via gnome-tweaks before, but doing so again the
ways you asked me to do that.
Getting back to the config showed a few of them enabled indeed, maybe that was
re-init
That was it, thanks Daniel!
Now I need to restore as much of my config as possible without breaking
it again ...
--
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/1896188
Title:
Act
Since so many components are involved a fix/change might have been missed.
And since I recently didn't hear anything about this otherwise rather hot bug I
was giving focal a try.
It turns out that this was indeed improved. Only the user of pkg:ifmail user
fdt name "Fidonet" is still visible. All
Hi Seth and Joy,
I see you cleared the list a lot - awesome!
You have subscribed and pinged the remaining ones which is a reasonable
approach as most might be no more real issues as of today.
I'm ok for the Ubuntu side of the pcsc-lite bugs now, what still needs
to be addressed is https://bugs.de
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also
affected I'm worried that I might just not hit the
Hi Gicaomo,
yeah every now and then I need to clean up most old builds to not get slapped
by the admins :-)
I have refreshed them:
small fix:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4187/+packages
big fix (more likely to help, but not really SRUable to Fical):
https://launch
Public bug reported:
The builds for riscv64 on e.g.
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1
hang eventually.
All other architectures work fine.
Build log tail will be like:
...
symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4
pkgstripfiles: Run
Great - thank you for that Giacaomo
Note to myself, for the sake of finding things more easily next time:
https://code.launchpad.net/~paelzer/ubuntu/+source/spice-vdagent/+git/spice-vdagent/+ref/lp1872527-clipboard-handling-small
https://code.launchpad.net/~paelzer/ubuntu/+source/spice-vdagent/+gi
It turned out that this has happened in the past and then resolved, so this is
a comeback.
For "dee" we can bump the timeout or skip the test on riscv64 for the immediate
problem
But the "dbus-test-runner timeout makes riscv64 builds" hang is a problem on
its own.
Therefore I added a bug task t
1 - 100 of 376 matches
Mail list logo
