[Desktop-packages] [Bug 1927751] [NEW] Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built without Wayland support

2021-05-07 Thread Michael Marley
Public bug reported:

The Impish build of Firefox 89 beta in the PPA seems to be built without
Wayland support.  This of course causes it to work only in XWayland mode
when running in Wayland, but also breaks VAAPI in both environments due
to "DMABUF unavailable by default: Wayland support missing" as reported
in about:support.

I am reporting this here instead of upstream because the upstream builds
are not affected by this issue (they have Wayland and VAAPI working) and
also the Hirsute builds in the PPA have both things working properly.
It seems limited to the Impish builds.  Additionally, if I check the
build logs for Impish, the only mention of Wayland seems to be the build
dependency packages being installed.  If I check the logs for Hirsute, I
see a number of references during the compilation itself.

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built
  without Wayland support

Status in firefox package in Ubuntu:
  New

Bug description:
  The Impish build of Firefox 89 beta in the PPA seems to be built
  without Wayland support.  This of course causes it to work only in
  XWayland mode when running in Wayland, but also breaks VAAPI in both
  environments due to "DMABUF unavailable by default: Wayland support
  missing" as reported in about:support.

  I am reporting this here instead of upstream because the upstream
  builds are not affected by this issue (they have Wayland and VAAPI
  working) and also the Hirsute builds in the PPA have both things
  working properly.  It seems limited to the Impish builds.
  Additionally, if I check the build logs for Impish, the only mention
  of Wayland seems to be the build dependency packages being installed.
  If I check the logs for Hirsute, I see a number of references during
  the compilation itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1927751/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2020-01-09 Thread Michael Marley
It looks like the VAAPI version is gone from the snap store again.  Is
there some reason why this hasn't been merged yet as mentioned in #96?

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1742750] [NEW] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

2018-01-11 Thread Michael Marley
Public bug reported:

Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-connect.patch,
which changes line 38 of /etc/pulse/default.pa to read ".endif### Load
audio drivers statically".  It appears that there are a couple of line
feeds missing here, and having the comment on the same line as the endif
causes pulseaudio not to start.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid
  /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie

2017-08-05 Thread Michael Marley
** Tags removed: patch

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

Title:
  nvidia 304 graphics causes Login loop in Ubuntu Budgie

Status in Ubuntu Budgie:
  New
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia 304 graphics kills budgie-window manager process and causes
  login loop in Ubuntu Budgie.

  Steps:
  - Enter password
  - System shows top bar (half cropped)
  - Sometimes dock  appears
  - Screen goes off (with no signal in monitor)
  - Screen shows login screen again

  System description:
  - OS:  Ubuntu Budgie 17.04 (daily build)
  - GPU: Nvidia GeForce 6150SE nForce 430

  Packages:
  - Budgie Desktop 10.2.9
  - Nvidia Graphics Drivers 304

  Notes:
  The system it's updated (full-upgrade)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1636355] [NEW] In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-24 Thread Michael Marley
Public bug reported:

The title says it all.

** Affects: lirc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-
  uinput executable is not installed

Status in lirc package in Ubuntu:
  New

Bug description:
  The title says it all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636355/+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 1636353] [NEW] In lirc 0.9.4, irexec.service fails to start because the irexec executable is in /usr/bin/, not /usr/sbin/

2016-10-24 Thread Michael Marley
Public bug reported:

Either the file needs to be moved to /usr/sbin/ or the
/lib/systemd/system/irexec.service needs to be updated to point to
/usr/bin/irexec instead.

** Affects: lirc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  In lirc 0.9.4, irexec.service fails to start because the irexec
  executable is in /usr/bin/, not /usr/sbin/

Status in lirc package in Ubuntu:
  New

Bug description:
  Either the file needs to be moved to /usr/sbin/ or the
  /lib/systemd/system/irexec.service needs to be updated to point to
  /usr/bin/irexec instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636353/+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 1571215] Re: Amarok uses mysql config option that is removed in 5.7

2016-04-16 Thread Michael Marley
** Patch added: "mysql57fix.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1571215/+attachment/4638418/+files/mysql57fix.debdiff

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

Title:
  Amarok uses mysql config option that is removed in 5.7

Status in amarok package in Ubuntu:
  In Progress

Bug description:
  The my.cnf file generated by amarok contains the option myisam-recover=FORCE
  This option was replaced by myisam-recover-options in 5.5 and removed in 5.7, 
so the embedded server will fail to start.
  Simply renaming it to myisam-recover-options will fix the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1571215/+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 1571215] Re: Amarok uses mysql config option that is removed in 5.7

2016-04-16 Thread Michael Marley
** Changed in: amarok (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Amarok uses mysql config option that is removed in 5.7

Status in amarok package in Ubuntu:
  In Progress

Bug description:
  The my.cnf file generated by amarok contains the option myisam-recover=FORCE
  This option was replaced by myisam-recover-options in 5.5 and removed in 5.7, 
so the embedded server will fail to start.
  Simply renaming it to myisam-recover-options will fix the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1571215/+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 1571215] Re: Amarok uses mysql config option that is removed in 5.7

