[Desktop-packages] [Bug 1639403] [NEW] xwindows freezes

2016-11-04 Thread Yuan Song
Public bug reported:

I have a java program that can freeze xwindows during initialization.
It takes very long time for the program to finish initialization.
During the initialization phase, my desktop does not respond.  Xorg uses
100% cpu.  Everything becomes ok after I kill my java program.  The
version of java I am using is oracle jdk 1.8.0_112 .

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.16 x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog: /dev/sda5: clean, 791821/14131200 files, 31394551/56509440 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Nov  4 23:30:55 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
 bbswitch, 0.8, 4.4.16, x86_64: installed
 megaraid_sas, 06.810.09.00-rc1, 4.4.16, x86_64: built
 nvidia-340, 340.96, 4.4.16, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e]
InstallationDate: Installed on 2016-05-11 (178 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.16 
root=UUID=1e3cfb77-cf43-4ab5-8797-b2c6be8c0805 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: H170M Pro4
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.:bvrP2.20:bd07/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH170MPro4: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.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Nov  2 04:30:23 2016
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  xwindows freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a java program that can freeze xwindows during initialization.
  It takes very long time for the program to finish initialization.
  During the initialization phase, my desktop does not respond.  Xorg
  uses 100% cpu.  Everything becomes ok after I kill my java program.
  The version of java I am using is oracle jdk 1.8.0_112 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.16 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 

[Desktop-packages] [Bug 1573936] Re: keyboard applet shown "as text" font size

2016-11-04 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  keyboard applet shown "as text" font size

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

Bug description:
  When you add to panel "Keyboard Layout" applet and switch in its Properties 
text instead of flag, font size settings does not apply - always the same huge 
size.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/mapper/sda5_crypt: clean, 396674/7806976 files, 
12449621/31209216 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2016-05-15 (113 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2776LFG
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=UUID=eb875bdd-519e-43c6-b08a-cf4ae0fbfc41 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6EET55WW (3.15 )
  dmi.board.name: 2776LFG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6EET55WW(3.15):bd12/19/2011:svnLENOVO:pn2776LFG:pvrThinkPadX301:rvnLENOVO:rn2776LFG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2776LFG
  dmi.product.version: ThinkPad X301
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

2016-11-04 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  login screen without background

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

Bug description:
  Login screen (even after screen saver with lock) has not background selected, 
just colour. 
  When you switch in dropdown menu to Guest (without login) and back to your 
account, background appears.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/mapper/sda5_crypt: clean, 396674/7806976 files, 
12449621/31209216 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2016-05-15 (113 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2776LFG
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=UUID=eb875bdd-519e-43c6-b08a-cf4ae0fbfc41 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6EET55WW (3.15 )
  dmi.board.name: 2776LFG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6EET55WW(3.15):bd12/19/2011:svnLENOVO:pn2776LFG:pvrThinkPadX301:rvnLENOVO:rn2776LFG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2776LFG
  dmi.product.version: ThinkPad X301
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573938/+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 1617727] Re: round synaptics scroll-wheel pad not working

2016-11-04 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-input-synaptics (Ubuntu) because there has
been no activity for 60 days.]

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  round synaptics scroll-wheel pad not working

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

Bug description:
  Fujitsu S series Lifebooks (S792, S771, SH572, S761, S762, etc.) have
  next to the normal rectangle touchpad a round 'scroll-pad'

  In Ubuntu this wonderful pad is not working at all.

  I had a look into the Synaptics config file, and there it appears to be 
enabled, but it does not work at all.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-07-14 (53 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1617727/+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 1612406] Re: numlock turn off alone

2016-11-04 Thread Launchpad Bug Tracker
[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/1612406

Title:
  numlock turn off alone

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hello;
  Im using Ubuntu 16.04.1 - 64bits, but this bug follow me from Ubuntu 14.04

  No aparecente reason, the numeric keypad buttons are off. To work
  again, i have to press the 'numlock' twice, turn off and on again.
  This occurs many times during use of the machine.

  No matter what application or task I'm doing, it happens repeatedly.

  
  Hardware details:

  Caminho do hardware  Dispositivo  Classe Descrição
  
system 670Z5E (SAMSUNG SENS Series)
  /0busNP670Z5E-XD1BR
  /0/0  memory 64KiB BIOS
  /0/34 memory 512KiB L2 cache
  /0/35 memory 128KiB L1 cache
  /0/36 memory 3MiB L3 cache
  /0/37 memory 8GiB Memória do sistema
  /0/37/0   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/37/1   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/37/2   memory 8GiB SODIMM DDR3 Síncrono 
1600 MHz (0,6 ns)
  /0/37/3   memory DIMMProject-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 
2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: 
Neliton Pereira Jr. Language-Team: Brazilian Portuguese 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 
17:08+X-Generator: Launchpad (build 18115) [vazio]
  /0/38 processor  Intel(R) Core(TM) i5-3230M 
CPU @ 2.60GHz
  /0/100bridge 3rd Gen Core processor DRAM 
Controller
  /0/100/1  bridge Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port
  /0/100/1/0genericIllegal Vendor ID
  /0/100/2  display3rd Gen Core processor 
Graphics Controller
  /0/100/14 bus7 Series/C210 Series Chipset 
Family USB xHCI Host Controller
  /0/100/14/0  usb4 busxHCI Host Controller
  /0/100/14/1  usb3 busxHCI Host Controller
  /0/100/14/1/3 genericUSB2.0-CRW
  /0/100/16 communication  7 Series/C210 Series Chipset 
Family MEI Controller #1
  /0/100/1a bus7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2
  /0/100/1a/1  usb1 busEHCI Host Controller
  /0/100/1a/1/1 busIntegrated Rate Matching Hub
  /0/100/1a/1/1/2   input  2.4G Keyboard Mouse
  /0/100/1a/1/1/4   multimedia WebCam SC-10HDP12631N
  /0/100/1b multimedia 7 Series/C210 Series Chipset 
Family High Definition Audio Controller
  /0/100/1c bridge 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1
  /0/100/1c/0  wlp2s0   networkCentrino Advanced-N 6235
  /0/100/1c.3   bridge 7 Series/C210 Series Chipset 
Family PCI Express Root Port 4
  /0/100/1c.3/0enp3s0   networkRTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller
  /0/100/1d bus7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1
  /0/100/1d/1  usb2 busEHCI Host Controller
 

[Desktop-packages] [Bug 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Bill Turner, wb4alm
I have confirmed that changing the theme fixed the problem in both "gedit" and 
in "files".
I will use Greybird for the time being. Again, thank you.

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Bill Turner, wb4alm
Thank YOU, Jeremy for the assistance. Had you not said "different theme"
I would not have remembered to look in that direction to see exactly
what was being used.

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Alberto Salvia Novella
** Changed in: light-themes (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1623512] Re: Fix for Play/Pause key on some MCE remotes

2016-11-04 Thread Alberto Salvia Novella
** Changed in: lirc (Ubuntu)
   Importance: Undecided => Medium

** Package changed: lirc (Ubuntu) => kodi (Ubuntu)

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

Title:
  Fix for Play/Pause key on some MCE remotes

Status in kodi package in Ubuntu:
  Confirmed

Bug description:
  The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a
  section reading:

  #seen on HP Pavilion dv3t remote  --Tim Mann, 3 Nov 2009
  Media 0x7b7f
  PlayPause 0x7b91

  I have a Compro VideoMate K300 remote, and I can't find a key
  corresponding to Media, but it does have a Play/Pause key generating
  the same code as above (0x7b91).

  However, using it with Kodi, for example, it does nothing useful,
  because Kodi does not recognise the "PlayPause" code.

  I suggest that for Kodi, XMBC & similar programs it's probably more
  useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE,
  which is also mentioned in Kodi's Lircmap.xml, but that did not work
  in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the
  key works as expected: it plays or pauses the music.

  The change is to change "PlayPause" in the above line to "KEY_PLAY".

  Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE",
  and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted
  to do this by editing Kodi's Lircmap.xml, but failed.

  I looked at upstream lirc, but that has completely changed the
  organisation of remote config files since 0.9.0, so it seems most
  appropriate to make a fix in Ubuntu (and possibly Debian).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lirc 0.9.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 14 14:00:37 2016
  InstallationDate: Installed on 2014-11-26 (658 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: lirc
  UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843
  mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1623512/+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 1172789] Re: nm-applet leaks memory

2016-11-04 Thread Alberto Salvia Novella
** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  nm-applet leaks memory

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

Bug description:
  When using the notebook for a long time, nm-applet leaks more and more 
memory. This happens especially when I'm connected to a weak wifi network 
(actually it is more likely that the wifi driver is weak) and the connection 
aborts frequently, ie. most of the time it is trying to connect.
  It is noticeable that the "searching wifi" animation in the Unity panel 
causes a significant CPU load (of the compiz process) and fan noise. When I 
kill nm-applet, the CPU load is gone (while it is still searching wifi).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager-gnome 0.9.6.2-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic i686
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Thu Apr 25 18:35:25 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 131.246.227.254 dev eth0  proto static 
   131.246.227.0/24 dev eth0  proto kernel  scope link  src 131.246.227.146  
metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   FRITZ!Box 317092def618-4fd5-41ce-b140-3e1dcc0e83b3   
802-11-wireless   1366564107   So 21 Apr 2013 19:08:27 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/2
   eduroam   e177d7a7-d263-4523-8bfb-7d4c1e8df279   
802-11-wireless   1366896127   Do 25 Apr 2013 15:22:07 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   AE2   dbb06a9e-8d94-4b3b-872a-397bc50f6cde   
802-11-wireless   1352861678   Mi 14 Nov 2012 03:54:38 CETno
no /org/freedesktop/NetworkManager/Settings/0
   Kabelnetzwerkverbindung 1 04eb73f4-c356-441c-aa02-064765445b9d   
802-3-ethernet1366907766   Do 25 Apr 2013 18:36:06 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.6.0connected   enabled   enabled 
disabled   enabled enabled
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   iface eth0 inet dhcp
  InstallationDate: Installed on 2015-06-06 (507 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 600 
   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.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.33  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  Package: network-manager-applet (not installed)
  Tags:  xenial
  Uname: Linux 4.2.0-040200rc3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  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/ubuntu/+source/network-manager-applet/+bug/1172789/+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 1639000] Re: New upstream release 0.4.13

2016-11-04 Thread Jeremy Bicha
I started on this months ago and pushed my changes to Debian svn, but I
don't have a proxy to test with.

https://anonscm.debian.org/viewvc/pkg-gnome/packages/unstable/libproxy/

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

Title:
  New upstream release 0.4.13

Status in libproxy package in Ubuntu:
  New

Bug description:
  New in Version 0.4.13
  ==
  * Allow linking webkit pacrunner against javascriptcore-4.0
(webkit2).
  * Allow to disable building of the KDE module (-DWITH_KDE=ON/OFF).
  * Fix compilation errors with CLang on MacOSX.
  * bindings: perl: Add an option to explicitly link against libperl.so
Some distributions want to do it, other prefer not to, the library
is anyway in context of perl.
  * config_kde: Add a basic cache and invalidation: performance improvement
for the KDE module.

  New in version 0.4.12
  ==
  * Move development to github.com/libproxy/libproxy
  * Fix fd leak in get_pac (Bug #185)
  * Detect running MATE session (Bug #186, Part1).
  * Fix linking of perl bindings to pthread (Bug #182)
  * Correctly detect spidermonky (mozjs185) (Bug #188)
  * Stop pxgsettings from segfaulting on exit (Bug #192)
  * Fix test #10 (Bug #189)
  * Fix build on Mac OS X (Bug #183)
  * Add a generic KDE Config module (fix crashes of Qt5 based
  apps) (issue#4)

  We should get this in zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1639000/+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 1528285] Re: outdated version in the repos

2016-11-04 Thread Jeremy Bicha
Ubuntu 16.04 LTS has Mono 4.2.1

https://launchpad.net/ubuntu/+source/mono/4.2.1.102+dfsg2-7ubuntu4

Ubuntu 17.04 Alpha has Mono 4.6.1
https://launchpad.net/ubuntu/+source/mono/4.6.1.3+dfsg-4ubuntu1

** Changed in: mono (Ubuntu)
   Status: New => Fix Released

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

Title:
  outdated version in the repos

Status in mono package in Ubuntu:
  Fix Released

Bug description:
  version installed is very far behind the version that is at the
  following repo

  http://download.mono-project.com/repo/debian

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mono-runtime 3.2.8+dfsg-4ubuntu4
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 21 08:34:01 2015
  SourcePackage: mono
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1528285/+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 1637369] Re: Can no longer paste a file in nautilus without keyboard

2016-11-04 Thread Rocko
Filed upstream at https://bugzilla.gnome.org/show_bug.cgi?id=773959.

** Bug watch added: GNOME Bug Tracker #773959
   https://bugzilla.gnome.org/show_bug.cgi?id=773959

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

Title:
  Can no longer paste a file in nautilus without keyboard

Status in nautilus package in Ubuntu:
  New

Bug description:
  In file list mode, nautilus used to either have a paste option in the
  titlebar menu or via a menu that could be opened from a "cog" symbol
  at the right-hand top of its window (and for a while, via the right-
  click menu if you right-clicked on whitespace instead of a file name).

  But the only non-keyboard option I can find in nautilus
  1:3.20.3-1ubuntu3.1 now is the right-click menu, but this is not
  available when the nautilus window is full of filenames (as in the
  attached screenshot), so pasting is impossible without the keyboard in
  this case.

  What happened to the "cog" menu? IIRC correctly this was present until
  quite recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 28 10:42:19 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'885x494+65+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
  InstallationDate: Installed on 2016-08-12 (76 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160812)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1637369/+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 1637957] Re: Chromium not working with SAML authentication

2016-11-04 Thread Alberto Salvia Novella
** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: chromium-browser (Ubuntu)
   Importance: Medium => High

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Chromium not working with SAML authentication

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  In Chromium 53 (tested on Xenial and Yakkety) sync setup fails if the
  account login goes through SAML authentication (the setup fails after
  a successful SAML login).

  Apparently this is fixed in release 54, see
  https://bugs.chromium.org/p/chromium/issues/detail?id=655960 and
  https://bugs.chromium.org/p/chromium/issues/detail?id=571001 for
  details about the bug.

  Would it be possible to SRU the new version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Peter
I can log in but have other side effects:

0ad shows the map but no buildings, landscape features, soldiers, trees etc. 
its unplayable.
totem media player shows a black window with sound but no picture.

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1632195] Re: eog won't load or display large jpg images

2016-11-04 Thread Alberto Salvia Novella
** Changed in: eog (Ubuntu)
   Importance: Undecided => High

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

Title:
  eog won't load or display large jpg images

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  eog (image viewer) in Ubuntu 16.04 won't display large (~5.0 mb
  filesize or larger) jpg images.  It used to work fine with images from
  my Canon T3i DSLR now it just displays a blank screen.  eog still
  works with smaller sized images like those from an iphone

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: eog 3.18.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Oct 11 00:39:43 2016
  InstallationDate: Installed on 2016-06-10 (123 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1632195/+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 1633923] Re: Banshee completely freezes whenever I try to import a folder

2016-11-04 Thread Alberto Salvia Novella
** Changed in: banshee (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Banshee completely freezes whenever I try to import a folder

Status in banshee package in Ubuntu:
  Confirmed

Bug description:
  Whenever I try to import a foler in banshee it completely freezes and
  the only thing I can do is force it to quit, which means I'm unable to
  add any further music to my library :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: banshee 2.9.0+really2.6.2-7ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:42:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-24 (1149 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: Upgraded to xenial on 2016-07-08 (100 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1633923/+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 1636582] Re: nvidia-304 - module doesn't install to (or load from) kernal)

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-304 - module doesn't install to (or load from) kernal)

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

Bug description:
  I have used nvidia-304 successfully with Lubuntu up through 16.04.
  (With nouveau, at some time or other, the screen "crashes" and I have
  to hard-shutdown)

  This time, with 16.10, I first noticed only 3 screen resolutions
  possible - max being 1024x768. Further research showed:

  Monitor Settings:  
  "The following monitor is detected...
  Default Monitor"

  scott@scott-ASUS-M2N68-AM-PLUS:~$ sudo lshw -c video
  [sudo] password for scott: 
*-display UNCLAIMED   
 description: VGA compatible controller
 product: C61 [GeForce 7025 / nForce 630a]
 vendor: NVIDIA Corporation
 physical id: d
 bus info: pci@:00:0d.0
 version: a2
 width: 64 bits
 clock: 66MHz
 capabilities: pm msi vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:de00-deff memory:c000-cfff 
memory:dd00-ddff memory:c-d

  scott@scott-ASUS-M2N68-AM-PLUS:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
  default connected 1024x768+0+0 0mm x 0mm
 1024x768  61.00* 
 800x600   61.00  
 640x480   60.00  

  The install from Synaptic had appeared to go just fine:

  Gtk-WARNING **: Theme directory  imported-Humanity/192 of theme Lubuntu has 
no size field
  Selecting previously unselected package nvidia-304.
  (Reading database ... 171834 files and directories currently installed.)
  Preparing to unpack .../0-nvidia-304_304.132-0ubuntu1_amd64.deb ...
  Unpacking nvidia-304 (304.132-0ubuntu1) ...
  Selecting previously unselected package nvidia-current.
  Preparing to unpack .../1-nvidia-current_304.132-0ubuntu1_amd64.deb ...
  Unpacking nvidia-current (304.132-0ubuntu1) ...
  Processing triggers for libc-bin (2.24-3ubuntu1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up nvidia-304 (304.132-0ubuntu1) ...
  update-alternatives: using /usr/lib/nvidia-304/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto 
mode
  update-alternatives: using /usr/lib/nvidia-304/alt_ld.so.conf to provide 
/etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
  update-alternatives: using /usr/share/nvidia-304/glamor.conf to provide 
/usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-304
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Loading new nvidia-304-304.132 DKMS files...
  Building only for 4.8.0-26-generic
  Building for architecture x86_64
  Building initial module for 4.8.0-26-generic
  Done.

  nvidia_304:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.8.0-26-generic/updates/dkms/

  depmod...

  DKMS: install completed.
  Setting up nvidia-current (304.132-0ubuntu1) ...
  Processing triggers for libc-bin (2.24-3ubuntu1) ...
  Processing triggers for initramfs-tools (0.125ubuntu5) ...
  update-initramfs: Generating /boot/initrd.img-4.8.0-26-generic

  However, running lsmod showed no nvidia-304 module, nor did it show
  one for nouveau. So it had correctly removed nouveau, but did not add
  nvidia-304.

  Un-installing nvidia-304 gets me nouveau in lsmod, it finds the VGA
  monitor for xrandr and Monitor Settings, lshw just shows "*-display",
  and I can use up to 1600x1200 - but sooner or later I have to do a
  hard-shutdown because of the vidio-"crash".

  I just tried using "Additional Drivers" to switch to nvidia-304, but with 
exactly the same result. Before I removed the package, I looked through the 
system logs, and copied out that which looked relevant.
  (I will attach the full file of log-excerpts that I created.)

  What seemed most important were:
  "nvidia: module verification failed: signature and/or required key missing - 
tainting kernel"
  "(EE) NVIDIA: Failed to load the NVIDIA kernel module."
  "(EE) Failed to load module "nvidia" (module-specific error, 0)" 

  
  Can anyone say why nvidia-304 appears to install, but never makes it into the 
kernel, and how I can fix this situation?

  [Also, I know 

[Desktop-packages] [Bug 1636582] Re: nvidia-304 - module doesn't install to (or load from) kernal)

2016-11-04 Thread Konrad
Looks like you have the same issue:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802

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

Title:
  nvidia-304 - module doesn't install to (or load from) kernal)

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

Bug description:
  I have used nvidia-304 successfully with Lubuntu up through 16.04.
  (With nouveau, at some time or other, the screen "crashes" and I have
  to hard-shutdown)

  This time, with 16.10, I first noticed only 3 screen resolutions
  possible - max being 1024x768. Further research showed:

  Monitor Settings:  
  "The following monitor is detected...
  Default Monitor"

  scott@scott-ASUS-M2N68-AM-PLUS:~$ sudo lshw -c video
  [sudo] password for scott: 
*-display UNCLAIMED   
 description: VGA compatible controller
 product: C61 [GeForce 7025 / nForce 630a]
 vendor: NVIDIA Corporation
 physical id: d
 bus info: pci@:00:0d.0
 version: a2
 width: 64 bits
 clock: 66MHz
 capabilities: pm msi vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:de00-deff memory:c000-cfff 
memory:dd00-ddff memory:c-d

  scott@scott-ASUS-M2N68-AM-PLUS:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
  default connected 1024x768+0+0 0mm x 0mm
 1024x768  61.00* 
 800x600   61.00  
 640x480   60.00  

  The install from Synaptic had appeared to go just fine:

  Gtk-WARNING **: Theme directory  imported-Humanity/192 of theme Lubuntu has 
no size field
  Selecting previously unselected package nvidia-304.
  (Reading database ... 171834 files and directories currently installed.)
  Preparing to unpack .../0-nvidia-304_304.132-0ubuntu1_amd64.deb ...
  Unpacking nvidia-304 (304.132-0ubuntu1) ...
  Selecting previously unselected package nvidia-current.
  Preparing to unpack .../1-nvidia-current_304.132-0ubuntu1_amd64.deb ...
  Unpacking nvidia-current (304.132-0ubuntu1) ...
  Processing triggers for libc-bin (2.24-3ubuntu1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up nvidia-304 (304.132-0ubuntu1) ...
  update-alternatives: using /usr/lib/nvidia-304/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto 
mode
  update-alternatives: using /usr/lib/nvidia-304/alt_ld.so.conf to provide 
/etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
  update-alternatives: using /usr/share/nvidia-304/glamor.conf to provide 
/usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-304
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Loading new nvidia-304-304.132 DKMS files...
  Building only for 4.8.0-26-generic
  Building for architecture x86_64
  Building initial module for 4.8.0-26-generic
  Done.

  nvidia_304:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.8.0-26-generic/updates/dkms/

  depmod...

  DKMS: install completed.
  Setting up nvidia-current (304.132-0ubuntu1) ...
  Processing triggers for libc-bin (2.24-3ubuntu1) ...
  Processing triggers for initramfs-tools (0.125ubuntu5) ...
  update-initramfs: Generating /boot/initrd.img-4.8.0-26-generic

  However, running lsmod showed no nvidia-304 module, nor did it show
  one for nouveau. So it had correctly removed nouveau, but did not add
  nvidia-304.

  Un-installing nvidia-304 gets me nouveau in lsmod, it finds the VGA
  monitor for xrandr and Monitor Settings, lshw just shows "*-display",
  and I can use up to 1600x1200 - but sooner or later I have to do a
  hard-shutdown because of the vidio-"crash".

  I just tried using "Additional Drivers" to switch to nvidia-304, but with 
exactly the same result. Before I removed the package, I looked through the 
system logs, and copied out that which looked relevant.
  (I will attach the full file of log-excerpts that I created.)

  What seemed most important were:
  "nvidia: module verification failed: signature and/or required key missing - 
tainting kernel"
  "(EE) NVIDIA: Failed to load the NVIDIA kernel module."
  "(EE) Failed to load module "nvidia" (module-specific error, 0)" 

  
  Can anyone say why nvidia-304 appears to install, but never makes it into the 
kernel, and how I can fix this situation?

  [Also, I know that it may not be nvidia-304's 

[Desktop-packages] [Bug 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Jeremy Bicha
** Tags removed: gnome3-ppa gnome3-staging third-party-packages
** Tags added: yakkety zesty

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: light-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1639201] Re: Can not resize GEDIT windows by moving window edge

2016-11-04 Thread Jeremy Bicha
Thank you. I can confirm this bug with Ambiance or Radiance with Ubuntu
GNOME 16.10 when running GNOME Shell.

As a workaround, I suggest you use a different theme. You can change the
them by using the Tweak Tool app. Adwaita is the default and well-
tested. You might also like Greybird (install greybird-gtk-theme ) which
is Xubuntu's default theme.

** Changed in: ubuntu-gnome
   Status: Incomplete => Triaged

** Changed in: ubuntu-gnome
   Importance: Undecided => Low

** Also affects: light-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can not resize GEDIT windows by moving window edge

Status in Ubuntu GNOME:
  Triaged
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  Gedit

  UBUNTU 16.04.1   GNOME 3-20   GEDIT 3.20.2
  Please restore the previously available ability to resize the gedit window by 
grabbing an edge or corner of the window and moving the edge.

  I manipulate many text files each day and frequently have several open and 
visible at the same time on the same monitor. (I have multiple monitors.)  The 
ability to quickly change the dimensions of individual windows is very 
important, and the "new" GNOME 3 method of:
  1. Move mouse to title bar, right click 
  2. move the "selection" bar -DOWN- several lines, click on the word "resize" 
  3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand 
or reduce the window size.
  4. More often then NOT, you then get to do this all over again because the 
computer moved the left side of the window, rather then the right side as you 
had intended, or the top of the window instead of the bottom, or some sort of 
vice-versa forcing you to now move your cursor to the top of the screen to 
reposition the entire window.

  Much easier to just grab an edge and move THAT edge.

  I have also noticed that the majority of the applications installed on
  my system also allow grabbing the window edges, even though most of
  them also have the "click on a non-existant icon and hope that you get
  a usable pulldown menu to do something useful." method of selecting
  options that gnome 3 seems to like.

  What's worse is where the "help" and "preferences" selections are -
  especially when you have a multi-monitor sysytem.  (But I will have to
  say, that GNOME 3 is much better than UNITY.)

  Now if this method of selecting options (Resize, help, preferences,
  Print, etc) was done to support "Touch screens" then I have to ask,
  please, PLEASE, provide a user selectable option of "Desktop" or
  "Touch Screen" so that the user can make their own choice...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:32:16 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1638983] Re: Boot splash with luks password prompt broken after nvidia upgrade to 367

2016-11-04 Thread Rahul Daga
Is there a way to go back to 361? When I purge all nvidia and try
installing 361 it installs 367 instead.

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

Title:
  Boot splash with luks password prompt broken after nvidia upgrade to
  367

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Just got the nvidia driver update from 361 to 367. Upon reboot, the
  boot splash (plymouth?) with the password prompt for the encrypted
  root is missing.

  The screen flashes dark purple and the switches to black with a
  blinking cursor echoing anything typed. Ctrl-alt-del reboots. Booting
  with kernel options "quiet splash" removed results in a text-mode boot
  process where the password prompt is present, proceeding normally.

  Wasn't sure if this was plymouth or nvidia issue, I'm guessing nvidia
  because that's what upgraded and broke functionality.

  Tried redoing update-grub and update-initramfs, didn't help. Found I
  had both nvidia-361 and nvidia-367 installed (why didn't -361
  uninstall?), but manually removing -361 (and redoing initramfs just in
  case) didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 17:45:14 2016
  InstallationDate: Installed on 2016-07-23 (103 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-367
  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-367/+bug/1638983/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Alberto Salvia Novella
** Changed in: cairo (Ubuntu)
   Importance: Undecided => High

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Fix Released

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

2016-11-04 Thread Rocko
@Christopher:

1) It's a physical machine (my laptop).

2) I'm using Ubuntu 16.10.

3) Graphics-wise, it's a standard installation except for the 4.9-rc3
kernel from mainline and a PPA for nvidia graphics drivers (but I wasn't
using the nvidia card at the time this happened, it was all on the Intel
GPU).

I only mentioned it because it looked exactly like what this bug would
have looked like if the laptop screen had been resized to a larger
vertical resolution, say from 1920x900 to 1920x1080, and because just
like this bug, killing and restarting nautilus fixed it (and I *was*
already running the updated nautilus 1:3.20.3-1ubuntu3.1).

I haven't seen it happen again, though, so it's not worth following up
on at this stage since I can't readily reproduce it.

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Yakkety:
  Fix Released

Bug description:
  [ Description ]

  Nautilus's wallpaper drawing doesn't respond to changes in monitor
  configuration. Instead of your wallpaper you see black.

  [ Fix ]

  Inside nautilus, the wallpaper widget connects to GTK's "monitors-
  changed" signal when it is constructed. It does this only once the
  widget is realized - a "realized" signal handler connects to
  "monitors-changed". In Yakkety, the "realized" signal handler is
  connected after the widget is already realized, meaning that the
  signal handler isn't called and we don't connect to the "monitors-
  changed" signal.

  The proposed fix remedies this by checking if we are realized and
  explicitly calling the signal handler if so.

  [ QA ]

  Have multiple monitors. Have only one of them connected. Log in. Plug
  in one monitor. If it's autoactivated, check you see your background
  on both monitors. If not, activate it ("Displays") and do the same.

  [ Regression potential ]

  I'm not sure why or where the order changed to make the widget be
  realized earlier, if it matters or if this was always buggy and we got
  lucky. I would guess a refactoring in Nautilus itself, and so the
  proposed fix is safe, but watch out for other weirdness.

  [ Original description ]

  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  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 Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
   Bus 001 Device 004: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: 

[Desktop-packages] [Bug 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Bug Watch Updater
** Changed in: cairo (Debian)
   Status: Unknown => Fix Released

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Fix Released

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1556296] Re: usb-modeswitch doesn't support usb-modeswitch-data 20160112-1

2016-11-04 Thread Jeremy Bicha
This was fixed in Ubuntu 16.10 with
https://launchpad.net/ubuntu/+source/usb-modeswitch-data/20160803-1.is.really.20151101-1ubuntu1

It was fixed in Ubuntu 16.04 by removing the new usb-modeswitch-data
from proposed.

I opened bug 1639379 to track getting the new usb-modeswitch into
Ubuntu.

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

Title:
  usb-modeswitch doesn't support usb-modeswitch-data 20160112-1

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Hi, this is not a real bug, but it may be somehow annoying - there is
  a new version of usb-modeswitch-data (Proposed: 20160112-1), but the
  usb-modeswitch seems it doesn't work with this version so it cannot be
  upgraded. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1556296/+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 1556296] Re: usb-modeswitch doesn't support usb-modeswitch-data 20160112-1

2016-11-04 Thread Jeremy Bicha
Please do not enable -proposed updates in pre-release versions of
Ubuntu.

** Changed in: usb-modeswitch (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  usb-modeswitch doesn't support usb-modeswitch-data 20160112-1

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Hi, this is not a real bug, but it may be somehow annoying - there is
  a new version of usb-modeswitch-data (Proposed: 20160112-1), but the
  usb-modeswitch seems it doesn't work with this version so it cannot be
  upgraded. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1556296/+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 1639379] [NEW] Merge usb-modeswitch with Debian 2.4.0+repack0-1

2016-11-04 Thread Jeremy Bicha
Public bug reported:

Please merge usb-modeswitch 2.4.0+repack0-1 from Debian
and fakesync usb-modeswitch-data 20160803-1

The last usb-modeswitch update in Ubuntu was
https://launchpad.net/ubuntu/+source/usb-modeswitch/2.2.5+repack0-1ubuntu1

** Affects: usb-modeswitch (Ubuntu)
 Importance: Wishlist
 Status: Confirmed

** Affects: usb-modeswitch-data (Ubuntu)
 Importance: Wishlist
 Status: Confirmed


** Tags: upgrade-software-version zesty

** Also affects: usb-modeswitch-data (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: usb-modeswitch-data (Ubuntu)
   Status: New => Confirmed

** Changed in: usb-modeswitch-data (Ubuntu)
   Importance: Undecided => Wishlist

** Tags added: zesty

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

Title:
  Merge usb-modeswitch with Debian 2.4.0+repack0-1

Status in usb-modeswitch package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  Please merge usb-modeswitch 2.4.0+repack0-1 from Debian
  and fakesync usb-modeswitch-data 20160803-1

  The last usb-modeswitch update in Ubuntu was
  https://launchpad.net/ubuntu/+source/usb-modeswitch/2.2.5+repack0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1639379/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Jeremy Bicha
** Description changed:

  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is already
  fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone else can
  work on the precise update.
  
  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44
  
  I didn't get gdb to work, but when I tried to convert the file, I got a
  crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash . After
  the update, no crash happened.
  
  I reproduced the crash and verified that the new package doesn't crash
- on xenial and yakkety only. I did not test on trusty.
+ on yakkety. In xenial I wasn't able to reproduce the crash. I did not
+ test on trusty.

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Unknown

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1627239] Re: Web pages not rendering with e10s enabled and AppArmor profile in enforce mode

2016-11-04 Thread mikecaines
Should this be reported as a bug against the apparmor package?
https://launchpad.net/ubuntu/+source/apparmor/+bugs

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

Title:
  Web pages not rendering with e10s enabled and AppArmor profile in
  enforce mode

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  STR:
  0. Enable enforce mode for the Firefox app-armor profile: sudo aa-enforce 
usr.bin.firefox
  1. Open Firefox 49 with clean profile (or force-enable e10s as per 
https://wiki.mozilla.org/Electrolysis#Force_Enable and restart Firefox)
  2. Go to any site

  What happens: The site loads but the content is rendered blank. The
  page is loaded properly since I can hover over (invisible) links and
  see the cursor change & the address to be shown in the bottom of the
  window.

  What should happen: The site is rendered properly.

  This is related to e10s and the default AppArmor profile shipped with
  firefox.

  See the attached screenshot for how the first-run page looks like with
  a clean profile, e10s and AppArmor enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 49.0+build4-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BuildID: 20160920074044
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat Sep 24 07:38:09 2016
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  RunningIncompatibleAddons: False
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627239/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Confirmed => Incomplete

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Incomplete
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Jeremy Bicha
** Patch added: "cairo-CVE-2016-9082-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1639372/+attachment/4772690/+files/cairo-CVE-2016-9082-yakkety.debdiff

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Unknown

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Jeremy Bicha
** Patch added: "cairo-CVE-2016-9082-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1639372/+attachment/4772691/+files/cairo-CVE-2016-9082-trusty.debdiff

** Information type changed from Public to Public Security

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9082

** Bug watch added: Debian Bug tracker #842289
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842289

** Also affects: cairo (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842289
   Importance: Unknown
   Status: Unknown

** Bug watch added: freedesktop.org Bugzilla #98165
   https://bugs.freedesktop.org/show_bug.cgi?id=98165

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=98165
   Importance: Unknown
   Status: Unknown

** Tags added: patch precise trusty xenial yakkety zesty

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Unknown

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Jeremy Bicha
** Patch added: "cairo-CVE-2016-9082-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1639372/+attachment/4772689/+files/cairo-CVE-2016-9082-xenial.debdiff

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed
Status in cairo package in Debian:
  Unknown

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 358817] Re: Add irexec, irxevent, ... to session

2016-11-04 Thread Martin von Wittich
Hi Alec, thanks for the feedback; I haven't used lirc for years, so I don't 
really care anymore ^^
Unfortunately I'm also not allowed to set the bug to wontfix, it just says 
"Doesn't fit with the project plans, sorry".

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

Title:
  Add irexec,irxevent,... to session

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  irexec (from package lirc) and irxevent (from package lirc-x) are
  useful tools that enable lirc users execute programs (irexec) or
  generate keystrokes (irxevent). For these to work, they have to be
  added to the session (go to System - Preferences - Sessions - Startup
  Programs and add "irexec -d" and "irxevent -d", but that is not very
  user-friendly and many people don't seem to get this. If you google
  for irexec, you will see that many people instead try to hack it into
  their /etc/init.d/lirc, which is plain wrong because these tools have
  to run inside the user context.

  I propose that the packages lirc and lirc-x should automatically add
  such tools (I name irexec and irxevent here because these are the ones
  I use, but there could be more) to the sessions of all users.

  A possible drawback: running all these tools when the user has only
  configured some of them inside his lircrc wastes memory. We could
  either make this somehow configurable (but I don't know how), or parse
  /etc/lirc/lircrc and ~/.lircrc for the required programs and only add
  those to the session. /etc/init.d/lirc could reparse the files
  whenever neccessary, so when the user edits his .lircrc and adds e.g.
  irexec, the init script could modify the user's session to run irexec
  too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/358817/+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 1639371] Re: OpenGL Graphics broken on November 4th upgrades

2016-11-04 Thread Tim Wescott
Forgot: the pertinent section of /var/log/apt/history.log:

Start-Date: 2016-11-04  10:30:28
Commandline: aptdaemon role='role-commit-packages' sender=':1.134'
Install: screen-resolution-extra:amd64 (0.17.1, automatic), 
nvidia-settings:amd64 (331.20-0ubuntu8, automatic), libcuda1-367:amd64 
(367.57-0ubuntu0.14.04.1), nvidia-367:amd64 (367.57-0ubuntu0.14.04.1), 
bbswitch-dkms:amd64 (0.7-2ubuntu1), nvidia-opencl-icd-340:amd64 
(340.98-0ubuntu0.14.04.1), nvidia-prime:amd64 (0.6.2, automatic)
Upgrade: libnl-genl-3-200:amd64 (3.2.21-1ubuntu3, 3.2.21-1ubuntu4), 
nvidia-opencl-icd-331-updates:amd64 (340.96-0ubuntu0.14.04.1, 
340.98-0ubuntu0.14.04.1), nvidia-opencl-icd-340-updates:amd64 
(340.96-0ubuntu0.14.04.1, 340.98-0ubuntu0.14.04.1), libnl-3-200:amd64 
(3.2.21-1ubuntu3, 3.2.21-1ubuntu4), libcurl3:amd64 (7.35.0-1ubuntu2.9, 
7.35.0-1ubuntu2.10), libnl-route-3-200:amd64 (3.2.21-1ubuntu3, 
3.2.21-1ubuntu4), libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.9, 7.35.0-1ubuntu2.10)
End-Date: 2016-11-04  10:33:20

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

Title:
  OpenGL Graphics broken on November 4th upgrades

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

Bug description:
  First: I don't know if I'm reporting this against the correct package.
  The bug report system needs a "unknown package" reporting system, for
  people who aren't freaking IT experts yet who are still smart enough
  to notice a real live problem.

  I have a Radeon card, but things most definitely broke TODAY
  immediately after I did a software upgrade.

  I use Scilab, which uses OpenGL heavily.  After today's upgrade, it
  was unable to display graphics, reporting

  "Caused by: javax.media.opengl.GLException: Profile GL_DEFAULT is not
  available on X11GraphicsDevice[type .x11, connection :0.0"

  The symptom in Scilab was that the graphics window opened, but no
  graph was drawn upon it.  glxinfo is unable to find an RGB visual; I
  assume that means that GL is broken -- glxinfo certainly works just
  fine on another machine upon which Scilab also works just fine.

  ubuntu-drivers devices returns

  == /sys/devices/pci:00/:00:01.0 ==
  modalias : pci:v1002d130Fsv1043sd85CBbc03sc00i00
  vendor   : Advanced Micro Devices, Inc. [AMD/ATI]
  driver   : fglrx-updates - distro non-free
  driver   : xserver-xorg-video-ati - distro free builtin recommended
  driver   : fglrx - distro non-free

  As near as I can tell, the xserver-xorg-video-ati is installed.  I
  have not attempted to change over to fglrx.

  glxinfo returns:
  name of display: :0.0
  Error: couldn't find RGB GLX visual or fbconfig
  Error: couldn't find RGB GLX visual or fbconfig

  lspci | grep VGA returns
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Kaveri [Radeon R7 Graphics]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1639371/+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 1639371] [NEW] OpenGL Graphics broken on November 4th upgrades

2016-11-04 Thread Tim Wescott
Public bug reported:

First: I don't know if I'm reporting this against the correct package.
The bug report system needs a "unknown package" reporting system, for
people who aren't freaking IT experts yet who are still smart enough to
notice a real live problem.

I have a Radeon card, but things most definitely broke TODAY immediately
after I did a software upgrade.

I use Scilab, which uses OpenGL heavily.  After today's upgrade, it was
unable to display graphics, reporting

"Caused by: javax.media.opengl.GLException: Profile GL_DEFAULT is not
available on X11GraphicsDevice[type .x11, connection :0.0"

The symptom in Scilab was that the graphics window opened, but no graph
was drawn upon it.  glxinfo is unable to find an RGB visual; I assume
that means that GL is broken -- glxinfo certainly works just fine on
another machine upon which Scilab also works just fine.

ubuntu-drivers devices returns

== /sys/devices/pci:00/:00:01.0 ==
modalias : pci:v1002d130Fsv1043sd85CBbc03sc00i00
vendor   : Advanced Micro Devices, Inc. [AMD/ATI]
driver   : fglrx-updates - distro non-free
driver   : xserver-xorg-video-ati - distro free builtin recommended
driver   : fglrx - distro non-free

As near as I can tell, the xserver-xorg-video-ati is installed.  I have
not attempted to change over to fglrx.

glxinfo returns:
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

lspci | grep VGA returns
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Kaveri [Radeon R7 Graphics]

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  OpenGL Graphics broken on November 4th upgrades

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

Bug description:
  First: I don't know if I'm reporting this against the correct package.
  The bug report system needs a "unknown package" reporting system, for
  people who aren't freaking IT experts yet who are still smart enough
  to notice a real live problem.

  I have a Radeon card, but things most definitely broke TODAY
  immediately after I did a software upgrade.

  I use Scilab, which uses OpenGL heavily.  After today's upgrade, it
  was unable to display graphics, reporting

  "Caused by: javax.media.opengl.GLException: Profile GL_DEFAULT is not
  available on X11GraphicsDevice[type .x11, connection :0.0"

  The symptom in Scilab was that the graphics window opened, but no
  graph was drawn upon it.  glxinfo is unable to find an RGB visual; I
  assume that means that GL is broken -- glxinfo certainly works just
  fine on another machine upon which Scilab also works just fine.

  ubuntu-drivers devices returns

  == /sys/devices/pci:00/:00:01.0 ==
  modalias : pci:v1002d130Fsv1043sd85CBbc03sc00i00
  vendor   : Advanced Micro Devices, Inc. [AMD/ATI]
  driver   : fglrx-updates - distro non-free
  driver   : xserver-xorg-video-ati - distro free builtin recommended
  driver   : fglrx - distro non-free

  As near as I can tell, the xserver-xorg-video-ati is installed.  I
  have not attempted to change over to fglrx.

  glxinfo returns:
  name of display: :0.0
  Error: couldn't find RGB GLX visual or fbconfig
  Error: couldn't find RGB GLX visual or fbconfig

  lspci | grep VGA returns
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Kaveri [Radeon R7 Graphics]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1639371/+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 1639372] [NEW] CVE-2016-9082: DOS attack in converting SVG to PNG

2016-11-04 Thread Jeremy Bicha
Public bug reported:

I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is already
fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone else can
work on the precise update.

Proof of Concept at
http://seclists.org/oss-sec/2016/q4/44

I didn't get gdb to work, but when I tried to convert the file, I got a
crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash . After
the update, no crash happened.

I reproduced the crash and verified that the new package doesn't crash
on xenial and yakkety only. I did not test on trusty.

** Affects: cairo (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on xenial and yakkety only. I did not test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1639372/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread alwuzomondo
Here is mine, ran on version 304.131-0ubuntu0.14.04.2

On 04-11-16 17:46, jani wrote:
> Here's mine, although I already downgraded the driver before I ran the
> command.
> 
> ** Attachment added: "nvidia-bug-report.log.gz"
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639051/+attachment/4772565/+files/nvidia-bug-report.log.gz
> 


** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/bugs/1639051/+attachment/4772674/+files/nvidia-bug-report.log.gz

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1631236] Re: Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

2016-11-04 Thread Alberto Salvia Novella
** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Posted first about this issue at
  https://ubuntuforums.org/showthread.php?t=2339198

  Pasted post below:

  "I installed Ubuntu 16.04 Desktop alongside Windows 10 Home on a Dell
  Inspiron 15-7559 with an Nvidia 960m card and embeded Intel Skylake
  graphics.

  When I first installed Ubuntu and attempted to boot, the display would
  freeze on the Ubuntu splash screen after entering my disk password.
  Strangely, by removing "quiet" and "splash" from my grub configuration
  during my next boot, I was able to finally boot to the login screen
  and access the desktop. I installed the Intel and Nvidia drivers in
  the "Additional Drivers" app and now I can boot to the login screen
  with no issues.

  Now, when closing the laptop lid to suspend the system, it resumes to
  a blank screen and I can't get it to recover from this state without
  holding the power button to force shutdown. I verified that it is a
  display issue because I was able to ssh into the machine while it had
  the blank screen.

  I was able to install and boot into the latest (4.8) mainline kernel,
  which also gave me a warning/error because of my installed proprietary
  drivers. I tried uninstalling the Nvidia drivers to see if Nouveau had
  been fixed/improved, but the previous splash screen freeze returned; I
  was able to reinstall the drivers by booting into 4.8 recovery mode
  and using the Failsafe graphics mode to reinstall the Nvidia drivers.

  Any help on getting Nouveau to work nicely with the 960m so I don't
  have to run proprietary drivers or solve the suspend issue?"

  Now, I sometimes cannot shutdown properly without getting warnings
  about cpu soft lockups from gpu-manager. I also get these when I boot
  without nvidia drivers with "quiet" and "splash" options removed from
  my grub config.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Oct  6 20:47:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-040800-generic, x86_64: installed
   nvidia-361, 361.42: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2016-09-29 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-040800-generic 
root=UUID=7dd53585-5dcb-4071-a47a-d1a7fede0e3f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  

[Desktop-packages] [Bug 1627800] Re: Xorg crash

2016-11-04 Thread Alberto Salvia Novella
** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The error occurred when playing streams, such as youtube, soundcloud
  and others by web browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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: Mon Sep 26 14:55:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-31-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2010]
  InstallationDate: Installed on 2016-09-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 2571:4101  
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=2465629d-ee53-4759-bbc2-a56450823561 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 1.05_
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: Intel Corp.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr1.05_:bd03/05/2011:svnIntelCorporation:pnHuronRiverPlatform:pvr0.1:rvnIntelCorp.:rnEmeraldLake:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 25 22:43:46 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id  19 
   vendor INL
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627800/+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 1638719] Re: Widevine crashes on Firefox 49.0.2 and Ubuntu 16.10

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Widevine crashes on Firefox 49.0.2 and Ubuntu 16.10

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 16.10 the Widevine plugin of Firefox crashes when 
trying to watch a video, while Widevine works fine in Chrome.
  Before upgrading it worked without problems with the same Firefox version. So 
I assume there is some conflict with Ubuntu.

  This happens on all my three devices.

  I logged into guest mode and tried it there, but same problem occurs.

  One of some crash reports I sent with Firefox: https://crash-
  stats.mozilla.com/report/index/088a0c5c-5509-423b-8347-6ed842161022
  #tab-details

  My corresponding question on askubuntu:
  http://askubuntu.com/questions/840511/firefox-widevine-plugin-crashes-
  immediately-after-upgrade-to-ubuntu-16-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1638719/+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 1620114] Re: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2016-11-04 Thread Alberto Salvia Novella
** Changed in: cups-filters (Ubuntu)
   Importance: Undecided => High

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Logged eerror

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Sep  4 20:23:57 2016
  DpkgHistoryLog:
   Start-Date: 2016-09-04  20:23:31
   Commandline: aptdaemon role='role-commit-packages' sender=':1.98'
   Upgrade: gnome-sudoku:amd64 (1:3.18.2-1, 1:3.18.4-0ubuntu2), 
google-chrome-stable:amd64 (52.0.2743.116-1, 53.0.2785.92-1)
  DuplicateSignature:
   package:cups-browsed:1.8.3-2ubuntu3.1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package cups-browsed (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-06 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc Dimension E521
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=bae9ce46-9dc5-421f-aaae-5feb0109c268 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2007
  dmi.bios.vendor: Dell Inc
  dmi.bios.version: 1.1.6
  dmi.board.name: 0UW457
  dmi.board.vendor: Dell Inc
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc
  dmi.modalias: 
dmi:bvnDellInc:bvr1.1.6:bd04/07/2007:svnDellInc:pnDimensionE521:pvr:rvnDellInc:rn0UW457:rvrA03:cvnDellInc:ct3:cvr:
  dmi.product.name: Dimension E521
  dmi.sys.vendor: Dell Inc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1620114/+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 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

2016-11-04 Thread Sinclair Yeh
This also fixes a defect we are seeing in a VMWare guest with Ubuntu
16.10.  The issue was wallpaper does not get resized when changing to a
higher desktop resolution, leaving a black border around the wallpaper,
and corruption occurs when when dragging a window over that black
border.

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Yakkety:
  Fix Released

Bug description:
  [ Description ]

  Nautilus's wallpaper drawing doesn't respond to changes in monitor
  configuration. Instead of your wallpaper you see black.

  [ Fix ]

  Inside nautilus, the wallpaper widget connects to GTK's "monitors-
  changed" signal when it is constructed. It does this only once the
  widget is realized - a "realized" signal handler connects to
  "monitors-changed". In Yakkety, the "realized" signal handler is
  connected after the widget is already realized, meaning that the
  signal handler isn't called and we don't connect to the "monitors-
  changed" signal.

  The proposed fix remedies this by checking if we are realized and
  explicitly calling the signal handler if so.

  [ QA ]

  Have multiple monitors. Have only one of them connected. Log in. Plug
  in one monitor. If it's autoactivated, check you see your background
  on both monitors. If not, activate it ("Displays") and do the same.

  [ Regression potential ]

  I'm not sure why or where the order changed to make the widget be
  realized earlier, if it matters or if this was always buggy and we got
  lucky. I would guess a refactoring in Nautilus itself, and so the
  proposed fix is safe, but watch out for other weirdness.

  [ Original description ]

  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  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 Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
   Bus 001 Device 004: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  

[Desktop-packages] [Bug 1639349] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-11-04 Thread Joni Rajala
Public bug reported:

installed Ubuntu 16.04 and it seems to me something went wrong in the
installation or I choose wrong...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Nov  4 22:22:28 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2009-01-01 (2863 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-11-04 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  installed Ubuntu 16.04 and it seems to me something went wrong in the
  installation or I choose wrong...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  4 22:22:28 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2009-01-01 (2863 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-11-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1639349/+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 1639347] [NEW] Please check about these issues

2016-11-04 Thread giorgio
Public bug reported:

I don't know, but don't you receive informatios by the program
Diagnose??

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Fri Nov  4 21:41:04 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
InstallationDate: Installed on 2016-08-24 (72 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.04
dmi.board.name: Newark
dmi.board.vendor: FOXCONN
dmi.board.version: HP P/N
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: NQ918AA-ABZ CQ5023IT
dmi.sys.vendor: Compaq-Presario
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Nov  4 21:15:37 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  Please check about these issues

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know, but don't you receive informatios by the program
  Diagnose??

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Fri Nov  4 21:41:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (72 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-11-04 Thread Josep Pujadas-Jubany
More... about intel drivers...

http://forums.debian.net/viewtopic.php?f=6=128643#p617404

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-11-04 Thread Josep Pujadas-Jubany
The use of this driver is discouraged if your hw is new enough (ca.
2007 and newer). You can try uninstalling this driver and let the
server use it's builtin modesetting driver instead.

https://packages.debian.org/sid/xserver-xorg-video-intel

https://launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/2:2.99.917+git20160325-1ubuntu1.1


sudo apt-get purge xserver-xorg-video*
sudo reboot

Woorking! Solved!

Acer TM B115M

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1639337] [NEW] Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

2016-11-04 Thread Aidan Walton
Public bug reported:

Please refer to bug filed with freedesktop.org:

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

I modified a driver for the Bosto Tablet 22HD and others, this has been
working without problems across the last several releases and continues
to work with 16.04.1 LTS.

When I upgraded to 16.10, pressure readings are lost from all
applications, X & Y data still visible.

evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but when
xinput is used.

xinput --list --long 

The Valuator for pressure is listed, but no changes occur as the tool is
used. The parameters of the Valuator can still be modified using xinput
tweaking tools, but no pressure reported.

All X apps requiring pressure data fail.

I made a fresh install of 16.10, loaded the driver  same issue.

I run 16.04.1 LTS, everything fine.
I have others users of my driver code also using 16.04.1 without issue.

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

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in network-manager package in Ubuntu:
  New

Bug description:
  Please refer to bug filed with freedesktop.org:

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

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639337/+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 1634802] Re: Could not insert module

2016-11-04 Thread Konrad
I've found a hack that will enable nvidia module to insert into kernel:

Uncomment this line:
#PATCH[1]="buildfix_kernel_4.3.patch"

in file /usr/src/nvidia-304-304.132/dkms.conf
then sudo dpkg-reconfigure nvidia-304

In Ubuntu 16.04 it was uncommented, because there were some mtrr changes
in 4.3.0 kernel. This patch works for 4.8.0 kernel also.

Module works, but something is wrong with acceleration, because Unity is
not working. This should throw some light on it:

$ glxgears
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  30
  Current serial number in output stream:  31

but running as sudo works

$ sudo glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
303 frames in 5.0 seconds = 60.420 FPS
300 frames in 5.0 seconds = 59.928 FPS

I'm currently using gnome-session-flashback with metacity.

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+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 1638983] Re: Boot splash with luks password prompt broken after nvidia upgrade to 367

2016-11-04 Thread Alberto Salvia Novella
** Changed in: nvidia-graphics-drivers-367 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Boot splash with luks password prompt broken after nvidia upgrade to
  367

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Just got the nvidia driver update from 361 to 367. Upon reboot, the
  boot splash (plymouth?) with the password prompt for the encrypted
  root is missing.

  The screen flashes dark purple and the switches to black with a
  blinking cursor echoing anything typed. Ctrl-alt-del reboots. Booting
  with kernel options "quiet splash" removed results in a text-mode boot
  process where the password prompt is present, proceeding normally.

  Wasn't sure if this was plymouth or nvidia issue, I'm guessing nvidia
  because that's what upgraded and broke functionality.

  Tried redoing update-grub and update-initramfs, didn't help. Found I
  had both nvidia-361 and nvidia-367 installed (why didn't -361
  uninstall?), but manually removing -361 (and redoing initramfs just in
  case) didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 17:45:14 2016
  InstallationDate: Installed on 2016-07-23 (103 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-367
  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-367/+bug/1638983/+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 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"

2016-11-04 Thread Henry Wertz
I wonder if this is a compiler error?  Can anyone tell if Chromium for
Ubuntu 14.04 and Chromium for 16.04 have different build flags, or if
their configure scripts detect something different?   To me, it seems
like if they have the same or very similar build flags, 16.04 build
breaks but 14.04 build doesn't, it implies gcc-5.4 is misbuilding
something that gcc-4.8 isn't (or, much less likely, gcc-5.4 is building
something correctly but chromium relies on some misbehavior of older
gcc.)

I have an Acer Chromebook 13 (Tegra K1) which had 14.04 on it; Chromium
52 or 53 worked fine.  Went to 16.04 (managing to hold back X so I could
keep the nvidia driver...) and chromium blew up as others have reported.

I also found the 14.04 build of (at this point, chromium 53) worked fine
after I set "--disable-namespace-sandbox"... I had the "Aw, snap!" but
found (per google) that "--disable-namespace-sandbox" fixed it without
the ill effects of "--no-sandbox".

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

Title:
  Chromium-browser armhf crashes with "InitializeSandbox() called with
  multiple threads in process gpu-process"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  crashes on startup with

  [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() 
called with multiple threads in process gpu-process
  Segmentation fault

  System ODROID XU3 armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+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 1289047] Re: [Trusty] hostapd package is broken

2016-11-04 Thread kenn
It's unbelievable to see that the buggy package ist still in repo and no
fix has proposed yet!

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

Title:
  [Trusty] hostapd package is broken

Status in One Hundred Papercuts:
  Triaged
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  When trying to create an access point, I am met with a fatal error
  with hostapd:

  nl80211: Could not configure driver mode
  nl80211 driver initialization failed.
  hostapd_free_hapd_data: Interface wlan0 wasn't started

  What worked before no longer works today after a package upgrade.

  After installing hostapd deb from Ubuntu 13.10, it works.

  WORKAROUND: For this to persist through reboots, execute the following in a 
terminal:
  sudo nano /etc/NetworkManager/NetworkManager.conf

  Add the following entry where the x's are replaced with your WiFi MAC 
address, save, and then reboot:
  [keyfile]
  unmanaged-devices=mac:xx:xx:xx:xx:xx:xx

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hostapd 1:2.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc5-lowlatency x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Thu Mar  6 16:57:20 2014
  InstallationDate: Installed on 2014-02-01 (33 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1289047/+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 1639298] Re: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2016-11-04 Thread Seth Arnold
snapd team:

Preparing to unpack .../gir1.2-accountsservice-1.0_0.6.40-2ubuntu11.3_i386.deb 
...
Unpacking gir1.2-accountsservice-1.0 (0.6.40-2ubuntu11.3) over 
(0.6.40-2ubuntu11.2) ...
Preparing to unpack .../libcuda1-340_340.98-0ubuntu0.16.04.1_i386.deb ...
Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not 
loaded.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/libcuda1-340_340.98-0ubuntu0.16.04.1_i386.deb 
(--unpack):
 there is no script in the new version of the package - giving up
Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or 
directory
var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it.
Preparing to unpack .../libcuda1-331-updates_340.98-0ubuntu0.16.04.1_i386.deb 
...
Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not 
loaded.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/libcuda1-331-updates_340.98-0ubuntu0.16.04.1_i386.deb 
(--unpack):
 there is no script in the new version of the package - giving up

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

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

Title:
  package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  errorenell'aggiornamento automatico

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-331-updates 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  4 17:34:34 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libcuda1-340 340.96-0ubuntu3.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: 2016-05-21 12:31:16,114 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-43-generic, i686: installed
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
   nvidia-304, 304.132, 4.4.0-46-generic, i686: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1969 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to xenial on 2016-05-21 (167 days ago)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  

[Desktop-packages] [Bug 1639296] Re: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2016-11-04 Thread Seth Arnold
Snapd team:

Preparing to unpack .../gir1.2-accountsservice-1.0_0.6.40-2ubuntu11.3_i386.deb 
...
Unpacking gir1.2-accountsservice-1.0 (0.6.40-2ubuntu11.3) over 
(0.6.40-2ubuntu11.2) ...
Preparing to unpack .../libcuda1-340_340.98-0ubuntu0.16.04.1_i386.deb ...
Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not 
loaded.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/libcuda1-340_340.98-0ubuntu0.16.04.1_i386.deb 
(--unpack):
 there is no script in the new version of the package - giving up

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

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

Title:
  package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  errore di installazione

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  4 17:34:33 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: 2016-05-21 12:31:16,114 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-43-generic, i686: installed
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1969 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to xenial on 2016-05-21 (167 days ago)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  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 Nov  4 17:14:38 2016
  xserver.configfile: default
 

[Desktop-packages] [Bug 1639084] Re: Slash in filename gives misleading error

2016-11-04 Thread Andrew Cone
My fix:
https://github.com/GNOME/gnome-screenshot/pull/3

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

Title:
  Slash in filename gives misleading error

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  If you put a slash in the filename, it fails to write it. This means
  that filenames are not being correctly sanitized.

  It is very natural to put a slash in a filename from gnome-screenshot
  because that is how dates are delimited in the US.

  Filenames should be sanity checked and sanitized by some standard
  means. They should probably not be interpreted as paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1639084/+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 1623666] Re: iOS10 will not connect to Ubuntu

2016-11-04 Thread Sam Gleske
This issue has been resolved after working with upstream maintainers.

See https://gitlab.com/gnutls/gnutls/issues/145

For the resolution see
https://github.com/libimobiledevice/libimobiledevice/issues/413

** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #413
   https://github.com/libimobiledevice/libimobiledevice/issues/413

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1639298] Re: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2016-11-04 Thread Seth Arnold
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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1639298

Title:
  package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  errorenell'aggiornamento automatico

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-331-updates 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  4 17:34:34 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libcuda1-340 340.96-0ubuntu3.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: 2016-05-21 12:31:16,114 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-43-generic, i686: installed
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
   nvidia-304, 304.132, 4.4.0-46-generic, i686: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1969 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-331-updates 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to xenial on 2016-05-21 (167 days ago)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  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 Nov  4 17:14:38 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1639296] Re: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2016-11-04 Thread Seth Arnold
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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1639296

Title:
  package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  errore di installazione

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  4 17:34:33 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: 2016-05-21 12:31:16,114 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-43-generic, i686: installed
   bbswitch, 0.8, 4.4.0-46-generic, i686: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1969 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to xenial on 2016-05-21 (167 days ago)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  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 Nov  4 17:14:38 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1635855] Re: Inkscape doesn't get installed from the Software Center on Ubuntu 16.10

2016-11-04 Thread su_v
** Also affects: inkscape (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Inkscape doesn't get installed from the Software Center on Ubuntu
  16.10

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  I have Samsung NC10 netbook. I am using Ubuntu 16.10. When in the
  Software Center, Inkscape starts to install then stops and the install
  button appears again. I have downloaded the inkscape.deb file and
  lunched sudo dpkg -i inkscape.deb in the terminal, it has responded to
  me, that it has dependencies problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1635855/+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 1612367] Re: [Touch] Incoming call gets silent randomly

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-11-04 Thread Pat McGowan
pending feedback from the system enablement team whether we fix or not

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

** Tags added: bq

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

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Jan Herold
bug report created with sudo nvidia-bug-report.sh as suggested at
comment 6 for bug 1639180

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+attachment/4772583/+files/nvidia-bug-report.log.gz

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639300] Re: Error while loading shared libraries

2016-11-04 Thread su_v
** Also affects: inkscape (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Error while loading shared libraries

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  Hi

  I can't run Inskcape 0.91
  Installation was fine :
  $ apt-cache policy inkscape
  inkscape:
Installed: 0.91-7ubuntu2
Candidate: 0.91-7ubuntu2
Version table:
   *** 0.91-7ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  A library seems to be missing when launching: 

  inkscape: error while loading shared libraries: libIlmImf.so.6: cannot
  open shared object file: No such file or directory

  Running Ubuntu 16.04 xenial 
  4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 
x86_64 GNU/Linux

  $ ldd $(which inkscape)
  linux-vdso.so.1 =>  (0x7ffc0e9ba000)
libgtkspell.so.0 => /usr/lib/libgtkspell.so.0 (0x7f801000)
libgtkmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1 
(0x7f801b598000)
libatkmm-1.6.so.1 => /usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1 
(0x7f801b34d000)
libgdkmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgdkmm-2.4.so.1 
(0x7f801b10)
libpangomm-1.4.so.1 => /usr/lib/x86_64-linux-gnu/libpangomm-1.4.so.1 
(0x7f801aed3000)
libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 
(0x7f801a887000)
libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 
(0x7f801a5d2000)
libpangocairo-1.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7f801a3c5000)
libgdk_pixbuf-2.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7f801a1a2000)
libgc.so.1 => /usr/lib/x86_64-linux-gnu/libgc.so.1 (0x7f8019f31000)
libcairomm-1.0.so.1 => /usr/lib/x86_64-linux-gnu/libcairomm-1.0.so.1 
(0x7f8019d0d000)
libgiomm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1 
(0x7f8019968000)
libglibmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 
(0x7f80196ef000)
libgsl.so.19 => /usr/lib/x86_64-linux-gnu/libgsl.so.19 
(0x7f80192b)
libgslcblas.so.0 => /usr/lib/x86_64-linux-gnu/libgslcblas.so.0 
(0x7f8019071000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 
(0x7f8018e4c000)
libxslt.so.1 => /usr/lib/x86_64-linux-gnu/libxslt.so.1 
(0x7f8018c0f000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x7f8018854000)
libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 
(0x7f801863e000)
libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7f80183f2000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7f80181ae000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8017fa8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8017d8e000)
libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 
(0x7f8017b6b000)
libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0 (0x7f801795f000)
libaspell.so.15 => /usr/lib/x86_64-linux-gnu/libaspell.so.15 
(0x7f80176b5000)
libgnomevfs-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 
(0x7f801744b000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7f80171a1000)
libwpg-0.3.so.3 => /usr/lib/x86_64-linux-gnu/libwpg-0.3.so.3 
(0x7f8016f85000)
libvisio-0.1.so.1 => /usr/lib/x86_64-linux-gnu/libvisio-0.1.so.1 
(0x7f8016cea000)
libcdr-0.1.so.1 => /usr/lib/x86_64-linux-gnu/libcdr-0.1.so.1 
(0x7f8016a4f000)
librevenge-0.0.so.0 => /usr/lib/x86_64-linux-gnu/librevenge-0.0.so.0 
(0x7f8016827000)
librevenge-stream-0.0.so.0 => 
/usr/lib/x86_64-linux-gnu/librevenge-stream-0.0.so.0 (0x7f8016608000)
libMagick++-6.Q16.so.5 => 
/usr/lib/x86_64-linux-gnu/libMagick++-6.Q16.so.5 (0x7f8016389000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7f801604f000)
libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8 
(0x7f8015df5000)
liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 
(0x7f8015b9e000)
libpoppler.so.58 => /usr/lib/x86_64-linux-gnu/libpoppler.so.58 
(0x7f801572)
libpoppler-glib.so.8 => /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 
(0x7f80154c7000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7f8015274000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f8014f63000)
libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 
(0x7f8014c4e000)
libstdc++.so.6 => 

[Desktop-packages] [Bug 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread jani
alwuzomondo:
Ah, you had/have it available. I don't and had to go for 304.117. 

Thanks for answering again.

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread jani
Here's mine, although I already downgraded the driver before I ran the
command.

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639051/+attachment/4772565/+files/nvidia-bug-report.log.gz

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1500282] Re: pixel scaling seems to be rounded to integers

2016-11-04 Thread Kai Mast
Seems to be fixed for Firefox in xenial but not for Thunderbird.

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

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

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

Title:
  pixel scaling seems to be rounded to integers

Status in Mozilla Firefox:
  Confirmed
Status in Mozilla Thunderbird:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Firefox adapts its highdpi settings to the value in unity-control-
  center.

  However, right now I have it set to 1.5 and firefox seems to scale it
  to 2.0. I.e. everything is much bigger than it should be.

  If I set devPixelsPerPx to 1.5 manually everything looks fine. So
  there must be some bug in firefox that is reading this value as an
  integer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1500282/+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 1630455] Re: rhythmbox crashes soon after being start in Ubuntu 16.04.1 with rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  rhythmbox crashes soon after being start in Ubuntu 16.04.1 with
  rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  For a few years, I used Ubuntu 12.04. I used rhythmbox in it all these
  years, it worked fine. Some library was collected.

  Then I upgraded to 14.04, and to 16.04 right away.

  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

  After I start rhythmbox, in a few seconds it crashes, even if I do
  nothing. Here is the output:

  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack:
  Add to Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist

  
  (rhythmbox:22810): RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: 
