Public bug reported:
Title basically
oracular-preinstalled-desktop-arm64+raspi.img.xz
2024-10-07 20:21
9aaacf14e4d12bd59ac20ba07d34dbe6ad2dee14bc211947915d6b2b845af424
To reproduce:
Fresh "installation"
Connect any bluetooth headset or speaker
Play any youtube video (preferably music you're fami
I tried to reproduce this twice, but couldn't. I did a fresh xubuntu
22.04 install, and then upgraded the machine. I didn't experience this
bug, but I did get the following crash (attached)
** Attachment added: "_usr_bin_blueman-tray.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/pam/+b
I found this bug report after experiencing the same problem. The error
message I got was exactly the same as the one in comment #2. The fix
suggested by Kazuhiro in comment #9 fixed the problem.
I think that since this bug affects more than one person, it's not
merely a problem with one person's l
I've tested the proposed mesa + hwe kernel and as far as I can tell it's
working well. I believe my Z16 is navi 2nd generation and it has an iGPU
and dGPU both AMD (600M series and RX 6500 respectively). What I tested:
- firefox you tube videos (with both DRI_PRIME=0 and 1)
- steam deb running dot
.
The systemd experts who have looked at this bug, including correspondence
I've had with them outside of this bug report, indicate that the problem
with x2go and nomachine look like a missing PAM step in the login process.
I will upgrade my server soon to check it out
regards
TIm
On Tue, 7
Public bug reported:
The color profile set either via the Gnome Control Center or colord has
no effect in the Wayland session.
I tested it with Firefox and can see no difference no matter what color profile
is set in GNOME.
I also changed the color profile in Firefox via the about:config and tri
You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.
s.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>
--
Tim Richardson
--
You received this bug notif
gt; https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps:
ivers
snaps that work.
On Wed, 18 Oct 2023, 04:15 Janus Kobain, <1951...@bugs.launchpad.net>
wrote:
> Tim, this is a desktop installation of 22.04 LTS, I simply followed
> where package updates led me.
>
> After installing linux-generic-hwe-22.04-edge package:
> $ snap
ope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syst
I just did this with vanilla ubuntu with the ubuntu-release-upgrader
version from proposed and everything was fine - no wild font changes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.lau
I tested a lunar -> mantic desktop upgrade last night and did not
encounter the bug described here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037497
Title:
gnome-shell crashed with SIGSEGV at NULL from e
Not a release blocker.
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1923052
Title:
screen reader d
** Tags removed: rls-mm-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in ubu
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019939
Title:
Outdated documentation about Network
Public bug reported:
As discussed in this thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811
On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.
According to the discussion a fix has been implemented in kernel
v6.6-rc1.
If it's possible for Ubuntu to i
Has this been seen more recently than 18/08?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2031899
Title:
File system layers missing - unable to boot live cd Ubun
Looks like it's fixed in today's daily image ! Lovely stuff :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-en in
Ubuntu.
https://bugs.launchpad.net/bugs/2033377
Title:
New whitespace between digits a
Running `sudo dhclient -6 ` appears to work, the problem
seems to be with the systemd-networkd DHCPv6 client.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2025382
Title:
Public bug reported:
Ubuntu 22.04.2 LTS
kernel 5.15.0-1038-oracle
systemd 249.11-0ubuntu3.9
After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6
via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also
other similar reports, e.g.
https://ubuntuforums.org/showthr
erence to the problem.
I can't find any help resources about this problem.
by using
systemctl show -p FragmentPath snapd.service
I can find the file and edit it manually, as a workaround.
'
tim@vm1:/etc/systemd/system$ lsb_release -rd
No LSB modules are available.
Des
ile and edit it manually, as a workaround.
'
tim@vm1:/etc/systemd/system$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
tim@vm1:/etc/systemd/system$ apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3
Candidate: 252.5-2ubuntu3
Versi
Seeing the boot log from Simon McVittie (smcv), this is QEMU kvm
machine.
-> May 09 14:32:15 ubuntu kernel: DMI: QEMU Standard PC (Q35 + ICH9,
2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Also a colleague and me could replicate this behavior (With the same
virtualization platform, same disk imag
I'm now on Ubuntu 23.04 (incl. new kernel) and managed to make the bass
work on my Lenovo Yoga 9 14IAP7 through this trick:
https://wiki.archlinux.org/title/Lenovo_Yoga_9i_2022_(14AiPI7)#Audio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Nick - yes. It is a rented linux box.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2013543
Title:
systemctl daemon-reexec forgets running services and starts everything
this problem is annoying...
** Changed in: systemd (Ubuntu Jammy)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2013543
Title:
sys
Okay, ?th time lucky
** Patch removed: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669367/+files/mysuperpatch.debdiff
** Patch added: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attac
** Patch removed: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669357/+files/mysuperpatch.debdiff
** Patch removed: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files
Launchpad is failing when I try to add ubuntu-studio-meta to this bug
report, not sure why
** Also affects: edubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntukylin-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntustudio-meta
Please find attached updated debdiff
** Patch added: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669357/+files/mysuperpatch.debdiff
** Also affects: ubuntu-unity-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affec
Public bug reported:
update script handled debootstrap and devscripts, does not handle
germinate. also doesn't handle potential specified versions in the
package directory.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification bec
** Patch added: "mysuperpatch.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files/mysuperpatch.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubunt
After restoring to a functional backup we discovered that updating from
cloud-init 22.2-0ubuntu1~18.04.3 is the cause of the problem.
** Package changed: systemd (Ubuntu) => cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Filing for a friend:
I have several Ubuntu servers that all just quit working at the same
time. By “quit working” I mean they take forever to boot and
applications do not work on them correctly until after about 30 minutes
(and the applications have been restarted).
Nov 14
ease, inform us if you get the point.
>
> Thank you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap
e you do startx, and see if it is valid. I'm going
to guess that it is not. When I spent some time looking at this a few
months ago, I had the impression that this variable needs to be set
correctly before the gui session starts.
On Sun, 23 Oct 2022 at 07:40, Akkana Peck <1951...@bugs.launc
@mtu and make sure that systemd is properly installed, how you check this I
don't know.
On Fri, 21 Oct 2022 at 08:13, Tim Richardson
wrote:
> hi @mtu, in that case no confined snaps will work for you, which you are
> probably noticing. Something is wrong with your installation, I
https://bugs.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>
--
Tim Richardson
--
You received
Akkana, what login manager are you using with openbox?
On Thu, 20 Oct 2022 at 14:57, Tim Richardson
wrote:
> The problem was identified as the session not being established correctly
> in some instances, and those instances were 100% involved in non-mainstream
> session starts (nom
e session can't
enable this, what do you propose that snapd do about it?
On Thu, 20 Oct 2022 at 08:20, Akkana Peck <1951...@bugs.launchpad.net>
wrote:
> Tim, I'm not sure where you got that impression about remote desktops
> (re #55), but I'm the original reporter and I
This is not a snap problem. I don't think it is a problem with standard
Linux desktops either. The problem seems to be entirely reported for remote
desktop sessions,.somehow they have missed something modern systemd sets up
at login.
On Mon, 17 Oct 2022, 13:40 Daniel van Vugt, <1951...@bugs.launc
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided
This worked for me as well with an HP OfficeJet Pro 9025.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1973441
Title:
Printing does not work on Ubuntu 22.04 - cups-pki-inva
orks as expected.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this b
I have the same problem as Philipp Jungkamp and Clem Schum on the Yoga 9
14IAP7 on Ubuntu 22.04. Hope this can get fixed soon, thank you very
much to everyone who is involved!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to al
Now I think we should file upstream bug reports with x2go (which I don't
use) and nomachine and get some clarity on whether they are doing the
login in compliance with up-to-date
https://www.freedesktop.org/software/systemd/man/systemd-
logind.service.html
--
You received this bug notification be
I have been reading a bit more. I'm starting to form the impression that
this problem may originate from the way our various remote solutions are
logging in. They may not be doing it the proper modern login-systemd
way. This would mean that nomachine, x2go are both wrong.
--
You received this bug
And let us hope that someone who can fix it steps up and fixes it
properly because right now, ubuntu 22.04 and derivatives are unfit for
remote desktop deployments.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
I'm just an ordinary user trying to get this working and volunteering what I
learn, so bear that in mind. I have no real clue about what the problem is and
I still don't understand where in the session start process
DBUS_SESSION_BUS_ADDRESS is set and why we get a wrong value when starting
sess
PS I do not think this is a bug in snap. It is a bug with the way the
session is being setup. I don't know what the bug is, I have spend some
hours trawling through bug reports and following clues (I tried to be
useful). My "spam" on the snapcraft bug was a helpful note directing
readers here, beca
I do not have cgroups disabled, I reverted that earlier change. My fix
works with cgroupsv2, at least for my xfce4 session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/195
I added that to my ~/.profile and confined snap apps run now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not
for me and my xfce4 login, in a terminal this lets me launch snaps:
tim@ubuntu ~ $ export DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus"
tim@ubuntu ~ $ firefox
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
This is what I get in journalctl when trying to start firefox:
Jun 15 13:09:30 ubuntu dbus-daemon[7531]: [session uid=1000 pid=7528]
Activating service name='org.freedesktop.systemd1' requested by ':1.60'
(uid=1000 pid=8624 comm="/snap/bin/firefox " label="unconfined")
Jun 15 13:09:30 ubuntu dbu
... running systemd --user in a terminal window first, and then starting
the snap-store worked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run sna
I ran into this again, this time in a virt-man virtual ubuntu 22.04
guest connected to via virt-viewer --attach.
tim@ubuntu-virtio:~$ snap-store
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-b5b3e096-ebb3-4eca-b9d1-d07ca7028b22.scope/init.scope
is
Yes, based on your link this 'work around' disables new cgroups.
: "If for some reason you need to keep the legacy cgroup v1 hierarchy, you
can select it via a kernel parameter at boot time:
systemd.unified_cgroup_hierarchy=0"
however, it at least allows a working session.
on another point: thi
Please note that nomachine technical support provided me with a
workaround. It works, but I don't understand the implications. This
fixed the problem with xubuntu 22.04. The support notes says it works
for ubuntu 22. 04 as well
In my case I added the kernel setting to GRUB_CMDLINE_LINUX which was
I have this problem connecting with nomachine to a virtual xubuntu desktop.
I hoped that the solution here might have helped:
https://askubuntu.com/a/1310739/152287
but this script does not fix the problem, although it is active for me
(the new environment variables are present in my session, for
Same issue:
PanGPLinux-5.3.2-c3 broke after upgrade to Ubuntu 22.04
above solution from Fernando worked for me.
thanks @fru1z and @kelly-schoenhofen
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https:/
I see this in the xorg session in the flatpak firefox save downloads
dialog, for instance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1971112
Title:
File picker gets b
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy
discussion.
** Bug watch added: Red Hat Bugzilla #2072070
https://bugzilla.redhat.com/show_bug.cgi?id=2072070
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib
Public bug reported:
the error message is already when i start my computer
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools-core 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
ApportVersion: 2.20.11-0
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Cont
(... Ubuntu 21.10)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
Status in evolution-data-server:
Unknown
S
I used proposed-updates today to get the latest evolution, and contact sync
works again.
So 3.40.4-1ubuntu2 works. (amd64 arch)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.l
timedatedPASS
hostnamedPASS
localed-locale PASS
localed-x11-keymap PASS
logind PASS
unit-config PASS
storage PASS
networkd-test.py PASS
build-login PASS
boot-and-servicesPASS
udev PASS
root-unittest
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is
caused by the dep8 tests of the tested source or the kernel has yet to
be determined.
Testing failed on:
amd64:
https://autopkg
Also observed with impish linux-aws 5.13.0-1000.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943441
Title:
lxc: lxc-test-parse-config-file failure
Status in lxc package
@Gabriel
Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as
well.
linux-image-generic-hwe-20.04
5.11.0.27.29~20.04.11
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
Observed on bionic:linux-aws-5.4 5.4.0-1055.58~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 ker
Also let me know if you need me to test anything else before I restore
my machine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enab
OK tested. Kernel works, I'm getting sound from both speaker bar and
the bass speakers on the bottom. Thank you.
Is it possible to get the code for the driver so I can compile it into
my kernel source for my laptop?
--
You received this bug notification because you are a member of Ubuntu
Touch
I can test today, just have to install ubuntu again(its unusable on this
laptop do to outdated libinput). Will install shortly and test the
kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https:
Will the fix be able to be compiled as a module for any kernel?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enabled on Lenovo Yoga
do you think this is a patch to alsa or a kernel patch?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enabled on Lenovo Yoga 9i
Stat
You are awesome! I ran the script with Fedora 34 as well(no changes to
the kernel) and the speaker works perfect now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926
DAC1 - no sound
DAC2 - sound(only through the top speaker bar)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enabled on Lenovo Yoga 9
Not sure if it helps, but when i run speaker-test -c 5, all 5 channels
get sent to the speaker bar up top.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
This kernel also does not produce sound from the bottom bass speakers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enabled on Lenovo
Here it is.
** Attachment added: "alsa-project.org.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5498257/+files/alsa-project.org.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to al
I'm running fedora 34, but I'm more then happy to install ubuntu back
today and try these kernels if it will help resolve the issue. Just
need some time to get that done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-d
No sound comes out of the bass speakers. This is an issue with the c940,
c930 and yoga 9i. Not sure if the cause is the same on all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpa
Public bug reported:
Ubuntu 20.04.2 LTS
systemd 245.4-4ubuntu3.4
The system is configured to use LDAP via nsswitch.conf:
passwd: files systemd ldap
group: files systemd ldap
shadow: files ldap
gshadow:files
Using libnss-ldap 265-5ubuntu1. When logging in with ss
As far as I can tell at the moment this bug appears to have been fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872504
Title:
date modified is wrong for files
Dimitri, I note your comment #106 about secureboot patches upstream. If
I recall correctly, a linux security update came down through Ubuntu
Updater about the same time or just prior to the LTS 20.04.1 updates in
mid September. A number of issues with LTS 20.04.1 appeared following
two "batches" of
Additional observation: I've tried using Ubuntu LTS 20.04 download
images from July and August, selecting the option to install third party
drivers. These images worked flawlessly at the end of the summer. But
since the mid-September updates, even these earlier iso's of Ubuntu LTS
20.04 Desktop fai
With reference to post #132 above: If this is relevant to this issue
I also am experiencing problems with switching drivers for the device on
my systems that uses (or can use) a Ubuntu third party driver.
Specifically nVidia for the GeForce 940MX. Changing between nVidia
driver versions (all wi
This is my first post here so I apologize if this is not appropriate.
On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:
"Could not install initramfs-tools"
"The upgrade will continu
This is my first post here so I apologize if this is not appropriate.
On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:
"Could not install initramfs-tools"
"The upgrade will continu
The fix for 1872159 (spinning logo hang on startup) has allowed me to
turn the splash screen back on; and this error is not visible. I do,
though, encourage completion of the fix for it since it rears its head
when the splash screens have to be disabled.
--
You received this bug notification beca
I am seeing much better stability of the Ubuntu distro today. I am
working with a reinstallation from a 20.04.1 image from late August; I
loaded it about a week ago hoping to recover from the 4 bugs I've been
dealing with but still had problems. Today I ran Ubuntu Update AND went
back to the open s
This is still present with Ubuntu 20.04 and the latest XFCE & LightDM.
This is a major pain almost to the point of me wanting to switch back to
GDM & Gnome.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
ht
These bugs started with a Ubuntu update just prior to Sept 14 (see post
103 above). By the 14th, there were initramfs problems on startup and
the hang on spinning circle which forced hard power downs.
Then on Sept 24, more updates installed including updates to grub,
*nvidia drivers*, and some oth
I already used the daily image; and yes I got the (re)installation to
complete without crashing. BUT the freshly (re)installed Ubuntu system
remained unstable and therefore unusable due to other bugs that were
introduced or re-introduced by the two Ubuntu Updater packages pushed
out since mid-Septe
I should add that, in researching old posts on these issues, I gather
that nVidia driver(s) have been a factor; so note that the last Ubuntu
Updater package prior to all this did also include an update to the
nVidia driver package.
--
You received this bug notification because you are a member of
Sorry to say that I tried to install from images from both May and June
of this year, obviously 20.04. Both failed with the same crash. And,
like you, I need nvidia and other specific drivers.
Even if you can get past the crash, other changes that have been made since
mid-September are wreaking h
1 - 100 of 1451 matches
Mail list logo