2016-04-16 Thread Michael Marley
** Changed in: amarok (Ubuntu)
   Status: New => Confirmed

** Changed in: amarok (Ubuntu)
 Assignee: (unassigned) => Michael Marley (mamarley)

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

Title:
  Amarok uses mysql config option that is removed in 5.7

Status in amarok package in Ubuntu:
  Confirmed

Bug description:
  The my.cnf file generated by amarok contains the option myisam-recover=FORCE
  This option was replaced by myisam-recover-options in 5.5 and removed in 5.7, 
so the embedded server will fail to start.
  Simply renaming it to myisam-recover-options will fix the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1571215/+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 1543546] [NEW] Monitor DPI settings are ignored after upgrade to Xenial

2016-02-09 Thread Michael Marley
Public bug reported:

I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24"
4K) from Wily to Xenial.  Before I did this, applications using all the
toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value
automatically detected from the monitor, causing them to automatically
scale to a usable size.  However, after upgrading to Xenial, GTK3
applications no longer have this behavior.  Instead, they appear at the
normal 96DPI size, causing them to be nearly unreadable due to the small
size of their widgets.

I am currently using GTK3 3.18.7-1ubuntu2,  but the issue has been
occurring since I upgraded to Xenial months ago.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Monitor DPI settings are ignored after upgrade to Xenial

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24"
  4K) from Wily to Xenial.  Before I did this, applications using all
  the toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value
  automatically detected from the monitor, causing them to automatically
  scale to a usable size.  However, after upgrading to Xenial, GTK3
  applications no longer have this behavior.  Instead, they appear at
  the normal 96DPI size, causing them to be nearly unreadable due to the
  small size of their widgets.

  I am currently using GTK3 3.18.7-1ubuntu2,  but the issue has been
  occurring since I upgraded to Xenial months ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1543546/+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 1460345] [NEW] network-manager can cause a continuous IPv6 router solicitation loop

2015-05-30 Thread Michael Marley
Public bug reported:

As described in the upstream bug report
https://bugzilla.redhat.com/show_bug.cgi?id=1207730, network-manager can
cause a continuous IPv6 router solicitation loop.  In my specific case,
a large number of computers running network-manager are on the network.
The resulting storm of traffic overloads the router and knocks computers
not running network-manager off of IPv6.  Could the fix please be
backported?  Thanks!

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  network-manager can cause a continuous IPv6 router solicitation loop

Status in network-manager package in Ubuntu:
  New

Bug description:
  As described in the upstream bug report
  https://bugzilla.redhat.com/show_bug.cgi?id=1207730, network-manager
  can cause a continuous IPv6 router solicitation loop.  In my specific
  case, a large number of computers running network-manager are on the
  network.  The resulting storm of traffic overloads the router and
  knocks computers not running network-manager off of IPv6.  Could the
  fix please be backported?  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460345/+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 1432158] [NEW] network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as long to boot to the login screen

2015-03-14 Thread Michael Marley
Public bug reported:

The enablement of NetworkManager-wait-online.service in network-manager
0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly
twice as long to boot to the login screen.  I did some investigating and
determined that this is because sddm.service depends on systemd-user-
sessions.service which depends on remote-fs.target which depends on
network-online.target which depends on NetworkManager-wait-
online.service.  For that reason, systemd is apparently waiting to start
sddm until both the wired and wireless adapters are connected, which
makes the system take much longer to boot.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: sddm (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: sddm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as
  long to boot to the login screen

Status in network-manager package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  The enablement of NetworkManager-wait-online.service in network-
  manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take
  nearly twice as long to boot to the login screen.  I did some
  investigating and determined that this is because sddm.service depends
  on systemd-user-sessions.service which depends on remote-fs.target
  which depends on network-online.target which depends on
  NetworkManager-wait-online.service.  For that reason, systemd is
  apparently waiting to start sddm until both the wired and wireless
  adapters are connected, which makes the system take much longer to
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432158/+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 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent

2014-11-25 Thread Michael Marley
This is still happening on Kubuntu 14.10.  GTK3 applications like
Synaptic won't scroll unless they are focused.

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

Title:
  Scrolling behaviour and window focus has changed and is inconsistent

Status in Compiz:
  Fix Released
Status in GTK+ GUI Toolkit:
  Fix Released
Status in X.Org X server:
  Confirmed
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xorg-server” package in Ubuntu:
  Won't Fix

Bug description:
  I wasn't sure which package to file this bug against, but seeing as
  it's a general desktop usability/consistency bug, the top level
  desktop environment seemed like a good target.

  On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc),
  except for installing nvidia-319-updates, all current packages as of
  now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have
  this behaviour which is different from Ubuntu versions up to 13.04,
  and, is also inconsistent within itself. Here's what I've found:

  The scrolling behaviour has changed, and seems to be different per
  application in Ubuntu 13.10.

  The old behaviour (up to 13.04): mouse pointer above window would allow 