assertion 'entry != NULL' failed
  Ошибка сегментирования (сделан дамп памяти)

  
  rhythmbox version is 3.3-1ubuntu7.

  I'm filing this bug here by hand because aport does not see these
  crashes for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1630455/+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 1627055] Re: CVE-2016-7382, 2016-7389

2016-11-04 Thread Marc Deslauriers
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: nvidia-graphics-drivers-367 (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: nvidia-graphics-drivers-367 (Ubuntu Precise)
   Status: New => Invalid

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

Title:
  CVE-2016-7382, 2016-7389

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  Fix Released

Bug description:
  The NVIDIA drivers are affected by a couple of vulnerabilities
  (CVE-2016-7382, 2016-7389), which NVIDIA are going to disclose on
  10/19.

  All the NVIDIA drivers in all the supported Ubuntu releases (12.04,
  14.04, 16.04) are affected.

  I am going to take care of the packaging and of the migrations to the
  new driver packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1627055/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Alberto Milone
Can you run the following command, and attach the resulting nvidia-bug-
report.log.gz (from your home directory), please?

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1635677] Re: Rename deletes the current name when using ibus-chewing

2016-11-04 Thread Jiawen Chen
** Changed in: nautilus (Ubuntu)
   Status: New => Fix Released

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

Title:
  Rename deletes the current name when using ibus-chewing

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When I rename in nautilus, the file name (not including extension
  name) will be cleared automatically. It is counter-productive when I
  want do make minor change to the file name, for example pluralizing.
  Unfortunately this case is one big use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635677/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Alberto Milone
