[Touch-packages] [Bug 411688]

2019-01-02 Thread Freedesktop-u
You are right that this feature needs to be enabled first to make the
bug rise. However I do not think that documentating this bug/behavior
solves the problem. I do want to use music streaming, but I cannot do
this as my router routes the traffic into the WLAN.

Lowering the rate is possibly not a good idea as it results in worse
quality. The format is by default "s16be" about which I have no idea
what a different format would help. I do not know if the data can
somehow be compress further, because this would definitely be an idea,
but I dont know the procols internal.

So the only left option is to solve the routing. For my personal setup
there is no way to fix this on the router side, so the sender pulse
module needs to take care of it. Using an ip as destination works
perfectly and would be an option to use (which should be added to
paprefs). However I tried that the last days and due to dhcp my receiver
always gets a new IP and using hostnames would be a better idea.

But the module does not seem to support hostnames. So I am wondering if
this could be fixed quite simple or needs a whole more work to do.

Another option would be to possibly create a port on the localhost and
route that to the destination ip/name. And the kernel itself can do the
name resolution. However I have no idea about that, but this could at
least be a workaround to solve this issue.

Other opinions?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
 

[Touch-packages] [Bug 411688]

2019-01-02 Thread Freedesktop-u
Sure mp3 would be way better. I just dont know how rtp works. I think
its reasonable to use mp3 here. However I dont know how that works for
streams and with pulse.

Fixing the compression method would be the better fix, however a
specific ip/hostname would not hurt neither.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 

[Touch-packages] [Bug 411688]

2019-01-02 Thread Freedesktop-u
I've also noticed this in the most up to data pulse versions from
archlinux. I also cannot use a ttl of 1, as the router does not decrease
the value when routing into wlan, as it has the same subnet. Neither
does destination ip 24.0.0.1 help. From my side I have no chance to
change the router config, because the internet is provided by someone
else.

What works for me though is to stream the music directly to the
destination via destination_ip=192.168.178.x

I could also add a menu in paprefs that'd also adress the ip directly,
however this is more of a struggle because of the old gtk2 (if anyone
here is following the mailing list). It would be highly appreciated to
fix this bug in the module itself and reduce the payload somehow.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  

[Touch-packages] [Bug 1438510]

2018-07-12 Thread Freedesktop-h
Can also confirm the issue with Sony WH-H900N headphones, Arch with
kernel 4.17.4, BlueZ 5.50, PulseAudio 12.0.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1438510

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 746383]

2016-03-13 Thread Freedesktop
*** Bug 94505 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/746383

Title:
  fontconfig confuses bold and medium weights

Status in Fontconfig:
  Fix Released
Status in Pango:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in pango package in Ubuntu:
  Triaged

Bug description:
  Attempts to set "Ubuntu Bold" in the Appearance settings fall back to
  "Ubuntu Medium". In fact, in the font selection screen there seems to
  be no difference between bold and medium.

  Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is*
  installed and accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Thu Mar 31 08:33:44 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110325)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 740506]

2015-10-17 Thread Ralph-freedesktop
(In reply to Albert Astals Cid from comment #82)
> > - Is '-c' the best option name for "don't perform certificate validation"? 
> 
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.

It's vital to put thought into "naming things" before a poor decision
becomes permanent because it becomes public.  At the very least, "-c"
suggests check and "-C" would often be the negative don't check, even if
no -c option exists because it's the default.

And then there's the issue Adrian raises.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 161058]

2015-05-23 Thread Freedesktop
Karl, would you have time to finish the patch for this?  That would be
really appreciated.  Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/161058

Title:
  some ~/.fonts.conf settings do no override desktop-wide gnome settings
  (hinting style)

Status in Cairo Graphics Library:
  Confirmed
Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  I didn't fill out the package field, since this seems to be an
  interaction between multiple packages (gnome-setting-daemon, libgtk,
  libcairo, pango/cairo).

  In the 'Appearance' control app, under the font settings, I like to
  use 'Subpixel' and 'Full' hinting by default, since this looks good
  for most bundled fonts.

  However, there is occasionally a font (especially in the msttcorefonts
  package) that doesn't look good with these settings. So I want to
  override their rendering settings using .fonts.conf. My main tactic is
  to usually turn on the autohinter in 'hintslight' mode for certain
  fonts. Lets take Times new Roman as an example.. the .fonts.conf
  incantation to do this would be:

   match target=font
   test name=family qual=any 
   stringTimes New Roman/string
   /test
  edit name=autohint booltrue/bool/edit
  edit name=hinting booltrue/bool/edit
  edit name=hintstyle  consthintslight/const /edit
   /match

  The odd thing about this is that the 'autohint' and 'hinting' edits
  seem to work, but the 'hintstyle' edit is always overridden by the
  control applet's settings. I can verify this by launching gedit each
  time after tweaking these settings.

  fc-match -v 'Times New Roman' does return the right settings, so its
  something in the chain of gtk libraries that is messing it up.

  Interstingly, it's not all possible edit settings that are ignored. It
  seems to only be hintstyle. For example if I were to say:

  
   match target=font
   test name=family qual=any 
   stringTimes New Roman/string
   /test
  edit name=antialias bool false /bool /edit
   /match

  Then this works correctly. Only Times New Roman will be non-antialiased even 
in gedit. Even setting hinting to false works.. its only the hintstyle 
setting that doesn't work.
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX 
Host bridge [8086:7190] (rev 01)
Subsystem: VMware Inc Device [15ad:1976]
  00:0f.0 VGA compatible controller [0300]: VMware Inc Abstract SVGA II Adapter 
[15ad:0405]
Subsystem: VMware Inc Abstract SVGA II Adapter [15ad:0405]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/161058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1199571]

