The valid CSS would be:
font-weight: lighter;
In the case of explicitly wanting "Ubuntu Light", once everything is
fixed, the CSS access will hopefully be just:
font-family: "Ubuntu";
font-weight: 300;
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Daniel, plan is to switch the fonts for source-built versions.
These source-built fonts should in the first instance be work-alikes
(equivalents) to the binary fonts currently shipped via Google Fonts.
The versions hosted on Google Fonts have undergone various refinements
of the metadata
This changeset was applied upstream:
https://www.virtualbox.org/changeset/62201/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Further discussion at:
https://irclogs.ubuntu.com/2016/07/12/%23ubuntu-devel.html#t15:20
with a pointer to:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c#L136
And side-discussion of possible better ways of how to detect client GL
vs. server GL, which
@ellisistfroh: I cannot see anything in the lightdm (1.18.2-0ubuntu1)
changelog to suggest that it might have addressed this issue.
@michael-thayer: thank you for spending the extra time to confirm that
lightdm (1.18.2-0ubuntu1) is still affected.
--
You received this bug notification because
** Description changed:
I sometimes get the "low-graphics mode" message when starting an Ubuntu
16.04 virtual machine inside of VirtualBox (current development code
trunk, somewhere past version 5.1 beta 3 and a debug build). When I
switch to VT-7 I find the X server running without any
Alternative solution implemented via Open Build Service 'Ubuntu:16.04'
configuration update.
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
So, guessing, was this the diff that was applied:
--- Ubuntu-16.04.txt.orig 2016-04-22 14:24:12.163974719 +0200
+++ Ubuntu-16.04.txt2016-04-22 14:23:51.095974821 +0200
@@ -88,2 +88,3 @@
+Ignore: upstart:ifupdown
Ignore:
Neal: do you have eg. an OBS commit log/changeset we can link this to?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1573275
Title:
ifupdown should not hard-depend upon
** Summary changed:
- does not use the new orange
+ Toolkit should use new orange #e95420
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-html5-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1572588
Title:
(For want of a better place to put it), useful ttx diffs + changelog
forwarded to me at the end of yesterday which gives more context on what
the above referenced .zip file delivery is.
[Kudos to DM Engineering to doing this in an automated fashion, and
those along the chain for passing it
The test case suggests a change to 'Ubuntu Mono', but the
'Ubuntu_0.831.zip' I have here doesn't have any Ubuntu Mono (nor source,
nor changelog, nor scripting, nor test cases, nor any contextual
information). I can see:
2016-01-04 11:31 Zip file (repacked today?)
2015-12-04 10:55 .ttfs
If other people want to test:
sudo apt-get install fonts-ubuntu-font-family-console
dpkg -L fonts-ubuntu-font-family-console | grep -m1 .psf | xargs sudo setfont
-C /dev/tty2
and then it's possible to flick between:
Ctrl-Alt-F1 (tty1 showing Ubuntu Mono Regular rendered to 8x16)
Possibly from the numeral glyphs being fetched from Ubuntu Arabic
Regular, and the Latin coming from Ubuntu Regular, and the metrics
somehow being confused.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Woo!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/683294
Title:
do not hardcode x86 hw breakpoint instruction
Status in Nux:
Fix Released
Status in nux package in
Simon: excellent work. I have a particular fondness for reading the
write-ups on this time of bug. It reminds me a little of the infamous
Doesn't print on Tuesdays (bug #248619).
Once again, kudos to gradually narrowing down how to replicate it, then
finding it and finally offering the patch.
As Ubuntu (proportional) and Ubuntu Mono have different family names
it would probably make sense to split the binary packages produced into
two .debs built at the same time—this would allow installing one or the
other. Doing this as a one-off would be painful, but it would be
relatively quick
This likely needs a day or two of debugging depending.
For fixing: once it's possible to rebuild the font, this is then likely
to be relatively easy to patch; either in the source, or binary. And
then an hour or so to confirm the fix works.
--
You received this bug notification because you are
*** This bug is a duplicate of bug 851457 ***
https://bugs.launchpad.net/bugs/851457
(Hasn't been updated, because there hasn't been a upstream realise to
fix it in).
** This bug has been marked a duplicate of bug 851457
[pkg] package should be renamed according to new Debian Fonts Policy
All in good time hopefully! :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/934038
Title:
[nc] FFe: Upload $newer upstream version
Status in
Install attached to:
~/.local/share/applications/logout.desktop
and a Logout icon will appear in Unity when typing logout.
** Attachment added: logout.desktop
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4284166/+files/logout.desktop
--
You received this bug
Install attached to:
~/.local/share/applications/shutdown.desktop
and a Shutdown icon will appear in Unity when typing shutdown.
** Attachment added: shutdown.desktop
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4284167/+files/shutdown.desktop
--
You received
Lonnie: being familiar with the Design team (having worked in it…), my
suspicion is that this class of feature improvement often gets bogged
down for (very) long periods of time. Therefore a method that can be
deployed (or at least prototyped) immediately using existing external
mechanisms is far
** Attachment removed: xserver.devices.txt
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282487/+files/xserver.devices.txt
** Attachment removed: xdpyinfo.txt
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282486/+files/xdpyinfo.txt
It should be possible to solve this by providing a '.desktop' file
containing entries for 'shutdown', 'logout', and 'reboot/restart'; and
then it's not a Unity dash issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity
Is the category empty for a reason, or is the filtering just broken?
(If so that could be fixed instead of removal).
--
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/864323
Anton: I'm interested in understanding the situation a little better:
1. Internal applications originally targeting eg. GNOME 2, and you're now
needing to run these under Unity.
2. Bought-in (external non-IBM) applications originally targeting eg. GNOME
2, and you're now needing to run
27 matches
Mail list logo