sudo nvidia-bug-report.sh

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread Alberto Milone
Can you run the following command, and attach the resulting nvidia-bug-
report.log.gz (from your home directory), please?

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread Alberto Milone
sudo nvidia-bug-report.sh

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1563588] Re: Synaptic Touchpad does not work on a Gigabyte P25W

2016-11-04 Thread Kushal
Wait, why did it expire?

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Expired => Incomplete

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

Title:
  Synaptic Touchpad does not work on a Gigabyte P25W

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

Bug description:
  Followed directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Touchpad does not show up at all in Ubuntu.

  cat /proc/bus/input/devices does not show the trackpad but an external
  mouse works fine.

  I've attached the dmesg here. I'll add xorg logs in a bit. Lauchpad
  won't let me add multiple attachments for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1563588/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-04 Thread Michael Sheldon
** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-04 Thread alwuzomondo
hi Jani,

I went back to version: 304.131-0ubuntu0.14.04.2

 1931  tail -n100 /var/log/apt/history.log
 1932  sudo apt-cache policy nvidia-current
 1933  sudo apt-get install nvidia-current=304.131-0ubuntu0.14.04.2
 1934  sudo apt-cache policy nvidia-current
 1935  sudo apt-get install nvidia-current=304.117-0ubuntu1
 1938  sudo apt-cache policy nvidia-current
 1939  sudo apt-cache policy nvidia-304
 1940  sudo apt-get install nvidia-
 1941  sudo apt-cache policy nvidia-304
 1942  sudo apt-get install nvidia-304=304.131-0ubuntu0.14.04.2
 1943  sudo apt-cache policy nvidia-libopencl1-304
 1944  sudo apt-get install nvidia-libopencl1-304=304.131-0ubuntu0.14.04.2
 1945  sudo apt-cache policy nvidia-opencl-icd-304
 1946  sudo apt-get install nvidia-opencl-icd-304=304.131-0ubuntu0.14.04.2
 1947  sudo apt-cache policy libcuda1-304
 1948  sudo apt-get install libcuda1-304=304.131-0ubuntu0.14.04.2
 1952  sudo apt-get update

