There was a funky character stream in the changelog due a fancy
apostrophe that got messed during the Jammy debdiff generation, I don`t
know how...
`1. Copy the font to userM-CM-"M-bM-^BM-,M-bM-^DM-"s directory.$`
...
** Patch added: "wsl-setup debdiff for jammy"
https://bugs.launchpad.net/
Updated the bug description and title to turn this into a SRU bug.
** Description changed:
- While doing the WSL Import and run test for 24.04.2, gtk4-demo failed to
- launch due to missing the library for libGLESv2.
+ [ Impact ]
+
+ * libgtk-4-1 has an implicit dependency on libgles2. GTK4 apps
** Also affects: gtk4 (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109978
Title:
[SRU] Update gtk4 to 4.14.5 for Noble
To manage notific
The previous debdiff of livecd-rootfs for jammy contained a bunch of
spurious whitespace changes in the debian/changelog file. This one
eliminates those spurious changes. Otherwise, the source contents remain
the same.
Proof of build can be found at:
- AMD64:
https://launchpad.net/~cnihelton/+ar
** Also affects: wsl-pro-service (Ubuntu Questing)
Importance: Undecided
Status: New
** Summary changed:
- [SRU] wsl-pro-service version 0.1.18 for Plucky, Oracular and Noble
+ [SRU] wsl-pro-service version 0.1.18 for Questing, Plucky, Oracular and Noble
--
You received this bug notif
The previous debdiff contained undesired changes past the changelog.
This one is correctly bound to only add the relevant changelog entries
without rewriting the package history. Otherwise, the source contents
remain the same.
Proof of build can be found at:
- AMD64:
https://launchpad.net/~cnihe
** Patch removed: "wsl-setup debdiff for jammy"
https://bugs.launchpad.net/ubuntu/jammy/+source/wsl-setup/+bug/2091293/+attachment/5875016/+files/jammy-wsl-setup.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Patch removed: "livecd-rootfs debdiff from jammy-updates"
https://bugs.launchpad.net/ubuntu/jammy/+source/wsl-setup/+bug/2091293/+attachment/5874911/+files/jammy-livecd-rootfs.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
We need to update questing first, thus here's the appropriate debdiff.
** Patch added: "debdiff for questing"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2106757/+attachment/5876408/+files/questing.debdiff
--
You received this bug notification because you are a member of U
** Description changed:
[ Impact ]
4.14.5 is a new bugfix release from upstream:
- https://gitlab.gnome.org/GNOME/gtk/-/blob/4.18.5/NEWS?ref_type=tags
+ https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/NEWS?ref_type=tags
- * Bugs fixed:
- - #5844 `gdk_surface_get_device_position: asser
Public bug reported:
[ Impact ]
4.14.5 is a new bugfix release from upstream:
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.18.5/NEWS?ref_type=tags
* Bugs fixed:
- #5844 `gdk_surface_get_device_position: assertion 'GDK_IS_SURFACE (surface)'
failed` on popover close (Alessandro Astone)
- #7
** Description changed:
- [WIP]
+ [Impact]
+
+ With the increasing adoption of tools like authd, it's very likely that
+ Linux desktop users in corporate environments end up with their
+ usernames like 'u...@org.com', what doesn't play nice with
+ sbuild/schroot. Without properly escaping the use
Here's the debdiff for oracular
** Patch added: "oracular.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2109853/+attachment/5875432/+files/oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Here's the debdiff for noble.
** Patch added: "noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2109853/+attachment/5875433/+files/noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Here's the debdiff for plucky
** Patch added: "plucky.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2109853/+attachment/5875431/+files/plucky.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
[WIP]
Fore more information about the issue, please check the upstream bug:
https://salsa.debian.org/debian/sbuild/-/issues/4
Skipping questing because it will receive the fix via debian-merges.
** Affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
**
The AMD64 build above behaved as expected in my tests. Other community
members are invited to test them if they have some time to spare.
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages
Images for AMD64 and ARM64 architectures are available at the following
Launchpad build links:
- AMD64:
https://launchpad.net/~ubuntu-wsl-dev/+livefs/ubuntu/jammy/wsl/+build/781418
- ARM64:
https://launchpad.net/~ubuntu-wsl-dev/+livefs/ubuntu/jammy/wsl/+build/781419
Those images were built from
Attached is the debdiff proposed for wsl-setup on 22.04 to make it
possible to build images of that LTS in the new WSL tar-only image
format.
The following links point to proof of builds from a PPA:
https://launchpad.net/~ubuntu-wsl-
dev/+archive/ubuntu/ppa/+build/30662779 and
https://launchpad.ne
Attaching now my proposed debdiff for livecd-rootfs targetting 22.04,
based on the current version available in jammy-updates.
Here's a link to a PPA as a proof of build:
https://launchpad.net/~cnihelton/+archive/ubuntu/pplayground/+build/30661786
With that we aim to provide supported images from
Proof of builds with the already attached debdiffs can be found on the
following PPA links.
Their version numbers are suffixed with the "~ppaN" to ensure version released
in the archive will override the PPA version afterwards.
Plucky:
- AMD64:
https://launchpad.net/~cnihelton/+archive/ubuntu
Public bug reported:
As part of our offerings to bring Ubuntu Pro to wider audiences we need
to backport this service to Ubuntu 22.04 LTS, so users can benefit of
the upcoming GA of Ubuntu Pro for WSL, as Windows system that allows
more easily secure and manage WSL instances, by automatically pro-
Proof of build can be seen in this PPA:
https://launchpad.net/~cnihelton/+archive/ubuntu/pplayground/+packages?field.name_filter=&field.status_filter=published&field.series_filter=jammy
The version numbers are slightly changed because I wanted to make sure
the archive will contain a higher version
** Attachment added: "wsl-pro-service_0.1.18~22.04.1_source.changes"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+attachment/5871127/+files/wsl-pro-service_0.1.18~22.04.1_source.changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "wsl-pro-service_0.1.18~22.04.1_source.buildinfo"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+attachment/5871126/+files/wsl-pro-service_0.1.18~22.04.1_source.buildinfo
--
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "wsl-pro-service_0.1.18~22.04.1.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+attachment/5871125/+files/wsl-pro-service_0.1.18~22.04.1.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "wsl-pro-service_0.1.18~22.04.1.dsc"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+attachment/5871124/+files/wsl-pro-service_0.1.18~22.04.1.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
tem journal.
+ * Removes workaround for livepatch no longer needed since pro-client v35
+ - systemd service is more confined again.
+ * Prevents unnecessary re-registration with Landscape
+ - by passing the CLI flag --register-if-needed to landscape-config.
+ * Upgrades va
** Summary changed:
- [SRU] Fix too much logging and fix vulnerabilities GO-2025-3563, GO-2025-3447
and GO-2025-3373
+ [SRU] wsl-pro-service version 0.1.18 for Plucky, Oracular and Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Patch added: "debdiff for noble"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2106757/+attachment/5870932/+files/noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/210
** Patch added: "debdiff for oracular"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2106757/+attachment/5870931/+files/oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Patch added: "debdiff for plucky"
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2106757/+attachment/5870908/+files/plucky.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
** Description changed:
- WIP
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and justification
+for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [ T
Public bug reported:
WIP
** Affects: wsl-pro-service (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106757
Title:
[SRU] Fix too much loggin
Skia, Thanks for your support.
I've issued that command you recommended, got some more errors googled a bit
and got the solution (chatgpt). You were right. I've tried to upgrade my hole
system some days before.
You support was fundamental to get me to the solution. Thanks a lot.
--
You received
This was what I'd got from GPT
GPT's Message
The message indicates that your system needs to be fully updated before
you can upgrade to a new Ubuntu release. Follow these steps to resolve
the issue:
### Step 1: Update Your Current System
Run the following commands:
```bash
sudo apt update
The current way of updating WSL is via its own command line: wsl
--update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987970
Title:
after installing wsl-setup WSLG GUI apps stopped working
To m
** Changed in: wsl-setup (Ubuntu)
Assignee: (unassigned) => Carlos Nihelton (cnihelton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104307
Title:
wsl-setup script not waiting for cloud
** Changed in: wsl-setup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104307
Title:
wsl-setup script not waiting for cloud-init to finish on plucky
To man
Public bug reported:
This bug is fixed upstream already but not yet released to Ubuntu. The
wsl-setup script should detect whether cloud-init is supposed to run or
not, and if so wait for it to complete before proceeding with its other
business. That's the behaviour observed on Noble but not on Pl
I'm seeing this on a fresh install of Plucky, I'm not sure when or how
mediascanner2.0 would have been installed and removed, unless if it was
a dependency of some other package and no longer is.
cn@a515 ~$ apt policy mediascanner2.0
mediascanner2.0:
Instalado: (nenhum)
Candidato: 0.117-3
Ta
> atm It looks that way, there certainly should be some though
>
> comment #4's
> @{HOME}/.cert/nm-openvpn/* r,
>
> seems reasonable. We will have to look into others
I'd rather use .config/ instead of .cert/ to be more aligned with the
XDG Base directories specification.
--
You received this b
** Changed in: javascript-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100586
Title:
package javascript-common 11+nmu1 failed to install/upgrade: in
Also reproduceable on a fresh install of Plucky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098513
Title:
eglinfo -B crash (seg fault)
To manage notifications about this bug go to:
https://bugs
Public bug reported:
Almost every installation I try using apt-get I get an error like this:
dpkg: error processing package javascript-common (--configure):
installed javascript-common package post-installation script subprocess
returned error exit status 1
(...) # this changes the depending on
** Changed in: gtk4 (Ubuntu)
Milestone: None => ubuntu-24.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098698
Title:
libgtk-4-1: Missing dependency libgles2 on Noble
To manage notificati
** Changed in: gtk4 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098698
Title:
libgtk-4-1: Missing dependency libgles2 on Noble
To manage notifications
** Summary changed:
- gtk-4-examples: Missing dependency libgles2
+ libgtk-4-1: Missing dependency libgles2 on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098698
Title:
libgtk-4-1: Missing
Hi! Many thanks for reporting this bug. In fact the test case already
warns about the implicit dependency.
The key point is that libgtk-4-1 up until version 4.14.4 didn't
explicitly depended on libgles2, even though it tries to render with
libGLESv2 at runtime. Newer versions of Ubuntu have that s
Missing package released (linux-signatures-nvidia-6.11.0-18), so I
upgraded and solved it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098724
Title:
Missing package linux-signatures-nvidia
Same here :(
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-18-generic (64-bit)
Graphics Platform: X11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Hi folks! I came across a very similar installer error related to snap
seed validation when trying the latest Kubuntu Plucky image published on
Feb 14. Calamares session.log (see attachment) contains this interesting
snippet:
```
2025-02-15 - 06:37:58 [6]: DEBUG (Qt): "Downloading snaps completed"
** Package changed: mesa-demos (Ubuntu) => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Milestone: ubuntu-25.04 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098513
Title:
eglinfo -B cra
If I add both nvidia and mesa json files to that environment variable it
also crashes.
$ echo $__EGL_VENDOR_LIBRARY_FILENAMES
/usr/share/glvnd/egl_vendor.d/10_nvidia.json:/usr/share/glvnd/egl_vendor.d/50_mesa.json
$ eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL ve
It seems pretty much like this bug:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12300
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #12300
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12300
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
On a plucky system recently upgraded from oracular with nvidia-
driver-570, `eglinfo -B` crashes with seg fault but if I run
`__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json
eglinfo -B` it succeeds.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Pack
Is the approach documented in https://forum.snapcraft.io/t/thunderbird-
snap-and-external-gnupg-for-smart-cards/39553 a viable solution to this
problem?
In a nutshel:
1. Forcing GPGme library to invoke the gpg binary shipped inside the snap and
2. Changing the AppArmor profile to allow connecting
@ahasenack, in case you need to track, with
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2091293/comments/22,
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2091293/comments/23 and
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2091293/comments/24
we complete one r
I successfully completed the following test cases:
* New instances on WSL1 (with cloud-init and WSL 2.4.8 or later - previous
versions of WSL had a bug not handling WSL1 properly)
* Package a rootfs containing wsl-setup 0.5.8 in the current format (Windows
application package)
on a Windows 11 l
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
To ease testing those packages @didrocks made available a test image in
the new format (.wsl) at the following address:
https://people.canonical.com/~didrocks/tmp/livecd.proposed.ubuntu-
wsl.wsl
The image was built with livecd-rootfs from noble-proposed and it
contains wsl-setup from noble-propos
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
** Changed in: livecd-rootfs (Ubuntu Noble)
Milestone: None => ubuntu-24.04.2
** Changed in: wsl-setup (Ubuntu Noble)
Milestone: None => ubuntu-24.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Hi @Andreas!
Per our conversation (for future reference):
1. do-release-upgrade: nothing happens. Upgrading the wsl-setup package
won't trigger any scripts per se. The content introduced in version
0.5.8 is only invoked by WSL itself (the Windows machinery) at
provisioning time. WSL has no notion
** Patch added: "Noble livecd-rootfs debdiff (24.04.82 to 24.04.83)"
https://launchpadlibrarian.net/772357299/livecd-rootfs_24.04.82_24.04.83.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Notice the binary ubuntu.ico didn't exist in previous versions, it's an
addition as part of the new format.
That's the reason for this line in the diff:
```
Binary files /tmp/tmpyoybmkkw/NMxChGAzw2/wsl-setup-0.5.4~24.04/wsl/ubuntu.ico
and /tmp/tmpyoybmkkw/QP2sYT2qeL/wsl-setup-0.5.8~24.04/wsl/ubu
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
** Description changed:
[Context]
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
Thanks a lot.
El jue, 9 ene 2025 a las 15:45, Julian Andres Klode (<
2093...@bugs.launchpad.net>) escribió:
> Thank you for your bug report. It seems your machine is using an out of
> date mirror configuration. Please pick a new one from software & updates
> in the desktop, or editing sources.lis
Public bug reported:
There are error for mirror not disponible for minimal instalation from
16.04 to 18,04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.32 [origin: unknown]
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-
** Attachment added: "pro_logs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2092548/+attachment/5847788/+files/pro_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Public bug reported:
the camera was working on ubuntu 24.04 but stopped working on ubuntu
24.10 and I have already tried using the kernel's native drivers and the
previous ones via intel and it doesn't work.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: intel-ipu6-dkms (not installed)
Pro
** Description changed:
[Context]
+
Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows application packages nor MS Store [1,2].
Instead distros are shipped as a single rootfs tarball with some special
metadata and the ".wsl" extension (to all
** Description changed:
- Microsoft is moving to a new package format which will allow us to
- release a .wsl rootfs and will be published to releases.ubuntu.com. Move
- to that format.
+ [Context]
+ Microsoft recently announced a new format for WSL distributions that no
longer depends on Windows
** Summary changed:
- Move WSL to new Microsoft WSL package format
+ [SRU] Move WSL to new Microsoft WSL package format
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091293
Title:
[SRU] Move WSL t
Public bug reported:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log f
Was cloud-init meant to be used in this set up at all?
It would be good to have the /run/cloud-init/ds-identify.log as part of
this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087605
T
Hi Dennis, thanks for you answer.
This week a did a upgrade to VMWare Workstation Pro 17.6.1 and the issue with
the lshw continues.
# vmware --version
[AppLoader] Use shipped Linux kernel AIO access library.
An up-to-date "libaio" or "libaio1" package from your system is preferred.
# modinfo v
4 and 172.16.12.0/24 to share folders.
Regards
======
Carlos Alberto Lima dos Santos
Eng. de Computação
http://www.linkedin.com/in/carlostoca
Campinas-SP / Brasil
On 9/23/24 06:38, Miriam España Acebal wrote:
> Hello Carlos Alberto,
>
> Thank you for taki
Public bug reported:
Failed to install.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: firefox (not installed)
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Da
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => José Carlos Cárcamo Camacho (charlisious)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047384
Title:
System Encryption Password
Same bug in Ubuntu 22.04.4, to install virtualbox-7 fixed the problem.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Virtualbox Guru meditation on VM start caused by kernel com
This is a common scenario for some customers on AWS, where they either
have strict rules for allow-listing external endpoints (so, instead of
getting a quick response for pro with the error, they only get a
timeout) and airgapped customers with no knowledge about setting up an
airgapped-contract se
Public bug reported:
pro collect-logs takes more than 1:30 minutes to complete on air-gapped
envs, while `pro status` and `pro help` won't work at all. After the
same amount of time they throw the `[Errno 101] Network is unreachable`
message.
Tested on 24.04 Pro on AWS and pro client version 31.2
We have seen this bug quite often on AWS when the customer is using
imported VMs. This means that cloud-init was initialized before the
image being imported to AWS, therefore, customers get that error when
converting to Pro. It has been quite a headache to be honest and while
the workaround works,
Public bug reported:
If use Nautilus or command line to share a folder
'net usershare' returned error 255: cli_rpc_pipe_open_noauth: rpc_pipe_bind for
pipe lsarpc failed with error NT_STATUS_CONNECTION_DISCONNECTED
net usershare add: cannot convert name "Everyone" to a SID. The transport
connec
Hi, dhcpig is working for sure with python 3 since version 1.5-4 (in
Debian at least, can't be sure for Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063966
Title:
version not compatible wi
7:55:35-03:00 [TERM="xterm-256color"
TTY="/dev/pts/1" COLUMNS="152" LINES="24"]
- [?2004h]0;root@toca-work:
/home/carlos/Dados/BeginConfig[01;31mroot@toca-work[00m:[01;34mBeginConfig[00m#
lshw -html
+ [?2004h]0;root@toca-work:
/home/ca
" LINES="24"]
[?2004h]0;root@toca-work:
/home/carlos/Dados/BeginConfig[01;31mroot@toca-work[00m:[01;34mBeginConfig[00m#
lshw -html
[?2004l
DMI
SMP
PA-RISC
device-tree
SPD
memory
/proc/cpuinfo
CPUID
PCI (
I don't have access to that PC now, it belongs to someone else, othere
people reported issues with their gpus, I think you should launch an ISO
before 24.04.1 correcting this with an upgraded version of drivers and
the oem installer as well
--
You received this bug notification because you are a
Same problem here. Affects some apps like VS Code, LibreOffice... But
not others like Firefox or Nautilus. Using Xorg and NVIDIA drivers.
Never turned on autologin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
error al procesar el archivo /var/cache/apt/archives/texlive-fonts-
extra-doc_2017.20180305-2_all.deb
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: texlive-fonts-extra-doc 2015.20160320-1
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Lin
Your question means that I didn't clarify enough the test I followed and
how it related to the original test plan proposed. The gap in
understanding is more due WSL specifics than cloud-init itself.
The fundamental difference between what is proposed in the bug report
and what I applied manually i
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
Well guys, yesterday I had the brilliant idea to update my Ubuntu from
23.10 to 24.04 LTS.
Silly me for not doing much research, but my laptop (which I use for
work) has burst all its graphic power, I don't
** Description changed:
- This error occurred on my PC when booting Ubuntu from 22.04 in any
+ This error occurred on my PC when booting Ubuntu from 22.04/24.04 in any
flavor, in Zorin and also with Pop!_OS 22.04.
Looks like a new kernel issue. It seems to me that it has to do with
Kernel
Public bug reported:
I tried 24.04 on a Nvidia 4090 and It only booted on safe graphics mode,
I haven't had this issue with any other Ubuntu previous versions on the
same computer.
A lot of people with other NVIDIA cards are complaining about this on
YouTube, please release an URGENT ISO with a n
Public bug reported:
This error occurred on my PC when booting Ubuntu from 22.04 in any
flavor, in Zorin and also with Pop!_OS 22.04.
Looks like a new kernel issue. It seems to me that it has to do with
Kernel 6.5, 6.8 +.
Should I be worried about this?
The problem does not occur in Fedora 39 o
It's unbelievable that this single package can broke your system and
that this bug has been unresolved for seven years
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717878
Title:
gdm3/gdm-session-w
1 - 100 of 4825 matches
Mail list logo
