from:"kyle"

[Desktop-packages] [Bug 1989826] [NEW] cannot start lightdm gui

2022-09-15 Thread Kyle Yannis M Estrada

Public bug reported:

i installed lightdm but cannot start it manually
using ubuntu 22.04.1 LTS
release 22.04
codename: jammy

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lightdm 1.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
Date: Fri Sep 16 01:27:20 2022
InstallationDate: Installed on 2022-08-28 (18 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  cannot start lightdm gui

Status in lightdm package in Ubuntu:
  New

Bug description:
  i installed lightdm but cannot start it manually
  using ubuntu 22.04.1 LTS
  release 22.04
  codename: jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: lightdm 1.30.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  Date: Fri Sep 16 01:27:20 2022
  InstallationDate: Installed on 2022-08-28 (18 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1989826/+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 1984031] [NEW] The username 'at' cannot list on logon screen

2022-08-08 Thread Kyle Cheng

Public bug reported:


OS: Ubuntu 20.04.x LTS (Desktop)

Problem description:
When I try to use 'at' as my username, after rebooting, gnome-initial-setup 
reappears and asks to create a new user.

Re-produce procedures (1):
1. Del all other users from terminal
2. Reboot to OS.
3. Add a user by gnome-initial-setup dialog.
4. Use 'at' as username and login name.
5. After setup finish, reboot.
6. When boot to OS, gnome-initial-setup will pop again for asking create a new 
user.

Re-produce procedures (2):
1. Create a user (e.g. username is 'user')
2. Check this user account can be showed on the logon screen and can login into 
OS.
3. Logout 'user' account and swith to terminal to modify the account with root 
permission. 
4. Modify account 'user' to 'at'
5. After finish, reboot
6. When boot to OS, gnome-initial-setup will pop again for asking create a new 
user.
7. At this moment, switch to terminal with root permission
8. Modify account 'at' to 'am' and reboot
9. After boot to OS, gnome-initial-setup doesn't pop up and account 'am' is 
showed on logon screen.

Is this a bug or 'at' is a reserved word? I can't find any document
relevant about this restriction.

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


** Tags: gdm3 logon username

** Summary changed:

- Some username cannot list on logon screen
+ The username 'at' cannot list on logon screen

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

Title:
  The username 'at' cannot list on logon screen

Status in gdm3 package in Ubuntu:
  New

Bug description:
  
  OS: Ubuntu 20.04.x LTS (Desktop)

  Problem description:
  When I try to use 'at' as my username, after rebooting, gnome-initial-setup 
  reappears and asks to create a new user.

  Re-produce procedures (1):
  1. Del all other users from terminal
  2. Reboot to OS.
  3. Add a user by gnome-initial-setup dialog.
  4. Use 'at' as username and login name.
  5. After setup finish, reboot.
  6. When boot to OS, gnome-initial-setup will pop again for asking create a 
new user.

  Re-produce procedures (2):
  1. Create a user (e.g. username is 'user')
  2. Check this user account can be showed on the logon screen and can login 
into OS.
  3. Logout 'user' account and swith to terminal to modify the account with 
root permission. 
  4. Modify account 'user' to 'at'
  5. After finish, reboot
  6. When boot to OS, gnome-initial-setup will pop again for asking create a 
new user.
  7. At this moment, switch to terminal with root permission
  8. Modify account 'at' to 'am' and reboot
  9. After boot to OS, gnome-initial-setup doesn't pop up and account 'am' is 
showed on logon screen.

  Is this a bug or 'at' is a reserved word? I can't find any document
  relevant about this restriction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1984031/+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 1980975] [NEW] Rubbish Bin Context Menu references wrong name

2022-07-07 Thread Kyle Pantall

Public bug reported:

When right clicking the rubbish bin in the file explorer or dock, the
context menu says "Empty wastebasket". This is an inconsistent reference
as it is now referred to as Rubbish Bin across the Ubuntu OS.

Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
describes "Delete all items in the Rubbish Bin".

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2022-07-07 17-42-53.png"
   
https://bugs.launchpad.net/bugs/1980975/+attachment/5601876/+files/Screenshot%20from%202022-07-07%2017-42-53.png

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

Title:
  Rubbish Bin Context Menu references wrong name

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  When right clicking the rubbish bin in the file explorer or dock, the
  context menu says "Empty wastebasket". This is an inconsistent
  reference as it is now referred to as Rubbish Bin across the Ubuntu
  OS.

  Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
  describes "Delete all items in the Rubbish Bin".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1980975/+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 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)

2022-03-07 Thread kyle

This issue affects me, too.  Ubuntu mate 20.04 with Nvidia Quadro P2200
Graphics card.  Please fix for the Mate desktop.

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

Title:
  present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA
  495.46)

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xorg-server source package in Focal:
  Confirmed
Status in xorg-server source package in Impish:
  Confirmed

Bug description:
  This bug causes xserver to crash when using newer Nvidia drivers
  (NVIDIA 495.46+) with Optimus. It's apparently triggered when using
  the MATE desktop environment. It has been noticed on xorg-server-21.1,
  but it's likely affecting version 1.20.13 as well.

  It has been fixed already, but could you please backport the fix?

  Patch that fixes it is here:
  
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c

  The bug report at freedesktop.org is here:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1959995/+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 1944087] [NEW] Login loop after adding authenticated smb share to nautilus

2021-09-19 Thread Kyle

Public bug reported:

Steps to reproduce:

Connect to authenticated smb share in nautilus
"remember password until you log out"
Bookmark the shared folder in the left panel
Logout

You will now be unable to log in.

Workaround:
Log in using wayland
unbookmark the smb share
logout
go back to default desktop environment
login

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 19 12:30:33 2021
GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1187, 
757)'
InstallationDate: Installed on 2021-09-16 (3 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

** Description changed:

  Steps to reproduce:
  
  Connect to authenticated smb share in nautilus
  "remember password until you log out"
  Bookmark the shared folder in the left panel
  Logout
  
  You will now be unable to log in.
+ 
+ Workaround:
+ Log in using wayland
+ unbookmark the smb share
+ logout
+ go back to default desktop environment
+ login
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 19 12:30:33 2021
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1187, 
757)'
  InstallationDate: Installed on 2021-09-16 (3 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

Title:
  Login loop after adding authenticated smb share to nautilus

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  Connect to authenticated smb share in nautilus
  "remember password until you log out"
  Bookmark the shared folder in the left panel
  Logout

  You will now be unable to log in.

  Workaround:
  Log in using wayland
  unbookmark the smb share
  logout
  go back to default desktop environment
  login

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 19 12:30:33 2021
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1187, 
757)'
  InstallationDate: Installed on 2021-09-16 (3 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944087/+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 1943137] [NEW] Mouse is connected however input does not move cursor

2021-09-09 Thread kyle g

Public bug reported:

I have two mice each with their own dongle.  1 is the microsoft sculpt
keyboard mouse combo and the other is a logitech master2 (using dongle
not bluetooth).  Both of the mice work while in the login screen but
once you log in neither will control the cursor.

I know they are connected because:
- keyboard works for the microsoft sculpt
- the logitech mouse is detected by the solar app i use to configure it.
- they both work during login

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.57.02  Tue Jul 13 16:14:05 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  9 09:19:31 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 470.57.02, 5.11.0-27-generic, x86_64: installed
 nvidia, 470.57.02, 5.11.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Device [1028:098f]
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:098f]
InstallationDate: Installed on 2021-03-25 (167 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. XPS 17 9700
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=1cef9c97-5ee0-47f7-aa9e-da9d48059d31 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2021
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd05/21/2021:br1.8:svnDellInc.:pnXPS179700:pvr:sku098F:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  Mouse is connected however input does not move cursor

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two mice each with their own dongle.  1 is the microsoft sculpt
  keyboard mouse combo and the other is a logitech master2 (using dongle
  not bluetooth).  Both of the mice work while in the login screen but
  once you log in neither will control the cursor.

  I know they are connected because:
  - keyboard works for the microsoft sculpt
  - the logitech mouse is detected by the solar app i use to configure it.
  - they both work during login

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""

[Desktop-packages] [Bug 1884437] Re: Windows are resized and reordered upon resume from lock or suspend

2020-06-22 Thread Kyle Weber

It's still doing it with the same process ID. I switched DP cables--
perhaps it's a bad port on the board or display... I'll look into it
further. Thanks for your assistance!

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

Title:
  Windows are resized and reordered upon resume from lock or suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After a resume from a lock/suspend, windows sizes are changed, fonts
  are incorrect sizes (until mouse over), and windows have moved from
  the secondary monitor to the primary monitor. This happens every time
  the displays have been off (from a suspend or lock screen). AMD
  graphics with dual 4K displays.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 07:46:41 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed
   asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed
   asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon 
RX Vega 56/64] [1462:3680]
  InstallationDate: Installed on 2020-03-07 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5406
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884437/+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 1884437] [NEW] Windows are resized and reordered upon resume from lock or suspend

2020-06-21 Thread Kyle Weber

Public bug reported:

After a resume from a lock/suspend, windows sizes are changed, fonts are
incorrect sizes (until mouse over), and windows have moved from the
secondary monitor to the primary monitor. This happens every time the
displays have been off (from a suspend or lock screen). AMD graphics
with dual 4K displays.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 21 07:46:41 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed
 asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed
 asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon RX 
Vega 56/64] [1462:3680]
InstallationDate: Installed on 2020-03-07 (105 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5406
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X470-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Windows are resized and reordered upon resume from lock or suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  After a resume from a lock/suspend, windows sizes are changed, fonts
  are incorrect sizes (until mouse over), and windows have moved from
  the secondary monitor to the primary monitor. This happens every time
  the displays have been off (from a suspend or lock screen). AMD
  graphics with dual 4K displays.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 07:46:41 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed
   asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed
   asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c1)

[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen

2020-05-04 Thread Kyle Weber

This happens to me as well. I too have two monitors, and sometimes the
menu is even on the wrong monitor. Oddly enough, if I click off then
right-click again (right away), the menu appears correctly. It's almost
as if it is triggered by not being invoked after x amount of time.

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

Title:
  Menus, tooltips and dropdowns are often misplaced on screen

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I've noticed a few problems with misplaced elements in firefox UI that
  I am not sure are all the same bug:

  - In what appears to be random chance tooltips and menus are often misplaced 
on screen. It's common but not fully reproducible. What I see is right-clicking 
an element on a page or hovering over a link and having the menu/tooltip show 
up somewhere different on the page. Doing it again immediately after often 
results in it appearing in the right place the second time.
  - When using an external screen placed on top of the internal one with 
firefox maximized on the internal screen the URL bar's dropdown would 
consistently appear on the external screen, completely outside the firefox 
window, instead of the normal location

  Let me know what extra information is needed do diagnose this. I'm
  running gnome-shell and have used both Xorg and Wayland sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2259 F pulseaudio
  BuildID: 20180703115938
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 15:00:50 2018
  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 2018-05-31 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 
600 
   169.254.0.0/16 dev tun0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1780790/+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 1868896] Re: Minimized windows reappear when closing the overview

2020-03-25 Thread Kyle Weber

Thanks for your quick response on this! So awesome!

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868896/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2019-12-14 Thread Kyle Van Wagenen

This issue impacts the experience with Ubuntu significantly. Android,
Windows, and OS X all sound much better with a Bluetooth headset when on
calls, playing games, or listening to music while using the headset
microphone.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

2019-12-14 Thread Martin Kyle

Had a panic moment when it appeared my i1pro meter had stopped working.
It seems I had not used it since upgrading to 18.04.LTS when I started
having problems with this issue. As I plugged the unit in gnome-control-
center opens at the device colour profile page. When I open a terminal
and try to use chartread I get:

etc

or with chartread -D I get:

Read Target Test Chart, Version 2.0.0
Author: Graeme W. Gill, licensed under the AGPL Version 3
usage: chartread [-options] outfile
-v Verbose mode
-c listno Set communication port from the following list (default 1)
Argyll 'V2.0.0' Build 'Linux 64 bit' System 'Linux #81-Ubuntu SMP Tue Nov 26
12:20:02 UTC 2019 4.15.0-72-generic x86_64'
usb_check_and_add: failed to open '/dev/bus/usb/004/025'
** No ports found **

As a last resort I uninstalled gnome-control-center with synaptic and
the device (after unplug and plug in) is available again to chartread -D
:

I re-installed and it's back to no-go. It's as though gnome-control-center is
grabbing the device and not allowing access even when the window is closed.

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

Title:
Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

Status in gnome-control-center package in Ubuntu:
New

Bug description:
I've been trying to calibrate my printer in Ubuntu 18.04.3LTS with
gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.5
Candidate: 1:3.28.2-0ubuntu0.18.04.5
Version table:
*** 1:3.28.2-0ubuntu0.18.04.5 500

The least documented part of printer profiling is printing the target. Every
guide says turn off printer profile calibration, but no-one tells you how.
Through trial, error and a lot of paper and ink it seems to me as though the
on / off button next to the printer description does nothing.
If the user deletes all existing profiles the field reads Not calibrated and
no button is displayed, though on a reboot this changes to a button showing
colour management (CMS) on and two default profiles are displayed (default RGB
and default grey) with RGB selected. The output of these two states is
identical. If the setting is default RGB profile with no others loaded, then
changing Cups in a browser to Colour Correction: uncorrected refreshes the
state to Not Calibrated, though this is the only time I could force this.
Setting Cups to Colour Correction: high accuracy does result in an altered
output from the printer. I am guessing this is no colour profiling being
applied.
However if Cups Colour Correction: uncorrected is set, and a profile is
loaded in Device Colour Profiles the output from the printer is the same
whether or not the CMS on /off button is pressed. I think this is the result of
the profile applied by Device Colour Profiles in either case.
Similarly, using Cups Colour Correction: High Accuracy and a profile loaded
in Device Colour Profiles, the printer output is the same whether or not the
CMS on /off button is pressed, though the output is different from the
preceding example. I presume this is the result of two colour transformations
being carried out.
The attached images of my printer output should hopefully help explain this
situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+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 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

2019-12-14 Thread Martin Kyle

etc

or with chartread -D I get:

As a last resort I uninstalled gnome-control-center with synaptic and
the device is available again to chartread -D :

I re-installed and it's back to no-go. It's as though gnome-control-center is
grabbing the device and not allowing access even when the window is closed.

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

Title:
Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

Status in gnome-control-center package in Ubuntu:
New

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

[Desktop-packages] [Bug 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

2019-12-14 Thread Martin Kyle

Ok, so I was looking for an option like that but could not find it in
any documentation. Just to add I was printing .ps targets from Argyll's
targen / printarg / chartread / colprof workflow with:

lp target.ps

I did some more test prints and have attached the results again.

The -o cm-calibration=1 option does seem to turn off calibration from
"Device Colour Profiles" but the "color correction setting" in CUPS
still has an effect on print output, quite noticeable on a couple of
targets which go from orange to purple.

I am going to create two profiles from targets printed with the -o cm-
calibration=1 option with:

a). Device Colour Profiles cms ON and a profile loaded, but Cups
colour correction set to High Accuracy.

b). Device Colour Profiles cms ON and a profile loaded, but Cups
colour correction set to Uncorrected.

Hopefully I will then be able to asses the best way forward.

** Attachment added: "printer output and screenshots"

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+attachment/5312322/+files/printer%20output%20pictures%202.zip

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

Title:
Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

Status in gnome-control-center package in Ubuntu:
New

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

[Desktop-packages] [Bug 1855615] [NEW] Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

2019-12-08 Thread Martin Kyle

Public bug reported:

I've been trying to calibrate my printer in Ubuntu 18.04.3LTS with
gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.5
Candidate: 1:3.28.2-0ubuntu0.18.04.5
Version table:
*** 1:3.28.2-0ubuntu0.18.04.5 500

The least documented part of printer profiling is printing the target. Every
guide says turn off printer profile calibration, but no-one tells you how.
Through trial, error and a lot of paper and ink it seems to me as though the on
/ off button next to the printer description does nothing.
If the user deletes all existing profiles the field reads Not calibrated and no
button is displayed, though on a reboot this changes to a button showing colour
management (CMS) on and two default profiles are displayed (default RGB and
default grey) with RGB selected. The output of these two states is identical.
If the setting is default RGB profile with no others loaded, then changing Cups
in a browser to Colour Correction: uncorrected refreshes the state to Not
Calibrated, though this is the only time I could force this. Setting Cups to
Colour Correction: high accuracy does result in an altered output from the
printer. I am guessing this is no colour profiling being applied.
However if Cups Colour Correction: uncorrected is set, and a profile is loaded
in Device Colour Profiles the output from the printer is the same whether or
not the CMS on /off button is pressed. I think this is the result of the
profile applied by Device Colour Profiles in either case.
Similarly, using Cups Colour Correction: High Accuracy and a profile loaded in
Device Colour Profiles, the printer output is the same whether or not the CMS
on /off button is pressed, though the output is different from the preceding
example. I presume this is the result of two colour transformations being
carried out.
The attached images of my printer output should hopefully help explain this
situation.

** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "A series of jpgs showing the process"

https://bugs.launchpad.net/bugs/1855615/+attachment/5310861/+files/printer%20output%20pictures.zip

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

Title:
Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

Status in gnome-control-center package in Ubuntu:
New

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

[Desktop-packages] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache

2019-03-13 Thread Kyle Brenneman

I just tagged a 1.1.1 release for libglvnd with the AARCH64 and PPC64LE fixes:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.1

If you're switching from 1.0.0, note that the dispatch table order
changed between v1.0.0 and v1.1.0, so you'll need matching builds of
libGLdispatch.so, libOpenGL.so, libGL.so, and the libGLES*.so libraries.

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

Title:
  GLVND: AARCH64 : Fix address passed to clear cache

Status in libglvnd package in Ubuntu:
  New

Bug description:
  [Impact]

  A new fix has been merged to NVIDIA libglvnd repo at 
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
  We need to include it in bionic.
  It would be ok to just include this fix even without updating to the latest 
glvnd version.

  This change fixes a crash seen in some GLX apps while calling
  glXGetProcAddress.

  Source Package :
  https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2

  Can we get this fix merged in current LTS 18.04 as "-updates"

  [Test app]

  To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
  And run a small test app with this piece of code.
  void *handle = dlopen("libGLX.so.0", 2);
  glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle, 
"glXGetProcAddressARB");
  glXGetProcAddressARB("glXAllocateMemoryMESA");

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2019-01-04 Thread Kyle Weber

Mine does EVERYTHING EXACTLY as you just mentioned.

Sent from my iPhone

> On Jan 4, 2019, at 3:25 AM, Benjamin Schmid <1748...@bugs.launchpad.net> 
> wrote:
> 
> @vanvugt Seeing this VERY regularly in cosmic, too. Just came back here
> to re-check the status of this long-term annoying issue.
> 
> The fact is, that gnome shell provides me a VERY poor UX experience:
> 
> Logged out for the session more than 10mins? Type your password and go
> get take a coffee, because it literally takes 1-2 minutes until the
> session finally crashes and restarts. Before my PC it literally
> unusable. Sometimes I also switch to the login screen and re-login into
> my running session to somehow provoke the crash to get it usable.
> 
> Ah – and by the way: On some occassions lockscreen does not work and
> expose the clickable (!) left sidebar. In this case I only can unlock
> via the login-screen way to crash the session.
> 
> Also commonly in normal operation the left sidebar looks strangely
> sized. Then I need to type "r" to restart the shell to resume normal
> operation.
> 
> Feels really like an old, nearly dying device …
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1755163).
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Invalid
> Status in mutter package in Ubuntu:
>  Fix Released
> Status in gnome-shell source package in Bionic:
>  Invalid
> Status in mutter source package in Bionic:
>  Fix Released
> 
> Bug description:
>  [Impact]
> 
>  * Xwayland is failing frequently (not crashing), which triggers a
>  crash in gnome-shell because gnome-shell doesn't know how to survive
>  after Xwayland has reset itself.
> 
>  * The frequent gnome-shell crashes create frequent problem reports and
>  annoying dialogs for users, after they log in to an apparently working
>  gnome-shell.
> 
>  * This affects Xorg sessions too, because the gdm login screen itself
>  is a Wayland session. And Xorg users will see the problem dialog after
>  they have logged into a Xorg session.
> 
>  * The fix simply converts the crash into a silent exit (as decided by
>  Gnome upstream). This avoids the mountain of crash reports and
>  annoying error dialogs at least. It does not fix the root causes that
>  remain in Xwayland, but this is considered acceptable because there
>  really isn't a bug in gnome-shell here other than it doesn't know how
>  to survive without a connection to Xwayland.
> 
>  * For users of Xorg sessions, like bionic default, this is a full fix
>  as Xorg users will never get an Xwayland instance after logging in.
>  And hence the Xwayland bugs are irrelevant.
> 
>  [Test Case]
> 
>  * Just install bionic, use it lightly and reboot a few times.
> 
>  * Observe crash files are left in /var/crash and problem report
>  dialogs after logging in.
> 
>  [Regression Potential]
> 
>  Medium. The fix does not really change the structure of the existing
>  error handling, only changes it from a core dump into a silent exit.
>  For Xorg users this should be invisible as the affected login screen
>  restarts automatically.
> 
>  [Other Info]
> 
>  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
> 1748450 and bug 1556601. All three should be considered the same crash for 
> the sake of this SRU. Just don't mark them as duplicates of each other
>  because they are all still collecting duplicates of their own.
> 
>  -
> 
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at

Re: [Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-25 Thread Kyle Weber

I didn’t need to remove GDM3, but installing LightDM (and switching to
it) fixed it for me. Well, I should say it was a workaround, anyway...

> On Oct 24, 2018, at 11:56 PM, ccdisle  wrote:
> 
> Uncommenting "WaylandEnable=false " worked.
> 
> Removing gdm3 did not work, I just got redirected to a tty3 login shell.
> 
> Thanks again
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1752053
> 
> Title:
>  nvidia-390 fails to boot graphical display
> 
> Status in mesa package in Ubuntu:
>  Fix Released
> Status in nvidia-graphics-drivers-390 package in Ubuntu:
>  Fix Released
> Status in xserver-xorg-video-nouveau package in Ubuntu:
>  Invalid
> 
> Bug description:
>  I'm using Bionic with the new 4.15 kernel. I've been using the
>  nvidia-384 driver with no problem for a while.  Today I issued "sudo
>  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
>  the nvidia-390.  After installing the driver and rebooting, I was only
>  able to boot in to the tty terminal.  The graphical display failed to
>  boot.  I have had similar problems with nvidia driver version 390 with
>  Arch Linux and with Open Suse Tumbleweed.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 639608] Re: manual duplex printing missing

2018-09-29 Thread Anne Kyle

I've actually gotten rid of both that printer and that laptop since then so
I'm afraid I can't help! Sorry!

Anne

On Sat 29 Sep 2018 at 18:01, gf <639...@bugs.launchpad.net> wrote:

> Hello Ann and Carsten,
> Thank you for reporting this bug and describing a problem with
> system-config-printer.  You made this bug report in 2010 and Ubuntu has
> been updated since then.
>
> Could you confirm that this is no longer a problem and that we can close
> the bug report?
> If it is still a problem, are you still interested in finding a solution
> to this bug?
> If you are, could you let us know, and in the current version, run the
> following (only once):
> apport-collect BUGNUMBER
> and upload the updated logs and and any other logs that are relevant for
> this particular issue.
>
> Thank you again for helping make Ubuntu better.
> G
> [Ubuntu Bug Squad volunteer triager]
>
> ** Changed in: gtk (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: system-config-printer (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: hplip (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/639608
>
> Title:
>   manual duplex printing missing
>
> Status in gtk package in Ubuntu:
>   Incomplete
> Status in hplip package in Ubuntu:
>   Incomplete
> Status in system-config-printer package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Binary package hint: hplip
>
>   I have problem with 'manual duplex' printing on my HP CP1514n in Ubuntu.
>   In 10.04 I select the double sided print option (print long edge). Print
> is now simplex printing, which is wrong.
>   In 10.10beta there is a new option checkbox : Duplexer installed.
> Because I don't have a duplexer attached to my printer, I  deselect this
> option. But then I cannot select double sided printing any more.
>   What to do?
>   I want first to print the even pages, then I want to place the printed
> stack (even pages) in the printer tray.
>   When I at last acknowledge with the OK printer button, the printer shall
> print the odd pages in the correct order on the opposite side of the even
> pages.
>   This works perfectly in Windows. Ubuntu (Linux) must have the same
> functionality!
>   I believe a lot of people have the same problem!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gtk/+bug/639608/+subscriptions
>
-- 
Sent from my iPhone

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

Title:
  manual duplex printing missing

Status in gtk package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: hplip

  I have problem with 'manual duplex' printing on my HP CP1514n in Ubuntu.
  In 10.04 I select the double sided print option (print long edge). Print is 
now simplex printing, which is wrong.
  In 10.10beta there is a new option checkbox : Duplexer installed. Because I 
don't have a duplexer attached to my printer, I  deselect this option. But then 
I cannot select double sided printing any more.
  What to do?
  I want first to print the even pages, then I want to place the printed stack 
(even pages) in the printer tray.
  When I at last acknowledge with the OK printer button, the printer shall 
print the odd pages in the correct order on the opposite side of the even pages.
  This works perfectly in Windows. Ubuntu (Linux) must have the same 
functionality!
  I believe a lot of people have the same problem!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk/+bug/639608/+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 1738164] Re: [snap] U2F doesn't work with yubikey

2018-09-19 Thread Kyle Fazzari

jdstrand, I've added those rules, and the denials go away, but I'm
afraid it still doesn't work. There doesn't seem to be any denials, but
it's like chrome just doesn't see it.

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+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 1782285] Re: Add missing libGLESv1_CM.so to Bionic

2018-08-14 Thread Kyle Brenneman

The actual release tag (plus tarball and release notes) is here:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.0

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

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  New

Bug description:
  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+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 1782285] Re: Add missing libGLESv1_CM.so to Bionic

2018-08-10 Thread Kyle Brenneman

The other libglvnd libraries would already cause a conflict with
nvidia-340, wouldn't they?

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

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  New

Bug description:
  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+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 1780039] Re: Khronos CTS failure on Bionic due to missing change in libegl1

2018-08-09 Thread Kyle Brenneman

Liblgnvd has a new 1.1.0 point release, which includes that fix (as well
as an assortment of others).

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

Title:
  Khronos CTS failure on Bionic due to missing change in libegl1

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  Currently Bionic contains 1.0.0-2ubuntu2 version of libegl1.

  There is a bug in libEGL.so.1 due to which a Khronos CTS failure
  happens on ARM platform.

  Cosmic has already upgraded to 1.0.0+git20180308-3ubuntu1 version of
  libegl1 where this bug is fixed.

  Details of fix in liglvnd-EGL code: 
https://github.com/NVIDIA/libglvnd/issues/151
  Failing Khronos CTS test: dEQP-EGL.functional.negative_api.make_current, 
which runs in bot OpenGL and OpenGL-ES CTS runs.

  Without above test passing, we can't submit logs to Khronos for the
  CTS run.

  Filing this bug to get libegl1 upgraded to cosmic's version in bionic repos.
  We've verified locally on ARM platform, there are no issues present due to 
this upgrade.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1780039/+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 1782285] Re: Add missing libGLESv1_CM.so to Bionic

2018-08-08 Thread Kyle Brenneman

Also, while GLESv1 is the fixed-pipeline stuff, libGLESv1_CM.so just
provides a set of forwarder functions. Libglvnd forwards those calls to
a vendor library based on the current context, so it's up to the vendor
library what to do with them. If a vendor doesn't provide a function to
forward to, then libglvnd sends the function to an error or no-op stub
(the same way it would handle calling a function without a current
context at all).

For something like GLESv1, if a vendor library doesnt't support it, then
it would just return NULL from its eglCreateConext or
glXCreateContextAttribsARB implementation. At that point, the vendor
library doesn't need to implement any of the GLESv1 functions -- trying
to call a GLESv1 function without a current GLESv1 context is an
application error.

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

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  Confirmed
Status in libglvnd source package in Bionic:
  New

Bug description:
  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+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 1782285] Re: Add missing libGLESv1_CM.so to Bionic

2018-08-07 Thread Kyle Brenneman

Just because Mesa doesn't provide GLESv1 doesn't mean other vendor
libraries can't. It certainly isn't any reason to prohibit GLESv1
support if a vendor library would otherwise be able to support it.

Conversely, having the full set of libglvnd libraries (including
libGLESv1_CM.so) doesn't require vendors to support every flavor of
OpenGL.

If you remove libGLESv1_CM.so, then any driver that does support GLESv1
would have to install its own copy of that library. Two drivers that
support GLESv1 would then end up overwriting each other or playing
symlink games to switch between them. The whole point of libglvnd is to
avoid that.

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

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+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 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

2018-07-27 Thread Jim Kyle

s/metter/better/!!!

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

2018-07-27 Thread Jim Kyle

I've encountered this bug on the past TWO kernel updates of my Xubuntu
16.04.4 (now .5) system that uses an Nvidia card. Initially I found that
falling back to the previous kernel was a satisfactory workaround. This
morning, I tried using the "Additional drivers" system setting to change
from the Nvidia driver to the noveau driver -- and that has worked
perfectly so far. This might be a possible recommended solution. I had
originally switched from noveau to the proprietary driver because noveau
didn't work properly, but that was several years ago and it has
obviously gotten much metter!

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-13 Thread Kyle Weber

I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I
purged the nvidia drivers, installed 396 through the PPA, rebooted, and
it came up and worked. It is a tower with GTX 1060.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-08 Thread Kyle Weber

I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to
give up on Ubuntu and give that a try. Some word of reassurance from the
Ubuntu team here would be nice. Where they marked this as fixed, I'm not
hopeful of a fix--at least anytime soon. If anyone has found a true and
simple workaround, please let us know! Otherwise, I think my hardware
will require me to look somewhere else...

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768388] [NEW] "Open Tilix Here" still in context menu after uninstalling Tilix

2018-05-01 Thread Kyle Piira

Public bug reported:

On Ubuntu Budgie there is an option in the context menu in GNOME Files
to "Open Tilix Here" which will open that directory in the Tilix
terminal emulator. However, after uninstalling Tilix the option still
appears but now does nothing (since its trying to open a program that
doesn't exist on the system anymore). There should be a check somewhere
to verify that Tilix is actually installed before showing the option.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Tue May  1 22:07:57 2018
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: budgie-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Package changed: gnome-terminal (Ubuntu) => budgie-desktop (Ubuntu)

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

Title:
  "Open Tilix Here" still in context menu after uninstalling Tilix

Status in budgie-desktop package in Ubuntu:
  New

Bug description:
  On Ubuntu Budgie there is an option in the context menu in GNOME Files
  to "Open Tilix Here" which will open that directory in the Tilix
  terminal emulator. However, after uninstalling Tilix the option still
  appears but now does nothing (since its trying to open a program that
  doesn't exist on the system anymore). There should be a check
  somewhere to verify that Tilix is actually installed before showing
  the option.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue May  1 22:07:57 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768388/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-01 Thread Kyle Weber

At the top of this page it says "Fix Released". Does anyone know to to
get them to change the status to an open bug and re-evaluate it? It's
clearly not fixed.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-30 Thread Kyle Weber

Hopeful this bug was fixed (as it improperly states above), I did a
fresh install on my machine with an Nvidia 1060. It will boot, then go
to a black screen on login, etc. I tried what people mentioned above,
but was not able to get a stable working system. I went back to 17.10
and have not had any issues since.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts

2018-04-19 Thread Michael Kyle

I found a solution on stackoverflow thanks to @kbenoit there.

https://askubuntu.com/questions/117899/configure-networkmanagers-
dnsmasq-to-use-etc-hosts

This is not really a bug at all. You just have to configure stuff under
/etc/NetworkManager/dnsmasq.d instead, e.g.,

# echo "addn-hosts=/etc/hosts" > /etc/NetworkManager/dnsmasq.d/hosts.conf
# service network-manager restart

I will point out the following statement from the networkmanager.conf
man page ON THE GNOME WEBSITE (not on the ubuntu 16.04 man page):

It is possible to pass custom options to the dnsmasq instance by adding
them to files in the "/etc/NetworkManager/dnsmasq.d/" directory.

Add any options you want.

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

Title:
Please make NetworkManager-controlled dnsmasq respect /etc/hosts

Status in network-manager package in Ubuntu:
Confirmed

Bug description:
Since 12.04 NetworkManager uses the dnsmasq plugin by default to
resolve DNS requests. Unfortunately the dnsmasq plug-in has --no-
hosts, etc. hard coded [1] which means (among other things) that after
the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS
requests. This changes the prior behavior of NetworkManager without
any visible warning to the end user. AFAICS there's no other way to
work around this problem as to manually revert the change and disable
the dnsmasq plug-in in the NetworkManager config, see [2,3]:

"To turn off dnsmasq in Network Manager, you need to edit
/etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq'
line then do a 'sudo restart network-manager'."

This is of course not a bug in the NetworkManager which just behaves
as intended. The problem is in the change of the configuration of the
Ubuntu packaging which will probably leave many wondering why their
/etc/hosts suddenly no longer works. This cost me considerable time to
debug and probably is a usability problem for others, too.

Maybe you could provide a more visible documentation than that in [3]?
E.g., *including a comment in /etc/hosts that explains the change* and
how to work around it would have saved me a lot of time. It would have
automatically alerted me on upgrade as manual changes to /etc/hosts
would then have triggered a prompt while leaving those users with
standard /etc/hosts in peace.

Probably similar problems arise with other disabled config files and
could be alerted to the users? Thinking of resolv.conf, etc.

[1]
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c,
line 285
[2] i.e. http://ubuntuforums.org/showthread.php?t=1968061
[3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993298/+subscriptions

[Desktop-packages] [Bug 1760966] [NEW] Cannot modify group members of existing group containing underscore.

2018-04-03 Thread Kyle Horodyski

Public bug reported:

I have 2 user accounts on my system:
  1: user
  2: user_name

I want to add them to each other's groups so that by default they can
always modify each others files.

When trying to modify group "user_name"'s properties in the users admin
application, clicking OK gives me a popup window with the message:

"Group name has invalid characters 
Please set a valid group name consisting of a lower case letter followed by 
lower case letters and numbers.".

As the group name already exists and can't be changed from its
properties window this seems like a contradiction.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-system-tools 3.0.0-4ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98
Uname: Linux 4.4.0-116-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: LXDE
Date: Tue Apr  3 14:58:25 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/users-admin
InstallationDate: Installed on 2018-03-04 (30 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-system-tools (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 gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1760966

Title:
  Cannot modify group members of existing group containing underscore.

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  I have 2 user accounts on my system:
1: user
2: user_name

  I want to add them to each other's groups so that by default they can
  always modify each others files.

  When trying to modify group "user_name"'s properties in the users
  admin application, clicking OK gives me a popup window with the
  message:

  "Group name has invalid characters 
  Please set a valid group name consisting of a lower case letter followed by 
lower case letters and numbers.".

  As the group name already exists and can't be changed from its
  properties window this seems like a contradiction.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-tools 3.0.0-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98
  Uname: Linux 4.4.0-116-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr  3 14:58:25 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/users-admin
  InstallationDate: Installed on 2018-03-04 (30 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1760966/+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 1754744] [NEW] Launching any electron app crashes Xorg

2018-03-09 Thread Kyle Fazzari

Public bug reported:

If I dare to launch any electron-based app (chrome, spotify, atom,
vscode, etc.) there's roughly an 80% chance that it kills X (bringing me
back to the login screen). This doesn't _always_ happen. Note that I
have a 4k laptop, with a 4k external screen. Things seem to have a
better chance of succeeding if I disconnect the external display before
launching the electron app. Once it launches successfully things seem to
be stable, even after re-connecting the external display.

I SSHd into this machine from another, and connected to X from gdb, then
opened vscode to cause the crash. Here is the backtrace I got from that
session (this is easy to reproduce, happy to provide any requested
info):

root@Pandora:~# gdb /usr/bin/Xorg $(pidof Xorg)
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/Xorg": not in executable format: File format not recognized
Attaching to process 2325
[New LWP 2480]
[New LWP 2481]
[New LWP 2482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3302ea95d3 in select () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) cont
Continuing.

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x55f7cbb6f650 in ?? ()
(gdb) bt f
#0  0x55f7cbb6f650 in ?? ()
No symbol table info available.
#1  0x55f7ca8ec6dc in ProcVidModeGetModeLine (client=0x55f7cc218ee0) at 
../../Xext/vidmode.c:255
stuff = 
rep = {type = 1 '\001', pad1 = 0 '\000', sequenceNumber = 254, length = 
5, dotclock = 0, hdisplay = 0, hsyncstart = 0, hsyncend = 0, 
  htotal = 0, hskew = 0, vdisplay = 0, vsyncstart = 0, vsyncend = 0, 
vtotal = 0, pad2 = 0, flags = 0, reserved1 = 0, reserved2 = 0, 
  reserved3 = 0, privsize = 0}
pScreen = 
mode = 0x7ffd64d56e20
dotClock = 32765
#2  0x55f7ca77ad9f in Dispatch () at ../../dix/dispatch.c:430
clientReady = 0x55f7cbf9c780
result = 
client = 0x55f7cc218ee0
nready = 0
icheck = 0x55f7cab7b130 
start_tick = 12090
#3  0x55f7ca77ee13 in dix_main (argc=11, argv=0x7ffd64d57018, 
envp=) at ../../dix/main.c:300
i = 
alwaysCheckForInput = {0, 1}
#4  0x7f3302dcc830 in __libc_start_main (main=0x55f7ca769030 , 
argc=11, argv=0x7ffd64d57018, init=, 
fini=, rtld_fini=, stack_end=0x7ffd64d57008) 
at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -792397858051174054, 
94522742050880, 140726295162896, 0, 0, -6839407696988057254, 
-687903866822310}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0xb, 0x55f7ca769030 }, data = {prev = 0x0, 
  cleanup = 0x0, canceltype = 11}}}
not_first_call = 
#5  0x55f7ca769069 in _start ()
No symbol table info available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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 Mar  9 12:09:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
InstallationDate: Installed on 2016-08-01 (585 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Dell Precision M3800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=53750055-6616-428b-88f9-c6c555f8c31d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: Dell

[Desktop-packages] [Bug 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

2018-02-27 Thread Christopher Kyle Horton

I'm also now wondering if perhaps this is a duplicate of 1720651.

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+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 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

2018-02-27 Thread Christopher Kyle Horton

I'm seeing something similar on Bionic when using the Communitheme on
Wayland session, where the scrollbar also goes past the bottom of the
window. It does not show up when using Xorg. I think the problem also
appears under the Ambiance theme on Wayland, but I do not have a
screenshot immediately available demonstrating this. The severity of the
problem seems to change depending on the theme used.

(I originally reported my issue here: https://github.com/Ubuntu/gtk-
communitheme/issues/199)

** Bug watch added: github.com/Ubuntu/gtk-communitheme/issues #199
   https://github.com/Ubuntu/gtk-communitheme/issues/199

** Attachment added: "Communitheme Terminal scrollbar past window edge.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+attachment/5064391/+files/Communitheme%20Terminal%20scrollbar%20past%20window%20edge.png

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+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 1720651] Re: gnome-terminal: Extra pixel line to right of scrollbar with wayland sesssion

2018-02-27 Thread Christopher Kyle Horton

I'm seeing something similar on Bionic when using the Communitheme on
Wayland session, where the scrollbar also goes past the bottom of the
window. It does not show up when using Xorg. I think the problem also
appears under the Ambiance theme on Wayland, but I do not have a
screenshot immediately available demonstrating this. The severity of the
problem seems to change depending on the theme used.

(I originally reported my issue here: https://github.com/Ubuntu/gtk-
communitheme/issues/199)

** Bug watch added: github.com/Ubuntu/gtk-communitheme/issues #199
   https://github.com/Ubuntu/gtk-communitheme/issues/199

** Attachment added: "Communitheme Terminal scrollbar past window edge.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720651/+attachment/5064387/+files/Communitheme%20Terminal%20scrollbar%20past%20window%20edge.png

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

Title:
  gnome-terminal: Extra pixel line to right of scrollbar with wayland
  sesssion

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Scrollbar drawing broken, with light theme variant on wayland session.
  See attached screenshot (white line right of scrollbar). To fix this
  you should remove some unity-compatible patch.

  Ubuntu 17.10, gnome-terminal-3.24.2-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720651/+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 1725078] Re: Can't set Ctrl+Shift as a shortcut

2018-01-24 Thread Kyle Robbertze

** Package changed: gnome-shell-extension-shortcuts (Ubuntu) => gnome-
shell (Ubuntu)

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

Title:
  Can't set Ctrl+Shift as a shortcut

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Can't set Ctrl+Shift (and many other key combinations) as a shortcut
  in new and shiny Ubuntu 17.10. Nothing happens when I press these
  keys. For example, when setting "Switch to next input source"
  shortcut, a window pops up waiting for a key combination, but nothing
  happens at all when I press Ctrl+Shift. I can still set some
  combinations like Super+Space, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-shortcuts (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 04:03:29 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell-extension-shortcuts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725078/+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 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

2017-11-22 Thread Kyle Raglin

Ubuntu 17.10 with all updates, however, this problem persists for me.  I
would not describe it as "fixed".

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Invalid
Status in hplip package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1714659/+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 1731111] Re: libreoffice crashes immediately

2017-11-08 Thread Kyle Bentley

This seems related to AMD's amdgpu pro:

Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging 
symbols found)...done.
(gdb) run
Starting program: /usr/lib/libreoffice/program/soffice.bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe149d700 (LWP 20986)]
[New Thread 0x7fffdf25c700 (LWP 20988)]
[New Thread 0x7fffdea5b700 (LWP 20989)]
[New Thread 0x7fffddf43700 (LWP 20990)]
[New Thread 0x7fffdc1c5700 (LWP 20994)]
[Thread 0x7fffdc1c5700 (LWP 20994) exited]
[Thread 0x7fffdf25c700 (LWP 20988) exited]
[New Thread 0x7fffdc1c5700 (LWP 20995)]

Thread 7 "soffice.bin" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdc1c5700 (LWP 20995)]
0x7fffc85d19ee in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
(gdb) bt
#0  0x7fffc85d19ee in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#1  0x7fffc85d1c79 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#2  0x7fffc85a7c02 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#3  0x7fffc85806b9 in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#4  0x7fffc8513fbf in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#5  0x7fffc85916ac in ?? () from 
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#6  0x732396ba in start_thread (arg=0x7fffdc1c5700) at 
pthread_create.c:333
#7  0x73ef13dd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

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

Title:
  libreoffice crashes immediately

Status in libreoffice package in Ubuntu:
  New

Bug description:
  kyle@SOONG:~/src/testing$ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
Version table:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This is a relatively new install.  I can't open libreoffice at all
  without it instantly crashing.  Nothing unusual from the terminal,
  just some GTK warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov  8 21:18:44 2017
  InstallationDate: Installed on 2017-10-30 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/173/+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 1731111] [NEW] libreoffice crashes immediately

2017-11-08 Thread Kyle Bentley

Public bug reported:

kyle@SOONG:~/src/testing$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
libreoffice:
  Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
  Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
  Version table:
 *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:5.1.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

This is a relatively new install.  I can't open libreoffice at all
without it instantly crashing.  Nothing unusual from the terminal, just
some GTK warnings.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Nov  8 21:18:44 2017
InstallationDate: Installed on 2017-10-30 (10 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/173

Title:
  libreoffice crashes immediately

Status in libreoffice package in Ubuntu:
  New

Bug description:
  kyle@SOONG:~/src/testing$ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
Version table:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This is a relatively new install.  I can't open libreoffice at all
  without it instantly crashing.  Nothing unusual from the terminal,
  just some GTK warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov  8 21:18:44 2017
  InstallationDate: Installed on 2017-10-30 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/173/+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 1705943] [NEW] No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line Out, Rear]

2017-07-23 Thread Kyle Enger

Public bug reported:

I upgraded from 16.10 to 17.04 using Software Updater on 2017-07-22. The
upgrade is working well except for almost complete lack of sound; the
only time I've heard sound is with the 1st set (but not 2nd set) of test
tones during the ubuntu-bug submission process for this bug. It is not a
hardware issue since my machine is a dual boot with Windows 10 and sound
works on Windows. pavucontrol says I have "Built-in Audio Digital Stereo
(IEC958)" and indicates the system is not muted and shows a visual
indicator of sound being played when I play a test sound. aplay -l gives
the following:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

Thank you for your help, and I'll be happy to provide further info as
needed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sun Jul 23 16:10:22 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-11-27 (238 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound 
at all
UpgradeStatus: Upgraded to zesty on 2017-07-22 (1 days ago)
dmi.bios.date: 07/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd07/16/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug zesty

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

Title:
  No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line
  Out, Rear]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded from 16.10 to 17.04 using Software Updater on 2017-07-22.
  The upgrade is working well except for almost complete lack of sound;
  the only time I've heard sound is with the 1st set (but not 2nd set)
  of test tones during the ubuntu-bug submission process for this bug.
  It is not a hardware issue since my machine is a dual boot with
  Windows 10 and sound works on Windows. pavucontrol says I have "Built-
  in Audio Digital Stereo (IEC958)" and indicates the system is not
  muted and shows a visual indicator of sound being played when I play a
  test sound. aplay -l gives the following:

   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
Subdevices: 0/1
Subdevice #0: subdevice #0

  Thank you for your help, and I'll be happy to provide further info as
  needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Jul 23 16:10:22 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-27 (238 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No

[Desktop-packages] [Bug 1555569] Re: Use 'title' field for snap apps

2017-07-18 Thread Kyle Fazzari

Sergio, what is the snapcraft solution to this? I'm still under the
impression the title (and license) need to go into the snap.yaml, but
you seemed to think it was only out-of-band to the store. Did we get
that resolved?

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

Title:
  Use 'title' field for snap apps

Status in Snapcraft:
  New
Status in Software Center Agent:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Snaps show using the snap 'name', which has a limited character set and is 
not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is 
more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd 
supports this field we should use it in GNOME Software.

  [Test Case]
  1. Start GNOME Software
  2. Search for 'moon'

  Expected result:
  A snap called 'Moon Buggy' is shown.

  Observed result:
  A snap called 'moon-buggy' is shown.

  [Regression Potential]
  The fix is to use the new field if it is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/169/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-13 Thread Christopher Kyle Horton

I got this same problem on Ubuntu GNOME 17.10 64-bit when trying to run
the following in the terminal:

sudo apt update && sudo apt upgrade -y

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-03-20 Thread Kyle Fazzari

** Changed in: nextcloud-snap
   Importance: Unknown => High

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+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 967022] Re: Cannot create new folder in Chromium download dialogue

2017-02-27 Thread Kyle Barbour

In case anyone is still coming to this bug, according to the GNOME devs,
this problem is actually in the GTK+ filechooser in gtk2, which
chromium-browser currently (v55) uses [1]. That explains why it affects
multiple applications, not just chromium-browser. The bug was fixed in
2014 in gtk3 [2], which chromium-browser has been slowly converting to
[3-4]. Accordingly I'm told that this bug is no longer present in the
gtk3-based builds of chromium-browser such as the current beta stream
(v57) [1], but I haven't had the chance to test it myself.

In short, this should be fixed in all applications based on gtk3 and so
will probably no longer be an issue in stable once v57 rolls out, but it
sounds like it will be WONTFIX for applications still using gtk2.

[1]: https://bugzilla.gnome.org/show_bug.cgi?id=779292
[2]: https://bugzilla.gnome.org/show_bug.cgi?id=729927
[3]: 
https://chromium.googlesource.com/chromium/src/+/acc4214c4dece4e70fb53355d557bd45f35965d6/docs/linux_gtk_theme_integration.md#GTK3
[4]: https://bugs.chromium.org/p/chromium/issues/detail?id=79722

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

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

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

Title:
  Cannot create new folder in Chromium download dialogue

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chrome Version   : 17.0.963.79
  OS Version: ubuntu 11.10 (64Bit) / opensuse 12.1 (64Bit)

  What steps will reproduce the problem?
  1.Set option to ask at every download where files should be saved
  2.select downloadable file and click create folder in downloads dialogue

  What is the expected result?
  New folder should be created. Possibility to rename the new folder

  What happens instead?
  New created folder disappears after 1 or 2 seconds

  This only happens in the Standard-Download folder which was created
  during the OS installation. Per default its named "Downloads".

  I also tried other applications. For example i created a new text-
  document in libre office and choose "save to". I switched into
  /Home/mf/Downloads/ and created a new folder. It works. Then i tried
  chromium again, download a file (no matter which filetype), and it
  doesn't work. I am not able to create a new folder into Downloads via
  the download dialogue.

  UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11
  (KHTML, like Gecko) Ubuntu/11.10 Chromium/17.0.963.79
  Chrome/17.0.963.79 Safari/535.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/967022/+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 967022] Re: Cannot create new folder in Chromium download dialogue

2017-02-25 Thread Kyle Barbour

Apologies, meant to include Chromium version - 55.0.2883.87.

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

Title:
  Cannot create new folder in Chromium download dialogue

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chrome Version   : 17.0.963.79
  OS Version: ubuntu 11.10 (64Bit) / opensuse 12.1 (64Bit)

  What steps will reproduce the problem?
  1.Set option to ask at every download where files should be saved
  2.select downloadable file and click create folder in downloads dialogue

  What is the expected result?
  New folder should be created. Possibility to rename the new folder

  What happens instead?
  New created folder disappears after 1 or 2 seconds

  This only happens in the Standard-Download folder which was created
  during the OS installation. Per default its named "Downloads".

  I also tried other applications. For example i created a new text-
  document in libre office and choose "save to". I switched into
  /Home/mf/Downloads/ and created a new folder. It works. Then i tried
  chromium again, download a file (no matter which filetype), and it
  doesn't work. I am not able to create a new folder into Downloads via
  the download dialogue.

  UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11
  (KHTML, like Gecko) Ubuntu/11.10 Chromium/17.0.963.79
  Chrome/17.0.963.79 Safari/535.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/967022/+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 967022] Re: Cannot create new folder in Chromium download dialogue

2017-02-25 Thread Kyle Barbour

This affects me as well - Ubuntu 16.04.2 LTS; 4.4.0-62-generic.

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

Title:
  Cannot create new folder in Chromium download dialogue

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chrome Version   : 17.0.963.79
  OS Version: ubuntu 11.10 (64Bit) / opensuse 12.1 (64Bit)

  What steps will reproduce the problem?
  1.Set option to ask at every download where files should be saved
  2.select downloadable file and click create folder in downloads dialogue

  What is the expected result?
  New folder should be created. Possibility to rename the new folder

  What happens instead?
  New created folder disappears after 1 or 2 seconds

  This only happens in the Standard-Download folder which was created
  during the OS installation. Per default its named "Downloads".

  I also tried other applications. For example i created a new text-
  document in libre office and choose "save to". I switched into
  /Home/mf/Downloads/ and created a new folder. It works. Then i tried
  chromium again, download a file (no matter which filetype), and it
  doesn't work. I am not able to create a new folder into Downloads via
  the download dialogue.

  UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11
  (KHTML, like Gecko) Ubuntu/11.10 Chromium/17.0.963.79
  Chrome/17.0.963.79 Safari/535.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/967022/+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 1665126] Re: snap not listed in categories

2017-02-15 Thread Kyle Fazzari

** Description changed:

  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)
  
- Looks like only .deb are listed in the Ubuntu Software?
+ Looks like only .deb are listed in categories within Ubuntu Software?

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

Title:
  snap not listed in categories

Status in gnome-software package in Ubuntu:
  New

Bug description:
  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)

  Looks like only .deb are listed in categories within Ubuntu Software?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1665126/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-20 Thread Kyle Vedder

I just received the patch and my touchpad now works as expected.

This is for my Dell Latitude E5470, which, before this update, had the
generic mouse drivers which did not recognize it as a touchpad.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1639899] [NEW] network-manager applet does not show wifi interface

2016-11-07 Thread Kyle Utecht

Public bug reported:

Per the 10/3/2016 post for bug 1574347, I'm submitting my own bug for no
wifi interface and the wrong icon on the network-manager applet on a
Thinkpad T440p running 16.04 LTS. Even though I see the wifi
disconnected icon and no wifi networks in the applet drop down, I am
still connected to a network and can access the internet.

Wireless card information:
$ lspci -v
...
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at f180 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

$ nmcli dev
DEVICE  TYPE  STATECONNECTION 
wlp4s0  wifi  connecteda 1  
enp0s25 ethernet  unavailable  -- 
lxdbr0  bridgeunmanaged-- 
vethYCXI2H  ethernet  unmanaged-- 
lo  loopback  unmanaged--   

$ ip route
default via 192.168.208.1 dev wlp4s0  proto static  metric 600 
10.1.8.107 via 192.168.208.1 dev wlp4s0  proto dhcp  metric 600 
192.168.208.0/20 dev wlp4s0  proto kernel  scope link  src 192.168.219.126  
metric 600 

nmtui does not list any active connections.

network-manager 1.2.2-0ubuntu0.16.04.3 installed.

It seems to run like this for a while, including several wake/sleep
cycles but then eventually won't connect at all and then I end up
restarting.

Please let me know if any other information would be helpful. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-gnome 1.2.0-0ubuntu0.16.04.4
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: Unity
Date: Mon Nov  7 12:48:28 2016
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-09-12 (56 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.208.1 dev wlp4s0  proto static  metric 600 
 10.0.1.0/24 dev lxdbr0  proto kernel  scope link  src 10.0.1.1 
 10.1.8.107 via 192.168.208.1 dev wlp4s0  proto dhcp  metric 600 
 169.254.0.0/16 dev lxdbr0  scope link  metric 1000 
 192.168.208.0/20 dev wlp4s0  proto kernel  scope link  src 192.168.219.126  
metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  network-manager applet does not show wifi interface

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

Bug description:
  Per the 10/3/2016 post for bug 1574347, I'm submitting my own bug for
  no wifi interface and the wrong icon on the network-manager applet on
  a Thinkpad T440p running 16.04 LTS. Even though I see the wifi
  disconnected icon and no wifi networks in the applet drop down, I am
  still connected to a network and can access the internet.

  Wireless card information:
  $ lspci -v
  ...
  04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at f180 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  $ nmcli dev
  DEVICE  TYPE  STATECONNECTION 
  wlp4s0  wifi  connecteda 1  
  enp0s25 ethernet  unavailable  -- 
  lxdbr0  bridgeunmanaged-- 
  vethYCXI2H  ethernet  unmanaged-- 
  lo  loopback  unmanaged--   

  $ ip route
  default via 192.168.208.1 dev wlp4s0  proto static  metric 600 
  10.1.8.107 via 192.168.208.1 dev wlp4s0  proto dhcp  metric 600 
  192.168.208.0/20 dev wlp4s0  proto kernel  scope link  src 192.168.219.126  
metric 600 

  nmtui does not list any active connections.

  network-manager 1.2.2-0ubuntu0.16.04.3 installed.

  It seems to run like this for a while, including several wake/sleep
  cycles but

[Desktop-packages] [Bug 1629456] [NEW] Summary isn't shown for snaps

2016-09-30 Thread Kyle Fazzari

Public bug reported:

Ubuntu packages are shown in gnome-software with the name, followed by
the summary, followed by install buttons, and finally followed by a more
detailed description. In contrast, snaps are shown with the name,
detailed summary, followed by install buttons. The summary isn't
present, and the experience isn't consistent with normal packages.

I suggest we maintain consistency: show the snap name, followed by the
snap summary, followed by install buttons, and finally followed by the
more detailed description.

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Summary isn't shown for snaps

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu packages are shown in gnome-software with the name, followed by
  the summary, followed by install buttons, and finally followed by a
  more detailed description. In contrast, snaps are shown with the name,
  detailed summary, followed by install buttons. The summary isn't
  present, and the experience isn't consistent with normal packages.

  I suggest we maintain consistency: show the snap name, followed by the
  snap summary, followed by install buttons, and finally followed by the
  more detailed description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1629456/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Kyle

I cant tell anymore as i cant even get to a command prompt anymore, if i
recall something about dns is the error now

Sent from my HTC

- Reply message -
From: "Florian Fainelli" 
To: 
Subject: [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
Date: Thu, Sep 15, 2016 10:15 PM

The "/etc/modprobe.d is not a file" error is kind of confusing actually
and seems to be some stray debug in share/hybrid/gpu-manager.c.

Do you have nvidia in /etc/modules by chance?

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

Title:
gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
Confirmed

Bug description:
Get these lines logged into gpu-manager.log, on that fresh stock
installation

/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 14 08:42:45 2014
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.default.whoopsie: [modified]
modified.conffile..etc.gdm.Init.Default: [modified]
mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+subscriptions

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-09-15 Thread Kyle

I updated to v16 and my pc is now unusable, though i suspect its because
i did not disable secure boot.

Sent from my HTC

- Reply message -
From: "Pander" <1369...@bugs.launchpad.net>
To: 
Subject: [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
Date: Thu, Sep 15, 2016 10:42 AM

Is there a workaround for xenial?

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

Title:
gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
Confirmed

Bug description:
Get these lines logged into gpu-manager.log, on that fresh stock
installation

/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 14 08:42:45 2014
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.default.whoopsie: [modified]
modified.conffile..etc.gdm.Init.Default: [modified]
mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+subscriptions

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

2016-08-27 Thread Kyle Katarn

This is my fist post, so i could forget something.
Version :
-Version-
Kernel  : Linux 4.4.0-34-generic (x86_64)
Compiled: #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
C Library   : Unknown
Default C Compiler  : GNU C Compiler version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.2) 
Distribution: Ubuntu 16.04.1 LTS
Home Directory  : /home/stef
Desktop Environment : XFCE 4

This is a installation from scratch.

the same problem occur with GEDIT.

thanks.

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

Title:
  Mousepad show the warning Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus -*

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  When I start mousepad in a terminal, I have this warning :

  ** (mousepad:25021): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion
  refusée

  When I start it with GKSU, the warning is not displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1617630] [NEW] Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

2016-08-27 Thread Kyle Katarn

Public bug reported:

When I start mousepad in a terminal, I have this warning :

** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée

When I start it with GKSU, the warning is not displayed.

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Mousepad show the warning Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus -*

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  When I start mousepad in a terminal, I have this warning :

  ** (mousepad:25021): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion
  refusée

  When I start it with GKSU, the warning is not displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1592866] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is

2016-06-15 Thread Kyle Taylor

Public bug reported:

Installing ubuntu-desktop from standard repositories led to package
conflicts with the account-plugin-facebook package from KDE.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Jun 13 16:07:38 2016
DuplicateSignature:
 package:account-plugin-facebook:(not installed)
 Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package kaccounts-providers 4:15.12.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-04-18 (57 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: account-plugins
Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-04-22 (53 days ago)

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


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

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

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

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Installing ubuntu-desktop from standard repositories led to package
  conflicts with the account-plugin-facebook package from KDE.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jun 13 16:07:38 2016
  DuplicateSignature:
   package:account-plugin-facebook:(not installed)
   Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-04-18 (57 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1592866/+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 1582424] [NEW] General inquire

2016-05-16 Thread Kyle Anderson

Public bug reported:

Just checking to see if there are known issues after a fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon May 16 14:47:36 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:1439]
InstallationDate: Installed on 2016-05-16 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 5986:0149 Acer, Inc 
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP G72 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b81f44cf-23e6-4c23-b629-5f83086b514b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.48
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1439
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 60.50
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd11/09/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058C110002252710001620100:rvnHewlett-Packard:rn1439:rvr60.50:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G72 Notebook PC
dmi.product.version: 058C110002252710001620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun May 15 19:01:58 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13140 
 vendor SEC
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 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/1582424

Title:
  General inquire

Status in xorg package in Ubuntu:
  New

Bug description:
  Just checking to see if there are known issues after a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 16 14:47:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core

Re: [Desktop-packages] [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-05-11 Thread Kyle

Also just an FYI:

https://wiki.ubuntu.com/Bugs/Triage (Internal Server Error)

-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Pam 
Satterthwaite
Sent: Wednesday, May 11, 2016 4:35 AM
To: k...@digitist.com
Subject: [Bug 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

So I'm having this problem too. I'm on Wily - pretty vanilla install,
although I'm using Gnome once I get that far. I don't have a graphics
card at all, just whatever intel put on the cruddy i3 mobo that's in
this $300 laptop - so no additional drivers.

What is strange is that I didn't have any problems yesterday, and I am
today, and yet I didn't install anything yesterday or do any system
upgrading.

Just wanted to say that it's not only in nvidia drivers.

If you need any more details, or logs or debugging help, I would gladly
provide.

thanks

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+subscriptions

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

2016-04-25 Thread Kyle

Just installed Ubuntu 15.04 a few weeks ago smashing my head against
the wall on this one. Any workarounds available? Is there an ETA on a
bugfix?

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+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 1573699] [NEW] Select region during install process cause crash

2016-04-22 Thread Kyle

Public bug reported:

When install the system, on the step which system asks me to select a
region (default is Los Angeles for me). And I tried to change to San
Francisco, but when I type "San", the installer freezes and cannot click
anywhere. I waited for a long time but doesn't work either so has to re-
install.

I can change region with no problem after installation is completed. But
I guess many users are trying to change region while install but most of
them don't know how to file a bug (which takes me 30 minutes to find the
correct way!!! Got to be easier if Ubuntu wants to replace Windows)

Please make the fix. Thanks.

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Select region during install process cause crash

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When install the system, on the step which system asks me to select a
  region (default is Los Angeles for me). And I tried to change to San
  Francisco, but when I type "San", the installer freezes and cannot
  click anywhere. I waited for a long time but doesn't work either so
  has to re-install.

  I can change region with no problem after installation is completed.
  But I guess many users are trying to change region while install but
  most of them don't know how to file a bug (which takes me 30 minutes
  to find the correct way!!! Got to be easier if Ubuntu wants to replace
  Windows)

  Please make the fix. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573699/+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 1573695] [NEW] System update broken

2016-04-22 Thread Kyle

Public bug reported:

System update easily broken. Here is the procedure. And I believe this
may happen to many Chinese users

I downloaded Sougou Pinyin (the most popular Chinese input app) from
official website which is released the same date 16.04 is released and
claims it supports 16.04.

I downloaded the file sogoupinyin_2.0.0.0072_amd64.deb, and double click
to install. Then Ubuntu Software window pops up. And I click "install",
then no response. And I clicked again, this time a "Waiting to install"
icon appears on the sidebar but never finishes. Then I turned off my PC
and turn it back on again, now I see a red icon appears on top of top
sidebar near time which indicates "An error occurred. Please run Package
Manager ..."

And since then I am not able to install any update.

I believe this is a blocker bug. And I have to re-install the system
again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 22 08:56:19 2016
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2016-04-22 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (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 gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1573695

Title:
  System update broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  System update easily broken. Here is the procedure. And I believe this
  may happen to many Chinese users

  I downloaded Sougou Pinyin (the most popular Chinese input app) from
  official website which is released the same date 16.04 is released and
  claims it supports 16.04.

  I downloaded the file sogoupinyin_2.0.0.0072_amd64.deb, and double
  click to install. Then Ubuntu Software window pops up. And I click
  "install", then no response. And I clicked again, this time a "Waiting
  to install" icon appears on the sidebar but never finishes. Then I
  turned off my PC and turn it back on again, now I see a red icon
  appears on top of top sidebar near time which indicates "An error
  occurred. Please run Package Manager ..."

  And since then I am not able to install any update.

  I believe this is a blocker bug. And I have to re-install the system
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 08:56:19 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573695/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

2016-04-05 Thread Kyle Brophy

** Changed in: xserver-xorg-video-intel (Ubuntu)
 Assignee: (unassigned) => Kyle Brophy (kylebrophy)

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video

[Desktop-packages] [Bug 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

2016-03-06 Thread Christopher Kyle Horton

I just found GNOME Calendar installed by default on my Ubuntu Xenial
Xerus desktop after a recent partial upgrade, which as a side effect
finally fixes this bug. Perhaps this should now be marked as Fix
Committed or something?

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Confirmed
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841409/+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 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor

2016-02-22 Thread Kyle Fazzari

When using trusty on my M3800 (4k screen) with an external monitor (also
4k) this happens VERY often-- several times a day. I wonder if it's
somehow related to GPU memory. This is really a productivity killer!

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

Title:
  cursor sometimes disappears on XPS 13 9343 and external monitor

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using
  an external display port monitor. Occasionally, the mouse cursor
  disappears (sometimes after screen lock, other times just normal
  usage). I saw something on stack exchange that said this might help:

  gsettings set org.gnome.settings-daemon.plugins.cursor active false

  I've done this and it sometimes helps and sometimes doesn't. I've also
  just seen the cursor come back on its own after a few minutes without
  doing anything. Trying to interact with the touch screen, then the
  mouse has no effect. Unplugging and replugging the mouse has no
  effect. Using the touchpad has no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 22 11:19:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-06-13 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet 
splash vt.handoff=7
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 10:53:54 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467595/+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 1513876] [NEW] package libnm-util2:amd64 1.0.4-0ubuntu5.1 failed to install/upgrade: package libnm-util2:amd64 is already installed and configured

2015-11-06 Thread Kyle

Public bug reported:

Happened during 'sudo apt-get upgrade'

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libnm-util2:amd64 1.0.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Nov  6 10:09:18 2015
DuplicateSignature: package:libnm-util2:amd64:1.0.4-0ubuntu5.1:package 
libnm-util2:amd64 is already installed and configured
ErrorMessage: package libnm-util2:amd64 is already installed and configured
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-09-10 (56 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 129.21.91.254 dev wlan0  proto static  metric 600 
 129.21.13.175 via 129.21.91.254 dev wlan0  proto dhcp  metric 600 
 129.21.88.0/22 dev wlan0  proto kernel  scope link  src 129.21.90.168  metric 
600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt  1.0.10.2ubuntu1
SourcePackage: network-manager
Title: package libnm-util2:amd64 1.0.4-0ubuntu5.1 failed to install/upgrade: 
package libnm-util2:amd64 is already installed and configured
UpgradeStatus: Upgraded to wily on 2015-10-23 (14 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
ritwpa2 f0c37e58-0db1-4380-9b81-70a5424f1252  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: already-installed amd64 apport-package need-duplicate-check wily

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

Title:
  package libnm-util2:amd64 1.0.4-0ubuntu5.1 failed to install/upgrade:
  package libnm-util2:amd64 is already installed and configured

Status in network-manager package in Ubuntu:
  New

Bug description:
  Happened during 'sudo apt-get upgrade'

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libnm-util2:amd64 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Nov  6 10:09:18 2015
  DuplicateSignature: package:libnm-util2:amd64:1.0.4-0ubuntu5.1:package 
libnm-util2:amd64 is already installed and configured
  ErrorMessage: package libnm-util2:amd64 is already installed and configured
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-10 (56 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 129.21.91.254 dev wlan0  proto static  metric 600 
   129.21.13.175 via 129.21.91.254 dev wlan0  proto dhcp  metric 600 
   129.21.88.0/22 dev wlan0  proto kernel  scope link  src 129.21.90.168  
metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: network-manager
  Title: package libnm-util2:amd64 1.0.4-0ubuntu5.1 failed to install/upgrade: 
package libnm-util2:amd64 is already installed and configured
  UpgradeStatus: Upgraded to wily on 2015-10-23 (14 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
ritwpa2 f0c37e58-0db1-4380-9b81-70a5424f1252  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged

[Desktop-packages] [Bug 1500144] Re: Xorg crashed with SIGSEGV

2015-11-05 Thread Kyle Boone

I have reproduced the crash while attached in gdb. Here is a backtrace.

** Attachment added: "gdb backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1500144/+attachment/4513674/+files/gdb-Xorg.txt

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

Title:
  Xorg crashed with SIGSEGV

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

Bug description:
  Crashes might be related to full screen video. Crashes when exiting
  fullscreen or switching windows.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   fsck from util-linux 2.26.2
   tito-root: clean, 2076967/15114240 files, 50801586/60448000 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 26 23:54:31 2015
  DistUpgraded: 2015-07-22 01:05:44,405 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-08-08 (414 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro splash quiet 
i915.enable_psr=1 vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fe56794acf9:cmpb   $0x48,(%rax)
   PC (0x7fe56794acf9) ok
   source "$0x48" ok
   destination "(%rax)" (0x23f2) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: Upgraded to wily on 2015-07-22 (66 days ago)
  UserGroups:
   
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Sep 26 23:54:36 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.17.2-1ubuntu7

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

2015-11-05 Thread Kyle Boone

I am also experiencing this bug on Ubuntu Gnome 15.10 after an upgrade
from 15.04. To reproduce it, I logged in, opened up Google Chrome, and
went to twitch.tv where I opened a full screen video. The X server
crashes within a few seconds after. Non fullscreen video is fine. I have
attached an Xorg log from a session like this.

I can also trigger an Xorg crash by switching to the virtual terminal
(Ctrl+alt+f1).

** Attachment added: "Xorg log with crash"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1500144/+attachment/4513667/+files/Xorg.1.log.old

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

Title:
  Xorg crashed with SIGSEGV

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

Bug description:
  Crashes might be related to full screen video. Crashes when exiting
  fullscreen or switching windows.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   fsck from util-linux 2.26.2
   tito-root: clean, 2076967/15114240 files, 50801586/60448000 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 26 23:54:31 2015
  DistUpgraded: 2015-07-22 01:05:44,405 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-08-08 (414 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro splash quiet 
i915.enable_psr=1 vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fe56794acf9:cmpb   $0x48,(%rax)
   PC (0x7fe56794acf9) ok
   source "$0x48" ok
   destination "(%rax)" (0x23f2) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: Upgraded to wily on 2015-07-22 (66 days ago)
  UserGroups:
   
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Sep 26 23:54:36 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.17.2-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1500144/+subscriptions

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

[Desktop-packages] [Bug 1493722] Re: [Media services] Volume up/down long press should skip to next/previous track

2015-10-23 Thread Kyle Fazzari

Peter, that would suck while running.

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

Title:
  [Media services] Volume up/down long press should skip to
  next/previous track

Status in Canonical System Image:
  Confirmed
Status in Media Hub:
  Invalid
Status in Ubuntu Music App:
  New
Status in Ubuntu UX:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A handy feature of music players is the ability to quickly skip tracks
  by long-pressing the volume buttons. This allows users to control
  their music without having to take the device out of their pocket,
  turn its screen on, unlock it, go to the music app and press "Next".

  As of now, when I long press the volume button, it rapidly increases
  the volume, which is not very nice to my ears ;-)

  Is it possible to control the music app this way on Ubuntu phone?

  Music app version tested: 2.2.910 (2015-09-03)
  Device: Meizu MX 4
  System info: Ubuntu 15.04 (r4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493722/+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 1501973] [NEW] Blurry/pixelated icon in Unity app switcher on scaled-up display

2015-10-01 Thread Christopher Kyle Horton

Public bug reported:

The icon for Firefox in the Unity app switcher is blurry / pixelated
when using display scaling other than 1. See attached screenshot where
the display scaling in Display settings is set to 1.25.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: firefox 41.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  christopher   1622 F pulseaudio
 /dev/snd/controlC0:  christopher   1622 F pulseaudio
BuildID: 20150918092427
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Oct  1 21:32:23 2015
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 2015-08-29 (33 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
IpRoute:
 default via 172.24.192.1 dev wlp4s0  proto static  metric 600
 169.254.0.0/16 dev wlp4s0  scope link  metric 1000
 172.24.192.0/18 dev wlp4s0  proto kernel  scope link  src 172.24.212.147  
metric 600
 198.111.37.218 via 172.24.192.1 dev wlp4s0  proto dhcp  metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=41.0/20150918092427 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET35WW (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S13M00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 Std
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20C0S13M00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S13M00:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0S13M00
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug wily

** Attachment added: "Blurry Firefox icon in Unity window switcher.png"
   
https://bugs.launchpad.net/bugs/1501973/+attachment/4481440/+files/Blurry%20Firefox%20icon%20in%20Unity%20window%20switcher.png

** Description changed:

- The icon for Firefox in the Unity app switcher is blurry / pixelated.
- See attached screenshot.
+ The icon for Firefox in the Unity app switcher is blurry / pixelated
+ when using display scaling other than 1. See attached screenshot where
+ the display scaling in Display settings is set to 1.25.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: firefox 41.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  christopher   1622 F pulseaudio
-  /dev/snd/controlC0:  christopher   1622 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  christopher   1622 F pulseaudio
+  /dev/snd/controlC0:  christopher   1622 F pulseaudio
  BuildID: 20150918092427
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Oct  1 21:32:23 2015
  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
+  # 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 2015-08-29 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
  IpRoute:
-  default via 172.24.192.1 dev wlp4s0  proto static  metric 600 
-  169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
-  172.24.192.0/18 dev wlp4s0  proto kernel  scope link  src 172.24.212.147  
metric 600 
-  198.111.37.218 via 172.24.192.1 dev wlp4s0  proto dhcp  metric 600
+  default via 172.24.192.1 dev wlp4s0  proto static  metric 600
+  169.254.0.0/16 dev wlp4s0  scope link  metric 1000
+  172.24.192.0/18 dev wlp4s0  proto kernel  scope link  src 172.24.212.147  
metric 600
+  198.111.37.218 via 172.24.192.1 dev wlp4s0  proto dhcp  metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js

[Desktop-packages] [Bug 1482439] Re: wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

2015-09-29 Thread Christopher Kyle Horton

The linked Fedora bug is closed with a note that wpa_supplicant-2.4.3
should fix this issue.

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

Title:
  wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa package in Fedora:
  Unknown

Bug description:
  wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: wpasupplicant 2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  Date: Wed Aug  5 00:08:21 2015
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2015-06-02 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f8880818cba <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f8880818cba) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
  UpgradeStatus: Upgraded to wily on 2015-06-17 (50 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1482439/+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 1492144] Re: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

2015-09-17 Thread Christopher Kyle Horton

During normal use of Wily on a Lenovo Yoga laptop convertible, I'm
getting this issue upon resuming from suspend.

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

Title:
  wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  This happens when running the NetworkManager autopkgtests

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: wpasupplicant 2.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Fri Sep  4 09:00:38 2015
  ExecutablePath: /sbin/wpa_supplicant
  ExecutableTimestamp: 1439920046
  ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd 
(%rdi),%xmm1
   PC (0x7f66fb181cc6) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+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 1485020] Re: firefox 40 shows a non-overrideable security error when talking to a captive portal

2015-09-14 Thread Kyle Fazzari

Try visiting about:config and temporarily toggle
security.ssl3.dhe_rsa_aes_128_sha and security.ssl3.dhe_rsa_aes_256_sha
to false-- that got me to a portal that was causing the same issue. Then
after you get online you can set them back to true.

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

Title:
  firefox 40 shows a non-overrideable security error when talking to a
  captive portal

Status in firefox package in Ubuntu:
  New

Bug description:
  When trying to connect to the airport wifi at the Portland Airport
  
(https://flypdxconnect.portofportland.com:8443/guestportal/gateway?sessionId=eb0a3d0a003315a2c104ce55=LOC1=cwa),
  firefox presents me with a non-overrideable security error:

  Secure Connection Failed

  An error occurred during a connection to
  flypdxconnect.portofportland.com:8443. SSL received a weak ephemeral
  Diffie-Hellman key in Server Key Exchange handshake message. (Error
  code: ssl_error_weak_server_ephemeral_dh_key)

  The page you are trying to view cannot be shown because the authenticity 
of the received data could not be verified.
  Please contact the website owners to inform them of this problem.

  When the user is behind a captive portal and talking to that portal is
  the only way to get Internet access, it is not acceptable to enforce
  an SSL security policy where the user has no way of overriding it, no
  way of fixing the server, and no reason to care about the security of
  the connection to this server.

  As a workaround for this issue, I ran chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1485020/+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 1485020] Re: firefox 40 shows a non-overrideable security error when talking to a captive portal

2015-09-14 Thread Kyle Fazzari

I like that Firefox tells you about this, but I don't think this should
be a non-overrideable error. This type of error should fall into the
same bucket as self-signed certificates: "Hey, we don't trust this
because of X. Are you sure you want to continue?"

I think that would be a decent fix for this without A) disabling this
feature all together or B) making Firefox figure out if its behind a
captive portal. I don't know if that would be a config change or a code
change, though. Thoughts?

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

Title:
  firefox 40 shows a non-overrideable security error when talking to a
  captive portal

Status in firefox package in Ubuntu:
  New

Bug description:
  When trying to connect to the airport wifi at the Portland Airport
  
(https://flypdxconnect.portofportland.com:8443/guestportal/gateway?sessionId=eb0a3d0a003315a2c104ce55=LOC1=cwa),
  firefox presents me with a non-overrideable security error:

  Secure Connection Failed

  An error occurred during a connection to
  flypdxconnect.portofportland.com:8443. SSL received a weak ephemeral
  Diffie-Hellman key in Server Key Exchange handshake message. (Error
  code: ssl_error_weak_server_ephemeral_dh_key)

  The page you are trying to view cannot be shown because the authenticity 
of the received data could not be verified.
  Please contact the website owners to inform them of this problem.

  When the user is behind a captive portal and talking to that portal is
  the only way to get Internet access, it is not acceptable to enforce
  an SSL security policy where the user has no way of overriding it, no
  way of fixing the server, and no reason to care about the security of
  the connection to this server.

  As a workaround for this issue, I ran chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1485020/+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 1490169] Re: Cannot install Google Chrome or Atom debs due to "bad quality" error

2015-09-03 Thread Christopher Kyle Horton

I just hit this problem again now when trying to install Skype. This is
a widespread issue. Someone on Google+ suggested this is due to a policy
change in lintian... should this bug be directed at that instead?

** Summary changed:

- Cannot install Google Chrome or Atom debs due to "bad quality" error
+ Cannot install common third-party debs due to "bad quality" error

** Description changed:

  When I try to install the official deb packages for Google Chrome or
  Atom, I get an error in the Software Center saying the package is of bad
  quality and should not be installed. For example, the details given for
  Atom read:
  
  "Lintian check results for /home/christopher/Downloads/atom-amd64.deb:
  Unknown tag "binary-file-compressed-with-upx" in profile "ubuntu/aptdaemon" 
at /usr/bin/lintian line 1661."
  
  It complains about binary-file-compressed-with-upx in the details for
  the Chrome package, too.
+ 
+ Packages known to be affected:
+ * Google Chrome
+ * Atom
+ * Skype
+ * audio-recorder
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-center 13.10-0ubuntu7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 29 13:13:44 2015
  InstallationDate: Installed on 2015-08-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cannot install common third-party debs due to "bad quality" error

Status in Lintian:
  New
Status in software-center package in Ubuntu:
  New

Bug description:
  When I try to install the official deb packages for Google Chrome or
  Atom, I get an error in the Software Center saying the package is of
  bad quality and should not be installed. For example, the details
  given for Atom read:

  "Lintian check results for /home/christopher/Downloads/atom-amd64.deb:
  Unknown tag "binary-file-compressed-with-upx" in profile "ubuntu/aptdaemon" 
at /usr/bin/lintian line 1661."

  It complains about binary-file-compressed-with-upx in the details for
  the Chrome package, too.

  Packages known to be affected:
  * Google Chrome
  * Atom
  * Skype
  * audio-recorder

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-center 13.10-0ubuntu7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 29 13:13:44 2015
  InstallationDate: Installed on 2015-08-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lintian/+bug/1490169/+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 1490169] Re: Cannot install common third-party debs due to "bad quality" error

2015-09-03 Thread Christopher Kyle Horton

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

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

Title:
  Cannot install common third-party debs due to "bad quality" error

Status in Lintian:
  New
Status in software-center package in Ubuntu:
  New

Bug description:
  When I try to install the official deb packages for Google Chrome or
  Atom, I get an error in the Software Center saying the package is of
  bad quality and should not be installed. For example, the details
  given for Atom read:

  "Lintian check results for /home/christopher/Downloads/atom-amd64.deb:
  Unknown tag "binary-file-compressed-with-upx" in profile "ubuntu/aptdaemon" 
at /usr/bin/lintian line 1661."

  It complains about binary-file-compressed-with-upx in the details for
  the Chrome package, too.

  Packages known to be affected:
  * Google Chrome
  * Atom
  * Skype
  * audio-recorder

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-center 13.10-0ubuntu7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 29 13:13:44 2015
  InstallationDate: Installed on 2015-08-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lintian/+bug/1490169/+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 1490169] [NEW] Cannot install Google Chrome or Atom debs due to bad quality error

2015-08-29 Thread Christopher Kyle Horton

Public bug reported:

When I try to install the official deb packages for Google Chrome or
Atom, I get an error in the Software Center saying the package is of bad
quality and should not be installed. For example, the details given for
Atom read:

Lintian check results for /home/christopher/Downloads/atom-amd64.deb:
Unknown tag binary-file-compressed-with-upx in profile ubuntu/aptdaemon at 
/usr/bin/lintian line 1661.

It complains about binary-file-compressed-with-upx in the details for
the Chrome package, too.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: software-center 13.10-0ubuntu7
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 29 13:13:44 2015
InstallationDate: Installed on 2015-08-29 (0 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150828)
PackageArchitecture: all
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lintian wily

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

Title:
  Cannot install Google Chrome or Atom debs due to bad quality error

Status in software-center package in Ubuntu:
  New

Bug description:
  When I try to install the official deb packages for Google Chrome or
  Atom, I get an error in the Software Center saying the package is of
  bad quality and should not be installed. For example, the details
  given for Atom read:

  Lintian check results for /home/christopher/Downloads/atom-amd64.deb:
  Unknown tag binary-file-compressed-with-upx in profile ubuntu/aptdaemon 
at /usr/bin/lintian line 1661.

  It complains about binary-file-compressed-with-upx in the details for
  the Chrome package, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-center 13.10-0ubuntu7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 29 13:13:44 2015
  InstallationDate: Installed on 2015-08-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150828)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1490169/+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 1490213] [NEW] Ubuntu Light renders incorrectly in Writer document

2015-08-29 Thread Christopher Kyle Horton

Public bug reported:

See the attached screenshot. I loaded an ODT file into LibreOffice
containing my resume, which included date headers meant to be displayed
using the Ubuntu Light font. However, The font is rendered very heavy,
even heavier than the plain Ubuntu font!

In the screenshot, the top line is regular Ubuntu, while the second line
is *supposed* to be Ubuntu Light. Ubuntu Light does appear correctly in
the font drop-down, however.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libreoffice-writer 1:4.4.4~rc3-0ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 29 19:14:51 2015
InstallationDate: Installed on 2015-08-29 (0 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150828)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Attachment added: LibreOffice Ubuntu vs Ubuntu Light.png
   
https://bugs.launchpad.net/bugs/1490213/+attachment/4454342/+files/LibreOffice%20Ubuntu%20vs%20Ubuntu%20Light.png

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

Title:
  Ubuntu Light renders incorrectly in Writer document

Status in libreoffice package in Ubuntu:
  New

Bug description:
  See the attached screenshot. I loaded an ODT file into LibreOffice
  containing my resume, which included date headers meant to be
  displayed using the Ubuntu Light font. However, The font is rendered
  very heavy, even heavier than the plain Ubuntu font!

  In the screenshot, the top line is regular Ubuntu, while the second
  line is *supposed* to be Ubuntu Light. Ubuntu Light does appear
  correctly in the font drop-down, however.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libreoffice-writer 1:4.4.4~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 29 19:14:51 2015
  InstallationDate: Installed on 2015-08-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150828)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1490213/+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 1371268] Re: Skydome image is malformed into a hyperbolic shape with streaking of windows

2015-08-27 Thread Kyle Barbour

This also occurs in the newer Lenovo X1 Carbon generation 3 laptop.

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

Title:
  Skydome image is malformed into a hyperbolic shape with streaking of
  windows

Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  I've searched Google and the Compiz forums regarding this, but
  unfortunately have failed to find the answer. I attempted to discuss
  the issue on the Compiz mailing list, the forums, and the Compiz bug
  tracker, but unfortunately due to login and posting failures on the
  forum and mailing list and the tracker being down was unable to do so.
  Apologies if I've accordingly missed something obvious.

  Compiz runs (for the most part) fine on my system. However, during rotation 
of the cube, instead of the background being completely
  filled with the skydome image, the skydome image takes a hyperbolic shape 
(see attached screenshot). Disabling the skydome results in a uniform black 
background as expected. This is reproduced on every reboot and simply by 
enabling the skydome. On this system, I've never had a normal-looking skydome. 
Additionally, when windows are present and I rotate the skydome, the windows 
streak across the background unless another window crosses the streak, which 
wipes it away (see second attached screenshot).

  Problems are reproduced with every cube rotation and persist after
  rebooting. After discussing the issue on the #compiz IRC channel, we
  concluded that the problem was not related to cube reflection (which
  is not enabled) or the image resolution (which is under
  MAX_TEXTURE_SIZE).

  Any thoughts on why this is happening or how to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 18 12:03:09 2014
  DistUpgraded: 2014-06-27 14:23:05,698 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f9]
  InstallationDate: Installed on 2014-01-29 (232 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 3443CTO
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=456834d4-a54c-4bc4-91e3-82586def6717 ro
  SourcePackage: compiz
  UpgradeStatus: Upgraded to trusty on 2014-06-27 (82 days ago)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3443CTO
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 15 07:04:13 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 898 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Desktop-packages] [Bug 272194] Re: webfav Add Shortcut text Add Favorite

2015-08-06 Thread Kyle Nitzsche

** Changed in: webfav
 Assignee: Kyle Nitzsche (knitzsche) = (unassigned)

** Changed in: webfav (Ubuntu)
 Assignee: Kyle Nitzsche (knitzsche) = (unassigned)

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

Title:
  webfav Add Shortcut text  Add Favorite

Status in Ubuntu Netbook Remix Launcher:
  Invalid
Status in webfav:
  Incomplete
Status in webfav package in Ubuntu:
  Incomplete

Bug description:
  Webfav, which is a mozilla add-on that enables the user to save the
  current web page as a link into the Favorites section of the Launcher,
  has slightly confusing text in the title bar of the dialog: Add
  Shortcut. It should be Add Favorite

To manage notifications about this bug go to:
https://bugs.launchpad.net/netbook-remix-launcher/+bug/272194/+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 1449268] Re: Allow disabling sending of state parameter

2015-08-04 Thread Kyle Nitzsche

** Changed in: savilerow
   Status: New = Fix Released

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

Title:
  Allow disabling sending of state parameter

Status in The Savilerow project:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released

Bug description:
  Some account providers are less-than-compliant when it comes to OAuth,
  and automatically sending a state parameter causes breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1449268/+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 1478272] [NEW] Any application using the GTK Headerbar minimize button crashed on minimize

2015-07-25 Thread Kyle

Public bug reported:

I am using Ubuntu 15.04
The application is my own
It can be downloaded in the following PPA: 
https://launchpad.net/~agronick/+archive/ubuntu/relay or in Github: 
https://github.com/agronick/Relay
The package is relay
When I click the minimize button I expect the program to minimize.
Instead compiz crashes. This ONLY happens on Compiz with themes that use the 
GTK Headerbar minimize button and not Ubuntu's. You can download it an see this 
problem. It affects other users as well.

I have an app and I set a different theme to use one that is darker. On
any theme where the minimize button is the square type build into the
headerbar on minimize compiz crashes. The app is fine. I am doing
nothing special to draw the minimize button. The app works fine on
anything besides compiz. If the minimize button is small and circular
like the default Ubuntu theme it minimizes fine.

Adwaita crashes as well as any other theme with square buttons in the
header bar.

The lines that set the theme are 128 and 129 in src/Relay.vala, This is:

if (on_ubuntu)
Gtk.Settings.get_default().gtk_theme_name = Adwaita;

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


** Tags: compiz crash minimize

** Description changed:

  I am using Ubuntu 15.04
  The application is my own
- It can be downloaded in the following PPA or in the Github link below: 
https://launchpad.net/~agronick/+archive/ubuntu/relay
+ It can be downloaded in the following PPA: 
https://launchpad.net/~agronick/+archive/ubuntu/relay or in Github: 
https://github.com/agronick/Relay
  The package is relay
  When I click the minimize button I expect the program to minimize.
- Instead compiz crashes. This ONLY happens on Compiz with themes that use the 
GTK Headerbar minimize buttons and not Ubuntu's.
+ Instead compiz crashes. This ONLY happens on Compiz with themes that use the 
GTK Headerbar minimize button and not Ubuntu's. You can download it an see this 
problem. It affects other users as well.
  
  I have an app and I set a different theme to use one that is darker. On
  any theme where the minimize button is the square type build into the
  headerbar on minimize compiz crashes. The app is fine. I am doing
  nothing special to draw the minimize button. The app works fine on
  anything besides compiz. If the minimize button is small and circular
  like the default Ubuntu theme it minimizes fine.
  
- This is the app: https://github.com/agronick/Relay
+ Adwaita crashes as well as any other theme with square buttons in the
+ header bar.
  
- Right now I am just hiding the minimize button on Ubuntu which is a
- terrible solution. If you delete lines 96 and 97 in src/main_window.vala
- which are:
- 
- else if (Relay.on_ubuntu)
-  toolbar.decoration_layout = maximize,close;
- 
- You'll get the minimize button back.
- 
- I set the theme on lines 128 and 129 in src/Relay.vala these are:
+ The lines that set the theme are 128 and 129 in src/Relay.vala, This is:
  
  if (on_ubuntu)
  Gtk.Settings.get_default().gtk_theme_name = Adwaita;
- 
- Adwaita crashes as well as any other theme with square buttons in the
- header bar.

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

Title:
  Any application using the GTK Headerbar minimize button crashed on
  minimize

Status in compiz package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 15.04
  The application is my own
  It can be downloaded in the following PPA: 
https://launchpad.net/~agronick/+archive/ubuntu/relay or in Github: 
https://github.com/agronick/Relay
  The package is relay
  When I click the minimize button I expect the program to minimize.
  Instead compiz crashes. This ONLY happens on Compiz with themes that use the 
GTK Headerbar minimize button and not Ubuntu's. You can download it an see this 
problem. It affects other users as well.

  I have an app and I set a different theme to use one that is darker.
  On any theme where the minimize button is the square type build into
  the headerbar on minimize compiz crashes. The app is fine. I am doing
  nothing special to draw the minimize button. The app works fine on
  anything besides compiz. If the minimize button is small and circular
  like the default Ubuntu theme it minimizes fine.

  Adwaita crashes as well as any other theme with square buttons in the
  header bar.

  The lines that set the theme are 128 and 129 in src/Relay.vala, This
  is:

  if (on_ubuntu)
  Gtk.Settings.get_default().gtk_theme_name = Adwaita;

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

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

[Desktop-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor

2015-07-24 Thread Kyle Fazzari

This happens to me on a Dell M3800 with _no_ external monitor. Probably
a few times a week. After anywhere from 5 minutes to a few hours, the
cursor comes back. I have to use the touchscreen until then. Man I hate
touchscreens.

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

Title:
  cursor sometimes disappears on XPS 13 9343 and external monitor

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using
  an external display port monitor. Occasionally, the mouse cursor
  disappears (sometimes after screen lock, other times just normal
  usage). I saw something on stack exchange that said this might help:

  gsettings set org.gnome.settings-daemon.plugins.cursor active false

  I've done this and it sometimes helps and sometimes doesn't. I've also
  just seen the cursor come back on its own after a few minutes without
  doing anything. Trying to interact with the touch screen, then the
  mouse has no effect. Unplugging and replugging the mouse has no
  effect. Using the touchpad has no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 22 11:19:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-06-13 (8 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet 
splash vt.handoff=7
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 10:53:54 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467595/+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 1470613] [NEW] instagram login fails

2015-07-01 Thread Kyle Nitzsche

Public bug reported:

Cannot log in with instagram scope: com.canonical.scopes.instagram
1.0.15

syslog shows this:
Jul  1 18:20:39 ubuntu-phablet signond[4887]: QObject::disconnect: Unexpected 
null parameter

(syslog attached)

current build number: 53
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-06-30 17:27:50
version version: 53
version ubuntu: 20150630.1
version device: 20150529-8e13c5f
version custom: 20150528-722-29-15-vivid

signon-plugin-oauth2:
  Installed: 0.22+15.04.20150603-0ubuntu1
  Candidate: 0.22+15.04.20150603-0ubuntu1
  Version table:
 *** 0.22+15.04.20150603-0ubuntu1 0
   1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
100 /var/lib/dpkg/status
 0.21+15.04.20150327-0ubuntu1 0
500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

** Affects: savilerow
 Importance: Undecided
 Status: New

** Affects: signon-plugin-oauth2 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: syslog
   https://bugs.launchpad.net/bugs/1470613/+attachment/4423063/+files/syslog

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

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

Title:
  instagram login fails

Status in The Savilerow project:
  New
Status in signon-plugin-oauth2 package in Ubuntu:
  New

Bug description:
  Cannot log in with instagram scope: com.canonical.scopes.instagram
  1.0.15

  syslog shows this:
  Jul  1 18:20:39 ubuntu-phablet signond[4887]: QObject::disconnect: Unexpected 
null parameter

  (syslog attached)

  current build number: 53
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-06-30 17:27:50
  version version: 53
  version ubuntu: 20150630.1
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

  signon-plugin-oauth2:
Installed: 0.22+15.04.20150603-0ubuntu1
Candidate: 0.22+15.04.20150603-0ubuntu1
Version table:
   *** 0.22+15.04.20150603-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.21+15.04.20150327-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1470613/+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 1449268] Re: Allow disabling sending of state parameter

2015-06-29 Thread Kyle Nitzsche

The can't log into Instagram bug 1466232 that was marked a dup of this
is not yet fixed.

phablet@ubuntu-phablet:~$ apt-cache policy signon-plugin-oauth2
signon-plugin-oauth2:
  Installed: 0.22+15.04.20150603-0ubuntu1

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 49
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-06-25 13:01:42
version version: 49
version ubuntu: 20150625
version device: 20150529-8e13c5f
version custom: 20150528-722-29-15-vivid


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

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

Title:
  Allow disabling sending of state parameter

Status in The Savilerow project:
  New
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released

Bug description:
  Some account providers are less-than-compliant when it comes to OAuth,
  and automatically sending a state parameter causes breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1449268/+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 1466232] Re: instagram scope login fails now

2015-06-29 Thread Kyle Nitzsche

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

I seem to have the pkg installed that fixes the bug this is marked a
duplicate of, but I still cannot log into Instagram.

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

Title:
  instagram scope login fails now

Status in The Savilerow project:
  New
Status in signon-plugin-oauth2 package in Ubuntu:
  Confirmed

Bug description:
  expecting details from cwayne...

  My experience is simply:
  * Login through scope fails
  * Scope continues to show login result
  * Settings  Accounts does not show instagram.

  current build number: 36
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-06-15 19:34:22
  version version: 36
  version ubuntu: 20150615.1
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1466232/+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 1466232] [NEW] instagram scope login fails now

2015-06-17 Thread Kyle Nitzsche

Public bug reported:

expecting details from cwayne...

My experience is simply:
* Login through scope fails
* Scope continues to show login result
* Settings  Accounts does not show instagram.

current build number: 36
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-06-15 19:34:22
version version: 36
version ubuntu: 20150615.1
version device: 20150529-8e13c5f
version custom: 20150528-722-29-15-vivid

** Affects: savilerow
 Importance: Undecided
 Status: New

** Affects: signon-plugin-oauth2 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  expecting details from cwayne...
  
  My experience is simply:
  * Login through scope fails
  * Scope continues to show login result
  * Settings  Accounts does not show instagram.
+ 
+ current build number: 36
+ device name: krillin
+ channel: ubuntu-touch/rc-proposed/bq-aquaris.en
+ last update: 2015-06-15 19:34:22
+ version version: 36
+ version ubuntu: 20150615.1
+ version device: 20150529-8e13c5f
+ version custom: 20150528-722-29-15-vivid

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

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

Title:
  instagram scope login fails now

Status in The Savilerow project:
  New
Status in signon-plugin-oauth2 package in Ubuntu:
  New

Bug description:
  expecting details from cwayne...

  My experience is simply:
  * Login through scope fails
  * Scope continues to show login result
  * Settings  Accounts does not show instagram.

  current build number: 36
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-06-15 19:34:22
  version version: 36
  version ubuntu: 20150615.1
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1466232/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad

2015-06-15 Thread Kyle

I just wanted to update. Its not fixed on EOS Freya.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Trusty:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad

2015-05-20 Thread Kyle

What would happen if I installed this on Freya? Would it break stuff?

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Trusty:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad

2015-05-20 Thread Kyle

I just tried it on EOS Freya. I had to force the install. Nothing has
locked up yet and everything appears to be working. I'll switch back to
Intel soon because Gala is broken on Freya.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Trusty:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1430459] [NEW] Mouse not working

2015-03-10 Thread Kyle Pierce

Public bug reported:

USB mouse worked fine upon installation.  Has since stopped working.
Unplug and plug in does not fix.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8.2
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: Tue Mar 10 12:39:25 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:022f]
   Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2015-03-10 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=60e2d5d1-f3aa-4e89-b9bf-0cf49e479a33 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Mar 10 12:00:35 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 769 
 vendor LPL
xserver.version: 2:1.16.0-1ubuntu1.3

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


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

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

Title:
  Mouse not working

Status in xorg package in Ubuntu:
  New

Bug description:
  USB mouse worked fine upon installation.  Has since stopped working.
  Unplug and plug in does not fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  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: Tue Mar 10 12:39:25 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:022f]
 Subsystem: Dell Device [1028:022f]
  InstallationDate: Installed on 2015-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=60e2d5d1-f3aa-4e89-b9bf-0cf49e479a33 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Desktop-packages] [Bug 1424119] Re: Edit Connections...now insensitive by default in network manager's menu

2015-03-02 Thread kyle

This also appears to disable 'Disconnect' from various networks (I have
2 networks connected, and I need to switch between them).  'Edit
Connections' is disable on my machine as well.

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

Title:
  Edit Connections...now insensitive by default in network manager's
  menu

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

Bug description:
  arno@arno-1000H:~$ lsb_release -rd
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04
  arno@arno-1000H:~$ apt-cache policy network-manager-gnome
  network-manager-gnome:
Installé : 0.9.4.1-0ubuntu2.4
Candidat : 0.9.4.1-0ubuntu2.4
   Table de version :
   *** 0.9.4.1-0ubuntu2.4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.4.1-0ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  
  Might be after upgrade to network-manager-gnome 0.9.4.1-0ubuntu2.4, the item 
Edit Connections... at the bottom of the network manager's menu is now 
insensitive i.e. grayed out, therefore user cannot configure his/her 
connections as indicated in 
http://docs.xubuntu.org/1204/internet-networks.html#network-connections

  workaround : launch /usr/bin/nm-connection-editor to display the
  network connections window and have access to the settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1424119/+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 269904] Re: Screen refresh problems with nvidia cards

2014-12-18 Thread Kyle Brenneman

That sounds like it's probably a different bug that's been uncovered by
this change, so I think a separate bug would be appropriate. If you've
still got a system handy that can reproduce it, the log from nvidia-bug-
report.sh would also be helpful.

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Triaged
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-fusion-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/269904/+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 1402438] [NEW] package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to install/upgrade: package gnome-themes-standard-data is already installed and configured

2014-12-14 Thread Kyle

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

Public bug reported:

package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to
install/upgrade: package gnome-themes-standard-data is already installed
and configured

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-themes-standard-data 3.10.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
AptdaemonVersion: 1.1.1-1ubuntu5.1
Architecture: amd64
Date: Sun Dec 14 14:43:16 2014
Dependencies:
 
DuplicateSignature: package:gnome-themes-standard-data:3.10.0-1ubuntu2:package 
gnome-themes-standard-data is already installed and configured
ErrorMessage: package gnome-themes-standard-data is already installed and 
configured
InstallationDate: Installed on 2014-12-09 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: gnome-themes-standard
Title: package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to 
install/upgrade: package gnome-themes-standard-data is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-themes-standard (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package trusty

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

Title:
  package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to
  install/upgrade: package gnome-themes-standard-data is already
  installed and configured

Status in gnome-themes-standard package in Ubuntu:
  New

Bug description:
  package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to
  install/upgrade: package gnome-themes-standard-data is already
  installed and configured

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-themes-standard-data 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  AptdaemonVersion: 1.1.1-1ubuntu5.1
  Architecture: amd64
  Date: Sun Dec 14 14:43:16 2014
  Dependencies:
   
  DuplicateSignature: 
package:gnome-themes-standard-data:3.10.0-1ubuntu2:package 
gnome-themes-standard-data is already installed and configured
  ErrorMessage: package gnome-themes-standard-data is already installed and 
configured
  InstallationDate: Installed on 2014-12-09 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-themes-standard
  Title: package gnome-themes-standard-data 3.10.0-1ubuntu2 failed to 
install/upgrade: package gnome-themes-standard-data is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1402438/+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 1273524] Re: LXDE guest session shows error message no session for pid pid for lxsession

2014-11-20 Thread Kyle Mallory

I see this bug has been triaged.  Is there a patch for it?  I'm trying
to build an information monitor/radiator machine, and am using lubuntu,
lightdm, and guest accounts to autologin and open firefox in fullscreen
mode to the radiator URL.

This particular bug (and the error dialog) is preventing the executiong
of /usr/lib/lightdm/guest-session-auto.sh until after the dialog is
cleared.

I'm happy to rebuild the package from source, if necessary.

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

Title:
  LXDE guest session shows error message no session for pid pid for
  lxsession

Status in One Hundred Papercuts:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lxsession” package in Ubuntu:
  Triaged

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error no session for pid pid for 
lxsession is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 850229] Re: Unread email count in thunderbird shown wrongly in messaging menu and launcher icon

2014-11-13 Thread Christopher Kyle Horton

@Pius Please don't change the bug status from Triaged to Confirmed
unless there's a reason for it. Triaged bugs are also confirmed by
definition. Also, Oneiric has already reached end-of-life status; do you
mean the bug is present in Ubuntu 14.04 instead?

** Tags added: trusty

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

Title:
  Unread email count in thunderbird shown wrongly in messaging menu and
  launcher icon

Status in Messaging Menu Thunderbird Extension:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  Fix Released
Status in “thunderbird” source package in Oneiric:
  Confirmed

Bug description:
  The number of unread emails is shown incorrectly in the messaging menu
  and unity launcher icon of thunderbird though thunderbird application
  shows the correct count. See the attached screenshot for the
  illustration.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0~b2+build2+nobinonly1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guruprasad   1650 F pulseaudio
  BuildID: 20110906005012
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf840 irq 47'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,103c30cc,0013 
HDA:10573055,10573055,00100700'
 Controls  : 21
 Simple ctrls  : 13
  Channel: default
  Date: Wed Sep 14 23:40:58 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8
  Profiles: Profile0 (Default) - LastVersion=7.0/20110906005012 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CB
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30CB:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv9700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/messagingmenu-extension/+bug/850229/+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 1385887] [NEW] Unable to mount DVD+R in 14.04

2014-10-26 Thread Kyle

Public bug reported:

Just installed a fresh copy of ubuntu 14.04 and when I put a blank dvd
in the drive it say Unable to mount DVD+R Disk, Location is already
mounted.

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unable to mount DVD+R in 14.04

Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  Just installed a fresh copy of ubuntu 14.04 and when I put a blank dvd
  in the drive it say Unable to mount DVD+R Disk, Location is already
  mounted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1385887/+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 1348254] Re: Dragging window to resize is reversed after resizing with keyboard

2014-10-16 Thread Kyle Coots

Here is a  Screen cast of what im experiencing.

** Attachment added: Screent of Bug
   
https://bugs.launchpad.net/compiz/+bug/1348254/+attachment/4238588/+files/asd.mp4

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

Title:
  Dragging window to resize is reversed after resizing with keyboard

Status in Compiz:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
After right-clicking the titlebar of a resizeable window and selecting 
resize, pressing the up arrow key to attach the cursor to the top edge of the 
window, resizing the window, and clicking or hitting enter to deselect the top 
edge, dragging the bottom edge of the window with the cursor no longer resizes 
the window in the proper direction.
Using the mouse to select the top edge or using the right-click, rezise, 
move method on the bottom edge still produce the right behavior.  This happens 
in all applications that use resizable windows.  I'm reproducing this bug with 
the default unity on Ubuntu 14.04.1 LTS

  I have attached a video demonstrating the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1348254/+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 1348254] Re: Dragging window to resize is reversed after resizing with keyboard

2014-10-15 Thread Kyle Coots

I am having the same issue but it does the same thing even without using
the keyboard to resize the window. Nothing I do seems to have an effect.
And its always the right side of the window that is reversed, the other
sides respond like normal.

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

Title:
  Dragging window to resize is reversed after resizing with keyboard

Status in Compiz:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
After right-clicking the titlebar of a resizeable window and selecting 
resize, pressing the up arrow key to attach the cursor to the top edge of the 
window, resizing the window, and clicking or hitting enter to deselect the top 
edge, dragging the bottom edge of the window with the cursor no longer resizes 
the window in the proper direction.
Using the mouse to select the top edge or using the right-click, rezise, 
move method on the bottom edge still produce the right behavior.  This happens 
in all applications that use resizable windows.  I'm reproducing this bug with 
the default unity on Ubuntu 14.04.1 LTS

  I have attached a video demonstrating the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1348254/+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 3 4 >

1 - 100 of 353 matches

Mail list logo