Available versions on my system:

:~$ sudo apt-cache policy nvidia-current
nvidia-current:
  Installed: 304.131-0ubuntu0.14.04.2
  Candidate: 304.131-0ubuntu0.14.04.2
  Package pin: 304.131-0ubuntu0.14.04.2
  Version table:
 304.132-0ubuntu0.14.04.2 1000
500 http://nl.archive.ubuntu.com/ubuntu/
trusty-updates/restricted amd64 Packages
500 http://security.ubuntu.com/ubuntu/
trusty-security/restricted amd64 Packages
 *** 304.131-0ubuntu0.14.04.2 1000
100 /var/lib/dpkg/status
 304.117-0ubuntu1 1000
500 http://nl.archive.ubuntu.com/ubuntu/ trusty/restricted amd64
Packages

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet 

[Desktop-packages] [Bug 1633527] Re: Nautilus 3.20 : deleted items are not shown in Trash folder

2016-11-04 Thread Luka
*** This bug is a duplicate of bug 1633824 ***
https://bugs.launchpad.net/bugs/1633824

Not a duplicate of #1633824, happens with other partitions on internal
HDD as well (tested only with NTFS), only files showing up in Trash are
those deleted from /home/user/

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

Title:
  Nautilus 3.20 : deleted items are not shown in Trash folder

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After a clean installation of Ubuntu 16.10, all files and folders being 
deleted from mounted ext4 partitions are not shown in the Trash folder. The 
items being deleted from the /home directory are shown. The deleted items are 
present in the .Trash-1000 folder of each ext4 partition though. After 
permanently deleting the folder and again deleting something, the folder is 
recreated as expected, but the Expunged sub folder is missing and there is 
still nothing to be seen in the Trash folder. The same behavior occurs when 
doing it from the installation media. This does not happen in other Linux 
distributions with GNOME 3.20 desktop environment when using the Nautilus 3.20 
file manager.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  DistroRelease: Ubuntu 16.10
  GsettingsChanges:
   org.gnome.nautilus.preferences click-policy 'single'
   org.gnome.nautilus.preferences show-delete-permanently true
   org.gnome.nautilus.preferences default-folder-viewer 'list-view'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.list-view default-visible-columns ['name', 'size', 
'type', 'date_modified']
  InstallationDate: Installed on 2016-10-13 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: nautilus 1:3.20.3-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633527/+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 1639280] [NEW] Firefox Sync is not working.

