[Desktop-packages] [Bug 1633855] Re: akonadi fails to start after upgrade to yakkety

[Flames_in_Paradise]

That ppa from comment #10 here seems to be gone?

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

Title:
  akonadi fails to start after upgrade to yakkety

Status in akonadi package in Ubuntu:
  Triaged
Status in akonadi source package in Precise:
  Fix Released
Status in mysql-5.5 source package in Precise:
  Confirmed
Status in akonadi source package in Trusty:
  Fix Released
Status in mysql-5.5 source package in Trusty:
  Confirmed
Status in akonadi source package in Yakkety:
  Confirmed
Status in mysql-5.5 source package in Yakkety:
  Confirmed
Status in akonadi source package in Zesty:
  Triaged
Status in mysql-5.5 source package in Zesty:
  Confirmed

Bug description:
  After yesterday 15 sept. upgrade to Kubuntu 16.10 Yakkety Yak, kmail
  fails to start, because akonadi backend fails.

  Starting akonadi from command line, 
  $ akonadictl start
  the output contains:
 stderr: "mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - 
No such file or directory)\n2016-10-16T11:54:23.365277Z 0 [Warning] The syntax 
'--log_warnings/-W' is deprecated and will be removed in a future release. 
Please use '--log_error_verbosity' instead.\n2016-10-16T11:54:23.365377Z 0 
[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use 
--explicit_defaults_for_timestamp server option (see documentation for more 
details).\n2016-10-16T11:54:23.365479Z 0 [ERROR] Failed to access directory for 
--secure-file-priv. Please make sure that directory exists and is accessible by 
MySQL Server. Supplied value : 
/var/lib/mysql-files\n2016-10-16T11:54:23.365488Z 0 [ERROR] 
Aborting\n\n2016-10-16T11:54:23.365508Z 0 [Note] Binlog end\n"

  The cause is a regression in the file 
  /etc/xdg/akonadi/mysql-global.conf
  provided by the package
  akonadi-backend-mysql

  Diff of the content of mysql-global.conf from Yakkety vs Xenial:
  

  diff -u "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf" 
"akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf" 
  --- "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf"  
  2016-06-24 15:51:12.0 +0200
  +++ "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf"  
  2016-04-20 10:42:09.0 +0200
  @@ -100,5 +100,14 @@
   # We use InnoDB, so don't let MyISAM eat up memory
   key_buffer_size=16K
   
  +# KUBUNTU:
  +# Unset the export dir check as only the full mysql-server package creates it
  +secure_file_priv=
  +
  +# KUBUNTU:
  +# workaround for 5.7 being more strict with column types
  +# (reverts to 5.6 behavior)
  +sql_mode=NO_ENGINE_SUBSTITUTION
  +
   [client]
   default-character-set=utf8

  

  Applying this patch fixes the bug.

  The "secure_file_priv" setting went missing is referenced in the package 
changelog:
 akonadi (4:15.12.3-0ubuntu5) xenial; urgency=medium

   * kubuntu_disable_secure_file_priv_check.diff:
  - Set secure_file_priv to empty as that directory is not set in a default
kubuntu install

  -- Philip Muškovac   Mon, 18 Apr 2016 15:24:43
  +0200

  Marco Gamberoni

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1633855/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

@ wxl: I've subscribed u to this bug, as it possibly could be tackled
for 16.04.2 ?

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

** Changed in: kubuntu-ppa
 Assignee: Greg (gcstatter) => (unassigned)

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

** Description changed:

  Installing from Kubuntu 15.04 backports:
  
  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  
- 
  SRU information
  ===
  
- [Impact] It's not possible to install KDE and Unity because of several
- file conflicts: many files under
+ [Impact] It's not possible to install KDE and Unity in co-existence
+ because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
- pluigins" source package, for example account-plugin-facebook.
+ plugins" source package, for example 'account-plugin-facebook'.
  
  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).
  
  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

@ bdresler:

Bitte akzeptiere, dass die Fehlerberichterstellung mit kleinstem
gemeinsamer Nenner in englischer Sprache stattfindet.

Please accept that bug-reporting takes place in english. As a unique
exception I did a free translation.  – (Als einmalige, ausserordentliche
Ausnahme habe ich Dir den Text übersetzt - für weitere Fragen nutze doch
bitte einfach Ubuntuusers.de , (lokales Hilfe-Forum)).

-> https://paste.ubuntu.com/23586350/

@ mardy: I'm not completely familiar with SRU-updates [1], but it may
certainly help to subscribe a sponsor as outlined there in 3.0.5 . They
definetly prefer to have 'debdiff'. Thanks for caring!

[1] https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which

[Flames_in_Paradise]

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  showing this error when installing kde environment in ubuntu 16.04. it
  say kaccounts  niot installed. so i think it may cause some security
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 27 18:11:18 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
    trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-08-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1617564/+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 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Flames_in_Paradise]

Various bugfixes were implemented in LightDM V. 1.18.2-0ubuntu1 [1]

This package is still awaiting approval as it covers a few issues...


The bugs are referenced there. Hope this helps.


[1] https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1


found via Pending Ubuntu SRU's: 
http://people.canonical.com/~ubuntu-archive/pending-sru

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

  IRC discussion at:

https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+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 1572497] Re: powerpc segfault with Qt 5.6

[Flames_in_Paradise]

** Tags added: xenial

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

Title:
  powerpc segfault with Qt 5.6

Status in gsettings-qt package in Ubuntu:
  New

Bug description:
  Build log at :
  
https://launchpadlibrarian.net/254349222/buildlog_ubuntu-xenial-powerpc.gsettings-qt_0.1+16.04.20160329-0ubuntu2~xenialoverlay1~2_BUILDING.txt.gz

  /«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/target_wrapper.sh  ./test  
-import "/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/.."
  Segmentation fault

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1572497/+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 1572496] Re: s390x build/run failure with Qt 5.6

[Flames_in_Paradise]

** Tags added: xenial

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

Title:
  s390x build/run failure with Qt 5.6

Status in gsettings-qt package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Ubuntu UI Toolkit FTBFS:s on s390x when used with Qt 5.6:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-011/+build/9600469 (Error: SEGV)

  gsettings-qt segmentation fault is similar and may be faster to debug
  https://launchpadlibrarian.net/254348976/buildlog_ubuntu-xenial-s390x
  .gsettings-
  qt_0.1+16.04.20160329-0ubuntu2~xenialoverlay1~2_BUILDING.txt.gz

  It is probably during executing 'qmlplugindump' (via build time Qt
  generated wrapper.sh script), which is from qtdeclarative-opensource-
  src.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1572496/+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 1547826] Re: [FFe] Enable libappindicator support

[Flames_in_Paradise]

** Summary changed:

- [FFe]Enable libappindicator support
+ [FFe] Enable libappindicator support

** Tags added: xenial

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

Title:
  [FFe] Enable libappindicator support

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  It appears an FFe is needed at this stage in Xenial cycle, thus
  changing the bug status.

  
  ---Original Report
  Please enable libappindicator support.
  This feature is good at KDE 5.
  https://desktopi18n.wordpress.com/2015/07/21/ibus-1-5-11-is-released/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1547826/+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 1505660] Re: ~/.cache/upstart/startkde.log fills up every available disk space

[Flames_in_Paradise]

@Vargnatt: I have been writing this to the original bug-reporter, as he
has been given valuable information.

 -> resource://gre/modules/commonjs/sdk/loader/sandbox.js -> resource
://ytda-at-notsie-dot-com/ytda/data/engine.js

This can be clearly identified.

@ Seth Arnold:

>> (Seriously, running firefox or (many? most? all?) kde programs from a
shell is illuminating. And painful.)

I do not accept any kind of offensive distro-bashing. If this happens
again in my presence, you may be assured that an incident as such will
be reported as violence to the code of conduct in a formal complaint
within the Ubuntu-community. As a user of Kubuntu since 8.04 I do feel
personnaly offended with unrelated comments as such.

For now I will accept a friendly apology to settle this matter, timely.

** Changed in: kubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  ~/.cache/upstart/startkde.log fills up every available disk space

Status in firefox package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  Invalid
Status in openjdk-7 package in Ubuntu:
  New

Bug description:
  I've recently discovered that ~/.cache/upstart/startkde.log is growing
  uncontrollably until a point it fills up my whole Linux partition. As
  I see, it's only filled with an endless recursion of the same error
  message:

  Object
- prototype Object
  console.error: ytda: 
  Object
- prototype Object
  console.error: ytda: 
  Object
  - _errorType = Error
  - message = document.getElementsByClassName(...)[0].click is undefined
  - fileName = resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://gre/modules/commonjs/sdk/loader/sandbox.js -> 
resource://ytda-at-notsie-dot-com/ytda/data/engine.js
  - lineNumber = 16
  - stack = checkDIV@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://gre/modules/commonjs/sdk/loader/sandbox.js -> 
resource://ytda-at-notsie-dot-com/ytda/data/engine.js:16:3|oInv<@resource://gre/modules/commonjs/toolkit/loader.js
 -> resource://gre/modules/commonjs/sdk/loader/sandbox.js -> 
resource://ytda-at-notsie-dot-com/ytda/data/engine.js:1:33|onFire@resource://gre/modules/commonjs/toolkit/loader.js
 -> resource://gre/modules/commonjs/sdk/loader/sandbox.js -> 
resource://gre/modules/commonjs/sdk/content/content-worker.js:149:11|
  - name = TypeError
  console.error: ytda: 


  I also observed that this behavior is probably triggered by Firefox
  (version 41.0.1). If I stop it, the log file doesn't grow faster than
  normal, if I start it, it logs again madly.

  I'm currently on Kubuntu 14.04.3 LTS (kernel 3.16.0-50-generic).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1505660/+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 1496980] Re: hp-plugin-ubuntu and hp-plugin-ubuntu -h does nothing but print a file path

[Flames_in_Paradise]

Also fixes bug #1527001 (hp-plugin hangs at invisible sudo prompt after
download of plugin files)

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

Title:
  hp-plugin-ubuntu and hp-plugin-ubuntu -h does nothing but print a file
  path

Status in hplip package in Ubuntu:
  Fix Released

Bug description:
  `hp-plugin-ubuntu` and `hp-plugin-ubuntu -h` prints `/usr/bin/hp-
  toolbox`. There's no way to figure out what the program does or is
  supposed to do.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Sep 17 20:46:43 2015
  InstallationDate: Installed on 2015-09-14 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat:
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn: 
hp:/net/HP_Color_LaserJet_MFP_M476dn?ip=192.168.178.41
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB): 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
   device for Hewlett-Packard-hp-LaserJet-4200: 
hp:/net/hp_LaserJet_4200?ip=141.20.27.45
   device for HP-Color-LaserJet-MFP-M476dn: 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'Hewlett-Packard-hp-LaserJet-4200.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn.ppd', 
'/etc/cups/ppd/HP-Color-LaserJet-MFP-M476dn.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB).ppd'] failed 
with exit code 2: /etc/cups/ppd/Hewlett-Packard-hp-LaserJet-4200: HP LaserJet 
4200 Series Postscript (recommended)
   Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn: HP Color LaserJet Pro MFP M476 
Postscript (recommended)
   grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M476dn.ppd: Keine Berechtigung
   Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB): HP Color LaserJet Pro MFP 
M476 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic 
root=UUID=ca5b3a35-462e-4adb-90e2-d00e286062ae ro rootflags=subvol=@
  SourcePackage: hplip
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1496980/+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 1527001] Re: hp-plugin hangs at invisible sudo prompt after download of plugin files

[Flames_in_Paradise]

This bug was fixed in the package hplip - 3.15.7-0ubuntu4

---
hplip (3.15.7-0ubuntu4) wily; urgency=low

  * debian/local/scripts/hp-plugin-ubuntu: Use pkexec instead of
