[Touch-packages] [Bug 1821494] Re: Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping

2020-04-25 Thread Nelson Elhage
I've submitted an upstream MR here based on the OP's fix with some
slight edits based on my tseting:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/286

-- 
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/1821494

Title:
  Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse &
  incorrect channel mapping

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Similar to the Steelseries Arctis headphones, these sound "cards"
  present as two output devices, one intended for voice chat and one for
  everything else. As a result they also need a special profile.

  But there's another complication. They also have hardware HRTF that
  requires no special driver logic; instead, the "everything else"
  output pretends to be 7.1, and simply applies the HRTF to the streams
  sent by the host. However, the channel mappings picked up by ALSA are
  wrong -- the rear speakers and center/LFE are swapped.

  I know, technically this is two bugs, but they have the same fix which
  is impractical to separate. I'm attaching a "sennheiser-gsx.conf"
  based on the Arctis 7 profile that both corrects the channel mapping
  and exposes both output subdevices. A simple udev rule seals the deal:

  ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e",
  ENV{PULSE_PROFILE_SET}="sennheiser-gsx.conf"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  roothorick   7548 F pulseaudio
   /dev/snd/controlC2:  roothorick   7548 F pulseaudio
   /dev/snd/controlC0:  roothorick   7548 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 23 23:09:21 2019
  InstallationDate: Installed on 2018-09-12 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-03-23T20:51:33.488207
  mtime.conffile..etc.pulse.default.pa: 2019-03-23T23:03:49.029912

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821494/+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 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-13 Thread Nelson Elhage
@paulgear, what locale is your system in? If you're in a 24-hour locale,
as mentioned in #5, this bug is not present (well, to be precise, it's
present in the opposite direction).

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

Title:
  indicator-datetime set for 24 hours does not show 24 hour clock for
  "Other Locations"

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I configured the clock format to be 24-hour. This takes affect in the
  system clock, however "other locations" are unaffected and still show
  12-hour clock. See screenshot.

  This is Ubuntu Trusty

  indicator-datetime: 13.10.0+14.04.20140415.3-0ubuntu1

  I expect the Other Locations to also be 24 hour display.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+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 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-12 Thread Nelson Elhage
I'm sorry, that should be `en_GB.UTF-8`. But I just tested and confirmed
that workaround works.

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

Title:
  indicator-datetime set for 24 hours does not show 24 hour clock for
  "Other Locations"

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I configured the clock format to be 24-hour. This takes affect in the
  system clock, however "other locations" are unaffected and still show
  12-hour clock. See screenshot.

  This is Ubuntu Trusty

  indicator-datetime: 13.10.0+14.04.20140415.3-0ubuntu1

  I expect the Other Locations to also be 24 hour display.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+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 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-12 Thread Nelson Elhage
This is a terrible hack, but I've discovered that the applet will
respect your locale, just not the preference option.

So setting `export LC_TIME=en_UK.UTF-8` in your `.gnomerc` should work,
assuming you have the `en_UK.UTF-8` locale installed and configured.

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

Title:
  indicator-datetime set for 24 hours does not show 24 hour clock for
  "Other Locations"

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I configured the clock format to be 24-hour. This takes affect in the
  system clock, however "other locations" are unaffected and still show
  12-hour clock. See screenshot.

  This is Ubuntu Trusty

  indicator-datetime: 13.10.0+14.04.20140415.3-0ubuntu1

  I expect the Other Locations to also be 24 hour display.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+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 1499075] [NEW] python3.4.3 SRU breaks awscli

2015-09-23 Thread Nelson Elhage
Public bug reported:

The recently (~6h ago) python3.4.3 SRU update contains backwards-
incompatible changes to the Python language, which in particular break
the version of `awscli` packaged in Ubuntu Trusty. From a fully-updated
Trusty machine:

r...@jenkinsworker15.nw:~# aws
Traceback (most recent call last):
  File "/usr/bin/aws", line 23, in 
