to apologize on our slowness, lots of things happened towards EOY 2023
and everyone got very busy, and this was delayed and overlooked, so my
apologies to the Release Team and the Technical Board.
Thomas Ward
LP: ~teward
Lubuntu Team Lead
Secondary Lubuntu Release Manager
Lubuntu Council Member
I can affirm with regards to Lubuntu that we are participating in 24.04 LTS,
with a support period of 3 years as typical for Lubuntu.
We are working on getting everything necessary for the Technical Board
recertification and will send that soon as well.
Thomas Ward
Lubuntu Team Lead
Lubuntu
(https://github.com/Cacti/cacti/issues/5523#issuecomment-1768240843) on the
Cacti GitHub repository that they meant this was fixed in 1.2.6 but not present
in 1.2.25 which was released since then.
Thomas
-Original Message-
From: Ubuntu-devel-discuss On
Behalf Of Alex Murray
Sent: Monday,
Same with Mantic.
On 10/30/23 15:09, Thomas Ward wrote:
The only thing in Lunar's backports are the `cockpit` package, I
forget did we give that an exception?
Thomas
On 10/30/23 10:58, Thomas Ward wrote:
I'll take a look at Lunar (didn't that just release though...?) as I
have a server
The only thing in Lunar's backports are the `cockpit` package, I forget
did we give that an exception?
Thomas
On 10/30/23 10:58, Thomas Ward wrote:
I'll take a look at Lunar (didn't that just release though...?) as I have a
server related task for that to work on.
Thomas
-Original
I'll take a look at Lunar (didn't that just release though...?) as I have a
server related task for that to work on.
Thomas
-Original Message-
From: ubuntu-backports On Behalf Of
Dan Streetman
Sent: Monday, October 30, 2023 10:55 AM
To: Backports Discussion
Subject: allowing
UTC (due to the DST change).
On Wed, Oct 25, 2023 at 9:35 AM Thomas Ward wrote:
>
> agreee +1 on skipping
>
>
>
> Sent from my Galaxy
>
>
>
> Original message
> From: Mattia Rizzolo
> Date: 10/25/23 09:15 (GMT-05:00)
> To: ubuntu-backpo
agreee +1 on skipping
Sent from my Galaxy
Original message
From: Mattia Rizzolo
Date: 10/25/23 09:15 (GMT-05:00)
To: ubuntu-backports@lists.ubuntu.com
Subject: today's meeting
Today we are scheduled to have a meeting in less than 2 hours from now.
I don't have any update
ntact field" in that case.
Thomas
On 10/18/23 15:57, Laurent Lyaudet wrote:
Hello :),
I found this list while searching contact information for this package:
https://packages.ubuntu.com/lunar/python3-uinput
Search Ubuntu MOTU Developers on the web page.
I think there must be a g
ntact field" in that case.
Thomas
On 10/18/23 15:57, Laurent Lyaudet wrote:
Hello :),
I found this list while searching contact information for this package:
https://packages.ubuntu.com/lunar/python3-uinput
Search Ubuntu MOTU Developers on the web page.
I think there must be a g
This has been accepted and is now in the queue pending publication.
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
I give this a provisional ACK but want to check with mapreri or ddstreet
first for a second ack before handling.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2030259
Title:
[BPO]
bonjour :-)
comment augmenter la taille d'un disque virtuel dans VirtualBox ?
dans l'utilitaire "disques" je vois bien la nouvelle taille, mais pas
dans "fichiers", et donc elle n'est pas rendue disponible pour qu'on
puisse s'en servir.
--
RAPID maintainer
Le 22/08/2023 à 16:13, Dhenain Yves a écrit :
Bonjour
Le 22/08/2023 à 16:00, Thomas De Contes a écrit :
j'ai ajouté des clés avec IdentityFile.
quand ssh a besoin de ces clés, il affiche :
Enter passphrase for key '...':
C'est par ce que la clef à été générée avec une passphrase je suppose
bonjour :-)
comment trouver à quel endroit on doit faire les remarques et demandes
d’amélioration pour des logiciels spécifiques, pour gedit par exemple ?
--
RAPID maintainer
http://savannah.nongnu.org/projects/rapid/
--
Liste de diffusion ubuntu-fr ubuntu-fr@lists.ubuntu.com
Pour
bonjour :-)
j'ai ajouté des clés avec IdentityFile.
quand ssh a besoin de ces clés, il affiche :
Enter passphrase for key '...':
dans le terminal, au lieu de faire une invite dans l'interface graphique.
Du coup, ça n'est pris en charge par aucun mécanisme de gestion de mdp ! :-(
pourquoi
Changing the package to include two *external* sources is not proper,
because you will have packaging conflicts.
If this bug is relevant to other packages, then cherrypicking the patch
from upstream and following the Stable Release Updates process for
fixing/updating libinsighttoolkit5 is where
As a backporter *and* a Developer, I have some major concerns about this
request.
(1) This has no developer backing. One of the major things about a
Backport is it needs a developer or sponsor willing to push this
through. I don't see any tied to this request.
(2) This request does **not**
@GregSharp
It's invalid against the Development release, Mantic. We added the
series target for Jammy which is what you requested the target OS to be.
"Invalid" for a bare package bug is against the devel release, not for
the entire request, because we track that by series tasks/targets.
--
** Also affects: plastimatch (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: plastimatch (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
Le 23 mars 2023 à 06:29, Pierre Guiard a écrit :
> Beaucoup de cartes mère sérieuses( HP, Dell, Asus) embarquent un contrôleur
> de Ram qui fait aussi bien son boulot que Memtest.*
Il se trouve que c'est un HP avec lequel j'ai un problème.
Peux tu me préciser comment on procède stp ?
2
I'll make some inquiries on my end, I already hinted to ogra that if we can't
reach Martin then we are going to have to escalate this - maybe to the TB for
"abuse of technical privileges", maybe higher (Mark?).
Sent from my Galaxy
Original message
From: Dan Streetman
18.04 because that's approaching it's EoSS
date) in order to make everything function in the currently supported
releases.
Thomas
On 4/6/23 15:55, Robie Basak wrote:
Hi Thomas,
Thank you for caring for this package in Ubuntu!
I'm not sure I follow why this is difficult to fix by cherry-
18.04 because that's approaching it's EoSS
date) in order to make everything function in the currently supported
releases.
Thomas
On 4/6/23 15:55, Robie Basak wrote:
Hi Thomas,
Thank you for caring for this package in Ubuntu!
I'm not sure I follow why this is difficult to fix by cherry-
hear by end of the week I will be going higher up the tech tree to get
things acted on.
Thomas
On 3/28/23 09:40, "Jørgen Thomsen" wrote:
The tor browser cannot be installed using the torbrowser-launcher
0.3.3 currently in the ubuntu repo.
1) A number of problems arising from
Le 23 mars 2023 à 08:24, FARGET Vincent a écrit :
> Bonjour,
>
>
>
> Oui, il faut créer une clé "multiboot", avec ce type de chose, par exemple
> "multisystem" :
>
> https://doc.ubuntu-fr.org/multisystem
>
> ... ou aussi "Ventoy" :
>
> https://www.ventoy.net/en/index.html
>
>
> Cela
il possible de mettre les 2 dispositifs sur la même clé ?
> Le 22/03/2023 à 17:02, Thomas De Contes a écrit :
>> Bonjour :-)
>>
>>
>> Dans mes souvenirs, il y avait des distributions linux qui contenaient sur
>> leur support d'installation un dispositif permett
@ddstreet While I agree in principle, when something changes to adhere
to EFI spec, that's a pretty significant change. And saves us having to
do the approval *twice*. I don't disagree this isn't Fantu's fault, but
it shouldn't be much more difficult for them to get -4 into their PPA
and then us
The only reason I'm going to reject this is that there's changes in -3
and -4 in Lunar now which update to match EFI spec.
Can you do a reupload / sponsor of -4 from Lunar to backports here for
Jammy?
Attached are the -3 and -4 changelog from Lunar / Debian (because it was
synced)
emtest86+
Bonjour :-)
Dans mes souvenirs, il y avait des distributions linux qui contenaient sur leur
support d'installation un dispositif permettant de tester la RAM.
J'aurais voulu l'utiliser parce que là justement j'ai un doute sur ma RAM,
mais sur la clé Ubuntu 16 que j'ai sous la main, je ne vois
oduce code
versions for updating. If you need the newer version you might want to
consider updating to the 23.04 release when it's out. Otherwise you'll have to
stick with the 2017 package version that is available in the version of Ubuntu
you are using.
Thomas
-Original Message-
From: Ub
features.
I have not heard back from the Release team on this, or the SRU team, so
I'm re-asking this. Is the SRU / Release team willing to let us do a
one-time backport from Lunar of 0.3.6-2 to the older releases currently
supported (to Bionic but no further backwards)?
Thomas
On 2/1/23
features.
I have not heard back from the Release team on this, or the SRU team, so
I'm re-asking this. Is the SRU / Release team willing to let us do a
one-time backport from Lunar of 0.3.6-2 to the older releases currently
supported (to Bionic but no further backwards)?
Thomas
On 2/1/23
to remind people about the CoC and how to be nice towards
others, or at least be constructive without coming off as hostile).
Thomas Ward
Ubuntu Community Council Member
On 3/13/23 14:48, Steve Langasek wrote:
On Mon, Mar 13, 2023 at 06:03:00PM +, Dimitri John Ledkov wrote:
We pushed 6.1 out
to remind people about the CoC and how to be nice towards
others, or at least be constructive without coming off as hostile).
Thomas Ward
Ubuntu Community Council Member
On 3/13/23 14:48, Steve Langasek wrote:
On Mon, Mar 13, 2023 at 06:03:00PM +, Dimitri John Ledkov wrote:
We pushed 6.1 out
Unfortunately here your choices are limited. The ODBC from Microsoft is
different than the one in the repos and the two packages conflict.
>From my experience you will have to pick one or the other - use Microsoft's
>packaged ODBC and no headers, or use the one in the repos with the headers
e Release Team and
the SRU team for consideration before I go through the process of building all
this for the SRU/MRE/Version Bump processes as well.
A full changelog upstream is available on their GitHub -
https://github.com/micahflee/torbrowser-launcher
Thomas
LP: https://launchpad.ne
ed OPenSSL or such is
used for libraries.
I've made this revision in the backports policies because myself and
Mattia had an agreement in IRC on this, we can revert this in a future
discussion if necessary. Per policy, this is the note for the
discussion here on the ML.
Thomas Ward
Backport
I've discussed this with mapreri who is another person on the
backporters team.
Given the API/ABI changes that happen during OpenSSL microreleases that
break packages integrations AND that this will add a security delta
(-backports doesn't receive Security Team support so if they change and
patch
Mark, are you asking this to be backported in -backports or in -updates
and -security? This is one of the packages that if we do this in
-backports any security patches applied by the Security team for OpenSSL
in -security and -updates would be ignored with the higher version of
this in
OpenSSL is one of those tricky things out there I would like to get a
Security insight for before we do any kind of backporting of it.
There's other things this could impact, backports or not.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is
Hi Julian,
On 12.01.23 17:54, Julian Andres Klode wrote:
(resend with proper subject, sigh, mutt mishaps)
As part of deb822 sources file enablement, the specification
states a MVP for 23.04 to move sources.list to sources.list.d/
ubuntu.sources (in deb822 format obviously) inside Docker
If the package is not yet in 22.04 it is unlikely to land except via Backports
which is its own process.
Sent from my Galaxy
Original message
From: Kent Kutan
Date: 1/14/23 16:34 (GMT-05:00)
To: ubuntu-devel-discuss@lists.ubuntu.com
Subject: libapache2-mod-shib2 package
Sponsored to -backports. I require at least one other backporter to
look at and OK this for acceptance into backports however.
Removing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
You already got a response on this thread from Colin, quoted below:
On Tue, Jan 03, 2023 at 12:04:34PM +0530, probal basak wrote:
> I am getting the below exception while trying to issue apt update:
> Getting this issue since last week. Previously the same thing used to
> work perfectly fine.
** Changed in: ipmctl (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1968076
Title:
[BPO] ipmctl with support for CPS hardware
To
FYI that's MOST vulnerability scanners. Most of them do not have privileged
access nor the database of ubuntu patch info in them so report solely on the
exposed version number and thats it. It leads to a lot of false positives and
then questions like these. ;)
Sent from my Galaxy
> I intend to update Ubuntu's debuginfod instance to use this new
package in the near future.
By "update" do you mean SRU or via Backports? If you are not going to
be doing this via Backports, then I would suggest that you hunt an SRU
on the sole basis that mixing and matching SRU/Backports
More about this here:
https://github.com/jobisoft/TbSync/issues/630#issuecomment-1308820475
There are many users with this quite essential plugin who can't get
their data synced anymore since a few weeks.
Thanks for releasing an update very soon
Thomas
--
Ubuntu-devel-discuss mailing list
This sounds like something that should be an SRU not a backport.
Especially since theres an open bug on this and a patch exists.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1995967
Mattia: Big change or not, SRU team might let it through because it's a
*performance bug fix*. This alone is not sufficient, in my opinion, for
a backport, when an SRU is the process it should be going through
because it fixes a bug - a performance one, granted, but it's still
SRUable I believe.
Is there a reason the fixes can't be cherrypicked and then SRU'd to fix
this issue? Backports is typically NOT the way to get fixes for issues
into already stable releases.
** Changed in: man-db (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Not all Autopkgtests have run and therefore you cannot claim they are
all passing. This is marked Incomplete until you have provided evidence
that all the autopkgtests and such clear for all supported
architectures.
** Changed in: libreoffice (Ubuntu Bionic)
Status: In Progress =>
OK just doing due diligence.
Approved for backports pocket, it'll need to build and publish then
should be available afterwards.
** Changed in: libreoffice (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
I'm confused, are you asking for a backport to the backports pocket or
an SRU? The bug refers to SRU in multiple places.
Backports in the backports pocket are NOT SRUs so its critical to
identify which process and goal you have in mind - SRU or backport.
--
You received this bug notification
of the program installed, and instead relying on nitpicked fixes.
Thomas
On 8/30/22 16:45, Maxime Pietrucci-Blacher wrote:
Good evening, I have come to contact you to find out if the
nginx-common and nginx-core packages are going to be updated soon, as
there are many problems with the use of TLS
in Ubuntu [2].
CVE-2022-29154 is the second one, and was deemed too intrusive [3] to include
as a security update for any of the releases at the time of review (see the
details in the link).
--
Thomas
[1]: https://rsync.samba.org/security.html
[2]: https://ubuntu.com/security/CVE-2022-37434
[3
Marking this as Won't Fix because of identified issues and Unit
indicating that this should be withdrawn.
** Changed in: dh-python (Ubuntu Focal)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to
** Changed in: elfutils (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1987356
Title:
[BPO] elfutils/0.187-1 from Kinetic
To
Both are in the process of working. socksio is in backports and
published. nala is pending publication in backports.
** Changed in: socksio (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nala (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: nala (Ubuntu)
(Backports pocket is a little bit different than AA "NEW" queue)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1984053
Title:
[BPO] nala/0.11.1 and socksio/1.0.0-2 from Kinetic Kudu
socksio has been accepted but I can also accept nala as well, if it
FTBFS we'll just rerun the build.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1984053
Title:
[BPO] nala/0.11.1
As of the July 25th DMB meeting, this Core Developer application was
approved, and we welcome Mattia into the ranks of the Ubuntu Core
Developers.
Congratulations, Mattia!
Thomas
Ubuntu DMB Member
On 7/13/22 12:13, Mattia Rizzolo wrote:
Hi DMB!
I decided to finally send in my core-dev
nion, so with my CC hat on, in my
opinion, you're taking non-consensus actions claiming this needed CC
intervention.
You can make requests for improvement as an individual developer
without needing to speak on behalf of the Community Council.
Thank you,
Jeremy Bicha
---
Thomas Ward
"The Man o
embers of Canonical’s development
teams thanks to my connections as an Ubuntu member.
Thomas
From: Ubuntu-devel-discuss On
Behalf Of wei tang
Sent: Wednesday, May 25, 2022 03:29
To: ubuntu-devel-discuss@lists.ubuntu.com
Cc: christoph.mar...@uni-mainz.de; k...@roeckx.be
Subject: Questions about openssl in
this issue?
1. move back the packages to normal linux-modules?
but I estimate there are packages not used very often on arm64 to save some
space.
2. create a depency on strongswan to linux-modules-extra-raspi on raspi
platform - maybe also other plattform, but I don't know.
br
Thomas
"failed to install/upgrade" also means that a package failed to
configure. If as Simon says the packages were left unconfigured, then
that means the package is "Installed but failed to restart on upgrade"
which is an action the postinst scripts execute. So it may not be an
'installer' failure
Looks like during your upgrade a certificate went awry, but this isn't
an NGINX issue, it's the maintenance of your system on your end.
From the journalctl data:
Jun 04 14:21:05 heliopolis-aws nginx[44002]: nginx: [emerg] cannot load
certificate "/etc/ssl/certs/heliosd.crt": BIO_new_file()
a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
https://bugs.lau
ror can't find grub_platform"
which is related to a few lines grub.cfg. In the end it turned out that
disabling these lines silences the message but does not speed up booting.
Have a nice day :)
Thomas
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
*
NACK as is. (negative acknowledgement aka "Debdiff Rejected")
You are attempting to submit a new upstream version not in the Ubuntu
repositories. Unlike Debian, an Ubuntu backport requires a little more
work to push this in.
Jammy has 03.00.00.0423-1. Your debdiff is for 03.00.00.0429 which is
NACK as is. (negative acknowledgement aka "Debdiff Rejected")
You are attempting to submit a new upstream version not in the Ubuntu
repositories. Unlike Debian, an Ubuntu backport requires a little more
work to push this in.
Jammy has 03.00.00.0423-1. Your debdiff is for 03.00.00.0429 which is
If you can give me an extra day or two (I'm suffering from COVID right
now), I can sponsor this. I'll let the other backporters handle
approval, etc. but uploading the package is something that only takes a
few minutes on my part. (Just need the patience - COVID is evil)
--
You received this
If you can give me an extra day or two (I'm suffering from COVID right
now), I can sponsor this. I'll let the other backporters handle
approval, etc. but uploading the package is something that only takes a
few minutes on my part. (Just need the patience - COVID is evil)
--
You received this
Public bug reported:
$ cat hello.f
print *,"Hello, world"
end
$ f2c hello.f
hello.f:
MAIN:
$ cat hello.c
/* hello.f -- translated by f2c (version 20160102).
You must link the resulting object file with libf2c:
on Microsoft Windows system, link with libf2c.lib;
If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.
Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark
I haven't been able to find other actual bugs/issues describing this
issue, but there are threads on reddit and such that seem to indicate
that this is a wayland/gnome42 issue, and that it affects all
distributions.
Sorry something went wrong with copy/paste in the description.
Central issue is that the part where the MOK certificates are loaded (in
5.15.0-33-generic):
```Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate:
UEFI:MokListRT (MOKvar table)
Mai 25 00:14:56 silvershadow
Public bug reported:
I started to test the oem kernel on ubuntu 22.04 jammy. Doing so I
wondered why all my dkms modules don't load when secure boot is active
although they are correctly signed. After investigating quite a while I
found that the MOK certificates are not loaded during boot. This
*** This bug is a duplicate of bug 1970069 ***
https://bugs.launchpad.net/bugs/1970069
well i'm getting to the roots of this step by step.. but as far as i see
it now i reported a bug where kernel parameters that set the loglevel
are beeing ignored by system daemons that monitor the init
*** This bug is a duplicate of bug 1970069 ***
https://bugs.launchpad.net/bugs/1970069
i'm quite sure that this is NOT a duplicate.. the other bug refers to
some kernel upgrades that lead to error messages with acpi and usb
devices in 22.04 (i also have these kernel messages but they are
Public bug reported:
running a fresh install of kubuntu 22.04
plymouth version: 0.9.5+git20211018-1ubuntu3
What should happen:
Plymouth should totally cover all bootmessages (no bootmessages should be
printed to console in the first place)
What actually happens:
When Plymouth quits the
y to it, because casper installed MBR partition 2
again after creating its persistent partition:
# Take care not to name any of your valuable disks as USB_STICK
USB_STICK=/dev/sdX
sudo dd if=/dev/zero bs=1 count=16 of="$USB_STICK" conv=notrunc seek=462
Have a nice day :)
Thomas
--
Agree with the comment and this particular update process is likely
acting as expected since an unsigned kernel was found. However, just to
set the context right - I didn't install the unsigned kernel. I rolled
back kernel 4.15-0-177 to work around Bug #1973482, using apt remove and
it
Public bug reported:
Dell XPS 15 9570. Dual boot with Windows 10. Linux was on 18.04 when
attempting to upgrade to 20.04. Had previously installed kernel
4.15-0-177 which was rolled back to working kernel 4.15-0-175 due to
issues already reported in Bug #1973482. Due to rollback, there was an
1427797/lshw.txt),
- (a Gigabyte GA-970A-DS3, BIOS F7a 01/24/2013 of tlk in #91, of which we
have no confirmation that removing MBR partition 2 really helps).
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
nc count=16
+dd if="$MBR_STASH" bs=1 seek=462 conv=notrunc count=48
fi
+rm "$MBR_STASH"
@Steve Langasek: Are you watching ? Do we need to open a new bug ?
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bu
and rarer machines,
- and can be disabled by the dd procedure.
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages to boot on BIO
iefly explain the problem and propose the manipulation
before putting the ISO onto the USB stick.
It would warn not to do this unless a first boot attempt really lasted
unreasonably long.
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs,
er, -indev without -outdev to the same device prevents writing
and -report_system_area "plain" does not want to write to the device.
So it would be safe even for the system disks.)
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
an option either.
So we should find easy-to-apply remedies for those old machines which need
to be left behind. To do so, we need to know which group of them will be
abandoned by the unmodified ISOs.
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of
Mark,
I'm tempted to start the migration to Kea, but the documentation is
extremely vague on proper migration. If we intend to move in that
direction, we'll need to have a migration guide of some sort, so that
it's a more seamless transition for people. Just a thought.
Thomas
On 5/16
or Lubuntu.
Thomas
(sent without my @ubuntu.com because GMail addresses are involved)
On 5/14/22 21:42, Aaron Rainbolt wrote:
Thank you for taking the time to reply. This is sort of what I was
thinking when I asked the question, but it's still close enough to a
problem that I'm worried about
t.
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
https:/
Public bug reported:
When starting the repo command (with no arguments) in a initialized repo
folder, it fails to start. Here is the traceback of the failure output
on the shell.
Traceback (most recent call last):
File "/home/tepperson/yocto/.repo/repo/main.py", line 56, in
from
the fence:
Fedora considers to adopt for its ISOs the GPT partition layout without
boot flag in MBR:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/2G3DQ5SGCV5DSD7NPVXU3KAKQ57BOXVU/
They found a Dell XPS 15 L502X laptop which does not boot from this
but also does not boot if a
** Attachment added: "lspci-dell-latitude-7300.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590019/+files/lspci-dell-latitude-7300.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue with Dell Latitude 7300. Device detection like disks fail,
apparently randomly. Some media keys don't work, Wifi was OK.
Previous kernel build is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "cpuinfo-dell-latitude-7300.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590018/+files/cpuinfo-dell-latitude-7300.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With this issue I was facing another one issue like my hp docking system
is not working. But after long time I found the best solution from this
website:
https://internettablettalk.com/fix-hp-docking-station-not-working/
--
You received this bug notification because you are a member of Ubuntu
101 - 200 of 59340 matches
Mail list logo