gksu (LP: #1496980).

 -- Till Kamppeter  Thu, 17 Sep 2015 21:24:00
-0300


** Changed in: hplip (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  hp-plugin hangs at invisible sudo prompt after download of plugin
  files

Status in hplip package in Ubuntu:
  Fix Released

Bug description:
  After downloading the plugin files with the recommended method and
  accepting the license agreement the installation routine hangs
  (doesn't proceed over multiple hours without any CPU or I/O load)
  after output `Number of files to install: 42` which is likely to be
  caused by a spawned process with the `cmdline`
  `/usr/bin/sudo/usr/bin/pythoninstallPlugin.py` which might request the
  user's `sudo` password which isn't visible for the user (and expected
  to be requested in a dialog anyway).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: hplip (not installed)
  Uname: Linux 4.3.0-040300-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 17 01:22:41 2015
  InstallationDate: Installed on 2015-12-12 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1527001/+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 286858] Re: Gwenview destroys EXIF info when rotating images!

[Flames_in_Paradise]

** Tags added: karmic

** Tags removed: karmic
** Tags added: intrepid

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

Title:
  Gwenview destroys EXIF info when rotating images!

Status in KDE Graphics:
  Won't Fix
Status in exiv2 package in Ubuntu:
  Fix Released

Bug description:
  What else can I say? This is KDE4 / Kubuntu 8.10.
  It works as expected in KDE3 / Kubuntu 8.04.
  This bug is critical (for this application) from my point of view as all the 
EXIF info is lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdegraphics/+bug/286858/+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 1537502] Re: GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

[Flames_in_Paradise]

Luca,

I've setup a bug-report [1], asking for a newer version of amdgpu for
Wily. Don't know yet, if this is possible – but should think so.


[1] bug #1557811

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

Title:
  GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

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

Bug description:
  Using the latest ubuntu 15.10 with fglrx-updates driver, a sapphire
  AMD R9 380 the fans are not moving even with an intensive OpenGL game
  opened, the temperature are very high but the fans still not even
  moving a bit.

  fglrxinfo
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon (TM) R9 380 Series 
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates 2:15.201-0ubuntu2~15.10.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Sun Jan 24 16:25:06 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e308]
  InstallationDate: Installed on 2016-01-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:7603 Microdia 
   Bus 001 Device 003: ID 04d9:a09f Holtek Semiconductor, Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=8a5e4c67-7489-410e-83b7-6d57e2f8cae9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.30
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.30:bd12/18/2015:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jan 24 16:13:56 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1537502] Re: GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

[Flames_in_Paradise]

Luca,

you may catch some interest in an article from Softpedia (Mar 10, 2016):

http://news.softpedia.com/news/canonical-recommends-open-source-amdgpu-
and-radeon-drivers-for-ubuntu-16-04-lts-501556.shtml

So, to correct me, the open-source-"driver" for your graphics (R9) is
xserver-xorg-video-amdgpu . It's installed by default. Upon purge of
fglrx, it should get selected as by default for ur graphics. To follow
this see log-file: /var/log/gpu-manager-log.

As u can see [1] the provided version for Wily is rather old. You could
test the newer version by incorporating the OIBAF-ppa into your Wily-
Installation, since it doesn't have LTS-Enablement-Stack. I have this
since a while in use in Wily with the most current mainline Kernel and
tested also if ppa-purge works. It does. Mentioning this, because u
should do so before an upgrade to 16.04.

Just for the completeness: Usage of PPA can lead to unexspected results
and can eventually cause instabilities of a system.


[1] 
http://packages.ubuntu.com/search?keywords=xserver-xorg-video-amdgpu=names=all=all

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

Title:
  GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

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

Bug description:
  Using the latest ubuntu 15.10 with fglrx-updates driver, a sapphire
  AMD R9 380 the fans are not moving even with an intensive OpenGL game
  opened, the temperature are very high but the fans still not even
  moving a bit.

  fglrxinfo
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon (TM) R9 380 Series 
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates 2:15.201-0ubuntu2~15.10.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Sun Jan 24 16:25:06 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e308]
  InstallationDate: Installed on 2016-01-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:7603 Microdia 
   Bus 001 Device 003: ID 04d9:a09f Holtek Semiconductor, Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=8a5e4c67-7489-410e-83b7-6d57e2f8cae9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.30
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.30:bd12/18/2015:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  

[Desktop-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

[Flames_in_Paradise]

** Tags added: xenial

** Tags added: cjk

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1424466] Re: Devel package not installable in 14.04.2

[Flames_in_Paradise]

@ ludoangot:

If you have questions pls go there:
https://answers.launchpad.net/ubuntu/+source/mesa

This bug was fixed & closed.

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

Title:
  Devel package not installable in 14.04.2

Status in apt package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Confirmed
Status in mesa source package in Trusty:
  Fix Released

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

   sudo apt-get install freeglut3-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1424466/+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 1307176] Re: Resolution limited to 1024x768

[Flames_in_Paradise]

> Monitor used is plugged on DVI with a DVI-to-VGA passive adapter

With such an Adapter U just don't get the EDID transported well (not at
all). This ugly truth hits up sometimes in the Help-forums. So just
don't use or U have to fill in the information manually.

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

Title:
  Resolution limited to 1024x768

Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  Bug reported with xdiagnose.

  # Summary

  On installing Ubuntu 13.10 or 14.04 on a NTA3500 nettop with a VGA
  monitor HP vs19e (native resolution 1280x1024), a resolution of
  1024x768 is obtained.

  The bug is not that the correct resolution cannot be obtained at all
  (there's a workaround below with xrandr) but about the fact that is is
  not automatically selected despite good EDID data available from
  monitor.

  # Details

  Machine has two video output ports: HDMI and DVI.
  No monitor is plugged on HDMI.
  Monitor used is plugged on DVI with a DVI-to-VGA passive adapter.

  The open-source driver is used.
  xrandr and graphical tools don't offer more than 1024x768 on this screen.

  xrandr output:

  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
  DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
 1280x1024  60.0 +   75.0  
 1152x864   75.0  
 1024x768   75.1 70.1 60.0* 
 832x62474.6  
 800x60072.2 75.0 60.3  
 640x48075.0 72.8 60.0  
 720x40070.1  
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 
0mm
 1024x768   60.0* 
 800x60060.3 56.2  
 848x48060.0  
 640x48059.9  

  
  # EDID information

  sudo get-edid | parse-edid

  This is read-edid version 3.0.1. Prepare for some fun.
  Attempting to use i2c interface
  Looks like no busses have an EDID. Sorry!
  Attempting to use the classical VBE interface

Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful

VBE version 300
VBE string at 0xc01cc "AMD ATOMBIOS"

  VBE/DDC service about to be called
Report DDC capabilities

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful

Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer

  Reading next EDID block

  VBE/DDC service about to be called
Read EDID

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful

  Checksum Correct

  Section "Monitor"
Identifier "HP vs19e"
ModelName "HP vs19e"
VendorName "HWP"
# Monitor Manufactured week 23 of 2006
# EDID version 1.3
# Analog Display
DisplaySize 380 300
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-83
VertRefresh 50-76
# Maximum pixel clock is 140MHz
#Not giving standard mode: 1280x1024, 60Hz
Modeline"Mode 0" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 
+hsync +vsync 
  EndSection
  Looks like VBE was successful. Have a good day.

  # Additional information, comparison

  Same monitor was used on various machines, bug only happens on this
  machine.

  With no change to hardware, when using ATI proprietary driver,
  1280x1024 is available by default (no need for a workaround).

  # Workaround

  A similar problem was reported on
  http://askubuntu.com/questions/207716/ubuntu-12-10-resolution-stuck-
  at-1024x768-using-open-source-radeon-driver .

  The following sequence allows to get a proper resolution with open-
  source driver once.

  cvt 1280 1024 60
  xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 
1034 1063 -hsync +vsync
  xrandr --addmode VGA-0 1280x1024_60.00
  xrandr --output DVI-0 --off --output VGA-0 --mode 1280x1024_60.00

  # Offer for help

  What can I do to improve Ubuntu so that other users (including me when
  I do a clean Ubuntu install in the future) automatically get correct
  resolution ?

  How to diagnose the reason why the correct resolution as reported by
  the monitor is not used by open-source driver ?

  
  Thank you for your attention


lsb_release -rd

  Description:  Ubuntu 14.04 LTS
  Release:  14.04


  LC_ALL=C apt-cache policy xorg

  xorg:
Installed: 1:7.7+1ubuntu8
Candidate: 1:7.7+1ubuntu8
Version table:
   *** 1:7.7+1ubuntu8 

[Desktop-packages] [Bug 1537502] Re: GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

[Flames_in_Paradise]

Luca

***ATTENZIONE***

With fans NOT running you risk high potential running into serious
hardware damage.

Have you tried RADEON?

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

Title:
  GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

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

Bug description:
  Using the latest ubuntu 15.10 with fglrx-updates driver, a sapphire
  AMD R9 380 the fans are not moving even with an intensive OpenGL game
  opened, the temperature are very high but the fans still not even
  moving a bit.

  fglrxinfo
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon (TM) R9 380 Series 
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates 2:15.201-0ubuntu2~15.10.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Sun Jan 24 16:25:06 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e308]
  InstallationDate: Installed on 2016-01-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:7603 Microdia 
   Bus 001 Device 003: ID 04d9:a09f Holtek Semiconductor, Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=8a5e4c67-7489-410e-83b7-6d57e2f8cae9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.30
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.30:bd12/18/2015:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jan 24 16:13:56 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1537502] Re: GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

[Flames_in_Paradise]

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

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

Title:
  GPU fans NOT MOVING with fglrx driver also with 100% GPU usage

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

Bug description:
  Using the latest ubuntu 15.10 with fglrx-updates driver, a sapphire
  AMD R9 380 the fans are not moving even with an intensive OpenGL game
  opened, the temperature are very high but the fans still not even
  moving a bit.

  fglrxinfo
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon (TM) R9 380 Series 
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates 2:15.201-0ubuntu2~15.10.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Sun Jan 24 16:25:06 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e308]
  InstallationDate: Installed on 2016-01-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:7603 Microdia 
   Bus 001 Device 003: ID 04d9:a09f Holtek Semiconductor, Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=8a5e4c67-7489-410e-83b7-6d57e2f8cae9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.30
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.30:bd12/18/2015:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jan 24 16:13:56 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

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

-- 

[Desktop-packages] [Bug 343716] Re: KIO filebrowser in amarok doesn't play files on a network share (smb/sftp)

[Flames_in_Paradise]

@ AdlerHorst: This bug-report was closed.  The version of Ubuntu this
bug was reported against is no longer maintained.

Jaunty Jackelope 9.04 has reached it's end fo lifecycle, EOL  on Oct.,
23 2010

You may find a list of curent supported versions of Ubuntu:
https://wiki.ubuntu.com/Releases

If you are suffering from an issue in a newer, supported  version pls.
consider to open a new bug-report against this package.

You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.




** Tags removed: networkfile
** Tags added: eol jaunty karmic

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

Title:
  KIO filebrowser in amarok doesn't play files on a network share
  (smb/sftp)

Status in Amarok:
  Fix Released
Status in amarok package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: amarok

  1)  System information: Kubuntu 9.04 Alpha 5 with all updates till
  today (2009-03-16)

  2)  Package Information - amarok:
Installed: 2:2.0.2mysql5.1.30-0ubuntu1
Candidate: 2:2.0.2mysql5.1.30-0ubuntu1
Version table:
   *** 2:2.0.2mysql5.1.30-0ubuntu1 0
  500 http://archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

  3)  browse and play files in amarok on network shares using the
  filebrowser build into amarok (kio browser)

  4) The file browser in amarok on KDE allows browsing a network folder but 
can't play any files. 
  Test I carried out:
  smb folder mapped in Dolphin - > browse: ok; play: fail
  sftp folder mapped in Dophin -> browse: ok; play fail
 both checked with filenames which contain no whitespaces with the same 
result
  drag from konqueror into the playlist of amarok -> doesn't work

  sshfs folder mapped under /mnt -> browse ok; play: ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/amarok/+bug/343716/+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 1283820] Re: content of windows (and desktop) appear black when using kwin, but not with kwin_gles - intel graphics

[Flames_in_Paradise]

https://wiki.ubuntu.com/Bugs/Bug%20status

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

Title:
  content of windows (and desktop) appear black when using kwin, but not
  with kwin_gles - intel graphics

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  
  When I start a session all my windows appear in black as well as my desktop 
if using kwin. This behavior is not entirely deterministic, it occurs about 75% 
of the times. I have an intel graphic card, and same thing happens no matter 
sna or uxa is used.

  This doesn't happen if using kwin_gles instead (but I don't use it
  because then the blur effect doesn't work). Please let me know if I
  should fill a bug in kde as well...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kde-window-manager 4:4.11.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 15:51:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-07-27 (942 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcEnviron:
   LANGUAGE=ca:ca@valencia:en_US:en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: kde-workspace
  UpgradeStatus: Upgraded to trusty on 2014-02-17 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1283820/+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 1283820] Re: content of windows (and desktop) appear black when using kwin, but not with kwin_gles - intel graphics

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  content of windows (and desktop) appear black when using kwin, but not
  with kwin_gles - intel graphics

Status in KDE Base Workspace:
  Unknown
Status in kde-workspace package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  
  When I start a session all my windows appear in black as well as my desktop 
if using kwin. This behavior is not entirely deterministic, it occurs about 75% 
of the times. I have an intel graphic card, and same thing happens no matter 
sna or uxa is used.

  This doesn't happen if using kwin_gles instead (but I don't use it
  because then the blur effect doesn't work). Please let me know if I
  should fill a bug in kde as well...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kde-window-manager 4:4.11.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 15:51:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-07-27 (942 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcEnviron:
   LANGUAGE=ca:ca@valencia:en_US:en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: kde-workspace
  UpgradeStatus: Upgraded to trusty on 2014-02-17 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1283820/+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 1538524] Re: Update to 1.6.3

[Flames_in_Paradise]

Tested all of these packages on Wily (Kubuntu). Absolutely no problems
at all.. Thanks.

** Tags removed: verification-done-wily
** Tags added: verification-done wily

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

Title:
  Update to 1.6.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-base1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-good1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Wily:
  Fix Committed
Status in gstreamer1.0 source package in Wily:
  Fix Committed

Bug description:
  [ Description ]

  We should stick with upstream's stable bugfix releases in 15.10

  [ Test plan & QA ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  This is a pure bugfix release, but there is always a chance that one
  of the fixes could be wrong.

  [ Development release ]

  Xenial is on a different 1.7 series and will be on 1.8 by release. All
  commits to the stable branch should come from the master branches that
  1.7 releases are made from, although there might be slight differences
  in release timing that means one is released before the other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1538524/+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 1538331] Re: Akonadi: Please package fix for 1.13 into Kubuntu 14.04 packages

[Flames_in_Paradise]

** Changed in: akonadi (Ubuntu)
   Status: New => Confirmed

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

Title:
  Akonadi: Please package fix for 1.13 into Kubuntu 14.04 packages

Status in akonadi package in Ubuntu:
  Confirmed

Bug description:
  I am a very happy user of the Kubuntu Backports PPA, but have recently
  been bitten by this bug here:

  https://bugs.kde.org/show_bug.cgi?id=341884

  Is there any chance you guys could please package the fix from here

  https://bugs.kde.org/show_bug.cgi?id=341884#c11

  It is here in git:
  
http://quickgit.kde.org/?p=akonadi.git=commit=9c0dc6b3f0826d32eac310b2e7ecd858ca3df681

  The tagging / branching is not great, so I can see why it has not been
  picked up.

  I have had a chat with Scarlet who suggested that this might have been
  packaged already by Jonathan, but despite running off the Kubuntu PPA
  + Backports PPA, I was still bitten by the underlying bug that causes
  Akonadi to duplicate data and effectively eat my SSD.

  The workarounds in the KDE bug work, as in akonadi fsck and then rm
  -rf .local/share/akonadi/file_lost+found; but the writes (35 GB /
  2hrs) wear out my SSD and force me to fstrim all the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1538331/+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 200462] Re: Copying Files From CD/DVD Sets Permissions To Read Only

[Flames_in_Paradise]

** Tags removed: regression-release
** Tags added: hardy lucid

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

Title:
  Copying Files From CD/DVD Sets Permissions To Read Only

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Hardy:
  Won't Fix

Bug description:
  Binary package hint: nautilus

  When I copy files from a CD or DVD to my Home directory, the files
  that are copied are given read only permissions. Prior to Hardy, the
  user that copied the files would have read/write permissions.

  Steps to reproduce:
  1.) Burn a data cd or dvd
  2.) Copy the files to your Desktop or Home directories
  3.) The files that were saved will be read only

  Regression Details
  Discovered in version: gvfs 0.2.3-0ubuntu4? (8.04)
  Last known good version: nautilus 1:2.20.0-0ubuntu7? (7.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/200462/+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 1548583] Re: Latest fglrx-installer update for Ubuntu 14.04.1 caused total crash of 3d rendering system

[Flames_in_Paradise]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1548583

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


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

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

Title:
  Latest fglrx-installer update for Ubuntu 14.04.1 caused total crash of
  3d rendering system

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Running Linux Mint 17.3 based on Ubuntu 14.04.1. Just updated on
  February 21st, 2016 through the update manager. Next time I attempted
  to log into Cinnamon Desktop, it was unable to start and all 3d
  dependent programs were non-functional. The system defaulted to the
  basic 2d drivers. 3d dependent WINE programs such as WoW failed to
  start and system acts like 3d hardware acceleration isn't even there.
  Had to install LXDE and revert to recommended xserver drivers in order
  to make system usable again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1548583/+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 95940] Re: No way to reset ALSA state from GUI

[Flames_in_Paradise]

** Tags added: hardy

** Tags added: jaunty

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

Title:
  No way to reset ALSA state from GUI

Status in gnome-applets:
  Won't Fix
Status in KDE Multimedia:
  New
Status in gnome-applets package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in gnome-applets source package in Hardy:
  Won't Fix
Status in linux source package in Hardy:
  Invalid
Status in linux-source-2.6.20 source package in Hardy:
  Won't Fix

Bug description:
  There is no way to reset the ALSA state from the mixer applet.

  Several users have found that they lose sound, and that the problem
  turns out to be an asound.state file which does not work for their
  hardware. It has not been established how the file came to be corrupt
  or whether the problem was caused by upgrades to newer versions which
  did not handle the file as written by the previous version. It has not
  been established what aspect of the asound.state files caused the
  problem. But several approaches can fix the problem:

1. Removing the ALSA modules, deleting the asound.state file, and
  reloading the modules. This is difficult to do for non-expert users,
  because applications such as the Gnome mixer and volume control can be
  using the modules, preventing their unloading.

2. Removing the ALSA modules, and editing the asound.state to an
  ultra-minimal state that reflects only the primary card, and reloading
  the modules.

   3. Invoking the alsa-utils "reset" option. On Ubuntu, typing this
  fixes the problem for Intel sound cards:

   /etc/init.d/alsa-utils reset Intel

  The latter option is thought to be best, because it doesn't require
  unloading and reloading modules.

  It would be very useful to be able to invoke that "reset" command from
  the GUI Gnome mixer applet, which is why this bug has been filed on
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-applets/+bug/95940/+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 1458220] Re: [master] system keyboard layout not honored

[Flames_in_Paradise]

** Tags added: kubuntu wily xenial

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

Title:
  [master] system keyboard layout not honored

Status in sddm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in sddm package in Mandriva:
  In Progress

Bug description:
  I'm on a fresh install of Kubuntu:
  Description:Ubuntu 15.04
  Release:15.04

  I chose German as installation language, de with nodeadkeys as
  keyboard and locale is set to de_DE.UTF-8.

  The console uses the correct keyboard, however when logging into sddm,
  the keyboard layout is set to US.

  SDDM doesn't seem to honour the keyboard configured during
  installation.

  SDDM installed is:
  ddm:
Installiert:   0.11.0-0ubuntu10
Installationskandidat: 0.11.0-0ubuntu10
Versionstabelle:
   *** 0.11.0-0ubuntu10 0
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  I believe it's a bug since the keyboard layout at login window after
  installing as described above should be the default system one, german
  in the above case.

  I have tried all sorts of ways (including some ugly hacks) to get this
  resolved on a previous installation but didn't find a way. Considering
  the many moving parts to get the login manager up and running, I'm
  aware this might be filed against the wrong package. It might even be
  an installer bug.

  
  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1458220/+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 1458220] Re: system keyboard layout not honored

[Flames_in_Paradise]

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  system keyboard layout not honored

Status in sddm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in sddm package in Mandriva:
  Unknown

Bug description:
  I'm on a fresh install of Kubuntu:
  Description:Ubuntu 15.04
  Release:15.04

  I chose German as installation language, de with nodeadkeys as
  keyboard and locale is set to de_DE.UTF-8.

  The console uses the correct keyboard, however when logging into sddm,
  the keyboard layout is set to US.

  SDDM doesn't seem to honour the keyboard configured during
  installation.

  SDDM installed is:
  ddm:
Installiert:   0.11.0-0ubuntu10
Installationskandidat: 0.11.0-0ubuntu10
Versionstabelle:
   *** 0.11.0-0ubuntu10 0
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  I believe it's a bug since the keyboard layout at login window after
  installing as described above should be the default system one, german
  in the above case.

  I have tried all sorts of ways (including some ugly hacks) to get this
  resolved on a previous installation but didn't find a way. Considering
  the many moving parts to get the login manager up and running, I'm
  aware this might be filed against the wrong package. It might even be
  an installer bug.

  
  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1458220/+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 1509434] Re: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin

[Flames_in_Paradise]

** Tags added: wily

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

Title:
  Kubuntu panel, starter, desktop do not redraw on change using EGL in
  kwin

Status in xorg package in Ubuntu:
  Incomplete
Status in plasma-desktop package in Fedora:
  Unknown

Bug description:
  After my upgrade from 15.04 to 15.10 certain Plasma elements don't redraw.
  This affects the task bar (in the panel), the starter and the desktop at 
least.

  So after starting an application it's not shown in the task bar. After
  adding a favourite it's not shown in the starter and after dropping a
  file on the desktop it's not shown.

  For the task bar I found a work around, by selecting the auto hide
  function. So each time I move to the bottom edge the task bar pops up,
  gets redrawn and shows the correct open applications.

  For the starter: after adding a favourite, click the starter icon
  (closes), then click again (opens with the change shown).

  For the desktop I could only logoff, then login.

  Prior to upgrading I had 15.04 with the Kubuntu Backports installed,
  and had not this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509434/+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 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized

[Flames_in_Paradise]

@flohack: If U want this as feature in Ubuntu-Touch - U should register
a separate bug against this applicaction ->

http://packages.ubuntu.com/search?keywords=ubuntu-
touch=names=all=all

U won't get any results/progress here, period - if U don't register a
bug-report against the package in question.

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

Title:
  Please provide a mechanism whereby Wi-Fi networks can be prioritized

Status in NetworkManager:
  Fix Released
Status in Plasma-widget-networkmanagement:
  Won't Fix
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in networkmanagement package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I've got few wifi network profiles. NM connects to 1st available
  network in alphabetical order. But at my home NM connects to slow and
  unstable free network and I want to connect to my own wifi router. I
  suggest to add some priorities to different networks to set the order
  which network to connect to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/366780/+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 1451728]

[Flames_in_Paradise]

This is a real blocker - so...  Multi-Desktop environment (still
recommended?) puts interested peoples desktop in a unsecure state as it
blocks APT then.

If there is no other solution we will have to ask to remove Telepathy
from Kubuntu-meta or _not_ to recommend a mixed Desktop-Environment any
longer  & put up a warning. May sound harsh, but...

This error covers two release + a third that's in current development.

A possible solution to get at least APT back into it's shoes again was
posted in askubuntu:

https://askubuntu.com/questions/618389/error-upgrading-kde-telepathy-
kubuntu-15-04

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in One Hundred Papercuts:
  Confirmed
Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Unknown
Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

my comment didn't get transfered into KDE-bug-tracking?

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in One Hundred Papercuts:
  Confirmed
Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Unknown
Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

Still piling up in Launchpad – hitting the community forums around the
world - breaking APT into a blocked state.

Still no solution in sight?

kind regards

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in One Hundred Papercuts:
  Confirmed
Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Unknown
Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1451728/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

Removin account-plugin from list solved the problem in Debian.

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in One Hundred Papercuts:
  Confirmed
Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Unknown
Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1451728/+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 1509251] Re: Custom shortcuts not working Wily Werewolf in mixed environment

[Flames_in_Paradise]

** Summary changed:

- Custom shortcuts not working Wily Werewolf
+ Custom shortcuts not working Wily Werewolf in mixed environment

** Summary changed:

- Custom shortcuts not working Wily Werewolf in mixed environment
+ Custom shortcuts not working Wily Werewolf in mixed environment 
(Ubuntu/Kubuntu)

** Summary changed:

- Custom shortcuts not working Wily Werewolf in mixed environment 
(Ubuntu/Kubuntu)
+ Custom shortcuts not working Wily Werewolf in mixed environment 
(Unity/Kubuntu)

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

Title:
  Custom shortcuts not working Wily Werewolf in mixed environment
  (Unity/Kubuntu)

Status in gsettings-qt package in Ubuntu:
  New
Status in kde-workspace package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New

Bug description:
  I have custom hotkeys (like CapsLock for changing keyboard layouts)
  and after some time they stop to work. Nothing happens when I use
  keyboard shortcut. It starts working again for sometime if I go to the
  settings and reconfigure it.

  $ lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  This is Kubuntu (fresh installation)

  Let me know what additional information I can provide. Unfortunately I
  don't know which package is responsible for keyboard shortcuts in
  Kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1509251/+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 1527001] Re: hp-plugin hangs at invisible sudo prompt after download of plugin files

[Flames_in_Paradise]

Confirm this bug-report with Kubuntu 16.04 LTS (Development-Release) as
per today

** Tags added: xenial

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