scrolling, regardless of focus
  Apps that use the old behaviour: libreoffice, firefox, gnome-terminal

  The new behaviour (13.10): window must be focused, and pointer hovered above 
to allow scrolling
  Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater

  
  STEPS TO REPRODUCE

  1. Open gEdit, press enter until the window is scrollable.
  2. Open Firefox, go to a webpage that's scrollable.
  3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar 
is still visible, have gEdit focused.
  4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit 
window to scroll.
  5. Move mouse pointer above Firefox but do not focus Firefox, observe 
scrollwheel causes Firefox window to scroll.
  6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes 
Firefox window to scroll
  7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel 
FAILS to cause gEdit window to scroll.

  
  This behaviour is the same with any combination of the above apps 
(libreoffice, firefox, gnome-terminal all scrollable as long as pointer is 
above them; nautilus, gedit, software-updater, ubunut-bug will not scroll 
unless focused *and* have pointer above them)

  What *SHOULD* happen, is that any window will scroll as long as the
  pointer is above it. That's how it's always been in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Oct 17 22:12:18 2013
  InstallationDate: Installed on 2013-09-30 (17 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1240957/+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 1374825] [NEW] VDPAU does not work in libav on Utopic

2014-09-27 Thread Michael Marley
Public bug reported:

After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support
has stopped working in all applications that use libav.  In mplayer2, it
prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I
get [7f909958] vdpau_avcodec generic error: decoder profile not
supported: 6.

** Affects: libav (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  New

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1374825] Re: VDPAU does not work in libav on Utopic

2014-09-27 Thread Michael Marley
This seems to be due to an API change in libav.  They dropped the old
API for using VDPAU decoding, which broke every application that uses
VDPAU through libav.  https://libav.org/releases/libav-10.5.release

** Also affects: vlc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mplayer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mplayer2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libav (Ubuntu)
   Status: New = Invalid

** Also affects: mpv (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  Invalid
Status in “mplayer” package in Ubuntu:
  New
Status in “mplayer2” package in Ubuntu:
  New
Status in “mpv” package in Ubuntu:
  New
Status in “vlc” package in Ubuntu:
  New

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1276875] [NEW] Since upgrade to xorg-server 1.15, touchpad acceleration behaves erratically

2014-02-05 Thread Michael Marley
Public bug reported:

Since upgrading to xorg-server 1.15, touchpad acceleration behaves
erratically.  Horizontal acceleration is much more pronounced than
vertical acceleration, which makes the cursor difficult to control.

This bug is already fixed by an upstream commit
(http://cgit.freedesktop.org/xorg/driver/xf86-input-
synaptics/commit/?id=0fb59b3487d57523a03f078a2061e2ea0cacbc7c).

** 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/1276875

Title:
  Since upgrade to xorg-server 1.15, touchpad acceleration behaves
  erratically

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

Bug description:
  Since upgrading to xorg-server 1.15, touchpad acceleration behaves
  erratically.  Horizontal acceleration is much more pronounced than
  vertical acceleration, which makes the cursor difficult to control.

  This bug is already fixed by an upstream commit
  (http://cgit.freedesktop.org/xorg/driver/xf86-input-
  synaptics/commit/?id=0fb59b3487d57523a03f078a2061e2ea0cacbc7c).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1276875/+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 1109137] [NEW] upower 0.9.19-1ubuntu1 breaks power management on KDE

2013-01-29 Thread Michael Marley
*** This bug is a duplicate of bug 1108995 ***
https://bugs.launchpad.net/bugs/1108995

Public bug reported:

Updating to upower 0.9.19-1ubuntu1 breaks all power management
functionality on Kubuntu Raring on my Dell Vostro 1500.  After upgrading
and rebooting, the battery applet does not detect the battery and states
that the AC adapter is unplugged, even though it is not.  Also, the
Suspend option is missing from the KDE launcher.  Reverting to the
previous version (0.9.19-1) causes the power management to begin working
again.

I can provide more system information if necessary, but I don't really
think that is applicable considering the simplicity of the changes
between the two versions.

** Affects: upower (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  upower 0.9.19-1ubuntu1 breaks power management on KDE

Status in “upower” package in Ubuntu:
  New

Bug description:
  Updating to upower 0.9.19-1ubuntu1 breaks all power management
  functionality on Kubuntu Raring on my Dell Vostro 1500.  After
  upgrading and rebooting, the battery applet does not detect the
  battery and states that the AC adapter is unplugged, even though it is
  not.  Also, the Suspend option is missing from the KDE launcher.
  Reverting to the previous version (0.9.19-1) causes the power
  management to begin working again.

  I can provide more system information if necessary, but I don't really
  think that is applicable considering the simplicity of the changes
  between the two versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1109137/+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