sys.exit(main())
  File "/usr/bin/aws", line 19, in main
return awscli.clidriver.main()
  File "/usr/share/awscli/awscli/clidriver.py", line 44, in main
driver = create_clidriver()
  File "/usr/share/awscli/awscli/clidriver.py", line 53, in create_clidriver
event_hooks=emitter)
  File "/usr/share/awscli/awscli/plugin.py", line 49, in load_plugins
plugin.awscli_initialize(event_hooks)
  File "/usr/share/awscli/awscli/handlers.py", line 73, in awscli_initialize
register_removals(event_handlers)
  File "/usr/share/awscli/awscli/customizations/removals.py", line 32, in 
register_removals
'verify-email-address'])
  File "/usr/share/awscli/awscli/customizations/removals.py", line 45, in remove
self._create_remover(remove_commands))
  File "/usr/lib/python3/dist-packages/botocore/hooks.py", line 64, in register
self._verify_accept_kwargs(handler)
  File "/usr/lib/python3/dist-packages/botocore/hooks.py", line 84, in 
_verify_accept_kwargs
argspec = inspect.getargspec(func)
  File "/usr/lib/python3.4/inspect.py", line 936, in getargspec
raise ValueError("Function has keyword-only arguments or annotations"
ValueError: Function has keyword-only arguments or annotations, use 
getfullargspec() API which can support them


This bug has been fixed upstream via https://github.com/aws/aws-cli/issues/800, 
but the version in Ubuntu hasn't been updated.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python3.4 3.4.3-1ubuntu1~14.04.1
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Wed Sep 23 21:06:39 2015
Ec2AMI: ami-8d5b5dbd
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2c
Ec2InstanceType: c4.8xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: python3.4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ec2-images trusty

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

Title:
  python3.4.3 SRU breaks awscli

Status in python3.4 package in Ubuntu:
  New

Bug description:
  The recently (~6h ago) python3.4.3 SRU update contains backwards-
  incompatible changes to the Python language, which in particular break
  the version of `awscli` packaged in Ubuntu Trusty. From a fully-
  updated Trusty machine:

  r...@jenkinsworker15.nw:~# aws
  Traceback (most recent call last):
File "/usr/bin/aws", line 23, in 
  sys.exit(main())
File "/usr/bin/aws", line 19, in main
  return awscli.clidriver.main()
File "/usr/share/awscli/awscli/clidriver.py", line 44, in main
  driver = create_clidriver()
File "/usr/share/awscli/awscli/clidriver.py", line 53, in create_clidriver
  event_hooks=emitter)
File "/usr/share/awscli/awscli/plugin.py", line 49, in load_plugins
  plugin.awscli_initialize(event_hooks)
File "/usr/share/awscli/awscli/handlers.py", line 73, in awscli_initialize
  register_removals(event_handlers)
File "/usr/share/awscli/awscli/customizations/removals.py", line 32, in 
register_removals
  'verify-email-address'])
File "/usr/share/awscli/awscli/customizations/removals.py", line 45, in 
remove
  self._create_remover(remove_commands))
File "/usr/lib/python3/dist-packages/botocore/hooks.py", line 64, in 
register
  self._verify_accept_kwargs(handler)
File "/usr/lib/python3/dist-packages/botocore/hooks.py", line 84, in 
_verify_accept_kwargs
  argspec = inspect.getargspec(func)
File "/usr/lib/python3.4/inspect.py", line 936, in getargspec
  raise ValueError("Function has keyword-only arguments or annotations"
  ValueError: Function has keyword-only arguments or annotations, use 
getfullargspec() API which can support them

  
  This bug has been fixed upstream via 
https://github.com/aws/aws-cli/issues/800, but the version in Ubuntu hasn't 
been updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python3.4 3.4.3-1ubuntu1~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Wed Sep 23 21:06:39 2015
  Ec2AMI: ami-8d5b5dbd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: c4.8xlarge
  Ec2Kernel