Public bug reported:
I know I made a mistake somewhere during the course of attempting to
install the deepin desktop.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
.tm
Public bug reported:
I was installing a 3rd and final OS and the power cut out.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.
If the 16.10 theme could be backported to 16.04 that would be awesome
(since there are HiDPI displays shipping with 16.04).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bu
Ah, it looks like this was fixed for @2x displays in Ubuntu 16.10.
** Changed in: ubuntu-themes (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.laun
Attached is a full-res screenshot on a 4k pixel doubled display.
** Tags added: hidpi
** Attachment added: "widget-factory.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1638398/+attachment/4771379/+files/widget-factory.png
--
You received this bug notification because yo
I chatted briefly with Daniel Fore of elementary, and he provided some
more details.
In the elementary GTK theme, we use @2x assets for anything that cannot
be done via GtkCSS. This means we provide pixel-doubled assets:
https://github.com/elementary/stylesheet/tree/master/gtk-3.0/assets.
This ens
Public bug reported:
Ambiance appears to provide lodpi raster assets, which means all of
these bits of the theme are not rendered crisply on hidpi displays. It
would be best to redraw these assets with GtkCSS to enable crisp
interface scaling, or at least find a way to provide vector or 2x
assets.
Hi Robie,
I tried purging and reinstalling openssh-server, but that failed again
with the same error.
I then rebooted the machine and was able to then successfully run apt-
get -f install to fix the package installation. Subsequently re-
installing the package worked without a problem.
Perhaps
I upgraded from Vivid => Wily => Xenial. I had switched back to
upstart-sysv on Vivid but I noticed that the upgrade software reinstalls
the ubuntu-standard package (and therefore systemd-sysv) on upgrade to a
new release, so I had re-installed upstart-sysv after each upgrade.
--
You received th
Hi Robie,
I had the same problem occur this morning on a couple of server installs
running systemd-sysv, so I'm thinking it might not be an upstart-
specific issue. I rebooted one of the servers and was then able to
upgrade the package successfully. I haven't yet rebooted the other
server. Both
Public bug reported:
This is a crash report submitted from cli for bug 1579978
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Archi
I had no problems installing the upgraded packages after switching from
upstart-sysv to systemd-sysv on the affected machines.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/
** Description changed:
This package upgrade failure has occurred on multiple machines, with the
same error on each machine. All affected machines are running Upstart
- as /sbin/init. The package installed/updated successfully on a machine
- running Systemd as /sbin/init.
-
- The affected m
Public bug reported:
This package upgrade failure has occurred on multiple machines, with the
same error on each machine. All affected machines are running Upstart
as /sbin/init. The package installed/updated successfully on a machine
running Systemd as /sbin/init.
The affected machines are als
Still a thing in Loki. Not sure if/how we want to work around it.
** Also affects: switchboard
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launc
*** This bug is a duplicate of bug 1390625 ***
https://bugs.launchpad.net/bugs/1390625
** This bug has been marked a duplicate of bug 1390625
mouse cursor gets corrupted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
*** This bug is a duplicate of bug 1390625 ***
https://bugs.launchpad.net/bugs/1390625
** This bug has been marked a duplicate of bug 1390625
mouse cursor gets corrupted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
*** This bug is a duplicate of bug 1390625 ***
https://bugs.launchpad.net/bugs/1390625
** This bug has been marked a duplicate of bug 1390625
mouse cursor gets corrupted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: xserver
Importance: Undecided
Status: New
** No longer affects: xserver
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1390625
Title:
mouse curso
Thanks everyone for the extra details. I'd also like to add that I've
experienced this in Ubuntu 14.10 on a 4th-gen Intel Core i5 and Intel HD
4600 graphics (System76 Sable Touch sabt3).
** Also affects: mesa
Importance: Undecided
Status: New
** Also affects: linux-kernel-headers
Imp
What would the appropriate Ubuntu project be for graphics or kernel
bugs?
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.la
This looks to be related to the 3.16 kernel and graphics stack. Users
who have manually upgraded their kernel or installed graphics drivers
from Intel are reporting that the issue no longer happens.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
** Changed in: elementaryos
Milestone: None => freya-0.3.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1390625
Title:
mouse cursor gets corrupted
Status in elementar
** Also affects: elementaryos
Importance: Undecided
Status: New
** Changed in: elementaryos
Status: New => Confirmed
** Changed in: elementaryos
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
Thanks. Looks like http://au.archive.ubuntu.com/ is out of date. I
will contact AARNet to get it updated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1385131
Title:
Public bug reported:
I just upgraded from 14.04 to 14.10 and lsb_release is showing an
incorrect description. I'm seeing the same problem in the lsb-release
file from "apt-get source base-files".
$ lsb_release -d
Description:Ubuntu Utopic Unicorn (development branch)
$ cat /etc/lsb-release
My understanding was that the changes to the International keyboard
was that it should be truly international, and support *all* of unicode.
Most of us writing in English would just as soon only have a little bit of
International.
There is a way to set up your input any way you want, and I've tak
27 matches
Mail list logo
