[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

[Артем]

Correction. I run command of Alain Rouet (alain-rouet):
# sed -i "s/boot_params\['nouveau.runpm'\] = '0'/boot_params\['nouveau.runpm'\] 
= '-1'/" /usr/bin/prime-select

And output of the coomand cat /sys/kernel/debug/vgaswitcheroo/switch was 
different. Now it's:
0:IGD:+:Pwr::00:02.0
1:DIS: :DynOff::01:00.0

And my nvidia card realy turn of. Thank you Alain Rouet! You are cool!

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

-- 
Mailing list: https://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 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon

[Daniel van Vugt]

Maybe also shrink the icon so as to ensure it never touches the bar when
the bar is visible.

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

Title:
  The position of audio mute icon doesn't keep alignment to audio on
  icon

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using audio hotkeys to adjust the audio volume, I found the
  position of audio mute icon doesn't keep alignment to audio on icon.

  Please compare the attached screenshots, i.e. AudioMute.png and
  AudioOn.png, to see the difference.

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

-- 
Mailing list: https://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 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon

[Daniel van Vugt]

To avoid any odd-looking padding I think the solution would be to
enforce the OSD to stay as a square always, and just optionally paint
the bar over the top (possibly with a border to avoid conflicting with
some/future icons).

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

Title:
  The position of audio mute icon doesn't keep alignment to audio on
  icon

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using audio hotkeys to adjust the audio volume, I found the
  position of audio mute icon doesn't keep alignment to audio on icon.

  Please compare the attached screenshots, i.e. AudioMute.png and
  AudioOn.png, to see the difference.

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

-- 
Mailing list: https://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 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys

[Daniel van Vugt]

Looks like a fix is coming:
https://bugzilla.gnome.org/show_bug.cgi?id=782011

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=782011
   Importance: Unknown
   Status: Unknown

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

Title:
  Speaker volume overlay sometimes jitters left/right slightly when
  pressing volume keys

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I press the volume keys on my keyboard the shell displays an
  overlay showing the volume level. Normally this overlay is stationary,
  but sometimes when adjusting the volume, the overlay shifts slightly a
  pixel or two left or right.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Mon May 22 11:02:57 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Daniel van Vugt]

We know. There are 830 reports of this crash from 18.04 right now:
https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

And globally this is the 9th most common gnome-shell crash for 18.04 (or
6th if you look at just the past month).

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => High

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] ProcEnviron.txt

[hackel]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1759621/+attachment/5136526/+files/ProcEnviron.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/1759621

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] GsettingsChanges.txt

[hackel]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1759621/+attachment/5136524/+files/GsettingsChanges.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/1759621

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] Dependencies.txt

[hackel]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1759621/+attachment/5136523/+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/1759621

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] ProcCpuinfoMinimal.txt

[hackel]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1759621/+attachment/5136525/+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/1759621

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[hackel]

ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-12-09 (150 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-shell 3.28.1-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Tags:  bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-04-28 (11 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True


** Tags added: apport-collected

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[hackel]

Sadly this is still happening to me on 18.04 as well.  Every single time
I resume my machine from suspend.  And it's not just that gnome-shell
crashes, but I have to sit for a good 2-3 minutes while apport does its
thing, while the machine is completely frozen from a UI perspective.
This is such a huge usability issue!  I still suspect it is being caused
by some particular combination of gnome-shell extensions that are
installed.  I've tried (unsuccessfully) to pin down which one it is, but
it never seems to work, leading me to believe it must be a combination.

I've attached my journalctl output, captured from the moment I resumed
my machine.  Really hope we can get to the bottom of this!


** Attachment added: "journalctl-gnome-shell.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+attachment/5136522/+files/journalctl-gnome-shell.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/1759621

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1768653] Re: chromium 66 FTBFS on armhf

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
  ^
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
   ^ ~
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
  return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
 ~~ ^

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

-- 
Mailing list: https://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 1765363] Re: prime-select intel is not powering off the nvidia card

[Артем]

Confirm on Lenovo ideapad 520S-14IKB (Intel i5-7gen, Nvidia 940MX , Intel 
620HD).
On Ubuntu 17.10 (Nvidia driver 390.48 from ppa:graphics-drivers/ppa 
ppa:graphics-drivers/ppa) prime-select worked fine.
On Ubuntu 18.04 prime-select not turn off nvidia (driver from ppa and driver 
from repository).
Nouveau and bumblebee switches the graphics card well.

I noticed a different output of the command: cat
/sys/kernel/debug/vgaswitcheroo/switch

nouveau driver:
0:IGD:+:Pwr::00:02.0
1:DIS: :DynOff::01:00.0

nvidia 390.48, after prime-select intel:
0:IGD:+:Pwr::00:02.0
1:DIS: :Off::01:00.0

You can see the different status of the discrete card. When "DunOff" it
really disconnected from the power supply, and in case of "Off" it
continues to consume energy. If it matters.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

-- 
Mailing list: https://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 1173234] Re: Chromium's content doesn't respect z order, obscuring everything else

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chromium's content doesn't respect z order, obscuring everything else

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I have a fresh Ubuntu 13.04 install where I have installed nothing
  else besides Chromium. When I go to Chromium's Chrome Web Store, its
  content displays above everything else. In the attached image, note
  how gedit is above Chromium, yet Chromium's content area is obscuring
  gedit.

  This could be related to #1030060.

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

-- 
Mailing list: https://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 1308598] Re: In Trusty Cr34, popup windows are too small

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  In Trusty Cr34, popup windows are too small

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Popup windows seem to be scaled before considering the display
  scaling, which means an attempt to enlarge the display makes a pop-up
  windows that are smaller than they should be.

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

-- 
Mailing list: https://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 1241947] Re: tabs do not get focus and freezes unless minimize/restore.

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tabs do not get focus and freezes unless minimize/restore.

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  multiple tabs freeze almost everything except minimize and restore -
  which is a workaround

  probably a regression - think i have written about this before

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 19 09:04:42 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-07-20 (90 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

-- 
Mailing list: https://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 537268] Re: Panel icon for "no network" looks like wireless (even when the machine lacks wireless)

[Launchpad Bug Tracker]

[Expired for ubuntu-themes (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Panel icon for "no network" looks like wireless (even when the machine
  lacks wireless)

Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ubuntu-mono

  It's in the title : no network icon in panel shouldn't be a wireless
  one when I haven't any wireless networking card.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
  CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
  Date: Thu Mar 11 12:06:46 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  NonfreeKernelModules: nvidia
  Package: ubuntu-mono 0.0.7
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR:fr:en_GB:en
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: ubuntu-mono
  Uname: Linux 2.6.32-16-generic i686

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

-- 
Mailing list: https://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 716280] Re: gvfsd-metadata process pegs CPU while nautilus waits

[Launchpad Bug Tracker]

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gvfsd-metadata process pegs CPU while nautilus waits

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Binary package hint: nautilus

  I have been getting delays of 30-60 seconds when nautilus copies data
  on an NTFS filesystem in a 1.5 TB My Book external USB disk from
  Western Digital. I was able to see the process that has 100% of the
  CPU and causes spinners in my Nautilus Windows until it finishes. It
  is gvfsd-metadata, for which I have no man page.

  Today, I closed an earlier bug thinking that the problem had resolved
  itself as I had nominal functionality with nautilus then. I noticed
  that the problem returned and looked at running processes with top (1)
  to see what process appeared and what it was using when it ran.

  I don't know what gvfsd-metadata does or how important it is, but it
  seems to be the hog process. As soon as it exits I get the FM back. It
  appears whenever I move (drag) files from one dir to another. Another
  bug where I had long delays moving a 1.0 GB dir from the boot drive to
  this external drive, may be the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Wed Feb  9 23:09:42 2011
  ExecutablePath: /usr/bin/nautilus
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

-- 
Mailing list: https://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 1243061] Re: bangla joint letter problem

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bangla joint letter problem

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Bangla joint letters is not corrctly visible in chromium-browser. Bangla 
fonts are already installed. Firefox, google-chrome are working just fine. I am 
attaching a screenshot. Related word should be 
  "দুর্দান্ত বক্তব্য"

  chromium-browser encoding setting is UTF-8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 12:32:54 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''

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

-- 
Mailing list: https://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 1252544] Re: chromium-browser precise/amd64 crashes every page

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  chromium-browser precise/amd64 crashes every page

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  LOG：
  $ chromium-browser 
  [3768:3768:1119/104003:ERROR:profile_sync_service.cc(1202)] History Delete 
Directives datatype error was encountered: Delete directives not supported with 
encryption.

  View：
  Ref attachment image.

  this monring i updae system follow  system update.

  THKs

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3
  ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51
  Uname: Linux 3.2.0-56-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Nov 19 10:48:05 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

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

-- 
Mailing list: https://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 1308596] Re: in Trusty Cr34, popup context windows are in the wrong place

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  in Trusty Cr34, popup context windows are in the wrong place

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Popup windows are in the wrong place, slightly to the left and/or up
  of where they should be.

  Contents of those popups may be offset within them new frame, too.

  This happens, as far as I know, only if you have changed your default
  scaling to something   non-default.

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

-- 
Mailing list: https://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 1244884] Re: URL doesn't open from other application in chromium-browser

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  URL doesn't open from other application in chromium-browser

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

-- 
Mailing list: https://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 1754674] Re: nautilus crashes on unzip attempt

[Launchpad Bug Tracker]

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nautilus crashes on unzip attempt

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  1) Description:   Ubuntu Bionic Beaver (development branch)
 Release:   18.04

  2) nautilus:
Installed: 1:3.26.2-0ubuntu3.1
Candidate: 1:3.26.2-0ubuntu3.1
Version table:
*** 1:3.26.2-0ubuntu3.1 500
 
  3) After a double click on a zip file, I expect to see archive manager 
opening that file

  4) After a double click on a zip file, the nautilus window disappeared
  and no unzipped file is available

  Notes: 
  - I can unzip the file from CLI without issues. The problem is also present 
