I tried a lot of things:
- watching dconf and gsettings (display config not shown there)
- xarndr (can't control the display that is off)
- https://github.com/maxwellainatchi/gnome-randr-rust (can't set the device on)
Sadly the only thing I found so far to get back the display I disabled
was boot
Setting back to new so that the team can have a look if the new data
helps
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad
Two more details
First, on shutdown the splash screen (Ubuntu + Lenovo in my case) is visible
again on the display that was formerly off
And then a really stupid issue, I mentioned above I disabled the screen
in setting. Well it comes back up disabled, and it can still not enable
it due to "Chang
Ah BTW, 4 out of 4 times this happened so far it was the same screen out of the
5.
1 more screen is the very same model, and 2 more are the previous years gen of
the same model - so quite similar.
This gets suspicious as that seems more than by chance.
It is the bottom left in the setup of 5 scre
Just FYI, happened about two weeks ago and yet again today.
This time I tried to turn off the screen and on again (vis settings ->
display). But turning on again is blocked by the UI saying "Changes can not be
Applied" "This could be due to hardware limitations". Was worth a try for a
mitigation
Only the source and bin:native-architecture was requested.
Promoted these now that all is approved and agreed.
Let us see if that allows things to migrate and resolve without further
mismatches.
Override component to main
native-architecture 0.2.3 in plucky amd64: universe/devel/optional/100% ->
Public bug reported:
when I use my file manager i can't click on download that my file
manager closes then I can't access to my dowloaded file by clicking only
by the terminal
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: nautilus 1:45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-44.44-
Public bug reported:
Affects snap packages of brave and plex mostly.
In brave, when you open the app, everything looks fine, but the first tab you
load is mostly black, and if you move the cursor around, it will sometimes load
the image below where the cursor is, then go black again when you mo
(In reply to jhertel from comment #44)
> Is there any way to test it without touching the stable installation of
> LibreOffice?
As far as I know you can just install the dev Version alongside your normal
verison (https://dev-builds.libreoffice.org/daily/master/current.html).
Your stable release
Thank you to the people working on this.
I just gave it a try on the latest dev build but unfortunately for me it still
just selects the text. Not sure if I am missing an option somewhere.
Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: dfeefe2e97a5412a445a3a508acb2d9ae05138e
> Bug 2062951 is also likely to affect this machine, and may cause
relevant side effects here.
I've not seen the flickering, but thanks for the info.
> The most relevant log messages I can see are:
> Cursor update failed: drmModeAtomicCommit: Invalid argument
Ah, that explains why I see it "of
** Attachment added: "journal of the system until it happened the second time
(ends with hard power the next morning)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083479/+attachment/5824065/+files/report-frozen-screen-second-occurance.txt.gz
** Tags added: apport-collected nob
You asked for drm_info which I had to install first, so this is taken after the
last reboot.
This mostly looks like HW/SW inventory, I doubt but let me know if it is
helpful to re-run that next time it happens again.
** Attachment added: "drm_info after fresh boot"
https://bugs.launchpad.net
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824069/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824068/+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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824067/+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/2083479/+attachment/5824066/+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
** Attachment added: "journal of the system until it happened (ends with hard
power off shortly after the issue triggered)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083479/+attachment/5824064/+files/report-frozen-screen-first-occurance.txt.gz
--
You received this bug notif
Public bug reported:
Hi,
I considered it a one off, but it now happened a second time so I thought it
might be worth to report so you can match against anything else you might get
reported.
## Setup
- Ubuntu 24.04 with mostly defaults (I config a few things but e.g. do
not install a massive am
Fix submitted for AppArmor upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/1333
Until the fix arrives in Ubuntu, you can add the additional lines to
your /etc/apparmor.d/abstractions/mesa or (better) create a file
/etc/apparmor.d/abstractions/mesa.d/lp2081692 with the added lines.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 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
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 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
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 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 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
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
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
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
# 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
# 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
# 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
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
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
i can confirm tat LO is not really usable with a touchscreen at the
moment. laptops with touch screen seem to become more and more common
these days, i therefore think it would be great if LibreOffice would be
able to assign this a higher priority.
--
You received this bug notification because y
For anyone who's struggled to use the task switcher since 22.04 and
until this is finally fixed, a reasonably painless workaround is
available: https://askubuntu.com/a/1492396/145568
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-s
I managed to "solve" this problem by deleting the complete
~/.config/dconf/user file and reinstall every gnome extension i had
installed. Now i can start gnome on wayland, but also had to do again
every customisation i had. (Not sure if removing every extension was
necessary)
also see in: https://
Public bug reported:
Hello Ubuntu community,
I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then
(1 Week) I've had problems starting GNOME under Wayland. Here are the
details of my system and the steps already taken:
System information:
Device: MS Surface Pro 5 (Intel Iris P
Public bug reported:
Nautilus displays a big directory symbol alongside the message
"directory is empty" [or something to that effect] for empty
directories. However, it does not differentiate at all between
directories that are truly empty, and directories that contain only
hidden files and direc
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
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
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
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
For the record, I can confirm that the version of LO that ships with
22.04 is no longer affected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1846790
Title:
[upstream] Saving f
Found a solution.
There were two separate issues:
FIRST ISSUE
Apparently systemd likes to start up lightdm early, so early that on a
reasonably fast system the GPU driver won't be ready in time ...
(I thought this was what systemd's dependency handling was for, but
never mind.)
This seems to b
gpu-manager.service is probably a red herring, or a separate bug. I
(sometimes?) get "Error: can't access /sys/bus/pci/devices/:6e:00.0/driver
\ The device is not bound to any driver." when booting with gdm as well; yet
gpu-manager.service doesn't fail, and gdm comes up normally.
I
--
You
Public bug reported:
I have a bog-standard loginctl multiseat setup, using lightdm because of
#2033323. Except for the lack of session locking, it worked beautifully,
across multiple reboots. Until it didn't.
Box woke from suspend, and to be fair was acting strangely even then
(Steam suddenly tri
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_
Public bug reported:
When a second seat is set up via loginctl --attach, the greeter will not
come up on the second screen unless WaylandEnable=false is set in
/etc/gdm3/custom.conf (and gdm restarted).
For completeness' sake, the udev rules set up by loginctl are:
TAG=="seat", ENV{ID_FOR_SEAT}=
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
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:
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.
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 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
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 =>
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
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: libqrtr-glib (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you a
Thank you for your response Konrad.
I followed the docs for replacing pulseaudio with pipewire which worked well.
Now the bluetooth app offers more codecs to use.
I figured out "mSBC" offers the best quality.
Compared to A2DP it still sucks and sounds horrible.
You dont want to accept this if you
Hi,
now it's 2023 and I still have this problem.
Using Mint 21.1 and Teams for Linux.
When I switch to A2DP I cannot use the headset mic.
When I switch to HFP the sound in conversations is horrible.
Would appreciate a fix here.
--
You received this bug notification because you are a member of Des
** 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: 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
** 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: libcamera (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/1999300
Title:
crash in global constructor
Status in libc
** 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
** 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.
Public bug reported:
An application built with libcamera-dev crashes instantly on start in a
global constructor. This can be reproduced by the 'cam' example in
package libcamera-tools (run 'cam -l') or via this simple example;
#include
int main(int argc, char **argv) {
libcamera::CameraM
Public bug reported:
An application built with libcamera-dev crashes instantly on start in a
global constructor. This can be reproduced by the 'cam' example in
package libcamera-tools (run 'cam -l') or via this simple example;
#include
int main(int argc, char **argv) {
libcamera::CameraM
I managed to get audio output going using amixer:
amixer sset Master mute unmute 1- 1+
Both parts are necessary (mute/unmute and volume adjustment). Just
muting/unmuting or adjusting the volume does not bring back audio
output.
I can put it in my start script without adding any possibly insuffici
** 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
Thunderbird 102.4.2 is distributed:
https://packages.ubuntu.com/search?keywords=thunderbird
On Ubuntu 22.04, my update worked fine, tbSync works again.
Thank you very much to the developers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
@r-e-wolff Thank you!
I had a similar issue and could solve it by editing the apparmor profile.
The apparmor file for cupsd:_
/etc/aopparmor.d/usr.sbin.cupsd
The following line was added:
/run/systemd/notify rw,
--
You received this bug notification because you are a member of Desktop
Pack
@jdpipe The latest version of Thunderbird in the official repositories (for
22.04) seems still to be 102.2.2
Due to https://packages.ubuntu.com/search?keywords=thunderbird at the moment
only kinetic seems to have the 102.3.3 version.
--
You received this bug notification because you are a mem
I have the same problem - any ongoing solutions ?
You can override the problem with a second plugged mouse too, if you
move it only one pixel at after startup the mousepointer appears and
stay until shutdown.
Maybe the problem is to initialise the pointer when using wacom ?
The Wacom pointer is
Same behaviour on Ubuntu 22.04.1 LTS with nemo 5.2.4-1 ...
The files seem to be moved there if you delete a directory of yours with files
from other users in it from the trash.
Proposal for behaviour changes:
1. Not create and use the "expunged" folder at all and just fail to delete
other user
@Seb FYI
This [1] upload is in the NEW queue right now.
But it refers to the old UIFe, not this one here - so I'm not accepting it
right now in csae you want to fix this up.
[1]: https://launchpadlibrarian.net/625301973/ubuntu-
wallpapers_22.10.1-0ubuntu1_amd64.changes
--
You received this bug
I see this on Ubuntu 20.04.4 LTS with geoclue-2.0/focal,now
2.5.6-0ubuntu1:
$ loginctl session-status c4
c4 - spiele (1002)
Since: Tue 2022-08-02 19:58:47 CEST; 11h ago
Leader: 3710
Seat: seat0; vc7
Display: :0
Service: lightdm; type x11; class us
1 - 100 of 1429 matches
Mail list logo
