from:"PJSingh5000"

Screenshot of Other Updates Section

** Attachment added: "Screenshot of Other Updates Section"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772131/+attachment/5498798/+files/Screenshot%20of%20Other%20Updates%20Section%202021-05-19.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772131

Title:
  Software Update checkbox cropped

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772131] Re: Software Update checkbox cropped

Screenshot of Security Updates Section

** Attachment added: "Screenshot of Security Updates Section"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772131/+attachment/5498797/+files/Screenshot%20of%20Security%20Updates%20Section%202021-05-19.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772131

Title:
  Software Update checkbox cropped

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772131] Re: Software Update checkbox cropped

This issue seems to only occur when there are more than one category of
updates (Such as "Security updates" and "Other updates").

STEPS TO REPRODUCE
--
This issue occurs on Ubuntu 20.04 thru 21.04.

Ubuntu 20.04 version is over a year old, and there are both "Security"
and "Other" updates available, so it is a good environment to reproduce
this issue...

1. Boot into 21.04 Live ISO
2. Open Software Updater
3. Notice that Notice that the "Security updates" checkbox is cropped.
4. Notice that Notice that the "Other updates" checkbox is cropped.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772131

Title:
  Software Update checkbox cropped

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927558] Re: Check boxes in Software Updater are trimmed along left edge

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

** Description changed:

  Check boxes in the 1st column of the tree view in the "Details of
  updates" pane of Software Updater are trimmed along left edge.
  
  Please see the attached screenshot.
  
  The check boxes in the first column are always trimmed, regardless of
  the interface font or font size.
+ 
+ This issue seems to only occur when there are more than one category of
+ updates  (Such as "Security updates" and "Other updates").
+ 
+ STEPS TO REPRODUCE
+ --
+ This issue occurs on Ubuntu 20.04 thru 21.04.
+ 
+ Ubuntu 20.04 version is over a year old, and there are both "Security"
+ and "Other" updates available, so it is a good environment to reproduce
+ this issue...
+ 
+ 1. Boot into 21.04 Live ISO
+ 2. Open Software Updater
+ 3. Notice that Notice that the "Security updates" checkbox is cropped.
+ 4. Notice that Notice that the "Other updates" checkbox is cropped.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: update-manager 1:21.04.8
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  6 18:15:22 2021
  DpkgHistoryLog.txt:
-  Start-Date: 2021-05-04  14:29:51
-  Commandline: packagekit role='update-packages'
-  Upgrade: openvpn:amd64 (2.5.1-1ubuntu1, 2.5.1-1ubuntu1.1)
-  End-Date: 2021-05-04  14:29:53
+  Start-Date: 2021-05-04  14:29:51
+  Commandline: packagekit role='update-packages'
+  Upgrade: openvpn:amd64 (2.5.1-1ubuntu1, 2.5.1-1ubuntu1.1)
+  End-Date: 2021-05-04  14:29:53
  InstallationDate: Installed on 2021-04-28 (8 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927558

Title:
  Check boxes in Software Updater are trimmed along left edge

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927558] Re: Check boxes in Software Updater are trimmed along left edge

2021-05-17 Thread PJSingh5000

The issue occurs when there are more than one tree roots in the updates
list.

This is what I see...

   ] Security updates
 > Ubuntu base
   ] Other updates
 > Ubuntu base

The expander ">" is missing and the leftmost section of the checkbox is
cropped.

It should look like this...

> [] Security updates
 > Ubuntu base
> [] Other updates
 > Ubuntu base


** Attachment added: "The expander ">" is missing and the leftmost section of 
the checkbox is cropped."
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1927558/+attachment/5498349/+files/Screenshot%20from%202021-05-17%2020-26-30.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927558

Title:
  Check boxes in Software Updater are trimmed along left edge

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click

The issue has since been fixed and is not present in gtk3, version 3.24.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731581

Title:
  Context menus do not appear for Gtk text areas upon right-click

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737433] Re: Ubiquity automatically removes qt5-gtk-platformtheme, but this is needed to integrate KDE apps

I'm marking this bug as invalid, since it is so old.
I'm not sure this is an issue anymore.

** Changed in: ubiquity (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737433

Title:
  Ubiquity automatically removes qt5-gtk-platformtheme, but this is
  needed to integrate KDE apps

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output

Is this behavior a consequence of Bug #1926256 "Pasted text in the
terminal is always highlighted and selected" ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922276

Title:
  Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only
  visible part of terminal output

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

@Egmont,

You mean it will always be like this going forward?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -

Is this the feature you are referring to?...

f. New active mark and face feature: when enabled, it will highlight the text
   inserted by a bracketed paste (the `active region') and the text found by
   incremental and non-incremental history searches. This is tied to bracketed
   paste and can be disabled by turning off bracketed paste.

..or, is it this one?...

h. Bracketed paste mode is enabled by default.

If so, it looks like this "feature" can be disabled. How?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -

I find there is an inconsistency with this new approach:
If you've just pasted text, then highlight the text, the text looks 
unhighlighted.
This is visually confusing.

Perhaps this is an unintended consequence that needs remediation?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926256

Title:
  Pasted text in the terminal is always highlighted and selected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] lspci.txt

apport information

** Attachment added: "lspci.txt"
   https://bugs.launchpad.net/bugs/1927827/+attachment/5497799/+files/lspci.txt

** Changed in: cheese (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1927827/+attachment/5497797/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1927827/+attachment/5497798/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported

apport information

** Tags added: apport-collected

** Description changed:

  Attempting to run cheese on a HDPI display in Wayland results in the
  following errors:
  
  (cheese:9303): Gdk-CRITICAL **: 10:29:11.221:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed
  
  (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than
  65535 pixels are not supported
  
  When this error happens, the cheese window does not open.
  
  Sometimes the "Native Windows ... not supported" does not occur, the
  cheese window does open. However, the photo area is black. I can work
  around this problem by changing the "Photo resolution" in preferences to
  a different value, and then changing it back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
  Date: Sat May  8 10:32:03 2021
  InstallationDate: Installed on 2021-04-28 (10 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 15.43
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.11
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 1VW22AV
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2021-04-28 (17 days ago)
+ InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
+ MachineType: HP HP Spectre x360 Convertible 15-bl1XX
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: cheese 3.38.0-3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
+ RelatedPackageVersions:
+  cheese3.38.0-3
+  cheese-common 3.38.0-3
+ Tags:  hirsute gstreamer-error
+ Uname: Linux 5.11.0-17-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 12/15/2020
+ dmi.bios.release: 15.43
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F.43
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 827F
+ dmi.board.vendor: HP
+ dmi.board.version: 95.11
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.ec.firmware.release: 95.11
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP Spectre
+ dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
+ dmi.product.sku: 1VW22AV
+ dmi.sys.vendor: HP
+ lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
+  Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

** Attachment added: "CheeseDebug.txt.gz"
   
https://bugs.launchpad.net/bugs/1927827/+attachment/5497795/+files/CheeseDebug.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

To manage notifications

[Bug 1927827] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1927827/+attachment/5497796/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927558] Re: Check boxes in Software Updater are trimmed along left edge

I now see the expander icon (">") and the full check-box next to the
first item in the tree, under "Install or remove".

** Attachment added: "Software Updater showing the full check box for "Ubuntu 
base" updates.."
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1927558/+attachment/5497794/+files/Screenshot%20from%202021-05-15%2009-23-52.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927558

Title:
  Check boxes in Software Updater are trimmed along left edge

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927558] Re: Check boxes in Software Updater are trimmed along left edge

I now see the expander icon (">") and the full check-box next to the
first item in the tree, under "Install or remove".

I'll attach the screen shot.

The difference between this screen shot and the previous one (showing
the bug) is that the previous screen shot had "Security Updates"; this
one has "Ubuntu base".

I'm going to monitor this for a little longer to see if the bug
reappears under different circumstances.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927558

Title:
  Check boxes in Software Updater are trimmed along left edge

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] [NEW] Error launching cheese: Native Windows taller than 65535 pixels are not supported

2021-05-08 Thread PJSingh5000

Public bug reported:

Attempting to run cheese on a HDPI display in Wayland results in the
following errors:

(cheese:9303): Gdk-CRITICAL **: 10:29:11.221:
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
'GDK_IS_WAYLAND_WINDOW (window)' failed

(cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than
65535 pixels are not supported

When this error happens, the cheese window does not open.

Sometimes the "Native Windows ... not supported" does not occur, the
cheese window does open. However, the photo area is black. I can work
around this problem by changing the "Photo resolution" in preferences to
a different value, and then changing it back.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: cheese 3.38.0-3
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
Date: Sat May  8 10:32:03 2021
InstallationDate: Installed on 2021-04-28 (10 days ago)
InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
MachineType: HP HP Spectre x360 Convertible 15-bl1XX
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 cheese3.38.0-3
 cheese-common 3.38.0-3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2020
dmi.bios.release: 15.43
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.43
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827F
dmi.board.vendor: HP
dmi.board.version: 95.11
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 95.11
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
dmi.product.sku: 1VW22AV
dmi.sys.vendor: HP
lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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


** Tags: amd64 apport-bug gstreamer-error hirsute wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported

2021-05-08 Thread PJSingh5000

My laptop's native resolution is:

   3840x2160

and this is what I have selected as the display output in GNOME.

I am using 200% scaling.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927827

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown

2021-05-07 Thread PJSingh5000

Affects Ubuntu 21.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280300

Title:
  Desktop contents displayed on resume, before lock screen is shown

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927558] [NEW] Check boxes in Software Updater are trimmed along left edge

2021-05-06 Thread PJSingh5000

Public bug reported:

Check boxes in the 1st column of the tree view in the "Details of
updates" pane of Software Updater are trimmed along left edge.

Please see the attached screenshot.

The check boxes in the first column are always trimmed, regardless of
the interface font or font size.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: update-manager 1:21.04.8
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May  6 18:15:22 2021
DpkgHistoryLog.txt:
 Start-Date: 2021-05-04  14:29:51
 Commandline: packagekit role='update-packages'
 Upgrade: openvpn:amd64 (2.5.1-1ubuntu1, 2.5.1-1ubuntu1.1)
 End-Date: 2021-05-04  14:29:53
InstallationDate: Installed on 2021-04-28 (8 days ago)
InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Software Updater showing the trimmed check box."
   
https://bugs.launchpad.net/bugs/1927558/+attachment/5495345/+files/Screenshot%20from%202021-05-06%2018-15-02.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927558

Title:
  Check boxes in Software Updater are trimmed along left edge

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926862] [NEW] Unable to exit Activities Overview in Ubuntu 21.04

Public bug reported:

In Ubuntu 21.04, after entering the Activities Overview by clicking on
Activities, by using the hot corner, or by pressing the Super key, the
user is not able to exit the Activities Overview and return to the
Desktop.

The user can still open or close applications, or move applications to
different work spaces, but the user can not interact with open
applications or return to the normal GNOME desktop.

This issue occurs randomly.

The only remedy is to logout, restart gnome shell with Alt-F2, R if
using  Xorg.

This affects:
Ubuntu 21.04
gnome-shell 3.38.4-1ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
Date: Sat May  1 21:37:12 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-04-28 (3 days ago)
InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926862

Title:
  Unable to exit Activities Overview in Ubuntu 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] Re: Computer does not shut down

I am closing this bug report, since GDM is not causing the shutdown
issue.

** Changed in: gdm3 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] Re: Computer does not shut down

I was able to get my computer to reliably shutdown by doing two things:

 1. Update the intramfs:

$ sudo update-initramfs -u

I'm not sure why this was necessary, since I have the default 21.04
kernel:

5.11.0-16-generic

 2. Add `acpi=force` to /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force
modprobe.blacklist=nouveau"

...and update grub:

$ sudo update-grub

I'm not sure why this is necessary, since I have a newer BIOS.
This has never been necessary for prior versions of Ubuntu.
Nevertheless, my laptop will consistently not shut down without this 
parameter.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] Re: Computer does not shut down

I was able to capture a journalctl logs for a *successful* shutdown.

In this log, I see the same GDM error:

gdm.service: Main process exited, code=exited, status=1/FAILURE
gdm.service: Failed with result 'exit-code'

Therefore, I must conclude that GDM is not the culprit in the shutdown
problem reported in this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] Re: Computer does not shut down

Jourrnalctl log of Xorg successful shutdown (no timestamps to facilitate
comparison).

** Attachment added: "Jourrnalctl log of Xorg successful shutdown (no 
timestamps to facilitate comparison)."
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926816/+attachment/5494136/+files/journal_ctl_2021-04-30-05%20Xorg%20Successful%20Shutdown%20-%20No%20Timestamps.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] Re: Computer does not shut down

Jourrnalctl log of Xorg unsuccessful shutdown (no timestamps to
facilitate comparison).

** Attachment removed: "Journalctl log from prior unsuccessful shutdown."
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926816/+attachment/5493993/+files/journal_ctl_2021-04-30-02.txt

** Attachment added: "Jourrnalctl log of Xorg unsuccessful shutdown (no 
timestamps to facilitate comparison)."
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926816/+attachment/5494135/+files/journal_ctl_2021-04-30-02%20Xorg%20Unsuccessful%20Shutdown%20-%20No%20Timestamps.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] [NEW] Computer does not shut down

2021-04-30 Thread PJSingh5000

Public bug reported:

In Ubuntu 21.04, when I shut down, my laptop never actually shuts down.

I see a black screen, the laptop stays on, and the fans spin up.

The computer will stay in this state all night.

I then have to press and hold the power button to shut down the device.

I am using the default kernel, 5.11.0-16-generic.
I am also using the Nvidia driver (nvidia-driver-460, version 
460.73.01-0ubuntu1) with XOrg.

This was not an issue for prior releases of Ubuntu on this machine. For
example, Ubuntu 20.04 does not have this problem.

I see the following messages in the journalctl log (attached) for
gdm.service, which I think may be contributing to this issue:

gdm.service: Main process exited, code=exited, status=1/FAILURE
gdm.service: Failed with result 'exit-code'.
Stopped GNOME Display Manager.
gdm.service: Triggering OnFailure= dependencies.
Requested transaction contradicts existing jobs: Transaction for 
plymouth-quit.service/start is destructive (umount.target has 'start' job 
queued, but 'stop' is included in transaction).
gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for 
plymouth-quit.service/start is destructive (umount.target has 'start' job 
queued, but 'stop' is included in transaction).

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gdm3 3.38.2.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
Date: Fri Apr 30 19:09:43 2021
InstallationDate: Installed on 2021-04-28 (2 days ago)
InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Journalctl log from prior unsuccessful shutdown."
   
https://bugs.launchpad.net/bugs/1926816/+attachment/5493993/+files/journal_ctl_2021-04-30-02.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

2021-04-27 Thread PJSingh5000

Ubuntu 21.04 uses the following vte packages:

libvte-2.91-0, version 0.62.3-1ubuntu1
libvte-2.91-common, version 0.62.3-1ubuntu1
gir1.2-vte-2.91, version 0.62.3-1ubuntu1

Ubuntu 20.04 uses the following vte packages:
libvte-2.91-0, version 0.60.1-1ubuntu1
libvte-2.91-common, version 0.60.1-1ubuntu1
gir1.2-vte-2.91, version 0.60.1-1ubuntu1

In Ubuntu 21.04, when text is pasted into Gnome Terminal, the text is
always highlighted.

- It appears as if the text is selected, but it is only highlighted.
- If you right-click on this highlighted text, the "Copy" option is actually 
disabled.
- Clicking in the terminal or clicking on the highlighted text does not 
un-highlight the text.
- The only way to un-highlight the pasted text is to type a key.
- If you try to select the highlighted text by clicking and dragging the mouse 
pointer, the text color actually inverts, and the text looks like it is not 
selected, when it in fact is selected. enter image description here

This confusing behavior is not present in Ubuntu 20.04.

- In Ubuntu 20.04, when text is pasted into Gnome Terminal, the text is not 
highlighted.
- Then, selecting the text highlights it, as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926256

Title:
  Pasted text in the terminal is always highlighted and selected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output

2021-04-27 Thread PJSingh5000

The "Select All" shortcut, when enabled, only selects text from the end
of the buffer that fits precisely within the height of the terminal.

For example

1. Type `ls -l /lib/*` and press Enter.
2. Scroll the terminal to the beginning.
3. Select all using your configured shortcut (Ctrl-Shift-A in my case).
4. Notice that no text is selected.
5. Then scroll the terminal to the bottom.
6. Notice all of the text that fits within the terminal window size is selected.
7. You can expand the terminal vertically to see that text above this area is 
not selected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922276

Title:
  Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only
  visible part of terminal output

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2021-02-26 Thread PJSingh5000

I am using nvidia-driver-460 version 460.39-0ubuntu0.20.04.1.

xserver-common version 2:1.20.9-2ubuntu1.2~20.04.1
xserver-xephyr version 2:1.20.9-2ubuntu1.2~20.04.1
xserver-xorg version 1:7.7+19ubuntu14
xserver-xorg-core version 2:1.20.9-2ubuntu1.2~20.04.1

The GDM screen would only appear after typing Ctrl+Alt+F2 followed by
Ctrl+Alt+F1.

The following seems to have fixed the issue for me, and the GDM screen
now appears without having to resort to the above "trick".

 1. Edit the file /lib/udev/rules.d/61-gdm.rules.

sudo nano /lib/udev/rules.d/61-gdm.rules

The original file looks like this:

# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", 
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

Comment all of the lines as shown:

# disable Wayland on Hi1710 chipsets
# ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", 
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
# DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

Type Ctrl+X to exit, then Y, and then Enter to save the file.

 2. Ensure that the Wayland is not disabled in GDM.

sudo nano /etc/gdm3/custom.conf

Comment the "WaylandEnable" line, if it is not already commented, as
shown:

# WaylandEnable=false

Type Ctrl+X to exit. If you made changes, type Y, and then Enter to
save the file.

 3. Finally, reboot.

Explanation

The /lib/udev/rules.d/61-gdm.rules file is supposed to prevent GDM from
displaying the Wayland session option when the NVIDIA proprietary
drivers are installed, since NVIDIA does not support Wayland.

However, in Ubuntu 20.04, there seems to be another redundant mechanism
or rule that also prevents GDM from displaying the Wayland session
option. I suspect this, because even after making the above change, the
Wayland session option is still not displayed in GDM. (Setting
WaylandEnable=true in /etc/gdm3/custom.conf has no effect).

Therefore, I have a hunch that there are two conflicting rules, and
disabling one of the rules (i.e. /lib/udev/rules.d/61-gdm.rules) seems
to remove the conflict.

Here is the journalctl boot log before making the above changes. You can
see there is an error loading the "fb" module.

/usr/lib/gdm3/gdm-x-session[964]: (II) Loading sub module "fb"
/usr/lib/gdm3/gdm-x-session[964]: (II) LoadModule: "fb"
/usr/lib/gdm3/gdm-x-session[964]: (II) Loading /usr/lib/xorg/modules/libfb.so
/usr/lib/gdm3/gdm-x-session[964]: (II) Module fb: vendor="X.Org Foundation"
/usr/lib/gdm3/gdm-x-session[964]: compiled for 1.20.9, module version = 
1.0.0
/usr/lib/gdm3/gdm-x-session[964]: ABI class: X.Org ANSI C Emulation, 
version 0.4
/usr/lib/gdm3/gdm-x-session[964]: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
/usr/lib/gdm3/gdm-x-session[964]: (EE)
/usr/lib/gdm3/gdm-x-session[964]: (EE) Backtrace:
/usr/lib/gdm3/gdm-x-session[964]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x55936e23a59c]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 
(funlockfile+0x60) [0x7f70b994541f]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7f70b978218b]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7f70b9761859]
/usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info 
found [-10]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 
(?+0x0) [0x7f70b976171a]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 
(__assert_fail+0x46) [0x7f70b9772f36]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 6: /usr/lib/xorg/Xorg 
(dixRegisterPrivateKey+0x239) [0x55936e0f7ac9]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_init+0xcf) [0x7f70b4b9735f]
/usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info 
found [-10]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f70b87fcc00]
/usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info 
found [-10]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 9: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f70b87f4dd0]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 10: /usr/lib/xorg/Xorg 
(AddGPUScreen+0xf5) [0x55936e0d92d5]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 11: /usr/lib/xorg/Xorg 
(xf86PlatformMatchDriver+0xa44) [0x55936e134cf4]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 12: /usr/lib/xorg/Xorg 
(xf86PlatformDeviceCheckBusID+0x225) [0x55936e13a035]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 13: /usr/lib/xorg/Xorg 
(config_fini+0xa4a) [0x55936e1368da]
/usr/lib/gdm3/gdm-x-session[964]: (EE) 14: /usr/lib/xorg/Xorg 
(config_fini+0x15eb) [0x55936e13810b]

[Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2021-02-26 Thread PJSingh5000

Could this be a regression of Bug #1792932 ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811023

Title:
  Xorg aborts with ../../../../dix/privates.c:384:
  dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1811023/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909699] [NEW] Please upgrate to Meld 3.21 for Hirsute Hippo

2020-12-30 Thread PJSingh5000

Public bug reported:

Meld 3.21 integrates better with the recent versions of Ubuntu.
Please consider upgrading the deb package to version 3.21.x for Hirsute Hippo.

References:

https://askubuntu.com/a/1302505/100356

https://github.com/GNOME/meld

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

** Attachment added: "Screenshot of Meld 3.21.1"
   
https://bugs.launchpad.net/bugs/1909699/+attachment/5448113/+files/Screenshot%20from%202020-12-30%2018-20-55.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909699

Title:
  Please upgrate to Meld 3.21 for Hirsute Hippo

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880277] Re: Ubiquity crashes on while installing Ubuntu 20.04

2020-05-23 Thread PJSingh5000

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

** This bug has been marked a duplicate of bug 1880344
   Cubic Experimental - Ubiquity crashes during installation of a customized ISO

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880277

Title:
  Ubiquity crashes on while installing Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04

2020-05-23 Thread PJSingh5000

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

** This bug has been marked a duplicate of bug 1880344
   Cubic Experimental - Ubiquity crashes during installation of a customized ISO

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880263

Title:
  Ubiquity consistently crashes in Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880277] [NEW] Ubiquity crashes on while installing Ubuntu 20.04

2020-05-23 Thread PJSingh5000

Public bug reported:

Ubiquity crashes on while installing Ubuntu 20.04

Options selected:
~ Normal install
~ Do not download updates
~ Something else
~ Selected install partition, efi partition, and mount points for two 
additional partitions
~ All partitions were ext4 (except efi partition)

Ubiquity crashed when the install was almost complete.

Ubiquity displayed "Configuring apt" expander.

The following output was visible on the terminal window below the
expander:

May 23 02:08:10 ubuntu /plugininstall.py:
ubiquity.install_misc.InstallStepError: AptSetup failed with code 1

May 23 02:08:10 ubuntu /plugininstall.py

/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:17: Warning: 
Source ID 8302 was not found when attempting to remove it
  GLib.source_remove(self.timeout_id)

/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:133: Warning: 
Source ID 8475 was not found when attempting to remove it
  GLib.source_remove(self.rows_changed_id)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Sat May 23 02:09:41 2020
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper 
iso-scan/filename=/ubuntu.iso noprompt noeject
LiveMediaBuild: Ubuntu 20.04.0 2020.05.23 LTS "Custom Focal Fossa" (20200523)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880277

Title:
  Ubiquity crashes on while installing Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04

2020-05-22 Thread PJSingh5000

When I try to re-run ubiquity, I get the error, ubi-partman failed with
exit code 10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880263

Title:
  Ubiquity consistently crashes in Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04

2020-05-22 Thread PJSingh5000

Ubiquity crashes when installation is almost finished.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880263

Title:
  Ubiquity consistently crashes in Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880263] [NEW] Ubiquity consistently crashes in Ubuntu 20.04

2020-05-22 Thread PJSingh5000

Public bug reported:

It's not clear what the bug or issue is.
Attempting to install Ubuntu 20.04 on HP Spectre.

The only message I see on the command line is...
$ ubiquity
/usr/bin/ubiquity:74: DeprecationWarning: the imp module is deprecated in 
favour of importlib; see the module's documentation for alternative uses
  import imp

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Fri May 22 23:23:08 2020
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper acpi=off 
iso-scan/filename=/ubuntu.iso noprompt noeject
LiveMediaBuild: Ubuntu 20.04.0 2020.05.23 LTS "Custom Focal Fossa" (20200522)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880263

Title:
  Ubiquity consistently crashes in Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI

2020-05-04 Thread PJSingh5000

I did additional testing, and I can confirm that adding "rmmod tpm" does
indeed work...

See comment number 51 by Alkis
(https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/comments/51).

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
menuentry "Install" {
set isofile="/ubuntu.iso"
rmmod tpm
loopback loop (hd0,2)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile 
noprompt noeject
initrd (loop)/casper/initrd
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

The Busy Box error I had experienced was actually due to a bad ISO file.

I tested "rmmod tpm" on a system running Ubuntu 19.10.

I tested two official Ubuntu *.iso files:
- Ubuntu 18.04
- Ubuntu 20.04

In both cases, the system successfully booted the specified *.iso.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  loopback command hangs in 2.04 under UEFI

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI

2020-05-04 Thread PJSingh5000

@Alkis Georgopoulos,

Thanks for the suggestion.
I added "rmmod tpm".
Unfortunately, it did not really help my situation...

$ sudo update-grub
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-51-generic
Found initrd image: /boot/initrd.img-5.3.0-51-generic
Found linux image: /boot/vmlinuz-5.3.0-46-generic
Found initrd image: /boot/initrd.img-5.3.0-46-generic
Adding boot menu entry for EFI firmware configuration
done
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

$ sudo nano /etc/grub.d/40_custom
$ sudo update-grub
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-51-generic
Found initrd image: /boot/initrd.img-5.3.0-51-generic
Found linux image: /boot/vmlinuz-5.3.0-46-generic
Found initrd image: /boot/initrd.img-5.3.0-46-generic
Adding boot menu entry for EFI firmware configuration
done
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

$ cat /etc/grub.d/40_custom
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type 
the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.

menuentry "Install" {
set isofile="/ubuntu.iso"
rmmod tpm
loopback loop (hd0,2)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile 
noprompt noeject
initrd (loop)/casper/initrd
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

Prior to this change, I would get a blank screen with a whirring fan.

With the above change, I do see the boot-up log messages.
But, I get a busy box...
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
BusyBox v1.301 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) Begin:  Running /scripts/casper-premount ... done.
Begin: waiting for devs... ... done.
touch /dev/.initramfs/lupin-waited-for-devs: No such file or directory
stdin: Invalid argument
done.
loop: can't get info on device /dev/loop1: No such device or address
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

I don't know why it is referencing "loop1" ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  loopback command hangs in 2.04 under UEFI

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1181666]

2020-01-19 Thread PJSingh5000

I'm using 3.34.1 in Ubuntu 19.10, and I don't experience this issue
anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard.

2019-11-26 Thread PJSingh5000

James,

Per comment #5 (https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1723678/comments/5) you should probably open a new bug
report, and link this old bug.

(Also, add a comment here with the link to the new bug report, so folks
that are subscribed to this bug and are also still experiencing this
issue can indicate that they are impacted).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723678

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'. | This was previously supported, but is not correct
  according to the ES6 standard.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error

2019-11-15 Thread PJSingh5000

* Ximin, apologies for the misspelling of your name; the spellcheck
override what I had typed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  Grub 2.04 Out of memory error, No server error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error

2019-11-15 Thread PJSingh5000

Coming,

This is good research.
Thanks for testing.
Perhaps the cause is a secondary library or dependency that iso9660.mod is 
using?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  Grub 2.04 Out of memory error, No server error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error

2019-11-12 Thread PJSingh5000

Does anyone know which package contains the iso9660 module for grub?

Would it be possible to copy the iso9660 module from the the 19.04 or
18.04 Ubuntu releases (e.g. grub 2.02), and explicitly load it before
executing the loopback command?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  Grub 2.04 Out of memory error, No server error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error

2019-11-07 Thread PJSingh5000

I can confirm that Booting ISO files from BIOS in Ubuntu 19.10 works fine.
UEFI seems to have the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  Grub 2.04 Out of memory error, No server error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error

2019-11-06 Thread PJSingh5000

During bootup, I enter the grub2 command-line by pressing c on the Grub
menu.

When I type the following command...

loopback loop (hd0,gpt2)/ubuntu-19.10-desktop-amd64.iso

...grub hangs, there is no more output or activity on the terminal, and
eventually the laptop fans spin up because the laptop gets hot.

The path (hd0,gpt2)/ubuntu-19.10-desktop-amd64.iso is valid on my
system.

I am experiencing this in Ubuntu 19.10 and did not have this issue in
prior Ubuntu releases.

The version of grub2 and grub2-common I have is 2.04-1ubuntu12.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311

Title:
  Grub 2.04 Out of memory error, No server error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-04-25 Thread PJSingh5000

I am using 18.10 and I have not yet experienced this issue.

For me, in 18.04, something that consistently triggered this bug was
whenever I accidentally touched the touch-screen on my laptop while
adjusting it.

In 19.04, I am able to interact with the touch-screen using my fingers,
and this issue has not appeared yet.

Also, I never used workspace related extensions. So, it is possible that
there are multiple issues here, that all have the same symptom. Perhaps
there is a common underlying cause, such as a memory issue, as Daniel
van Vugt had suggested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825919] Re: Gedit right click context menu stops working

2019-04-25 Thread PJSingh5000

It just happened now...

When this happened, I had right clicked on a misspelled work in a
Firefox text area. I didn't get a popup context menu; I thought it was
just Firefox acting up.

So, I switched to my open Gedit window, to cut the correctly spelled
word from my text document, and the context menu in Gedit wouldn't work
either.

It didn't work for a while. But as I started to research and copy logs
in order to collect information to post here, the right click context
menu magically started to work again, after some time.

I'll post the journalctl out put here. The issue happened around 10:19
in the logs...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825919

Title:
  Gedit right click context menu stops working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825919] Re: Gedit right click context menu stops working

2019-04-25 Thread PJSingh5000

Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded.
Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != 
NULL' failed
Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 
comm="/usr/bin/gnome-shell " label="unconfined")
Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.Logs'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' 
(uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' 
(uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="u
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.Characters.BackgroundService' requested by ':1.15' 
(uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 
comm="/usr/bin/gnome-shell " label="unconfined")
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 
pid=1936 comm="/usr/bin/gnome-shell " label="unconf
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.clocks'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.seahorse.Application'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.Characters.BackgroundService'
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.Calculator.SearchProvider'
Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search 
provider org.gnome.seahorse.Application.desktop during GetResultMetas: 
Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M
Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned 
by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0
Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after 
attribute name “Less-than” of element “:”
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 
pid=1936 comm="/usr/bin/gnome-shell " label="unconf
Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon...
Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all 
features are available
Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 
(series 16; classic) ubuntu/19.04 (amd64) linux/5.0.0-13-generic.
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.seahorse.Application'
Apr 25 10:19:21 PS006 systemd[1]: tmp-sanity\x2dmountpoint\x2d888950326.mount: 
Succeeded.
Apr 25 10:19:21 PS006 systemd[1745]: 
tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded.
Apr 25 10:19:21 PS006 systemd[1217]: 
tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded.
Apr 25 10:19:21 PS006 systemd[1]: Started Snappy daemon.
Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after 
attribute name “Less-than” of element “:”
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 
pid=1936 comm="/usr/bin/gnome-shell " label="unconf
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] 
Successfully activated service 'org.gnome.seahorse.Application'
Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search 
provider org.gnome.seahorse.Application.desktop during GetResultMetas: 
Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMet
Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned 
by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0
Apr 25 10:19:21 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != 
NULL' failed
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating 
service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 
comm="/usr/bin/gnome-shell " label="unconfined")
Apr 25 10:19:21 PS006

[Bug 1825919] Re: Gedit right click context menu stops working

2019-04-23 Thread PJSingh5000

NON_DEFAULT EXTENSIONS
--

Dash to Dock
https://extensions.gnome.org/extension/307/dash-to-dock/
Note: I have removed gnome-shell-extension-ubuntu-dock

Bluetooth Quick Connect
https://extensions.gnome.org/extension/1401/bluetooth-quick-connect/

Caffeine [INACTIVE]
https://extensions.gnome.org/extension/517/caffeine/

Clipboard Indicator
https://extensions.gnome.org/extension/779/clipboard-indicator/

Coverflow Alt-Tab
https://extensions.gnome.org/extension/97/coverflow-alt-tab/

Printers
https://extensions.gnome.org/extension/1218/printers/

Refresh Wifi Connections
https://extensions.gnome.org/extension/905/refresh-wifi-connections/

Sound Input & Output Device Chooser
https://extensions.gnome.org/extension/906/sound-output-device-chooser/

TLP Switcher
https://extensions.gnome.org/extension/1212/tlp-switcher/

DEFAULT EXTENSIONS
--

Desktop Icons [INACTIVE]
Note: Default Ubuntu extension

Ubuntu appindicators
Note: Default Ubuntu extension


GEDIT PLUGINS
-

I have the following Gedit plugin packages installed:
1. gedit-plugins
2. gedit-source-code-browser-plugin

The following Gedit plugins are activated:
Character Map
Code Comment
Document Statistics
File Browser Panel
Find in Files
Insert Date/Time
Join/Split Lines
Smart Spaces
Sort
Source Code Browser
Spell Checker
Word Completion
Zeitgeist dataprovider

REPRODUCING ISSUE
-

I haven't been able to find a consistent way to reproduce this issue...

It occurs after using Gedit for a long time.
I use Gedit heavily, open many tabs, and open local and remote text documents.
I do  lot of cut-and-paste, I use the right-click context menu a frequently to 
cut or paste text.

While using Gedit, I simultaneously use Meld, and sometimes I have the same 
document(s) open in Gedit and in Meld.
I may edit a document at the same time in Meld and in Gedit. (When I do this, I 
simply reload the file when Meld or Gedit warn me that a file has changed).
One extension that I use heavily is Clipboard Indicator.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825919

Title:
  Gedit right click context menu stops working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825919] Re: Right click context menu stops working

I see this in my application logs:

Unable to parse accelerator ???:ignored request to install 6
accelerators

(Where ??? is a non-printing character).

** Description changed:

  The Gedit text area right-click context menu stops appearing.
  
- This bug affects Ubuntu 19.10, but may be a regression of old Bug
+ This bug affects Ubuntu 19.04, but may be a regression of old Bug
  #1731581 from Ubuntu 17.10.
  
  Gedit version: 3.32.0-3
  Fresh install of Ubuntu 19.04
  gkt-3 version: 3.24.8-1ubuntu1
  
  RECREATING ISSUE
  
  When I first log in, the right-click context menus in Gedit works fine.
  After some time of usage, the right-click context menu no longer appears.
  
  SIDE-EFFECT
  
  A side-effect of this issue is that the mouse cursor does not revert to
  a pointer style after doing a right-click. It retains the "I" (Insert)
  shape even when you hover outside Gedit's text area.

** Summary changed:

- Right click context menu stops working
+ Gedit right click context menu stops working

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825919

Title:
  Gedit right click context menu stops working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

Still present in Ubuntu 19.04, fresh install.

(Although, now, clicking twice seems to bring up the authentication
dialog, and you don't have to click very rapidly).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

Ubuntu version 19.04
GTK3 version 3.24.8-1ubuntu1
Gnome Shell Version 3.32.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825919] [NEW] Right click context menu stops working

Public bug reported:

The Gedit text area right-click context menu stops appearing.

This bug affects Ubuntu 19.10, but may be a regression of old Bug
#1731581 from Ubuntu 17.10.

Gedit version: 3.32.0-3
Fresh install of Ubuntu 19.04
gkt-3 version: 3.24.8-1ubuntu1

RECREATING ISSUE

When I first log in, the right-click context menus in Gedit works fine.
After some time of usage, the right-click context menu no longer appears.

SIDE-EFFECT

A side-effect of this issue is that the mouse cursor does not revert to
a pointer style after doing a right-click. It retains the "I" (Insert)
shape even when you hover outside Gedit's text area.

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

** Description changed:

  The Gedit text area right-click context menu stops appearing.
  
- This may be a regression of old Bug #1731581 from Ubuntu 17.10.
+ This bug affects Ubuntu 19.10, but may be a regression of old Bug
+ #1731581 from Ubuntu 17.10.
  
- Gedit version: 3.32.0-3
- Fresh install of Ubuntu 19.04
- gkt-3 version: 3.24.8-1ubuntu1
+ Gedit version: 3.32.0-3
+ Fresh install of Ubuntu 19.04
+ gkt-3 version: 3.24.8-1ubuntu1
  
  RECREATING ISSUE
  
  When I first log in, the right-click context menus in Gedit works fine.
  After some time of usage, the right-click context menu no longer appears.
  
  SIDE-EFFECT
  
  A side-effect of this issue is that the mouse cursor does not revert to
  a pointer style after doing a right-click. It retains the "I" (Insert)
  shape even when you hover outside Gedit's text area.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825919

Title:
  Right click context menu stops working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

For reference, here are the upstream bugs:

GITLAB:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

BUGZILLA:
https://bugzilla.gnome.org/show_bug.cgi?id=724935
https://bugzilla.gnome.org/show_bug.cgi?id=703046

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738676

Title:
  With natural scrolling, horizontal sliders behave backwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

This bug is still being tracked in bugzilla.

** Bug watch added: GNOME Bug Tracker #724935
   https://gitlab.gnome.org/724935

** Changed in: gnome-shell
   Status: New => Unknown

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 => GNOME Bug 
Tracker #724935

** Bug watch added: GNOME Bug Tracker #703046
   https://gitlab.gnome.org/703046

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738676

Title:
  With natural scrolling, horizontal sliders behave backwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

Oops, I meant to say, "Less than *4* doesn't work, and more than 4 are
not necessary."

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

I opened this issue against gnome-shell, upstream.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

I did not report this bug against gtk+3.0. Should I do that as well?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1159
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738676

Title:
  With natural scrolling, horizontal sliders behave backwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740894] Re: KEY_RFKILL is not passed to userspace

Works on 18.10 x64 for me...

$ sudo apt update
$ sudo apt install --reinstall libxkbcommon0 libxkbcommon-x11-0 xkb-data

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740894

Title:
  KEY_RFKILL is not passed to userspace

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

Interesting...

I tried that, and I noticed that 4 rapid clicks (actually taps on my
touchpad) consistently brings up the pkexec password box. Less than 3
doesn't work, and more than 4 are not necessary.

Once you've been authenticated, you are able to make changes on the
Other Software tab, as you would expect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

Sam James Houlbrook,

If you are still having this problem, after updating, you'll need to
open a new bug report, since a fix was released.

(I am able to type capital enters using the onscreen keyboard in 18.10,
so I can't test this in 18.04).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730211

Title:
  Unable to type capital letters using onscreen keyboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon

2018-10-26 Thread PJSingh5000

Marco,

I tried the extension level patch at https://github.com/micheleg/dash-
to-dock/issues/128#issuecomment-432913072.

Here are my findings...

#1
It worked great for preventing two instances of am application from launching 
when touching an icon on the dock.

#2
However, touching the App Grid Icon still does not work. (It seems like the App 
Grid is unresponsive, but what is really happening is that the applications 
overview appears briefly and suddenly disappears, as if you had tapped on the 
App grid Icon twice).

Does the fix at https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/272 resolve item #2 above?

System Info...

$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename:   cosmic

$ gnome-shell --version
GNOME Shell 3.30.1

$ uname -r
4.18.0-10-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745888

Title:
  Two instances of a program launch whenever you touch a favorites icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon

2018-10-24 Thread PJSingh5000

I'm willing to help test this, so please let me know what to do.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745888

Title:
  Two instances of a program launch whenever you touch a favorites icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

The fact that the Dash is visible on the desktop ~immediately after~ a
touch event seems to be contributing to the problem.

See this experiment I did...

https://github.com/micheleg/dash-to-
dock/issues/128#issuecomment-423012581

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384

Title:
  On touch screens, the apps icon in the dock does not open when touched

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

Reading through the bug report linked by Daniel van Vugt (vanvugt) in
comment #24 (https://github.com/micheleg/dash-to-dock/issues/128), I
noticed that Dash-to-Dock is only affected.

I had uninstalled the Ubuntu Dock...
$ sudo apt autoremove --purge gnome-shell-extension-ubuntu-dock

However, I was using the Dash-to-Dock extension, instead.
$ sudo apt install gnome-shell-extension-dashtodock

So, I disabled Dash-to-Dock.
Now the problem is gone.

Are all of you using either Dash-to-Dock or the Ubuntu-Dock?
If so, what happens when you disable or remove it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384

Title:
  On touch screens, the apps icon in the dock does not open when touched

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

I'll go first...


$ sudo dmidecode | grep -A9 "System Information"
System Information
Manufacturer: HP
Product Name: HP Spectre x360 Convertible 15-bl1XX
Version:  
Serial Number: 5CD74284QL
UUID: 37444335-3234-3438-514C-4C3432344435
Wake-up Type: Power Switch
SKU Number: 1VW22AV
Family: 103C_5335KV HP Spectre


$ sudo lshw -short
H/W path   Device  Class  Description
=
   system HP Spectre x360 Convertible 15-bl1XX 
(1VW22AV)
/0 bus827F
/0/0   memory 64KiB BIOS
/0/10  memory 16GiB System Memory
/0/10/0memory 8GiB SODIMM DDR4 Synchronous Unbuffered 
(Unregistered) 2667 MHz (0.4 ns)
/0/10/1memory 8GiB SODIMM DDR4 Synchronous Unbuffered 
(Unregistered) 2667 MHz (0.4 ns)
/0/14  memory 256KiB L1 cache
/0/15  memory 1MiB L2 cache
/0/16  memory 8MiB L3 cache
/0/17  processor  Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
/0/100 bridge Intel Corporation
/0/100/2   displayIntel Corporation
/0/100/4   genericSkylake Processor Thermal Subsystem
/0/100/13  genericIntel Corporation
/0/100/14  busSunrise Point-LP USB 3.0 xHCI Controller
/0/100/14/0usb1busxHCI Host Controller
/0/100/14/0/5  multimedia HP TrueVision FHD RGB-IR
/0/100/14/0/7  communication  Bluetooth wireless interface
/0/100/14/1usb2busxHCI Host Controller
/0/100/14.2genericSunrise Point-LP Thermal subsystem
/0/100/15  genericSunrise Point-LP Serial IO I2C Controller 
#0
/0/100/16  communication  Sunrise Point-LP CSME HECI #1
/0/100/1c  bridge Intel Corporation
/0/100/1c/0displayNVIDIA Corporation
/0/100/1c.4bridge Sunrise Point-LP PCI Express Root Port #5
/0/100/1c.6bridge Sunrise Point-LP PCI Express Root Port #7
/0/100/1c.6/0  wlo1networkWireless 8265 / 8275
/0/100/1c.7bridge Sunrise Point-LP PCI Express Root Port #8
/0/100/1c.7/0  genericRTS525A PCI Express Card Reader
/0/100/1d  bridge Sunrise Point-LP PCI Express Root Port #9
/0/100/1d/0storageToshiba America Info Systems
/0/100/1f  bridge Intel Corporation
/0/100/1f.2memory Memory controller
/0/100/1f.3multimedia Intel Corporation
/0/100/1f.4busSunrise Point-LP SMBus
/1 power  KB06079XL


$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP 
Integrated Sensor Hub (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 
(rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
0115 (rev 01)


$ lsmod | grep multi
hid_multitouch 20480  0
hid   118784  4 
hid_sensor_hub,i2c_hid,hid_multitouch,intel_ishtp_hid


$ modinfo hid_multitouch | grep version
srcversion: F120069FA6914E49C917A88

--

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

This bug seems to only affect Xorg. Wayland is not affected (see
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1725384/comments/18).

Since Xorg is not a priority, I suspect this bug is not getting attention.
Unfortunately, many of us have to use Xorg (if you have Nvidia hardware, for 
example).

Initially, I thought that perhaps Gnome is generating multiple touch
events, causing the apps overview to open, and then close again (see
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1725384/comments/10).

However, this could be an issue in Gnome Shell, Gnome Dash, Xorg,
specific hardware, or something else entirely.

Let's see if we can narrow it down or find some kind of pattern, or
clue, to what is going wrong.

Doing this may help provide the developers with enough information to
spot the cause and fix this bug.

It would really useful for all of us to list the hard ware we have...

Please share the output of:

(1)
$ sudo dmidecode | grep -A9 "System Information"

(2)
$ sudo lshw -short

(3) 
$ lspci

(4) Is the multi-touch module loaded (most likely for all of us)...
$ lsmod | grep multi

(5) Multi-touch module version number...
$ modinfo hid_multitouch | grep version

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384

Title:
  On touch screens, the apps icon in the dock does not open when touched

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1752323] Re: Ubiquity crashes at startup on Kubuntu daily iso - 2018/02/28

2018-08-02 Thread PJSingh5000

Did you `apt update; apt install --reinstall ubiquity` to get the latest
version, before launching the installer?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752323

Title:
  Ubiquity crashes at startup on Kubuntu daily iso - 2018/02/28

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767259] Re: ubuntu 18.04 The 'grub-efi-amd64-signed' package failed to install into / targer.

2018-07-13 Thread PJSingh5000

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

I also experienced this (Ubuntu 18.04, x64, with EFI enabled on an HP
Laptop).

During install, I do not have an internet connection enabled.
Both checkboxes were disabled:
  - "Download updates..."
  - "Install third-party software..."

Questions:
a) Is the package "grub-efi-amd64-signed" simply not included in the Live CD?
   [WOULD SOMEONE PLEASE CHECK AND POST THE ANSWER IN THIS BUG REPORT?]

   If this is the case:

   Would executing the following in a live session before launching Ubiquity 
solve the problem?...
 $ apt install grub-efi-amd64-signed" before launching Ubiquity solve the 
problem?

   Should the Live CD come shipped with this package?
   Should the ubiquity package be updated to include
 grub-efi-amd64-signed as a "depends" or "recommends"?

...or...

b) Does the Ubiquity installer need a newer updated version of this package?
   [WOULD SOMEONE PLEASE CHECK WHICH VERSION IS INSTALLED AND POST IN THIS BUG 
REPORT?]

   If this is the case:

   Would executing the following in a live session before launching Ubiquity 
solve the problem?...
 $ apt update
 $ apt install grub-efi-amd64-signed" before launching Ubiquity solve the 
problem?

   Perhaps Canonical needs to issue a point release Live CD (version 18.04.1?)
 with an updated version of this package?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767259

Title:
  ubuntu 18.04 The 'grub-efi-amd64-signed' package failed to install
  into / targer.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778726] Re: 'Details of updates' frame does not expand vertically

2018-06-26 Thread PJSingh5000

Software Updater - How It Should Look

** Attachment added: "Software Updater How It Should Look"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778726/+attachment/5156786/+files/Software%20Updater%20How%20It%20Should%20Look.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778726

Title:
  'Details of updates' frame does not expand vertically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778726] [NEW] 'Details of updates' frame does not expand vertically

2018-06-26 Thread PJSingh5000

Public bug reported:

SUMMARY

There are two expandable sections of the Software Updater window:
  1. 'Details of updates'
  2. 'Technical description'

When the Software Updater window first opens, the 'Details of updates'
section is not expand vertically, and an empty 'Technical description'
takes 1/2 the vertical space.


ISSUE

When the Software Updater window first opens, these sections are given
the same vertical height, even though 'Technical description' has not
been expanded. As a result, 'Details of updates' takes 1/2 the vertical
space, and 'Technical description' takes the other 1/2. However nothing
is shown in the 'Technical description' section, so Software Updater has
a large empty space at the bottom 1/2 of the window. This is especially
pronounced if you increase the vertical height of the Software Updater
window.

See the issue in the attached screenshot 'Software Updater With
Bug.png'.


STEPS TO RECREATE

1. Open Software Updater when you have updates pending.
2. Notice that the 'Technical description' section is collapsed, so it does not 
display text.
3. Do _not_ click on the expander triangle next to 'Technical description'.
4. Stretch the Software Updater window vertically using the bottom or top 
window edge and mouse.
5. Notice that 'Technical description' area takes 1/2 of the vertical window 
space even though it has not been expanded. **THIS IS THE ISSUE***

6. Close the Software Updater window. (Do _not_ click Install Now).
7. Open Software Updater (when you have updates pending).
8. Notice that the window 'remembers' its previous size, and is stretched 
vertically.
9. Notice that 'Technical description' area still takes 1/2 of the vertical 
window space even though it has not been expanded. **THIS IS THE ISSUE***

10. Click on the expander triangle next to 'Technical description'
11. A text area appears below 'Technical description'. (It may be blank if you 
have not selected a package in the 'Details of updates' section, but this is 
OK).
12. Notice that 'Technical description' area takes 1/2 of the vertical window 
space, since it has been expanded. This is OK, because there ~is~ a text area 
to display.

13. Click on the expander triangle next to 'Technical description' again to 
collapse this section.
14. Notice that 'Technical description' now appears at the _bottom_ of the 
window. It no longer takes 1/2 the vertical space. The 'Details of updates' 
frame now uses most of the vertical space, as it should.
15. ***This is how the Software Updater window should look when it first opens 
in step 2 above.***


HOW IT SHOULD BEHAVE

When the Software Updater window first opens:
- The 'Technical description' section should be shown near the _bottom_ of the 
window.
- The 'Details of updates' section should be stretched to fill the available 
vertical space.
- The 'Technical description' section should not take 1/2 the vertical space.
- The 'Technical description' section should only use 1/2 the vertical space 
when it is expanded (using the the expander triangle).

See the the expected behavior in the attached screenshot 'Software
Updater How It Should Look.png'.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: update-manager 1:18.04.11
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Aptdaemon:
 
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun 26 08:51:21 2018
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'948'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'window-width' b'586'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1530011694'
InstallationDate: Installed on 2018-05-09 (48 days ago)
InstallationMedia: Ubuntu 18.04.0 2018.05.09 LTS x64 "Custom Bionic Beaver"
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Software Updater With Bug"
   
https://bugs.launchpad.net/bugs/1778726/+attachment/5156781/+files/Software%20Updater%20With%20Bug.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778726

Title:
  'Details of updates' frame does not expand vertically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2018-06-08 Thread PJSingh5000

I don't use workspaces-to-dock, and I still have the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

2018-05-09 Thread PJSingh5000

I think this bug has been moved to https://gitlab.gnome.org/GNOME/gnome-
shell/issues/135

How can we add a remote bug watch for that?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730211

Title:
  Unable to type capital letters using onscreen keyboard

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770299] [NEW] Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

2018-05-09 Thread PJSingh5000

Public bug reported:

I executed gnome-shell --replace from the terminal.

After navigating through gnome-shell using my touch screen, I observed
the following warnings in the terminal window...

(gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
property 'discreteGpuAvailable' on the module 'appDisplay'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway.

(gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed May  9 22:29:33 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-05-05 (5 days ago)
InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- I executed gnome-shell --restart from the termnal.
+ I executed gnome-shell --replace from the termnal.
  
- 
- After navigating through gnome-shell using my touch screen, I observed the 
following warnings in the terminal window... 
+ After navigating through gnome-shell using my touch screen, I observed
+ the following warnings in the terminal window...
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
  property 'discreteGpuAvailable' on the module 'appDisplay'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
  property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  9 22:29:33 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver"
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- I executed gnome-shell --replace from the termnal.
+ I executed gnome-shell --replace from the terminal.
  
  After navigating through gnome-shell using my touch screen, I observed
  the following warnings in the terminal window...
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
  property 'discreteGpuAvailable' on the module 'appDisplay'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
  property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

2018-05-09 Thread PJSingh5000

If restart gnome-shell using the following in a terminal...

gnome-shell --replace

...then the dock behaves normally, launching one instance of an
application for each tap

I do see some errors after I do this, but they may be unrelated, since
it works fine after issuing the above command.

(However the error "ubuntu-dock [...] unreachable code after return
statement" seems a bit suspicious).


$ gnome-shell --replace
Gjs-Message: 22:08:47.482: JS WARNING: [resource:///org/gnome/shell/ui/main.js 
340]: reference to undefined property "MetaStage"
Gjs-Message: 22:08:47.495: JS WARNING: 
[resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property 
"MetaWindowGroup"
Gjs-Message: 22:08:47.525: JS WARNING: 
[resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to 
undefined property "MetaDBusDisplayConfigSkeleton"
current session already has an ibus-daemon.
Gjs-Message: 22:08:47.759: JS WARNING: 
[resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property 
"CallyActor"
GNOME Shell-Message: 22:08:47.804: Telepathy is not available, chat integration 
will be disabled.
Gjs-Message: 22:08:47.998: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1027]: 
unreachable code after return statement
Ubuntu AppIndicators-Message: 22:08:48.361: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.62/org/ayatana/NotificationItem/software_update_available
GNOME Shell-Message: 22:08:48.492: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Gjs-Message: 22:08:57.112: JS WARNING: 
[resource:///org/gnome/shell/ui/keyboard.js 822]: reference to undefined 
property "label"

(gnome-shell:2512): GLib-GObject-CRITICAL **: 22:09:01.792:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384

Title:
  On touch screens, the apps icon in the dock does not open when touched

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon

2018-05-07 Thread PJSingh5000

Copying the description from duplicate bug #1769540, since there is more
information in that description. Also, note that this bug is present in
18.04 (as well as 17.10)...

If you touch an icon on the dock using a touch screen, the dock performs
duplicate actions for a single touch event.

1. Touching the app-grid icon on the dock with your finger causes the
"applications dash" to appear, and quickly disappear, as if you had
left-clicked on the app-grid icon *twice* using a mouse button.

2. Touching any favorites icon on the dock with your finger causes the
selected application to open *two* instances, as if you had left-clicked
on the app-grid icon twice using a mouse button.

THIS ONLY AFFECTS UBUNTU-DOCK
-

This only happens when using the touch screen to interact with the dock.
Using a mouse or track-pad works as expected.

The top-bar behaves as expected, as well, when using the touch screen.
For example, touching the Activities label ovens the "dash overview" as
expected; touching the notifications area on the top bar opens the
notifications/calendar as expected; touching the indicator icons behave
as expected as well.

Interacting with open applications using the touch screen also works as
expected. Applications respond to touch events as if a single event was
generated.

UBUNTU DOCK
---

Only the ubuntu-dock acts as if it received two (or more) touch events
for each single touch action.

EXPECTED BEHAVIOR
-

Ubuntu dock should respond as if it received a single click event, for
each single touch event.

ADDITIONAL INFORMATION
--

If I touch the "Action" item at the top left of the desk-top, the
overview appears. THEN, if I touch an icon in the dock, it behaves
correctly.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745888

Title:
Two instances of a program launch whenever you touch a favorites icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1745888/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769540] [NEW] Dock on touch screen does not handle touch events correctly

2018-05-06 Thread PJSingh5000

Public bug reported:

If you touch an icon on the dock using a touch screen, the dock performs
duplicate actions for a single touch event.

1. Touching the app-grid icon on the dock with your finger causes the
"applications dash" to appear, and quickly disappear, as if you had
left-clicked on the app-grid icon *twice* using a mouse button.

2. Touching any favorites icon on the dock with your finger causes the
selected application to open *two* instances, as if you had left-clicked
on the app-grid icon twice using a mouse button.


THIS ONLY AFFECTS UBUNTU-DOCK
-

This only happens when using the touch screen to interact with the dock.
Using a mouse or track-pad works as expected.

The top-bar behaves as expected, as well, when using the touch screen.
For example, touching the Activities label ovens the "dash overview" as
expected; touching the notifications area on the top bar opens the
notifications/calendar as expected; touching the indicator icons behave
as expected as well.

Interacting with open applications using the touch screen also works as
expected. Applications respond to touch events as if a single event was
generated.


UBUNTU DOCK
---

Only the ubuntu-dock acts as if it received two (or more) touch events
for each single touch action.


EXPECTED BEHAVIOR
-

Ubuntu dock should respond as if it received a single click event, for
each single touch event.


ADDITIONAL INFORMATION
--

If I touch the "Action" item at the top left of the desk-top, the
overview appears. THEN, if I touch an icon in the dock, it behaves
correctly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun May  6 20:35:07 2018
InstallationDate: Installed on 2018-05-05 (1 days ago)
InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver"
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769540

Title:
  Dock on touch screen does not handle touch events correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769540/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

2018-05-06 Thread PJSingh5000

This is still an issue on Ubuntu 18.04 using Xorg.

Interestingly, capital letters now work on the login GDM screen.

But on the desktop, it does't work.
Touching the virtual shift key still produces lower case letters.

Also, when I select the symbols key to bring up the symbols keyboard layout, 
not all the keys work.
The keys below the top row number of number keys actually produce numbers 
instead of symbols.
Some of the virtual symbols keys do nothing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730211

Title:
  Unable to type capital letters using onscreen keyboard

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

2018-05-04 Thread PJSingh5000

Still experiencing this in Bionic 18.04...


* Touching the App-Grid icon in the dash-to-dock causes the app icons to 
appear, and quickly disappear. (It's as if you touched the App-Grid icon twice, 
very quickly).

* Touching a favorites icon in the dash-to-dock causes two instances of the 
application to open. 
(It's as if you touched the favorite icon twice, very quickly).


$ sudo dmidecode | grep -A9 "System Information"
System Information
Manufacturer: HP
Product Name: HP Spectre x360 Convertible 15-bl1XX
Version:  
Serial Number: 5CD74284QL
UUID: 37444335-3234-3438-514C-4C3432344435
Wake-up Type: Power Switch
SKU Number: 1VW22AV
Family: 103C_5335KV HP Spectre

$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

$ uname -a
Linux PS006 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ echo $DESKTOP_SESSION 
gnome-xorg

$ gnome-shell --version
GNOME Shell 3.28.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384

Title:
  On touch screens, the apps icon in the dock does not open when touched

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-03 Thread PJSingh5000

I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual
machine.

Instead of corrupted graphics in the Ubiquity window, I saw a blank
white area above the "Copying files..." progress bar.

After a few seconds, the Ubiquity slide show appeared as usual, and I
did *not* get a crash.

I will also try this on actual hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751252

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-02 Thread PJSingh5000

Ubiquity also crashes inside a virtual machine (VirtualBox) running on a
non-HiDPI host machine.

I have observed corrupted graphics in the "main area" of Ubiquity when
this bug occurs. By "main area", I am referring to the rendered
rectangular area in Ubiquity below the title bar and above the "Copying
files..." progress bar.

The corruption looks like jagged diagonal lines or "snow". I have seen
this on both actual hardware (HiDPI machine scaled at 200%) and in a
virtual machine (non-HiDPI hardware scaled at 100%).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751252

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-01 Thread PJSingh5000

Here is the backtrace (bt f) with debug symbols.

I still have gdb open, if anyone needs me to do anything else?

** Attachment added: "gdb backtrace (bt f) with debug symbols"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131712/+files/gdb_output_with_debug_symbols.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751252

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

2018-05-01 Thread PJSingh5000

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

@seb128, the three packages libx11-6-dbgsym, libgtk-3-0-dbgsym,
libglib2.0-0-dbgsym do not seem to be available in the repositories for
bionic. Is there a PPA I need to add, or some other location to get
these from?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

Oops, in comment #25, I forgot to attach the installer/debug file.
Here it is.

** Attachment added: "installer/debug"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5131119/+files/debug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

@slashd, I will try again with the command you provided.

In the mean time, I was able to use gdb to attach to a running instance
of Ubiquity.

Here is the backtrace at gdk_x_error.


** Attachment added: "gdb output with backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5131112/+files/gdb_output_with_backtrace.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

The command
gdb file /usr/bin/ubiquity
gives the error
"not in executable format: File format not recognized"

What am I missing?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

lspci

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130958/+files/lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

installer/debug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

dmidecode

** Attachment added: "dmidecode"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130957/+files/dmidecode.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

Contents of installer/version is...

ubiquity 18.04.14

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

syslog after crash

** Attachment added: "syslog after crash"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130956/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720

Title:
  Ubiquity crashed during install of 18.04 with error 'BadAccess
  (attempt to access private resource denied)'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'