with right-click and selecting 'Open With Archive Manager'.
  - I have updated to Bionic from Ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar  9 15:24:24 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'166'
   b'org.gnome.nautilus.window-state' b'geometry' b"'898x651+26+23'"
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
  InstallationDate: Installed on 2017-10-22 (137 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1754674/+subscriptions

-- 
Mailing list: https://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 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[srinivas]

** Changed in: hplip
   Status: New => In Progress

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

Title:
  package python3 3.6.5-3 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hello, error came up while updating. Paketmanager has canceled the
  update completely. Not yet analyzed for errors with console ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 00:01:23 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago)

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

-- 
Mailing list: https://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 1770067] [NEW] Sync transmission 2.94-1 (main) from Debian unstable (main)

[Simon Quigley]

Public bug reported:

Please sync transmission 2.94-1 (main) from Debian unstable (main)

The only delta exists for Unity indicator support, and Ayatana support
has been merged into Debian, so this is no longer needed.

Changelog entries since current cosmic version 2.92-3ubuntu2:

transmission (2.94-1) unstable; urgency=medium

  * New upstream release
  * refresh patches
  * debian/patches/8c8386a7f3f482a9c917f51d28e0042e55f56b3e.patch,
debian/patches/bts885151_fix_ftcbfs_ac_run_ifelse.patch
- dropped, released upstream
  * debian/copyright
- refresh copyright with `decopy`, most importantly add OpenSSL
  exception
  * debian/control
- replace libcurl4-gnutls-dev with libcurl4-openssl-dev as b-d, to reduce
  the memory usage of transmission-daemon; patch provided by Andrey Gursky;
  Closes: #865624

 -- Sandro Tosi   Sun, 06 May 2018 19:34:20 -0400

transmission (2.93-2) unstable; urgency=medium

  * debian/control
- add qt5-qmake:native to b-d, to make it cross buildable; patch by Helmut
  Grohne; Closes: #896699

 -- Sandro Tosi   Thu, 26 Apr 2018 22:54:36 -0400

