Public bug reported:
When a user is logged in to the Ubuntu desktop, a power button event
will cause the user to be prompted to choose if they'd like to proceed
with a shutdown. However, if the system is sitting at a greeter screen,
a power button event will instead attempt a suspend w/o prompting
On Tue, Nov 10, 2020 at 7:45 AM Sebastien Bacher
<1902...@bugs.launchpad.net> wrote:
>
> is it important enough to justify doing the SRU work?
>From my myopic (server-oriented) point-of-view, changing the default
in 20.04 to prompt is a good idea. I've found that users often install
Ubuntu Desktop
The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so
@Naresh: see my comment #4, asking if you are running Ubuntu Desktop.
dmesg doesn't tell me that - but an sosreport would, if you can attach
that.
We've recently hit this on an x86 server, and did tie that back to the
system having a desktop installed (Nvidia CUDA 11 somehow brings in gdm
as a dep
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu
overrides the GNOME default of auto-suspending, but that override only
takes effect if you have the ubuntu-settings package installed. I tested
this out on a Saber system, and I can confirm that it does seem to only
happen whe
gdm3 is being pulled in via a "Recommends" chain. Disabling recommends will
avoid it[*].
On my groovy system it reduced new packages installed from 452/291MB of
archives to 56/165MB of archives. Seems like the right thing to do for at least
--gpgpu installs - but maybe for all?
[*]
--- /usr/bi
Public bug reported:
On an Nvidia DGX2 system running bionic w/ ubuntu-drivers-common
1:0.5.2.5:
$ sudo ubuntu-drivers list --gpgpu
nvidia-headless-no-dkms-450, (kernel modules provided by
linux-modules-nvidia-450-generic)
nvidia-headless-no-dkms-460, (kernel modules provided by
linux-modules-n
** Attachment added: "sosreport-akis-2021-03-22-hgypyvd.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1920791/+attachment/5479223/+files/sosreport-akis-2021-03-22-hgypyvd.tar.xz
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
Today I noticed that the software manager is telling me there's a juju
update available (2.7.1), with an option to update. When I click update,
it says "Unable to update juju: snap has no updates available". Sure
enough, `snap info` confirms that I'm already on 2.7.*2*:
chann
I suspect it did autorefresh, but didn't confirm. But yeah, the issue
IMO is the UI one. Once I click update, I'd expect gnome-software to see
that it was already up to date and respond as though the update was
complete - i.e., go away :)
--
You received this bug notification because you are a me
Verified - I do now get the prompt! Thanks laney & didrocks!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-s
Public bug reported:
I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
included a change that dropped a number of transitional packages:
mesa (23.1.4-1) unstable; urgency=medium
[ Diederik de Haas ]
* Drop transitional libegl1-mesa package (Closes: #1032712)
* Drop transiti
Public bug reported:
When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attempt to "switch to" a n
** Attachment added: "_usr_bin_gnome-shell.1002.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015386/+attachment/5661328/+files/_usr_bin_gnome-shell.1002.crash
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificatio
I need to deploy the machine from scratch each time I access it, so I
won't be able to run that command in the same install. I tried
reproducing again from scratch, but this time "switch user" immediately
aborted w/o generating a gnome-shell crash. I'm not sure what was
different - I do know that t
Public bug reported:
Split out from https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2015386/comments/9 .
I'm using the nvidia 525-server drivers.
When I create a new user, then attempt to "switch to" that user from
another user's GNOME session, the new session immediately aborts and
I reset all the relevant packages back to the versions used when I
originally filed this bug (luckily I stashed an sosreport), and I was
able to reproduce.
https://errors.ubuntu.com/user/b18128bc669a4a4d1f371a58f4f5d719833ab52c5ab794dbbc9d9e55b45d12516efcc5085f9d93e4d219bc6948f530cdaa31ddf8e34b7e9
Attached
** Attachment added: "_usr_bin_gnome-shell.1001.crash"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+attachment/5663851/+files/_usr_bin_gnome-shell.1001.crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
The .crash file from comment 11 has been submitted via ubuntu-bug in bug
2016299 - I'll leave it to the developers to determine which one should
be the dupe.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.l
I could not reproduce with kinetic (see my steps in bug 2016193). I went
back to a clean jammy install, reproduced, then upgraded just the gdm3
packages to kinetic's versions, and the problem went away, so it seems
gdm3 in isolation is the relevant difference. I took a look at the
differences betwe
Upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/808
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #808
https://gitlab.gnome.org/GNOME/gdm/-/issues/808
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/-/issues/808
Importance: Unknown
Status: Unknown
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1991553
Title:
can't add a p
I found that this issue also impacts upstream kernels, so I bisected and
found that the problem was introduced in this commit:
commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2
Author: Thomas Zimmermann
Date: Thu May 7 11:06:40 2020 +0200
drm/ast: Don't check new mode if CRTC is being disabl
** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz
--
You received this bug notification because you are a member of Desktop
Packages, wh
On Thu, Jun 1, 2017 at 7:27 AM, Zhanglei Mao wrote:
> Daniel,
>
> It is really good. For patch driver and new kernel buiding, I cc Dann on the
> mail too, he is our engineer for this enablement project with Hisilicon.
> This is pearl kernel was build by him too.
>
> Dann,
>
> Can you patch and bui
This was brought to my attention on the Linaro cross-distro list:
http://lists.linaro.org/pipermail/cross-distro/2014-December/000765.html
** Bug watch added: Mozilla Bugzilla #1050258
https://bugzilla.mozilla.org/show_bug.cgi?id=1050258
** Also affects: firefox via
https://bugzilla.mozil
Public bug reported:
I reproduced by:
1) starting firefox on an armhf system
2) browsing to http://us.archive.ubuntu.com
3) right clicking on the "folder" image, clicking "Save Image As..."
4) then selecting a folder.
ubuntu@hb06-22:/tmp$ firefox
(process:23506): GLib-CRITICAL **: g_slice_set_
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1398898
Title:
[armhf] segfaults when trying to save a file
Status in
I've verified that the upstream patch applies cleanly to firefox in
trusty, and that it does resolve the problem.
** Patch added: "tested patch w/ dep-3 headers"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1398898/+attachment/4273747/+files/armhf-xpcom-correct-argument-passing.patc
29 matches
Mail list logo
