Thanks, is it doing it after a reboot? One theory could be that when the
session files on disk change then gdm doesn't refresh its index and
things get confused
** Changed in: gnome-session (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member o
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Daniel Axtens (daxtens)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714420
Title:
kernel oops - kvm guest started at boot time
To ma
The issue is that chrome/electron enable the use of indicators only
under Unity, they need to be fixed. The TopIcon code handles the legacy
systray but that's deprecated and being removed from GNOME and shouldn't
be used nowadays, the correct fix there is to make electron use
indicators in our sess
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714245
Title:
'Add to Favourites' should say 'Lock to Dock' o
It would also be a good idea to refresh our meta package before the
release of 17.10! I will try and prepare an upload later today.
** Also affects: ubuntustudio-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bug
Artful complete, setting up MPs to review for SRUs:
On Testing from the PPAs [1][2] it worked for me fixing the issue and
not wreaking other havoc.
MPs at [3][4]
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2935
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu
@Robie The ntpdate command has a test mode that does not attempt to set
the clock, which the sntp command lacks.
I've confirmed on multiple systems that the installation of ntpdate
prevents ntp from starting on boot, which IMO is worthy of fixing.
** Changed in: ntp (Ubuntu Xenial)
Status:
** Changed in: pdfsam (Debian)
Status: New => 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/1167469
Title:
PdfSam does not start - FATAL GuiClient Error
(java.lang.NoClassDefF
--- Comment From heinz-werner_se...@de.ibm.com 2017-09-01 03:17 EDT---
IBM Bugzilla Status -> Rejected.. see last comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712534
Title:
qemu-de
I have been using (x)sane with my 17.02 without a problem.
After upgrade to 17.10:
- my Xerox WorkCentre 3525 doesn't get detected (editing
/etc/sane.d/xerox_mfp.conf helps though).
- the XSane GUI closes after preview or scan with the following message "Not a
JPEG file: starts with 0x00 0x00"
I'm using a slightly different variant of this keyboard - Corsair Strafe
(without RGB; product ID is 1b15). I had more or less the same problem
(error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems
to work every time. I did a quick test - previously keyboard worked 5
out of 10 reb
Public bug reported:
Hi Folks
Problem:
system doesn't reboot/shutdown but *only* when the network configuration
is static (described below). When I change the network configuration to
dhcp, the bug doesn't occur.
The network configuration is set to static:
iface eth0 inet static
address my
** Changed in: gnome-shell
Status: Unknown => Confirmed
** Changed in: gnome-shell
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691676
Title:
Mouse cursor
Public bug reported:
No login prompt or anything on console after switch to runlevel 3/5 from
1
Step to reproduce
1) Make sure root password is set
2) login as root on console
3) `init 1` switch to runlevel 1
4) login again as root
5) `init 3` or `init 5` and no login or prompt
root@D05-2:~# ini
Similar issue:
Configuration file '/etc/default/rcS'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : ke
Additional observations (now someone's taken notice ;-) and I'm reminded
of it myself):
It affects Wayland sessions too. Not xorg-specific.
Affects suspend/resume cycle too, not just display-sleep.
It may not affect all QT apps. For instance, since reporting this bug
I've switched from Owncloud
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713472
Title:
linux-gcp: 4.10.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713468
Title:
linux-gke: 4.4.0-1029.29 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713465
Title:
linux-snapdragon: 4.4.0-1074.79 -proposed track
Hello leder,
Could you try with caps lock+space? Did the issue come after an upgrade?
Best regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656832
Title:
orca key, e. g. insert + space, is
@Piotr,
File a new bug, thanks!
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has trou
Looks like other distributions suffer from the same:
https://bugzilla.redhat.com/show_bug.cgi?id=1468986
** Bug watch added: Red Hat Bugzilla #1468986
https://bugzilla.redhat.com/show_bug.cgi?id=1468986
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'd just closed software updater when crash occurred.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623278
Title:
WebKitWebProcess crashed with SIGSEGV
To manage notifications about this bug go to
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713467
Title:
linux-aws: 4.4.0-1033.42 -proposed tracker
Public bug reported:
Description:Ubuntu 16.04.3 LTS
Release:16.04
What I did/expected:
Updating samba from version
2:4.3.11+dfsg-0ubuntu0.16.04.9
to
2:4.3.11+dfsg-0ubuntu0.16.04.10
What happened:
Update process threw error messages.
Steps to reproduce:
1. sudo apt update && sudo apt
** Description changed:
+ SRU Justifications:
+
+ [Impact]
+ Touchpad on Lenovo ideapad 320-14IKB does not work.
+
+ [Test Case]
+ After adding the ID to the elan_i2c driver, the touchpad works.
+
+
+ [Regression Potential]
+ Very low.
+ It only adds device ID to the driver, no functional cha
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
I attach a debdiff for sponsorship to refresh the Ubuntu Studio meta
package for artful.
** Patch added: "Refresh us-meta for artful"
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1698225/+attachment/4942218/+files/ubuntustudio-meta.debdiff
** Changed in: ubuntustudio-meta
** Description changed:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
What I did/expected:
Updating samba from version
2:4.3.11+dfsg-0ubuntu0.16.04.9
to
- 2:4.3.11+dfsg-0ubuntu0.16.04.10
+ 2:4.3.11+dfsg-0ubuntu0.16.04.10
What happened:
Update process threw error messa
I have the problem too. After the dhcp lease is expired the avahi-daemon
or something else doesn't renew the dhcp lease. It helps to request an
ip address manually:
# sudo dhclient
sudo dhclient enp3s0
Configure the lease time on your dhcp server to 86400 seconds (one day)
and it should help the
(a) is preferable obviously, but may not be quick happening
(b) will work ok. have tested a build locally with autotests build and run in
LXC against arftul
(c) need to do a test rebuild in a PPA for that, to confirm it works and no
regressions when building the old 16.12.3 version against new an
Public bug reported:
As per KDE bug: https://bugs.kde.org/show_bug.cgi?id=379404
Interface hangs indefinitely on "initiating session".
Version 16.12.3 seems so work ok.
This is resulting in package version 17.04.3 being stuck in -proposed
pocket for artful, as the 'testmaxima' autopackagetest i
Hi Mariusz,
as already written in the post 2 it is irresponsible to use a package
from the Experimental branch in a production system.
CU
Jörg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Patch in #11 tested by myself and Corey; full pass on tempest smoke
testing and unable to reproduce the problem using repeated "nova reboot
--hard".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/171425
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
Filed one freedesktop bug for this issue.
https://bugs.freedesktop.org/show_bug.cgi?id=102508
** Bug watch added: freedesktop.org Bugzilla #102508
https://bugs.freedesktop.org/show_bug.cgi?id=102508
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
Right after logging in to the Ubuntu desktop environment, a message like
the one in the attached screenshot appears. I researched the cause and
found several links (see [1] and [2] below) pointing to the cause: a
command in either .bashrc, .profile or /etc/profile.d outputs to
I ran the following test:
1. Boot your system
2. Select Xorg
-> Xorg session starts
3. Logout and select Wayland
-> Wayland session starts
4 Logout and select Xorg
-> FAIL: Wayland session starts
I'll try the other way around but it seems to confirm you theory that it works
on a fresh
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
Same question from me: We cannot possibly want to break a big percentage
of all scanners and MFC devices out in the wild.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
Public bug reported:
I was installing "pinta". I am using LINUX on a partition on Windows.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_6
Looking at the InstallationDate maybe it referers to another package
named "ROSETTA", a software for hydro-geological purposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714443
Title:
package s
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714443
Title:
package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
failed to install/upgrade: subpr
While I was testing builds on the hotfix fix suggested upstream:
https://www.redhat.com/archives/libvir-list/2017-September/msg00015.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714254
Title:
Public bug reported:
the bootloader seems to make problem.
It is saying that the file system is read only.bootloader may not be able to
load or boot the sytem
boot may fail
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-g
found the answer https://lists.ubuntu.com/archives/ubuntu-
desktop/2017-July/005054.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713607
Title:
gcin is not launched in ubuntu arful
To manage
no longer have the test hardware to verify the kernel in -proposed, but
I did verify that the commit in question fixes the problem (hence my
report ;)).
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a membe
Public bug reported:
After latest kernel upgrade to version 4.4.0-93 machine failed to boot
with message
Error 18: Selected cylinder exceeds maximum supported by BIOS
Selecting old kernel (4.4.0-92) it boots normally.
This is a virtual machine (kvm) running 16.04.3. Apport report attached.
(Cou
Can we know when the decision will be made?
Or is there a bug tracking this (using ibus or fcitx)?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706558
Title:
Japanese Input Method doesn't
It's enabled since v4.12, so it will work out of the box on v4.13.
Backport to v4.4 is no easy task and I doubt anyone really need this on
Xenial.
** Changed in: hwe-next/xenial
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
sweethome3d still wont work (Ubuntu 14/Ubuntu 16/Debian 8 Jessie):
me@ubuntu14:~$ sweethome3d
Java 3D: implicit antialiasing enabled
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f98a2aadf63, pid=62375, tid=140294035650304
#
# JRE version: Op
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=102508
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714178
Title:
Tri
** Changed in: hwe-next
Status: New => 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/1581711
Title:
024C:B723 Need support for Realtek Wifi card rtl8723bs
To manage notifications a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714282
Title:
Sorry
Public bug reported:
Hi,
Artful won't switch to building mesa against libglvnd, so it makes sense
to remove libglvnd from the archive for now. It should be added back to
BB soon after the archive opens.
Currently, it'll just conflict with the mesa libs and brings no joy.
** Affects: libglvnd (U
Hi Ader,
IMHO that is not a bug in Ubuntu but an upstream feature request.
Thou there are certain workarounds [1] already that might be better then
the | tee.
If really needed, having multiple screenrc files ready and pointing to
either one defining the outputfile is rather close to what you want
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.
This sounds like an upstream bug to me. If this can be confirmed as an
upstream bug (or actually feat
** Description changed:
After applying the latest update the Software-center now opens but still
has a problem.
For the Launch pad, software center, in Ubuntu 17.10 it reports this error
when trying to open it.
"Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown
Public bug reported:
gnome-shell doesn't respect hinting and subpixel order under Wayland.
Note that the Xorg session has the fix for this.
Check the referenced bug for screenshots and comparing with the gtk
renderer of decoration in the wired bugzilla bug.
More context on the IRC discussion at
** Tags added: artful gnome-17.10 visual-quality
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714459
Title:
Shell panel font is blurry under wayland
To manage notifications about this bug go to:
Public bug reported:
creepy sound, not so much, but quiet poor quality and some underruns
occur
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.
*** This bug is a duplicate of bug 1622991 ***
https://bugs.launchpad.net/bugs/1622991
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1622991, so is being marked as such.
I thank you for your report and your help to make Ubuntu better.
But for now I'll mark it incomplete until it is clear what the requested action
shall be.
Please feel free to set back to new when the clarification is provided.
--
You received this bug notification because you are a member of Ub
Hi Cody,
that would be a bug (feature request) against (upstream) overlayfs then right?
I wonder this being against "cloud-initramfs-tools (Ubuntu)".
Lets retarget the bug at overlayfs for now to discuss in that context (which is
the kernel package).
Or OTOH you meant to want us to consider pick
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => 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/1713473
Title:
linux-raspi2: 4.10.0-1017.20 -proposed tra
The X11 hinting itself is fixed in old version of G-S, closing thus.
Note that there is another issue under wayland, referenced in
https://bugs.launchpad.net/gnome-shell/+bug/1714459
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notificat
** Changed in: exo (Debian)
Status: New => 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/1425972
Title:
Firefox no longer supports -remote parameter
To manage notifications abou
Screenshot (Wayland on top and Xorg below)
** Attachment added: "wayland_vs_xorg.png"
https://bugs.launchpad.net/gnome-shell/+bug/1714459/+attachment/4942272/+files/wayland_vs_xorg.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
An error is shown after a boot process
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fluid-soundfont-gm 3.1-5
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
A
1 - 100 of 518 matches
Mail list logo
