** Changed in: ubiquity (Ubuntu)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1173655
Title:
Ubuntu 13.04 - ubiquity crash due to the wifi bro
awesome :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2099864
Title:
[p-m] depwait on riscv64 due to missing linux-bpf-dev in Ubuntu
Status in linux package in Ubuntu:
Invalid
Sta
--- stderr ---
Ubuntu clang version 20.1.0 (+rc2-1~exp2ubuntu0.4)
Target: bpf
Thread model: posix
InstalledDir: /usr/lib/llvm-20/bin
Available CPUs for this target:
generic
probe
v1
v2
v3
v4
Use -mcpu or -mtune to specify the target's processor.
For
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711358
Title:
20170817 - ISO hangs on boot on qemu with splash scre
** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work with secure boot
** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916971
Title:
After fresh Ubuntu 20.04 install, dow
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1874278
Title:
Can't install any packages with ub
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857398
Title:
ubiquity should support encryption by default wit
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1547332
Title:
[Feature Request] Provide option to install root to a
** Changed in: linux-base (Ubuntu Plucky)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/2098735
Title:
Update apport kernel symlinks
Status in
Sure, let's give this a try!
I'm curious if $arch will work, but let's see.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095529
Title:
Please merge 2.2.7-2 into plucky
Status in
The SRU template definitely looks a bit light, but I have no objections
with your patch. It's in the queue now.
Thanks!
** Also affects: thermald (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: thermald (Ubuntu)
Status: New => Fix Released
** Changed in: thermal
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049352
Title:
Package BlueZ 5.72 for Noble
Status in bluez pack
This was missing a build dependency on python3-pygments (which is in
Main), I added it.
Testing well with my Beats Flex, YouTube Music with the Firefox Nightly
snap. I can adjust the latency offset with no issue, and blueman DTRT
with connecting and disconnecting. Popped open journalctl and syslog
It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)
After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.
--
You received this bug notification because you are a member of Ker
> Simon, ell already has a recent approved MIR LP: #1971738
Er, the binary packages in question don't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
Force pushing my local commits over, sorry not sorry. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.
I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.
Something's up with my loca
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:
```
$ check-mir
Checking support status of build dependencies...
* debhelper-compat does not exist (pure virtual?)
* libel
** Changed in: bluez (Ubuntu)
Status: Fix Released => In Progress
** Summary changed:
- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)
--
You received this bug notifi
Daniel, I don't want you to feel burned over this. That wiki page does
seem quite rational, and I appreciate that you linked it. I'm reading
some mixed feelings, so let me be clear: thank you for the work you
*are* able to put into this.
Both Gianfranco and I are Ubuntu Core Developers but are als
> In other words, asking an Archive Admin to build binfmt-support on
i386.
I have stopped short of this so far because I'm entirely unsure if we
still need that build dependency in the first place. Debian doesn't have
it, and I'm not sure I see rationale on our end for it.
There is probably somet
Following the dependency chain through to the cause for the i386 builds,
binfmt-support should be added to the i386 allowlist. This may be a bug
in evolution-data-server in the case libebook-contacts-1.2-4 can build
without libphonenumber8-protobuf32 - for now, blanket-disabling that
dependency in
This is now blocking a Lubuntu feature goal. I tested this locally with
my bluetooth earbuds, and have been streaming audio with no problems.
Uploaded Gianfranco's packaging with some minor tweaks.
Please, we *need* to merge this from Debian *this* cycle. The Security
Team will NOT be happy when
Rik mentioned a common mistake that I've been trying harder to catch
(but didn't in this case, to my great frustration)...
If we're doing a merge and an orig tarball already exists in Debian,
always always ALWAYS grab that one instead of using uscan or finding the
tarball yourself. It breaks tooli
The reason I essentially blindsponsored this was out of faith and
courtesy for the Desktop Team.
Lubuntu does similar things, but we have a merge party from Debian once
a cycle. If your response would be "we don't follow Debian," *I get it*,
but once or twice a cycle a merge should really be looke
Daniel, if you'd like to iterate on this (a debdiff for an ubuntu2
upload), it would be appreciated.
If you don't have the time, say the word, this looks like a simple fix.
...on everything but i386. What's up with that?
--
You received this bug notification because you are a member of Kernel
P
> 34174 lines in this case is not plausibly reviewable.
I typically use filterdiff to get the packaging changes, and review
specific source files as necessary (including copyright changes in the
diff, which can be important, even if you're just using a script for
it).
Thanks for your help here. I
I very much dislike reviewing packages this way. For a package to be in
the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz.
I understand that it's a new upstream release, but that does not excuse
the need for a debdiff, even if you *also* include these files.
I'm uploading this
** Changed in: thermald (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: thermald (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842382
Title:
/proc/self/maps paths missing on live session (was vlc won't start;
eoan 19.10 & bionic 18.
The bug was only fixed in our Calamares configuration and still needs to
be fixed in initramfs-tools.
Adjusting bug statuses appropriately and adding the release tag. I'll
ping vorlon and xnox on IRC to get their take.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump comman
Please see my comment on bug 1771783 -- unsubscribing the Ubuntu
Sponsors Team.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771764
Title:
Add enca
Hello! Thank you for your contribution to Ubuntu.
If you would like this to be sponsored to Xenial, please edit the bug
description to follow the SRU bug template. More information can be
found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
Additionally, I see in your debdiff
Bump; was this patch sent upstream? What is the status of it at the
moment?
The attached patch can't be uploaded as-is to any currently-supported
release, unsubscribing sponsors (please resubscribe when more details
are given).
--
You received this bug notification because you are a member of Ke
Unsubscribing ~ubuntu-sponsors because there is nothing more to sponsor.
If this was done in error, please resubscribe us.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/179
** Changed in: bionic-backports
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package thunderbolt-tools - 0.9.3-3
Sponsored for Colin Ian King (colin-king)
---
thunderbolt-tools (0.9.3-3) unstable; urgency=medium
* Remove redundant copy of udev rules (LP: #1762187)
-- Colin King Sun, 8 Apr 2018 15:43:12
+0100
** Changed in: thun
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/997085
Title:
Unable to install Ubuntu 12.04 (neither 32 nor 64 bit)
Status in ubiquity package in Ub
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Unsubscribing ~ubuntu-sponsors as there's nothing left to do. If that is
incorrect, please feel free to resubscribe.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1550301
Title:
ZFS
Doesn't affect the test cases.
** Description changed:
Using Virt-manager the Beta2 ISO fails to boot when a UEFI BIOS is
selected. 4GB RAM, 8 CPUs. Nothing appears on the console after the
Tiancore splash screen.
+
+ Here is an image of what it hangs at:
+ http://img.ctrlv.in/img/16/09/27
I can reproduce this bug on my system with 1 GB of RAM and 1 CPU core
assigned to it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1627875
Title:
Yakkety server Beta install fails in a
@sudodus Is this the Xenial daily image or the Yakkety daily image that
is affected?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1596281
Title:
the target drive is not found when conn
61 matches
Mail list logo