transmission (2.93-1) unstable; urgency=medium

  * New upstream release; Closes: #890325, #857511, #895869
  * debian/patches/*
- drop patches merged upstream
  * debian/control
- bump Standards-Version to 4.1.4 (no changes needed)
- update Homepage field to use HTTPS
- update Vcs-* fields to point to salsa
  * enable Ayatana AppIndicator support; Closes: #894410
  * set QT_SELECT=qt5 rather than build-depending on qt5-default; patch by
Helmut Grohne; Closes: #887849

 -- Sandro Tosi   Sat, 21 Apr 2018 19:19:08 -0400

** Affects: transmission (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: New

** Changed in: transmission (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: transmission (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync transmission 2.94-1 (main) from Debian unstable (main)

Status in transmission package in Ubuntu:
  New

Bug description:
  Please sync transmission 2.94-1 (main) from Debian unstable (main)

  The only delta exists for Unity indicator support, and Ayatana support
  has been merged into Debian, so this is no longer needed.

  Changelog entries since current cosmic version 2.92-3ubuntu2:

  transmission (2.94-1) unstable; urgency=medium

* New upstream release
* refresh patches
* debian/patches/8c8386a7f3f482a9c917f51d28e0042e55f56b3e.patch,
  debian/patches/bts885151_fix_ftcbfs_ac_run_ifelse.patch
  - dropped, released upstream
* debian/copyright
  - refresh copyright with `decopy`, most importantly add OpenSSL
exception
* debian/control
  - replace libcurl4-gnutls-dev with libcurl4-openssl-dev as b-d, to reduce
the memory usage of transmission-daemon; patch provided by Andrey 
Gursky;
Closes: #865624

   -- Sandro Tosi   Sun, 06 May 2018 19:34:20 -0400

  transmission (2.93-2) unstable; urgency=medium

* debian/control
  - add qt5-qmake:native to b-d, to make it cross buildable; patch by Helmut
Grohne; Closes: #896699

   -- Sandro Tosi   Thu, 26 Apr 2018 22:54:36 -0400

  transmission (2.93-1) unstable; urgency=medium

* New upstream release; Closes: #890325, #857511, #895869
* debian/patches/*
  - drop patches merged upstream
* debian/control
  - bump Standards-Version to 4.1.4 (no changes needed)
  - update Homepage field to use HTTPS
  - update Vcs-* fields to point to salsa
* enable Ayatana AppIndicator support; Closes: #894410
* set QT_SELECT=qt5 rather than build-depending on qt5-default; patch by
  Helmut Grohne; Closes: #887849

   -- Sandro Tosi   Sat, 21 Apr 2018 19:19:08 -0400

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

-- 
Mailing list: https://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 1770059] Re: Please merge 5.6-3 from Debian Sid

[Simon Quigley]

Attached is a debdiff applicable to 5.6-3, which is the current version
in Sid.

** Patch added: "1-5.6-3-to-5.6-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1770059/+attachment/5136511/+files/1-5.6-3-to-5.6-3ubuntu1.debdiff

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

Title:
  Please merge 5.6-3 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid contains a new upstream release of brltty. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  brltty (5.6-3) unstable; urgency=medium

* debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
  1.6 and later (Closes: Bug#893102).

   -- Samuel Thibault   Fri, 16 Mar 2018 15:20:39
  +0100

  brltty (5.6-2) unstable; urgency=medium

* debian/copyright: Fix licence terms.

   -- Samuel Thibault   Tue, 13 Feb 2018 11:35:38
  +0100

  brltty (5.6-1) experimental; urgency=medium

* New upstream release.
  - debian/patches/api_startup.patch: Upstreamed.
  - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
  - debian/patches/brldefs-install.patch: Upstreamed.
  - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
  - debian/brltty-udeb.udev.rules: Add new device IDs.
  - debian/control: Add liblouis-dev build-dep.
  - debian/rules: Make brltty install appstream data.
* control: Avoid the ALSA PCM package on non-Linux.

   -- Samuel Thibault   Sun, 11 Feb 2018 17:18:14
  +0100

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

-- 
Mailing list: https://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 1769895] Re: pulseaudio crashed with SIGABRT in pa_sink_input_process_rewind()

[Daniel van Vugt]

Although Ubuntu 14.04 is still supported it is due to reach end-of-life
next year.

https://wiki.ubuntu.com/Releases

I recommend upgrading to a newer version of Ubuntu, not least because
PulseAudio 4.0 is very much out of date now and the developers would be
unlikely to be able to help (the current PulseAudio version is 11.1).

** Information type changed from Private to Public

** Summary changed:

- pulseaudio crashed with SIGABRT in pa_sink_input_process_rewind()
+ pulseaudio crashed with SIGABRT in pa_sink_input_process_rewind() from 
pa_sink_process_rewind() from pa_sink_input_set_state_within_thread()

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_process_rewind() from
  pa_sink_process_rewind() from pa_sink_input_set_state_within_thread()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  trying to load module-ladspa-sink with master=uplink (virtual sink)
  when client was playing stream

  i.e

  1) deadbeef is playing (OK)
  2) pacmd load-module module-virtual-source source_name=vsource 
uplink_sink=uplink (OK)
  3) pacmd load-module module-ladspa-sink sink_name=veq master=uplink 
plugin=ladspa_dsp label=ladspa_dsp:eq (pulseaudio crashed)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tp24292 F pulseaudio
   /dev/snd/controlC1:  tp24292 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue May  8 16:34:39 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-07-27 (1016 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_process_rewind () from /usr/lib/libpulsecore-4.0.so
   pa_sink_process_rewind () from /usr/lib/libpulsecore-4.0.so
   pa_sink_input_set_state_within_thread () from /usr/lib/libpulsecore-4.0.so
   pa_sink_process_msg () from /usr/lib/libpulsecore-4.0.so
   ?? () from /usr/lib/libpulsecore-4.0.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_process_rewind()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-V EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-23T19:43:36.853439

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

-- 
Mailing list: https://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 1769922] Re: my left speaker has crackling sound. when i was hearing music in my laptop speaker the window locked. At that time the crackling sound started

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 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.


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

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

Title:
  my left speaker has crackling sound. when i was hearing music in my
  laptop speaker the window locked. At that  time the crackling sound
  started

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  please fix this soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-42-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   gokul  1656 F...m pulseaudio
   /dev/snd/controlC0:  gokul  1656 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue May  8 20:35:43 2018
  InstallationDate: Installed on 2018-04-11 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0210DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF15212SNW:pvrC10HUWG0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15212SNW
  dmi.product.version: C10HUWG0
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1770059] [NEW] Please merge 5.6-3 from Debian Sid

[Simon Quigley]

Public bug reported:

Debian Sid contains a new upstream release of brltty. Let's merge it.

Changelog entries since the last Ubuntu upload:

brltty (5.6-3) unstable; urgency=medium

  * debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
1.6 and later (Closes: Bug#893102).

 -- Samuel Thibault   Fri, 16 Mar 2018 15:20:39
+0100

brltty (5.6-2) unstable; urgency=medium

  * debian/copyright: Fix licence terms.

 -- Samuel Thibault   Tue, 13 Feb 2018 11:35:38
+0100

brltty (5.6-1) experimental; urgency=medium

  * New upstream release.
- debian/patches/api_startup.patch: Upstreamed.
- debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
- debian/patches/brldefs-install.patch: Upstreamed.
- debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
- debian/brltty-udeb.udev.rules: Add new device IDs.
- debian/control: Add liblouis-dev build-dep.
- debian/rules: Make brltty install appstream data.
  * control: Avoid the ALSA PCM package on non-Linux.

 -- Samuel Thibault   Sun, 11 Feb 2018 17:18:14
+0100

** Affects: brltty (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Description changed:

  Debian Sid contains a new upstream release of brltty. Let's merge it.
+ 
+ Changelog entries since the last Ubuntu upload:
+ 
+ brltty (5.6-3) unstable; urgency=medium
+ 
+   * debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
+ 1.6 and later (Closes: Bug#893102).
+ 
+  -- Samuel Thibault   Fri, 16 Mar 2018 15:20:39
+ +0100
+ 
+ brltty (5.6-2) unstable; urgency=medium
+ 
+   * debian/copyright: Fix licence terms.
+ 
+  -- Samuel Thibault   Tue, 13 Feb 2018 11:35:38
+ +0100
+ 
+ brltty (5.6-1) experimental; urgency=medium
+ 
+   * New upstream release.
+ - debian/patches/api_startup.patch: Upstreamed.
+ - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
+ - debian/patches/brldefs-install.patch: Upstreamed.
+ - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
+ - debian/brltty-udeb.udev.rules: Add new device IDs.
+ - debian/control: Add liblouis-dev build-dep.
+ - debian/rules: Make brltty install appstream data.
+   * control: Avoid the ALSA PCM package on non-Linux.
+ 
+  -- Samuel Thibault   Sun, 11 Feb 2018 17:18:14
+ +0100

** Changed in: brltty (Ubuntu)
   Status: New => In Progress

** Changed in: brltty (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: brltty (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Please merge 5.6-3 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid contains a new upstream release of brltty. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  brltty (5.6-3) unstable; urgency=medium

* debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
  1.6 and later (Closes: Bug#893102).

   -- Samuel Thibault   Fri, 16 Mar 2018 15:20:39
  +0100

  brltty (5.6-2) unstable; urgency=medium

* debian/copyright: Fix licence terms.

   -- Samuel Thibault   Tue, 13 Feb 2018 11:35:38
  +0100

  brltty (5.6-1) experimental; urgency=medium

* New upstream release.
  - debian/patches/api_startup.patch: Upstreamed.
  - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
  - debian/patches/brldefs-install.patch: Upstreamed.
  - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
  - debian/brltty-udeb.udev.rules: Add new device IDs.
  - debian/control: Add liblouis-dev build-dep.
  - debian/rules: Make brltty install appstream data.
* control: Avoid the ALSA PCM package on non-Linux.

   -- Samuel Thibault   Sun, 11 Feb 2018 17:18:14
  +0100

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

-- 
Mailing list: https://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 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[Daniel van Vugt]

Please try to only report one issue per bug report.

The first issue you report is in an area that has been bugging me for a
few years too (see bug 1607677). Please reword the bug title and
description to just be about that first issue.

The second issue you report is possibly bug 1759300.

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

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

** Changed in: gnome-control-center (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/1769845

Title:
  The Settings->Devices menu in gnome-shell Wayland doesn't provide
  enough configurations options, and there is no cfg file to work around
  it

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  First, the obvious: the mouse experience out of the box (at least on
  ubuntu 17.04) is bad. I thought this was because Wayland is slightly
  slower on animations + mouse movement but although this is happening
  for some reason (memory leak, whatever) it's mostly because the
  setting to set the mouse 'Acceleration Profile' to 'adaptive' is
  hidden in the gnome-tweak tool and set to default 'linear'. I highly
  suspect that this setting was on by default on X11 synaptics, because
  my mouse experience became equal after i turned it to adaptive when it
  was inferior before.

  This is probably the cause of many of the mouse complaints on the
  ubuntu upgrade.

  Another problem. Previously, on Xorg and synaptics i could use the
  right border area of my touchpad to simulate a middle mouse button
  click (that button doesn't exist on my keypad that has a structure
  like this:

  (imagine # is non-breaking spaces here because i sure can't make them work 
here)
  ---
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  ---
  |##|##|
  ---

  (i have a acer aspire 5738 if you want to see images on google)

  The bottom are the left and right mouse buttons, the right column was
  for scrolling (another bug: doesn't actually work on nautilus at the
  moment but works on Firefox).

  Previously taps on that scroll area could open firefox links, open
  tabs in nautilus etc, as per 3rd mouse button. Now that whole area
  only does scrolling  and i have to try the lottery of trying the
  'three finger tap' on the central are to simulate mouse click (this
  doesn't work 80% of the time, and the other 15% is right clicking,
  that's two fingers. Even if it works, 3 fingers probably meanwhile
  moved the cursor when i lifted or tapped). I'd *really really* like it
  if i could configure those areas somehow, either graphically or on a
  config file.

  Meanwhile i'm using ctrl+tap or ctrl+click but that requires two
  hands.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 09:26:49 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-25 (590 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago)

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

-- 
Mailing list: https://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 1769981] Re: Temporary screen freeze when coming back from screen standby

[Daniel van Vugt]

See also related bugs:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=unlock

** Tags added: unlock

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

Title:
  Temporary screen freeze when coming back from screen standby

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When waking up the PC screen from standby, quite often the screen freezes for 
10-20s.
  I can't move the mouse or type anything. After a while, it unfreezes.
  This is quite annoying because often the freeze is long enough to send the 
screen to standby again for absence of singal, so then I have to wake it up and 
wait again.

  This is not 100% reproducible but happens very frequently, both when
  the screen is locked and when it's not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 20:26:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-25 (72 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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/1769981/+subscriptions

-- 
Mailing list: https://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 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed

[Daniel van Vugt]

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

Thanks. Let's track this in bug 1723615 then.

If you find more crash files then please continue to report them using
'ubuntu-bug' and the robots will hopefully be able to analyse those and
tell you what each one is.

** This bug has been marked a duplicate of bug 1723615
   gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

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

Title:
  Logged out when unplugging external monitors with screen locked and
  lid closed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
  laptop. At work, I plug two displays into my laptop, one DisplayPort
  and one HDMI.

  If, while both displays are plugged in and the laptop lid is closed
  and the laptop's built-in display is therefore disabled, I:

  1. lock my screen;
  2. unplug both displays at about the same time;
  3. wait about ten seconds; and then
  4. open my laptop lid,

  I find that I have been logged out.

  If I immediately log back in to the built-in display, a couple seconds
  after I log in, the screen locks. If I then immediately log out and
  log back in again, the screen does _not_ lock.

  It seems that this weird lock-right-after-login behavior is related to
  the fact that I get logged out as described above. It seems that the
  shell remembers that it is supposed to be locked despite the crash /
  logout, such that when I log back in, it realizes that it's supposed
  to be locked and locks itself.

  Note that I am filing this bug as instructed in
  https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105:
  "BTW, we have fixed many gnome-shell bugs with these symptoms recently
  in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
  problems."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 14:26:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-09 (635 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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

-- 
Mailing list: https://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 1768993] Re: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot

[Daniel van Vugt]

No problem. This bug is now closed.

Anyone else who has problems can open a new bug.

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

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

Title:
  [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  Note, I have kde and gnome installed. Previously I was using lightdm,
  but since this was removed with the upgrade, I chose to use gdm. When
  booting, gdm did not start but instead I was at a shell login prompt.
  No errors were present in syslog or dmesg. dmesg output is attached.

  I could start the x server by executing `startx` from the CLI. I then
  issued a  `dpkg-reconfigure sddm` and selected sddm, then `dpkg-
  reconfigure gdm` and selected gdm. It gave me some sort of error about
  invoke-rc.d, so I then did `invoke-rc.d gdm3 start`, and it started
  gdm fine without rebooting. Then on next reboot as well, gdm started.
  So I'm not sure what there actually caused it to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  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: KDE
  Date: Thu May  3 15:46:12 2018
  InstallationDate: Installed on 2017-10-06 (209 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

[Daniel van Vugt]

Javier,

If your physical buttons (the ones that move independently of the
touchpad, and not just painted on) are not behaving correctly then
please log a bug with:

  ubuntu-bug libinput10

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions

-- 
Mailing list: https://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 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi

[Daniel van Vugt]

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

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

  ---

  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic
  was in process of installing programs (downloads were complete &
  actual install was in progress)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  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-shell/+bug/1422253/+subscriptions

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[KenWilson]

I upgraded from Ubuntu 17.10 to 18.04 and all was fine for a couple
weeks. I think an update yesterday (5/7) caused the problem. I have two
accounts on the system. I can initially log into either fine but
switching to the other causes the purple screen with cursor only. It
does not matter if I log out of the first account or switch user, either
way I have the problem. The password seems to be accepted fine. It seems
that the windows don't start or start correctly.

I'm using an HP dv7-2043cl Notebook

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[Jeremy Bicha]

Your bug report appears to be from Ubuntu 17.10. Please consider
upgrading to Ubuntu 18.04 LTS.

** 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/1769845

Title:
  The Settings->Devices menu in gnome-shell Wayland doesn't provide
  enough configurations options, and there is no cfg file to work around
  it

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  First, the obvious: the mouse experience out of the box (at least on
  ubuntu 17.04) is bad. I thought this was because Wayland is slightly
  slower on animations + mouse movement but although this is happening
  for some reason (memory leak, whatever) it's mostly because the
  setting to set the mouse 'Acceleration Profile' to 'adaptive' is
  hidden in the gnome-tweak tool and set to default 'linear'. I highly
  suspect that this setting was on by default on X11 synaptics, because
  my mouse experience became equal after i turned it to adaptive when it
  was inferior before.

  This is probably the cause of many of the mouse complaints on the
  ubuntu upgrade.

  Another problem. Previously, on Xorg and synaptics i could use the
  right border area of my touchpad to simulate a middle mouse button
  click (that button doesn't exist on my keypad that has a structure
  like this:

  (imagine # is non-breaking spaces here because i sure can't make them work 
here)
  ---
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  ---
  |##|##|
  ---

  (i have a acer aspire 5738 if you want to see images on google)

  The bottom are the left and right mouse buttons, the right column was
  for scrolling (another bug: doesn't actually work on nautilus at the
  moment but works on Firefox).

  Previously taps on that scroll area could open firefox links, open
  tabs in nautilus etc, as per 3rd mouse button. Now that whole area
  only does scrolling  and i have to try the lottery of trying the
  'three finger tap' on the central are to simulate mouse click (this
  doesn't work 80% of the time, and the other 15% is right clicking,
  that's two fingers. Even if it works, 3 fingers probably meanwhile
  moved the cursor when i lifted or tapped). I'd *really really* like it
  if i could configure those areas somehow, either graphically or on a
  config file.

  Meanwhile i'm using ctrl+tap or ctrl+click but that requires two
  hands.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 09:26:49 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-25 (590 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago)

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

-- 
Mailing list: https://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 1769372] Re: Prompt the user when the power button is pressed on a VM

[Daniel van Vugt]

OK, as is the pattern this week, the confusion here is the intersection
of two different bugs. Not one.

My gitlab merge request solves a different problem to this bug.

** Summary changed:

- Prompt the user when the power button is pressed
+ Prompt the user when the power button is pressed on a VM

** Changed in: gnome-control-center (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Prompt the user when the power button is pressed on a VM

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS as VirtualBox guest
  2. Login to session
  3. Press ACPI Power button/key

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Note 1: Problem exists with both VirtualBox 5.1.36 and 5.2.10 (guest
  additions and extpack are installed and have corresponding versions).
  Ubuntu 16.04.4 LTS amd64 is a host.

  Note 2: Problem exists if use QEMU-KVM (sudo kvm -m 1536 -drive
  file=/dev/sdc,format=raw) too. Sending system_powerdown from
   shutdowns system without prompt.

  Workaround/fix (1)

  gsettings set org.gnome.settings-daemon.plugins.power power-button-
  action interactive

  Workaround/fix (2)

  Settings >
  Power >
  Suspend & Power Button >
  When the Power Button is pressed = Power Off (actually does prompt the user)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  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: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-settings-daemon
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

[Daniel van Vugt]

There's probably no way GDM could cause this directly. But indirectly if
you are logging into a Wayland session in one case and Xorg in the
other, then that might be the main factor here.

Please try logging into both Xorg and Wayland sessions to see if one
works better.

Also, for Nvidia there used to be settings to control tearing in the
nvidia control panel. So you shouldn't need to "To get rid of tearing I
added nvidia-drm.modeset=1"...?

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

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

Status in gdm3 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

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

-- 
Mailing list: https://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 1770052] [NEW] display crashes

[shyju]

Public bug reported:

i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor with 
1GB RAM,500GB HDD,
UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display crashes

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
Uname: Linux 4.4.0-22-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May  9 07:14:59 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:03d6]
InstallationDate: Installed on 2018-05-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
Lsusb:
 Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=efc9f66a-4d8f-412d-b243-becd83011893 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed May  9 12:23:14 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImExPS/2 Logitech Explorer Mouse MOUSE, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output   VGA-1
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: nouveau

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


** Tags: apport-bug i386 trusty 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/1770052

Title:
  display crashes

Status in xorg package in Ubuntu:
  New

Bug description:
  i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor 
with 1GB RAM,500GB HDD,
  UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display 
crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  9 07:14:59 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:03d6]
  InstallationDate: Installed on 2018-05-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 002: ID 

[Desktop-packages] [Bug 1770048] 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

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1767116, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1767116
   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.48-0ubuntu3

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

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.48-0ubuntu3

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

Bug description:
  I was changing from 390 to 340 when it happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May  8 20:16:03 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  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.48-0ubuntu3
  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/1770048/+subscriptions

-- 
Mailing list: https://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 1770048] [NEW] 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-com

[Kilz]

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

Public bug reported:

I was changing from 390 to 340 when it happened.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Tue May  8 20:16:03 2018
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.106-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
  trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is 
also in package nvidia-kernel-common-390 390.48-0ubuntu3
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
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.48-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

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.48-0ubuntu3

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

Bug description:
  I was changing from 390 to 340 when it happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May  8 20:16:03 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  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.48-0ubuntu3
  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/1770048/+subscriptions

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

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

[Kyle Weber]

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

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1767116] 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

[Peter Valdemar Mørch]

This occurs in 18.04 because versions 340 and 390 are attempted to be
installed at the same time and they apparently both want to modify
/lib/udev/rules.d/71-nvidia.rules

apt-get install -f was not able to fix the situation.

Workaround: remove all packages mentioning nvidia 340 and 390 (beware
you may want to check what this does):

# show the packages we're about to remove
dpkg-query -W  | egrep 'nvidia.*3[49]0' | perl -naE 'say $F[0]'
# remove them
dpkg-query -W  | egrep 'nvidia.*3[49]0' | perl -naE 'say $F[0]' | sudo xargs 
dpkg -P

Now install *ONLY* the version 340 one. And then both apt and
subsequently the nvidia driver worked for me.

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

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.48-0ubuntu3

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

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 16:22:30 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2016-05-19 (706 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  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.48-0ubuntu3
  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/1767116/+subscriptions

-- 
Mailing list: https://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 1757180] Re: nvidia-prime can't switch off the discrete GPU

[Tom]

Confirm the issue seems everybody on 18.04 and Nvidia GeForce is
suffering...

Duplicates ? 
 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
   https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363

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

Title:
  nvidia-prime can't switch off the discrete GPU

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a
  change in the nvidia packaging, and a change of behaviour in logind,
  broke this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions

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

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

[Symin]

In my case it was... complicated.

Turns out that after upgrade to 18.04 wayland was on by default for me.
prime-select intel worked fine
prime-select nvidia gdm would not show

Changing wayland to xorg in gdm (with intel) would not work - login
screen just kept reapearing. Forcing xorg through /etc/gdm3/custom.conf
only made it worse.

In the end I have decided to try and unplug my DP cable from the
mainboard and plug it into the gfx card. This has worked. After the
reboot GDM has showed up and only xorg was available (I have switched to
xorg before I swapped the cable, though).

No reverse prime for me :( Hopefuly plymouth works with nvidia these
days or this gets fixed soon.

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

[Tom]

Confirming on Dell XPS 15 9560; Nvidia is not power-down when prime
selecting Intel: I am now on 13W with TLP enabled... 17.10 would give me
about half of that.

In addition, I cant suspend properly. Half of the times it will freeze
an I need to force power down...

Together with https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1752053 ir seems that 18.04 indeed broke all Nvidia
dual laptops.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

-- 
Mailing list: https://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 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[i30817]

No, that 'area' setting doesn't work on my touchpad for some reason. A
alternative i found at https://askubuntu.com/questions/881939/libinput-
how-to-map-different-tappings-to-buttons-tappingbuttonmap-has-no-effe/

does something useful that i'd like to be a setting in the future,
exchange the 'double finger tap' by the 'triple finger tap' that is
double finger tap is mouse 3.

Unfortunately i also can't make it work. I suspect my driver is always
being set to synaptics.

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

Title:
  The Settings->Devices menu in gnome-shell Wayland doesn't provide
  enough configurations options, and there is no cfg file to work around
  it

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  First, the obvious: the mouse experience out of the box (at least on
  ubuntu 17.04) is bad. I thought this was because Wayland is slightly
  slower on animations + mouse movement but although this is happening
  for some reason (memory leak, whatever) it's mostly because the
  setting to set the mouse 'Acceleration Profile' to 'adaptive' is
  hidden in the gnome-tweak tool and set to default 'linear'. I highly
  suspect that this setting was on by default on X11 synaptics, because
  my mouse experience became equal after i turned it to adaptive when it
  was inferior before.

  This is probably the cause of many of the mouse complaints on the
  ubuntu upgrade.

  Another problem. Previously, on Xorg and synaptics i could use the
  right border area of my touchpad to simulate a middle mouse button
  click (that button doesn't exist on my keypad that has a structure
  like this:

  (imagine # is non-breaking spaces here because i sure can't make them work 
here)
  ---
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  |###|#|
  ---
  |##|##|
  ---

  (i have a acer aspire 5738 if you want to see images on google)

  The bottom are the left and right mouse buttons, the right column was
  for scrolling (another bug: doesn't actually work on nautilus at the
  moment but works on Firefox).

  Previously taps on that scroll area could open firefox links, open
  tabs in nautilus etc, as per 3rd mouse button. Now that whole area
  only does scrolling  and i have to try the lottery of trying the
  'three finger tap' on the central are to simulate mouse click (this
  doesn't work 80% of the time, and the other 15% is right clicking,
  that's two fingers. Even if it works, 3 fingers probably meanwhile
  moved the cursor when i lifted or tapped). I'd *really really* like it
  if i could configure those areas somehow, either graphically or on a
  config file.

  Meanwhile i'm using ctrl+tap or ctrl+click but that requires two
  hands.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 09:26:49 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-25 (590 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago)

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

-- 
Mailing list: https://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 1768258] Re: Intermittend black screen - after login on bootup

[Launchpad Bug Tracker]

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

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

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

Title:
  Intermittend black screen - after login on bootup

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm experiencing intermittent dekstop environment loading issues with gnome 
3.28. After logging in on the Session greeter, it loads for a few seconds and 
no desktop appears just a grey/black backround, nothings gonna happen.
  First I just done Alt-Print-REISUB to recover, but I found out switching 
console Ctrl-Alt-F3 and back to Ctrl-Alt-F1 brings me back to the login screen 
and I can do another login which resolved the issue for me everytime it 
happened.
  I think it is going to hapen every 10-20st boot.
  I'll attach a few logs.

  Additionally I've got to tell I manually installed NVIDIA 390.42 after
  upgrading to 18.04 beta.

  Best regards

  Kitsab

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  1 15:55:32 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-02-14 (1172 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  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/1768258/+subscriptions

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

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

[Tom]

This all might be related to https://bugs.launchpad.net/ubuntu/+source
/nvidia-prime/+bug/1765363  I think...

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1401017] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from glamor_pixmap_ensure_fb()

[Christopher M. Penalver]

Closing as I don't have that hardware anymore, I don't use eog, and will
not be using pre-18.04 OS.

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from glamor_pixmap_ensure_fb()

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The OS kicks you to the login screen executing the following in a terminal 
with the attached file:
  eog family_room.svg > eog.txt

  Also happens when double clicking the file. However, apport wasn't
  generating a crash file unless I executed the above command.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Dec 10 01:45:38 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] [1002:9830] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3802]
  InstallationDate: Installed on 2014-06-21 (171 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20319
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=a2db89ed-d599-4138-8838-0b950b6c3fbb ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? () from /usr/lib/x86_64-linux-gnu/libglamor.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglamor.so.0
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CCN29WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S415 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S415 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CCN29WW(V2.03):bd11/14/2013:svnLENOVO:pn20319:pvrLenovoIdeaPadS415Touch:rvnLENOVO:rnLenovoIdeaPadS415Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoIdeaPadS415Touch:
  dmi.product.name: 20319
  dmi.product.version: Lenovo IdeaPad S415 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Dec 10 01:45:49 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.5
  xserver.video_driver: radeon

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

-- 
Mailing list: https://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 1702351] Re: [snap] "User installation could not be completed"

[modolo]

After rm...

snap run libreoffice
Traceback (most recent call last):
  File "/snap/libreoffice/59/javasettings.py", line 41, in 
java_output).group("version")
AttributeError: 'NoneType' object has no attribute 'group'
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"

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

Title:
  [snap] "User installation could not be completed"

Status in snapd:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

-- 
Mailing list: https://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 1728467] Re: All files on ntfs partitions are marked executable

[Doug McMahon]

Not sure what the heck you all are recently taking about.

Most linux users of a ntfs partition are using to store files for use on any Os 
or store files without any permission nonsense.
Those that actually place .exe files & want to then execute them from an Ubuntu 
session would likely be using something like wine.
In that case the .exe does not need to be "executable" to be run.

The prior settings for ntfs defaults was best for the vast majority of
users, period.

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

Title:
  All files on ntfs partitions are marked executable

Status in ntfs-3g package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  This did not happen in 14.04 but somewhere since then udisks2 sets any & all 
files on ntfs partitions as executable.
  Additionally if file is copied over to user's ext4 partion the bit remains 
set.
  Can't see why this would be intentional??

  In 14.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", 
"fmask=0177", NULL };

  In 16.04, 17.04, 17.10,18.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Oct 29 21:20:19 2017
  InstallationDate: Installed on 2017-09-16 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728467/+subscriptions

-- 
Mailing list: https://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 1702351] Re: [snap] "User installation could not be completed"

[Olivier Tilloy]

Okay, so it looks like the traceback might have been a one-off.

If you remove the settings file and run libreoffice again, do you get
the traceback again?

rm 
$HOME/snap/libreoffice/current/.config/libreoffice/4/user/config/javasettings_Linux_X86_64.xml
snap run libreoffice

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

Title:
  [snap] "User installation could not be completed"

Status in snapd:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

-- 
Mailing list: https://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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10

[Duncan Richard Murphy]

This problem has just arisen, with my Canon Lide 200, on a recently
installed Ubuntu 18.04. The scanner worked fine with Ubuntu 16.04 and
still works under Winblows.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+subscriptions

-- 
Mailing list: https://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 1769757] Re: Can't edit Microsoft .docx/ .doc within Libreoffice

[Olivier Tilloy]

Can you observe the issue yourself with a similar setup?

Where are the files being open located? Is it on a USB stick? If so and
if the stick is mounted read-only, that explains why files can't be
edited. Note that in that case libreoffice should display a ribbon that
informs the user that the file has been opened in read-only mode, and
that it cannot be edited.

What happens if the file is first copied onto the home folder of the
guest session, and then opened?

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

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

Title:
  Can't edit Microsoft .docx/ .doc within Libreoffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu 18.04 Bionic Beaver 
  (Description: Ubuntu 18.04 LTS Release:   18.04)
  dm: LightDM Destop Manager
  Sessiontype: Guest-Session

  Libreoffice-Version (About):
  Version: 6.0.3.2
  Build-ID: 1:6.0.3-0ubuntu1
  CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
  Gebietsschema: de-DE (de_DE.UTF-8); Calc: group

  libreoffice:
Installiert:   (keine)
Installationskandidat: 1:6.0.3-0ubuntu1
Versionstabelle:
   1:6.0.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  We are using the guest-session of ldm for an restricted session for
  postpaid-modus.

  After recent OS upgrade to 18.04, some guests experienced issues, that either 
Nautilus mounts their USB-Stick in read-only mode, as also and that is for what 
this bug report is for,
  That if they open Microsoft documents (type of .docx / .doc), those documents 
are opened correctly
  but Libreoffice (swriter) reject any input without any error message.

  Those documents were NOT secured by any password, as guests are
  claiming.

  Weirder, if I copy the content of the document into, f.e. abiword, the
  program still reject any change or input.

  This behavior does not apply when the user creat a blank new document,
  but if he try to open a microsoft documen, he is again not able to
  edit the content.

  This is a major issue for us, as we have already update all our three
  PC to 18.04, so we have no alternative. And the customers are
  unsatisfied...

  Hope you can help out here.

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

-- 
Mailing list: https://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 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi

[Treviño]

I've a proposed fix at
https://gitlab.gnome.org/3v1n0/mutter/commit/993a40c9a4e161e40faa0467f98eadd1ac50dd22

I'm discussing with upstream about it.

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

  ---

  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic
  was in process of installing programs (downloads were complete &
  actual install was in progress)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  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-shell/+bug/1422253/+subscriptions

-- 
Mailing list: https://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 934291] Re: Deleting or stopping print jobs does not work

[Launchpad Bug Tracker]

This bug was fixed in the package cups-pk-helper - 0.2.6-1ubuntu2

---
cups-pk-helper (0.2.6-1ubuntu2) cosmic; urgency=medium

  [ Shem Pasamba ]
  * 
debian/patches/Use_cups-pk-helper_in_org.opensuse.CupsPkHelper.Mechanism.conf.patch
- Use cups-pk-helper in org.opensuse.CupsPkHelper.Mechanis.conf
  instead of root
  * debian/patches/run_as_cups-pk-helper.patch
- Make the cups-pk-helper run as cups-pk-helper passing cups-pk-helper as
  user too. (LP: #934291)
  * debian/cups-pk-helper.postinst:
- Add cups-pk-helper group and user.
  * debian/cups-pk-helper.postrm:
- Remove cups-pk-helper user and group.
  * Added --with-daemon-user

  [ Till Kamppeter ]
  * Use cups-pk-helper as system user.

 -- Till Kamppeter   Fri,  4 May 2018 17:37:58
+0200

** Changed in: cups-pk-helper (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups-pk-helper package in Ubuntu:
  Fix Released
Status in cups-pk-helper source package in Bionic:
  New

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Treviño]

It could be that fixing this would also fixes lp:1703300
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

[Treviño]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Treviño]

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

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1728467] Re: All files on ntfs partitions are marked executable

[Jean-Pierre]

> why it defaults to execute on when the in kernel driver does not.

Well, most users do not define the mapping of their user ids to Windows
ids, so the permissions cannot be stored to the device, and the
permissions have to be the same for all files and all users. If the
default was no-execute, they could not execute any file, even by
tweaking the umask. Ntfs-3g only uses metadata defined for Windows, and
does not store any extra metadata which would be useful for Posix usage.

Users who need standard Linux per file and per user ownership and
permissions may define their user mapping.

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

Title:
  All files on ntfs partitions are marked executable

Status in ntfs-3g package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  This did not happen in 14.04 but somewhere since then udisks2 sets any & all 
files on ntfs partitions as executable.
  Additionally if file is copied over to user's ext4 partion the bit remains 
set.
  Can't see why this would be intentional??

  In 14.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", 
"fmask=0177", NULL };

  In 16.04, 17.04, 17.10,18.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Oct 29 21:20:19 2017
  InstallationDate: Installed on 2017-09-16 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728467/+subscriptions

-- 
Mailing list: https://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 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

[Apport retracing service]

** 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/1723615

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/130
  https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339

  ---

  This happened while I was away from the computer. By the timing it
  should have been well after the time it should have gone *into*
  displaysleep, and was also about 45min before I returned, so certainly
  wasn't the wake-up process either.

  What I observed when I did return: My 4K monitor didn't wake up
  (that's a known problem with this monitor, Dell P2715Q), the second
  monitor (Dell U2711) did wake up, showing the login screen.

  So although I've considered my Dell 4K problem a problem with waking
  up, I wonder if it might be actually a problem with it apparently
  going away completely after a longer displaysleep (it's usually fine
  if I just do a short sleep of a minute or two).

  Another possibility is the cat stepped on the keyboard and thus
  triggered an attempted display-wake. But that would actually be out of
  character (for the cat).

  Either way is a bug because the session should survive monitor
  shenanigans... :-)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 14 15:39:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-30 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fae20ab44a0 : 
mov0x8(%rdi),%eax
   PC (0x7fae20ab44a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1769991] [NEW] [16.04] Unable to import OpenVPN configuration into Network Manager

[Thomas Ward]

Public bug reported:

In 16.04, it is currently not possible to import OpenVPN configurations.
Specifically, imports fail with the error of:

The file 'filename.ovpn' could not be read or does not contain
recognized VPN connection information.

Error: Key file contains line 'client' which is not a key-value pair,
group, or comment.

--

An example configuration that fails to import is as follows (with some
critical components excluded, like a proper remote address, or a proper
x509 name); this is a config that otherwise works with a Sophos XG
Firewall-based SSL VPN system

client
dev tun
persist-tun
persist-key
proto tcp
verify-x509-name ""
route remote_host 255.255.255.255 net_gateway
resolv-retry infinite
remote 1.2.3.4 8443 tcp
ca ca.crt
cert client.crt
key client.key
auth-user-pass
cipher AES-256-CBC
auth SHA512
comp-lzo no
route-delay 4
verb 3
reneg-sec 0

--

This same exact configuration works with a direct call of `openvpn
./filename.ovpn`.

Why Network Manager is unable to parse or import the OpenVPN
configuration is beyond my ability to comprehend.

Note that the same configuration made by hand in the new VPN window
works fine, but the import function fails.  (Which is a pretty severe
bug)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May  8 14:59:54 2018
InstallationDate: Installed on 2016-12-20 (503 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Description changed:

  In 16.04, it is currently not possible to import OpenVPN configurations.
  Specifically, imports fail with the error of:
  
  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.
  
  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.
  
  --
  
- An example configuration that fails to import is as follows:
+ An example configuration that fails to import is as follows (with some
+ critical components excluded, like a proper remote address, or a proper
+ x509 name):
  
  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
- remote ipaddr 8443 tcp
+ remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0
  
  --
  
  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.
  
  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.
  
  Note that the same configuration made by hand in the new VPN window
  works fine, but the import function fails.  (Which is a pretty severe
  bug)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 14:59:54 2018
  InstallationDate: Installed on 2016-12-20 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  In 16.04, it is currently not possible to import OpenVPN configurations.
  Specifically, imports fail with the error of:
  
  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.
  
  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.
  
  --
  
  An example configuration that fails to import is as follows (with some
  critical components excluded, like a proper remote address, or a proper
- x509 name):
+ x509 name); this is a config that otherwise works with a Sophos XG
+ Firewall-based SSL VPN system
  
  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
  remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0
  
  --
  
  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.
  
  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.
  
  

[Desktop-packages] [Bug 1769982] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1723615, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136315/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136317/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136322/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136323/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136324/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136325/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1769982/+attachment/5136326/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1723615
   gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Submitting crash as instructed in bug 1769720.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 14:34:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-05-19 (354 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f399f4fa210 : 
mov0x8(%rdi),%eax
   PC (0x7f399f4fa210) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (11 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo 
vboxusers wireshark

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

-- 
Mailing list: https://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 1765363] Re: prime-select intel is not powering off the nvidia card

[Noam Mor]

Can confirm on a Dell XPS 9550 - power draw went from ~7W to ~20W after
updating to 18.04, even with prime-select intel.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

-- 
Mailing list: https://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 1728467] Re: All files on ntfs partitions are marked executable

[Phillip Susi]

Udisks specifying a default mask was removed intentionally, leaving the
default to the NTFS driver.  ntfs-3g defaults to all executable.  People
often do have executable files on their NTFS drives and want to be able
to execute them.  This has gone back and forth a few times over the
years and without the execute bit, less experienced users are unable to
make things work and don't understand why.  With the bit, more
experienced users are... well, let's just say offended.  I think we're
better off where we are, but maybe the ntfs-3g devs can chime in on why
it defaults to execute on when the in kernel driver does not.  My guess
is that it is intentional but we'll see.


** Changed in: udisks2 (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: ntfs-3g (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  All files on ntfs partitions are marked executable

Status in ntfs-3g package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  This did not happen in 14.04 but somewhere since then udisks2 sets any & all 
files on ntfs partitions as executable.
  Additionally if file is copied over to user's ext4 partion the bit remains 
set.
  Can't see why this would be intentional??

  In 14.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", 
"fmask=0177", NULL };

  In 16.04, 17.04, 17.10,18.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Oct 29 21:20:19 2017
  InstallationDate: Installed on 2017-09-16 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728467/+subscriptions

-- 
Mailing list: https://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 1769981] [NEW] Temporary screen freeze when coming back from screen standby

[Alberto Donato]

Public bug reported:

When waking up the PC screen from standby, quite often the screen freezes for 
10-20s.
I can't move the mouse or type anything. After a while, it unfreezes.
This is quite annoying because often the freeze is long enough to send the 
screen to standby again for absence of singal, so then I have to wake it up and 
wait again.

This is not 100% reproducible but happens very frequently, both when the
screen is locked and when it's not.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May  8 20:26:27 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-02-25 (72 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic 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/1769981

Title:
  Temporary screen freeze when coming back from screen standby

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When waking up the PC screen from standby, quite often the screen freezes for 
10-20s.
  I can't move the mouse or type anything. After a while, it unfreezes.
  This is quite annoying because often the freeze is long enough to send the 
screen to standby again for absence of singal, so then I have to wake it up and 
wait again.

  This is not 100% reproducible but happens very frequently, both when
  the screen is locked and when it's not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 20:26:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-25 (72 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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/1769981/+subscriptions

-- 
Mailing list: https://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 1769977] [NEW] jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

[Esteban]

Public bug reported:

jackd2 package don't install in Ubuntu 18.04 LTS.

Broken dependencies, libreadline6 can't be installed anymore.

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

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

Title:
  jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

Status in jackd2 package in Ubuntu:
  New

Bug description:
  jackd2 package don't install in Ubuntu 18.04 LTS.

  Broken dependencies, libreadline6 can't be installed anymore.

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

-- 
Mailing list: https://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 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream

[Raul Dias]

I have a lot of computers in my office that needs this drive to work.
Neither Nouveau or VESA works with them.
If this decision persists I will have to move to another distribution (which I 
hope to avoid).

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

Title:
  Remove from the archive: this legacy driver is unmaintained upstream

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Fix Released

Bug description:
  This driver branch is now dead upstream, so it should be removed from
  bionic.

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

-- 
Mailing list: https://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 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Michael Bushey]

Sure, here it is.

** Attachment added: "apt-clone_system_state.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+attachment/5136348/+files/apt-clone_system_state.tar.gz

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Incomplete

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
Mailing list: https://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 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed

[Jonathan Kamens]

Note that there are crashes around the same time in /usr/lib/hidpi-
daemon/hidpi-daemon and /usr/lib/hidpi-daemon/hidpi-notification, which
are provided by System76, but looking at the dumps in /var/crash for
them, it looks like they are crashing _as a result of_ the gnome-shell
crash, as opposed to because of it.

The hidpi-daemon crash says this:

 GLib.GError: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient
disconnected from message bus without replying (4)

which I _think_ means it was trying to message gnome-shell and failed
because the shell had crashed. And the hidpi-notification crash says
this:

Title: hidpi-notification crashed with GLib.GError in get(): g-dbus-
error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name com.system76.hidpi was not provided by any .service files (2)

which I think means that it crashed because hidpi-daemon crashed.

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

Title:
  Logged out when unplugging external monitors with screen locked and
  lid closed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
  laptop. At work, I plug two displays into my laptop, one DisplayPort
  and one HDMI.

  If, while both displays are plugged in and the laptop lid is closed
  and the laptop's built-in display is therefore disabled, I:

  1. lock my screen;
  2. unplug both displays at about the same time;
  3. wait about ten seconds; and then
  4. open my laptop lid,

  I find that I have been logged out.

  If I immediately log back in to the built-in display, a couple seconds
  after I log in, the screen locks. If I then immediately log out and
  log back in again, the screen does _not_ lock.

  It seems that this weird lock-right-after-login behavior is related to
  the fact that I get logged out as described above. It seems that the
  shell remembers that it is supposed to be locked despite the crash /
  logout, such that when I log back in, it realizes that it's supposed
  to be locked and locks itself.

  Note that I am filing this bug as instructed in
  https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105:
  "BTW, we have fixed many gnome-shell bugs with these symptoms recently
  in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
  problems."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 14:26:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-09 (635 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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

-- 
Mailing list: https://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 1769969] [NEW] GDM3 does not start if SDDM is installed (18.04)

[Raul Dias]

Public bug reported:

After upgrading my office machines to 18.04, some machines did not start
the GDM3.

After some testing the problem was that the ones that it did not work,
had SDDM installed too (KDE environment in those machines).

The upgrade were from 17.10 and 16.04.

Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none
worked.

On gdm3 side: systemctl is-active gdm3 reports static (which might be
the problem).

After removing sddm and rebooting, everything worked as expected.

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

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

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

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

Title:
  GDM3 does not start if SDDM is installed (18.04)

Status in gdm3 package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  After upgrading my office machines to 18.04, some machines did not
  start the GDM3.

  After some testing the problem was that the ones that it did not work,
  had SDDM installed too (KDE environment in those machines).

  The upgrade were from 17.10 and 16.04.

  Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none
  worked.

  On gdm3 side: systemctl is-active gdm3 reports static (which might be
  the problem).

  After removing sddm and rebooting, everything worked as expected.

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

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Bug Watch Updater]

** Changed in: gdm
   Status: Unknown => Confirmed

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

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

Do you happen to have and could you provide us with the following file
from the system?

/var/log/dist-upgrade/apt-clone_system_state.tar.gz

Thanks in advance.

** Changed in: desktop-file-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Incomplete

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
Mailing list: https://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 1769883] Re: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  update is stoped

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CupsErrorLog:
   
  Date: Tue May  8 21:06:50 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-12-08 (1246 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build i386 LIVE Binary 
20140428-16:49
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: Acer Aspire R3600
  Papersize: a4
  PpdFiles: Canon-MG3500-series: Canon MG3500 series - CUPS+Gutenprint v5.2.11
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=a6bf5d92-719b-4fa2-89f5-962918d51005 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A2
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MCP7A
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A2:bd04/30/2009:svnAcer:pnAspireR3600:pvr:rvnAcer:rnMCP7A:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire R3600
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed

[Jonathan Kamens]

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769982

** 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/1769720

Title:
  Logged out when unplugging external monitors with screen locked and
  lid closed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
  laptop. At work, I plug two displays into my laptop, one DisplayPort
  and one HDMI.

  If, while both displays are plugged in and the laptop lid is closed
  and the laptop's built-in display is therefore disabled, I:

  1. lock my screen;
  2. unplug both displays at about the same time;
  3. wait about ten seconds; and then
  4. open my laptop lid,

  I find that I have been logged out.

  If I immediately log back in to the built-in display, a couple seconds
  after I log in, the screen locks. If I then immediately log out and
  log back in again, the screen does _not_ lock.

  It seems that this weird lock-right-after-login behavior is related to
  the fact that I get logged out as described above. It seems that the
  shell remembers that it is supposed to be locked despite the crash /
  logout, such that when I log back in, it realizes that it's supposed
  to be locked and locks itself.

  Note that I am filing this bug as instructed in
  https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105:
  "BTW, we have fixed many gnome-shell bugs with these symptoms recently
  in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
  problems."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 14:26:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-09 (635 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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

-- 
Mailing list: https://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 1663050] Re: Intel 7265 wireless device disconnect: link is not ready

[Ubuntu Kernel Bot]

** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  Intel 7265 wireless device disconnect: link is not ready

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The wifi device disconnect sometime randomly or sometime when switching 
hotspot with the following dmesg output:
  [ 1039.212949] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.213503] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.221549] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 1039.221561] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 1039.221566] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 1039.221569] pcieport :00:1c.0:[ 0] Receiver Error (First)
  [ 1039.239086] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

  The device at pcieport :00:1c.0 seems to be the Intel 7265 wireless:
  $ lspci -tv
  -[:00]-+-00.0  Intel Corporation Device 5904
 +-02.0  Intel Corporation Device 5916
 +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
 +-14.2  Intel Corporation Sunrise Point-LP Thermal subsystem
 +-16.0  Intel Corporation Sunrise Point-LP CSME HECI #1
 +-17.0  Intel Corporation Sunrise Point-LP SATA Controller [AHCI 
mode]
 +-1c.0-[01]00.0  Intel Corporation Wireless 7265
 +-1d.0-[02]00.0  Samsung Electronics Co Ltd NVMe SSD Controller
 +-1f.0  Intel Corporation Device 9d58
 +-1f.2  Intel Corporation Sunrise Point-LP PMC
 +-1f.3  Intel Corporation Device 9d71
 \-1f.4  Intel Corporation Sunrise Point-LP SMBus

  To allow the device to connect again I use the following:
  $ sudo systemctl restart network-manager.service

  That said, the pcieport :00:1c.0 dmesg outputs sometimes appears
  without affecting the wifi connection...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ inxi -Abd
  System:Host: 710s Kernel: 4.4.0-62-generic x86_64 (64 bit) Desktop: Unity 
7.4.0  Distro: Ubuntu 16.04 xenial
  Machine:   System: LENOVO (portable) product: 80VQ v: Lenovo ideapad 
710S-13IKB
 Mobo: LENOVO model: Lenovo ideapad 710S-13IKB v: SDK0J40709 WIN
 Bios: LENOVO v: 3HCN12S2 date: 10/07/2016
  CPU:   Dual core Intel Core i7-7500U (-HT-MCP-) speed/max: 600/2701 MHz
  Graphics:  Card: Intel Device 5916
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1920x1080@60.02hz
 GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 
11.2.0
  Audio: Card Intel Device 9d71 driver: snd_hda_intel Sound: ALSA v: 
k4.4.0-62-generic
  Network:   Card: Intel Wireless 7265 driver: iwlwifi
  Drives:HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
 Optical: No optical drives detected.
  Info:  Processes: 244 Uptime: 34 min Memory: 2000.8/7876.3MB Client: 
Shell (bash) inxi: 2.2.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1663050/+subscriptions

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Ads20000]

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

** Changed in: gdm
   Importance: Undecided => Unknown

** Changed in: gdm
   Status: New => Unknown

** Changed in: gdm
 Remote watch: None => GNOME Bug Tracker #795940

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Unknown
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1767817] Re: Full text search does not work

[Wolf Walter]

I have the same problem. Does also not work with the nautilus version
from flathub.

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

-- 
Mailing list: https://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 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
Mailing list: https://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 1769954] [NEW] package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Michael Bushey]

Public bug reported:

run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: desktop-file-utils 0.23-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Tue May  8 16:59:12 2018
Ec2AMI: ami-70873908
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2a
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: dependency problems - leaving triggers unprocessed
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

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


** Tags: amd64 apport-package bionic ec2-images

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
Mailing list: https://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 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

[Iain Lane]

I'm thinking that Multi-Arch: foreign on the transitional package libp11
-kit-gnome-keyring might help.

If someone wants to verify that, please do, otherwise I'll try tomorrow.

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

-- 
Mailing list: https://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 1730410] Re: Window full-screen size when Firefox starts

[Ubfan]

Ubuntu 18.04, Firefox 59.02 64 bit has the same problem. Nvidia driver
390.48 in use.

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

Title:
  Window full-screen size when Firefox starts

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 17.10 Wayland (64 bits AMD), Firefox opens always with the
  window in full-screen size. If you reduce the size before closing it,
  next time, it will open in full-screen size.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpaul  1618 F pulseaudio
   /dev/snd/controlC0:  jpaul  1618 F pulseaudio
   /dev/snd/controlC1:  jpaul  1618 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 15:49:44 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-30 (554 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto static metric 600 
   169.254.0.0/16 dev wlp4s6 scope link metric 1000 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-7494d4c2-9262-44e6-8fb2-3ca0d2161203
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20171025.1-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-7494d4c2-9262-44e6-8fb2-3ca0d2161203
   bp-80a96d18-eeb9-455f-b7c6-046ac2160509
   bp-8e0dc06d-4cc6-4ab7-8618-421d12160508
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to artful on 2017-10-23 (14 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd11/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://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 934291] Re: Deleting or stopping print jobs does not work

[Ken VanDine]

** Also affects: cups-pk-helper (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in cups-pk-helper source package in Bionic:
  New

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

-- 
Mailing list: https://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 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[Asif Youssuff]

FWIW, I tried the Position_fix quirking suggestions here:
https://wiki.ubuntu.com/Audio/PositionReporting and didn't see any
improvement.

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  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: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+subscriptions

-- 
Mailing list: https://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 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

[Iain Lane]

Anyone affected - were you using any PPAs?

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

-- 
Mailing list: https://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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 18.10.1

---
ubiquity (18.10.1) cosmic; urgency=medium

  [ Iain Lane ]
  * Bump sources to cosmic
  * Automatic update of included source packages: bterm-unifont 1.5,
choose-mirror 2.78ubuntu4, preseed 1.71ubuntu8.

  [ Andrea Azzarone ]
  * misc.py: Restore the corrent euid in regain_privileges_save. Calling
regain_privileges_save should restore the effective user-id to the one
before the call  to drop_privileges_save. We need to call os.setresuid and
os.setresgid twice to avoid permission issues when calling os.setgroups.
(LP: #1751252)

 -- Iain Lane   Tue, 08 May 2018 12:07:44 +0100

** Changed in: ubiquity (Ubuntu)
   Status: In Progress => Fix Released

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

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

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: 

[Desktop-packages] [Bug 1762127] Re: Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04

[tim]

Removing amdgpu-pro by running "amdgpu-pro-uninstall" from ubuntu
recovery mode solved this problem for me.

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

Title:
  Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04

Status in xdiagnose package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  * I did a do-release-upgrade -d
  * After the upgrade was done, I rebooted

  Result:

  My computer was stuck in a boot loop, showing alternatively a black
  screen, a text log and a set of random pixels.

  Here is a GIF of the loop: https://imgur.com/zGGTzma

  As I had to make my computer work again I had to reinstal Ubuntu from
  a 18.04 live USB stick, so I'm not sure if I could get information
  from the previous installation. Reinstalling made my computer work
  fine with 18.04. I just need to reinstall all my applications.

  I had an external Mesa installation on 17.10 from Padoka Stable PPA.
  May it be related? At the moment, Mesa version from Padoka Stable is
  18.0.0~*~padoka0, whereas after a 18.04 reinstall it is 18.0.0-rc5

  Note: I tried to boot in safe mode with graphics, but it does not start, I 
get this error in the console:
  /usr/share/xdiagnose/failsafeXinit: line 194 : [: == : unary operator expected

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.13
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  8 08:56:54 2018
  InstallationDate: Installed on 2018-04-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769936] [NEW] [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[Asif Youssuff]

Public bug reported:

Happy to do further testing, fresh install of Bionic. Discovered this
when trying to do a video conference using the built in mic and was able
to verify the issue by installing gnome-sound-recorder.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
 /dev/snd/controlC0:  asif   2213 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue May  8 11:58:37 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-28 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 4MCN31WW(V2.03)
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: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 720-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
dmi.product.family: YOGA 720-15IKB
dmi.product.name: 80X7
dmi.product.version: Lenovo YOGA 720-15IKB
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  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: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+subscriptions

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

[Desktop-packages] [Bug 1543345] Re: nautilus ignores the --geometry= positions unless sudo is used

[Ubfan]

For nautilus, neither position nor size works for either user or sudo in
the Ubuntu 18.04 release, nautilus package 1:3.26.3-0ubuntu4.

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

Title:
  nautilus ignores the --geometry= positions unless sudo is used

Status in nautilus package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04, patched to Feb 7, 2016, running nautilus
  1:3.10.1-0ubuntu9.10 , starting nautilus from a terminal using the
  --geometry=800x300+200+100 will ignore the '+200+100' positioning part
  unless sudo is used, in which case, the positioning is correctly used.
  The size of 800 pixels wide and 300 pixels tall appears by eye to be
  correct for non-sudo and sudo invocations of nautilus, but the window
  position of 200 pixels down and 100 pixels right is ignored unless
  sudo in used for the invocation.

  Non-standard kernel in use:
  uname -a
  Linux tosi 4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

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

-- 
Mailing list: https://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 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

[David Kastrup]

Pretty sure at least I did at several points in the past.  Not sure they
were active at the time of the report, though.

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

-- 
Mailing list: https://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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Diep Pham]

I rebuild the ibus-gtk3 package myself and it seems to work fine so far:
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16.

** Bug watch added: Mozilla Bugzilla #1405634
   https://bugzilla.mozilla.org/show_bug.cgi?id=1405634

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Diep Pham]

Should we just ask author of
https://salsa.debian.org/debian/ibus/commit/097e35c350edf76015c637c26ef637d80191052d
commit to know the reason why the ibus-xx-f19-password.patch is removed?
As I see from this comment in ibus' github page:
https://github.com/ibus/ibus/issues/2002#issuecomment-386537208, @Raytar
told that the problem will happen in Ubuntu 17.10 too with the patch
removed. So, I think there is no harm apply the patch to mitigate the
problem temporarily?

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769922] [NEW] my left speaker has crackling sound. when i was hearing music in my laptop speaker the window locked. At that time the crackling sound started

[Gokul]

Public bug reported:

please fix this soon.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-42-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   gokul  1656 F...m pulseaudio
 /dev/snd/controlC0:  gokul  1656 F pulseaudio
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Tue May  8 20:35:43 2018
InstallationDate: Installed on 2018-04-11 (27 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0210DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF15212SNW:pvrC10HUWG0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVF15212SNW
dmi.product.version: C10HUWG0
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug zesty

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

Title:
  my left speaker has crackling sound. when i was hearing music in my
  laptop speaker the window locked. At that  time the crackling sound
  started

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  please fix this soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-42-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   gokul  1656 F...m pulseaudio
   /dev/snd/controlC0:  gokul  1656 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue May  8 20:35:43 2018
  InstallationDate: Installed on 2018-04-11 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0210DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF15212SNW:pvrC10HUWG0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15212SNW
  dmi.product.version: C10HUWG0
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

[Bug Watch Updater]

** Changed in: fonts-liberation2 (Debian)
   Status: New => Fix Released

** Changed in: fonts-liberation (Debian)
   Status: New => Fix Released

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

Title:
  Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

Status in fonts-liberation package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in fonts-liberation package in Debian:
  Fix Released
Status in fonts-liberation2 package in Debian:
  Fix Released

Bug description:
  Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc
  "Liberation") with sligtly shrinked font metrics. This issue leads to
  all office documents typed in Liberation Sans fonts have corrupted
  formatting in Ubuntu 18.04 (but these documents correctly opened in
  other OS's, for example Ubuntu 17.10). Documents with corrupted
  formatting can not print properly: all paragraphs are shifted up,
  embedded tables in text - splitted on page breaks. Document
  circulation in system based on Ubuntu 18.04 operating systems
  temporarily paralized, because Liberation fonts are basic fonts for
  open-source document circulation.

  In attachment I have type a example office document with 2 pages and
  enumerated strings. On normal ordinary conditions this document have
  54 strings on first page and 54 string on second page. But if this
  document open in Ubuntu 18.04, it's found than 5 strings from second
  page moves to first page. Compare font versions embedded with Ubuntu
  packages we can see that versions are different (sudo apr search
  fonts-liberation* command):

  Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3
  Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5

  I have create a bug 117411 "Font metrics slightly changed after update
  OS to Ubuntu 18.04", see
  https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I
  think that this bug concerns a Ubuntu/Xubuntu 18.04 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+subscriptions

-- 
Mailing list: https://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 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Jeremy Bicha]

I closed the Xenial task since deja-dup in Xenial doesn't use ulimit.

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  Fix Released
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Invalid
Status in deja-dup source package in Artful:
  Fix Released
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

-- 
Mailing list: https://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 1769914] Re: PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink

[Julian Andres Klode]

Attaching lsusb -vv of the device.

** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1769914/+attachment/5136192/+files/lsusb.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/1769914

Title:
  PulseAudio configures Fiio E10K DAC/headphone amp as input, but it
  only is a sink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio thinks that a Fiio E10K can capture audio and tries to
  configure that, leading to a ton of:

  retire_capture_urb: 2492 callbacks suppressed

  messages in dmesg. The device has no capture ability, alsamixer also
  only shows one master playback control; no capture one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:11.1-1ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
   /dev/snd/controlC2:  jak2367 F pulseaudio
   /dev/snd/controlC1:  jak2367 F pulseaudio
   /dev/snd/controlC0:  jak2367 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  8 16:43:47 2018
  InstallationDate: Installed on 2018-03-14 (54 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  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:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1769914] [NEW] PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink

[Julian Andres Klode]

Public bug reported:

PulseAudio thinks that a Fiio E10K can capture audio and tries to
configure that, leading to a ton of:

retire_capture_urb: 2492 callbacks suppressed

messages in dmesg. The device has no capture ability, alsamixer also
only shows one master playback control; no capture one.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:11.1-1ubuntu7
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
 /dev/snd/controlC2:  jak2367 F pulseaudio
 /dev/snd/controlC1:  jak2367 F pulseaudio
 /dev/snd/controlC0:  jak2367 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May  8 16:43:47 2018
InstallationDate: Installed on 2018-03-14 (54 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
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:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

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


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

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

Title:
  PulseAudio configures Fiio E10K DAC/headphone amp as input, but it
  only is a sink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio thinks that a Fiio E10K can capture audio and tries to
  configure that, leading to a ton of:

  retire_capture_urb: 2492 callbacks suppressed

  messages in dmesg. The device has no capture ability, alsamixer also
  only shows one master playback control; no capture one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:11.1-1ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
   /dev/snd/controlC2:  jak2367 F pulseaudio
   /dev/snd/controlC1:  jak2367 F pulseaudio
   /dev/snd/controlC0:  jak2367 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  8 16:43:47 2018
  InstallationDate: Installed on 2018-03-14 (54 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  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:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Iain Lane]

Removed the .gladep file; it seems to have crept in by error during the
git migration (also in my cosmic upload) and uploaded bionic. Thanks and
sorry cyphermox if this treads on your toes.

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

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

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: