[Desktop-packages] [Bug 1681523] Re: [Launcher] missing right click options

2017-07-13 Thread md_5
Apologies for the spam, but this was fixed for Artful in:

gnome-terminal (3.24.1-0ubuntu2) artful; urgency=medium

  * Revert 01_onlyshowin.patch to use Unity instead of Unity7
to fix test failure triggered by desktop-file-validate

 -- Jeremy Bicha   Wed, 03 May 2017 06:52:22 -0400

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

Title:
  [Launcher] missing right click options

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Running : 
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Not sure where to postthis but...

  Just noticed that "Right Click" options for the "Terminal" App are
  missing when it's locked to the 'Launcher' side-bar.

  You used to get the option to open "Open a New Window" or "Open a New
  Tab" when you right clicked on the launcher icon.

  Now the only options are "Terminal", "Unlock from Launcher" and
  "Quit".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity 7.5.0+17.04.20170407.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  378.13  Tue Feb  7 20:10:06 
PST 2017
   GCC version:  gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  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
  Date: Mon Apr 10 18:44:46 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] 
[19da:7326]
  InstallationDate: Installed on 2017-03-04 (36 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Apr 10 18:43:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage 

[Desktop-packages] [Bug 1680111] Re: gnome-terminal does not start in unity8

2017-07-11 Thread md_5
Jeremy, the fix for this is the cause of 
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1681523
Can it please get another look at?

Thanks

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

Title:
  gnome-terminal does not start in unity8

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal does not start in unity8 in Ubuntu 17.04.

  gnome-terminal is an unusual app with a server and a client.

  It looks like errors.ubuntu.com is bundling the crash with some other
  issues.

  Here's one report:
  https://errors.ubuntu.com/oops/4645497a-19f9-11e7-88fb-fa163ef911dc

  As a workaround, for now I will probably set gnome-terminal to not
  show in the Unity 8 app launcher.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1680111/+subscriptions

-- 
Mailing list: https://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 1681523] Re: [Launcher] missing right click options

2017-07-11 Thread md_5
I take that back, commenting out the line in
/usr/share/applications/org.gnome.Terminal.desktop worked for me. Not
sure why there is /usr/share/applications/org.gnome.Terminal.desktop
and /usr/share/applications/gnome-terminal.desktop.

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

Title:
  [Launcher] missing right click options

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Running : 
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Not sure where to postthis but...

  Just noticed that "Right Click" options for the "Terminal" App are
  missing when it's locked to the 'Launcher' side-bar.

  You used to get the option to open "Open a New Window" or "Open a New
  Tab" when you right clicked on the launcher icon.

  Now the only options are "Terminal", "Unlock from Launcher" and
  "Quit".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity 7.5.0+17.04.20170407.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  378.13  Tue Feb  7 20:10:06 
PST 2017
   GCC version:  gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  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
  Date: Mon Apr 10 18:44:46 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] 
[19da:7326]
  InstallationDate: Installed on 2017-03-04 (36 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Apr 10 18:43:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1681523] Re: [Launcher] missing right click options

2017-07-01 Thread md_5
Workaround does not work for me either, nor did
https://askubuntu.com/questions/908201/how-to-restore-open-new-terminal-
by-right-click-in-unity.

Hoping for some insight on this *regression*

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

Title:
  [Launcher] missing right click options

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Running : 
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Not sure where to postthis but...

  Just noticed that "Right Click" options for the "Terminal" App are
  missing when it's locked to the 'Launcher' side-bar.

  You used to get the option to open "Open a New Window" or "Open a New
  Tab" when you right clicked on the launcher icon.

  Now the only options are "Terminal", "Unlock from Launcher" and
  "Quit".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity 7.5.0+17.04.20170407.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  378.13  Tue Feb  7 20:10:06 
PST 2017
   GCC version:  gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  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
  Date: Mon Apr 10 18:44:46 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] 
[19da:7326]
  InstallationDate: Installed on 2017-03-04 (36 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Apr 10 18:43:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1681523/+subscriptions

-- 

[Desktop-packages] [Bug 1681523] Re: [Launcher] missing right click options

2017-04-15 Thread md_5
Affects me too - very annoying!
Tried replacing the gnome-terminal.desktop file with the one from Yakkety, but 
that didn't help, so I'm out of ideas.
Other applications such as Firefox have their right click options just fine.

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

Title:
  [Launcher] missing right click options

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Running : 
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Not sure where to postthis but...

  Just noticed that "Right Click" options for the "Terminal" App are
  missing when it's locked to the 'Launcher' side-bar.

  You used to get the option to open "Open a New Window" or "Open a New
  Tab" when you right clicked on the launcher icon.

  Now the only options are "Terminal", "Unlock from Launcher" and
  "Quit".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity 7.5.0+17.04.20170407.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  378.13  Tue Feb  7 20:10:06 
PST 2017
   GCC version:  gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu3
  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
  Date: Mon Apr 10 18:44:46 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] 