2015-01-25 Thread Freedesktop
Patchset is now upstream in FreeType.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/1199571

Title:
  Huge multi-threading violations in freetype

Status in FreeType: High Quality Font Rendering:
  Fix Released
Status in freetype package in Ubuntu:
  In Progress

Bug description:
  Fresh dist-upgrade; brought up the dash, typed term; single clicked
  on the terminal app and _bang_.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Tue Jul  9 17:47:10 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-06-06 (33 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax)
   PC (0x7ff3b4ed7a10) ok
   source %rdx ok
   destination 0x10(%rax) (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/freetype/+bug/1199571/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1177995]

2015-01-23 Thread Freedesktop
Closing.  FC_HASH was shortlived.  Doesn't exist anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1177995

Title:
  libfontconfig from Gnome3 staging PPA breaks CSS webfonts in firefox

Status in Fontconfig - Font Configuration Library:
  Invalid
Status in Ubuntu GNOME:
  Fix Released
Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  When i install he Gnome3 staging PPA the webfont support in Firefox
  breaks. I only see fallback fonts, but not the correct webfonts
  downloaded from the server. this happens everywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libpango1.0-0 1.33.9-0ubuntu1~raring0 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed May  8 23:50:37 2013
  InstallationDate: Installed on 2013-02-01 (96 days ago)
  InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pango1.0
  UpgradeStatus: Upgraded to raring on 2013-04-22 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1177995/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1199571]

2015-01-04 Thread Freedesktop
I now have a complete patchset up here:

  https://github.com/behdad/freetype/commits/ftthread


Will be sending upstream soon.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1199571

Title:
  Huge multi-threading violations in cairo

Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Fresh dist-upgrade; brought up the dash, typed term; single clicked
  on the terminal app and _bang_.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Tue Jul  9 17:47:10 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-06-06 (33 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax)
   PC (0x7ff3b4ed7a10) ok
   source %rdx ok
   destination 0x10(%rax) (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/libcairo/+bug/1199571/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1199571]

2015-01-04 Thread Freedesktop
Done.  See:
http://www.mail-archive.com/freetype-devel@nongnu.org/msg06758.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1199571

Title:
  Huge multi-threading violations in cairo

Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Fresh dist-upgrade; brought up the dash, typed term; single clicked
  on the terminal app and _bang_.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Tue Jul  9 17:47:10 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-06-06 (33 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax)
   PC (0x7ff3b4ed7a10) ok
   source %rdx ok
   destination 0x10(%rax) (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/libcairo/+bug/1199571/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1199571]

2015-01-04 Thread Freedesktop
So, I ended up trying to fix this in FreeType.  Have made huge progress
so far.  Here's a tree:

  https://github.com/behdad/freetype/commits/ftthread

And here's a standalone test:

  https://github.com/behdad/ftthread

There's still some more work to do.  I can't yet understand this crash
for example:

https://bugzilla.redhat.com/show_bug.cgi?id=1165471

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1199571

Title:
  Huge multi-threading violations in cairo

Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Fresh dist-upgrade; brought up the dash, typed term; single clicked
  on the terminal app and _bang_.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Tue Jul  9 17:47:10 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-06-06 (33 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax)
   PC (0x7ff3b4ed7a10) ok
   source %rdx ok
   destination 0x10(%rax) (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/libcairo/+bug/1199571/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 746383]

2014-07-27 Thread Freedesktop
Tracking pango issue here:
https://bugzilla.gnome.org/show_bug.cgi?id=733764

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/746383

Title:
  fontconfig confuses bold and medium weights

Status in Fontconfig - Font Configuration Library:
  Fix Released
Status in Pango - Layout and Text Rendering LIbrary:
  Fix Released
Status in “fontconfig” package in Ubuntu:
  Triaged
Status in “pango” package in Ubuntu:
  Triaged

Bug description:
  Attempts to set Ubuntu Bold in the Appearance settings fall back to
  Ubuntu Medium. In fact, in the font selection screen there seems to
  be no difference between bold and medium.

  Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is*
  installed and accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Thu Mar 31 08:33:44 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 746383]

2014-07-27 Thread Freedesktop
My bad, this *is* a fontconfig issue.  Investigating.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/746383

Title:
  fontconfig confuses bold and medium weights

Status in Fontconfig - Font Configuration Library:
  Fix Released
Status in Pango - Layout and Text Rendering LIbrary:
  Fix Released
Status in “fontconfig” package in Ubuntu:
  Triaged
Status in “pango” package in Ubuntu:
  Triaged

Bug description:
  Attempts to set Ubuntu Bold in the Appearance settings fall back to
  Ubuntu Medium. In fact, in the font selection screen there seems to
  be no difference between bold and medium.

  Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is*
  installed and accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Thu Mar 31 08:33:44 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 746383]

2014-07-27 Thread Freedesktop
Pango fixed.  See screenshots here:
https://bugzilla.gnome.org/show_bug.cgi?id=733764

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/746383

Title:
  fontconfig confuses bold and medium weights

Status in Fontconfig - Font Configuration Library:
  Fix Released
Status in Pango - Layout and Text Rendering LIbrary:
  Fix Released
Status in “fontconfig” package in Ubuntu:
  Triaged
Status in “pango” package in Ubuntu:
  Triaged

Bug description:
  Attempts to set Ubuntu Bold in the Appearance settings fall back to
  Ubuntu Medium. In fact, in the font selection screen there seems to
  be no difference between bold and medium.

  Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is*
  installed and accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Thu Mar 31 08:33:44 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp