date:20150619

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

** This bug is no longer a duplicate of private bug 942472
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise() when selecting
  downloads

Status in transmission package in Ubuntu:
  New

Bug description:
  crashed when selecting torrents for download

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: transmission-gtk 2.50-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  8 18:57:21 2012
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  ProcCmdline: transmission-gtk
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: transmission
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-05 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/950363/+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 1438029] Re: Display Drivers

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Display Drivers

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Default installed display drivers for intel graphics media accelerator
  x4500hd

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar 30 09:16:51 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
   virtualbox, 4.3.10, 3.16.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2a84]
 Subsystem: Hewlett-Packard Company Device [103c:2a84]
  InstallationDate: Installed on 2015-03-17 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Compaq dx7500 Microtower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic 
root=UUID=fde9fdaa-3323-4ae7-8c26-a7857b7b72bb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.09
  dmi.board.name: 2A84h
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: CZC9102B97
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.09:bd12/16/2008:svnHewlett-Packard:pnHPCompaqdx7500Microtower:pvr:rvnPEGATRONCORPORATION:rn2A84h:rvr1.03:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: HP Compaq dx7500 Microtower
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Mar 29 09:48:24 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 8
   inputPixArt USB Optical Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1438029/+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 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.

2015-06-19 Thread crystal

** Changed in: yelp (Ubuntu)
   Status: Incomplete = Opinion

** Changed in: yelp (Ubuntu)
   Status: Opinion = Confirmed

** Changed in: yelp (Ubuntu)
 Assignee: (unassigned) = crystal (crystalallen831)

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

Title:
  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  after upgrading to 14.10 alpha 2 when i try to launch yelp from
  command or from menu it shows

  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

  even when i try to search it shows the same

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: yelp 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Aug 24 11:53:45 2014
  InstallationDate: Installed on 2012-03-24 (882 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324)
  SourcePackage: yelp
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1360756/+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 1437719] Re: [Dell Inspiron 5547] Black Screen on user switch

2015-06-19 Thread Rusty Shackleford

Decided there is no point adding any logs from a live-usb session
confusing the situation not knowing that they will reveal anything.
Going to put the state of this defect back to Status New since no
resolution has been found yet and await further guidance on what info I
can provide to help debug it.

** Changed in: xorg (Ubuntu)
   Status: Incomplete = New

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

Title:
  [Dell Inspiron 5547] Black Screen on user switch

Status in xorg package in Ubuntu:
  New

Bug description:
  When switching users (primarly using Ctrl-Alt-F(7-10) the monitor will
  sometimes go black. This happens once or twice a day, although on
  occasion it doesn't occur for several days. It has occurred at least
  once a week since I installed Ubuntu 14.04.1. It seems to be more of a
  problem since moving to 14.04.2 - I did perform installation of the
  Utopic Kernel, X, and MesaGL packages, but this is only perception. At
  the same time I switched from Unity to Cinnamon (Jeremy Clarkson isn't
  the only dinosaur roaming the world) - but I have confirmed that just
  running Unity desktops is vunerable.

  The display can be restored by sudo service lightdm restart - run from
  an ssh login from another system.

  Steps to consistently reproduce the problem is simply to perform
  abusive user stress testing: switching from one user to another
  rapidly: as soon as the display switches go back to the other. Usually
  I can get a black screen with this method in under a minute with Unity
  desktops.

  I have the same issue with another system (Dell Vostro 3550) reported
  in Bug #1437557 - submitting a new defect since this is different
  hardware and even though the defects look the same there might be
  differences underneath the hood causing the problem.

  
  14.04.2 Trusty
  3.16.0-33-generic.
  I'll edit this report shortly with additional system info.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar 28 14:45:26 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:063e]
  InstallationDate: Installed on 2014-12-23 (95 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5547
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic 
root=UUID=6eb0eadb-81ed-43ee-aab3-e3fe6b37ca75 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/12/2014:svnDellInc.:pnInspiron5547:pvrA05:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 5547
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar 27 15:14:18 2015
  xserver.configfile: default
  xserver.errors:
   SynPS/2 Synaptics TouchPad: Read error 19
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Desktop-packages] [Bug 1323825] Re: transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

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

** This bug is no longer a duplicate of bug 1304004
   transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()
** This bug has been marked a duplicate of bug 1324564
   transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

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

Title:
  transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

Status in transmission package in Ubuntu:
  New

Bug description:
  I downloaded a torrent-file
  (http://www.stresslinux.org/sl/downloads/55.torrent). After
  downloading = double-click. = transmission crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: transmission-gtk 2.82-1.1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 27 22:10:52 2014
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2013-12-29 (149 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: transmission-gtk 
/home/username/Downloads/stresslinux/stresslinux_64bit_11.4.x86_64-0.7.106.iso.bz2.torrent
  SegvAnalysis:
   Segfault happened at: 0x7fbd40a8fb19 gnutls_x509_crt_import+25:mov
(%rsi),%rsi
   PC (0x7fbd40a8fb19) ok
   source (%rsi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: transmission
  StacktraceTop:
   gnutls_x509_crt_import () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
  Title: transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()
  UpgradeStatus: Upgraded to trusty on 2014-03-30 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1323825/+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 1467033] [NEW] package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to '/usr/lib

2015-06-19 Thread mark

Public bug reported:

will not boot in normal mode and sends to busy box when booting

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libreoffice-common 1:4.2.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Thu Jun 18 20:29:42 2015
DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu2:cannot copy 
extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2015-02-28 (111 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1)
PackageArchitecture: all
SourcePackage: libreoffice
Title: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' 
to '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of 
file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade:
  cannot copy extracted data for
  './usr/lib/libreoffice/share/gallery/sg24.sdv' to
  '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end
  of file or stream

Status in libreoffice package in Ubuntu:
  New

Bug description:
  will not boot in normal mode and sends to busy box when booting

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Thu Jun 18 20:29:42 2015
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu2:cannot copy 
extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-02-28 (111 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' 
to '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of 
file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1467033/+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 1437725] Re: Mouse flickering using 3 screens on 2 graphic adapters

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Mouse flickering using 3 screens on 2 graphic adapters

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   30.935310] init: plymouth-upstart-bridge main process ended, respawning
   [  795.191467] audit_printk_skb: 123 callbacks suppressed
   [  795.191470] type=1400 audit(1427576703.540:74): apparmor=STATUS 
operation=profile_replace profile=unconfined 
name=/usr/lib/cups/backend/cups-pdf pid=3091 comm=apparmor_parser
   [  795.191475] type=1400 audit(1427576703.540:75): apparmor=STATUS 
operation=profile_replace profile=unconfined name=/usr/sbin/cupsd 
pid=3091 comm=apparmor_parser
   [  795.191768] type=1400 audit(1427576703.540:76): apparmor=STATUS 
operation=profile_replace profile=unconfined name=/usr/sbin/cupsd 
pid=3091 comm=apparmor_parser
  Date: Sat Mar 28 21:11:47 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] 
[1002:6719] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2307]
  InstallationDate: Installed on 2015-02-01 (55 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic 
root=UUID=c51a3625-d8fc-49d8-94b8-f29e4c8b25f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/16/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Mar 28 20:52:12 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437725/+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 1441414] Re: Monitor graphics problem

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Monitor graphics problem

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I am having a problem with my monitor, since about a week now all that
  appears is stretched horizontally making it impossible to see
  everything on the screen, i have tried everything and I am unable to
  change it back to normal view. Can you help me fix this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr  7 20:39:10 2015
  DistUpgraded: 2014-10-25 17:41:12,216 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:0102]
  InstallationDate: Installed on 2014-02-21 (410 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic 
root=UUID=b383f696-c9bc-4390-acc7-11aec39bddf1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-10-25 (164 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H61M-DGS
  dmi.board.vendor: ASRock
  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.:bvrP1.20:bd04/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-DGS:rvr: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.20150122-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  7 20:37:16 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputPS/2+USB Mouse   MOUSE, id 9
   inputDell Dell USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1441414/+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 1439859] Re: Bug on the screen

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Bug on the screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Block strip around the windows. Even the right click widow also
  getting the block box around.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  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: Thu Apr  2 15:25:55 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0577]
  InstallationDate: Installed on 2014-10-15 (168 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=b4be5a89-3a7d-4e30-9c27-1abe2256de60 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0WR7PY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141215.99537089-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Thu Apr  2 14:13:22 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors: intel: Failed to load module present (module does not 
exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439859/+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 1440577] Re: GUI filled with random shapres instead of user interface.

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  GUI filled with random shapres instead of user interface.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  To reproduce boot the April 5th dialy amd64 live iso of lubuntu and
  and select try lubuntu without installing. Plymoth will show up and
  youi ar egreeted with a screen of random shapes. The underlying system
  still seems to work for user input for the keyboard as control alt t
  opened up a terminal and pressing alt f2 the run shorcut brought up a
  dialog and lauunched firefox although a corrupted window launched.

  
  Description Ubuntu Vivid Vervet (development branch)
  Release : 15.04 

  I expected a readable GUI that I could navigate.

  Instead the UI looked entierly corrupted in X.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1440577/+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 1304004] Re: transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

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

** This bug has been marked a duplicate of bug 1324564
   transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

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

Title:
  transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Tried to download a bittorrent containing a pdf file. Transmission
  crashed before it downloaded anything (seemingly).

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: transmission-gtk 2.82-1.1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Apr  7 21:04:18 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2013-02-16 (415 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130207.1)
  LocalLibraries: /usr/local/lib/librtmp.so.0
  ProcCmdline: transmission-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3f93adab19 gnutls_x509_crt_import+25:mov