[19da:7326]
  InstallationDate: Installed on 2017-03-04 (36 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Apr 10 18:43:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.

2016-10-10 Thread md_5
Forgot to add, I'm on Yakkety (up to date as of 10/10/16) and it is not
fixed.

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

Title:
  Software properties gtk implies my cpu is unknown and not working.

Status in software-properties package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  To reproduce install lubuntu 415 i386 on a t6500 core 2 duo cpu. I know I am 
installing 32 bit on 64 but it will show like in with both a braodcom 4322 
which I have not yet installed the prorpietary driver and this intel cpu. Open 
additional drivers from the menu in lxde. 
  software-properties-gtk:
Installed: 0.96.4
Candidate: 0.96.4
Version table:
   *** 0.96.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  https://gist.github.com/dabcbbc9bdcb7ed8d87d is the hardware tracker profile 
for this laptop. 

  I expected software-properties-gtk to not say my processor is unkown
  and not working because I have not installed the latest microcode.
  Instead it said this device which can use the proprietary intel
  microcode driver is unknown and not working and the only device this
  makes sense to be is the cpu.

  I have a screenshot attached of the messages that make no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: software-properties-gtk 0.96.4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic i686
  ApportVersion: 2.17.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Apr 15 13:11:51 2015
  InstallationDate: Installed on 2015-04-15 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta i386 (20150415)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions

-- 
Mailing list: https://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 1444682] Re: Software properties gtk implies my cpu is unknown and not working.

2016-10-10 Thread md_5
```
╰─$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd1184sv3842sd3778bc03sc00i00
model: GK104 [GeForce GTX 770]
vendor   : NVIDIA Corporation
driver   : nvidia-340 - distro non-free
driver   : nvidia-367 - distro non-free recommended
driver   : xserver-xorg-video-nouveau - distro free builtin

== cpu-microcode.py ==
driver   : intel-microcode - distro non-free
```

cpu-microcode needs to return model and vendor for usage in software-properties.
Both are available in /proc/cpuinfo which is already where cpu-microcode looks:
```
vendor_id   : GenuineIntel
model name  : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
```

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

Title:
  Software properties gtk implies my cpu is unknown and not working.

Status in software-properties package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  To reproduce install lubuntu 415 i386 on a t6500 core 2 duo cpu. I know I am 
installing 32 bit on 64 but it will show like in with both a braodcom 4322 
which I have not yet installed the prorpietary driver and this intel cpu. Open 
additional drivers from the menu in lxde. 
  software-properties-gtk:
Installed: 0.96.4
Candidate: 0.96.4
Version table:
   *** 0.96.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  https://gist.github.com/dabcbbc9bdcb7ed8d87d is the hardware tracker profile 
for this laptop. 

  I expected software-properties-gtk to not say my processor is unkown
  and not working because I have not installed the latest microcode.
  Instead it said this device which can use the proprietary intel
  microcode driver is unknown and not working and the only device this
  makes sense to be is the cpu.

  I have a screenshot attached of the messages that make no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: software-properties-gtk 0.96.4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic i686
  ApportVersion: 2.17.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Apr 15 13:11:51 2015
  InstallationDate: Installed on 2015-04-15 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta i386 (20150415)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions

-- 
Mailing list: https://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 1017630] Re: Inappropriate background scaling on newly-enabled monitor

2016-03-03 Thread md_5
Don't think this is a driver issue, I think Nautilus is failing to
handle resolution changes for display modes such as zoom.

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

Title:
  Inappropriate background scaling on newly-enabled monitor

Status in Unity:
  Invalid
Status in gnome-session package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When I enable my 1080p monitor via nvconfig or disper, the wallpaper
  image is fuzzy, and looks like a scaled-up version of the image on the
  existing 1366x768 monitor, even though the source image has greater
  resolution.  I've used the "The Forbidden City" wallpaper from Ubuntu
  Precise as an example.  It also occurs with my personal wallpapers.

  The problem can be fixed by re-selecting the same wallpaper.

  The attached images are crops of "The Forbidden City":
  "rescaled.png": The way the wallpaper image looks on my 1080p monitor 
immediately after enabling

  "orig-monitor.png": The way the wallpaper image looks on my 1366x768
  monitor

  "re-selected": The way the wallpaper image looks on my 1080p monitor
  after re-selecting it.  (i.e. the way it should look immediately after
  enabling)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1017630/+subscriptions

-- 
Mailing list: https://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 1094612] Re: Wallpaper not using "display mode" set by user

2016-03-03 Thread md_5
Having a semi-related issue whereby the wallpaper zoom after login is
different to the wallpaper zoom after just setting it.

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

Title:
  Wallpaper not using "display mode" set by user

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Architecture: amd64
  Version: 1.2.1-0ubuntu1.1
  Ubuntu 12.04

  LightDM for me uses the same wallpaper in the login and lock screens
  that I have set for my desktop. Lock screen wallpaper seems to look
  the same as my desktop wallpaper. However the login screen wallpaper
  does not use the same "display mode" as my desktop wallpaper.

  I have set my desktop wallpaper to "scale". But the login screen seems
  to use something else (it looks the same as when I choose "zoom" for
  the wallpaper). This is terrible news for the look of my login screen,
  because with "zoom", half the wallpaper doesn't show!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1094612/+subscriptions

-- 
Mailing list: https://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 935296] Re: java-atk-wrapper prevents java applications from starting

2015-11-02 Thread md_5
Just gonna link this ticket in here @samuel: 
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1510009
Seems that the ATK wrapper is causing issues for Java 8 in Wily.
Interestingly enough Java 7 is still disabled, referencing this bug:

# Doesn't work, see LP: #935296
#assistive_technologies=org.GNOME.Accessibility.AtkWrapper

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

Title:
  java-atk-wrapper prevents java applications from starting

Status in java-atk-wrapper package in Ubuntu:
  Fix Released
Status in openjdk-6 package in Ubuntu:
  Fix Released
Status in openjdk-7 package in Ubuntu:
  Fix Released
Status in java-atk-wrapper source package in Precise:
  Confirmed
Status in openjdk-6 source package in Precise:
  Triaged
Status in openjdk-7 source package in Precise:
  Triaged
Status in java-atk-wrapper package in Debian:
  Fix Released

Bug description:
  
  default java at command line is still java6.  invoke java from command line, 
and minecraft fails to start, usually with no 
  message, but there is some variety.  Most usual:

  charles@basquette:~/Desktop$ java -jar ./minecraft.jar

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to 
socket /tmp/dbus-oSohfHsLYR: Connection refused
  charles@basquette:~/Desktop$

  another case:

  charles@basquette:~/Desktop$ java -jar ./minecraft.jar

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to 
socket /tmp/dbus-oSohfHsLYR: Connection refused
  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  java: ../../src/xcb_io.c:273: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  Aborted (core dumped)
  charles@basquette:~/Desktop$ 

  another version, as suggested by:
  http://ubuntuforums.org/showthread.php?p=11696963

  is to invoke as root, yielding:

  root@basquette:/home/charles/Desktop# java -jar ./minecraft.jar

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  Gtk-WARNING **: Unable to locate theme engine in module_path:
  "pixmap",

  ** WARNING **: Unable to create Ubuntu Menu Proxy: The connection is
  closed

  ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to 
socket /tmp/dbus-oSohfHsLYR: Connection refused
  java.io.FileNotFoundException: /root/.minecraft/lastlogin (No such file or 
directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:137)
at net.minecraft.LoginForm.readUsername(LoginForm.java:131)
at net.minecraft.LoginForm.(LoginForm.java:76)
at net.minecraft.LauncherFrame.(LauncherFrame.java:30)
at net.minecraft.LauncherFrame.main(LauncherFrame.java:158)
at net.minecraft.MinecraftLauncher.main(MinecraftLauncher.java:13)
  ^Croot@basquette:/home/charles/Desktop# exit

  minecraft is stock .jar  unchanged for several weeks/months

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: openjdk-6-jre 6b24-1.11.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
  Uname: Linux 3.2.0-16-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sat Feb 18 09:39:32 2012
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openjdk-6
  UpgradeStatus: Upgraded to precise on 2012-01-15 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/935296/+subscriptions

-- 
Mailing list: https://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 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

2015-08-01 Thread md_5
Confirmed in 15.04

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

Status in File Roller:
  New
Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy file-roller
  file-roller:
Installed: 3.12.2-0ubuntu1
Candidate: 3.12.2-0ubuntu1
Version table:
   *** 3.12.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens a tarball with file-
  roller, and without extracting the file, open it (ex. open PDF file
  with evince) the file-roller utilizes /tmp for this.

  4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , 
where * is a changing folder name. If one logs out, or kills the file-roller 
process via:
  kill PID

  the temp files are left behind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions

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