[Desktop-packages] [Bug 1442921] Re: Ubuntu-Proposed Catalyst fglrx* 2:15.200 missing link to fglrx_drv_video.so

2015-04-11 Thread Dennis-martin-herbers
Can confirm. Setting the link manually fixes it.

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

Title:
  Ubuntu-Proposed Catalyst fglrx* 2:15.200 missing link to
  fglrx_drv_video.so

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  Hi, i'm testing the new driver Catalyst from ubuntu proposed repo:

  $ sudo apt-get install fglrx-updates fglrx-amdcccle-updates fglrx-
  updates-core fglrx-updates-dev

  hs1974g@unity7:~$ fglrxinfo
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon R7 200 Series   
  OpenGL version string: 4.4.13374 Compatibility Profile Context 15.20.1013

  
  when i checked Hardware Video Decode Acceleration using VA-API :

  hs1974g@unity7:~$ vainfo

  libva info: VA-API version 0.37.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  The link is missing to /usr/lib/x86_64-linux-
  gnu/dri/fglrx_drv_video.so.

  The correct link is:

  $ sudo ln -s /usr/lib/libXvBAW.so.1.0 /usr/lib/x86_64-linux-
  gnu/dri/fglrx_drv_video.so

  after i run ..

  hs1974g@unity7:~$ vainfo

  libva info: VA-API version 0.37.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
  libva info: Found init function __vaDriverInit_0_33
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.37 (libva 1.5.1)
  vainfo: Driver version: AMD MMD 1.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG4Simple:   VAEntrypointVLD
VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
VAProfileMPEG4Main  :   VAEntrypointVLD
VAProfileH264Baseline   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD

  More info (Discussion):

  http://www.phoronix.com/forums/showthread.php?115666-AMD-Will-Release-
  New-Catalyst-Linux-Driver-Update-This-Month/page21

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 2:15.200-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 11 18:10:56 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 15.200, 3.13.0-49-generic, x86_64: installed
   fglrx-updates-core, 15.200, 3.16.0-34-generic, x86_64: installed
   vboxhost, 4.3.26, 3.13.0-49-generic, x86_64: installed
   vboxhost, 4.3.26, 3.16.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X] 
[1002:6658] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2935]
  InstallationDate: Installed on 2015-03-30 (11 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic 
root=UUID=38f9493f-e6c0-4234-a47e-f171cae7154d ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78T-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: com

[Desktop-packages] [Bug 1286552] Re: No wifi after suspend

2015-01-25 Thread Dennis-martin-herbers
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
wpa-supplicant 2.3 and rebooting immediately fixed the issue. I know
that at least some people here had this issue...

https://packages.debian.org/sid/wpasupplicant

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

Title:
  No wifi after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After suspending ubuntu the wifi doesn't work. The solution given here
  (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
  connecting-after-suspend) worked for me but when I have updated my
  Ubuntu now it won't work. I have tried to test mainline kernel but it
  won't to boot with it.

  To reproduce the bug : just suspend the computer and then power it.
  There's no wifi network until you restart the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubuntu-release-upgrader-core 1:0.205.4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashDB: ubuntu
  Date: Sat Mar  1 15:20:39 2014
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradi 1503 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  MachineType: Hewlett-Packard HP Compaq 6830s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116.2
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog: Mar  1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] 
perf samples too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate 
to 25000
  dmi.bios.date: 03/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZD Ver. F.0C
  dmi.board.name: 30E9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 95.1C
  dmi.chassis.asset.tag: CNU91609Y2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6830s
  dmi.product.version: F.0C
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+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 1305857] Re: wireless authentication always times out after standby

2015-01-25 Thread Dennis-martin-herbers
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
wpa-supplicant 2.3 and rebooting immediately fixed the issue.

https://packages.debian.org/sid/wpasupplicant

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

Title:
  wireless authentication always times out after standby

Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  After updating from saucy to trusty, putting the system to standby
  makes wireless stop working after wake up. Rebooting the system fixes
  it until next time standby is entered.

  I've tried various hints about unloading modules, restarting the 