Title:
  hp-plugin hangs at invisible sudo prompt after download of plugin
  files

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After downloading the plugin files with the recommended method and
  accepting the license agreement the installation routine hangs
  (doesn't proceed over multiple hours without any CPU or I/O load)
  after output `Number of files to install: 42` which is likely to be
  caused by a spawned process with the `cmdline`
  `/usr/bin/sudo/usr/bin/pythoninstallPlugin.py` which might request the
  user's `sudo` password which isn't visible for the user (and expected
  to be requested in a dialog anyway).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: hplip (not installed)
  Uname: Linux 4.3.0-040300-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 17 01:22:41 2015
  InstallationDate: Installed on 2015-12-12 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1527001/+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 1509251] Re: Custom shortcuts not working Wily Werewolf (Unity/Kubuntu)

[Flames_in_Paradise]

@ rostopiradev: Tks for clarification, changed title accordingly.–

** Summary changed:

- Custom shortcuts not working Wily Werewolf in mixed environment 
(Unity/Kubuntu)
+ Custom shortcuts not working Wily Werewolf (Unity/Kubuntu)

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

Title:
  Custom shortcuts not working Wily Werewolf (Unity/Kubuntu)

Status in gsettings-qt package in Ubuntu:
  New
Status in kde-workspace package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New

Bug description:
  I have custom hotkeys (like CapsLock for changing keyboard layouts)
  and after some time they stop to work. Nothing happens when I use
  keyboard shortcut. It starts working again for sometime if I go to the
  settings and reconfigure it.

  $ lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  This is Kubuntu (fresh installation)

  Let me know what additional information I can provide. Unfortunately I
  don't know which package is responsible for keyboard shortcuts in
  Kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1509251/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

** Summary changed:

- kde-config-telepathy-accounts package install error
+ [master] kde-config-telepathy-accounts package install error

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in One Hundred Papercuts:
  Confirmed
Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Unknown
Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1451728/+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 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://

[Flames_in_Paradise]

** Summary changed:

- Amaroks Wikipedia applet does not work anymore
+ Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change 
for https://

** Tags added: wily

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

Title:
  Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-
  change for https://

Status in amarok package in Ubuntu:
  New

Bug description:
  Amaroks wikipedia applet stopped showing any information. According to
  the upstream bug report (https://bugs.kde.org/show_bug.cgi?id=349313)
  this is caused by a change in wikipedias api, which requires now a ssl
  connection. This means, that all amarok versions currently available
  on ubuntu are affected.

  The same bug report mentions a commit
  http://commits.kde.org/amarok/284342b48dc32341c3553fd2b0ee5069d75b58f9
  which (partially) fixes the issue by making it possible to enable ssl
  for the applet. It might be worth backporting if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: amarok 2:2.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan  8 13:25:04 2016
  InstallationDate: Installed on 2015-09-22 (107 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: amarok
  UpgradeStatus: Upgraded to xenial on 2015-10-30 (70 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+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 1529963] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in pac

[Flames_in_Paradise]

*** This bug is a duplicate of bug 1475828 ***
https://bugs.launchpad.net/bugs/1475828

** This bug has been marked a duplicate of bug 1475828
   package account-plugin-google (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.04.2-0ubuntu1

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/accounts/services
  /google-im.service', which is also in package kde-config-telepathy-
  accounts 4:15.08.2-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Preparing to unpack 
.../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  Error in function: 
  dpkg: dependency problems prevent configuration of unity-scope-gdrive:
   unity-scope-gdrive depends on account-plugin-google; however:
Package account-plugin-google is not installed.

  dpkg: error processing package unity-scope-gdrive (--configure):
   dependency problems - leaving unconfigured

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 29 21:34:11 2015
  DpkgTerminalLog:
   Preparing to unpack 
.../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ...
   Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) ...
  DuplicateSignature: package:account-plugin-google:(not installed):trying to 
overwrite '/usr/share/accounts/services/google-im.service', which is also in 
package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  InstallationDate: Installed on 2015-07-18 (163 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150716)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1529963/+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 1527001] Re: hp-plugin hangs at invisible sudo prompt after download of plugin files

[Flames_in_Paradise]

Also reported on sourceforge:

http://sourceforge.net/projects/hplip/ (by "koebln", 14.12.2015)

confirming here as I run into issue as well. (Kubuntu 15.10, official
hplip from Ubuntu)

** Changed in: hplip (Ubuntu)
   Status: New => Confirmed

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

Title:
  hp-plugin hangs at invisible sudo prompt after download of plugin
  files

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After downloading the plugin files with the recommended method and
  accepting the license agreement the installation routine hangs
  (doesn't proceed over multiple hours without any CPU or I/O load)
  after output `Number of files to install: 42` which is likely to be
  caused by a spawned process with the `cmdline`
  `/usr/bin/sudo/usr/bin/pythoninstallPlugin.py` which might request the
  user's `sudo` password which isn't visible for the user (and expected
  to be requested in a dialog anyway).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: hplip (not installed)
  Uname: Linux 4.3.0-040300-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 17 01:22:41 2015
  InstallationDate: Installed on 2015-12-12 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1527001/+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 1520286] Re: fglrx-core 2:15.200-0ubuntu0.6: fglrx-core kernel module failed to build

[Flames_in_Paradise]

bot stop nagging

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

Title:
  fglrx-core 2:15.200-0ubuntu0.6: fglrx-core kernel module failed to
  build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  Crash occurred during software update procedure.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-core 2:15.200-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
  Uname: Linux 3.16.0-51-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 3.16.0-51-generic
  Date: Thu Nov 26 10:34:23 2015
  DistUpgraded: 2014-09-01 14:08:19,791 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.13.0-70-generic, x86_64: installed
   virtualbox, 4.3.34: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Radeon HD 7450 [1682:3200]
  InstallationDate: Installed on 2014-01-19 (676 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageVersion: 2:15.200-0ubuntu0.6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-51-generic 
root=UUID=29264224-1692-41a1-ac94-abe4d909eb18 ro plymouth:debug 
crashkernel=384M-:128M drm.debug=0xe crashkernel=384M-:128M
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.200-0ubuntu0.6: fglrx-core kernel module failed to 
build
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 1: X Error of failed request:  BadRequest (invalid request code or no 
such operation)
 Major opcode of failed request:  157 (ATIFGLEXTENSION)
 Minor opcode of failed request:  66 ()
 Serial number of failed request:  23
 Current serial number in output stream:  23
  UpgradeStatus: Upgraded to trusty on 2014-09-01 (450 days ago)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd10/01/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 15 11:20:45 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputEee PC WMI hotkeys   KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1520286/+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 1514106] Re: screen corruption

[Flames_in_Paradise]

Is affecting plasma-workspace, but depends on the hardware & and the
module in question.

** Package changed: plasma-workspace (Ubuntu) => xserver-xorg-video-
intel (Ubuntu)

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

Title:
  screen corruption

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  The desktop is fully corrupted, it's full of glitches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1514106/+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 1514106] Re: screen corruption

[Flames_in_Paradise]

possibly a duplicate of bug #1507255 (Garbled graphics in Wily with
Intel GMA4500 chip)

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

Title:
  screen corruption

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  The desktop is fully corrupted, it's full of glitches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1514106/+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 1493888] Re: FGLRX incompatible with gcc 5

[Flames_in_Paradise]

@ Arnkell (logpip)

Timeline? see -> (https://wiki.ubuntu.com/StableReleaseUpdates) -> 3.6
Procedure

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+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 1510573] Re: fglrx should blacklist amdgpu

[Flames_in_Paradise]

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

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

Title:
  fglrx should blacklist amdgpu

Status in One Hundred Papercuts:
  New
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510573/+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 1510573] Re: fglrx should blacklist amdgpu

[Flames_in_Paradise]

@ SRU-Team: Package is still in proposed pocket as per today 20.11.

Has to be ssen in conjunction wt bug #1493888

They are like siamese-twins not going nowhere w/o each other...

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

Title:
  fglrx should blacklist amdgpu

Status in One Hundred Papercuts:
  New
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510573/+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 1510573] Re: fglrx should blacklist amdgpu

[Flames_in_Paradise]

This bug hindered user wt newer AMD to use the Upgrade. It was mentioned
int the Release-Notes -so they would just endup with a black-screen. The
severity has to be judged as highly critical. The culpürit was in this
case AMD not beeing ready for the swift to GCC-5. This doesn't interest
a user in the 1st place. The publisher of software in general has a
responsibilty not to leave a user w/t a unfunctional system. A Standard
user will judge his HW borked & broken on Linux. So this does not even
hurt Ubuntu's-Image but the Image of the movement in a whole. This
happens over and over in the last years. And people are feed with this.

Options:

1. Delay release date until fix is tested and implemented.
2. Ubitquity the Installer has the option to add a comment not to tick "yes" 
when it comes to the questions - Do you want to install 3rd partie Drivers.

This is a pitfall beyond believe – and it makes people turn away. Pls
see also bug #1493888, reported on 9.9.2015

Hopefully this will lead to a blueprint for improvement?

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

Title:
  fglrx should blacklist amdgpu

Status in One Hundred Papercuts:
  New
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510573/+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 1510573] Re: fglrx should blacklist amdgpu

[Flames_in_Paradise]

** Changed in: hundredpapercuts
   Status: New => Confirmed

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

Title:
  fglrx should blacklist amdgpu

Status in One Hundred Papercuts:
  Confirmed
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510573/+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 1493888] Re: FGLRX incompatible with gcc 5

[Flames_in_Paradise]

@ SRU-Team  comment #216 removed verification needed Nov.18.Nov2015

This package has to be seen in conjunction with bug #1510573 and vice
versa

This package here is still in proposed-pocket as per TODAY and does not
appear in

http://people.canonical.com/~ubuntu-archive/pending-sru#wily.html

https://launchpad.net/ubuntu/wily/+queue?queue_state=3_text=fglrx

Pls. investigate and report to QC

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+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 577716] Re: ibus should work "out of the box" on Kubuntu

[Flames_in_Paradise]

** Tags added: eol lucid

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

Title:
  ibus should work "out of the box" on Kubuntu

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: ibus

  ibus works "out of the box" on Ubuntu. It should do the same on
  Kubuntu as well. This is not a feature request. A working input method
  for international data entry is a *must* for modern desktop
  environments. So the absence of this is a bug.

  Possibly due to the recent work for Lucid to integrate GNOME tray
  applications in KDE, it is  possible to use the Ibus tray application
  and input international data into all KDE/GNOME applications (except
  OpenOffice) from the KDE 4 desktop environment itself. The relevant
  steps are outlined at http://wiki.debian.org/I18n/ibus and working on
  a regular Kubuntu Lucid release. Therefore, the steps outlined in the
  above wiki must be by default integrated into the default Kubuntu
  installation so that by merely installing the relevant ibus packages
  users of Kubuntu will be automatically enabled to enter international
  data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/577716/+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 1475037] Re: 14.04 Latest Updates Logs Out Remote Host

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  14.04 Latest Updates Logs Out Remote Host

Status in vino package in Ubuntu:
  New

Bug description:
  I don't even know if this is related to vino, as it seems the package
  hasn't changed in quite some time for 14.04.  I have Ubuntu computers
  on 11.04, 13.04, 14.04, Windoze Computers, Android Tablets and even an
  old Mac running Tiger.  Now, while I can connect to any of those from
  any other computer, it is only the 2 running Ubuntu 14.04 that seem to
  be affected.  It seems that I can connect to the 14.04 computers fine
  with Remote Desktop, Remmina or even TightVNC on Windows.  The Problem
  is that the host/server, i.e - the one I'm not sitting in front of,
  always logs out at some point (usually pretty quick).  Once that
  happens, I have to walk to the computer in the house or the computer
  in my building to log back in.  It is only these 2 that are having the
  problem and it only started after some updates within the last 2 or 3
  weeks.  I even tried downgrading vino, uninstalling vino to install
  krfb and quite a few other things like uninstalling recently installed
  items and a urserver, which is for universal remote from Android to
  Ubuntu.  It is quite the annoying bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1475037/+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 1451728] Re: kde-config-telepathy-accounts package install error

[Flames_in_Paradise]

** Tags added: wily

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

Title:
  kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  New
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Confirmed
Status in account-plugins source package in Wily:
  Confirmed
Status in kaccounts-providers source package in Wily:
  Confirmed
Status in ktp-accounts-kcm source package in Wily:
  Confirmed

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 548886] Re: KDE won't start with fglrx drivers in Lucid

[Flames_in_Paradise]

corr.: status eq. "incomplete" allows bug-report to expire in 60 days.

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