2016-11-04 Thread Anton
Public bug reported:

"Invalid authorization code" message every time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 49.0.2+build2-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  anarchy3658 F pulseaudio
 /dev/snd/controlC0:  anarchy3658 F pulseaudio
BuildID: 20161025170400
Channel: Unavailable
CurrentDesktop: Unity
Date: Fri Nov  4 18:37:15 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-11-04 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.0.1 dev enp3s0  proto static  metric 100 
 169.254.0.0/16 dev enp3s0  scope link  metric 1000 
 192.168.0.0/24 dev enp3s0  proto kernel  scope link  src 192.168.0.101  metric 
100
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=49.0.2/20161025170400 (In use)
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z77 Pro4-M
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.30:bd07/13/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro4-M: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.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Firefox Sync is not working.

Status in firefox package in Ubuntu:
  New

Bug description:
  "Invalid authorization code" message every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 49.0.2+build2-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anarchy3658 F pulseaudio
   /dev/snd/controlC0:  anarchy3658 F pulseaudio
  BuildID: 20161025170400
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Nov  4 18:37:15 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.0.0/24 dev enp3s0  proto kernel  scope link  src 192.168.0.101  
metric 100
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=49.0.2/20161025170400 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: Z77 Pro4-M
  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.30:bd07/13/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be 

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread jokrebel
Same here. 
Since upgrade with "nvidia-304:i386 (304.131-0ubuntu3, 
304.132-0ubuntu0.16.04.2" I am no more able to login into Unity or Gnome 
(Compiz). After a vew Seconds the Login-Screen gets back.
With Gnome (Metacity) login is possible

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Jamie Strandboge
More details:
- this is on Ubuntu 12.04
- the module does load into the kernel
- lightdm does present a login screen
- nvidia-340 doesn't work on this system
- compiz fails to start (from ~/.xsession-errors):
gnome-session[6632]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[6632]: WARNING: Application 'compiz.desktop' killed by signal
gnome-session[6632]: WARNING: App 'compiz.desktop' respawning too quickly
- no amount of moving ~/.compiz* ~/.nv* ~/.cache/compiz* ~/.config/compiz* 
aside made a difference

The only thing that worked was grabbing the previous version from here:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/304.131-0ubuntu0.12.04.1

and apt-pinning it like so:
/etc/apt/preferences.d/nvidia.pref 
Package: nvidia-304
Pin: version 304.131-0ubuntu0.12.04.1
Pin-Priority: 1001

Package: nvidia-current
Pin: version 304.131-0ubuntu0.12.04.1
Pin-Priority: 1001

'sudo apt-get update && sudo apt-get upgrade' now does not upgrade to
the problematic version.

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1634939] Re: Copy progress popover should close on completion

2016-11-04 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => Confirmed

** Changed in: nautilus
   Importance: Unknown => Medium

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

Title:
  Copy progress popover should close on completion

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

Bug description:
  When copying folders/files and the popover progress window opens it
  pops up in all opened instances of Nautilus. You also need to close
  the popover on every single window or close every window to get it to
  disappear. This also applies to the progress-bar in launcher.

  Expected behavior: copy popover should close after successfully
  performing the copy operation.

  Ubuntu 16.10
  Nautilus 1:3.20.3-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1634939/+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 1638983] Re: Boot splash with luks password prompt broken after nvidia upgrade to 367

2016-11-04 Thread Mike Berkley
Worked around the problem by:
0. Use "Esc" key to interrupt boot, edit boot to remove "quiet splash" from 
boot line, then boot.
1. Replace "quiet splash" with "" in /etc/default/grub
2. Run "sudo update-grub".

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

Title:
  Boot splash with luks password prompt broken after nvidia upgrade to
  367

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Just got the nvidia driver update from 361 to 367. Upon reboot, the
  boot splash (plymouth?) with the password prompt for the encrypted
  root is missing.

  The screen flashes dark purple and the switches to black with a
  blinking cursor echoing anything typed. Ctrl-alt-del reboots. Booting
  with kernel options "quiet splash" removed results in a text-mode boot
  process where the password prompt is present, proceeding normally.

  Wasn't sure if this was plymouth or nvidia issue, I'm guessing nvidia
  because that's what upgraded and broke functionality.

  Tried redoing update-grub and update-initramfs, didn't help. Found I
  had both nvidia-361 and nvidia-367 installed (why didn't -361
  uninstall?), but manually removing -361 (and redoing initramfs just in
  case) didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 17:45:14 2016
  InstallationDate: Installed on 2016-07-23 (103 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-367
  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-367/+bug/1638983/+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 1582430] Re: spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

2016-11-04 Thread Andrea Azzarone
** Changed in: bamf (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is
  already playing music

Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already 
playing music

  [Test Case]

  1. Start Rhythmbox.
  2. Play some music.
  3. Close the Rhythmbox window.
  4. Open Rhythmbox from Dash or Launcher (if Rhythmbox is locked to it).
  5. Admire annoying spinning wheel for about 13 seconds.

  If Rhythmbox is reopened from the sound tray menu it is ok, no
  spinning wheel.

  [Possible Regresssions]
  Unity fails to notify the application startup or the startup notification 
process finishes too soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1582430/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Jamie Strandboge
I see this on:
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 305M] 
(rev a2) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device 395a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d200 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at 4000 [size=128]
[virtual] Expansion ROM at d308 [disabled] [size=512K]
Capabilities: 
Kernel driver in use: nvidia
Kernel modules: nvidia_304, nouveau, nvidiafb

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  no login possible after update to nvidia 304.132

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

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-11-04 Thread Trent Gamblin
Have the same issue FWIW. Even many apps that ship with Ubuntu can't be
clicked anymore. If nothing else perhaps keying of 'interpreter' would
be more reasonable as none of the shared libraries I've checked have
one.

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

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

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

  Also, all executable files compiled with gcc6 have a generic icon
  instead of the purple lozenge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1635376/+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 1638373] Re: End marker/start marker drop-down menus are empty

2016-11-04 Thread Hachmann
@rot13: Ah, that's unfortunate...

Can you post this as a new bug report? It's a problem on the Inkscape
side of the ppa / build process, and not a downstream packaging problem
(and also add this info: for Ubuntu 16.04, libpoppler58 is available,
while 61 is not, so hopefully it is not exchanged, but rather both
versions should be allowed - else it won't work on the LTS version
anymore).

You can also just copy the whole share/... folder from the repo,
meanwhile (and remove the ppa, use the version from Ubuntu repos).

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

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  The dropdown menus for start marker, end marker and mid markers do not
  contains any arrows to select. I have clean up all local settings and
  run inkscape fresh but the same problem.

  Inkscape 0.91, Ubuntu 16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1638373/+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 1607815] Re: After suspend, connected to wifi but wifi indicator not showing signal strength

