date:20181126

Thanks. Unfortunately that didn't attach everything I was thinking of.
Can you please also:

1. Run 'lspci -k' and attach the output.

2. Run 'dpkg -l > allpackages.txt' and attach the file
'allpackages.txt'.


** Summary changed:

- Lock screen corrupt since upgrade to 18.04.01
+ [i945] Lock screen corrupt since upgrade to 18.04.01

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

** Changed in: mesa (Ubuntu)
   Status: New => Incomplete

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

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  [i945] Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1805148] ProcCpuinfoMinimal.txt

2018-11-26 Thread Paul Chambre

apport information

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

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

Title:
  Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1805148] Re: Lock screen corrupt since upgrade to 18.04.01

2018-11-26 Thread Paul Chambre

apport information

** Tags added: apport-collected wayland-session

** Description changed:

- Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of
- this laptop (an HP 6910p) became corrupt. When logged in and using the
- system, video display is fine, but the lock screen is consistently
- garbled as in the attached photo. Switching to Wayland made no
- difference in this behavior.
+ Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
+ GsettingsChanges:
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ InstallationDate: Installed on 2016-01-23 (1038 days ago)
+ InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
+ Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
+ Tags:  bionic wayland-session
+ Uname: Linux 4.15.0-39-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
+ UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

** Summary changed:

- New On-screen keyboard cannot be manually triggered to appear
+ New On-screen keyboard does not appear automatically when selecting some text 
fields

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Confirmed
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have always used an on-screen keyboard as a virtual keyboard for
  entering text in a different layout than my physical keyboard. This
  time I cannot, since I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

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

[Desktop-packages] [Bug 1792365] Re: On-screen keyboard appears automatically only in the login screen and the activities menu

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

** This bug is no longer a duplicate of bug 1791551
   The OSK does not auto-activate reliably when selecting any text widget
** This bug has been marked a duplicate of bug 1760399
   New On-screen keyboard does not appear automatically when selecting some 
text fields

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

Title:
  On-screen keyboard appears automatically only in the login screen and
  the activities menu

Status in gedit package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  For example, it works in the login screen and the Activities menu and
  not in Chrome and gedit.

  The release of Ubuntu: Ubuntu 18.04.1 LTS

  The version of the package: 3.28.2

  Expected behavior: I expected to see the on-screen keyboard when
  clicking on a chrome text field.

  Actual behavior: The on-screen keyboard didn't appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:39:44 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-24 (111 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798227] Re: OnScreen Keyboard missing

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

** This bug is no longer a duplicate of bug 1791551
   The OSK does not auto-activate reliably when selecting any text widget
** This bug has been marked a duplicate of bug 1760399
   New On-screen keyboard does not appear automatically when selecting some 
text fields

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

Title:
  OnScreen Keyboard missing

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I tried support platforms and was told that onscreen keyboard won’t
  appear all the time even if you enable it through accessibility. I
  have experienced it first hand on a laptop where the keyboard is
  dead.As you can see in the screen shot attached, I expect to see OSK
  after enabling it from setting and activating through Accessibility.
  But there is no sign of OSK. I am typing this from a physical keyboard
  and till now there is no sign of OSK. It will be great if you can fix
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 17 06:13:20 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-11 (247 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (172 days ago)

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

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

[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

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

** Changed in: gnome-user-docs (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-user-docs source package in Bionic:
  Confirmed
Status in im-config source package in Bionic:
  Triaged

Bug description:
  im-config SRU request
  =

  [Impact]

  When in a Wayland session, accented characters as well as some special
  characters can't be entered via the screen keyboard. The issue is
  fixed via the proposed upload of im-config, which has been changed to
  not set the GTK_IM_MODULE environment variable for IBus on Wayland
  (previously GTK_IM_MODULE was set to "ibus").

  Making this accessibility tool work without issues on Wayland is
  important enough to justify this SRU.

  [Test Case]

  1. Log in to an Ubuntu on Wayland session

  2. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  -> Accented characters via long-press does not work.
 Example: long-press a and select à from the popup

 Also, certain keys for special characters result in incorrect
 characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢

  3. Install im-config from bionic-proposed

  4. Relogin and repeat step 2.

  -> Everything works as expected

  [Regression Potential]

  There are reasons to presuppose that GTK_IM_MODULE does not need to be
  set at all for IBus on a GNOME desktop:

  * GTK has a mechanism for selecting a built-in IM.

  * IBus is default in GNOME, and vanilla GNOME (which does not make use
of im-config) does not set the GTK_IM_MODULE environment variable.

  But the change is only made for Wayland sessions, which is not default
  in 18.04. Given this limitation, the regression risk is deemed to be
  low.

  [Original description]

  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

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

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

[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

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

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Confirmed

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-user-docs source package in Bionic:
  Confirmed
Status in im-config source package in Bionic:
  Triaged

Bug description:
  im-config SRU request
  =

  [Impact]

  When in a Wayland session, accented characters as well as some special
  characters can't be entered via the screen keyboard. The issue is
  fixed via the proposed upload of im-config, which has been changed to
  not set the GTK_IM_MODULE environment variable for IBus on Wayland
  (previously GTK_IM_MODULE was set to "ibus").

  Making this accessibility tool work without issues on Wayland is
  important enough to justify this SRU.

  [Test Case]

  1. Log in to an Ubuntu on Wayland session

  2. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  -> Accented characters via long-press does not work.
 Example: long-press a and select à from the popup

 Also, certain keys for special characters result in incorrect
 characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢

  3. Install im-config from bionic-proposed

  4. Relogin and repeat step 2.

  -> Everything works as expected

  [Regression Potential]

  There are reasons to presuppose that GTK_IM_MODULE does not need to be
  set at all for IBus on a GNOME desktop:

  * GTK has a mechanism for selecting a built-in IM.

  * IBus is default in GNOME, and vanilla GNOME (which does not make use
of im-config) does not set the GTK_IM_MODULE environment variable.

  But the change is only made for Wayland sessions, which is not default
  in 18.04. Given this limitation, the regression risk is deemed to be
  low.

  [Original description]

  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

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

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

[Desktop-packages] [Bug 1799515] Re: Gnome on-screen keyboard doesn't appear when a text field is focused

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

I think we should use bug 1791551 until proven otherwise.

** This bug has been marked a duplicate of bug 1791551
   The OSK does not auto-activate reliably when selecting any text widget

** This bug is no longer a duplicate of bug 1791551
   The OSK does not auto-activate reliably when selecting any text widget
** This bug has been marked a duplicate of bug 1760399
   New On-screen keyboard does not appear automatically when selecting some 
text fields

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

Title:
  Gnome on-screen keyboard doesn't appear when a text field is focused

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After installing ubuntu-18.04-desktop-amd64.iso the on-screen keyboard
  was working as expected: the on-screen keyboard would come up as soon
  as the focus was in a gnome-terminal or gedit window.

  But after upgrading gnome-shell from 3.28.1-0ubuntu2 to
  3.28.3-0ubuntu0.18.04.2 the on-screen keyboard stopped coming up when
  focusing a gnome-terminal or gedit window. The only place (I found)
  where the on-screen keyboard still comes up is in the text fields of
  the shell such as the search field in the gnome overview.

  Details:
  * The on-screen keyboard was explicitly enabled in accessibility.
  * None of the caribou and onboard packages are installed.
  * Only two packages were upgraded between the working and broken 
configurations:
gnome-shell 3.28.1-0ubuntu2 ---> 3.28.3-0ubuntu0.18.04.2
gnome-shell-common  3.28.1-0ubuntu2 ---> 3.28.3-0ubuntu0.18.04.2
  * Bug #1589240 is similar but very old and was closed with instructions to 
reopen a new bug if needed.
  * The test environment is a VMware VM which does have a "real" keyboard and 
does not have a touchscreen. I don't think that justifies the change in 
behavior, particularly given the inconsistency between gnome-shell's text 
fields and the others.

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

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

[Desktop-packages] [Bug 1805257] Re: gnome apps provided by snaps show default "executable" icon with default icon theme

Quick sanity check: Can you please try disabling/removing all
extensions:

b'org.gnome.shell' b'enabled-extensions' b"['battery-
percent...@nohales.org', 'battery-remaining-t...@dadexix86.github.com',
'bettervol...@tudmotu.com', 'drive-menu@gnome-shell-
extensions.gcampax.github.com', 'battery_sta...@milliburn.github.com',
'window_butt...@biox.github.com', 'hide-top-pa...@dimka665.gmail.com',
'multicl...@mibus.org', 'world_clock@ailin.nemui', 'clock-
overr...@gnomeshell.kryogenix.org', 'move_cl...@rmy.pobox.com',
'topic...@phocean.net', 'ubuntu-appindicators_ubuntu.com', 'docker-
integration_jan.trejbal.gmail.com', 'bettervolume_tudmotu.com',
'battery_status_milliburn.github.com', 'drive-menu_gnome-shell-
extensions.gcampax.github.com', 'TopIcons_phocean.net',
'hide_activit...@shay.shayel.org', 'docker-
integrat...@jan.trejbal.gmail.com']"

and tell us if the problem still happens?

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome apps provided by snaps show default "executable" icon with
  default icon theme

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On 18.10 with GNOME session and default Adwaita icon theme, desktop
  apps installed via snap, like gnome-calculator, gnome-system-monitor,
  ... all have the default executable icon (diamond with gears), instead
  of their own icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 26 23:50:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1791551] Re: The OSK does not auto-activate reliably when selecting any text widget

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

** Summary changed:

- Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to 
discover in Wayland and not possible in X
+ The OSK does not auto-activate reliably when selecting any text widget

** This bug has been marked a duplicate of bug 1760399
   New On-screen keyboard does not appear automatically when selecting some 
text fields

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

Title:
  The OSK does not auto-activate reliably when selecting any text widget

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The new OSK does not auto-activate reliably by selecting any text widget as 
the Gnome 3.28 release notes claim:
  "The new keyboard automatically activates when a text area is selected, ..."
  -- https://help.gnome.org/misc/release-notes/3.28/

  This does not work with text widgets of alien toolkits (Chrome,
  Firefox, Qt, ...).

  Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does 
only for the search boxes of Activity and Application menus, not anywhere else 
that I can find. Not even epiphany, gedit, or other first-class Gnome 
applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this 
report is also referenced as evidence further down).
  Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk 
libraries, or in each individual application where it does not work who is 
using these libraries?

  Hence it is necessary to have a way for manual activation. This is
  possible in Wayland by swiping up from bottom of screen on a touch
  screen, but there is no UI hint for this and I banged my head bloody
  until I stumbled on the solution.

  In the default X session the swipe does not work and hence it cannot
  be manually activated at all.

  The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and
  contributes to the confusion. Bug report:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548

  I refer you to user confusion on the following links, note that the
  previously available answers on Askubuntu all provide incorrect or
  incomplete solutions:

  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399
  (I added a description in comment #10 earlier today)

  Askubuntu (I added new answers earlier today):
  
https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461
  
https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756
  
https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754
  
https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  9 23:04:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-15 (2185 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago)

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

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

[Desktop-packages] [Bug 1741843] Re: caribou (gnome-shell osk): special characters not working

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

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Tags added: artful

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

Title:
  caribou (gnome-shell osk): special characters not working

Status in Caribou:
  In Progress
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware
  is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this
  issue on both Wayland and XOrg. I've reproduced this issue on the
  17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox.

  Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display
  the vast majority of special characters (the ones that you long press
  on vowels to get). Nor do the upside down question and exclamation
  marks work on it either. Nor do the Euro or Sterling signs work. This
  makes it impossible to use when writing in any other languages than
  English.

  
  1)  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2) package version:

  caribou:
Installed: 0.4.21-2
Candidate: 0.4.21-2
Version table:
   *** 0.4.21-2 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3) What do I expect to happen: I expect that when I long press on e and get 