network-manager service or nm-applet, nmcli nm sleep false
  or using rfkill / the hardware kill switch. None of these changed the 
behaviour or seemed wrong. After following 
https://wiki.gnome.org/Projects/NetworkManager/Debugging, I was able to get the 
attached lines in /var/log/syslog.
  The driver works fine after wake up and scanning for networks works too. Upon 
trying authentication, the request fails after 5 seconds with a timeout. I 
managed to make the connection working again by killing wpa_supplicant so it 
must somehow be stuck.

  
  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  (current today, April 10th 2014)

  wpasupplicant version is 2.1-0ubuntu1

  System: Lenovo Thinkpad R61
  Wireless Driver: iwl3945
  $ uname -a
  Linux  3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1305857/+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 1370245] Re: wpa_supplicant version 2.2 available

2015-01-25 Thread Dennis-martin-herbers
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
wpa-supplicant 2.3 and rebooting immediately fixed the issue.

https://packages.debian.org/sid/wpasupplicant

There are a lot of issues related to this that would be fixed by the new
upstream release.

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

Title:
  wpa_supplicant version 2.2 available

Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  Currently version 2.1 is still the version slated to be shipped with
  utopic. It seems from http://w1.fi/wpa_supplicant/ that wpa_supplicant
  version 2.2 was released in 2014-06. Is it possible for 2.2 to be
  packaged?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1370245/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal

2013-01-30 Thread Dennis-martin-herbers
Nice. This is keeping me from Using Ubuntu 12.10.

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

Title:
  FFE: libmessaging-menu transitions for quantal

Status in Gmail Watcher:
  Triaged
Status in Lightread:
  New
Status in Quassel Irc Client:
  New
Status in Skype-wrapper:
  In Progress
Status in “evolution-indicator” package in Ubuntu:
  Triaged
Status in “gm-notify” package in Ubuntu:
  Triaged
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “kdenetwork” package in Ubuntu:
  New
Status in “kdepim” package in Ubuntu:
  New
Status in “libdbusmenu-qt” package in Ubuntu:
  New
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “liferea” package in Ubuntu:
  Triaged
Status in “pidgin” package in Ubuntu:
  Fix Released
Status in “pidgin-libnotify” package in Ubuntu:
  Fix Released
Status in “quassel” package in Ubuntu:
  New
Status in “smuxi” package in Ubuntu:
  Fix Released
Status in “telepathy-indicator” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  Fix Released
Status in “unity-mail” package in Ubuntu:
  Fix Released
Status in “xchat-indicator” package in Ubuntu:
  Fix Released
Status in “gm-notify” source package in Quantal:
  Triaged
Status in “gwibber” source package in Quantal:
  Fix Released
Status in “indicator-messages” source package in Quantal:
  Fix Released
Status in “kdenetwork” source package in Quantal:
  New
Status in “kdepim” source package in Quantal:
  New
Status in “libdbusmenu-qt” source package in Quantal:
  New
Status in “libunity-webapps” source package in Quantal:
  Fix Released
Status in “liferea” source package in Quantal:
  Triaged
Status in “pidgin” source package in Quantal:
  Confirmed
Status in “pidgin-libnotify” source package in Quantal:
  In Progress
Status in “quassel” source package in Quantal:
  New
Status in “smuxi” source package in Quantal:
  Fix Released
Status in “telepathy-indicator” source package in Quantal:
  Fix Released
Status in “thunderbird” source package in Quantal:
  Fix Released
Status in “unity-mail” source package in Quantal:
  Fix Released
Status in “xchat-indicator” source package in Quantal:
  Fix Released

Bug description:
  indicator-messages got updated, introducing a new libmessaging-menu
  api (deprecating the old libindicate library) which should make
  application developper's life easier.

  The indicator work is done and the library is ready and we started
  porting applications

  The current stack is being tested in https://launchpad.net/~ubuntu-
  desktop/+archive/ppa/

  It includes
  - indicator-messages
  - gwibber
  - indicator-telepathy
  - thunderbird (soon, work is being finished)

  which is what we consider the minimal set for landing the feature

  for quantal we will add those soon:
  - pidgin
  - xchat-indicator
  - evolution-indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal

2012-11-16 Thread Dennis-martin-herbers
Will you update your PPA to the v3 patch? Will it get into quantal-
updates at some point?

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

Title:
  FFE: libmessaging-menu transitions for quantal

Status in Gmail Watcher:
  Triaged
Status in Lightread:
  New
Status in Quassel Irc Client:
  New
Status in Skype-wrapper:
  In Progress
Status in “evolution-indicator” package in Ubuntu:
  Triaged
Status in “gm-notify” package in Ubuntu:
  Triaged
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “kdenetwork” package in Ubuntu:
  New
Status in “kdepim” package in Ubuntu:
  New
Status in “libdbusmenu-qt” package in Ubuntu:
  New
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “liferea” package in Ubuntu:
  Triaged
Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “pidgin-libnotify” package in Ubuntu:
  Fix Released
Status in “quassel” package in Ubuntu:
  New
Status in “smuxi” package in Ubuntu:
  Fix Released
Status in “telepathy-indicator” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  Fix Released
Status in “unity-mail” package in Ubuntu:
  Fix Released
Status in “xchat-indicator” package in Ubuntu:
  Fix Released
Status in “gm-notify” source package in Quantal:
  Triaged
Status in “gwibber” source package in Quantal:
  Fix Released
Status in “indicator-messages” source package in Quantal:
  Fix Released
Status in “kdenetwork” source package in Quantal:
  New
Status in “kdepim” source package in Quantal:
  New
Status in “libdbusmenu-qt” source package in Quantal:
  New
Status in “libunity-webapps” source package in Quantal:
  Fix Released
Status in “liferea” source package in Quantal:
  Triaged
Status in “pidgin” source package in Quantal:
  Confirmed
Status in “pidgin-libnotify” source package in Quantal:
  In Progress
Status in “quassel” source package in Quantal:
  New
Status in “smuxi” source package in Quantal:
  Fix Released
Status in “telepathy-indicator” source package in Quantal:
  Fix Released
Status in “thunderbird” source package in Quantal:
  Fix Released
Status in “unity-mail” source package in Quantal:
  Fix Released
Status in “xchat-indicator” source package in Quantal:
  Fix Released

Bug description:
  indicator-messages got updated, introducing a new libmessaging-menu
  api (deprecating the old libindicate library) which should make
  application developper's life easier.

  The indicator work is done and the library is ready and we started
  porting applications

  The current stack is being tested in https://launchpad.net/~ubuntu-
  desktop/+archive/ppa/

  It includes
  - indicator-messages
  - gwibber
  - indicator-telepathy
  - thunderbird (soon, work is being finished)

  which is what we consider the minimal set for landing the feature

  for quantal we will add those soon:
  - pidgin
  - xchat-indicator
  - evolution-indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+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 1058636] Re: system lags with fglrx, Chrome and Vsync

2012-10-25 Thread Dennis-martin-herbers
This is fixed with the AMD Catalyst/fglrx 9.01 release stream (aka
Catalyst 12.11), among other 2D improvements.

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

Title:
  system lags with fglrx, Chrome and Vsync

Status in Chromium Browser:
  New
Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Using the latest Ubuntu 12.10 build, the system stutters (to the point
  that the mouse doesn't move for a few milliseconds, very noticeable
  and annoying) when using the latest AMD Catalyst driver (fglrx 9.000
  from the quantal repository), Google Chrome and overwriting the driver
  software blacklist in about:flags (normally it should be accelerated
  by default anyway, it does with the driver from AMD.com and Ubuntu
  12.04).

  You you hover over some links, like the ones on engadget.com on the
  right (recent reviews), it stutters A LOT. When you go to about:flags
  and check "disable GPU Vsync" it runs smoothly and perfectly fine like
  it did with Compiz 0.9.7.x.

  Also while hovering/moving over links (with Vsync on/off), CPU usage
  goes up till 60% on my quadcore, but that's another story and has
  always been like that).

  I know there's one more Vsync related fix coming with the final compiz
  0.9.8.4 release, but I think I've read it only matters for nVidia.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1058636/+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