libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute amd64:
universe/libs/optional/100% -> main
libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute arm64:
universe/libs/optional/100% -> main
libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute armhf:
universe/libs/optional/100% -> main
*** This bug is a duplicate of bug 1894329 ***
https://bugs.launchpad.net/bugs/1894329
** This bug has been marked a duplicate of bug 1894329
ZFS revert from grub menu not working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** No longer affects: zsys (Ubuntu Bionic)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1897565
Title:
[SRU] Persistent dataset print strangely
Status in zsys package in Ubuntu:
$ ./change-override -c main -S golang-github-openprinting-goipp
Override component to main
golang-github-openprinting-goipp 1.0.0-1 in groovy: universe/misc -> main
golang-github-openprinting-goipp-dev 1.0.0-1 in groovy amd64:
universe/devel/optional/100% -> main
** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
** No longer affects: zsys (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notificat
** Changed in: libgweather (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update libgweather to 3.36.1
I reapplied your debian/changelog directly and pushed to focal (pending
approval). Thanks a lot!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update
Hey Amr and thanks for making ubuntu better.
Do you mind double checking your patch?
Trying to apply it on 3.36.0-1, I get those chunks failing to apply
(tried both your .diff and .diff.gz):
patching file debian/changelog
patching file libgweather/gweather-weather.c
patching file
** Also affects: zsys (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: zsys (Ubuntu)
Importance: Undecided => Medium
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Did
Public bug reported:
[Impact]
* When running When I run zsysctl show --full, the output of persistent
datasets is garbagled, like:
Persistent Datasets:
- &{rpool/usr/local %!!(MISSING)s(bool=false)
{/usr/local on %!!(MISSING)s(bool=true) %!!(MISSING)s(bool=false)
Public bug reported:
[Impact]
* People having personal layout, like a persistent dedicated dataset under
/boot like /boot/grub will get it unmouted after a state revert.
* Side effects:
- those datasets are never marked as being part of the current machine, or
any state.
- bpool and
se of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: flatpak (Ubuntu)
Assignee: Didier Roche (didrocks) => Ubuntu
or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: ostree (Ubuntu)
Assignee: Didier Roche (didrocks) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a memb
Robert, you didn’t get desktop-packages subscribed again, mind doing so
before resetting to NEW and assigning? Thanks!
** Changed in: ostree (Ubuntu)
Status: New => Incomplete
** Changed in: ostree (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received
This was fixed in zsys 0.4.6.
** Changed in: zsys (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1883887
Title:
Focal installer destroyed
Public bug reported:
Tried with both manufacturer and gutenprint driver:
1. plug an epson stylus photo rx560 via usb
2. add the driver (manufacturer first, retried with gutenprint) autodetected
our gtk ubuntu specific application.
3. Tried to print with multiple apps: the task is queued and
Please run apport-collect to attach logs so that we can debug your setting.
@baling: why subscribing zsys to this bu? There is no mention of zsys being
used here, it seems directly a manual zfs setup.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification
*** This bug is a duplicate of bug 1886214 ***
https://bugs.launchpad.net/bugs/1886214
** This bug has been marked a duplicate of bug 1886214
zsys package post-installation failed when boot pool is not imported
--
You received this bug notification because you are a member of Desktop
Public bug reported:
[Impact]
* People start experiencing /boot and disk near being full due to our snapshot
policy.
* Until we implement GC pressure based on disk space, mitigate the issue by
only keeping last month.
[Test Case]
* Install new ZSys version
* zsysctl show
-> You should see
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu)
Importance: Undecided => Medium
** Changed in: zsys (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Did
** Changed in: zsys (Ubuntu)
Importance: Undecided => Low
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu Focal)
Importance: Undecided
tu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1875420
Title:
zsys causes apt install to output a confusing message
Status
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (
with traditional ext4 system
+ running ubuntu kernel and installing ZSys, as this was already handled.
** Changed in: zsys (Ubuntu)
Importance: Medium => Low
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Also affects: zsys (Ubuntu Focal)
Impo
** Changed in: shadow (Ubuntu)
Importance: Undecided => Medium
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Also affects: shadow (Ubuntu Focal)
I
other states unlinked as well)
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu)
Importance: Undecided => High
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
ht
having a lot of datasets or in code
path we didn’t optimize yet.
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu Focal)
Importance: Undecided => High
** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (di
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu Focal)
Importance: Undecided => High
** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification becau
Sorry Colin, this was ZSys and I targetted the wrong component when
filing batch-bugs for ZSys 0.5 upload.
Fixed in https://launchpad.net/ubuntu/+source/zsys/0.5.0.
** Package changed: zfs-linux (Ubuntu) => zsys (Ubuntu)
** Changed in: zsys (Ubuntu)
Status: Incomplete => Fix Released
--
Public bug reported:
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully
zsys unlinked user state (with every other states unlinked as well)
** Affects: zsys (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
>From the log:
mai 12 09:41:27 casanier zsysd[48398]: gdm
mai 12 09:41:27 casanier zsysctl[48826]: level=error msg="couldn't save state
for user \"gdm\":user \"gdm\" doesn't exist"
mai 12 09:41:27 casanier systemd[2480]: zsys-user-savestate.service: Main
process exited,
Public bug reported:
autotrim should be enable and people upgrading should have trim enabled
to prevent performance degration on SSD over time
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Public bug reported:
When building other machines or when listing after a revert system
states, ensure we present the correct order (snapshots taken on this
filesystem dataset should be before the filesystem dataset itself, as it
was used afterwards).
** Affects: zsys (Ubuntu)
Importance:
Public bug reported:
/etc/apt/apt.conf.d/90_zsys_system_autosnapshot is still installed and
try to execute /usr/libexec/zsys-system-autosnapshot on apt
install/remove/upgrade which then prints an error (but didn’t fail
thanks to || true).
** Affects: zsys (Ubuntu)
Importance: Undecided
** Summary changed:
- Collect unmatched bootfs-datasets on all userdata
+ Collect deleted users
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in
The ZSys part of the issue (garbage collection not being agressive
enough when reaching bpool or rpool size limit) is handled on bug
#1876334.
I’ll just add a reference there and remove the ZSys task instead of
dupping so that the foundation team can handle the grub side of it.
** No longer
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2716
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
Importance: Unknown
Status: Unknown
--
You received this bug
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2715
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
Fresh install of 20.04 LTS with nvidia binary driver from our archive.
(dual Intel/Nvidia setup)
No setting change has been done. The card supports "On demand".
Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing
the same result:
- default launch
Public bug reported:
I think the menu should rather be a checkbox which pins/unpins using a
dedicated card option. That way, people can always launch, for instance,
their browser with nvidia hardware acceleration for instance.
Something to discuss upstream of course.
ProblemType: Bug
Public bug reported:
Once you select manually performance mode in nvidia-settings, GNOME
Shell shouldn’t display "Use dedicated card option".
Launching directly any app, in this mode, starts your application using
the nvidia card already.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
The client can timeout while the daemon is still doing a lot of active
work.
There are 3 cases to take into account:
- daemon not started: give a timeout for the daemon to start before the client
exits. Ideally, we would pulse back to the client, but the entrypoint isn’t
Thanks for your suggestion!
Actually, zsys does it a little bit differently:
- snapshots (state save) are taken everytime you modify your system by apt or
other things.
- In addition to this, everytime you reach graphical.target, we stamp the
current state (which can also be a clone) as the
** Package changed: zsys (Ubuntu) => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1874191
Title:
Brightness setting too high
Status in
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
Public bug reported:
There is no more zsys integration for this part of the stack.
Fix regression from disco due to useradd merge with debian.
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
** Changed in: zsys (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1871576
Title:
apport hook test 2
Status in zsys package in Ubuntu:
Invalid
** Changed in: zsys (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1871550
Title:
Bug with apport report
Status in zsys package in Ubuntu:
Public bug reported:
Test 2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture:
Public bug reported:
Test bug with apport content
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
** Changed in: ubuntu-report (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1870084
Title:
ubuntu-report ftbfs in focal
Public bug reported:
Two kind of datasets we should collect in the GC:
- root and children datasets if reverting failed (initramfs cloned -> failed in
generator)
- states that don’t have a valid LastUsed
To evaluate:
- main dataset for a machine is never cleaned up, so ok
- only consider (and
Public bug reported:
Similar to https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870052,
the source can be "" for canmount. It seems to happen on swap dataset.
We should evaluates what we consider it (maybe inherited to avoid
setting it)
** Affects: zsys (Ubuntu)
Importance: Undecided
Public bug reported:
Untag them as part of GC so that we can clean them up later
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Run that as part of GC so that we can clean them up later
+ Untag them as part of GC so that we can clean them up
Thanks for your bug report! This is now fixed in zfs-linux
0.8.3-1ubuntu10 in focal.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Public bug reported:
This is a valid source that we should consider "inherit".
Example in log: https://github.com/ubuntu/zsys/issues/62 and
https://gist.github.com/nirvdrum/67b9e496b215276538cbcf7bce6d3a4b.
The bet is that it’s the case when the pool itself doesn’t have any
mountpoint set. (and
Retargetting to correct project with tag
** Package changed: zsys (Ubuntu) => gnome-disk-utility (Ubuntu)
** Tags added: zfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
Public bug reported:
Sorry, I don't understand the way of this bug
came after update of the day
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libvte-2.91-common 0.59.91-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
Uname: Linux 5.4.0-20-generic x86_64
Hey BertN45,
as stated on the other bug report, those aren’t necessarily snapshots as
clones can be a state. Using the terminology snapshots will be confusing
like advanced users like you are.
Manual snapshots on system state saving won’t be considered as a valid
reverting state to zsys, as you
Closing right now as no new feedback report. Feel free to reopen if this
didn’t fix the issue.
** Changed in: zsys (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
Thanks for reporting this bug and help making ubuntu better.
The local cache (of software-updater) isn’t refreshed yet but will be
for the release. Note that the zsys command doesn’t exist since the
split is daemon (zsysd) / client (zsysctl).
Closing the zsys task of bug as invalid as there is
$ ./change-override -c main -S zsys
Override component to main
zsys 0.3.3 in focal: universe/admin -> main
zsys 0.3.3 in focal amd64: universe/admin/optional/100% -> main
zsys 0.3.3 in focal arm64: universe/admin/optional/100% -> main
zsys 0.3.3 in focal armhf: universe/admin/optional/100% -> main
tepl 4.3.1-1 in focal: universe/misc -> main
gir1.2-tepl-4 4.3.1-1 in focal amd64: universe/introspection/optional/100% ->
main
gir1.2-tepl-4 4.3.1-1 in focal arm64: universe/introspection/optional/100% ->
main
gir1.2-tepl-4 4.3.1-1 in focal armhf: universe/introspection/optional/100% ->
main
amtk 5.0.2-1 in focal: universe/misc -> main
gir1.2-amtk-5 5.0.2-1 in focal amd64: universe/introspection/optional/100% ->
main
gir1.2-amtk-5 5.0.2-1 in focal arm64: universe/introspection/optional/100% ->
main
gir1.2-amtk-5 5.0.2-1 in focal armhf: universe/introspection/optional/100% ->
main
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Bionic)
Assignee: Didier Roche (didrocks) => (unassigned)
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Cosmic)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification becau
Override component to main
fonts-urw-base35 20170801.1-3 in focal: universe/misc -> main
fonts-urw-base35 20170801.1-3 in focal amd64: universe/fonts/optional/100% ->
main
fonts-urw-base35 20170801.1-3 in focal arm64: universe/fonts/optional/100% ->
main
fonts-urw-base35 20170801.1-3 in focal
Promotion done.
Till, as ghostscript doesn’t need any promotion if I‘m correct, I let you close
the bug in the changelog for your corresponding ghostscript upload.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
Promoted
$ ./change-override -c main -t openjpeg2
Override component to main
openjpeg2 2.3.1-1 in focal: universe/misc -> main
Override [y|N]? y
1 publication overridden.
$ ./change-override -c main libopenjp2-7
Override component to main
libopenjp2-7 2.3.1-1 in focal amd64:
Rationale: this is a regression on X11 in eoan (maybe not worth fixing
for it right now), but at least, should be fixed in focal IMHO
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
- Open some non dbus activated apps (so, not terminal for instance) in your dock
- Kill the shell with SIGKILL
- Applications are being killed with the Shell being killed, apart from the
dbus activated ones.
This wasn't the case before 19.10 on X11. (caused by dbus user
** Changed in: zsys (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1850052
Title:
installing zsys breaks desktop login
Status in
** Description changed:
+ [Impact]
+ After installing zsys on 19.10, you can't log in in your desktop. Removing it
won't fix the issue.
+
+ [Test Case]
+ Test A: (migrating broken people)
+ 1. Install 19.10 using experimental ZFS disk partitioning and reboot on
installed system.
+ 2. sudo apt
zsys is handling this (adduser will try to execute it and creates a
dataset, and if it can't, it fallbacks to traditional directory
creation.
zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so
I encourage you to install and test it! Thanks :)
I'll have to mark the bug as
(The issue is only on grub, marking the other tasks as invalid and the
grub one as incomplete until we get feedback)
** Changed in: grub (Ubuntu)
Status: New => Incomplete
** Changed in: zsys (Ubuntu)
Status: New => Invalid
** Changed in: ubiquity (Ubuntu)
Status: New =>
@Daniel, however, this creates "interesting" issues, like when you have a
pulseaudio server on the network. Even if your laptop is connected before the
user session, it will always switch to the server, even if you reverted on this
decision at previous reboot.
However what I describe above
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Changed in: grubzfs-testsuite (Ubuntu)
Status: New =>
Public bug reported:
As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: zsys
Public bug reported:
Part of the zsys spec is creating/associating one user dataset for each
HOME user.
As zsys is an official experimentation for 19.10, we would like to
include this feature in a safe way, and reachable for any tool creating
users (adduser, gnome-control-center, ubiquity…).
This is a regression for our vast majority of users using the normal
ubuntu product and quite visible one, I wouldn't put it as low.
** Changed in: gnome-shell (Ubuntu)
Importance: Low => High
** Changed in: mutter (Ubuntu)
Importance: Low => High
--
You received this bug notification
Public bug reported:
GNOME Shell & mutter on 3.33.91
When pressing volume up or down on Xorg and keeping it pressed, only the first
key event is sent, so the volume only goes up or down once, and doesn't scale
up/down as long as you keep the button pressed.
ProblemType: Bug
DistroRelease:
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1833555
Title:
Add OEM->Family
Status
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-report (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-report (Ubuntu Disco)
Assignee: (unassigned) => Didier Roche
** Description changed:
[Impact]
- * Any new report after an installation in a Virtualbox machine won't
- show up CPU informations.
+ * Any new report after an installation in a Virtualbox machine won't show up
CPU informations.
+ * Note that we don't fix Cosmic: it's almost EOL and
** Description changed:
+ [Impact]
+
+ * Any new report after an installation in a Virtualbox machine won't
+ show up CPU informations.
+
+ [Test Case]
+
+ * Make a new installation in virtualbox
+ * Run "ubuntu-report show".
+ -> you won't have any "CPU" field in the output
+ * Install
** Also affects: ubuntu-report (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
The last screen shows a spinner which is frozen until the spinner is
replaced with snap content.
The only relevant error in the journal is:
avril 17 10:32:01 d-Standard-PC-Q35-ICH9-2009 gnome-initial-s[2055]: Failed to
get featured snaps: Failed to read from snapd
The
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
MIR: mesa-vulkan-drivers FFE: install by default
Status in mesa
here is the output (reenabled drm to get it back):
$ glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.116
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502
doesn't fix it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia]
FYI, this happens even without drm enabled and only on Xorg session.
Alt+F2 -> r fixes it until next reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
-> I'm using 2 monitors (1 internal and 1 external).
-> The nvidia GPU is enabled, monitor is plugged to it through HDMI.
-> The CPU usage of GNOME Shell spikes. There is no writed at the same time
(the led doesn't blink) and no other process seems to run for it. The memory
usages seems stable
** Attachment added: "cpu_mem.logs"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+attachment/5253048/+files/cpu_mem.logs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050
Mobile] (rev a1)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
Public bug reported:
Mutter is hanging for multiple seconds (5 or so) at random times, especially
when your user session starts and you open new applications from the launcher:
- the screen freeze (apps & Shell) completely
- you have a second cursor that you can move and refresh during that
s/upon/until
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia] All on screen text is tiny. Icons are normal size
but text is nearly unreadable.
Note that I'm seeing this with modeset=1 (nvidia):
- Shell UI has small text (and so, small panel and such…)
- icons and application have normal size
Going to g-c-c => displays scaling factor is at 100% (I never changed it before
on that machine). Going to 200% -> Apply. The text is giant. Then,
confirming. I'm seeing the same regularly.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
We need a decision if we SRU the workaround or not. After further
investigations, I still can't reproduce it.
There is nothing clear in the bindings and it seems people can reproduce it
without the plugin?
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Cosmic)
Status:
I have tried reproducing it both on disco (without the prevent-
reordering patch) and stock bionic with german locale installed.
I tried adding all available columns, reordering them, click on them. I
also imported some MP3 with altered metadata with umlaüt on each
category and retry the above
101 - 200 of 1496 matches
Mail list logo