Title:
  KDE won't start with fglrx drivers in Lucid

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu lucid (development branch)
  Release:10.04

  KDE won't start with fglrx drivers.
  GNOME works properly.  KDE works with installed (vesa?) driver.  

  Upon attempting to log in to a KDE desktop session from KDM, the KDE
  splash screen comes up and the 4 fuzzy icons can be dimly seen.  They
  never solidify as they normally do.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Mar 26 08:13:08 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100225)
  NonfreeKernelModules: fglrx
  Package: kubuntu-desktop 1.165
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: kubuntu-meta
  Uname: Linux 2.6.32-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/548886/+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 548886] Re: KDE won't start with fglrx drivers in Lucid

[Flames_in_Paradise]

Setting the bug status to "invalid" as this edition of Ubuntu has
reached End-of-life-cycle.

If you experience a similar symptom on a  supported version please file
a new bug.

If you are not satisfied with the solution please feel free to reopen
the bug-report.

Thanks for reporting and apologies for any inconveniences.

** Tags added: eol

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

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

Title:
  KDE won't start with fglrx drivers in Lucid

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu lucid (development branch)
  Release:10.04

  KDE won't start with fglrx drivers.
  GNOME works properly.  KDE works with installed (vesa?) driver.  

  Upon attempting to log in to a KDE desktop session from KDM, the KDE
  splash screen comes up and the 4 fuzzy icons can be dimly seen.  They
  never solidify as they normally do.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Mar 26 08:13:08 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100225)
  NonfreeKernelModules: fglrx
  Package: kubuntu-desktop 1.165
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: kubuntu-meta
  Uname: Linux 2.6.32-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/548886/+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 1064192] Re: [update request] nvidia-173.14.36 adds support for xserver ABI 13 [quantal and precise .2]

[Flames_in_Paradise]

** Changed in: nvidia-graphics-drivers-173-updates (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [update request] nvidia-173.14.36 adds support for  xserver ABI 13
  [quantal and precise .2]

Status in nvidia-graphics-drivers-173 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-173-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-173 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-173-updates source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-173 source package in Quantal:
  Fix Released
Status in nvidia-graphics-drivers-173-updates source package in Quantal:
  Won't Fix

Bug description:
  New stable 173-driver was released on 2012.10.04
  :
   * Added support for xserver ABI 13 (xorg-server 1.13)

  http://www.nvidia.com/object/linux-display-ia32-173.14.36-driver.html
  http://www.nvidia.com/object/linux-display-amd64-173.14.36-driver.html

  Additional information is at hand on the linked pages in the drivers
  documentation.

  So there woudln't be as many complaints as been seen on the last release...
  if this could be included for the final-release of Quantal 12.10.

  This regards also to nvidia-common (?)

  and

  nvidia-settings (which includes nvidia-xconfig)

  Thanks for the great support to help making Ubuntu better every day.
  Quantal beats W8 already by numbers :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1064192/+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 1332944] Re: Update not working correctly

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  Update not working correctly

Status in thunderbird package in Ubuntu:
  New

Bug description:
  - Ubuntu 14.04 64-bit -

  After regular update from Thunderbird 24.5.0 to 24,6.0 I had following issues:
  - No proper localisation i.e., I had to manually activate the language from 
addons manager and restart.
  - All open tabs were lost.
  Before processing the update, my Thunderbird was propperly closed.

  *** I see this problem since 2 years, but not on any update ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1332944/+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 1291526] Re: could not start ksmserver with nvidia-prime at next login

[Flames_in_Paradise]

** Changed in: nvidia-prime (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  could not start ksmserver with nvidia-prime at next login

Status in “nvidia-prime” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  Install nvidia-prime,
  select nvidia card using prime-select nvidia,
  connect external monitor and try to change the resolution,
  log out and log back in,
  Could not start ksmserver message pops up.
  Works fine with ubuntu, must be a KDE related bug.
  The problem is not present when using the intel card.
  This bug has been present in 13.10, too.

  baloo@LeW-O-Laptop:~$ dpkg -l | grep nvidia
  ii  nvidia-331331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA binary driver - version 331.49
  ii  nvidia-libopencl1-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL Driver and ICD Loader library
  ii  nvidia-opencl-icd-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime  0.6 
amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings   331.38-0ubuntu1~xedgers~trusty1 
amd64Tool for configuring the NVIDIA graphics driver
  I'm on a Dell N7110.

  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kdebase-workspace (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 12 18:57:25 2014
  InstallationDate: Installed on 2014-03-11 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311)
  SourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291526/+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 1291526] Re: could not start ksmserver with nvidia-prime at next login

[Flames_in_Paradise]

In accordance wt comment #27  this bug got closed somewhere else.

Thanks for reporting Xavier. Hope you still have fun with Kubuntu. Enjoy
it! (like me)

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

Title:
  could not start ksmserver with nvidia-prime at next login

Status in “nvidia-prime” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  Install nvidia-prime,
  select nvidia card using prime-select nvidia,
  connect external monitor and try to change the resolution,
  log out and log back in,
  Could not start ksmserver message pops up.
  Works fine with ubuntu, must be a KDE related bug.
  The problem is not present when using the intel card.
  This bug has been present in 13.10, too.

  baloo@LeW-O-Laptop:~$ dpkg -l | grep nvidia
  ii  nvidia-331331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA binary driver - version 331.49
  ii  nvidia-libopencl1-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL Driver and ICD Loader library
  ii  nvidia-opencl-icd-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime  0.6 
amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings   331.38-0ubuntu1~xedgers~trusty1 
amd64Tool for configuring the NVIDIA graphics driver
  I'm on a Dell N7110.

  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kdebase-workspace (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 12 18:57:25 2014
  InstallationDate: Installed on 2014-03-11 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311)
  SourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291526/+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 339326] Re: [MASTER] some parts of Firefox are not localized

[Flames_in_Paradise]

** Tags added: unicorn

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

Title:
  [MASTER] some parts of Firefox are not localized

Status in The Mozilla Firefox Browser:
  New
Status in Ubuntu Translations:
  Triaged
Status in “firefox” package in Ubuntu:
  Triaged

Bug description:
  When you upgrade firefox to a new version the extension compatiblity checking 
process starts at firefox next restart but I noticed that the window saying 
that the compatibility process is starting isn't translated in Italian.
  In launchpad (https://translations.launchpad.net/ubuntu/hardy/+lang/it) we 
can see that the italian translation status of firefox is 100% translated but I 
think it's wrong as I have explained above.

  Tested with Ubuntu Hardy and firefox 3.0.7

  Also, any notice at startup, like Firefox is already running is not
  translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/339326/+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 949606] Re: 64 bit dev packages should include 32 bit .so library file

[Flames_in_Paradise]

Even in the press already:, as this regards trusty too:

http://www.webupd8.org/2014/04/install-google-earth-in-ubuntu-1404.html

Also we can find quite a  few people who suffered this with the LTS-
Enablement-Stacks-Support... and Installations of any offcial flavour 
12.04.1

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

Title:
  64 bit dev packages should include 32 bit .so library file

Status in “mesa” package in Ubuntu:
  Triaged

Bug description:
  64 bit dev packages contain a 64 bit version of the library file(s)
  that they provide for linking but not a 32 bit version of the library
  file(s). In previous versions of Ubuntu, however, it was possible to
  compile 32 bit applications using the 64 bit dev packages in by
  installing ia32-libs, which contained the required 32 bit library
  files.

  In the move to multiarch, 32 bit library files are being removed from
  ia32-libs. Multiarch (I assume) aims to keep the architectures
  separate, so the generally intended solution is to install the i386
  version of the dev package when compiling 32 bit applications, ie
  side-by-side with the 64 bit dev package.

  However, some 64 bit development packages conflict with their 32 bit
  equivalent. This creates a regressive situation where it is impossible
  to install them side-by-side - you are forced to either install the 32
  bit package, which breaks 64 bit compilations, or the 64 bit package,
  which breaks 32 bit compilations.

  An example is libglu1-mesa-dev, which conflicts with libglu1-mesa-
  dev:i386. The libglu1-mesa-dev file contains all the necessary
  development files for 32 bit *except* for the 32 bit library file. It
  does contain the 64 bit library file. Since the library file is part
  of the development files, libglu1-mesa-dev does not contain all the
  necessary development files for 32 bit, ie it does not contain all the
  necessary development files for multiarch. I think that it *should*
  contain all the necessary files for building multarch applications.

  The two workarounds are:

  1. Manually re-install the required i386 dev packages before compiling
  32 bit apps, and then manually re-install the required amd64 dev
  packages before compiling 64 bit apps. This is a real pain.

  2. Install the i386 binary package (eg libglu1-mesa:i386) and the
  amd64 dev package (eg libglu1-mesa-dev), and manually create symlinks
  for the i386 libXYZ.so package (eg sudo ln -s /usr/lib/i386-linux-
  gnu/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so). This is a more
  permanent solution but is a real pain to set up, as you have to find
  each missing library manually, and some library files, like
  mesa/libGL.so.1, are in subfolders.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libglu1-mesa-dev 8.0.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,resize,compiztoolbox,vpswitch,place,gnomecompat,move,regex,animation,imgpng,snap,mousepoll,session,expo,workarounds,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Mar  8 10:20:54 2012
  DistUpgraded: Log time: 2012-02-26 08:25:08.500725
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 4.1.8, 3.2.0-12-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-14-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-17-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120201.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=630a9f76-6f8f-43be-bb99-6be721c9deaf ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: mesa
  UpgradeStatus: Upgraded to precise on 2012-02-26 (11 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  

[Desktop-packages] [Bug 1290717] Re: akonadi 1.11.80 fails to start

[Flames_in_Paradise]

** Tags added: kubuntu trusty

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

Title:
  akonadi 1.11.80  fails to start

Status in Akonadi - The PIM Storage Service:
  Fix Released
Status in “akonadi” package in Ubuntu:
  Triaged
Status in “akonadi” source package in Trusty:
  Triaged
Status in “akonadi” source package in Utopic:
  Fix Committed

Bug description:
  [Impact]

  installations that used to be trusty and went through akonadi 1.11.80
  (early beta upgrades to 14.04) have a broken database

  adding a fix for these broken setups as per upstream request.

  [Test Case]

  * have a broken akonadi and upgrade
  OR
  * install 14.04 alpha
  * login and setup mails
  * upgrade akonadi to [1]
  * logout and login again, observe akonadi being broken
  * upgrade to final+proposed
  * akonadi should be repaired

  [1] https://launchpad.net/ubuntu/+source/akonadi/1.11.80-0ubuntu3

  [Regression Potential]

  N/A

  [Other Info]
   
  N/A

  --

  
  akonadi fails to start since the update from 1.11.0 to 1.11.80
  Full description in upstream bug report: 
https://bugs.kde.org/show_bug.cgi?id=331867

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/1290717/+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 339326] Re: [MASTER] some parts of Firefox are not localized

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  [MASTER] some parts of Firefox are not localized

Status in The Mozilla Firefox Browser:
  New
Status in Ubuntu Translations:
  Triaged
Status in “firefox” package in Ubuntu:
  Triaged

Bug description:
  When you upgrade firefox to a new version the extension compatiblity checking 