the popup and select ê, ë that these letter appear
  4) they do not. nothing happens

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

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

[Desktop-packages] [Bug 1741843] Re: caribou (gnome-shell osk): special characters not working

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

Also, see bug 1761554 :)

** This bug has been marked a duplicate of bug 1761554
   [bionic] Extended characters in GNOME screen keyboard don't get entered

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

Title:
  caribou (gnome-shell osk): special characters not working

Status in Caribou:
  In Progress
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware
  is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this
  issue on both Wayland and XOrg. I've reproduced this issue on the
  17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox.

  Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display
  the vast majority of special characters (the ones that you long press
  on vowels to get). Nor do the upside down question and exclamation
  marks work on it either. Nor do the Euro or Sterling signs work. This
  makes it impossible to use when writing in any other languages than
  English.

  
  1)  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2) package version:

  caribou:
Installed: 0.4.21-2
Candidate: 0.4.21-2
Version table:
   *** 0.4.21-2 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3) What do I expect to happen: I expect that when I long press on e and get 
the popup and select ê, ë that these letter appear
  4) they do not. nothing happens

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

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

[Desktop-packages] [Bug 1805247] Re: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen

** Tags added: bionic

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

Title:
  Onscreen Keyboard in Wayland cannot be summoned by swiping up on the
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  -- Ubuntu 18.04 LTS
  -- gnome-shell 3.28.1-0ubuntu2

  When user is logged in using Wayland, swipe-up gesture cannot be used
  to summon the OSK.  Problem is non-existent on Xorg.

  This has been reproduced on multiple devices, leaving the user unable
  to use the OSK in many situations.

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

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

[Desktop-packages] [Bug 1804683] Re: there is too many errors in my ubuntu 18.04

** Package changed: xorg (Ubuntu) => ubuntu

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

Title:
  there is too many errors in my ubuntu 18.04

Status in Ubuntu:
  New

Bug description:
  I am trying to install nvidia driver 415 there is already 390 but the
  laptop recommends 415 when i insert the code it says that there is a
  held broken packeges please help me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 18:59:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1805298] Re: Unknown Xorg error message

Can you please clarify in more detail what problem you would like this
bug to be about?

** Tags added: radeon

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Unknown Xorg error message

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  games slow, pc speeds up & pc shuts down

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 27 09:41:27 2018
  DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
  InstallationDate: Installed on 2018-11-12 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDION MS-7800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M7800W08.209
  dmi.board.name: MS-7800
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr:
  dmi.product.name: MS-7800
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Tue Nov 27 08:03:13 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1805200] Re: Xorg crashes when it tries to resume a scale transformation after that Screen has been closed

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Xorg crashes when it tries to resume a scale transformation after that Screen 
has been closed
+ Xorg crashes when it tries to resume a scale transformation after that Screen 
has been closed. Crashed in __strlen_avx2() from transform_filter_length() from 
ProcRRGetCrtcTransform()

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

Title:
  Xorg crashes when it tries to resume a scale transformation after that
  Screen has been closed. Crashed in __strlen_avx2() from
  transform_filter_length() from ProcRRGetCrtcTransform()

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous
  versions

  Very easy to reproduce:
  Start a simple (empty) X server instance (say Xorg :2 vt8)
  Set a scale transformation
  xrandr -d :2 --output eDP-1 --scale 2x2
  Call xrandr again so that the server tries to resume the previous 
transformation
  xrandr -d :2

  I've addressed the issue at
  https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
  various fixes for that, but so far no feedback.

  Marking it as incoming rls bug as this needs to be addressed as per
  supporting xrandr scaling support in desktop.

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

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

[Desktop-packages] [Bug 1805189] Re: gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Actually the best thing to try first is to remove all gnome-shell
extensions. You have a few:

b'org.gnome.shell' b'enabled-extensions'
b"['system76-po...@system76.com', 'no-title-...@franglais125.gmail.com',
'openweather-extens...@jenslody.de', 'dash-to-
pa...@jderose9.github.com', 'dynamic-panel-
transpare...@rockon999.github.io']"

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

Title:
  gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i7-8750H (6 cores, 12 threads)
  32GB DDR
  GTX 1070 Max-Q
  500GB SSD
  4K external monitor (Dell U2718Q)

  No problem without the 4K monitor hooked up. When it is hooked up,
  CPU1 ~ 100% in idle. Gnome-shell and Xorg the problem.

  nvidia 410 from nvidia-ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 00:22:13 2018
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805189] Re: gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Can you please try downgrading to a supported version of the nvidia
driver:

  https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390

and tell us if the problem still happens?

** Tags added: nvidia

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

** Tags added: performance

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

Title:
  gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i7-8750H (6 cores, 12 threads)
  32GB DDR
  GTX 1070 Max-Q
  500GB SSD
  4K external monitor (Dell U2718Q)

  No problem without the 4K monitor hooked up. When it is hooked up,
  CPU1 ~ 100% in idle. Gnome-shell and Xorg the problem.

  nvidia 410 from nvidia-ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 00:22:13 2018
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805247] Re: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen

** Tags added: osk

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

Title:
  Onscreen Keyboard in Wayland cannot be summoned by swiping up on the
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  -- Ubuntu 18.04 LTS
  -- gnome-shell 3.28.1-0ubuntu2

  When user is logged in using Wayland, swipe-up gesture cannot be used
  to summon the OSK.  Problem is non-existent on Xorg.

  This has been reproduced on multiple devices, leaving the user unable
  to use the OSK in many situations.

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

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

[Desktop-packages] [Bug 1805148] Re: Lock screen corrupt since upgrade to 18.04.01

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1805148

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Tags added: bionic

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

Title:
  Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen
  of this laptop (an HP 6910p) became corrupt. When logged in and using
  the system, video display is fine, but the lock screen is consistently
  garbled as in the attached photo. Switching to Wayland made no
  difference in this behavior.

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen still shows desktop windows

Assigned to extensions packages only, per comment #8.

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

Title:
  Lock screen still shows desktop windows

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in gnome-shell-extensions package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen still shows desktop windows

Changed the bug title to avoid ongoing confusion with bug 1769383.

** Summary changed:

- Lock screen doesn't hide the screen contents
+ Lock screen still shows desktop windows

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

** No longer affects: gdm3 (Ubuntu)

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

Title:
  Lock screen still shows desktop windows

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in gnome-shell-extensions package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

Thanks.

Your kernel log shows a lot of messages from Discord. I wonder is that
app affected, and can you please try a few other voice apps too?

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
   Desktop freeze running VirtualBox, Intel graphics

Status in linux package in Ubuntu:
  New

Bug description:
  This is identical to bug 1804885, but as requested I am filing this while 
running the standard Ubuntu kernel.  I will copy and paste my summary below.  
Updates since I created that bug:
   * This occurs with the mainline PPA 4.18.12-041812-generic kernel.
   * The glxinfo section I include below is identical with 4.18.0-11-generic 
(presumably no surprise).
   * I would appreciate a bit of hand-holding for bisecting this.  Does the 
