Public bug reported:
[Availability]
Available on all archs, new package in eoan.
[Rationale]
We are supporting and pushing ZFS on root as an experimental option for 19.10.
Through the installer, people will be able to enable that experimental feature
and install ZFS on root.
ZFS itself has
This can be closed. The changelog has been rewritten apparently and so,
didn't have the stenza on this fix, but it's in 2.04-1ubuntu2.
** Changed in: grub2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Reopening, this isn't in ubuntu yet.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on
** Bug watch added: Github Issue Tracker for ZFS #8833
https://github.com/zfsonlinux/zfs/issues/8833
** Also affects: zfs via
https://github.com/zfsonlinux/zfs/issues/8833
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Description changed:
- # zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
- # zfs create rpool/ROOT -o canmount=off -o mountpoint=none
- # zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
- # zfs create
** Description changed:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create
** Description changed:
-
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create
Public bug reported:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O normalization=formD
-O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create
This is committed in the grub ubuntu packaging branch, waiting for the
next release handled by the foundation team (due to a FTBFS to debug +
merge)
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
** Also affects: python-pygraphviz (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: python-pygraphviz (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: python-pygraphviz (Ubuntu Disco)
Importance: Undecided
Status: New
** Also
Thanks for confirming!
After deep analysis, the best path is to rewrite a critical part of the
logic in shell it seems. At least, you are unblocked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok, found the issue. I think if you followed the zol ubuntu
administration guide
(https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), which
is only using a debootstrap, you are using mawk and not gawk, which is
why the regexp don't match and find your kernel.
Traditional ubuntu
Thanks for the results!
Can you run "zfs get all bpool/BOOT/ubuntu" please?
I'm a little bit puzzled about this line:
bpool/BOOT/ubuntu 121M 246M 120M legacy
legacy means you have a manual mountpoint set on this dataset. How do you mount
it? Can you paste your /etc/fstab (I guess you
case for it.
Also, the output of update-grub would be excellent to ensure there was
no failure.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification becau
** Also affects: ubuntu-report (Ubuntu Bionic)
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/1833555
Title:
Add OEM->Family
To manage notifications
Thanks for keeping us posted Christian :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833040
Title:
virt-manager fails to show virtual console: internal error: unable to
execute QEMU command
Public bug reported:
This bug is similar to
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1747442, but
since latest libvirt 5.4.0-0ubuntu1 hit Eoan, it reappaerred.
It seems a new syscall is made by this version of libvirt, with the apparmor
profile denying it:
juin 17 09:56:35
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Description changed:
As per iso testcase the screen-reader is supposed to be auto activated
if the user enabled it when installing. This is not the case in the ISO
(5oct2018)
+
+ Note: as of 19.04, the user session has the screen reader enabled, GDM
+ though hasn't.
ProblemType:
Public bug reported:
After installing 19.04 (16/04/2019 image) and enabling in isolinux screen
reader:
- screen reader is active in live/install session
After installation:
- screen reader is NOT active in gdm, when picking up user
- screen reader is active in user session
screen reader should
Public bug reported:
With the default configuration (nothing changed), I see in the
development version of ubuntu (disco) that unattended-upgrade is now
updating every package first thing after boot.
As you can see below, it didn't update packages from the security
pocket, but all packages in
Let's turn those as incomplete to get off the list until we get over
them again (probably next cycle).
** Changed in: gupnp-av (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See https://bugs.launchpad.net/ubuntu/+source/libayatana-
appindicator/+bug/1770146/comments/14. This is still invalid. Please
don't reopen without a new rationale.
** Changed in: libayatana-appindicator (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
on the autopkgtests question, I guess some for each components will be
good to have a finer grained migration prevention. (even if those are
testing the same thing, duplicated between packages).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Let's turn those as incomplete to get off the list until we get over
them again (probably next cycle).
** Changed in: gupnp-dlna (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please set it back to New once the MIR team can have a look at it.
** Changed in: xdg-dbus-proxy (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811824
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
MIR: mesa-vulkan-drivers FFE: install by default
To manage notifications
Public bug reported:
We are calling lb_chroot_archive in lb_chroot_layered only for the root
pass(es):
- we wait all passes to have the same archive snapshot, and avoid apt update &&
apt full-upgrade between passes (which may be repercuted on every children
pass).
However, one issue with this
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823301
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia] All on screen
-> 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia] All on
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to 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.
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815550
$ ./change-override -c main -t vulkan-loader
Override component to main
vulkan-loader 1.1.101.0-2 in disco: universe/libs -> main
Override [y|N]? y
1 publication overridden.
$ ./change-override -c main libvulkan1
Override component to main
libvulkan1 1.1.101.0-2 in disco amd64:
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 don't expect high regression potential from the lib and the database itself,
as those are only metadata passing around and new functions won't be used.
It's also easily revertable as long as we don't upgrade GNOME Boxes.
--
You received this bug notification because you are a member of Ubuntu
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
Public bug reported:
GNOME Boxes is requiring recent libosinfo updates. The latter needs a
recent release of osinfo-db for the tests to pass, which has latest
data, but almost small features like autoinstall on ubuntu (via seeds).
Note that we don't install Boxes by default, and having an up to
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/?id=5353c36718d103c8f8939a54a027104cadc1c8d5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220950
Title:
[MIR]
$ ./change-override -c main open-vm-tools-desktop
Override component to main
open-vm-tools-desktop 2:10.3.5-8 in disco amd64: universe/admin/extra/100% ->
main
open-vm-tools-desktop 2:10.3.5-8 in disco i386: universe/admin/extra/100% ->
main
Override [y|N]? y
2 publications overridden.
--
You
I'll try looking at it again tomorrow. I tried multiple combinations
yesterday and no luck so far…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812683
Title:
rhythmbox crashes when trying to play
** Summary changed:
- UIFe for late GNOME 3.32 icon name changes
+ GNOME 3.32 icon name changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820767
Title:
GNOME 3.32 icon name changes
To manage
I confirmed that 3.32.0 + trunk commits fixes the crash.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819126
Title:
Ok, after some more testing with new GNOME Shell (3.32.0 + some commits
backported), the situation has now improved when this case happens:
- there is no more icons for applications not having any appinfo, like the
update-notifier one.
- applications with appinfo have an icon with a decent size
signee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubiquity (Ubuntu Disco)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818890
Title:
[
Needs to be retested with G-S 3.32 which fixes the crash
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126. Test case
is:
1. sleep 1000 on one terminal
2. kill -SIGSEGV $(pidof sleep)
-> wait for update-notifier to try showing up apport (application crash) or
update-notifier
The snaps were never published in the manifest in "flat" images:
https://forum.snapcraft.io/t/no-more-preinstalled-snap-on-ubuntu-19-04/10339/7.
However, adding them is trivial and I can handle it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The .manifest issue isn't a regression: see
https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/1819287/comments/4. However, this is valid and could be
added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
GNOME Shell freeze and crash if appindicator can't lookup an icon. A lot
of messages are spawned in the logs:
Feb 20 15:40:46 neutrino gnome-shell[2735]: message repeated 2 times: [
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4575]
Feb 20 15:40:46
This is merged and released
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798612
Title:
OSD shows volume level =
I think this is fixed with newer Byobu (at least the LTS version).
Please reopen if not.
** Changed in: byobu (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gupnp-av (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785629
Title:
[MIR] gupnp-av
To manage notifications ab
** Changed in: rygel (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786489
Title:
[MIR] rygel
To manage notifications about this
** Changed in: gnome-shell (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722886
Title:
Include logs, monitors.
** Changed in: gupnp-dlna (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785649
Title:
[MIR] gupnp-dlna
To manage notificati
** Changed in: gupnp (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799974
Title:
[MIR] gupnp
To manage notifications about this
** Changed in: gssdp (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799977
Title:
[MIR] gssdp
To manage notifications about this
Code and packaging looks good. Nothing to worry about. Are we promoting
all binaries, or only the lib? (and let the -dev, gir and tools in
universe).
One thing to fix though (I'm happy to not block and require a new upload if
this is comitted in salsa):
* debian/copyright isn't up to date and
Updating the status to fix committed thus, after doko's and Leonidas'
feedbacks.
** Changed in: libnfs (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey!
I think the issue is on LXQt and desktop detection itself. It should
honor "StartupWMClass=" and not rely only on the binary which is ran
(which is gnome-terminal, hence the confusion for this desktop).
I'm unsure though which LXQt component is handling desktop detection.
Feel free to
I think Daniel was clear by changing to verification-done that this can go in.
We are talking about a less than a second flash, while blocking a bunch of
fixes for GNOME Shell in cosmic. Note that this second flash already existed
before the fix, and that the fix is correct, it will only be
Ok, so to sum up, remaining work to do:
- Add multi-arch to the libs
- (optional) Run as autopkgtests to ensure vala doesn't break this build
Once the above is addressed (multi-arch), +1 from the MIR team.
I think the security team can start right now reviewing this package and the
rdepends.
--
ack for me, seb told me he would take care of the tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803230
Title:
[MIR] teckit & xxhash, new rdeps of texlive-bin
To manage notifications about
Thanks! Do you mind listing the exact binary package list which should
then be promoted?
Agreed with you on the autopkgtests. This could have helped if vala were
to regressed the lib build, but unsure this is really needed as a
separate autopkgtests.
So, +1 for me, the security team should feel
Thanks! Do you mind listing the exact binary package list which should
then be promoted?
I would have appreciated the simple nitpick to be fixed while you were
fixing the other issues, but as said, not a requirement…
Agreed with you on the autopkgtests. This could have helped if vala were
to
Hey Gunnar,
After reorganizing the seeds for ubuntu desktop and see which strategy
we are going to take for the new installer (negative layered langpacks,
I can expand on this a little bit later), I think we have a robust story
to avoid the unsync we have between language-selector and the
Uploaded 2.2.9-2, hopefully fixing the debci test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803149
Title:
Update to 2.2.9
To manage notifications about this bug go to:
There isn't a bionic.xml file in bionic (I think the release has been cut a
little bit earlier), and so, any unknown vm -> 2GB of RAM, which is why we
didn't see the issue there.
However, there is no hurt in having this backported if anyone has time to do it
:)
--
You received this bug
I don't have the time to do a testround again, but I can give pointers
for whoever has time to have a look:
The patch is
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb,
in particular:
systemBackground = new
Are you sure it's differently? Look at the diff, it's supposively
exactly the same values than Yaru. Please check it and revert the status
as needed.
** Changed in: gnome-shell (Ubuntu Cosmic)
Assignee: Didier Roche (didrocks) => Daniel van Vugt (vanvugt)
--
You received this
Setting it as Won't fix then for cosmic.
** Changed in: yaru-theme (Ubuntu Cosmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799217
Title:
[SRU] Really
The best way to get it fixed is to be able to disable mod extensions,
which is something I'm working on, and you can follow it on
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2. This will
probably be for dingo.
--
You received this bug notification because you are a member of Ubuntu
People complained upstream that no GTK2 variant was there. Visually
impaired should still use the accessibility highcontrast profile as they
won't have good support with the default theme (Shell for instance has a
lot of white elements).
There are instructions though on the github project on
Setting as incomplete until I hear back.
** Changed in: vulkan-loader (Ubuntu)
Status: New => Incomplete
** Changed in: vulkan-loader (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
I would like the rationale to be updated to reflect what will be
promoted from vulkan-loader, please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742711
Title:
MIR: vulkan-loader
To manage
** Changed in: gupnp (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799974
Title:
[MIR] gupnp
To manage notifications about this
** Changed in: gssdp (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799977
Title:
[MIR] gssdp
To manage notifications about this
* There are a lot of crash reports in launchpad. Those are several years old
and shouldn't apply anymore. Maybe a little bit of cleanup of really old one,
and looking at more recent ones will help once supported to review real new
crashes (between launchpad and errors.ubuntu.com)?
* What is
Tests are actually ran during package build (but one is skipped, as it
needs a more complex setup). So, good in that regard. Should it ran as
autopkgtests though?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tests are actually ran during package build. So, good in that regard.
Should it ran as autopkgtests though?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785629
Title:
[MIR] gupnp-av
To manage
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
Thanks for opening this bug and help making ubuntu better.
Indeed, the bug is in Dash to Dock itself, do you mind reporting it
upstream? https://github.com/micheleg/dash-to-dock/issues
I checked that maybe theming could workaround this, but I think it's
better to directly get it fixed upstream
I tried with gnome-3-26-1604 rev 74 is still slow fo me at first gnome-
calculator application startup (with no ~/snap)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794951
Title:
Calculator
ish includes 'Yaru-dark', which is
not complete (it lacks of gtk2 folder).
Note, as discussed on IRC, in order to support applications that prefer
dark variant, /usr/share/themes/Yaru/gtk-3.0/gtk-dark.css is enough
** Also affects: yaru-theme (Ubuntu Cosmic)
Importance: Low
Assignee: Did
** Summary changed:
- Yaru-dark packaged even if not complete, nor necessary
+ [SRU] Really don't ship Yaru-dark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799217
Title:
[SRU] Really don't
I guess dh_translations was written by Martin long before dh(1) came in,
and that's why it had its own euristic to determine the current build
system. This has never been revisited because the maintainance on this
package is low.
I agree though that it should have both systems:
- one for dh(1)
Yeah, sorry that we had different terms for the same things :) Ok, I
understand now as well. I'm trying to look at this whole thing globally
and not from the technical split (which is a little bit artificial) that
we did.
> Please note that the language-options script serves the purpose of
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/357609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798747
Title:
Ticks in
501 - 600 of 16202 matches
Mail list logo
