date:20160303

[Desktop-packages] [Bug 1553061] Re: Default Hysteresis causes poor, sticky and jumpy movement on Logitech T650

2016-03-03 Thread Trent Lloyd

Tested on xenial

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1553061

Title:
Default Hysteresis causes poor, sticky and jumpy movement on Logitech
T650

Status in xserver-xorg-input-synaptics package in Ubuntu:
New

Bug description:
I have a Logitech T650 touch-pad. Out of the box, this device feels
very poor to use because the HorizHysteresis and VertHysteresis
settings are quite high. It is very difficult to make small
movements, and if you want to move slightly diagonally it is basically
impossible. The amount of movement on screen that it jumps is several
mm on a 27" 1080p monitor.

It's hard to explain how horrible this is to use, but I would consider
this "high" on the poor usability factor, not just a minor annoyance.

This setting causes movement to be ignored until it reaches the threshold..
it defaults to 0.5% of the hardwares diagonal size or about "14". This is
designed to reduce noise on some devices, but I suspect the main issue here is
that this is quite a large trackpad that is also very accurate. The hardware
area is 2606x2110 which seems to be at least double most laptop trackpads.

Further testing on similar devices would be required, but this default
algorithm may need some tweaking for device size and to scale better.. but
obviously it is hard to know how this will affect other devices. Otherwise is
there some way to build up a hardware quirks list? Probably not ideal but
better than nothing.

The following significantly improves the feel:
synclient HorizHysteresis=0 VertHysteresis=0

As a side note, the scroll speed is also quite slow which again I
suspect is related to the device being larger than many touch pads.
VertScrollDelta and HorizScrollDelta of -65 work much better than the
default -78 (or +78 for non-natural scrolling)

Neither of these settings can be configured in settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1553061/+subscriptions

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

[Desktop-packages] [Bug 1553061] [NEW] Default Hysteresis causes poor, sticky and jumpy movement on Logitech T650

2016-03-03 Thread Trent Lloyd

Public bug reported:

I have a Logitech T650 touch-pad. Out of the box, this device feels
very poor to use because the HorizHysteresis and VertHysteresis settings
are quite high. It is very difficult to make small movements, and if
you want to move slightly diagonally it is basically impossible. The
amount of movement on screen that it jumps is several mm on a 27" 1080p
monitor.

It's hard to explain how horrible this is to use, but I would consider
this "high" on the poor usability factor, not just a minor annoyance.

This setting causes movement to be ignored until it reaches the threshold.. it
defaults to 0.5% of the hardwares diagonal size or about "14". This is
designed to reduce noise on some devices, but I suspect the main issue here is
that this is quite a large trackpad that is also very accurate. The hardware
area is 2606x2110 which seems to be at least double most laptop trackpads.

The following significantly improves the feel:
synclient HorizHysteresis=0 VertHysteresis=0

Neither of these settings can be configured in settings.

** Affects: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1553061

Title:
Default Hysteresis causes poor, sticky and jumpy movement on Logitech
T650

Status in xserver-xorg-input-synaptics package in Ubuntu:
New

It's hard to explain how horrible this is to use, but I would consider
this "high" on the poor usability factor, not just a minor annoyance.

The following significantly improves the feel:
synclient HorizHysteresis=0 VertHysteresis=0

Neither of these settings can be configured in settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1553061/+subscriptions

[Desktop-packages] [Bug 1481832] Re: VA-API implementation for gallium missing

2016-03-03 Thread Timo Aaltonen

enabling this would mean moving libva to main, and it'd also pull in
ffmpeg and a plethora of other packages..

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1481832

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832/+subscriptions

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

[Desktop-packages] [Bug 1369217] Re: Could not acquire the 'org.freedesktop.ModemManager1' service name

2016-03-03 Thread do

** Changed in: modemmanager (Ubuntu)
   Status: Expired => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1369217

Title:
  Could not acquire the 'org.freedesktop.ModemManager1' service name

Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Get these lines logged into  /var/log/upstart/modemmanager.log

  ModemManager[1104]:   ModemManager (version 1.2.0) starting...
  ModemManager[1104]:   Could not acquire the 
'org.freedesktop.ModemManager1' service name
  ModemManager[1104]:   ModemManager is shut down
  ModemManager[701]:   ModemManager (version 1.2.0) starting...
  ModemManager[701]:   Couldn't find support for device at 
'/sys/devices/pci:00/:00:1c.3/:04:00.0': not supported by any plugin
  ModemManager[701]:   Couldn't find support for device at 
'/sys/devices/pci:00/:00:1c.4/:03:00.0': not supported by any plugin

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: modemmanager 1.2.0-1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:53:09 2014
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1369217/+subscriptions

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

[Desktop-packages] [Bug 1547491] Re: [MIR] xserver-xorg-input-void

2016-03-03 Thread Timo Aaltonen

bumping priority, blocking xserver migration atm

** Changed in: xserver-xorg-input-void (Ubuntu)
   Importance: Undecided => High

** Description changed:

- s390x wants this
+ [Availability]
+ has been in debian/ubuntu for ages
+ 
+ [Rationale]
+ s390x needs this
+ 
+ [Security]
+ a dummy input driver, no security issues
+ 
+ [Quality assurance]
+ no bugs filed besides this
+ 
+ [Dependencies]
+ none
+ 
+ [Standards compliance]
+ packaged just like any other X driver
+ 
+ [Maintenance]
+ maintained in Debian & Ubuntu

** Description changed:

  [Availability]
  has been in debian/ubuntu for ages
  
  [Rationale]
  s390x needs this
  
  [Security]
  a dummy input driver, no security issues
  
  [Quality assurance]
  no bugs filed besides this
  
  [Dependencies]
- none
+ all in main
  
  [Standards compliance]
  packaged just like any other X driver
  
  [Maintenance]
  maintained in Debian & Ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-void in Ubuntu.
https://bugs.launchpad.net/bugs/1547491

Title:
  [MIR] xserver-xorg-input-void

Status in xserver-xorg-input-void package in Ubuntu:
  New

Bug description:
  [Availability]
  has been in debian/ubuntu for ages

  [Rationale]
  s390x needs this

  [Security]
  a dummy input driver, no security issues

  [Quality assurance]
  no bugs filed besides this

  [Dependencies]
  all in main

  [Standards compliance]
  packaged just like any other X driver

  [Maintenance]
  maintained in Debian & Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-void/+bug/1547491/+subscriptions

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

[Desktop-packages] [Bug 1541369] Re: remove stale xorg drivers from the archive

2016-03-03 Thread Timo Aaltonen

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Fix Released

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1541369

Title:
  remove stale xorg drivers from the archive

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in xf86-input-multitouch package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-video-s3 package in Ubuntu:
  New

Bug description:
  No one should be using these since a few years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1541369/+subscriptions

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

[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

2016-03-03 Thread Martin Pitt

> Other FFEs will be opened for NM VPN plugins and for NetworkManager-
applet.

I suspect that they need to be updated in lockstep, so perhaps better
just add tasks here? Or are they really independent from updating NM
itself?

I generally support this as well, but this needs loads of testing across
devices that we have. With that I'm interested in a contingency plan, i.
e. at this point I'd like to make sure that in the worst case we can
roll back. Which other packages would this upgrade affect aside from
network-manager{,-vpn,-applet}?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1552424

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  New

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" command and via
  D-Bus API.
  * The API for VPN plugins now supports multiple simultaneous connections.
  Most popular VPN plugins have been

1 2 3 >

1 - 100 of 207 matches

Mail list logo