process starts at firefox next restart but I noticed that the window saying 
that the compatibility process is starting isn't translated in Italian.
  In launchpad (https://translations.launchpad.net/ubuntu/hardy/+lang/it) we 
can see that the italian translation status of firefox is 100% translated but I 
think it's wrong as I have explained above.

  Tested with Ubuntu Hardy and firefox 3.0.7

  Also, any notice at startup, like Firefox is already running is not
  translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/339326/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

** Tags added: hw-specific

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -Dn` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1291526] Re: could not start ksmserver with nvidia-prime at next login

[Flames_in_Paradise]

Looks like bug #1260220 (Greeter and other clients cannot connect to X
server) to me.

So if this gets in line again with the next update of LightDM
(1.9.12-0ubuntu1), pls advise.

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

Title:
  could not start ksmserver with nvidia-prime at next login

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  Install nvidia-prime,
  select nvidia card using prime-select nvidia,
  connect external monitor and try to change the resolution,
  log out and log back in,
  Could not start ksmserver message pops up.
  Works fine with ubuntu, must be a KDE related bug.
  The problem is not present when using the intel card.
  This bug has been present in 13.10, too.

  baloo@LeW-O-Laptop:~$ dpkg -l | grep nvidia
  ii  nvidia-331331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA binary driver - version 331.49
  ii  nvidia-libopencl1-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL Driver and ICD Loader library
  ii  nvidia-opencl-icd-331 331.49-0ubuntu1~xedgers14.04.3  
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime  0.6 
amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings   331.38-0ubuntu1~xedgers~trusty1 
amd64Tool for configuring the NVIDIA graphics driver
  I'm on a Dell N7110.

  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kdebase-workspace (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 12 18:57:25 2014
  InstallationDate: Installed on 2014-03-11 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311)
  SourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291526/+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 1291326] Re: Ubuntu 14.04 fail to wakeup from sleep

[Flames_in_Paradise]

This is the result on my machine on the above given terminal-command:

SUSPEND is supported
HIBERNATE is supported
SUSPENDHYBRID is supported

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

Title:
  Ubuntu 14.04 fail to wakeup from sleep

Status in “nvidia-prime” package in Ubuntu:
  Confirmed

Bug description:
  I'm using Kubuntu 14.04 64 bit on a Dell E5440 machine. After
  installing the alpha2 version two weeks ago wakeup from sleep was
  working fine. I update the system everyday and during last week
  something broke this feature. From then I have updated the bios (from
  A00 version June 2013 to A04 January 2014) and I've seen other bugs
  (VGA out among others) fixed, but not this one.

  When the system wakes from sleep the login screen appears, but
  mouse/keyboard don't working. I have found that plugin something to
  the VGA out and unplugin it will bring mouse/keyboard alive again, but
  this solution only works for the first time I enter sleep mode.
  Ctrl+Alt+F6 followed by Ctrl+Alt+F7 to return to the graphics mode
  ends with a black screen (the mouse works, but no login is possible).
  I installed the graphics driver with Optimus support (Prime), keeping
  active the Nvidia card GT720M.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 12 12:28:20 2014
  InstallationDate: Installed on 2014-02-27 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140227)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alonso 2770 F pulseaudio
   /dev/snd/controlC0:  alonso 2770 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1bc33d13-cf2d-4092-9768-3bc7d7602762
  InstallationDate: Installed on 2014-02-27 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140227)
  MachineType: Dell Inc. Latitude E5440
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=f23bdd16-c018-4bf4-843d-ce96a510108e ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  Tags:  trusty
  Uname: Linux 3.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0WV8K7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd01/22/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn0WV8K7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291326/+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 1291326] Re: Ubuntu 14.04 fail to wakeup from sleep

[Flames_in_Paradise]

Thomas,

could you open a terminal and insert the following command via copy 
paste

echo; for i in --suspend --hibernate --suspend-hybrid; do pm-is-
supported $i  echo $(echo $i | tr [:lower:] [:upper:] | tr -d -) is
supported; done; echo

And return the result?

Background: In general the STR /STD abiity is turned off by default.
With the execption of machines that are know /tested to function on
this. These are Ubuntu-certified.

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

Title:
  Ubuntu 14.04 fail to wakeup from sleep

Status in “nvidia-prime” package in Ubuntu:
  Confirmed

Bug description:
  I'm using Kubuntu 14.04 64 bit on a Dell E5440 machine. After
  installing the alpha2 version two weeks ago wakeup from sleep was
  working fine. I update the system everyday and during last week
  something broke this feature. From then I have updated the bios (from
  A00 version June 2013 to A04 January 2014) and I've seen other bugs
  (VGA out among others) fixed, but not this one.

  When the system wakes from sleep the login screen appears, but
  mouse/keyboard don't working. I have found that plugin something to
  the VGA out and unplugin it will bring mouse/keyboard alive again, but
  this solution only works for the first time I enter sleep mode.
  Ctrl+Alt+F6 followed by Ctrl+Alt+F7 to return to the graphics mode
  ends with a black screen (the mouse works, but no login is possible).
  I installed the graphics driver with Optimus support (Prime), keeping
  active the Nvidia card GT720M.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 12 12:28:20 2014
  InstallationDate: Installed on 2014-02-27 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140227)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alonso 2770 F pulseaudio
   /dev/snd/controlC0:  alonso 2770 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1bc33d13-cf2d-4092-9768-3bc7d7602762
  InstallationDate: Installed on 2014-02-27 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140227)
  MachineType: Dell Inc. Latitude E5440
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=f23bdd16-c018-4bf4-843d-ce96a510108e ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  Tags:  trusty
  Uname: Linux 3.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0WV8K7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd01/22/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn0WV8K7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291326/+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 1283353] Re: System ends with black screen after latest update

[Flames_in_Paradise]

** Changed in: nvidia-prime (Ubuntu)
   Status: Confirmed = Opinion

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

Title:
  System ends with black screen after latest update

Status in “nvidia-prime” package in Ubuntu:
  Opinion

Bug description:
  After latest update on Kubuntu 14.04 system ends with black screen
  just when login screen should shows up. Lightdm or kdm doesn't work.
  Removing nvidia-prime results with normal booting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1283353/+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 1292730] Re: Optimus: Nvidia Settings asks sudo password to change between Nvidia and Intel card

[Flames_in_Paradise]

** Tags added: precise

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

Title:
  Optimus: Nvidia Settings asks sudo password to change between Nvidia
  and Intel card

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  Nvidia Settings asks sudo password to change between Nvidia and Intel
  card.

  It should be something trivial, no need to password here... (hey,
  bumblebee does this without password, and by the way, without
  something like a button Performance x Power Saving)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 14 23:30:02 2014
  InstallationDate: Installed on 2014-03-14 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140314)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1292730/+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 1260683] Re: Jockey should not make NVIDIA Optimus available on the desktop

[Flames_in_Paradise]

** Tags added: 12.04.4 precise

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

Title:
  Jockey should not make NVIDIA Optimus available on the desktop

Status in “jockey” package in Ubuntu:
  Invalid
Status in “jockey” source package in Precise:
  In Progress

Bug description:
  Currently we try to offload graphics rendering to the discrete NVIDIA
  GPU when we detect systems with an Intel integrated GPU and an NVIDIA
  discrete card regardless of whether the computer is a desktop or a
  laptop.

  While this is a perfectly desirable feature on a laptop, where the
  internal display is always driven by the integrated GPU, on a desktop
  system, users will probably add a discrete card to get better
  performance and connect the monitor to it (instead of using the
  integrated card). This will result in a black screen on boot because
  the xserver will expect the monitor to be connected to the Intel card.
  Users should disable the Intel card from the BIOS instead.

  For this reason, Jockey should check that it's dealing with a laptop
  before suggesting the installation of the NVIDIA drivers on systems
  with hybrid graphics. This also affects the Ubuntu installer, where
  the NVIDIA driver is installed by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1260683/+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 1265383] Re: Black screen and mouse after login.

[Flames_in_Paradise]

Hi

no log files? No description what Ubuntu Version is in  use. Makes it
quite hard to provide a follow-up...

** Changed in: fglrx-pxpress (Ubuntu)
   Status: New = Incomplete

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

Title:
  Black screen and mouse after login.

Status in “fglrx-pxpress” package in Ubuntu:
  Incomplete

Bug description:
  Hello. I have installed

  sudo apt-get install fglrx fglrx-pxpress

  I get the login screen and a can to enter password. But after login i
  see the black screen and mouse cursor only (and system message bouble
  in top right corner (it is simple message about network configuration,
  non about graphics))

  I have HP Pavilion G7 1303er AMD A6-3420M. I installed driver by
  control panell (is fglrx-updates) and no have problem. But in CCC i se
  only 6520G (no 7450M).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1265383/+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 1284558] Re: SEGFAULT at start: GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  SEGFAULT at start: GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  This is for 14.04. Since the last glibc update a few days ago I can
  not start firefox anymore. I get this error:

  (process:3489): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  (firefox:3489): GLib-GObject-WARNING **: Attempt to add property
  GnomeProgram::sm-connect after class was initialised

  (firefox:3489): GLib-GObject-WARNING **: Attempt to add property
  GnomeProgram::show-crash-dialog after class was initialised

  (firefox:3489): GLib-GObject-WARNING **: Attempt to add property
  GnomeProgram::display after class was initialised

  (firefox:3489): GLib-GObject-WARNING **: Attempt to add property 
GnomeProgram::default-icon after class was initialised
  Segmentation fault (core dumped)

  The same goes for thunderbird, but i will post a new bugreport for
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1284558/+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 1288260] Re: firefox apparmor updates for trusty

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  firefox apparmor updates for trusty

Status in “firefox” package in Ubuntu:
  Fix Committed

Bug description:
  Attached is a patch to fix the apparmor syslog noise I see after
  upgrading to trusty.  It follows the chromium apparmor profile in
  terms of what to allow and deny.

  --- ./usr.bin.firefox 2014-03-05 13:52:13.470886569 +
  +++ /etc/apparmor.d/usr.bin.firefox   2014-03-05 13:56:42.640802391 +
  @@ -38,7 +38,9 @@
 /etc/ r,
 /etc/mime.types r,
 /etc/mailcap r,
  +  /etc/udev/udev.conf r,
 /etc/xdg/*buntu/applications/defaults.listr, # for all derivatives
  +  /sys/devices/pci[0-9]*/**/uevent r,
 /usr/share/xubuntu/applications/defaults.list r,
 owner @{HOME}/.local/share/applications/defaults.list r,
 owner @{HOME}/.local/share/applications/mimeapps.list r,
  @@ -73,6 +75,9 @@
 # TODO: investigate
 deny /usr/bin/gconftool-2 x,
   
  +  # This is requested, but doesn't seem to actually be needed so deny for now
  +  deny /run/udev/data/** r,
  +
 # These are needed when a new user starts firefox and firefox.sh is used
 @{MOZ_LIBDIR}/** ixr,
 /usr/bin/basename ixr,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1288260/+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 1262752] Re: nvidia_304 not blacklisted or removed when nvidia_304_updates is installed.

[Flames_in_Paradise]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.116-0ubuntu0.0.1

---
nvidia-graphics-drivers-304 (304.116-0ubuntu0.0.1) precise-proposed; urgency=low

  * New upstream release (LP: #1259237):
- Improved compatibility with recent Linux kernels.
- Updated the NVIDIA OpenGL driver to write temporary files to
  $TMPDIR if it is set, instead of unconditionally writing to
  /tmp (LP: #1212425).
- Updated a fallback of writing temporary files to $HOME/.nvidia
  to use $HOME/.nv instead, as the latter path is already used
  for other NVIDIA driver related files.

  [ Alberto Milone ]
  * debian/substvars:
- Add support for lts flavours up to saucy.
  * debian/templates/control.in:
- Depend on lib32gcc1 [amd64], libc6-i386 [amd64]
  (LP: #1236945).
- Drop lpia.
  * debian/templates/dkms.conf.in:
- Drop patch for Linux 3.10.
  * debian/rules:
- Blacklist the opposite flavour.
- Blacklist kernel modules from the other flavours.
- Add the download-sources target.
  * debian/templates/nvidia-graphics-drivers.dirs.in,
debian/templates/nvidia-graphics-drivers.install.in,
debian/templates/nvidia-graphics-drivers.override.in,
debian/templates/nvidia-graphics-drivers.postinst.in,
debian/nvidia-autostart.desktop.in,
debian/ubuntu-nvidia-settings.desktop.in:
- Remove nvidia-settings icon, desktop file, and autostart file.
  This is all provided by nvidia-settings now.
  * debian/templates/nvidia-graphics-drivers.prerm.in,
debian/templates/nvidia-graphics-drivers.install.in,
debian/templates/nvidia-graphics-drivers.postinst.in:
- Disable glamoregl.
- Do not update gmenucache any more.

  [ Andy Dick ]
  * debian/templates/nvidia-graphics-drivers.preinst.in:
- Attempt uninstallation of any existing .run file
  installation before installing Debian-packaged
  driver.
  * debian/templates/nvidia-graphics-drivers.postinst.in:
- Add libcuda.so symlinks in /usr/lib*.
  * debian/rules:
- Conditionalize the copying of Makefile.kbuild to
  Makefile. This adds support for newer drivers,
  while maintaining support for packaging older drivers.
- Avoid extracting unnecessary .run files. The 64-bit
  package needs both the 32- and 64-bit .run files, but
  the 32-bit package does not. Change the unpackaging
  rules to unpack only the native package by default,
  and only unpack the 32-bit x86 package on amd64.
  Also, instead of changing the .run file permissions
  to ensure that the .run file is executable, just call
  it as an argument to sh.
- Don't assume that extracted files are writable.
  The package contents extracted from some .run file
  installers may not have write permissions enabled.
  To work around this, move files instead of copying
  them to a temporary location before running sed
  scripts, and add force flags to applicable commands.
 -- Alberto Milone alberto.mil...@canonical.com Wed, 11 Dec 2013 14:07:02 
+0100

see bug #1259237 comment #17


** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu)
   Status: Confirmed = Fix Released

** Tags removed: regression-update

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

Title:
  nvidia_304 not blacklisted or removed when nvidia_304_updates  is
  installed.

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released

Bug description:
  Dell Latitude E6520 Laptop

  System had a working nvidia-304 driver package installed (304.88-0ubuntu0.0.3)
  A regular system update installed, build and activated nvidia-304-updates 
(304.108-0ubuntu0.0.1)

  The new driver does not blacklist nvidia-304 which is still available at 
/lib/modules/3.2.0-57-generic/updates/dkms/nvidia_304.ko
  Depending on which driver is found first on the filesystem, it is possible 
that udev loads the wrong driver at system boot. (Driver detection and loading 
based on pci-aliases found in the system).

  Xorg.0.log shows:
  [22.112] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. 
Please see the
  [22.112] (EE) NVIDIA(0): system's kernel log for additional error 
messages and
  [22.112] (EE) NVIDIA(0): consult the NVIDIA README for details.
  [22.112] (EE) NVIDIA(0):  *** Aborting ***
  [22.112] (EE) NVIDIA(0): Failing initialization of X screen 0

  Dmesg shows:
  [   22.227733] NVRM: API mismatch: the client has the version 304.108, but
  [   22.227735] NVRM: this kernel module has the version 304.88.  Please
  [   22.227735] NVRM: make sure that this kernel module and all NVIDIA driver
  [   22.227736] NVRM: components have the same version.
  [   22.298983] init: lightdm main process (1406) terminated with status 1

  1) Description: Ubuntu 12.04.03 LTS
   

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

This is not true, because then it would appear in the unapproved queue:

https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text=

The package has not even been build yet...

I really think this is a quality issue with launchpad, if the bug
appears here with importance= high why (in hell) this status doesn't get
transferred accordingly?

So this bug got fixed in Trusty quite fast, but 5 days is a long time
for users making an inappropriate experience with Ubuntu in an existing
LTS.

I already got comments in the german Ubuntu-help forum: Why does this
works in Trusty, but not in Precise?

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

** Tags added: verification-needed

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -Dn` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

Excuse me, when will this arrive in Precise LTS?

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

I've checked even a few ubuntu-mirrors (status=uptodate). So it seems to
be stuck somewhere?

Thanks in advance.

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

It's stuck in the upload-queue with priority=low

https://launchpad.net/ubuntu/precise/+queue?queue_state=0queue_text=

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

hi!

Would it be argueable to have this SRU-backported to Precise 12.04.4 ?

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1260128] Re: Nvidia-prime produces unbearable visual stutter

