[Bug 573266] [NEW] [Ambiance, radiance] forcibly override the window button order
Public bug reported: Binary package hint: light-themes Changing to ambiance or radiance, including ambiance the *GTK+* (not metacity) theme, forcibly overrides the /apps/metacity/general/button_layout setting to put the buttons on the left, overriding the user setting. This is completely wrong and basically destroys the user settings to force the system defaults. Defaults should be that, default in the absence of specific customisations, not forced upon users each time they happen to look ambiance's way. I don't know if this is the same as bug #568796, but the description in it describes a somewhat different thing, so opening a new bug. ** Affects: light-themes (Ubuntu) Importance: Undecided Status: New -- [Ambiance, radiance] forcibly override the window button order https://bugs.launchpad.net/bugs/573266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573266] Re: [Ambiance, radiance] forcibly override the window button order
Yes, this is about 2. The value in /apps/metacity/general/button_layout is being changed to the default left-side layout, replacing the value I put in it. -- [Ambiance, radiance] forcibly override the window button order https://bugs.launchpad.net/bugs/573266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998862] Re: [TECRA R850, Realtek ALC269VB, Mic, Internal] No sound captured at all
I hit this issue on Mint 16 (which is derived from 13.10, running PulseAudio 4.0), on an MSI X370 laptop, which also has Realtek ALC269VB. I have been able to identify the issue (in a way), and work around it for now using pavucontrol, though it's clearly wrong. The problem is that the normal capture stream for the "Built-in Analogue Stereo" device is completely distorted, to the point where it appears to be just flat noise with no correlation to anything the microphone captures. It's not truly the case, you can actually hear certain loud sounds when you bump up the capture volume, but they're very, very mangled and unrecognisable. However, the *Monitor* of Built-in Analogue Stereo has perfectly fine, clear sound. I don't know enough about PA to pinpoint the issue, but it shows that the problem is purely in the software and has nothing to do with hardware or faulty drivers. If I were to chance a guess, I'd say it's something like the wrong codec or sample format being output, different than what is advertised. Because the monitor stream collects all data passing through, it has the ability to replicate the capture stream, but is apparently not affected by whatever is causing the ordinary capture stream to mangle its data. Now, the workaround is to install pavucontrol, and in Input Devices tab set the Monitor of Built-in Analogue Stereo as the fallback device. This will make all apps use that rather than the capture device directly, thus letting you use the microphone. It's ugly as sin and very wrong, but it works while we look for a real solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998862 Title: [TECRA R850, Realtek ALC269VB, Mic, Internal] No sound captured at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/998862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998862] Re: [TECRA R850, Realtek ALC269VB, Mic, Internal] No sound captured at all
Scratch what I said, the Monitor thing is no solution because it's simply a mirror of what is being played back on the sound card, and it only appeared to help because of how I was debugging it. Still, there's enough distorted similarity between what I *should* be hearing captured and what actually comes from the mic that it makes me think the audio stream is somehow being misinterpreted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998862 Title: [TECRA R850, Realtek ALC269VB, Mic, Internal] No sound captured at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/998862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839189] [NEW] font hinting produces nonsensical results for tilde-a
Public bug reported: This is a problem with hinting, so I'm assigning it tentatively to FT, because I don't really know where the problem lies. As described below the problem is present on an installed Ubuntu 10.04, as well as completely pristine 11.04 run from a USB stick. Description: Font hinting fails completely for U+00E3 LATIN SMALL LETTER A WITH TILDE (ã). For instance in the "Ubuntu" font at 18pt size it's rendered indistinguishable from a macron, whereas at 19pt it's very clearly a tilde. The problem is not limited to a single font, or a single size, or only for small enough sizes. Another font exhibiting the same problem is Trebuchet MS -- the tilde looks perfect at 32pt, but at 33pt it's almost a straight line with barely visible trace of waves. Same for lower sizes: below 14pt it's rendered as a macron, 15 and 16 have it look right, then macron up until 23pt, then 24pt is great again but 25pt is a macron, etc. The same problem is not present for U+0303 COMBINING TILDE. A combined with it (ã) is rendered properly and visibly at all point sizes down to 8pt. At 7pt it does look like a straight line, but it's hard to judge because the font is so tiny. The attached .gif is a small animation clearly showing the issue. ** Affects: freetype (Ubuntu) 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/839189 Title: font hinting produces nonsensical results for tilde-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/839189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839189] Re: font hinting produces nonsensical results for tilde-a
** Attachment added: "tilde.gif" https://bugs.launchpad.net/bugs/839189/+attachment/2341806/+files/tilde.gif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839189 Title: font hinting produces nonsensical results for tilde-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/839189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839189] Re: font hinting produces nonsensical results for tilde-a
To add to the above, and especially given the behaviour with Trebuchet MS, where it's nice at a nice, round size of 16, and twice that 32, but fails at one point larger, I'd wager it's overzealous pixel grid snapping distorting the shape at sizes which have the tilde's waves come ever so slightly outside the grid. But I dunno how to influence that, so I can't really track down the root cause myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839189 Title: font hinting produces nonsensical results for tilde-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/839189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839189] Re: font hinting produces nonsensical results for tilde-a
So the problem is only limited to LCD subpixel aliasing, when I select the antialiasing type of "best contrast", "best shapes" or "monochrome", tilde remains a tilde. All these antialising however cause huge variations in the font widths and kerning, as well as causing perceived emboldening at the 12→13pt switch. Subpixel antialiasing produces fonts that are visually consistent across point sizes, but clearly does something too eagerly to the tilde. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839189 Title: font hinting produces nonsensical results for tilde-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/839189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666806] [NEW] [Maverick] APPINDICATOR automake-fu is broken
Public bug reported: Binary package hint: gnome-settings-daemon As of 2.32.0-0ubuntu3, the automake-fu, as listed on https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#Automake%20fu, has been applied wrongly, for no visible reason. Namely, the original bit: AC_ARG_ENABLE(appindicator, AS_HELP_STRING([--enable-appindicator[=@<:@no/auto/yes@:>@]],[Build support for application indicators ]), [enable_appindicator=$enableval], [enable_appindicator="auto"]) has been instead changed to: AC_ARG_ENABLE([appindicator], AS_HELP_STRING([--enable-appindicator[=@<:@no/auto/yes@:>@]],[Build support for application indicators]), [enable_appindicator="yes"], [enable_appindicator="auto"]) Due to the way automake snippets are expanded and organised, this has the effect of ignoring the actual value supplied to --enable- appindicator and always substituting "yes" instead. The original form of '[enable_appindicator=$enableval]' should be restored to fix it. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- [Maverick] APPINDICATOR automake-fu is broken https://bugs.launchpad.net/bugs/666806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666806] Re: [Maverick] appindicator patch to g-s-d breaks compilation for appindicator-less case
** Summary changed: - [Maverick] APPINDICATOR automake-fu is broken + [Maverick] appindicator patch to g-s-d breaks compilation for appindicator-less case -- [Maverick] appindicator patch to g-s-d breaks compilation for appindicator-less case https://bugs.launchpad.net/bugs/666806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666806] Re: [Maverick] appindicator patch to g-s-d breaks compilation for appindicator-less case
Additionally, the 06_use_application_indicator.patch omits #ifdefs around one chunk of appindicator-specific code, breaking the compilation for --enable-appindicator=no. The attached diff is a patch to that patch, fixing both problems reported.b ** Patch added: "06_use_application_indicator.patch.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/666806/+attachment/1712630/+files/06_use_application_indicator.patch.diff -- [Maverick] appindicator patch to g-s-d breaks compilation for appindicator-less case https://bugs.launchpad.net/bugs/666806 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