2016-11-04 Thread Dariusz Gadomski
Hey David,
Since the upstream issue (as linked in bug #1589401) seems to be stuck and 
their last request was to test a clean nm-applet build without Ubuntu patches - 
I have prepared such in a ppa:dgadomski/nm-applet.

It's basically a Xenial build with the patches disabled.

Could you please give it a try and report if the behaviour is any
different from the default build?

Thanks!

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

Title:
  After suspend, connected to wifi but wifi indicator not showing signal
  strength

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have an issue that is similar to the following bugs:

  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347
  https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143

  I am running Xenial 16.04.1. I did an apt-get dist-upgrade on July
  29th 2016 and rebooted after the upgrade and put the laptop in suspend
  mode before going to bed. This morning (July 30th), I resumed my
  laptop and I see up-down arrows instead of a wifi icon in the system
  tray to the top right. After about 15 seconds, the wifi icon appears
  instead of the arrows and does a little scan action animation. After
  that, my Internet works but I can't see the strength bars on the icon
  (as if the signal strength was zero bars). When I click on the icon, I
  can't see my wifi network in the list of networks anywhere.

  My wifi connection works, but the icon does not show it.

  A "sudo service network-manager restart" fixes this issue. I can then
  see my wifi network in the Wi-Fi Networks list.

  ---

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.0-0ubuntu0.16.04.3
Candidate: 1.2.0-0ubuntu0.16.04.3
Version table:
   *** 1.2.0-0ubuntu0.16.04.3 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  Attached is a screenshot of the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1607815/+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 1638373] Re: End marker/start marker drop-down menus are empty

2016-11-04 Thread rot13
I have the same problem and I tried installing from PPA, but then I get:

The following packages have unmet dependencies:
 inkscape : Depends: libpoppler58 (>= 0.41.0) but it is not installable
E: Unable to correct problems, you have held broken packages.

I only have libpoppler61, not 58, in my packages.

# apt-cache policy inkscape
inkscape:
  Installed: 0.91-11
  Candidate: 0.91.0+51~ubuntu16.10.1
  Version table:
 0.91.0+51~ubuntu16.10.1 500
500 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu yakkety/main 
amd64 Packages
 *** 0.91-11 500
500 http://pl.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy libpoppler58
libpoppler58:
  Installed: (none)
  Candidate: (none)
  Version table:
# apt-cache policy libpoppler61
libpoppler61:
  Installed: 0.44.0-3ubuntu2
  Candidate: 0.44.0-3ubuntu2
  Version table:
 *** 0.44.0-3ubuntu2 500
500 http://pl.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  The dropdown menus for start marker, end marker and mid markers do not
  contains any arrows to select. I have clean up all local settings and
  run inkscape fresh but the same problem.

  Inkscape 0.91, Ubuntu 16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1638373/+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 1196239] Re: Add support for fake modes on laptop screens which only have one

2016-11-04 Thread Bill Filler
this feature becomes quite critical to use a unity8 desktop, as it's
unusable now on a high res screen unless you have amazing vision :)

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

Title:
  Add support for fake modes on laptop screens which only have one

Status in Canonical System Image:
  Triaged
Status in Mir:
  Triaged
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+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 1638929] Re: after disabling a display, enabling makes screens go black

2016-11-04 Thread Jonas G. Drange
(Got my bugs mixed up, I didn't actually mention silo 2140. :))

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638929/+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 1638929] Re: after disabling a display, enabling makes screens go black

2016-11-04 Thread Jonas G. Drange
Silo 2140 as mentioned will give you a way to reproduce this. I am
currently unable to since I've lost the option to log into a unity8 desktop
session.

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638929/+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 1633826] Re: nautilus desktop crashes when called with --no-desktop

2016-11-04 Thread Fork
This issue actually appears to be a regression:
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1453655

I'm reluctant to mark the bug as duplicate, though, since the other
issue is version-specific and marked as closed.

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

Title:
  nautilus desktop crashes when called with --no-desktop

Status in nautilus package in Ubuntu:
  Incomplete
Status in nautilus-dropbox package in Ubuntu:
  Confirmed

Bug description:
  When calling nautilus with the --no-desktop flag in Ubuntu 16.10 while
  it is already running, the existing desktop stops responding. All
  icons disappear, and the desktop doesn't react to mouse input.

  nautilus may or may not throw the following error:

  (nautilus:3723): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  (nautilus:3723): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  This is relevant since e.g. the Dropbox indicator calls nautilus this
  way, resulting in the desktop crashing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633826/+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 1634930] Re: emacs24 fails to build on ppc64el

2016-11-04 Thread Graham Inggs
** Also affects: notmuch (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  emacs24 fails to build on ppc64el

Status in emacs24 package in Ubuntu:
  New
Status in gnuplot package in Ubuntu:
  New
Status in hkl package in Ubuntu:
  New
Status in ledger package in Ubuntu:
  New
Status in notmuch package in Ubuntu:
  New

Bug description:
  https://launchpad.net/ubuntu/+source/emacs24/24.5+1-7ubuntu1/+build/11038801

  building with -O2, -fno-PIE, or building sequentially doesn't help,
  even with 12GB of RAM.

  make[4]: Entering directory 
'/home/doko/tmp/emacs24-24.5+1/debian/build-x/lisp'
  Compiling emacs-lisp/cconv.el
  Compiling emacs-lisp/macroexp.el
  Compiling emacs-lisp/bytecomp.el
  Compiling emacs-lisp/autoload.el
  Compiling emacs-lisp/byte-opt.el
  
Memory e
MxMMM-h---xaxxx u   sted--susossmosoomeemme- 
ee-Mb--bu-bbufuxufff ffefsefraeresvrrs ses t - thsthtoehenhme neen e-n exb 
exieuxtxifi itftate  n raadasnn n ddrdt  e hrrsreeetnessa sttertaaxtarr rittEtt 
 m E EaamEmcnamasdacc
  cssrs

  e
  start Emacs
  Makefile:282: recipe for target 'emacs-lisp/macroexp.elc' failed
  make[4]: *** [emacs-lisp/macroexp.elc] Error 255
  make[4]: *** Waiting for unfinished jobs
  Makefile:282: recipe for target 'emacs-lisp/cconv.elc' failed
  make[4]: *** [emacs-lisp/cconv.elc] Error 255
  Makefile:282: recipe for target 'emacs-lisp/autoload.elc' failed
  make[4]: *** [emacs-lisp/autoload.elc] Error 255
  Makefile:282: recipe for target 'emacs-lisp/bytecomp.elc' failed
  make[4]: *** [emacs-lisp/bytecomp.elc] Error 255
  Makefile:282: recipe for target 'emacs-lisp/byte-opt.elc' failed
  make[4]: *** [emacs-lisp/byte-opt.elc] Error 255
  make[4]: Leaving directory '/home/doko/tmp/emacs24-24.5+1/debian/build-x/lisp'
  Makefile:815: recipe for target 'bootstrap-emacs' failed
  make[3]: *** [bootstrap-emacs] Error 2
  make[3]: Leaving directory '/home/doko/tmp/emacs24-24.5+1/debian/build-x/src'
  Makefile:389: recipe for target 'src' failed
  make[2]: *** [src] Error 2
  make[2]: Leaving directory '/home/doko/tmp/emacs24-24.5+1/debian/build-x'
  debian/rules:373: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/home/doko/tmp/emacs24-24.5+1'
  debian/rules:240: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1634930/+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 1639223] [NEW] Cannot connect to web with bluetooth connection after resuming from suspend

2016-11-04 Thread Peter Rhone
Public bug reported:

If I resume from suspend and reconnect my phone's bluetooth internet
connection, my web browsers claim I'm offline. I can successfully ping
8.8.8.8 but cannot resolve domain names. Restarting network manager with
"sudo service network-manager restart" and reconnecting to my phone
fixes the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Nov  4 11:57:24 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-12-15 (689 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IpRoute:
 default via 192.168.44.1 dev bnep0  proto static  metric 750 
 169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
 192.168.44.0/24 dev bnep0  proto kernel  scope link  src 192.168.44.77  metric 
750 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-16 (18 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Cannot connect to web with bluetooth connection after resuming from
  suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  If I resume from suspend and reconnect my phone's bluetooth internet
  connection, my web browsers claim I'm offline. I can successfully ping
  8.8.8.8 but cannot resolve domain names. Restarting network manager
  with "sudo service network-manager restart" and reconnecting to my
  phone fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov  4 11:57:24 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-15 (689 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.44.1 dev bnep0  proto static  metric 750 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.44.0/24 dev bnep0  proto kernel  scope link  src 192.168.44.77  
metric 750 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (18 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639223/+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 1612240] Re: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

2016-11-04 Thread Luca Boccassi
Hello,

Just found this discussion. We just released 4.2.0, sorry it took a while, 
difficult times.
I hope the delay didn't cause you guys too much trouble.

The patch to use dynamic ports in the test looks very interesting, it's
something I wanted to fix for a while but never had to the time, so if
you want to push it up to Github we'd have a look, although it has to
work on Windows too (I see there's some pthread use). Also at least one
should use the hard-coded port, to test that code path, but it can be a
separate individual unit test.

Thanks for your work!

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

Title:
  [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zmqpp package in Ubuntu:
  Fix Released

Bug description:
  Please update zmqpp to version 4.1.2 with the following patch that I proposed 
upstream (it got merged into their "develop" branch):
  https://github.com/zeromq/zmqpp/pull/167/files

  (alternatively, use master + my patch or develop branch of zmqpp).

  This will require the current git snapshot of the zmq library (which
  will be version 4.2 when it's released) -
  https://github.com/zeromq/libzmq

  All the above is needed to support the new USE_FD socket option, which
  will probably be critical for scopes as snaps.

  == Feature Freeze Exception details ==

  These packages are required by the ongoing work of the unity scopes
  for snappy. Due to unrelated to zeromq issues (unity-scopes-api unit-
  test issues on arm64, possibly due to recent toolchain changes) we did
  not make it in time before Feature Freeze. The packages have been
  prepared and tested in:

  https://launchpad.net/~ci-train-ppa-
  
service/+archive/ubuntu/landing-005/+packages?field.name_filter=_filter=published_filter=yakkety

  There is no ABI breakage in zeromq3 so no reverse-depends rebuilds are
  required. The zmqpp package does break ABI so a so bump and rebuild of
  rev-deps was needed, but the currently only consumer of the zmqpp
  packages is unity-scopes-api. The new release of zeromq3 is based on a
  git snapshot as a new stable release of this project is planned in the
  nearest future, so a bit too late for the current plans. Some reverse-
  depends of zeromq3 have been tested to work fine with the new package
  as is.

  We kindly request a FFe for this very particular case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1612240/+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 1622073] Re: zmq::mechanism_t::socket_type_string off-by-one

2016-11-04 Thread Luca Boccassi
Hi,

Good catch!

This is fixed in 4.2.0 already, and I will fix it for the next 4.1
stable release (4.1.7).

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

Title:
  zmq::mechanism_t::socket_type_string off-by-one

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  Hello, the zmq::mechanism_t::socket_type_string function in
  ./src/mechanism.cpp appears to have an off-by-one mistake:

  const char *zmq::mechanism_t::socket_type_string (int socket_type) const 
  {   
  static const char *names [] = {"PAIR", "PUB", "SUB", "REQ", "REP",
 "DEALER", "ROUTER", "PULL", "PUSH",
 "XPUB", "XSUB", "STREAM"};
  zmq_assert (socket_type >= 0 && socket_type <= 10);
  return names [socket_type];
  }   

  names[11] is "STREAM" but that triggers the assert.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1622073/+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 1636397] Re: Fix modesetting slave output names

2016-11-04 Thread Kai-Heng Feng
** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed
Status in xorg-server source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Currently, NVIDIA and modesetting drivers are using same output names, that 
creates confusion for xrandr clients like gnome-setting-daemon or xrandr 
utility.

  When modesetting outputs act as slave for other x-screen (like NVIDIA
  X-screen here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

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


  1   2   >