kernel team have ready-built kernel packages for bisecting?  Or guidance about 
the fastest way of doing it (i.e. not rebuilding things which do not need to be 
rebuilt for successive rounds)?

  === Original report follows ===

  When I start a VirtualBox virtual machine (reproducible with the
  Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with
  VMSVGA emulation and 3D pass-through enabled, my system hangs.
  Sometimes I can recover if I get to a VT fast enough to kill the
  process. Also, the OOM killer sometimes triggers and kills the process
  or gnome-shell, but the OOM killer entries in dmesg look like neither
  of the two are using excessive memory compared to available system
  RAM. When I switch to the Ubuntu drm-tip kernel packages from the
  kernel PPA the problem goes away. Debugging shows that the hang occurs
  during the first glXMakeCurrent call made by the application. It did
  not occur using the standard Ubuntu kernel but running the application
  under apitrace. I can provide the trace if that helps.

  Short extract from glxinfo running the 4.20 drm-tip kernel:

  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916)
  Version: 18.2.2
  Accelerated: yes
  Video memory: 3072MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 26 15:01:53 2018
  DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2018-06-12 (166 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HES0E73E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET78W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES0E73E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HES0E73E
  dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel:

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

Adam,

That's not this bug. That is bug 1769383.

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

Thanks. If Gnome (particularly the Wayland session) experiences the same
bug then this isn't a problem in any desktop environment. It's more
likely the kernel.


** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Incomplete => New

** No longer affects: linux (Ubuntu)

** Project changed: ubuntu-mate => mir

** No longer affects: mir

** Package changed: mate-common (Ubuntu) => linux (Ubuntu)

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in linux package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multi-monitor mode.

  
  EDIT: 2018-11-22 // The problems are not observed when using HDMI instead of 
mini display-port. Moreover, if one can regain control of HID devices when mini 
DP plugged in, the resolution of the monitor plugged in is completely wrong. 

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2016-07-23 (848 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog:
   (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: LENOVO 20F9004FUS
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=074ff7b7-c074-4137-8cf7-d46cdd7dd723 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic ubuntu
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (32 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9004FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20F9004FUS:pvrThinkPadT460s:rvnLENOVO:rn20F9004FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20F9004FUS
  dmi.product.sku: LENOVO_MT_20F9_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-10-generic, x86_64: installed

[Desktop-packages] [Bug 1729539] Re: copy/paste failed in gedit after a few hours of work

2018-11-26 Thread Bug Watch Updater

** Changed in: gedit
   Status: Unknown => Incomplete

** Changed in: gedit
   Importance: Unknown => Medium

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

Title:
  copy/paste failed in gedit after a few hours of work

Status in gedit:
  Incomplete
Status in gedit package in Ubuntu:
  New

Bug description:
  After a few hours of work, copy in gedit does not work with other 
applications. In clipit, no copied lines.
  It is new with ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  2 10:19:21 2017
  InstallationDate: Installed on 2016-01-31 (640 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to artful on 2017-10-28 (4 days ago)

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

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

[Desktop-packages] [Bug 837557] Re: fraudulent DigiNotar certificate issuance

2018-11-26 Thread Nora Blob

Hello Oliver Tilloy,
I can reproduce this issue in

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

I created a new profile with firefox -p --new-instance, and get the
certificates in the new profile with the new instance. If I delete the
certificates they will be in the certificate manager with every new
profile.

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

Title:
  fraudulent DigiNotar certificate issuance

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in seamonkey package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.2 package in Ubuntu:
  Invalid
Status in ca-certificates source package in Lucid:
  Fix Released
Status in chromium-browser source package in Lucid:
  Fix Released
Status in firefox source package in Lucid:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in qt4-x11 source package in Lucid:
  Fix Released
Status in seamonkey source package in Lucid:
  Won't Fix
Status in thunderbird source package in Lucid:
  Fix Released
Status in xulrunner-1.9.2 source package in Lucid:
  Fix Released
Status in ca-certificates source package in Maverick:
  Fix Released
Status in chromium-browser source package in Maverick:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in nss source package in Maverick:
  Fix Released
Status in qt4-x11 source package in Maverick:
  Fix Released
Status in seamonkey source package in Maverick:
  Won't Fix
Status in thunderbird source package in Maverick:
  Fix Released
Status in xulrunner-1.9.2 source package in Maverick:
  Fix Released
Status in ca-certificates source package in Natty:
  Fix Released
Status in chromium-browser source package in Natty:
  Fix Released
Status in firefox source package in Natty:
  Fix Released
Status in nss source package in Natty:
  Fix Released
Status in qt4-x11 source package in Natty:
  Fix Released
Status in seamonkey source package in Natty:
  Won't Fix
Status in thunderbird source package in Natty:
  Fix Released
Status in xulrunner-1.9.2 source package in Natty:
  Fix Released
Status in ca-certificates source package in Oneiric:
  Fix Released
Status in chromium-browser source package in Oneiric:
  Fix Released
Status in firefox source package in Oneiric:
  Fix Released
Status in nss source package in Oneiric:
  Fix Released
Status in qt4-x11 source package in Oneiric:
  Fix Released
Status in seamonkey source package in Oneiric:
  Won't Fix
Status in thunderbird source package in Oneiric:
  Fix Released
Status in xulrunner-1.9.2 source package in Oneiric:
  Invalid
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  USN Information: This is being tracked in USN-1197-*

  NOTE: The Firefox update causes a regression for certain Dutch sites which is 
being tracked in Bug #838322.
  NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA 
as trusted in the certificate manager.  This is due to Thunderbird using the 
system version of NSS. In this initial update, Thunderbird will actively 
distrust any certificate signed by the DigiNotar Root CA.  Future updates will 
properly show the root CA as distrusted in the certificate manager.

  WORKAROUND (from blog post):
  http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert

  -

  http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-
  certificate/

  Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the-
  diginotar-security-breach-means-for-qt-users-continued/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/837557/+subscriptions

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

[Desktop-packages] [Bug 735297] Re: Can not print on an SMB shared printer after password change

2018-11-26 Thread teramind

@ronan Where can I find this printer configuration?

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

Title:
  Can not print on an SMB shared printer after password change

Status in cups package in Ubuntu:
  Expired
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  I print to a number of SMB shared printers in a 2003 Active Directory
  domain. My password is changed from time to time as a policy in our
  organisation. When this happens I get prompted to enter the new
  password  but I can no longer connect to the using the new password.
  The previous password was saved using the  "Saved forever" option

  The only workaround I found is to delete the printer and recreate it.
  I had this problem several times in the past and so are the rest of my
  ubuntu users. Is there a workaround for that. Can someone confirm this
  bug?

  I tried to sniff the packets from my PC to the Print Server but
  wireshark showed nothing! This means that the problem is actually on
  my side. I can connect to other domain services like file shares using
  the same credentials. I am using the DOMAIN\username format to
  connect.

  The relevant cups error logs are here in case you want to have a look:
  http://paste.ubuntu.com/580463/

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: cups 1.4.4-6ubuntu2.3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Mar 15 08:25:04 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=CN84A3D1SN052D
   device for FOLLOWME: smb://prs03ist00.lim.tepak.int/FollowMe
   device for hp-LaserJet-2300-series: 
dnssd://hp%20LaserJet%202300%20series%20(0001E6A8204B)._printer._tcp.local/
   device for PDF: cups-pdf:/
   device for SRB02MF001: smb://prs03ist00.lim.tepak.int/srb02mf001
  MachineType: LENOVO 2767WB7
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles:
   SRB02MF001: NRG MP C2500 PXL
   Deskjet-F4200-series: HP Deskjet f4200 Series hpijs, 3.10.6
   PDF: Generic CUPS-PDF Printer
   hp-LaserJet-2300-series: HP LaserJet 2300 Postscript (recommended)
   FOLLOWME: KONICA MINOLTA C252 PS(P)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=5440d147-6520-49af-a1fd-76b8ec027c80 ro splash quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=el_GR.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET49WW (1.19 )
  dmi.board.name: 2767WB7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET49WW(1.19):bd10/17/2008:svnLENOVO:pn2767WB7:pvrThinkPadT400:rvnLENOVO:rn2767WB7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2767WB7
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1805298] [NEW] Unknown Xorg error message

2018-11-26 Thread Warrick

Public bug reported:

games slow, pc speeds up & pc shuts down

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Nov 27 09:41:27 2018
DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
InstallationDate: Installed on 2018-11-12 (14 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: MEDION MS-7800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: M7800W08.209
dmi.board.name: MS-7800
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr:
dmi.product.name: MS-7800
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Tue Nov 27 08:03:13 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.1-3ubuntu2.1
xserver.video_driver: radeon

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


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

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

Title:
  Unknown Xorg error message

Status in xorg package in Ubuntu:
  New

Bug description:
  games slow, pc speeds up & pc shuts down

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 27 09:41:27 2018
  DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
  InstallationDate: Installed on 2018-11-12 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDION MS-7800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

I have identified at power management at least 5 critical bug in the
last 3 years which hasn't been solved. For example one year before my
battery lifetime showed 4 hours, now just 2 hours. 2 years before 2
hours. So in the middle of the time frame something has been fixed and
after that the fix has been reverted.

I have removed also the diagram from my top bar, which shows the cpu
usage. (as I have read forums, that 120HZ might kill something in Ubuntu
while animating - that one solved the system-ud hog - as a process
hasn't locked something right away, with a delayed chrome start, the
system was more stable)

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

with GPU flickering hasn't been solved. The HD5500 using a different set
of code in Ubuntu, so either with mesa or without it, the problem
persists, and it's not just video playback, it's scrolling also. (with
similar frequency)

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

at flickering - cpu was on 20-30%.

With the dev version of chrome and using h264ify, so the gpu has been
used with youtube, cpu goes under 10%, but the flickering persists.
HD5500 hasn't any gpu hardware acceleration, only the secondary card,
which only appears when mesa installed. (AMD M260 Topaz)

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

disabled all the power management option anyway being displayed on the
gnome panel, so something still exists in the background

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

WIFI is unusable when I'm connecting with ubuntu directly. When I'm
connecting with my phone and using the usb tethering is much more
stable. Unfortunately, even if I set Xperia always on, it seems at some
point it's disconnecting, even if the stream is trying to load the next
batch.

With usb tethering, Xperia disconnects rarely even if the screen is
inactive (blank on the phone) than in Ubuntu, even if the screen is
active.

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1804688] Re: libreoffice always crashes when I do this

2018-11-26 Thread Bug Watch Updater

Launchpad has imported 16 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=118416.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-06-27T15:11:07+00:00 tml wrote:

Description:
In a developer build, with --enable-debug:

make debugrun
r --calc
add some numbers into A1 and A2
click the column header, Control-C
Control-Q, click "Don't Save"
Boom. Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.

Stack trace:

> #0  0x773e6530 in __memset_sse2_unaligned_erms () at /lib64/libc.so.6
> #1  0x7fffe0095475 in _cairo_xlib_surface_create_similar_shm () at 
> /lib64/libcairo.so.2
> #2  0x7fffe0068b17 in cairo_surface_create_similar_image () at 
> /lib64/libcairo.so.2
> #3  0x7fffe0068d08 in cairo_surface_create_similar () at 
> /lib64/libcairo.so.2
> #4  0x7fffec574d4d in SvpSalVirtualDevice::SetSizeUsingBuffer(long, long, 
> unsigned char*) (
> this=0x2f55e10, nNewDX=85, nNewDY=17895697, pBuffer=0x0) at 
> /ssd1/lo/fedora/vcl/headless/svpvd.cxx:107
> #5  0x7fffec574ae7 in SvpSalVirtualDevice::SetSize(long, long) 
> (this=0x2f55e10, nNewDX=85, nNewDY=17895697)
> at /ssd1/lo/fedora/vcl/headless/svpvd.cxx:63
> #6  0x7fffec262de2 in VirtualDevice::InnerImplSetOutputSizePixel(Size 
> const&, bool, unsigned char*) (
> this=0x26eeb10, rNewSize=Size = {...}, bErase=true, pBuffer=0x0) at 
> /ssd1/lo/fedora/vcl/source/gdi/virdev.cxx:304
> #7  0x7fffec263376 in VirtualDevice::ImplSetOutputSizePixel(Size const&, 
> bool, unsigned char*) (this=0x26eeb10, rNewSize=Size = {...}, bErase=true, 
> pBuffer=0x0) at /ssd1/lo/fedora/vcl/source/gdi/virdev.cxx:379
> #8  0x7fffec263690 in VirtualDevice::SetOutputSizePixel(Size const&, 
> bool) (this=0x26eeb10, rNewSize=Size = {...}, bErase=true)
> at /ssd1/lo/fedora/vcl/source/gdi/virdev.cxx:425
> #9  0x7fffc320cfe6 in 
> ScTransferObj::GetData(com::sun::star::datatransfer::DataFlavor const&, 
> rtl::OUString const&) (
> this=0x686c640, rFlavor=...) at 
> /ssd1/lo/fedora/sc/source/ui/app/transobj.cxx:378
> #10 0x7fffee789e8c in 
> TransferableHelper::getTransferData2(com::sun::star::datatransfer::DataFlavor 
> const&, rtl::OUString const&) (this=0x686c640, rFlavor=..., rDestDoc="") at 
> /ssd1/lo/fedora/svtools/source/misc/transfer.cxx:377
> #11 0x7fffee789009 in 
> TransferableHelper::getTransferData(com::sun::star::datatransfer::DataFlavor 
> const&) (this=0x686c640, rFlavor=...) at 
> /ssd1/lo/fedora/svtools/source/misc/transfer.cxx:275
> #12 0x7fffee789093 in non-virtual thunk to 
> TransferableHelper::getTransferData(com::sun::star::datatransfer::DataFlavor 
> const&) ()
> at 
> /usr/bin/../lib/gcc/x86_64-redhat-linux/8/../../../../include/c++/8/bits/stl_iterator.h:794
> #13 0x7fffd1267f3a in 
> VclToGtkHelper::setSelectionData(com::sun::star::uno::Reference
>  const&, _GtkSelectionData*, unsigned int) (this=0x22fb0b0, 
> rTrans=uno::Reference to (ScTransferObj *) 0x686c668, 
> selection_data=0x7ffedb50, info=5) at 
> /ssd1/lo/fedora/vcl/unx/gtk3/gtk3gtkinst.cxx:488
> #14 0x7fffd1267d44 in VclGtkClipboard::ClipboardGet(_GtkSelectionData*, 
> unsigned int) (
> this=0x22fafa0, selection_data=0x7ffedb50, info=5) at 
> /ssd1/lo/fedora/vcl/unx/gtk3/gtk3gtkinst.cxx:357
> #15 0x7fffd126a2ef in (anonymous 
> namespace)::ClipboardGetFunc(_GtkClipboard*, _GtkSelectionData*, unsigned 
> int, void*) (selection_data=0x7ffedb50, info=5, 
> user_data_or_owner=0x22fafa0) at 
> /ssd1/lo/fedora/vcl/unx/gtk3/gtk3gtkinst.cxx:385
> #16 0x75d18add in g_closure_invoke () at /lib64/libgobject-2.0.so.0
> #17 0x75d2bf43 in signal_emit_unlocked_R () at 
> /lib64/libgobject-2.0.so.0
> #18 0x75d3506a in g_signal_emit_valist () at 
> /lib64/libgobject-2.0.so.0
> #19 0x75d35b44 in g_signal_emit_by_name () at 
> /lib64/libgobject-2.0.so.0
> #20 0x7fffd0b570db in gtk_selection_invoke_handler () at 
> /lib64/libgtk-3.so.0
> #21 0x7fffd0b58c8e in _gtk_selection_request () at /lib64/libgtk-3.so.0
> #22 0x7fffd0ac67a8 in _gtk_marshal_BOOLEAN__BOXEDv () at 
> /lib64/libgtk-3.so.0
> #23 0x75d18d36 in _g_closure_invoke_va () at 
> /lib64/libgobject-2.0.so.0
> #24 0x75d34ae4 in g_signal_emit_valist () at 
> /lib64/libgobject-2.0.so.0
> #25 0x75d35663 in g_signal_emit () at /lib64/libgobject-2.0.so.0
> #26 0x7fffd0c14134 in gtk_widget_event_internal () at /lib64/libgtk-3.so.0
> #27 0x7fffd0ac5716 in gtk_main_do_event () at /lib64/libgtk-3.so.0
> #28 0x7fffd05ce639 in _gdk_event_emit () at /lib64/libgdk-3.so.0
> #29 0x7fffd05ffe76 in gdk_event_source_dispatch () at /lib64/libgdk-3.so.0
> #30 0x75a3d8ad in

