To assist with debugging please try both of these options
(individually) from a clean state:
(a) sudo mount -o remount,exec /dev
(b) sudo setsebool -P mmap_low_allowed
(ie. boot, test, reboot, test the other).
Do either of those work?
--
You received this bug notification because you are a
** Description changed:
On Ubuntu 18.04, with `apt-get source ` being the de facto
way of getting (src-deb) sources for a binary package, it is not so with
the linux kernel.
`apt-get source linux-image-$(uname -r)` -- leads to "linux-signed" which is
not the kernel src deb
`apt-get
The new upstream maintainers are quite enthusiastically working to help
get Openbve back into Debian/Ubuntu. If the data files hang around, it
is likely to be less work later on:
* https://github.com/leezer3/OpenBVE/issues/330#issuecomment-484102817
(The data files can be used with other
Excellent, Jacob! Thanks for keeping tabs on it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/56459
Title:
Unix putty does not accept user@host syntax
To manage notifications about this bug go
** Changed in: fonts-ubuntu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574534
Title:
Aspect ratio of Ubuntu Mono font at small sizes changed
To
https://irclogs.ubuntu.com/2018/09/27/%23ubuntu-devel.html#t11:31
The BIOS shows a RAID1 (mirror) pair, this is designated as:
RAID Level: "Recovery (Cont.)" in the BIOS. (screenshot)
This stands for "Recovery Set" == RAID1/Mirror group.
Newer 'mdadm --detail-platform' only reports:
$
TL;DR: probably mdadm commit from April 2018; see end.
Today's IRC logs of debugging session with reporter:
https://irclogs.ubuntu.com/2018/09/26/%23ubuntu-devel.html#t06:41
Current understanding of the situation from log analysis:
08:21 reboot with (4.15.0-29.31-generic), no problem
Per the earlier conversation:
https://irclogs.ubuntu.com/2018/09/25/%23ubuntu-devel.html#t09:22
need to know:
* exact version number of last working Linux kernel
* exact version number of non-working Linux kernel
--
You received this bug notification because you are a member of Ubuntu
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
Bugs, which
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
Christian: looking back and your reply in #478, it would appear that
you're on Mint, not Ubuntu. It is likely the case that Mint is still
shipping the buggy kernel(s).
We can see in #478: "When installing the Kernels provided above, I can
again do changes in BIOS and they stay over reboot.
@Paul sabret00the. Please can you file separate new bugs for the
"disassociated with its launcher icon", "my swap disk has issues", and
"I can't launch any Virtual Boxes". These are not related to the CMP
bit in the flash chip, and putting them on this bug report adds
confusion to this issue
Register map documentation for the SPI (Serial Peripheral Interface) in
recent Intels begins on page 5626
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000
-datasheet-vol-2.pdf
HSFSTS (Hardware Sequencer Status) + HSFCTL (Hardware Sequencer Control)
are covered
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Could somebody with the hardware also do a test with the following lines
commented out in 'intel-spi.c', commenting out the writel() that
disables SMI interrupt generation, re-compile the kernel and retest:
Mika Westerberg emailed again with a pointer to the commit from a few
months ago, specifically dealing with a similar issue on Lenovo Yoga
machines:
"""
mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell
At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the
(For clarity the above upload of linux (kernel)=4.13.0-21.24) is a
workaround that just disables compiling in of the module under
suspicion. Because the module is not compiled it, it will not therefore
be loaded either).
--
You received this bug notification because you are a member of Ubuntu
[The two theories provided by Mika Westerberg, verbatim]
"""
Instead I have a theory since as far as I know there have been to kinds
of issues.
1. Flash is left locked. This makes the BIOS impossible to save
settings.
This seems to happen only for GigaDevice flashes and for all of
Have received an excellent reply from Mika Westerberg (thank you!). One
with a suggestion regarding 'GigaDevice' flash chips, and one regarding
certain 'Winbond' flash chips.
Is somebody with access or one of more of these machine(s) able to
provide insight into what flash parts are in their
Page 5 of:
http://opensecuritytraining.info/IntroBIOS_files/Day2_03_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SPI%20Flash%20Protection%20Mechanisms.pptx
Talks about "Flash Protection Mechanism";
"Write Protect / Writes blocked / Not Range Specific / SMI# override:
Same as Write
I've emailed Mika Westerberg (author of the module) to ask to share
anything further documentation they've got that would allow a better
understanding of the (intended) operation of the 'intel-spi' module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
FWIW, the Intel-SPI Readme contains:
https://github.com/torvalds/linux/blob/master/Documentation/mtd/intel-
spi.txt
"makes it possible to read and write the SPI serial flash, if certain
protection bits are not set and locked."
"… If it finds any of them set, the whole MTD device is made
Aidan: I think I made the code to make it work. From what I recall the
main upstream author is/was not happy with the just API compatibility
(recompiling) and would have preferred to see an ABI compatible (binary
compatibility). This effectively means the need for a full i386+Win32
environment
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599775
Title:
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573275
Title:
ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572588
Title:
Toolkit should use new orange #e95420
To
** Description changed:
'/etc/init.d/networking' for 'ifupdown' starts with:
# Required-Start:mountkernfs $local_fs urandom
it would appear that 'mountkernfs' and 'urandom' are not hard-
dependencies, and their presence prevents successful installation in
- virtual machines in
** Description changed:
'/etc/init.d/networking' for 'ifupdown' starts with:
- # Required-Start:mountkernfs $local_fs urandom
+ # Required-Start:mountkernfs $local_fs urandom
it would appear that 'mountkernfs' and 'urandom' are not hard-
dependencies, and their presence
Public bug reported:
'/etc/init.d/networking' for 'ifupdown' starts with:
# Required-Start:mountkernfs $local_fs urandom
it would appear that 'mountkernfs' and 'urandom' are not hard-
dependencies, and their presence prevents successful installation in
virtual machines in some
(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
I received a 'Ubuntu_0.831.zip' file yesterday, without any context, but
appears to a possible test case[1] that if applied to the main font
build would unblock this and allow Dash to select Medium (hopefully;
other blocker was in Qt).
[1] (Selected font test, probably for confirmation of that
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
Bugs, which is subscribed to Ubuntu.
** Description changed:
Filing here per request at:
http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35
- The issue is regarding touch infra-red overlay touch screen panels from
+ The issue is regarding infra-red overlay touch screen panels from
Wivitouch in China:
-
** Description changed:
Filing here per request at:
http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35
- I have approximately 300 USB touch panels. These are from two different
- batches, but all report the same USB ID 0c45:8419. The manufacturer
- told me they had
** Description changed:
Filing here per request at:
http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35
I have approximately 300 USB touch panels. These are from two different
batches, but all report the same USB ID 0c45:8419. The manufacturer
told me they had
** Summary changed:
- New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
+ New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no
longer working under 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment removed: "hidreplay-not-working .txt"
https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+attachment/4524728/+files/hidreplay-not-working%20.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Filing here per request at:
http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35
- I have approximately fifty USB touch panels. These are from two
- different batches, but all report the same USB ID 0c45:8419. The
- manufacturer told me they had
Cesar, there is only one copy of the output of "sudo lsusb - -d
0c45:8419", please can you run if for *both* the old and new firmware-
revision devices, so that it's possible to compare and see if there is a
way to tell them apart.
Please can you include the information from the manufacturer
(Extracted from tarball and re-attached).
** Attachment added: "lsusb--0c45:8419-not-working.txt"
https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+attachment/4524711/+files/lsusb--0c45%3A8419-not-working.txt
** Description changed:
Filing here per request at:
-
(Extracted from tarball and re-attached).
** Description changed:
- This new device does not work.
+ Filing here per request at:
- EventTest of not working one
- $ sudo evtest
- No device specified, trying to scan all of /dev/input/event*
- Available devices:
- /dev/input/event0: Power
Will: Ideally, please consider getting MPT's input on this prior to
picking one, he has a good knack for finding clear solutions in cases
like this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Woo!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683294
Title:
do not hardcode x86 hw breakpoint instruction
To manage notifications about this bug go to:
** Description changed:
- This is an issue that I have confirmed in ZNC 1.6.
+ ZNC is an IRC proxy. This is an issue that I have confirmed in ZNC 1.6.
When a module is being compiled by znc-buildmod as part of znc-dev, and
relies on unicode support or any functions provided by the icu
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.
*** This bug is a duplicate of bug 1447294 ***
https://bugs.launchpad.net/bugs/1447294
** This bug has been marked a duplicate of bug 1447294
package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
*** This bug is a duplicate of bug 1447294 ***
https://bugs.launchpad.net/bugs/1447294
** This bug has been marked a duplicate of bug 1447294
package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
*** This bug is a duplicate of bug 1447294 ***
https://bugs.launchpad.net/bugs/1447294
** This bug has been marked a duplicate of bug 1447294
package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
*** This bug is a duplicate of bug 1447294 ***
https://bugs.launchpad.net/bugs/1447294
** This bug has been marked a duplicate of bug 1447294
package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
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
Just a general observation on timings: when I last used this it was for
OpenStreetMap collection, where 1Hz is the generally required/desired
rate for track collection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934038
Title:
[nc] FFe: Upload $newer upstream version
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864323
Title:
Category fonts in
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
Clockwork: The glyph has been replaced in 0.910-prerelease (see above).
0.910 currently has other regressions that make it hard to release in
its current form.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Alex, Г has been fixed in the 0.910-prerelease Ubuntu Mono
received from Dalton Maag. This PDF should shows the Russian, Ukrainian
and some other Balkan Cyrillic glyphs as they are in the
0.910-prerelease mono.
The 0.910-prelease has a number of other fixes (this is a good thing),
but also
** Summary changed:
- Replace the package bitcoin with an empty dummy package
+ bitcoin to be maintained upstream in PPA: Replace distro archive bitcoin
bitcoin with an empty dummy package
** Description changed:
+ The Bitcoin utilities are a set of virtual-currency tools. Going
+ forward the
Hadess: I had been looking that this; and my presumption is that each
layer shown/hidden/exported from Inkscape one at a time. But it's
definitely something that I'll make scripted so it's easy to re-export
the whole suite at $preferred_bitmap_size.
--
You received this bug notification because
Now split out into:
https://launchpad.net/timezonemap
** Also affects: ubiquity
Importance: Undecided
Status: New
** Project changed: ubiquity = timezonemap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- English US international not behaving as expected.
+ Common Dutch US international not available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248351
Title:
Common Dutch US
** Description changed:
- Problem:
- Dead keycombinations not working as expected, for example I'm becomes Iḿ.
- Adding a spreadsheet with every dead keycombination that doesn't work as
expected (expected output included).
+ In System Settings-Keyboard Layouts-Add the following Dutch layouts
+
** Changed in: linux (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/1205791
Title:
Dell Vostro V131: special keys not working
To manage notifications about
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205791
Title:
Dell Vostro V131: special keys not working
To manage notifications about this bug go to:
Whoopie: please can you attach a copy of 'lspnp'.
** Description changed:
- Hi,
+ Bug filed, following conversation on IRC at:
- I own a Dell Vostro V131. This model has 3 special hotkeys (quick launch
keys, see
http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg).
-
Page 12 of:
http://odm.ubuntu.com/uhs/2011/Enabling%20Hotkey%20Features%20on%20Ubuntu.pdf
gives this as the Dell WMI GUID:
9DBB5994-A997-11DA-B012-B622A1EF5492 dell_wmi
Whoopie: are you seeing unhandled WMI event at the same time as the
key is pressed?
If this is not obviously the case it
$ lsb_release -d
Description:Ubuntu 12.04.2 LTS
$ lusb | grep Canon
Bus 002 Device 010: ID 04a9:2216 Canon, Inc. CanoScan 3200F
$ sane-find-scanner
found USB scanner (vendor=0x04a9, product=0x2216, chip=GL841?) at libusb:002:010
found USB scanner (vendor=0x147e, product=0x2016) at
Ejectmail, thank you for looking into it. Remember that the interim UFL
has drawn up as a first take, with the hope to refine it, so input is
appreciated, because out of it we can get a better libre font licence
than the choices that were available at the time.
Obviously one must start
NOPE, VOLUME KEYS HAVE ALWAYS BEEN ALWAYS RELATIVE (CAPPED AT) 100% WHEN
GOING UP.
** Package changed: unity (Ubuntu) = gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adolfo: please could you attach the curve files that you were working
with to this bug report so they don't get lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/650498
Title:
Expansion: 'ẞ'
What font name is display when right-clicking on these glyphs in the
Character Map (this shows which font they are really coming from). If I
select Ubuntu and then right-click on these glyphs it shows me that
they are originating from FreeSans. Is this what you see too?
** Changed in:
Nicolò: I'd really like not to have a EULA style box. Users have
negative feelings towards whack-a-mole popups and EULA windows between
between them and the interface. User tend to dismiss them anyway but
remember the annoyance.
A few years ago Mozilla tried something very similar with Firefox
Nicolò: OTOH, it would increase code in Unity Dash for very little gain,
and probably negative gain. Firstly it's a 90%/10% thing; the legal
notice is not frequently used, but still needs to be reliable and easy
to interact with when required. The current situation of using a Web
browser would
Miguel/Cliff: it's a bit of a backronym, but perhaps think of it this
way. We have the *buntu core (kernels, system libraries, brand, fonts,
…) on top of which are built several optimised distributions (remixes):
KDE: [Ku]buntu
LxDE: [Lu]buntu
XDE: [Xu]ubuntu
Unity: [U]buntu
Gnome3
James: I think a lot of it is about works with Ubuntu vs. works
against some APIs that were made 10 years ago, and which most/some
Unices' Windows Managers have supported at some time. For stuff to
work with *the Ubuntu experience* some effort will be required; this is
much the same as following
Chris: which (precise) applications that you use for work do not support
the Unity global menu?
For example, for myself, there are two applications without have global
menu support:
1. JOSM (OpenStreetMap editor, Java-based owing to portability)
2. Fontforge (purely custom widget set, owing
Probably the easiest is to start gnome-character-map/gcharmap; select
Ubuntu, search to U+25D2 and then *right-click* on the glyph. This
will then show a larger rendering of the glyph and state the _actual_
font that the glyph is coming from in the pop-up.
Depending on whether it's correct or
** Package changed: ubuntu-font-family-sources (Ubuntu) = ttf-dejavu
(Ubuntu)
** Bug watch added: freedesktop.org Bugzilla #55197
https://bugs.freedesktop.org/show_bug.cgi?id=55197
** Also affects: dejavu-fonts via
https://bugs.freedesktop.org/show_bug.cgi?id=55197
Importance: Unknown
From memory we don't have these two glyphs in the Ubuntu Font Family
yet; would you be able to supply a screenshot so that we can try and
work out where they're being substituted from and fix them in /that/
font.
** Changed in: ubuntu-font-family-sources (Ubuntu)
Status: New = Incomplete
For anyone wondering, Xi's PNG is correct and is white-on-white; the
white text is solid/opaque and the white background is transparent. The
text reads ubuntu^ 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Daniel; thank you for the comment. While the point about
dithering may be valid different issue though; one of style/technical
choices; rather than of JPEG compression. Would you be able to file it
as a new, separate issue, if you'd still like to follow it up?
** Changed in:
Marking as Fixed, as the core issue of size restrictions leading to
high-compression is hopefully resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016824
Title:
Ubuntu wallpapers are low
Hi Sam, as a work-around, try Shift+Fn+Home/End.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/218712
Title:
Backlight brightness on Lenovo R61 won't go all the way down
To manage notifications
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete = Invalid
** Changed in: command-not-found (Ubuntu)
Status: Incomplete = Invalid
** Changed in: ayatana-design
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Stephen: It's not really ideal, but I can try shunting it around to
increase the likelihood of a 60-day time out happening. I'd welcome any
more-ideal solutions/suggestions if somebody can make them. I have a
feeling that Launchpad used to have a null project for shunting
miscellaneous items
drmgiver: What would you like to see done? Could you please explain how
setting it to confirmed helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055766
Title:
grep -R doesn't automatically
Sergei: go for it! It should be possible to do something with the
machine's webcam and Processing:
http://processing.org/
plus some OCR. The search domain could be kept smaller by cross-
referencing potential CD/Album title matches with FreeDB to look up the
contents of a CD once you have the
1 - 100 of 3224 matches
Mail list logo