(%rsi),%rsi
   PC (0x7f3f93adab19) ok
   source (%rsi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: transmission
  StacktraceTop:
   gnutls_x509_crt_import () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
  Title: transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()
  UpgradeStatus: Upgraded to trusty on 2014-02-06 (59 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1304004/+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 1467033] Re: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to '/usr/lib/l

2015-06-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade:
  cannot copy extracted data for
  './usr/lib/libreoffice/share/gallery/sg24.sdv' to
  '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end
  of file or stream

Status in libreoffice package in Ubuntu:
  New

Bug description:
  will not boot in normal mode and sends to busy box when booting

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Thu Jun 18 20:29:42 2015
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu2:cannot copy 
extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-02-28 (111 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' 
to '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of 
file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1467033/+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 1467039] Re: My lenovo t540p with Ubuntu 14.04 freezes very often

2015-06-19 Thread Ehsan

Related to https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1184451

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

Title:
  My lenovo t540p with Ubuntu 14.04 freezes very often

Status in xorg package in Ubuntu:
  New

Bug description:
  I need to reboot each time as it freezes forever. Many people are
  having this issue unfortunately.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  Uname: Linux 3.19.0-031900rc2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  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: Fri Jun 19 20:19:35 2015
  DistUpgraded: 2014-05-08 21:45:39,590 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: 8192cu, 1.10, 3.19.0-031900rc2-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2210]
  InstallationDate: Installed on 2014-03-25 (451 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BECTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900rc2-generic 
root=UUID=3184abc7-3a2d-41bb-abbd-db9c6305619e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-09 (406 days ago)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET70WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET70WW(2.18):bd03/05/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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: Fri Jun 19 20:05:15 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5556 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1467039/+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 1448272] Re: White line between the interface and the application window title

2015-06-19 Thread Ubuntu Foundations Team Bug Bot

The attachment style.css patch to remove the 1px border of the primary
toolbar seems to be a patch.  If it isn't, please remove the patch
flag from the attachment, remove the patch tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  White line between the interface and the application window title

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description: Ubuntu 15.04
  Release: 15.04

  Software version
  rhythmbox 3.1-1ubuntu3

  What i expected to happen
   I think that space between header and application interface should not 
exist

  Additional information:
  I just installed OS. Packages upgraded to the latest version from the 
repositories.
  Screen: 22 inch 1920x1080

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1448272/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-06-19 Thread Nigel Pegram

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

The PPA fix at https://launchpad.net/~tj/+archive/ubuntu/nvidia worked
for my 14.04 LTS release. (Update versions installed.)

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in NVIDIA Drivers Ubuntu:
  Fix Released
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-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released

Bug description:
  2015-06-16 TJ:

  I've published a possibly fixed package for Trusty to my PPA at:

  https://launchpad.net/~tj/+archive/ubuntu/nvidia

  Please test and report back if that fixes the issue. If it does I can
  attach the fixed branch to bug #1431753 where the other release fixes
  are being tracked.

  --- original bug report follows 

  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for LUG in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  Update 2015-05-23:
  As of the recent kernel update (3.13.0-53), the above two commands followed 
by a reboot may not fix it. Instead:

  $ sudo apt-get install --reinstall nvidia-331 nvidia-331-uvm

  followed by a reboot.

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1467033] Re: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to '/usr/lib/l

2015-06-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

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

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade:
  cannot copy extracted data for
  './usr/lib/libreoffice/share/gallery/sg24.sdv' to
  '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end
  of file or stream

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  will not boot in normal mode and sends to busy box when booting

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Thu Jun 18 20:29:42 2015
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu2:cannot copy 
extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/libreoffice/share/gallery/sg24.sdv' to 
'/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-02-28 (111 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu2 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libreoffice/share/gallery/sg24.sdv' 
to '/usr/lib/libreoffice/share/gallery/sg24.sdv.dpkg-new': unexpected end of 
file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1467033/+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 1458981] Re: Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem Cannot turn on display power on i915

2015-06-19 Thread Canaan

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

the patch does seem to have fixed the problem. I am getting full sound
thru HDMI output. All is well again. Thank you.

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

Title:
  Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH,
  playback] Playback problem Cannot turn on display power on i915

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Digital playback was working just fine. HDMI connected to 32 Vizio
  television from msi Z97 PC Mate Motherboard. Now no digital output,
  not even as an option. Analog audio works just fine. When I plug
  headphones in there is no problem. that is all identified in Settings
  panel and terminal commands used for troubleshooting. but the HDMI
  output does not appear to be recognized as everything says Analog.
  Ubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canibal2344 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 26 14:59:34 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-05 (293 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (30 days ago)
  dmi.bios.date: 04/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd04/18/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1458981/+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 1467039] [NEW] My lenovo t540p with Ubuntu 14.04 freezes very often

2015-06-19 Thread Ehsan

Public bug reported:

I need to reboot each time as it freezes forever. Many people are having
this issue unfortunately.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
Uname: Linux 3.19.0-031900rc2-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
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: Fri Jun 19 20:19:35 2015
DistUpgraded: 2014-05-08 21:45:39,590 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: 8192cu, 1.10, 3.19.0-031900rc2-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2210]
InstallationDate: Installed on 2014-03-25 (451 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: LENOVO 20BECTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900rc2-generic 
root=UUID=3184abc7-3a2d-41bb-abbd-db9c6305619e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-09 (406 days ago)
dmi.bios.date: 03/05/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET70WW (2.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET70WW(2.18):bd03/05/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20BECTO1WW
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
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: Fri Jun 19 20:05:15 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5556 
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  My lenovo t540p with Ubuntu 14.04 freezes very often

Status in xorg package in Ubuntu:
  New

Bug description:
  I need to reboot each time as it freezes forever. Many people are
  having this issue unfortunately.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  Uname: Linux 3.19.0-031900rc2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  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: Fri Jun 19 20:19:35 2015
  DistUpgraded: 2014-05-08 21:45:39,590 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: 8192cu, 1.10, 3.19.0-031900rc2-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2210]
  InstallationDate: Installed on 2014-03-25 (451 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BECTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900rc2-generic 
root=UUID=3184abc7-3a2d-41bb-abbd-db9c6305619e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-09 (406 days ago)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET70WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor:

[Desktop-packages] [Bug 775635] Re: blocklist will not update in ubuntu 11.04

does this ever occur in trusty or later?

It works for me in trusty now while I was able to reproduce the problem
in lucid.  What I do see is a discrepancy between the numbers in the
Update Blocklist window telling me the blocklist has X rules and the
resulting window in preferences saying it has Y rules.

** Changed in: transmission (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: transmission (Ubuntu)
 Assignee: (unassigned) = Rolf Leggewie (r0lf)

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

Title:
  blocklist will not update in ubuntu 11.04

Status in transmission package in Ubuntu:
  Incomplete
Status in transmission source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: transmission

  fresh install of ubuntu 11.04 using gnome desktop. blocklist rules
  will not update.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: transmission-gtk 2.13-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon May  2 10:47:21 2011
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/775635/+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 1158839] Re: transmission-gtk crashed with SIGABRT in raise()

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

** This bug is no longer a duplicate of private bug 958764
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise()

Status in transmission package in Ubuntu:
  New

Bug description:
  transmission-gtk crashed with SIGABRT in raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: transmission-gtk 2.77-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Fri Mar 22 20:48:35 2013
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2013-03-20 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130319)
  MarkForUpload: True
  ProcCmdline: transmission-gtk
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: transmission
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1158839/+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 1103597] Re: transmission-gtk crashed with SIGABRT in raise()

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

** This bug is no longer a duplicate of private bug 958764
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise()

Status in transmission package in Ubuntu:
  New

Bug description:
  Nothing

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: transmission-gtk 2.76-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  Date: Wed Jan 23 12:56:38 2013
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2012-12-07 (46 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: transmission-gtk 
/home/username/Downloads/[kat.ph]angry.beavers.complete.series.torrent
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: transmission
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1103597/+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 963849] Re: transmission-gtk crashed with SIGABRT in raise()

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

** This bug is no longer a duplicate of private bug 958764
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise()

Status in transmission package in Ubuntu:
  New

Bug description:
  Adding torrents.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: transmission-gtk 2.50-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  Date: Sat Mar 24 05:17:04 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 
(20120201.2)
  ProcCmdline: transmission-gtk /tmp/Kayden.Kross.XXX.MegaPack.torrent
  Signal: 6
  SourcePackage: transmission
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/963849/+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 984008] Re: transmission-gtk crashed with SIGABRT in raise()

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

** This bug is no longer a duplicate of private bug 958764
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise()

Status in transmission package in Ubuntu:
  New

Bug description:
  Starting download Ubuntu 12.04 Beta 2 torrent and error report pop up

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: transmission-gtk 2.51-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: i386
  Date: Tue Apr 17 17:11:00 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcCmdline: transmission-gtk /tmp/ubuntu-12.04-beta2-desktop-i386.iso.torrent
  Signal: 6
  SourcePackage: transmission
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-10 (37 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/984008/+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 973763] Re: transmission-gtk crashed with SIGABRT in raise()

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

** This bug is no longer a duplicate of private bug 958764
** This bug has been marked a duplicate of private bug 941105

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

Title:
  transmission-gtk crashed with SIGABRT in raise()

Status in transmission package in Ubuntu:
  New

Bug description:
  I dont know.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: transmission-gtk 2.50-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic i686
  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  Date: Wed Apr  4 22:44:38 2012
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcCmdline: transmission-gtk 
/tmp/[BELOAD-386244]The.Way.2010.CUSTOM.DVDRip.X.torrent
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: transmission
  Title: transmission-gtk crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-17 (18 days ago)
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/973763/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Stefan Bader