[Desktop-packages] [Bug 1805257] [NEW] gnome apps provided by snaps show default "executable" icon with default icon theme

2018-11-26 Thread Alberto Donato

Public bug reported:

On 18.10 with GNOME session and default Adwaita icon theme, desktop apps
installed via snap, like gnome-calculator, gnome-system-monitor, ... all
have the default executable icon (diamond with gears), instead of their
own icons.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 26 23:50:22 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-11-24 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic package-from-proposed wayland-session

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

Title:
  gnome apps provided by snaps show default "executable" icon with
  default icon theme

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On 18.10 with GNOME session and default Adwaita icon theme, desktop
  apps installed via snap, like gnome-calculator, gnome-system-monitor,
  ... all have the default executable icon (diamond with gears), instead
  of their own icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 26 23:50:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 867424] Re: Oneric: On boot up Firefox always displays the “Well, This Is Embarrassing” screen.

2018-11-26 Thread Fabrizio Gennari

In the most recent version (example: Firefox 63.0.3 on Cosmic) the
behaviour is different. Firefox actually blocks the restart/shutdown
process by showing a popup "X tabs will be closed". But the whole OS
also creates a modal dialog box, asking whether to cancel, reboot or
turn off, and the modal dialog boxes actually prevents the user from
closing Firefox properly using the Firefox pop-up window. If "reboot" or
"turn off" are chosen, Firefox will show the dreaded "Well, This Is
Embarrassing" screen.

This is an improvement from the previous versions. However, a proper
shutdown sequence should allow the user to close applications properly
right after initiating the reboot/shutdown procedure.

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

Title:
  Oneric: On boot up Firefox always displays the “Well, This Is
  Embarrassing” screen.

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged
Status in firefox source package in Precise:
  Triaged
Status in thunderbird source package in Precise:
  Triaged

Bug description:
  This happens on every restart or boot. Firefox fails to load previous
  tabs.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:240: no soundcards found...
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20110929022028
  CRDA: Error: [Errno 2] No such file or directory
  Channel: release
  Date: Tue Oct  4 13:15:01 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, 
Version=2.1.4rc2, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, 
Type=extension, Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110910)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.4  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929022028 (Running)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserJS: general.useragent.vendor - Firefox
  dmi.bios.date: 01/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EH
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd01/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

system-ud cpu hog and flickering issues are unrelated, as when i
restarted the system-ud, and it did disappear from the top 20 process,
flickering issues didn't disappear, just less frequently happened, if I
restarted the chrome browser. (unfortunately my chrome browser is the
first program, what i tend to open and does not stop, even if i work 14
hours a day)

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

When I'm restarting it (Grammarly bug - not with it :)), system-ud does
not appear on the top 30 processes.

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

xperia phone = in context with usb tethering (so every test made on the
ubuntu laptop - with and without usb tethering)

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

I can't really test dns throttling, so the answer is no.

Latest experiences on this tricky issue. I had problems with prover
management in years time.

WIFI is unusable (using usb tethering), so and it's kept
"disconnecting". (disconnecting mean, that it's connected, but the
connection dies (locks the chrome tab, even if I'm kept pushing the
refresh button - if I open a new tab many times the responsiveness comes
back again) unlike xperia phone, where even if the wifi is disconnected
at some point not so frequently, the tab does not die, connecting back,
right away will get the connection and update the page, if it's
necessary)

Upgraded mesa on daily basis, and it was getting worse.

I have disabled the dimming (power management), and the problem seemed
to be disappeared for a while.

When I'm opening chrome before packageit process is finishing its job.
(so right away after I see the default desktop screen), I'm more likely
getting system-ud cpu hog (50-100%), and flickering issues. When I'm
restarting with it, system-ud does not appear on the top 30 processes.

When I restarted my chrome browser (the initial ubuntu loading has been
finished - no CPU usage - 1-2%), the flickering issue has not happened
that frequently.

I have disabled also screensavers. (i had to install the program to
disable it)

It seems to happen on full screen only and sometimes I have a feeling
that the ubuntu is just stopping after some inactivity period, as my
wifi is gone in the background. (unfortunately even if I set wifi always
on xperia, it seems disconnecting the wifi, but not that frequently, and
when i'm activating the xperia again goes back - but in this case wifi
should be always active)