[Flames_in_Paradise]

** Tags added: trusty

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

Title:
  Nvidia-prime produces unbearable visual stutter

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I've installed NVIDIA-Prime v0.5 on Ubuntu 14.04 with all required
  dependencies, on a Clevo 355STQ with a 765m.

  My issue is that whilst the new switching feature works very well, it
  still produces an extremely noticable amount of visual stuttering. In
  graphical and applications and games I can produce very large frames-
  per-second numbers yet the amount of visual tear makes the program
  unusable. Vsync/Sync to Vblank/vblank_mode=1 also does not work as
  intended, with tearing still present.

  Has anyone else had this issue or found a fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1260128/+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 1282796] Re: prime-xconfig can write an invalid BusID string

[Flames_in_Paradise]

** Tags added: precise

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+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 1276123] Re: Xorg loads wrong libglx.so

[Flames_in_Paradise]

** Tags added: saucy

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

Title:
  Xorg loads wrong libglx.so

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  New

Bug description:
  This bug concerns all versions of the nvidia-packages I have tested so
  far, actually since ubuntu 8.something...

  If I install the proprietary nvidia drivers, I can properly set up my
  xorg.conf and the Xorg driver as well as the kernel module load
  correctly. However, when using unity or anything requiring libglx.so,
  X simply crashes. The reason is that X is loading the wrong libglx.so:

  grep glx /var/log/Xorg.0.log

  [ 11312.722] (II) glx will be loaded. This was enabled by default and also 
specified in the config file.
  [ 11312.722] (II) LoadModule: glx
  [ 11312.722] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [ 11312.722] (II) Module glx: vendor=X.Org Foundation

  My first solution was to move
  /usr/lib/xorg/modules/extensions/libglx.so out of the way and to
  replace it with a symlink to /usr/lib/nvidia-VERSION/xorg/libglx.so.
  However, as you might imagine, this quick-and-dirty fix has to be
  redone each time that MESA gets updated, as my symlink is destroyed. I
  have now found a better solution, which consists in telling Xorg where
  the right library is in /etc/X11/xorg.conf

  Section Files
  ModulePath  /usr/lib/nvidia-VERSION/xorg
  ModulePath  /usr/lib/xorg/modules
  ...
  EndSection

  nvidia-VERSION has to be replaced by the proper nvidia version (such
  as nvidia-current). As a result, X loads the right libglx.so.

  This solution could be included in all nvidia- packages, so that the
  problem does not occur any longer. I have found other bug reports from
  other distributions about this, but most are solved by moving
  libglx.so out of the way.

  Just for information, here's some details about my system:
  philippe@saaba:~$ dpkg -l xorg
  Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
  | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
   Halb installiert/Trigger erWartet/Trigger anhängig
  |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
  ||/ Name   Version  Architektur  Beschreibung
  +++-==---=
  ii  xorg   1:7.7+1ubunt amd64X.Org X Window System

  philippe@saaba:~$ lspci | grep VGA
  02:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9600M GT] 
(rev a1)

  philippe@saaba:/var/log$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  nvidia-current is at 304.88-0ubuntu8 0, I also had the problem with
  nvidia-319-updates 319.60-0ubuntu1 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1276123/+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 1252442] Re: nvidia-prime breaks on reboot after latest updates

[Flames_in_Paradise]

It turns out that the original bugreporter had solved his problem (Nov
22/13):

http://askubuntu.com/questions/379052/latest-update-breaks-nvidia-prime

 It turns out the fix for this is actually pretty simple: Delete the
/etc/X11/xorg.conf file, and use nvidia-xconfig to regenerate it. This
fixed the problem upon restart

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

Title:
  nvidia-prime breaks on reboot after latest updates

Status in “nvidia-prime” package in Ubuntu:
  Incomplete

Bug description:
  Currently I'm using a Dell Latitude E6430. I recently updated to to
  Ubuntu 13.10 (from 13.04).

  I installed the nvidia-319-updates/nvidia-settings-319-updates/nvidia-
  prime drivers (also tried the plain nvidia-319/nvidia-settings-319
  drivers), disabled optimus, and was able to use multiple monitors with
  the dell dock (after creating some xrandr scripts).

  However, after the latest round of updates (I applied them on 11/14)
  everything got weird. Now, whenever I boot the 80% of the screen is
  stuck on the blue FDE (full disk encryption) password screen, the
  other 20% will load an incredibly skewed login screen (compressed to a
  height of ~100-200 pixels, and the width of the screen). You can move
  the mouse and see that the screen is updating, it's just not legible
  at all.

  In order to fix it, I have to do the following:
  * Shutdown
  * Startup (going to the BIOS)
  * Enable Optimus
  * Reboot
  * Boot up, enter FDE password
  * Wait until boot finishes (fails?), as I'm stuck on a blank screen
  * Shutdown
  * Startup (going to the BIOS)
  * Disable Optimus
  * Reboot
  * Starts up normally

  I have to do this every time I restart the computer. Needless to say,
  it's rather annoying.

  I've tried: re-re-installing lightdm, the nvidia drivers, etc...

  n.b. I have the latest firmware/BIOS updates from Dell.
  n.b. #2 I always start the laptop in an undocked state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1252442/+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 903194] Re: multiseat not set up correctly

[Flames_in_Paradise]

** Tags added: precise

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

Title:
  multiseat not set up correctly

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
  called seat-chris and seat-brynn)

  Based on the below details, it seems that -sharevts is needed, but not
  handled correctly by lightdm

  
  If I use a fairly minimal config, I get:
  When lightdm starts, Seat 0 is activated
  Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
  Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)

  lightdm.conf:
  
  [LightDM]
  start-default-seat=false
  [SeatDefaults]
  session-wrapper=/etc/lightdm/Xsession
  xserver-config=xorg.conf.multiseat
  [Seat:0]
  xserver-layout=seat-chris
  [Seat:1]
  xserver-layout=seat-brynn

  pstree
  ---
  lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
|   `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
|   `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884


  When I use the sharevts flag on Seat 1, I see the following:
  On lightdm start, Seat 0 is activated
  After a second or so, Seat 0 goes blank, and Seat 1 is activated
  Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on 
both correctly

  lightdm.conf
  -
  [LightDM]
  start-default-seat=false
  [SeatDefaults]
  session-wrapper=/etc/lightdm/Xsession
  xserver-config=xorg.conf.multiseat
  greeter-hide-users=false
  [Seat:0]
  xserver-layout=seat-chris
  [Seat:1]
  xserver-command=/usr/bin/X -sharevts
  xserver-layout=seat-brynn

  pstree
  ---
  lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn 
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
|   `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
|   `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215

  
  If I try sharevts on both sessions, I see the following:

  On lightdm start, Seat 1 starts up
  Seat 0 shows a mouse pointer on a text mode console printing the kernel 
message 'Invalid Framebuffer ID'
  If I force kill lightdm and restart it using the init.d service, then it 
starts correctly

  lightdm.conf
  --
  [LightDM]
  start-default-seat=false
  [SeatDefaults]
  session-wrapper=/etc/lightdm/Xsession
  xserver-config=xorg.conf.multiseat
  greeter-hide-users=false
  [Seat:0]
  xserver-command=/usr/bin/X -sharevts
  xserver-layout=seat-chris
  [Seat:1]
  xserver-command=/usr/bin/X -sharevts
  xserver-layout=seat-brynn

  pstree
  
  lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris 
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn 
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
|   `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
|   `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

[Flames_in_Paradise]

** Tags added: precise

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

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del 
pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted 
system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from 
org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that getting session list timeout, 
which is about a minute later than vt7, and does not have a password input 
field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/997483/+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 977547] Re: doesn't switch to graphical VT when auto login is turned on, (multiseat)

[Flames_in_Paradise]

** Tags added: precise

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

Title:
  doesn't switch to graphical VT when auto login is turned on,
  (multiseat)

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  I have a working multiseat system with the 2nd seat Displaylink-based
  USB touchscreen.

  the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine
  to lightdm.

  If i set autologinup, then the 2nd seat starts fine, but the first
  seat is blank until i

  ctrl-alt-f7

  at which it logs in.

  is it this in my Xorg, does it need to VT switch agressively like
  lightdm usually does, or is it this in my Xorg:

  
  Section ServerLayout
Option  AllowEmptyInput   true
  EndSection

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/977547/+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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings

[Flames_in_Paradise]

** Tags added: removal-candidate

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

Title:
  Transitioning between nvidia drivers (updates, 304, 310) results in
  install failure due to conflicting nvidia-settings

Status in “nvidia-settings” package in Ubuntu:
  Invalid
Status in “nvidia-settings-experimental-304” package in Ubuntu:
  Invalid
Status in “nvidia-settings-experimental-310” package in Ubuntu:
  Invalid
Status in “nvidia-settings-updates” package in Ubuntu:
  Invalid
Status in “nvidia-settings” source package in Precise:
  Invalid
Status in “nvidia-settings-experimental-304” source package in Precise:
  Invalid
Status in “nvidia-settings-experimental-310” source package in Precise:
  Invalid
Status in “nvidia-settings-updates” source package in Precise:
  Invalid

Bug description:
  package nvidia-settings was installed. Seemed to conflict somehow.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-settings-experimental-310 (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu14
  AptOrdering:
   nvidia-settings-experimental-310: Install
   nvidia-settings-experimental-310: Configure
  Architecture: amd64
  Date: Thu Nov  8 17:00:14 2012
  DpkgTerminalLog:
   Unpacking nvidia-settings-experimental-310 (from 
.../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb
 (--unpack):
trying to overwrite '/usr/bin/nvidia-settings', which is also in package 
nvidia-settings-updates 304.43-0ubuntu0.2
  DuplicateSignature:
   Unpacking nvidia-settings-experimental-310 (from 
.../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb
 (--unpack):
trying to overwrite '/usr/bin/nvidia-settings', which is also in package 
nvidia-settings-updates 304.43-0ubuntu0.2
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also 
in package nvidia-settings-updates 304.43-0ubuntu0.2
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-settings-experimental-310
  Title: package nvidia-settings-experimental-310 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also 
in package nvidia-settings-updates 304.43-0ubuntu0.2
  UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+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 1259696] Re: desktop effects + newly attached monitor = both monitors blank

[Flames_in_Paradise]

** Tags added: kubuntu saucy

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

Title:
  desktop effects + newly attached monitor = both monitors blank

Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu:
  New

Bug description:
  I have a monitor and a TV connected to my desktop, with the TV usually
  off. When desktop effects are enabled and the TV is turned on, both
  monitor and TV go blank (black), and only the mouse pointer is
  visible. The only way out of this is to disable desktop effects - I
  had to add a keyboard shortcut for this, otherwise only a hard reboot
  would get me out of this state. I no longer enable desktop effects due
  to this, and hope it will be fixed soon.

  Kubuntu 13.10 with KDE 4.11.3, NVidia 9300 with 319-updates (319.60)
  drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1259696/+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 1259699] Re: nvidia drivers don't apply sync to vblank when second monitor is turned on

[Flames_in_Paradise]

** Tags added: saucy

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

Title:
  nvidia drivers don't apply sync to vblank when second monitor is
  turned on

Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu:
  New

Bug description:
  I have a desktop with monitor and TV connected to it. In order to
  prevent tearing when watching video on the TV, I enable sync to vblank
  and select the TV as the display to sync to in the nvidia setting
  dialog. However, the next time I turn on the TV the setting is not re-
  applied and there is tearing. Interestingly, the solution is simply to
  open and close the settings dialog without changing anything - it does
  remember these preferences, but they simply don't get applied when the
  TV is turned on unless the settings are opened and closed. This gets
  annoying... it should automatically apply the settings when the TV is
  turned on, just like it does the rest of the settings (e.g. twinview,
  geometry, etc.)

  Kubuntu 13.10 with KDE 4.11.3, NVidia 9300 with 319-updates (319.60)
  drivers and TwinView.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1259699/+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 339326] Re: [MASTER] some parts of Firefox are not localized

[Flames_in_Paradise]

Not yet fixed FF 26 - looks really sweet in W$. And btw: Thanks for
reporting

** Tags added: langpack precise

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

Title:
  [MASTER] some parts of Firefox are not localized

Status in The Mozilla Firefox Browser:
  New
Status in Ubuntu Translations:
  Triaged
Status in “firefox” package in Ubuntu:
  Triaged

Bug description:
  When you upgrade firefox to a new version the extension compatiblity checking 
process starts at firefox next restart but I noticed that the window saying 
that the compatibility process is starting isn't translated in Italian.
  In launchpad (https://translations.launchpad.net/ubuntu/hardy/+lang/it) we 
can see that the italian translation status of firefox is 100% translated but I 
think it's wrong as I have explained above.

  Tested with Ubuntu Hardy and firefox 3.0.7

  Also, any notice at startup, like Firefox is already running is not
  translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/339326/+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 1259237] Re: Hybrid graphics enablement in 12.04.4

[Flames_in_Paradise]

Hello there!

With reference to comment#8 : Could 304 drivers kindly get released?
There is the urge to close bug #1262752

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

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  In Progress
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  In Progress
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  In Progress
Status in “nvidia-prime” source package in Precise:
  Fix Committed
Status in “screen-resolution-extra” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+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 1266466] [NEW] [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

[Flames_in_Paradise]

Public bug reported:

Upgrade happend already in Trusty

Changes were:

*Added support for X.org xserver ABI 15 (xorg-server 1.15).
*   Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module to be in conflict with the NVIDIA  OpenGL driver. This module 
can cause the NVIDIA libGL to be loaded into the same process (the X server) as 
the NVIDIA libglx.so extension module, which is not a supported use case.

Source of information:
http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk

nvidia-settings is incompatible since a while ... bug #1100994

** Affects: nvidia-graphics-drivers-173 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: precise upgrade-software-version

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

Title:
  [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  New

Bug description:
  Upgrade happend already in Trusty

  Changes were:

  *Added support for X.org xserver ABI 15 (xorg-server 1.15).
  *   Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module to be in conflict with the NVIDIA  OpenGL driver. This module 
can cause the NVIDIA libGL to be loaded into the same process (the X server) as 
the NVIDIA libglx.so extension module, which is not a supported use case.

  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk

  nvidia-settings is incompatible since a while ... bug #1100994

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1266466/+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 1266466] Re: [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

[Flames_in_Paradise]

** Description changed:

  Upgrade happend already in Trusty
  
- Changes were:
+ Precise has: 173.14.35-0ubuntu0.2 (as per today).
  
- *Added support for X.org xserver ABI 15 (xorg-server 1.15).
- *   Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module to be in conflict with the NVIDIA  OpenGL driver. This module 
can cause the NVIDIA libGL to be loaded into the same process (the X server) as 
the NVIDIA libglx.so extension module, which is not a supported use case.
+ Changes 173.14.39 are:
+ 
+ * Added support for X.org xserver ABI 15 (xorg-server 1.15).
+ * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
+   to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
+   libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
+   extension module, which is not a supported use case.
  
  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk
  
+ 
+ Changes in 173.14.38 were:
+ * Improved compatibility with recent Linux kernels.
+ 
+ Changes in 173.14.37 were:
+ * Removed a spurious dependency on libpangox from the nvidia-settings binary 
shipped 
+   as   part of the driver package.
+ * Added support for X.org xserver ABI 14 (xorg-server 1.14).
+ * Fixed font rendering performance and corruption problems on X servers with 
backported
+   support for the new glyph cache functionality added to Pixman 0.27.
+ 
+ Changes in 173.14.36 were:
+ * Fixed a bug that caused libglx.so to fail to load on 32-bit X servers.
+ * Added support for xserver 1.11.99.901 (also known as 1.12 RC1).
+ * Added support for X.Org xserver 1.11.
+ * Improved compatibility with recent Linux kernels.
+ 
+ 
  nvidia-settings is incompatible since a while ... bug #1100994

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

Title:
  [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  New

Bug description:
  Upgrade happend already in Trusty

  Precise has: 173.14.35-0ubuntu0.2 (as per today).

  Changes 173.14.39 are:

  * Added support for X.org xserver ABI 15 (xorg-server 1.15).
  * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
extension module, which is not a supported use case.

  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk

  
  Changes in 173.14.38 were:
  * Improved compatibility with recent Linux kernels.

  Changes in 173.14.37 were:
  * Removed a spurious dependency on libpangox from the nvidia-settings binary 
shipped 
as   part of the driver package.
  * Added support for X.org xserver ABI 14 (xorg-server 1.14).
  * Fixed font rendering performance and corruption problems on X servers with 
backported
support for the new glyph cache functionality added to Pixman 0.27.

  Changes in 173.14.36 were:
  * Fixed a bug that caused libglx.so to fail to load on 32-bit X servers.
  * Added support for xserver 1.11.99.901 (also known as 1.12 RC1).
  * Added support for X.Org xserver 1.11.
  * Improved compatibility with recent Linux kernels.

  
  nvidia-settings is incompatible since a while ... bug #1100994

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1266466/+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 1266466] Re: [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

[Flames_in_Paradise]

** Description changed:

- Upgrade happend already in Trusty
  
- Precise has: 173.14.35-0ubuntu0.2 (as per today).
+ Precise has: 173.14.37-0ubuntu0.0.1 (as per today) – .Upgrade happend
+ already in Trusty
  
  Changes 173.14.39 are:
  
  * Added support for X.org xserver ABI 15 (xorg-server 1.15).
  * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
-   to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
-   libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
-   extension module, which is not a supported use case.
+   to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
+   libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
+   extension module, which is not a supported use case.
  
  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk
  
- 
  Changes in 173.14.38 were:
  * Improved compatibility with recent Linux kernels.
  
- Changes in 173.14.37 were:
- * Removed a spurious dependency on libpangox from the nvidia-settings binary 
shipped 
-   as   part of the driver package.
- * Added support for X.org xserver ABI 14 (xorg-server 1.14).
- * Fixed font rendering performance and corruption problems on X servers with 
backported
-   support for the new glyph cache functionality added to Pixman 0.27.
- 
- Changes in 173.14.36 were:
- * Fixed a bug that caused libglx.so to fail to load on 32-bit X servers.
- * Added support for xserver 1.11.99.901 (also known as 1.12 RC1).
- * Added support for X.Org xserver 1.11.
- * Improved compatibility with recent Linux kernels.
- 
- 
  nvidia-settings is incompatible since a while ... bug #1100994

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

Title:
  [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  New

Bug description:

  Precise has: 173.14.37-0ubuntu0.0.1 (as per today) – .Upgrade happend
  already in Trusty

  Changes 173.14.39 are:

  * Added support for X.org xserver ABI 15 (xorg-server 1.15).
  * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
    to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
    libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
    extension module, which is not a supported use case.

  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk

  Changes in 173.14.38 were:
  * Improved compatibility with recent Linux kernels.

  nvidia-settings is incompatible since a while ... bug #1100994

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1266466/+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 1266466] Re: [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

[Flames_in_Paradise]

*** This bug is a duplicate of bug 1259237 ***
https://bugs.launchpad.net/bugs/1259237

This is proprietary so confirming this from myself, as an exception.

There is only little time left, to have this adjusted, until 12.04.4
hits the road.


** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
   Status: New = Confirmed

** Description changed:

- 
- Precise has: 173.14.37-0ubuntu0.0.1 (as per today) – .Upgrade happend
+ Precise has: 173.14.35-0ubuntu0.2 (as per today) – .Upgrade happend
  already in Trusty
  
  Changes 173.14.39 are:
  
  * Added support for X.org xserver ABI 15 (xorg-server 1.15).
  * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
    to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
    libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
    extension module, which is not a supported use case.
  
  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk
  
  Changes in 173.14.38 were:
  * Improved compatibility with recent Linux kernels.
  
  nvidia-settings is incompatible since a while ... bug #1100994

** This bug has been marked a duplicate of bug 1259237
   Hybrid graphics enablement in 12.04.4

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

Title:
  [upgrade software version] 173.14.39 released on 6/12/13 [Precise]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  Confirmed

Bug description:
  Precise has: 173.14.35-0ubuntu0.2 (as per today) – .Upgrade happend
  already in Trusty

  Changes 173.14.39 are:

  * Added support for X.org xserver ABI 15 (xorg-server 1.15).
  * Updated nvidia-installer to consider the libglamoregl.so X loadable 
extension module
    to be in conflict with the NVIDIA  OpenGL driver. This module can cause the 
NVIDIA
    libGL to be loaded into the same process (the X server) as the NVIDIA 
libglx.so
    extension module, which is not a supported use case.

  Source of information:
  http://www.nvidia.co.uk/download/driverResults.aspx/71313/en-uk

  Changes in 173.14.38 were:
  * Improved compatibility with recent Linux kernels.

  nvidia-settings is incompatible since a while ... bug #1100994

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1266466/+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 1219908] Re: [needs-packaging] All nvidia-current and nvidia-updates need repackaging to mirror official Nvidia releases...

[Flames_in_Paradise]

** Tags added: precise

** Tags added: saucy

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

Title:
  [needs-packaging] All nvidia-current and nvidia-updates need
  repackaging to mirror official Nvidia releases...

Status in Nvidia Feature Request and Bug Reporting:
  New
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” source package in Precise:
  Fix Released
Status in “nvidia-graphics-drivers-319-updates” source package in Precise:
  Fix Committed

Bug description:
  The official Nvidia long-lived-branch stable driver is now 319.49.
  That means that the recommended official driver is 319.49 and should
  be used by all Nvidia users except those using old legacy devices.
  There are important fixes that are in this driver and the previous
  319.17 that affect Chromium browser users especially:

  + Fixed a memory leak that occurred when destroying a GLX window but
  not its associated X window.

  These can crash machines using Nvidia GPU's according to a Chromium-
  bug http://crbug.com/145600 NVIDIA linux drivers are unstable when
  using multiple Open GL contexts and with low memory.: and if check
  `about:gpu` you will see this is a major reason most if not all Nvidia
  GPU's are currently blacklisted.

  Also, when using Windows 7 I am at liberty to install any driver
  version I want, keeping my machine up to date with the latest official
  Nvidia fixes.  With Ubuntu I'm stuck with older drivers that affect
  performance and contain old bugs that have already been fixed.  This
  leads to a lower quality experience than with Windows.  Drivers need
  to be kept current with upstream in my opinion.  For the time being I
  have been cherry-picking *.deb packages from X-Org-Edgers so that I
  can replicate that Windows experience and it's been working.  However,
  all Ubuntu users should have this experience as well and most do not
  know how to manually install packages using DPKG so it is out of their
  reach.

  The current Nvidia driver versions are as follows:
  http://www.nvidia.com/object/unix.html

  Long Lived Branch version: 319.49 -- `nvidia-current` should be here as 
stable
  Short Lived Branch version: 325.15 -- `nvidia-updates` should be here as 
unstable
  Legacy GPU version (304.xx series): 304.108 -- `nvidia-current-legacy` 
should be here.

  This situation has to be solved, Ubuntu cannot be so far behind the
  curve that it cannot keep Nvidia drivers fresh and in sync with the
  upstream Nvidia release schedule...

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