Alberto is rolling this back into older releases over time. To be fair
it is an annoying issue but not one that is so fatal one would not be
able to recover a system. In the majority of cases this ends up being
just a false system issue notification. Because on kernel update the
parallel builds are actually started 3 times. By now I just made it a
habit of doing the following whenever kernel updates come in:

- run dkms status to see whether both nvidia modules appear for the latest 
kernel (bbswitch is always there)
- if one(or both) is missing, do sudo dkms install -m module -v module 
version -k kernel version
   (the name and versions taken from the dkms status report)
- sudo rm /var/crash/*nvidia* to ignore the build failures before

When the fixed version of the driver hits this can be noticed by having
only one module reported by dkms for nvidia. The *-uvm one will be gone
and the module it produced will be part of the remaining dkms module
which then produces two kernel modules.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1443456] Re: Xorg crashed with SIGABRT in fbBltOne()

2015-06-19 Thread mrl586

I have tested LibreOffice 4.4 with Debian and I have noticed following:

Xorg 1.17.1 with radeon driver - not work
Xorg 1.17.1 with fglrx - it works!
Xorg 1.16.4 with radeon driver - it works!

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

Title:
  Xorg crashed with SIGABRT in fbBltOne()

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  system restarts when trying to open libreoffice writer, just after the
  installation of the latest updates (after a fresh install)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.17.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17-0ubuntu2
  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
  CrashCounter: 1
  Date: Mon Apr 13 16:32:19 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] 
[1002:1309] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3830]
  InstallationDate: Installed on 2015-04-13 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 80EC
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   fbBltOne () from /usr/lib/xorg/modules/libfb.so
   fbCopy1toN () from /usr/lib/xorg/modules/libfb.so
   ?? () from /usr/lib/xorg/modules/libglamoregl.so
   miCopyRegion ()
   miDoCopy ()
  Title: Xorg crashed with SIGABRT in fbBltOne()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A4CN32WW (V 2.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B3
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-75
  dmi.modalias: 
dmi:bvnLENOVO:bvrA4CN32WW(V2.01):bd09/11/2014:svnLENOVO:pn80EC:pvrLenovoZ50-75:rvnLENOVO:rnLancer5B3:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ50-75:
  dmi.product.name: 80EC
  dmi.product.version: Lenovo Z50-75
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Apr 13 16:32:28 2015
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1443456/+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 1300514] Re: Account with UID 501 disappeared after update

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: accountsservice (Ubuntu)
   Status: New = Confirmed

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

Title:
  Account with UID 501 disappeared after update

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  After today performing a system update from 13.10 [previously updated
  cca 1mo ago], my account with UID has disappeared from lightdm.

  /etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have
  all been configured to treat users with minimum UID 500 as regular
  users.

  The remark in users.conf mentioning AccountsService gave me a hint to
  explore what this service is.  It's very nasty that this completely
  opaque and unknown service determines whether an account will appear
  on the list or not.

  Digging around its process /usr/lib/accountsservice/accounts-daemon
  (what a nasty place to put this binary) using strace, I noticed
  /var/lib/AccountsService/users/myusername is being accessed. This may
  be obvious to developers, but to someone troubleshooting, it's bad and
  unexpected.

  I fixed my issue by editing the aforementioned file and replacing
  SystemAccount=true with SystemAccount=false, killing the accounts-
  daemon and (to avoid restart) starting it in terminal. This would all
  be worth just a rant instead of a bug report, were it not for the fact
  that only today have I logged in correctly from the main screen,
  updated the system, and after only a reboot -- without touching or
  knowing about /var/lib/AccountsService/users directory -- my account
  has disappeared. Either this directory was automagically touched, or
  SystemAccount=true previously didn't affect lightdm.

  Please provide and expose a canonical and universal place to determine
  minimum UID for the system to treat a user account as a human
  account. Having three somewhat-documented files and none of them
  having effect upon accountsservice is quite bad.

  If this package is inappropriate for this bug report, please reassign.

  [The reason why UID 1000 is no-good are OS X partitions -- on which
  I'd like to be able to access my files without resorting to sudo
  voodoo. The default UID on OS X happens to be 501.]

  Package version: 0.6.34-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr  1 00:43:23 2014
  InstallationDate: Installed on 2014-02-18 (41 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-06-19 Thread Nima

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

I want to go to another linux distribution ,
Can any body give me a hint about it?
CentOS or Opensuse? Which one is better?
which one has a full resource of software like ,for example ubuntu
software center?
Thanks for any help in advance

Best Regards,
Nima Soltani
--
Graduate Student of Physical Chemistry
Department of Chemistry,
Sharif University of Technology.
=

On Wed, Jun 17, 2015 at 11:39 AM, William Grant m...@williamgrant.id.au
wrote:

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

 ** This bug has been marked a duplicate of bug 1431753
Nvidia binary driver FTBS due to DKMS layer violation

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1268257

 Title:
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
   failed to build, with only error: objdump: '... .tmp_nv.o': No such
   file

 Status in NVIDIA Drivers Ubuntu:
   Fix Released
 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-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released

 Bug description:
   2015-06-16 TJ:

   I've published a possibly fixed package for Trusty to my PPA at:

   https://launchpad.net/~tj/+archive/ubuntu/nvidia

   Please test and report back if that fixes the issue. If it does I can
   attach the fixed branch to bug #1431753 where the other release fixes
   are being tracked.

   --- original bug report follows 

   **WARNING:** This bug has been widely reported and has *many*
   automatic subscribers. Please be considerate.

   **If you need help:** try searching and asking on
   http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
   nearby user group (see http://loco.ubuntu.com or search for LUG in
   your area). Link back to this bug for clarity.

   ---

   This seems to fix it (at least for one version upgrade) for many
   people

   $ sudo dpkg-reconfigure nvidia-331

   after that...

   $ sudo dpkg-reconfigure nvidia-331-uvm

   (some users may be on the versions of these packages suffixed with
   -updates )

   Update 2015-05-23:
   As of the recent kernel update (3.13.0-53), the above two commands
 followed by a reboot may not fix it. Instead:

   $ sudo apt-get install --reinstall nvidia-331 nvidia-331-uvm

   followed by a reboot.

   ---

   **If you want to unsubscribe:** see
   https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
   drivers-331-updates/+bug/1268257/+subscribe. You can also change your
   settings so you don't get comments but do get notified when the bug is
   solved - see https://askubuntu.com/questions/576523 for details.

   **If you want to comment:** Please consider if you have something
   meaningful to contribute to the 2500+ people who will get an email.

   **If you are an Ubuntu developer:** thanks for looking into this! :D

   

   Nvidia kernel module failed to build on kernel 3.13.0-2
   Yesterday when the new kernel was pushed, the dkms process failed.

   ProblemType: Package
   DistroRelease: Ubuntu 14.04
   Package: nvidia-331-updates 331.20-0ubuntu9
   ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
   Uname: Linux 3.12.0-7-generic x86_64
   ApportVersion: 2.13.1-0ubuntu1
   Architecture: amd64
   DKMSKernelVersion: 3.13.0-2-generic
   Date: Sun Jan 12 01:28:35 2014
   InstallationDate: Installed on 2013-11-03 (69 days ago)
   InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
 (20131016.1)
   PackageVersion: 331.20-0ubuntu9
   SourcePackage: nvidia-graphics-drivers-331-updates
   Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel
 module failed to build
   UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions


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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in NVIDIA Drivers Ubuntu:
  Fix Released
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-graphics-drivers-340 package

[Desktop-packages] [Bug 1466870] [NEW] some traditional Chinese words can only be entered if simplified Chinese is also enabled

2015-06-19 Thread Sirius

Public bug reported:

In settings there is 'Chinese mode' with 5 options: Simplified Chinese,
Traditional Chinese, Simplified Chinese before Traditional Chinese,
Traditional Chinese before Simplified Chinese, and All Chinese
characters

If traditional Chinese only mode is selected, some characters common to both
traditional and simplified Chinese cannot be entered.
For example,
In traditional Chinese only mode, entering ‘RC’ (口金) only suggest 叭 and 唫. 只 is
not available
In traditional Chinese only mode, entering ‘EYG’ (水卜土) only suggest 塰. 注 is not
available
In any other mode that include simplified Chinese characters, 只 and 注 are
listed in suggestions as expected.

Ubuntu Gnome 15.04
ibus 1.5.9-1ubuntu3
ibus-table 1.9.1-3ubuntu1
ibus-table-cangjie5 1.8.2-1

P.S. cangjie code for 塰 should be 水十土 or 水卜十土, not 水卜土. But that's a
completely unrelated issue.

** Affects: ibus-table-cangjie (Ubuntu)
Importance: Undecided
Status: New

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

Title:
some traditional Chinese words can only be entered if simplified
Chinese is also enabled

Status in ibus-table-cangjie package in Ubuntu:
New

Bug description:
In settings there is 'Chinese mode' with 5 options: Simplified
Chinese, Traditional Chinese, Simplified Chinese before Traditional
Chinese, Traditional Chinese before Simplified Chinese, and All
Chinese characters

If traditional Chinese only mode is selected, some characters common to both
traditional and simplified Chinese cannot be entered.
For example,
In traditional Chinese only mode, entering ‘RC’ (口金) only suggest 叭 and 唫. 只
is not available
In traditional Chinese only mode, entering ‘EYG’ (水卜土) only suggest 塰. 注 is
not available
In any other mode that include simplified Chinese characters, 只 and 注 are
listed in suggestions as expected.

Ubuntu Gnome 15.04
ibus 1.5.9-1ubuntu3
ibus-table 1.9.1-3ubuntu1
ibus-table-cangjie5 1.8.2-1

P.S. cangjie code for 塰 should be 水十土 or 水卜十土, not 水卜土. But that's a
completely unrelated issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-table-cangjie/+bug/1466870/+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 395322] Re: Load averages should be moved to Resources tab

2015-06-19 Thread Karl-Philipp Richter

After the redesign mentioned in the upstream bug there's no system load
displayed at all. It'd make sense to add a resource monitor for it (like
there's for CPU, memory and network). Reopen this issue or create a new
one?

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

Title:
  Load averages should be moved to Resources tab

Status in The GNOME System Monitor:
  Expired
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-system-monitor

  After working on this bug:
  https://bugs.edge.launchpad.net/hundredpapercuts/+bug/389133

  and spending time working on the Processes tab, I've realized that the
  Load Averages at the top are ugly and out of place on the process tab
  and should be moved to the resources tab.

  If somebody else agrees with me, I will create a patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/395322/+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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread İsmail Arılık

Friends, are you kidding? It is enough, please do not pollute this thread
any longer! If you wonder anything, please google it first. If you cannot
find anything, open a new issue in a related place. Be more responsive
please!

Sorry, I have also made dirty the mail thread but these were necessary to
tell.
Scroll  to the very bottom  and follow  the link


Sent from my Sprint Samsung Galaxy S® 6. Original message 
From: Umut Yazgan umut@gmail.com
Date: 06/19/2015  6:06 AM  (GMT-07:00)
To: zew...@yahoo.com
Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
  violation

Hello how can I unsubscribe this?
On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com
wrote:

 I am already working on it (I've been busy with other work). There's no
 need to make this any more complicated than it needs to be.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1395993).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Confirmed

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:


https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions


--
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to

[Desktop-packages] [Bug 1464365] Re: Resolution is incorrect; screen mostly occluded

** Changed in: xorg (Ubuntu)
   Status: New = Triaged

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

Title:
  Resolution is incorrect; screen mostly occluded

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I have a 3440x1440 monitor and after today's full dist-upgrade, most
  of the screen real-estate is unusable.  I see a small rectangular
  patch in the lower left corner, and on this patch I can right-button
  to bring up the menu.  While the rest of the screen will display the
  cursor, it is neither the correct background color (nor can it be set
  to the right color; it's just black), and the rest of the screen will
  not respond to mouse clicks at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jun 11 15:02:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2014-11-22 (201 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141120)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=9d28685f-2eae-4d72-8bdc-73fd28aba577 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.12.1+15.10.20150511-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jun 11 14:57:39 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.17.1-0ubuntu4
  xserver.video_driver: vmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1464365/+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 64295] Re: [Upstream] [hardy] Can't paste a table inside another table in Writer

Bryan Quigley, thanks for the the response.

Unfortunately, LO 4.4.3 is not available via an official Ubuntu
repository.

Also, as WORKAROUNDs are not fixes, this would not fit the criteria of
Fix Released as defined in https://wiki.ubuntu.com/Bugs/Status .

As well, this is still reproducible in the latest version of LO
available in an official Ubuntu repository.

lsb_release -rd  apt-cache policy libreoffice-writer
Description:Ubuntu 15.04
Release:15.04
libreoffice-writer:
  Installed: 1:4.4.2-0ubuntu1
  Candidate: 1:4.4.2-0ubuntu1
  Version table:
 *** 1:4.4.2-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

** Description changed:

  1) lsb_release -rd
  Description:Ubuntu 11.04
  Release:11.04
  
  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
-   Installed: 1:3.3.2-1ubuntu5
-   Candidate: 1:3.3.2-1ubuntu5
-   Version table:
-  *** 1:3.3.2-1ubuntu5 0
- 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
+   Installed: 1:3.3.2-1ubuntu5
+   Candidate: 1:3.3.2-1ubuntu5
+   Version table:
+  *** 1:3.3.2-1ubuntu5 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
- 100 /var/lib/dpkg/status
-  1:3.3.2-1ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
+ 100 /var/lib/dpkg/status
+  1:3.3.2-1ubuntu4 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  
  3) What is expected to happen in LibreOffice Writer via the Terminal:
  
  cd ~/Desktop  wget
- 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/64295/+attachment/18400/+files/20061006_final_pres_handout.odt
+ 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295/+attachment/18400/+files/20061006_final_pres_handout.odt
   lowriter -nologo 20061006_final_pres_handout.odt
  
  click box to right of [GP Practice?] - Edit - Select All - Edit -
  Copy - click cell below Joe elects Option A - Edit - Paste and the
  table is pasted into cell.
  
  4) What happens instead is the table is not pasted, but the word Car is
  pasted into the cell, and 30,000 is pasted into the cell to the right.
  
  WORKAROUND: Use AbiWord.
  
  apt-cache policy abiword
  abiword:
-   Installed: 2.8.6-0.3build1
-   Candidate: 2.8.6-0.3build1
-   Version table:
-  *** 2.8.6-0.3build1 0
- 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
+   Installed: 2.8.6-0.3build1
+   Candidate: 2.8.6-0.3build1
+   Version table:
+  *** 2.8.6-0.3build1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

** Changed in: libreoffice (Ubuntu)
   Status: Fix Released = Triaged

** Summary changed:

- [Upstream] [hardy] Can't paste a table inside another table in Writer
+ [Upstream] Can't paste a table inside another table in Writer

** Tags added: amd64 i386 precise trusty utopic vivid wily

** Tags added: natty

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

Title:
  [Upstream] Can't paste a table inside another table in Writer

Status in LibreOffice Productivity Suite:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:Ubuntu 11.04
  Release:11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.2-1ubuntu5
    Candidate: 1:3.3.2-1ubuntu5
    Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop  wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295/+attachment/18400/+files/20061006_final_pres_handout.odt
   lowriter -nologo 20061006_final_pres_handout.odt

  click box to right of [GP Practice?] - Edit - Select All - Edit -
  Copy - click cell below Joe elects Option A - Edit - Paste and the
  table is pasted into cell.

  4) What happens instead is the table is not pasted, but the word Car
  is pasted into the cell, and 30,000 is pasted into the cell to the
  right.

  WORKAROUND: Use AbiWord.

  apt-cache policy abiword
  abiword:
    Installed: 2.8.6-0.3build1
    Candidate: 2.8.6-0.3build1
    Version table:
   *** 2.8.6-0.3build1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/64295/+subscriptions

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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Zewbie

Scroll  to the very bottom  and follow  the link

Sent from my Sprint Samsung Galaxy S® 6. Original message 
From: Umut Yazgan umut@gmail.com 
Date: 06/19/2015  6:06 AM  (GMT-07:00) 
To: zew...@yahoo.com 
Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
  violation 

Hello how can I unsubscribe this?
On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com
wrote:

 I am already working on it (I've been busy with other work). There's no
 need to make this any more complicated than it needs to be.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1395993).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Confirmed

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1466824] [NEW] When suspend message appeared in top left corner and after using computer upower crashed

2015-06-19 Thread Mohammed Alkindi

Public bug reported:

Upower crashed after activating my computer and after automatic suspend
appeared

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upower 0.9.23-2ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20~14.04.1-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: amd64
Date: Fri Jun 19 15:09:29 2015
InstallationDate: Installed on 2015-03-15 (95 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
SourcePackage: upower
UpgradeStatus: Upgraded to utopic on 2015-06-18 (0 days ago)

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


** Tags: amd64 apport-bug third-party-packages utopic

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

Title:
  When suspend message appeared in top left corner and after using
  computer upower crashed

Status in upower package in Ubuntu:
  New

Bug description:
  Upower crashed after activating my computer and after automatic
  suspend appeared

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20~14.04.1-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: amd64
  Date: Fri Jun 19 15:09:29 2015
  InstallationDate: Installed on 2015-03-15 (95 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: upower
  UpgradeStatus: Upgraded to utopic on 2015-06-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1466824/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread teo1978

 Nima this really isn't the place for that talk.

It has become the place since nobody has given a fuck about fixing this
huge system-screwing bug for years (and even now, they insist in
treating it as a minor annoyance).

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Jonners59

Please stop this banter, clogging my emails up.

I sorted my PCs and laptops out with the following fix for now.  Not had
ANY issues since doing below:

Card driver
http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

nVidia

Boot and after GRUB…
Control+ALT+F1
Sudo su
sudo update-pciids
sudo lspci -v -s 01:00.0


Sudo service lightdm stop (stopping lightdm)
sudo apt-get clean  apt-get autoclean  apt-get autoremove (a little 
cleaning)
sudo apt-get update  apt-get install –f  (update source and fix)
sudo apt-get purge libvdpau-va-gl1 bumblebee* nvidia*
OR
dpkg -l | grep nvidia
lists everything installed for nvidia
then remove everything except
nvidia-cg-toolkit (if it or equivellent exists)
nvidia-common
sudo apt-get purge nvidia- (where  is anything from the list)

sudo apt-get autoremove
sudo dpkg-reconfigure nvidia-common (should return a message does not exist)
sudo apt-get install nvidia-352 nvidia-settings nvidia-prime nvidia-current 
nvidia-cg-toolkit nvidia-common
OR
Sudo apt-get install --reinstall nvidia-xxx-updates-uvm (install nvidia-xxx 
where xxx is driver version: 304, 331, 340, 349, 352 or current)

sudo apt-get install xserver-xorg-video-nouveau
sudo apt-get install linux-headers-generic
sudo apt-get clean  apt-get autoclean  apt-get autoremove
sudo apt-get apt-get upgrade  update  apt-get install –f
sudo update-alternatives --config x86_64-linux-gnu_gl_conf
sudo ldconfig -n
sudo update-initramfs -u
sudo shutdown –r now


Let the devs get on and do perm fix in the meantime.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1464925] Re: Installed and attempted to use Mbuntu

2015-06-19 Thread Marc Deslauriers

Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

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

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

Title:
  Installed and attempted to use Mbuntu

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I followed the instructions on the web site for MacBuntu, installed
  and was able to run for a short period of time, perhaps three hours.
  Then I began getting messages that Ubuntu had developed internal
  problems and needed to be shut down.  That was two days ago. Today I
  again had several programs stop, lock up the computer, ShotWell,
  Audacious, VLC, RythomBox.  Attempted to remove Mbuntu following the
  commands to restore system. Total failure and crash.  What is next??

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jun 13 15:46:05 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D] 
[1002:990c] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  InstallationDate: Installed on 2015-06-11 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 
(20150422)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=baaae4ff-e2ca-4d3b-97c8-4f24c67b9b50 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Jun 13 15:37:28 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1464925/+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 1466235] Re: Xorg crash

2015-06-19 Thread Marc Deslauriers

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  when system do two or three process it come back to login page

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun 18 03:09:03 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-53-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-54-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-55-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0651]
  InstallationDate: Installed on 2015-01-19 (149 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=b21e5ae6-b281-43f4-843f-e37c074abc16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 09V1VC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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: Wed Jun 17 20:47:06 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5567 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.7

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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Umut Yazgan

Hello how can I unsubscribe this?
On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com
wrote:

 I am already working on it (I've been busy with other work). There's no
 need to make this any more complicated than it needs to be.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1395993).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Confirmed

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions


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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Zewbie

You may remove yourself from this thread at anytime, since you have
seemed to have resolved this issue thanks and all the best.

Sent from my Sprint Samsung Galaxy S® 6. Original message 
From: Jonners59 1431...@bugs.launchpad.net 
Date: 06/19/2015  5:49 AM  (GMT-07:00) 
To: zew...@yahoo.com 
Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
  violation 

Please stop this banter, clogging my emails up.

I sorted my PCs and laptops out with the following fix for now.  Not had
ANY issues since doing below:

Card driver
http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

nVidia

Boot and after GRUB…
Control+ALT+F1
Sudo su
sudo update-pciids
sudo lspci -v -s 01:00.0

Sudo service lightdm stop (stopping lightdm)
sudo apt-get clean  apt-get autoclean  apt-get autoremove (a little 
cleaning)
sudo apt-get update  apt-get install –f  (update source and fix)
sudo apt-get purge libvdpau-va-gl1 bumblebee* nvidia*
OR
dpkg -l | grep nvidia
lists everything installed for nvidia
then remove everything except
nvidia-cg-toolkit (if it or equivellent exists)
nvidia-common
sudo apt-get purge nvidia- (where  is anything from the list)

sudo apt-get autoremove
sudo dpkg-reconfigure nvidia-common (should return a message does not exist)
sudo apt-get install nvidia-352 nvidia-settings nvidia-prime nvidia-current 
nvidia-cg-toolkit nvidia-common
OR
Sudo apt-get install --reinstall nvidia-xxx-updates-uvm (install nvidia-xxx 
where xxx is driver version: 304, 331, 340, 349, 352 or current)

sudo apt-get install xserver-xorg-video-nouveau
sudo apt-get install linux-headers-generic
sudo apt-get clean  apt-get autoclean  apt-get autoremove
sudo apt-get apt-get upgrade  update  apt-get install –f
sudo update-alternatives --config x86_64-linux-gnu_gl_conf
sudo ldconfig -n
sudo update-initramfs -u
sudo shutdown –r now

Let the devs get on and do perm fix in the meantime.

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in

[Desktop-packages] [Bug 1460442] Re: Ubuntu Mate 15.04 does not allow to set a password for login after resume from Suspend

2015-06-19 Thread Marc Deslauriers

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is available, members of the security team will review it and
publish the package. See the following link for more information:
https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures

** Package changed: compiz (Ubuntu) = mate-screensaver (Ubuntu)

** Changed in: mate-screensaver (Ubuntu)
   Status: New = Incomplete

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

Title:
  Ubuntu Mate 15.04 does not allow to set a password for login after
  resume from Suspend

Status in mate-screensaver package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a DELL XPS13, which came factory pre-installed with
  Ubuntu 14.04, but due to various bugs I have upgraded to Ubuntu Mate
  15.04.

  The laptop can go into suspend, and does resume from it. However, it
  always resumes without asking for a password, and the Power
  Management Preferences do not offer to set a password, neither for AC
  nor for battery.

  This problem exists for both Window Manager, Compiz and Marco. (though
  the extra problem with Marco is, that is does not even resume properly
  from suspend, reported here
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454651

  It seems to be an unnecessary use risk  to use a laptop which can be
  run by anyone by just opening (when suspended, but this is the typical
  use scenario)

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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Umut Yazgan

Thanks!
On Jun 19, 2015 15:31, Zewbie 1431...@bugs.launchpad.net wrote:

 Scroll  to the very bottom  and follow  the link

 Sent from my Sprint Samsung Galaxy S® 6. Original message 
 From: Umut Yazgan umut@gmail.com
 Date: 06/19/2015  6:06 AM  (GMT-07:00)
 To: zew...@yahoo.com
 Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
   violation

 Hello how can I unsubscribe this?
 On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com
 wrote:

  I am already working on it (I've been busy with other work). There's no
  need to make this any more complicated than it needs to be.

  --
  You received this bug notification because you are subscribed to a
  duplicate bug report (1395993).
  https://bugs.launchpad.net/bugs/1431753

  Title:
Nvidia binary driver FTBS due to DKMS layer violation

  Status in nvidia-graphics-drivers-331 package in Ubuntu:
Confirmed
  Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
  Status in nvidia-graphics-drivers-340 package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-346 package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-331 source package in Trusty:
Triaged
  Status in nvidia-graphics-drivers-331-updates source package in Trusty:
Triaged
  Status in nvidia-graphics-drivers-340 source package in Trusty:
Confirmed
  Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Confirmed
  Status in nvidia-graphics-drivers-346 source package in Trusty:
Confirmed
  Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Confirmed

  Bug description:
Filing this against the 340-updates version but possibly the same
applies to older versions, too. The nvidia source package produces two
individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
The problem is that the DKMS build of the nvidia-uvm module runs
compile steps inside the nvidia modules build directory. This is
violating the DKMS assumption that each module can be build
independently (there is no way of describing cross-modules
dependencies and even more important, the autoinstall step after a new
kernel is installed will run the modules build in parallel).

Since nvidia and nvidia-uvm are very dependent on each other the right
course of action seems to be to combine both sources in one DKMS
module that produces two kernel modules (this is supported by DKMS).
For the transition this resulting dkms package needs to have a
breaks/replaces for the nvidia-uvm package.

  To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1382608).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Confirmed

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the

[Desktop-packages] [Bug 224288] Re: Playbar acting strange

2015-06-19 Thread Bug Watch Updater

** Changed in: rhythmbox
   Status: Confirmed = Fix Released

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

Title:
  Playbar acting strange

Status in The Rhythmbox Music Management Application:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  I know that Rhythmbox has always been this way and I'm not sure if
  there is a reason, but when you click on the playbar to a point
  further into the song it will increase the time in increments and keep
  going past the point of the click.  I would image the proper behavior
  of this should be for the song to jump directly to the that is clicked
  instead of this strange jumping behavior.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Apr 29 11:37:12 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.11.5-0ubuntu6
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux 2.6.24-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/224288/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Nima

I want to go to another linux distribution , 
Can any body give me a hint about it? 
CentOS or Opensuse? Which one is better?
which one has a full resource of software like ,for example ubuntu software 
center?
Thanks for any help in advance

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting

2015-06-19 Thread dino99

This is fixed into Wily

** Changed in: network-manager (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: hundredpapercuts
   Status: Confirmed = Fix Released

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

Title:
  Ordering processes: networkmanager should wait for kernel'module been
  activated first before starting

Status in One Hundred Papercuts:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Get that journalctl log showing networkmanager starting before the
  related kernel'module been ready:

  systemd[1]: Starting Network.
  systemd[1]: Starting /etc/rc.local Compatibility...
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (lo): link connected
  NetworkManager[724]: info (lo): carrier is ON
  NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' 
ifindex: 1)
  NetworkManager[724]: info (lo): exported as 
/org/freedesktop/NetworkManager/Devices/0
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth0): carrier is OFF
  NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' 
ifindex: 2)
  NetworkManager[724]: info (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
  NetworkManager[724]: info (eth0): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
  NetworkManager[724]: info (eth0): preparing device
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth1): carrier is OFF
  NetworkManager[724]: info (eth1): new Ethernet device (driver: 'sky2' 
ifindex: 3)
  NetworkManager[724]: info (eth1): exported as 
/org/freedesktop/NetworkManager/Devices/2
  NetworkManager[724]: info (eth1): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
  kernel: sky2 :04:00.0 eth0: enabling interface
  kernel: sky2 :03:00.0 eth1: enabling interface
  NetworkManager[724]: info (eth1): preparing device
  NetworkManager[724]: info urfkill disappeared from the bus

  that mobo have eth0  eth1 ports, but only eth1 is used. As the last
  lines logged, networworkmanager is able to be loaded when the module
  sky2 is enabled.

  network-manager 0.9.10.0-4ubuntu13

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:41:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1466821] [NEW] Opt-out Chrome Hotword Shared Module

Public bug reported:

This is the Ubuntu version of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909

With upstream fix to allow disabling of the enable_hotwording build flag at 
compile time:
https://code.google.com/p/chromium/issues/detail?id=491435

It would be nice if we could disable this at build time, in turn staying
in sync with Debian.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: chromium-browser 43.0.2357.81-0ubuntu0.15.04.1.1170
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
DRM.card0.HDMI.A.1:
 edid-base64: 
 dpms: On
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0.LVDS.1:
 edid-base64: 
AP///wAGrzwQAAAWAQSQHxF4AhC1l1hXkiYeUFQBAQEBAQEBAQEBAQEBAQEBEhtWRlAAIzAmFjYANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwWFRUMDEuMCAKADk=
 dpms: On
 modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
 enabled: enabled
 status: connected
Date: Fri Jun 19 05:56:31 2015
Desktop-Session:
 'gnome-flashback-metacity'
 '/etc/xdg/xdg-gnome-flashback-metacity:/usr/share/upstart/xdg:/etc/xdg'
 '/usr/share/gnome-flashback-metacity:/usr/local/share/:/usr/share/'
Env:
 'None'
 'None'
InstallationDate: Installed on 2014-06-21 (362 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
Load-Avg-1min: 1.14
Load-Processes-Running-Percent:   0.6%
MachineType: LENOVO 20319
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed 
root=UUID=a2db89ed-d599-4138-8838-0b950b6c3fbb ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to vivid on 2015-03-13 (98 days ago)
dmi.bios.date: 10/14/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 8CCN34WW(V3.04)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo IdeaPad S415 Touch
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S415 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr8CCN34WW(V3.04):bd10/14/2014:svnLENOVO:pn20319:pvrLenovoIdeaPadS415Touch:rvnLENOVO:rnLenovoIdeaPadS415Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoIdeaPadS415Touch:
dmi.product.name: 20319
dmi.product.version: Lenovo IdeaPad S415 Touch
dmi.sys.vendor: LENOVO
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2015-01-26T21:00:35.859194

** Affects: chromium-browser (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: amd64 apport-bug trusty vivid wily

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

Title:
  Opt-out Chrome Hotword Shared Module

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  This is the Ubuntu version of:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909

  With upstream fix to allow disabling of the enable_hotwording build flag at 
compile time:
  https://code.google.com/p/chromium/issues/detail?id=491435

  It would be nice if we could disable this at build time, in turn
  staying in sync with Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 43.0.2357.81-0ubuntu0.15.04.1.1170
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.LVDS.1:
   edid-base64: 
AP///wAGrzwQAAAWAQSQHxF4AhC1l1hXkiYeUFQBAQEBAQEBAQEBAQEBAQEBEhtWRlAAIzAmFjYANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwWFRUMDEuMCAKADk=
   dpms: On
   modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
   enabled: enabled
   status: connected
  Date: Fri Jun 19 05:56:31 2015
  Desktop-Session:
   'gnome-flashback-metacity'
   '/etc/xdg/xdg-gnome-flashback-metacity:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome-flashback-metacity:/usr/local/share/:/usr/share/'

[Desktop-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

** Changed in: xorg (Ubuntu)
   Status: Incomplete = New

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

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Zewbie

Try fedora 21 not 22

Sent from my Sprint Samsung Galaxy S® 6. Original message 
From: Nima nima@gmail.com 
Date: 06/19/2015  3:43 AM  (GMT-07:00) 
To: zew...@yahoo.com 
Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
  violation 

I want to go to another linux distribution , 
Can any body give me a hint about it? 
CentOS or Opensuse? Which one is better?
which one has a full resource of software like ,for example ubuntu software 
center?
Thanks for any help in advance

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1431753] Vacation reply

2015-06-19 Thread Dustin Barrett

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Camil Staps

Zewbie, what is wrong with you? Did you not read #29 and #35? Do you
have any idea how many people are getting an email when you comment on
this bug? Have a little responsibility.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Kristian Erik Hermansen

OSX is the way to go for sure...sorry for the annoying email alert

On Fri, Jun 19, 2015 at 4:32 AM Camil Staps i...@camilstaps.nl wrote:

 Zewbie, what is wrong with you? Did you not read #29 and #35? Do you
 have any idea how many people are getting an email when you comment on
 this bug? Have a little responsibility.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1405694).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions


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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze

2015-06-19 Thread mika

no more black screen, thank you so much #40

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

Title:
  ubuntu 14.04 after install nvidia binary driver  331.89  black screen
  and freeze

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver
  331.89 from Additional Drivers application then reboot, it shows black
  screen, no login window, I even can't use ctrl+alt+F2 to switch to
  text mode, then I reboot and go to recovery mode, use 'prime-select
  intel' to switch to intel GPU and reboot, everything is fine, but as
  soon as I switch to nvidia GPU, still same issue.

  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+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 1411158] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

2015-06-19 Thread Roberto

** This bug is no longer a duplicate of bug 1431753
   Nvidia binary driver FTBS due to DKMS layer violation

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

Title:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Thu Jan 15 10:06:36 2015
  InstallationDate: Installed on 2015-01-08 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1411158/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Simon Reed

To be fair it is an annoying issue but not one that is so fatal one
would not be able to recover a system.

It leaves the system not working.  That's is more than just annoying.
Also, I actually did re-install the operating system at least once
because of this bug to try to get this PC working again.  I actually
spent about three days struggling with driver versions and trying to
work out what the real problem was.  I was also swopping out video cards
to see if that helped.  Any sane person would have gone out and bought a
Windows licence and installed that instead.

By now I just made it a habit of doing the following…

Sadly, those instructions are the sort of reason people say Linux is not
ready for the mainstream.  How do I tell Auntie Margaret over the phone
she just needs to sudo dkms install -m module -v module version -k
kernel version ?

It might be trivial to an operating systems programmer with a computer
science degree.  But some of us want to USE Ubuntu-based operating
systems for work purposes, not for working on.

I am sorry to add a whinge to this saga, but to imply it's just a
nuisance and there's an easy workaround is not how it feels to some of
the user community.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1284377] Re: Cross-references are broken, when copied to other document or part of the document

Jaime Peña Álvarez, you would be experiencing either a regression since the 
fix, or a different problem. Either way, please file a new report via a 
terminal:
ubuntu-bug libreoffice

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

Title:
  Cross-references are broken, when copied to other document or part of
  the document

Status in LibreOffice Productivity Suite:
  Fix Released
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Michael Stahl committed a patch related to this bug that has been
  pushed to libreoffice-4-1-5. Please, see for more details:

  https://bugs.freedesktop.org/show_bug.cgi?id=63553

  The bug has been reported to be solved in libreoffice-writer 4.1.5.2
  on 2014-02-02.

  I am using libreoffice-writer 1:4.2.1-0ubuntu1~saucy1 on Ubuntu 13.10
  64 bit from http://ppa.launchpad.net/libreoffice/ppa/ubuntu.

  The bug is still present.

  Thank you very much. If there is anything I can do to help, or if it
  is not the proper way to report this kind of issue, please tell.

  Jean-Sebastien

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1284377/+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 1438128] Re: gedit crashed with SIGSEGV in gtk_action_group_get_action()

2015-06-19 Thread Sebastien Bacher

it's the most reported e.u.c gedit issue,
https://errors.ubuntu.com/problem/c9479f6740d9d0cbcbab79c7a1a76a594d8d79a3

** Information type changed from Private to Public

** Changed in: gedit (Ubuntu)
   Importance: Medium = High

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

Title:
  gedit crashed with SIGSEGV in gtk_action_group_get_action()

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  just opened two tabs with text in gedit

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gedit 3.10.4-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 13:36:37 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2015-03-27 (2 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  ProcCmdline: gedit /home/username/Desktop/gpuintel
  SegvAnalysis:
   Segfault happened at: 0x7f8764f5796c gtk_action_group_get_action+28:   
cmp%rax,0x0(%rbp)
   PC (0x7f8764f5796c) ok
   source %rax ok
   destination 0x0(%rbp) (0x4) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   gtk_action_group_get_action () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gedit crashed with SIGSEGV in gtk_action_group_get_action()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1438128/+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 1466761] [NEW] /usr/share/apport/apport-gtk:AssertionError:lambda:collect_info:return_value

2015-06-19 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding apport.  This problem was most recently seen with version
2.17.3-0ubuntu4, the problem page at
https://errors.ubuntu.com/problem/b2fb55a76b202a208b4ea89c5e92e89ae88437de
contains more details.

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


** Tags: kylin-15.04 vivid wily

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

Title:
  /usr/share/apport/apport-
  gtk:AssertionError:lambda:collect_info:return_value

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.17.3-0ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/b2fb55a76b202a208b4ea89c5e92e89ae88437de
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1466761/+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 1464669] Re: New upstream microreleases 9.1.18, 9.3.9, 9.4.4

2015-06-19 Thread Martin Pitt

autopkgtests succeeded, and the failing reverse dependencies (asn1oid,
orafce) are known bugs in the older tests suites.

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

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

Title:
  New upstream microreleases 9.1.18, 9.3.9, 9.4.4

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Utopic:
  Fix Committed
Status in postgresql-9.4 source package in Vivid:
  Fix Committed
Status in postgresql-9.4 source package in Wily:
  Fix Released

Bug description:
  As a further followup to the previous round of updates in bug 1461425
  upstream pushed out new microreleases today:
  http://www.postgresql.org/about/news/1592/

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

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread josh

Nima this really isn't the place for that talk. Will EVERYONE please keep
this thread on topic about this bug and only this bug please
On 19 Jun 2015 21:51, Nima nima@gmail.com wrote:

 I want to go to another linux distribution ,
 Can any body give me a hint about it?
 CentOS or Opensuse? Which one is better?
 which one has a full resource of software like ,for example ubuntu
 software center?
 Thanks for any help in advance

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1412043).
 https://bugs.launchpad.net/bugs/1431753

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Confirmed
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Confirmed

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions


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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--

[Desktop-packages] [Bug 1445134] Re: Network manager never scanning for new access points

2015-06-19 Thread Iain Lane

I think I saw this bug on my laptop the other day. I did something like
this.

1. Turn it on, log in
2. Look at the wireless list
3. Ah, there's no wifi here, I'll tether. Turn on the AP on my phone.
4. Wait for it to appear in NM so I can connect to it (or it auto connects if 
I've seen it before)

I waited about 5 minutes and the AP was never seen. Ended up restarting
NM (sudo systemctl restart network-manager) and the AP was then seen and
associated with. I didn't test comment #3's solution.

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

Title:
  Network manager never scanning for new access points

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  While trying to reproduce another bug related with the last seen value
  from the access points, I noticed that network manager is never really
  scanning for new access points on my desktop, not even when not
  connected.

  $ sudo nmcli g logging level debug domains wifi_scan

  Then powered an access point, but was never really able to see it.
  From syslog, noticed that there is never really a scan, which explains
  why the ap never goes away and why it is not able to find it in the
  first place.

  If I force a scan via cmdline it works as expected (and I noticed a
  scan also happens when changing connections).

  Was also able to reproduce this issue on mako, with the following image:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 173
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-16 14:58:58
  version version: 173
  version ubuntu: 20150416
  version device: 20150210
  version custom: 20150416

  In the mako case, I booted with a known connection in place, it
  connected successfully but it never really scans for other access
  points. Scan works fine after disconnecting though.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu14
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 16 14:21:42 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-29 (534 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-11-04T02:19:36.923463
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+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 1466670] Re: WebGL Not Working

2015-06-19 Thread Heath

That is indeed a concerning amount. Have you seen that number drop
dramatically since this release rolled out? I never had detrimental
crashing issues using WebGL. I am unfamiliar with the Chromium build
process but is there a way to disable the feature on update but allow
the end user to override that option? I am a developer and one of our
products is WebGL driven, I am making due by using Google Chrome for now
but it would be nice to have it back in Chromium at some point. Thanks
for the work.

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

Title:
  WebGL Not Working

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
  like Gecko) Ubuntu Chromium/43.0.2357.81 Chrome/43.0.2357.81
  Safari/537.36

  Steps to reproduce the problem:
  1. Visit https://get.webgl.org/
  2. Shows WebGL Disabled
  3. Look in `chrome://flags/`
  4. Look for `Disable WebGL`, this is showing WebGL as enabled

  What is the expected behavior?
  WebGL works

  What went wrong?
  Can't use sites that use WebGL

  Did this work before? Yes on 6/10/2015 was the last day it worked

  Chrome version: 43.0.2357.81  Channel: stable
  OS Version: Ubuntu 14.04
  Flash Version: Shockwave Flash 16.0 r0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1466670/+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 1466918] [NEW] menu's not visible

2015-06-19 Thread Xtien

Public bug reported:

After using Android Studio for an hour or so, the menu's don't work any
more, have to restart AS. Same is true for Eclipse, and, to a lesser
extent, Thunderbird. I have the menus in the window title bar.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: evince 3.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jun 19 17:48:30 2015
InstallationDate: Installed on 2014-04-21 (424 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: evince
UpgradeStatus: Upgraded to vivid on 2015-05-05 (45 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  menu's not visible

Status in evince package in Ubuntu:
  New

Bug description:
  After using Android Studio for an hour or so, the menu's don't work
  any more, have to restart AS. Same is true for Eclipse, and, to a
  lesser extent, Thunderbird. I have the menus in the window title bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 19 17:48:30 2015
  InstallationDate: Installed on 2014-04-21 (424 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: evince
  UpgradeStatus: Upgraded to vivid on 2015-05-05 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1466918/+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 1466934] [NEW] Trying to maximize battery life on HP dv7-4272us

2015-06-19 Thread foobar

Public bug reported:

This AMD 3-core + Radeon runs really hot, and I'm trying to maximize
battery life.

When I try radeon.dpm=1, I get display glitching every few seconds when
the dpm switches displays.  I haven't found any way to force dpm to keep
the discrete display completely turned off, both to save power and to
stop the glitching.

Among other problems, the mere existence of HDMI audio keeps waking up
the discrete GPU, both wasting power  glitching the display.  So I
tried radeon.audio=0.  I don't think it helps, but I left it in.

The only way to really kill the HDMI audio problems is to blacklist
snd_hda_intel, but that kills _all_ of my audio (except Bluetooth
audio).  So I had to un-blacklist snd_hda_intel.

So I'm using radeon.dpm=0.

If radeon.runpm=1, I still get problems.

So I'm using radeon.runpm=0.

This works pretty well; I've gotten the temperature down to 68 degrees
or so, but this is still too hot.

If I turn off the discrete graphics completely using

echo OFF  /sys/kernel/debug/vgaswitcheroo/switch

this works quite well -- I can get the temperature down to 64 degrees or
so -- but now my log fills up with complaints that my radeon discrete
driver isn't turned on.  (I'll send you another report showing you
this.)

I want to be able to operate this HP laptop in the most power-saving way
-- by completely turning off the discrete radeon GPU.

Could you provide any suggestions about how to do this?

Thanks very much.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.1
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: Fri Jun 19 09:31:02 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1641]
 Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] 
[1002:68e4] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Radeon HD 6370M [103c:1641]
InstallationDate: Installed on 2015-06-06 (13 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=0a49d103-e2eb-4b21-a433-c41a1ef8d27b ro quiet splash radeon.runpm=0 
radeon.dpm=0 radeon.audio=0 radeon.pcie_gen2=0 acpiphp.disable=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1641
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 67.33
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058312242B2620100:rvnHewlett-Packard:rn1641:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 058312242B2620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Jun 19 09:08:20 2015
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid

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

Title:
  Trying to

[Desktop-packages] [Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back

2015-06-19 Thread Brian Murray

Hello Doug, or anyone else affected,

Accepted nautilus into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.10.1-0ubuntu9.9 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nautilus (Ubuntu Trusty)
   Status: New = Fix Committed

** Tags added: verification-needed

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

Title:
  Open with on folders was removed, Ubuntu should consider patching back

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Committed
Status in nautilus source package in Trusty:
  Fix Committed

Bug description:
  * Impact:
  the open with action is missing on directories

  * Test case:
  right click on a directory and see if open with is listed

  * Regression potentiel:
  check that the open with items work as they should

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1026254/+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 1466936] [NEW] fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]

2015-06-19 Thread Elliott Saille

Public bug reported:

fglrx-core kernel module fails to build on Ubuntu 15.04 kernel
3.19.0-15,3.19.0-18, 3.19.0-20, 3.19.0-21. All with the same error.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.101-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.1
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
DKMSKernelVersion: 3.19.0-21-generic
Date: Fri Jun 19 11:46:23 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.101: added
DuplicateSignature: 
dkms:fglrx-core:2:15.101-0ubuntu1:/var/lib/dkms/fglrx-core/15.101/build/2.6.x/firegl_public.c:4819:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cayman XT [Radeon HD 6970] [1002:6718] 
(prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Device [1787:2010]
InstallationDate: Installed on 2015-05-23 (26 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: MSI MS-7924
PackageVersion: 2:15.101-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: fglrx-installer
Title: fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-G43(MS-7924)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd07/22/2014:svnMSI:pnMS-7924:pvr1.0:rvnMSI:rnH97M-G43(MS-7924):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7924
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Jun 19 11:36:38 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: radeon

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 ubuntu vivid

** Attachment added: DKMS Build log for kernel 3.19.0-15
   https://bugs.launchpad.net/bugs/1466936/+attachment/4417196/+files/make.log

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

Title:
  fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build
  [error: implicit declaration of function ‘__get_cpu_var’]

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  fglrx-core kernel module fails to build on Ubuntu 15.04 kernel
  3.19.0-15,3.19.0-18, 3.19.0-20, 3.19.0-21. All with the same error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.101-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  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
  DKMSKernelVersion: 3.19.0-21-generic
  Date: Fri Jun 19 11:46:23 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.101: added
  DuplicateSignature: 
dkms:fglrx-core:2:15.101-0ubuntu1:/var/lib/dkms/fglrx-core/15.101/build/2.6.x/firegl_public.c:4819:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]

[Desktop-packages] [Bug 1466936] Re: fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]

2015-06-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build
  [error: implicit declaration of function ‘__get_cpu_var’]

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  fglrx-core kernel module fails to build on Ubuntu 15.04 kernel
  3.19.0-15,3.19.0-18, 3.19.0-20, 3.19.0-21. All with the same error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.101-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  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
  DKMSKernelVersion: 3.19.0-21-generic
  Date: Fri Jun 19 11:46:23 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.101: added
  DuplicateSignature: 
dkms:fglrx-core:2:15.101-0ubuntu1:/var/lib/dkms/fglrx-core/15.101/build/2.6.x/firegl_public.c:4819:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cayman XT [Radeon HD 6970] 
[1002:6718] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2010]
  InstallationDate: Installed on 2015-05-23 (26 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: MSI MS-7924
  PackageVersion: 2:15.101-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-G43(MS-7924)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd07/22/2014:svnMSI:pnMS-7924:pvr1.0:rvnMSI:rnH97M-G43(MS-7924):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7924
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Jun 19 11:36:38 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1466936/+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 1466950] [NEW] drm complains bitterly when discrete graphics turned off

2015-06-19 Thread foobar

Public bug reported:

I'm using radeon.dpm=0 and radeon.runpm=0 for reasons explained in a
previous bug report.

I'm able to turn the radeon discrete graphics off using

echo IGD  /sys/kernel/debug/vgaswitcheroo/switch
echo OFF  /sys/kernel/debug/vgaswitcheroo/switch

and my power consumption drops dramatically to a nice low level,
but then the kernel log starts filling up with all sorts of complaints from drm:

Jun 19 10:19:43 HP-ubuntu kernel: [  360.548772] radeon: switched off
Jun 19 10:19:44 HP-ubuntu kernel: [  361.083818] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:44 HP-ubuntu kernel: [  361.083872] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:44 HP-ubuntu kernel: [  361.098291] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:44 HP-ubuntu kernel: [  361.098365] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:44 HP-ubuntu kernel: [  361.800076] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:44 HP-ubuntu kernel: [  361.800117] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:44 HP-ubuntu kernel: [  361.874996] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:44 HP-ubuntu kernel: [  361.875074] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:44 HP-ubuntu kernel: [  361.892348] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:44 HP-ubuntu kernel: [  361.892425] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:45 HP-ubuntu kernel: [  362.083837] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:45 HP-ubuntu kernel: [  362.083909] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:45 HP-ubuntu kernel: [  362.098414] radeon :02:00.0: couldn't 
schedule ib
Jun 19 10:19:45 HP-ubuntu kernel: [  362.098485] [drm:radeon_cs_ioctl [radeon]] 
*ERROR* Failed to schedule IB !
Jun 19 10:19:45 HP-ubuntu kernel: [  362.143361] radeon :02:00.0: couldn't 
schedule ib

etc., at a great rate!

The whole point of the exercise is to keep the discrete graphics off, so
why is drm:radeon_cs_ioctl still trying to issue commands to it?

Also, Ubuntu doesn't want to shut down cleanly after the radeon discrete
graphics unit is turned off.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.1
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: Fri Jun 19 10:20:25 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1641]
 Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] 
[1002:68e4] (rev ff) (prog-if ff)
InstallationDate: Installed on 2015-06-06 (13 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=0a49d103-e2eb-4b21-a433-c41a1ef8d27b ro quiet splash radeon.runpm=0 
radeon.dpm=0 radeon.audio=0 radeon.pcie_gen2=0 acpiphp.disable=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1641
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 67.33
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058312242B2620100:rvnHewlett-Packard:rn1641:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 058312242B2620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati

[Desktop-packages] [Bug 998489] Re: Fn+F11 does not control Ambient Light Sensor on HP 8560W

2015-06-19 Thread Ivo Maag

The same on Ubuntu 14.04 with the Elitebook 8440p. Setting
/sys/devices/platform/hp-wmi/als to 1 worked for me too.

Thank you a lot, no sunshine in my face experience anymore after boot.
Only the function key still doesn't work.

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

Title:
  Fn+F11 does not control Ambient Light Sensor on HP 8560W

Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04 LTS with Gnome Classic tries to disable touchpad (at
  least it displays that image in top right corner). But actually seems
  nothing happens at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/998489/+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 1466821] Re: Opt-out Chrome Hotword Shared Module

2015-06-19 Thread Chad Miller

Is this really a problem? I don't think Debian does, and I know Ubuntu
doesn't ship with NaCl support, so downloading any nacl module should do
nothing other than occupy a tiny fraction of disk space.

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) = Chad Miller (cmiller)

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

Title:
  Opt-out Chrome Hotword Shared Module

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  This is the Ubuntu version of:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909

  With upstream fix to allow disabling of the enable_hotwording build flag at 
compile time:
  https://code.google.com/p/chromium/issues/detail?id=491435

  It would be nice if we could disable this at build time, in turn
  staying in sync with Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 43.0.2357.81-0ubuntu0.15.04.1.1170
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.LVDS.1:
   edid-base64: 
AP///wAGrzwQAAAWAQSQHxF4AhC1l1hXkiYeUFQBAQEBAQEBAQEBAQEBAQEBEhtWRlAAIzAmFjYANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwWFRUMDEuMCAKADk=
   dpms: On
   modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
   enabled: enabled
   status: connected
  Date: Fri Jun 19 05:56:31 2015
  Desktop-Session:
   'gnome-flashback-metacity'
   '/etc/xdg/xdg-gnome-flashback-metacity:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome-flashback-metacity:/usr/local/share/:/usr/share/'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-06-21 (362 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Load-Avg-1min: 1.14
  Load-Processes-Running-Percent:   0.6%
  MachineType: LENOVO 20319
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed 
root=UUID=a2db89ed-d599-4138-8838-0b950b6c3fbb ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to vivid on 2015-03-13 (98 days ago)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S415 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S415 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CCN34WW(V3.04):bd10/14/2014:svnLENOVO:pn20319:pvrLenovoIdeaPadS415Touch:rvnLENOVO:rnLenovoIdeaPadS415Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoIdeaPadS415Touch:
  dmi.product.name: 20319
  dmi.product.version: Lenovo IdeaPad S415 Touch
  dmi.sys.vendor: LENOVO
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-26T21:00:35.859194

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1466821/+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 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back

2015-06-19 Thread Mathew Hodson

** Tags removed: nosense

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

Title:
  Open with on folders was removed, Ubuntu should consider patching back

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Committed
Status in nautilus source package in Trusty:
  Fix Committed

Bug description:
  * Impact:
  the open with action is missing on directories

  * Test case:
  right click on a directory and see if open with is listed

  * Regression potentiel:
  check that the open with items work as they should

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1026254/+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 1295670] Re: Nautilus doesn't save items view

2015-06-19 Thread Bug Watch Updater

** Changed in: nautilus
   Status: New = Confirmed

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

Title:
  Nautilus doesn't save items view

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Nautilus Files doesn't save items view style (List or Icons view)
  after closing window and opening it again. Previous Nautilus release
  does it.

  The following screencast shows the bug “in action”:
  http://www.youtube.com/watch?v=EdrsO5Kwtlgfeature=youtu.be

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 17:06:24 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-03-18 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1295670/+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 1436073] Re: Graphical Rendering Issues with Unity - Text Missing, Boxes Disappearing

2015-06-19 Thread Cindy Quach

Apologies for the delay in response, doesn't seem that apport-collect is
working for me:

$ apport-collect -p xorg 1436073
Traceback (most recent call last):
  File /usr/share/apport/apport-gtk, line 594, in module
app.run_argv()
  File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv
return self.run_update_report()
  File /usr/lib/python2.7/dist-packages/apport/ui.py, line 572, in 
run_update_report
attachment_comment='apport information')
  File /usr/lib/python2.7/dist-packages/apport/crashdb_impl/memory.py, line 
113, in update
r = self.reports[id]
IndexError: list index out of range

Are there any specific files I can send you? I'll also dig back into
this to see if I can pinpoint certain errors.

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

Title:
  Graphical Rendering Issues with Unity - Text Missing, Boxes
  Disappearing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Currently running the latest utopic kernel 3.16 and installed the
  Trusty Enablement Stack with sudo apt-get install --install-recommends
  linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-glx-lts-
  utopic libegl1-mesa-drivers-lts-utopic

  It's having some pretty bad graphical rendering issues, like text is
  missing and my dialogue boxes are disappearing. (Screenshot attached).
  I tested this on a Lenovo X1 Gen 3 and a Lenovo X250, both of which
  can reproduce this issue. I also have a Dell M3800 which is not seeing
  this issue.

  xorg:
  [18.323]
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  [18.323] X Protocol Version 11, Revision 0
  [18.323] Build Operating System: Linux 3.2.0-70-generic x86_64 Ubuntu
  [18.323] Current Operating System: Linux cindyq-glaptop 3.16.0-33-generic 
#44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64
  [18.323] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic 
root=/dev/mapper/sysvg-root ro elevator=deadline quiet splash vt.handoff=7
  [18.323] Build Date: 12 February 2015  11:11:26PM
  [18.323] xorg-server 2:1.16.0-1ubuntu1.2~trusty2 (For technical support 
please see http://www.ubuntu.com/support)
  [18.323] Current version of pixman: 0.30.2
  [18.323]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [18.323] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [18.324] (==) Log file: /var/log/Xorg.0.log, Time: Tue Mar 24 13:55:15 
2015
  [18.333] (==) Using system config directory /usr/share/X11/xorg.conf.d
  [18.335] (==) No Layout section.  Using the first Screen section.
  [18.335] (==) No screen section available. Using defaults.
  [18.335] (**) |--Screen Default Screen Section (0)
  [18.335] (**) |   |--Monitor default monitor
  [18.335] (==) No monitor specified for screen Default Screen Section.
   Using a default monitor configuration.
  [18.335] (==) Automatically adding devices
  [18.335] (==) Automatically enabling devices
  [18.335] (==) Automatically adding GPU devices
  [18.339] (WW) The directory /usr/share/fonts/X11/cyrillic does not 
exist.
  [18.339]  Entry deleted from font path.
  [18.339] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist.
  [18.339]  Entry deleted from font path.
  [18.339] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist.
  [18.339]  Entry deleted from font path.
  [18.339] (WW) The directory /usr/share/fonts/X11/100dpi does not exist.
  [18.339]  Entry deleted from font path.
  [18.339] (WW) The directory /usr/share/fonts/X11/75dpi does not exist.
  [18.339]  Entry deleted from font path.
  [18.339] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/Type1,
   built-ins
  [18.339] (==) ModulePath set to 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules
  [18.339] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [18.339] (II) Loader magic: 0x7fe7d1657c80
  [18.339] (II) Module ABI versions:
  [18.339]  X.Org ANSI C Emulation: 0.4
  [18.339]  X.Org Video Driver: 18.0
  [18.339]  X.Org XInput driver : 21.0
  [18.339]  X.Org Server Extension : 8.0
  [18.340] (II) xfree86: Adding drm device (/dev/dri/card0)
  [18.344] (--) PCI:*(0:0:2:0) 8086:1616:17aa:2226 rev 9, Mem @ 
0xf000/16777216, 0xe000/268435456, I/O @ 0x3000/64
  [18.344] (II) LoadModule: glx
  [18.349] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [18.396] (II) Module glx: vendor=X.Org Foundation
  [

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-06-19 Thread Pablo

Nima,

I moved to SteamOS. I am afraid you have to format your OS drive though.
For me is important my NVidia works correctly for games and work
projects. I know they will take care of that part.

In general I like Debian or Debian variants. They have a huge number of
packages.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1466936] Re: fglrx-core 2:15.101-0ubuntu1: fglrx-core kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]