I think it's something with the power management, what I felt so buggy
in the last couple of years. (the only thing which has been resolved,
that from hibernate mode it's not corrupting my ubuntu anymore, and
doesn't make cpu hog also)

It's very hard to really figure out when the problem happens, but I do
think it's nothing to do with mesa, it's something else, which keep
killing the mesa.

The voice was steadily working, just every 5-10 sec video playback
stopped for 3 sec. It's the worst case scenario.

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64

[Desktop-packages] [Bug 1805252] [NEW] keyring nightmare

2018-11-26 Thread jerryol...@ieee.org

Public bug reported:

Good day.  I an new to Ubuntu and run 9.04.  I set up a secure wireless
connection to the internet a few weeks ago, and entered the required
password for "unlock keyring",  which was the same as my logon PW. My
wireless hub has a separate hex PW.   Everytime I logon to my pc I'm
prompted for the "key ring" PW to enable my wireless connection - I find
this quite bothersome.

Recently I changed my logon password, however, the keyring application
does not accept my new password. I've tried deleting and reinstalling
the wireless network using my new password, however, I get dialog box
from  "unlock keyring" :

The application "nm-connection-editor" (/usr/bin/nm-connections-editor)
wants access to the default keyring, but it is locked.  It prompts for a
password, and it will not accept my new password, however, my old
password is accepted and the wireless connection to my internet hub is
completed.

I would be obliged for any help in getting the keyring application to
accept my new PW.Many thanks,

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

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

Title:
  keyring nightmare

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Good day.  I an new to Ubuntu and run 9.04.  I set up a secure
  wireless connection to the internet a few weeks ago, and entered the
  required password for "unlock keyring",  which was the same as my
  logon PW. My wireless hub has a separate hex PW.   Everytime I logon
  to my pc I'm prompted for the "key ring" PW to enable my wireless
  connection - I find this quite bothersome.

  Recently I changed my logon password, however, the keyring application
  does not accept my new password. I've tried deleting and reinstalling
  the wireless network using my new password, however, I get dialog box
  from  "unlock keyring" :

  The application "nm-connection-editor" (/usr/bin/nm-connections-
  editor) wants access to the default keyring, but it is locked.  It
  prompts for a password, and it will not accept my new password,
  however, my old password is accepted and the wireless connection to my
  internet hub is completed.

  I would be obliged for any help in getting the keyring application to
  accept my new PW.Many thanks,

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

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

[Desktop-packages] [Bug 1803848] Re: Playing video on chrome freezes frequently (Too slow to catch up)

Paco, with this last comment do you mean that after solving this DNS
throttling issue the problem with video playback is seemingly resolved?

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

Title:
  Playing video on chrome freezes frequently (Too slow to catch up)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest update of ubuntu made some strange problems:

  system-udev made a high CPU usage on nvidia, i have made a restart on
  the udev, thus i have decided to bleach it and run the following
  commands:

  sudo systemctl start systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket
  sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket

  It solved some of the flickering problem, but it did not disappear.

  I'm running on 120Hz, sometimes the screen resolution has been changed
  so quickly on boot, that i have noticed lines at the bottom of my
  screen. (like in a bad monitor) Why ubuntu needs to change that so
  frequently, it just amortize the graphics card.

  The real issue is that my video playback youtube / scolling main site
  of origo.hu (local news portal) etc. flickering frequently. It is too
  slow to catch up. Suddenly stops, and after 2-3 seconds it restarts.

  It only happens on chrome seems to me, and does not happen when i disabling 
gpu.
  https://bugs.chromium.org/p/chromium/issues/detail?id=906861#c8

  As a matter of fact, my CPU usage is not that much with or without gpu,
  so on gnome-shell some optimization needs to happen.

  Why i have GPU acceleration, if the gnome-shell swallows the benefit?

  On firefeox it does not happen, but the WebConsole CPU usage is 3
  times more than in chrome. (70-80% on a full hd video, which is
  burning up all my cpu time, so it cannot be the solution to jump to
  firefox)

  Other thing is that the cooler less frequently making noise without
  gpu, even if the CPU has got higher load. If the cooler is running on
  high frequency, i hardly able to work.

  The non-accelerated Chrome CPU usage is half of the accelerated
  firefox cpu usage.

  I have posted the problem on both side, because i have a feeling there
  is problem at the middle, how ubuntu and chrome corporates with each
  other.

  Visual studio code also has some high CPU problem while scrolling,
  cooler makes noise.

  To me seems that it does matter whether the gpu makes the heat or the cpu 
regarding to cooling insensitivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-08-07 (471 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (89 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1803848/+subscriptions

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

[Desktop-packages] [Bug 1805247] [NEW] Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen

2018-11-26 Thread Juan Martinez

Public bug reported:

-- Ubuntu 18.04 LTS
-- gnome-shell 3.28.1-0ubuntu2

When user is logged in using Wayland, swipe-up gesture cannot be used to
summon the OSK.  Problem is non-existent on Xorg.

This has been reproduced on multiple devices, leaving the user unable to
use the OSK in many situations.

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

** Description changed:

- Ubuntu 18.04 LTS
- 
- gnome-shell 3.28.1-0ubuntu2
+ -- Ubuntu 18.04 LTS
+ -- gnome-shell 3.28.1-0ubuntu2
  
  When user is logged in using Wayland, swipe-up gesture cannot be used to
  summon the OSK.  Problem is non-existent on Xorg.
  
  This has been reproduced on multiple devices, leaving the user unable to
  use the OSK in many situations.

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

Title:
  Onscreen Keyboard in Wayland cannot be summoned by swiping up on the
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  -- Ubuntu 18.04 LTS
  -- gnome-shell 3.28.1-0ubuntu2

  When user is logged in using Wayland, swipe-up gesture cannot be used
  to summon the OSK.  Problem is non-existent on Xorg.

  This has been reproduced on multiple devices, leaving the user unable
  to use the OSK in many situations.

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

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

[Desktop-packages] [Bug 837557] Re: fraudulent DigiNotar certificate issuance

Nora Blob, Ubuntu 17.10 is EOL and not supported any longer. Is the
issue present in a supported release of Ubuntu (14.04, 16.04, 18.04,
18.10) or in the current development version (19.04) ?

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

Title:
  fraudulent DigiNotar certificate issuance

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in seamonkey package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.2 package in Ubuntu:
  Invalid
Status in ca-certificates source package in Lucid:
  Fix Released
Status in chromium-browser source package in Lucid:
  Fix Released
Status in firefox source package in Lucid:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in qt4-x11 source package in Lucid:
  Fix Released
Status in seamonkey source package in Lucid:
  Won't Fix
Status in thunderbird source package in Lucid:
  Fix Released
Status in xulrunner-1.9.2 source package in Lucid:
  Fix Released
Status in ca-certificates source package in Maverick:
  Fix Released
Status in chromium-browser source package in Maverick:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in nss source package in Maverick:
  Fix Released
Status in qt4-x11 source package in Maverick:
  Fix Released
Status in seamonkey source package in Maverick:
  Won't Fix
Status in thunderbird source package in Maverick:
  Fix Released
Status in xulrunner-1.9.2 source package in Maverick:
  Fix Released
Status in ca-certificates source package in Natty:
  Fix Released
Status in chromium-browser source package in Natty:
  Fix Released
Status in firefox source package in Natty:
  Fix Released
Status in nss source package in Natty:
  Fix Released
Status in qt4-x11 source package in Natty:
  Fix Released
Status in seamonkey source package in Natty:
  Won't Fix
Status in thunderbird source package in Natty:
  Fix Released
Status in xulrunner-1.9.2 source package in Natty:
  Fix Released
Status in ca-certificates source package in Oneiric:
  Fix Released
Status in chromium-browser source package in Oneiric:
  Fix Released
Status in firefox source package in Oneiric:
  Fix Released
Status in nss source package in Oneiric:
  Fix Released
Status in qt4-x11 source package in Oneiric:
  Fix Released
Status in seamonkey source package in Oneiric:
  Won't Fix
Status in thunderbird source package in Oneiric:
  Fix Released
Status in xulrunner-1.9.2 source package in Oneiric:
  Invalid
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  USN Information: This is being tracked in USN-1197-*

  NOTE: The Firefox update causes a regression for certain Dutch sites which is 
being tracked in Bug #838322.
  NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA 
as trusted in the certificate manager.  This is due to Thunderbird using the 
system version of NSS. In this initial update, Thunderbird will actively 
distrust any certificate signed by the DigiNotar Root CA.  Future updates will 
properly show the root CA as distrusted in the certificate manager.

  WORKAROUND (from blog post):
  http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert

  -

  http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-
  certificate/

  Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the-
  diginotar-security-breach-means-for-qt-users-continued/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/837557/+subscriptions

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

[Desktop-packages] [Bug 1805241] [NEW] Problem using secret-tool as root

2018-11-26 Thread pickadi

Public bug reported:

Ubuntu release: 18.10 x64
Package version: libsecret-tools 0.18.6-3

Command example: sudo secret-tool store --label='password' key value
(similar issues can be obtained with secret-tool lookup / clear /
search)

Expected behavior: the same behavior as a non-privileged user, that is:
no output in stdout nor syslog, secret-tool simply asks for the password
and stores it.

Observed behavior: After a few seconds of waiting, secret-tool crashes
with the following output in stdout:

(secret-tool:3394): GLib-GObject-CRITICAL **: 15:45:12.811: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

and the following output in /var/log/syslog:

dbus-daemon[4246]: [session uid=0 pid=4244] AppArmor D-Bus mediation is enabled
dbus-daemon[4246]: [session uid=0 pid=4244] Activating service 
name='org.freedesktop.secrets' requested by ':1.0' (uid=0 pid=4240 
comm="secret-tool store --label=password key value " label="unconfined")
gnome-keyring-d[4249]: couldn't create socket directory: 
/home/user/.cache/keyring-XTN8SZ: Permission denied
gnome-keyring-d[4249]: couldn't bind to control socket: 
/home/user/.cache/keyring-XTN8SZ/control: Permission denied

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

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

Title:
  Problem using secret-tool as root

Status in libsecret package in Ubuntu:
  New

Bug description:
  Ubuntu release: 18.10 x64
  Package version: libsecret-tools 0.18.6-3

  Command example: sudo secret-tool store --label='password' key value
  (similar issues can be obtained with secret-tool lookup / clear /
  search)

  Expected behavior: the same behavior as a non-privileged user, that
  is: no output in stdout nor syslog, secret-tool simply asks for the
  password and stores it.

  Observed behavior: After a few seconds of waiting, secret-tool crashes
  with the following output in stdout:

  (secret-tool:3394): GLib-GObject-CRITICAL **: 15:45:12.811: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

  and the following output in /var/log/syslog:

  dbus-daemon[4246]: [session uid=0 pid=4244] AppArmor D-Bus mediation is 
enabled
  dbus-daemon[4246]: [session uid=0 pid=4244] Activating service 
name='org.freedesktop.secrets' requested by ':1.0' (uid=0 pid=4240 
comm="secret-tool store --label=password key value " label="unconfined")
  gnome-keyring-d[4249]: couldn't create socket directory: 
/home/user/.cache/keyring-XTN8SZ: Permission denied
  gnome-keyring-d[4249]: couldn't bind to control socket: 
/home/user/.cache/keyring-XTN8SZ/control: Permission denied

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

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

[Desktop-packages] [Bug 1804853] Re: firefox menu button stops working after update

What desktop environment / session do you use? I'm not seeing that in
the default GNOME/X11 session on 18.04 (there's no menu bar there,
either).

Can you please run the following command to attach additional
information to the bug report?

apport-collect 1804853

Thanks!

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

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

Title:
  firefox menu button stops working after update

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After an update of Ubuntu 18.04, firefox stopped working. Uninstalling
  and reinstalling does not help. Starting in safe-mode does not help.

  The part that stopped working is certain menus. The seven menus on the
  menu bar (File/Edit/View/History/Bookmarks/Tools/Help) all work, that
  is, they show a drop-down menu for the left mouse button, nothing for
  the middle mouse button, and "Pin to Overflow Menu / Remove from
  Toolbar / Menu Bar / Bookmarks Toolbar / Customize" for the right
  mouse button. Fine.

  The 3-bar button on the right gives zero reaction to left or middle
  button and comes with the same "Pin to Overflow Menu / Remove from
  Toolbar / Menu Bar / Bookmarks Toolbar / Customize" for the right
  mouse button. Bad.

  The small triangles in menus as given in the preferences (for example
  to set Default Font or Font Size) do not react to any mouse button.
  Bad.

  $ firefox --version
  Mozilla Firefox 63.0.3
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy firefox
  firefox:
Installed: 63.0.3+build1-0ubuntu0.18.04.1
Candidate: 63.0.3+build1-0ubuntu0.18.04.1
Version table:
   *** 63.0.3+build1-0ubuntu0.18.04.1 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  What I expected to happen: 3-bar and triangle mouse buttons react to left 
mouse button.
  What happens: no reaction.

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

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

[Desktop-packages] [Bug 1803142] Re: [SRU] libreoffice 6.1.3 for cosmic

One of the crashes fixed in 6.1.3 was reported as a separate bug report
by an Ubuntu user: bug #1804688.

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

Title:
  [SRU] libreoffice 6.1.3 for cosmic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New

Bug description:
  [Impact]

   * LibreOffice 6.1.3 is the third bugfix release of the fresh 6.1 line. 
Version 6.1.2 is currently in cosmic.
 For a list of fixed bugs compared to 6.1.2 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.3/RC2#List_of_fixed_bugs
 (that's a total of 66 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 66 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1804688] Re: libreoffice always crashes when I do this

This is an upstream crash
(https://bugs.documentfoundation.org/show_bug.cgi?id=118416), which was
fixed in 6.1.3, which will soon be SRU’d to cosmic (see bug #1803142).

** Bug watch added: Document Foundation Bugzilla #118416
   https://bugs.documentfoundation.org/show_bug.cgi?id=118416

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=118416
   Importance: Unknown
   Status: Unknown

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

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

Title:
  libreoffice always crashes when I do this

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805189] Re: gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  i7-8750H (6 cores, 12 threads)
  32GB DDR
  GTX 1070 Max-Q
  500GB SSD
  4K external monitor (Dell U2718Q)

  No problem without the 4K monitor hooked up. When it is hooked up,
  CPU1 ~ 100% in idle. Gnome-shell and Xorg the problem.

  nvidia 410 from nvidia-ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 00:22:13 2018
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

2018-11-26 Thread Adam Niedling

Example video of the Launcher being visible on top of the Lock screen:

https://bugs.launchpad.net/ubuntu/+source/gnome-
screensaver/+bug/1805014/+attachment/5216139/+files/Launcher%20visible%20on%20Lock%20screen.ogv

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

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

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

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805014] Re: Launcher is visible on the Lock screen and apps can be launched

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

** This bug has been marked a duplicate of bug 1803807
   Lock screen doesn't hide the screen contents

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

Title:
  Launcher is visible on the Lock screen and apps can be launched

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This is happening after upgrading from 18.04 to 18.10. I have to press
  super+l twice. When pressing it the first time the text from the top
  bar disappears. Pressing it the second time brings up the Lock screen
  but the Launcher stays on top of it. Apps can be launched/closed as
  well. They can be right clicked too.

  I've created a video about this problem.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 25 15:24:42 2018
  InstallationDate: Installed on 2017-08-13 (468 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to cosmic on 2018-10-23 (33 days ago)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805134] Re: Ability to launch/view apps from lock screen

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

** This bug is no longer a duplicate of bug 1805014
   Launcher is visible on the Lock screen and apps can be launched
** This bug has been marked a duplicate of bug 1803807
   Lock screen doesn't hide the screen contents

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

Title:
  Ability to launch/view apps from lock screen

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I've come across a problem where I am able to perform several tasks
  from the lock screen which should not be possible. This includes:

- Viewing desktop windows currently running as the logged-in user
- Launching programs as the logged-in user
- Closing windows of running programs
- Enabling/disabling network interfaces and joining networks

  I don't believe there's a way to interact with the running programs -
  it's only possible to start a program and view its preview thumbnail.

  Another note is that I had to press Super+L twice to lock the screen,
  which has been mentioned in other recent bugs.

  The unfortunate part is that my PC has been running for days and I
  have absolutely no idea how I got it into this state. I upgraded it
  from 18.04 to 18.10 earlier this week. It was a clean 18.04 install
  from a few months back. I haven't done anything that I would consider
  a desktop customisation.

  I've taken some crude hand-held video of the issue.

  https://youtu.be/TjH9KUjA6pY

  I could not show the entire Thunderbird window as it displayed my
  email address. However it's there.

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

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

[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2018-11-26 Thread Adam Conrad

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libdrm (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack

2018-11-26 Thread Adam Conrad

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-7 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-7/1:7-3~ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: llvm-toolchain-7 (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

** Changed in: libdrm (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

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

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

[Desktop-packages] [Bug 1798597] Please test proposed package

2018-11-26 Thread Adam Conrad

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

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

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

[Desktop-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-26 Thread Jonathan Polak

Both Gnome and Gnome-on-Xorg exhibit the same behavior when connecting a
DP monitor. The HID freezes until disconnecting the DP screen.

Both Gnome and Gnome-on-Xorg work on HDMI. 
I left the HDMI connected when switching between Gnome and Gnome-on-Xorg. When 
I unplugged HDMI it crashed the Gnome-on-Xorg session. Upon re-logon to that 
session with no monitor connected Ubuntu automatically created an error report 
which was generated on  2018 Nov 26 @ 10:34 Pacific Standard Time (18:34 UTC ) 

TITLED: Xorg crashed with SIGABRT in WaitForSomething()
PACKAGE: xserver-xorg-core 2:1.20.1-3ubuntu2.1

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multi-monitor mode.

  
  EDIT: 2018-11-22 // The problems are not observed when using HDMI instead of 
mini display-port. Moreover, if one can regain control of HID devices when mini 
DP plugged in, the resolution of the monitor plugged in is completely wrong. 

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2016-07-23 (848 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog:
   (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: LENOVO 20F9004FUS
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=074ff7b7-c074-4137-8cf7-d46cdd7dd723 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic ubuntu
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (32 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9004FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20F9004FUS:pvrThinkPadT460s:rvnLENOVO:rn20F9004FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20F9004FUS
  dmi.product.sku: LENOVO_MT_20F9_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded:

[Desktop-packages] [Bug 1804683] Re: there is too many errors in my ubuntu 18.04

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

** Information type changed from Private Security to Public

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

Title:
  there is too many errors in my ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to install nvidia driver 415 there is already 390 but the
  laptop recommends 415 when i insert the code it says that there is a
  held broken packeges please help me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 18:59:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1804693] Re: Copy problem with small files from shares mounted with libpam-mount

2018-11-26 Thread Alexandre Neveux

Hello,

Here my simple configuration working well since two years except this
issue:

libpam-mount configuration:
---
$ sudo apt-get install cifs-utils libpam-mount
$ sudo vi /etc/security/pam_mount.conf.xml






samba configuration:

[homes]
   comment = Home directories
   browseable = no
   read only = no
   create mask = 0644
   directory mask = 0755
   valid users = %S

Copying files with cp or gvfs-copy works well without any issue.

I can report this bug with Xfce Manjaro, Gnome Fedora, Cinnamon/Mate LinuxMint 
too.
This bug doesn't appear on KDE !

Kind regards

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

Title:
  Copy problem with small files from shares mounted with libpam-mount

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Dear all,

  With a fresh install of ubuntu 18.04.1 and libpam-mount, I encounter
  issue when I copy small text files of few octets from remote share to
  local host with nautilus.

  More exactly, when I paste the file from a mounted remote samba share
  to a local directory, nautilus reports a time of transfer of
  approximatively 596523 hours! The process keep locked and I need to
  killall nautilus to terminate the copy.

  It seems that nautilus is unable to "understand" the end of copy
  because the file is well copied from remote to local directory and is
  usable.

  Can you resolve this issue please ?

  Kind regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 20:01:59 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'235'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+992+52'"
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating

2018-11-26 Thread Joe Barnett

I'll try to test on an X session in a bit.  One thing I have noticed is
that while I still get the log messages, the unrotate behavior seems
much better when setting the `dc=0` amdgpu module parameter (was also
behaving better with the module blacklisted, but not sure about log
messages), as per comments in
https://gitlab.gnome.org/GNOME/mutter/issues/357 and
https://gitlab.gnome.org/GNOME/mutter/issues/365

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

Title:
  [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in iio-sensor-proxy package in Ubuntu:
  Confirmed

Bug description:
  on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy
  functionality by doing:

  modprobe intel-ish-ipc
  echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id

  
  This makes `monitor-sensor` display rotation events, and gnome-shell 
auto-rotate the screen upon receiving them.  However, immediately after 
rotating, the screen rotates back to its normal orientation (unless I quickly 
lock rotation), displaying the following in journalctl:

  Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 
1: Invalid argument
  Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully.
  Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 10 09:06:40 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-26 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago)

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

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

[Desktop-packages] [Bug 1805014] Re: Launcher is visible on the Lock screen and apps can be launched

** Information type changed from Private Security to Public Security

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

Title:
  Launcher is visible on the Lock screen and apps can be launched

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This is happening after upgrading from 18.04 to 18.10. I have to press
  super+l twice. When pressing it the first time the text from the top
  bar disappears. Pressing it the second time brings up the Lock screen
  but the Launcher stays on top of it. Apps can be launched/closed as
  well. They can be right clicked too.

  I've created a video about this problem.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 25 15:24:42 2018
  InstallationDate: Installed on 2017-08-13 (468 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to cosmic on 2018-10-23 (33 days ago)

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

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

[Desktop-packages] [Bug 1804894] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

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

** Information type changed from Private Security to Public

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  usb drivers needed for china phone

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 09:16:38 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-11-23 (0 days ago)
  InstallationMedia: Lubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-11-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1804894/+subscriptions

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

[Desktop-packages] [Bug 1804935] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

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

** Information type changed from Private Security to Public

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  Uname: Linux 4.18.7 x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Sat Nov 24 19:27:53 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2017-08-12 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804949] Re: Screen locking issue data leak~

** Information type changed from Private Security to Public Security

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

Title:
  Screen locking issue data leak~

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Closing laptop (HP-ProBook-6470b) lid lights go out and appears to
  sleep.

  Opening lid displays last desktop & window contents, mouse cursor does
  move around but screen cannot be interacted with.

  Then screen will flash repeatedly, 10 times or so.

  Closing lid , waiting for sleep again, and reopening lid results in a
  login screen as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 24 10:57:58 2018
  InstallationDate: Installed on 2018-11-04 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805014] Re: Launcher is visible on the Lock screen and apps can be launched

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

** Changed in: gnome-screensaver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Launcher is visible on the Lock screen and apps can be launched

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This is happening after upgrading from 18.04 to 18.10. I have to press
  super+l twice. When pressing it the first time the text from the top
  bar disappears. Pressing it the second time brings up the Lock screen
  but the Launcher stays on top of it. Apps can be launched/closed as
  well. They can be right clicked too.

  I've created a video about this problem.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 25 15:24:42 2018
  InstallationDate: Installed on 2017-08-13 (468 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to cosmic on 2018-10-23 (33 days ago)

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

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

[Desktop-packages] [Bug 1805200] [NEW] Xorg crashes when it tries to resume a scale transformation after that Screen has been closed

2018-11-26 Thread Treviño

Public bug reported:

Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous versions

Very easy to reproduce:
Start a simple (empty) X server instance (say Xorg :2 vt8)
Set a scale transformation
xrandr -d :2 --output eDP-1 --scale 2x2
Call xrandr again so that the server tries to resume the previous 
transformation
xrandr -d :2

I've addressed the issue at
https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
various fixes for that, but so far no feedback.

Marking it as incoming rls bug as this needs to be addressed as per
supporting xrandr scaling support in desktop.

** Affects: xorg (Ubuntu)
 Importance: High
 Assignee: Timo Aaltonen (tjaalton)
 Status: Triaged


** Tags: rls-dd-incoming

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

Title:
  Xorg crashes when it tries to resume a scale transformation after that
  Screen has been closed

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous
  versions

  Very easy to reproduce:
  Start a simple (empty) X server instance (say Xorg :2 vt8)
  Set a scale transformation
  xrandr -d :2 --output eDP-1 --scale 2x2
  Call xrandr again so that the server tries to resume the previous 
transformation
  xrandr -d :2

  I've addressed the issue at
  https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
  various fixes for that, but so far no feedback.

  Marking it as incoming rls bug as this needs to be addressed as per
  supporting xrandr scaling support in desktop.

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

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

[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-26 Thread Junaid Ahmed

Tested positive on: Intel Core i3 3rd generation, Intel HD graphics
Also with Intel Core i7 8700k & Intel Core M-5Y31

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

2018-11-26 Thread Paul

I'm using a jack connector. I use a steelseries arctis 3 but I tries
with other mics.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805048/+attachment/5216539/+files/journal.txt

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics

2018-11-26 Thread Michael Thayer

Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is
not.

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

Title:
   Desktop freeze running VirtualBox, Intel graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  This is identical to bug 1804885, but as requested I am filing this while 
running the standard Ubuntu kernel.  I will copy and paste my summary below.  
Updates since I created that bug:
   * This occurs with the mainline PPA 4.18.12-041812-generic kernel.
   * The glxinfo section I include below is identical with 4.18.0-11-generic 
(presumably no surprise).
   * I would appreciate a bit of hand-holding for bisecting this.  Does the 
kernel team have ready-built kernel packages for bisecting?  Or guidance about 
the fastest way of doing it (i.e. not rebuilding things which do not need to be 
rebuilt for successive rounds)?

  === Original report follows ===

  When I start a VirtualBox virtual machine (reproducible with the
  Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with
  VMSVGA emulation and 3D pass-through enabled, my system hangs.
  Sometimes I can recover if I get to a VT fast enough to kill the
  process. Also, the OOM killer sometimes triggers and kills the process
  or gnome-shell, but the OOM killer entries in dmesg look like neither
  of the two are using excessive memory compared to available system
  RAM. When I switch to the Ubuntu drm-tip kernel packages from the
  kernel PPA the problem goes away. Debugging shows that the hang occurs
  during the first glXMakeCurrent call made by the application. It did
  not occur using the standard Ubuntu kernel but running the application
  under apitrace. I can provide the trace if that helps.

  Short extract from glxinfo running the 4.20 drm-tip kernel:

  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916)
  Version: 18.2.2
  Accelerated: yes
  Video memory: 3072MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 26 15:01:53 2018
  DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2018-06-12 (166 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HES0E73E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET78W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES0E73E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HES0E73E
  dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1

[Desktop-packages] [Bug 1805189] [NEW] gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

2018-11-26 Thread Tuan Ho

Public bug reported:

i7-8750H (6 cores, 12 threads)
32GB DDR
GTX 1070 Max-Q
500GB SSD
4K external monitor (Dell U2718Q)

No problem without the 4K monitor hooked up. When it is hooked up, CPU1
~ 100% in idle. Gnome-shell and Xorg the problem.

nvidia 410 from nvidia-ppa.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 27 00:22:13 2018
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-shell high CPU usage (~100% CPU1) in idle with external monitor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i7-8750H (6 cores, 12 threads)
  32GB DDR
  GTX 1070 Max-Q
  500GB SSD
  4K external monitor (Dell U2718Q)

  No problem without the 4K monitor hooked up. When it is hooked up,
  CPU1 ~ 100% in idle. Gnome-shell and Xorg the problem.

  nvidia 410 from nvidia-ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 00:22:13 2018
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

2018-11-26 Thread Paul

*tried ;-)
And thank you for helping !

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

The issue was fixed in cosmic and the fix was part of that SRU update to bionic
https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.1

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1723249] Re: gnome-control-center crashed with SIGSEGV in maybe_add_app_id()

The issue was fixed in 3.30 upstream, could be worth SRUing back to
bionic, https://gitlab.gnome.org/GNOME/gnome-control-
center/merge_requests/120

(The e.u.c reports confirms that's the case
https://errors.ubuntu.com/problem/3a5b4bfcb598ac34a0b6249c7ce3787819dd2065)

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-control-center crashed with SIGSEGV in maybe_add_app_id()

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  open gnome-control-center . then try to set night light

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 16:23:02 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5593df67e4e5:cmpb   $0x0,(%rbx)
   PC (0x5593df67e4e5) ok
   source "$0x0" ok
   destination "(%rbx)" (0x4002) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1769260] Re: file-roller fails for one usser while tar works

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Low

** Changed in: file-roller (Ubuntu)
   Status: New => Incomplete

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

Title:
  file-roller fails for one usser while tar works

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  file-roller adds user gja directories fine. However, for user lin it
  gets well into the adding of files when it fails saying it cannot find
  a file in "/home/lin/.config/dconf/user.13FBIZ". I suspect this might
  be a temporary file it is building, Every time I try it the error is
  the same except the ending after the last dot in the file name
  changes. This may be a bug or suggest a flaw in the data it is adding.

  The system operates correctly for all users, even the account that is
  supposed to be backed up. Also if I look in the specified directory I
  do not see the file for which it is looking.

  Directly using tar works fine. Tar must use a pipe to connect to a
  compressor but does not run into the name problem file-roller does.
  You may want to consider this a bug.

  This is Unbuntu 18.04 LTS
  On a new machine with:
11.6 GiB
intel Core i5-7400 CPU @ 3.OOGHz x 4
intel HD Graphics 630 (Kaby Lake GT2)
GNOME 3.28.1
64-bit
Disk 124.4 GB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: file-roller 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 15:43:46 2018
  InstallationDate: Installed on 2018-04-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

2018-11-26 Thread Claude van Ackere

-- Logs begin at Thu 2018-11-01 16:00:55 CET, end at Mon 2018-11-26 16:45:36 
CET. --
nov. 26 16:42:47 claude-M61PME-S2P mintmenu[12883]: mintMenu.py: Fatal IO error 
11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P unknown[12887]: clock-applet: Fatal IO error 
11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]: XIO:  fatal IO 
error 11 (Resource temporarily unavailab
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]:   after 5057 
requests (5057 known processed) with 0
nov. 26 16:42:47 claude-M61PME-S2P unknown[12889]: notification-area-applet: 
Fatal IO error 11 (Ressource temporaireme
nov. 26 16:42:47 claude-M61PME-S2P unknown[12885]: wnck-applet: Fatal IO error 
11 (Ressource temporairement non dispon
nov. 26 16:42:47 claude-M61PME-S2P polkitd(authority=local)[698]: Unregistered 
Authentication Agent for unix-session:c
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12397 (lightdm) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12415 (gnome-keyring-d) with signal 
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12762 (ssh-agent) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12912 (applet.py) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 13265 (dbus-launch) with signal SIGT
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 13931 (xplayer) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopping Session c12 of user 
claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopped Session c12 of user 
claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd-logind[628]: Removed session c12.
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so:
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: 
pam_kwallet.so
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.s
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: 
pam_kwallet5.so

Lightdm ends on login screen

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

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

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 09:10:12 2018
  InstallationDate: Installed on 2018-04-28 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions

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

[Desktop-packages] [Bug 1763591] Re: dlmopen glib2.0 crashed in g_variant_lookup_value

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software on https://gitlab.gnome.org/GNOME/glib/issues/

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  dlmopen glib2.0 crashed in g_variant_lookup_value

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  when dlmopen glib2.0 and the program is linked with pthread, glib2.0 crashed 
in g_variant_lookup_value when dlmopen with 
  LM_ID_NEWLM

  following is the poc:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  
  int main(int argc, char*argv[])
  {
char buf[4096] = {0};
pthread_attr_t attr;

pthread_attr_init();
snprintf(buf, sizeof(buf), "/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2");
dlmopen(-1, buf, RTLD_NOW|RTLD_LOCAL);
return 0;
  }

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

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

[Desktop-packages] [Bug 1767877] Re: /usr/bin/gnome-software:realloc(): invalid old size

There has been no report on 3.30, assuming it's fixed in the current
version

** Changed in: gnome-software (Ubuntu)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Released

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

Title:
  /usr/bin/gnome-software:realloc(): invalid old size

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/ef4d4c0327e15e2fad0077b413cefdcf872f8a8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

2018-11-26 Thread Claude van Ackere

This happens from time to time in CAJA and when launching VLC.

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

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

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 09:10:12 2018
  InstallationDate: Installed on 2018-04-28 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-26 Thread Brian Murray

Hello Dariusz, or anyone else affected,

Accepted unity-settings-daemon into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-settings-daemon/15.04.1+16.04.20160701-0ubuntu3 in a few hours,
and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unity-settings-daemon (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1763256] Re: The "update-interval" don't go beyond 100 secs and the app can crash

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

One alternative would be to provide the id of the automatic report you
mentioned.

Also if the only way to trigger the bug is to change the schemas by hand
then it's not a really a bug that impacts Ubuntu, could still be a bug
in the code not handling that change but that would be reported upstream

** Changed in: gnome-system-monitor (Ubuntu)
Importance: Undecided => Low

** Changed in: gnome-system-monitor (Ubuntu)
Status: New => Incomplete

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

Title:
The "update-interval" don't go beyond 100 secs and the app can crash

Status in gnome-system-monitor package in Ubuntu:
Incomplete

Bug description:
Steps:

1 - Edit the range on the 'update-interval' key to a max over 100.00 seconds.
2 - Re-compile the schemas (glib-compile-schemas)
3 - Run gnome-system-monitor.
4 - Open the 'Preferences' window
5 - Click on the "+" button several times
6 - Verify that it won't be beyond "100.00".

Also, if after following the above steps you use 'gsettings' or
'dconf-editor' to update the current value to a value above 100.00
secs you will see that the 'Preferences' window will keep the value
'100.00' - please see the attached screenshot.

Finally, during the tests the app crashed several times. At least in
one of them I sent the automatic report.

My environment:

Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

Hardware:

Memory: 7.7 GiB
Processor: Intel Core i7-5600U CPY @ 2.60GHz x 4
Graphics: Intel HG Graphics 5500 (Broadwell GT2)
OS type:64-bit
Disk: 243.6 GB

Please, let me know if you need more data or info.

Thank you.

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

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

[Desktop-packages] [Bug 1802586] Re: sane-backends library name issues

2018-11-26 Thread Gianfranco Costamagna

we should probably ask debian to provide a transitional package too

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

Title:
  sane-backends library name issues

Status in sane-backends package in Ubuntu:
  New

Bug description:
  There is a dispute in Debian about the package name for the sane
  library.

  See especially https://bugs.debian.org/913346

  Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+subscriptions

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

[Desktop-packages] [Bug 1156335] Re: gedit crashed with signal 5 in _XReply()

2018-11-26 Thread Paul White

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to
expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  gedit crashed with signal 5 in _XReply()

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  This occurred when editing sources.list ; was opened by a right-click
  script in nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gedit 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 17 15:44:11 2013
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2013-02-12 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  MarkForUpload: True
  ProcCmdline: gedit /home/username/Desktop/comms-start
  Signal: 5
  SourcePackage: gedit
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gedit crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to raring on 2013-03-09 (8 days ago)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1094991] Re: gedita doesn't delete temporary / backup files (name type: admin~, hidden)

2018-11-26 Thread Paul White

paolode,

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug nearly six years
ago and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to
expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  gedita doesn't delete temporary / backup files (name type: admin~,
  hidden)

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  gedit doesn't delete temporary / backup hidden files (name type:
  admin~)

  ubuntu  12.04,   gedit 3.4.1

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

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

[Desktop-packages] [Bug 1726906] Re: invalid read in the plugin loader code

I didn't see that one in recent version, closing

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  invalid read in the plugin loader code

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Using the 17.10 version valgrind shows that error (the system has an
  invalid snap store login account configured so it might be due to
  that)

  ==4467== Invalid read of size 8
  ==4467==at 0x52E7747: g_type_check_instance_is_a (gtype.c:4008)
  ==4467==by 0x175E3C: GS_IS_PLUGIN_EVENT (gs-plugin-event.h:34)
  ==4467==by 0x175E3C: gs_plugin_event_add_flag (gs-plugin-event.c:210)
  ==4467==by 0x52C1F9C: g_closure_invoke (gclosure.c:804)
  ==4467==by 0x52D4CDD: signal_emit_unlocked_R (gsignal.c:3635)
  ==4467==by 0x52DD4B4: g_signal_emit_valist (gsignal.c:3391)
  ==4467==by 0x52DDECE: g_signal_emit (gsignal.c:3447)
  ==4467==by 0x52C6463: g_object_dispatch_properties_changed 
(gobject.c:1080)
  ==4467==by 0x52C8838: g_object_notify_by_spec_internal (gobject.c:1173)
  ==4467==by 0x52C8838: g_object_notify (gobject.c:1221)
  ==4467==by 0x17AECF: gs_plugin_loader_notify_idle_cb 
(gs-plugin-loader.c:297)
  ==4467==by 0x5550E24: g_main_dispatch (gmain.c:3148)
  ==4467==by 0x5550E24: g_main_context_dispatch (gmain.c:3813)
  ==4467==by 0x55511EF: g_main_context_iterate.isra.30 (gmain.c:3886)
  ==4467==by 0x555127B: g_main_context_iteration (gmain.c:3947)
  ==4467==  Address 0x2bf16960 is 0 bytes inside a block of size 72 free'd
  ==4467==at 0x4C30D3B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==4467==by 0x52E6AB0: g_type_free_instance (gtype.c:1943)
  ==4467==by 0x1783F1: glib_autoptr_cleanup_GObject 
(gobject-autocleanups.h:25)
  ==4467==by 0x1783F1: glib_autoptr_cleanup_GsPluginEvent 
(gs-plugin-event.h:34)
  ==4467==by 0x1783F1: gs_plugin_loader_create_event_from_error 
(gs-plugin-loader.c:332)
  ==4467==by 0x1783F1: gs_plugin_error_handle_failure 
(gs-plugin-loader.c:410)
  ==4467==by 0x17953F: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:742)
  ==4467==by 0x17A073: gs_plugin_loader_run_refine_internal 
(gs-plugin-loader.c:816)
  ==4467==by 0x17A58E: gs_plugin_loader_run_refine (gs-plugin-loader.c:950)
  ==4467==by 0x17B14F: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3170)
  ==4467==by 0x58A5D55: g_task_thread_pool_thread (gtask.c:1328)
  ==4467==by 0x557900F: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==4467==by 0x5578644: g_thread_proxy (gthread.c:784)
  ==4467==by 0x82D07FB: start_thread (pthread_create.c:465)
  ==4467==by 0x85FCB0E: clone (clone.S:95)
  ==4467==  Block was alloc'd at
  ==4467==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==4467==by 0x5556578: g_malloc (gmem.c:94)
  ==4467==by 0x556E0F5: g_slice_alloc (gslice.c:1025)
  ==4467==by 0x556E588: g_slice_alloc0 (gslice.c:1051)
  ==4467==by 0x52E66D4: g_type_create_instance (gtype.c:1848)
  ==4467==by 0x52C75E7: g_object_new_internal (gobject.c:1797)
  ==4467==by 0x52C8D84: g_object_new_with_properties (gobject.c:1965)
  ==4467==by 0x52C9800: g_object_new (gobject.c:1637)
  ==4467==by 0x175F91: gs_plugin_event_new (gs-plugin-event.c:319)
  ==4467==by 0x178294: gs_plugin_loader_create_event_from_error 
(gs-plugin-loader.c:347)
  ==4467==by 0x178294: gs_plugin_error_handle_failure 
(gs-plugin-loader.c:410)
  ==4467==by 0x17953F: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:742)
  ==4467==by 0x17A073: gs_plugin_loader_run_refine_internal 
(gs-plugin-loader.c:816)

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

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

[Desktop-packages] [Bug 1760240] Re: Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

Thank you for your bug report, that looks like an upstream issue and
should be reported on https://gitlab.gnome.org/GNOME/gtk/issues

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  In all repositories there is a buffer-overrun in the function
  gtk_rc_add_default_file(), where if the dynamic array
  gtk_rc_default_files has exactly max_default_files entries, a NULL
  will be written past the allocated memory.  The resize function does
  not resize the null terminated array in this case, and address
  sanitizer (and valgrind) detects a memory access violation in any code
  leading to this function.

  The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
  {{{
for (n = 0; n < max_default_files; n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n == max_default_files)
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  Proposed modified implementation is as follows:
  {{{
for (n = 0; n < (max_default_files-1); n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n >= (max_default_files-1))
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  This implementation should be changed in all branches:

  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1760240/+subscriptions

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

[Desktop-packages] [Bug 1738538] Re: Scrolling (with two finger scroll) not working in shotwell

Bionic has shotwell 0.28 and it's fixed there

** Changed in: shotwell (Ubuntu)
   Importance: Undecided => Low

** Changed in: shotwell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Scrolling (with two finger scroll) not working in shotwell

Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  Scrolling the photos pane with my trackpad doesn't work in shotwell.
  Scrolling the library pane (list of events) works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 12:37:09 2017
  InstallationDate: Installed on 2017-12-14 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723824] Re: Unable to scroll down to all photos

The issue was fixed in newer versions

** Changed in: shotwell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Unable to scroll down to all photos

Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  Shotwell would not let my scroll down any further to select some
  photoss on the bottom row.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:54:26 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718694] Re: /usr/lib/gvfs/gvfsd-mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Upstream believes that has been fixed in newer version, the reports
almost stopped in recent version indeed so could be e.u.c matching
similar issues, but considering that one resolved. The reports are low
enough in older serie that it doesn't seem worth SRUing

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

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

Title:
  /usr/lib/gvfs/gvfsd-
  
mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1733577] Re: Buttons to go right, left, rotate are not well visible