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

[Daniel van Vugt]

** Information type changed from Private to Public

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The error is reported on boot up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1557581] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I couldn't log on the desktop and had to delete .XAuthority.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Mar 15 10:39:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1457682482
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-01-12 (427 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=ebb2347f-b7d8-4b1b-a1b8-dda5904995ae ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0211
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 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.:bvr0211:bd05/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Mar 15 14:59:49 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, 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.version: 2:1.18.1-1ubuntu4
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1557346] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1421808, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I think this crash was after a resume (suspended just after removing a
  DisplayLink device)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 14 23:45:43 2016
  DistUpgraded: 2016-02-26 13:01:01,567 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:15a7]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-12-20 (1180 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUSTeK COMPUTER INC. UX51VZA
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=/dev/mapper/ubuntu-root ro pcie_aspm=force drm.vblankoffdelay=1 
i915.semaphores=1 nmi_watchdog=0 "acpi_osi=!Windows 2012"
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (17 days ago)
  UserGroups:
   
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX51VZA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX51VZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX51VZA.204:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnUX51VZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX51VZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 14 23:46:00 2016
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 803 
   vendor LGD
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1565276] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashed with SIGABRT in OsAbort() after resume from suspend

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.28  Wed Feb  3 15:48:04 
PST 2016
   GCC version:  gcc version 5.3.1 20160323 (Ubuntu 5.3.1-13ubuntu1)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Apr  2 14:10:30 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed
   nvidia-361, 361.28, 4.4.0-15-generic, x86_64: installed
   nvidia-361, 361.28, 4.4.0-16-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 520] 
[1462:2632]
  InstallationDate: Installed on 2016-03-30 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=8c810fe3-46d0-4ba7-ac6a-a68c26af42d8 ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B63F1P02
  dmi.board.name: H61MXL/H61MXL-K
  dmi.board.vendor: Foxconn
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB63F1P02:bd09/21/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH61MXL/H61MXL-K:rvr:
  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.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  2 14:10:41 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input2.4G ReceiverKEYBOARD, id 8
   input2.4G ReceiverKEYBOARD, id 9
   inputYSTEK USB Mouse  MOUSE, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1569351] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I am running the development build of xenial 16.04 on a Lenovo w540
  laptop.  Since this is a development build I update and upgrade daily,
  and did both yesterday. I was able to boot this morning and I selected
  "Suspend" from the unity menu. The computer properly suspended and I
  closed the lid.

  When I tried to resume from suspend I was unable to get access to my
  xorg session (black screen). I hit Ctrl+Alt+F5 to switch to a tty
  session, but before I could log in the tty session froze up. I was
  unable to change to a different tty session or do any keyboard input
  at all.

  When I rebooted I got this error with xorg.  Please let me know if you
  need any other information or files. I am mbruzek on IRC.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.15  Sat Apr  2 21:30:33 
PDT 2016
   GCC version:  gcc version 5.3.1 20160407 (Ubuntu 5.3.1-13ubuntu6)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 07:54:50 2016
  DistUpgraded: 2016-02-19 09:58:41,249 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e]
  InstallationDate: Installed on 2015-01-19 (449 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150118)
  MachineType: LENOVO 20BGCTO1WW
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=f27ec108-0f6f-4b63-ac43-61e5c3b6f60e ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to xenial on 2016-02-19 (52 days ago)
  UserGroups: docker
  dmi.bios.date: 11/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET69WW (2.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BGCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 Std
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET69WW(2.17):bd11/26/2014:svnLENOVO:pn20BGCTO1WW:pvrThinkPadW540:rvnLENOVO:rn20BGCTO1WW:rvr0B98405Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BGCTO1WW
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 12 08:00:34 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1569351/+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 1625283] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  crashes repeatedly

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: tito-root: clean, 1313859/15114240 files, 51881669/60448000 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep 19 18:43:20 2016
  DistUpgraded: 2016-09-19 18:24:27,589 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.4.0-38-generic, x86_64: installed
   acpi-call, 1.1.0, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.4.0-38-generic, x86_64: installed
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2014-08-08 (773 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro splash quiet vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to yakkety on 2016-09-19 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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

[Desktop-packages] [Bug 1565334] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed when resuming from suspend.

  xubuntu 16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Apr  2 14:10:03 2016
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2016-04-02 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1722824] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Happened after an upgrade.  First the desktop became unresponsive
  (Emacs window stopped accepting input even while appearing to have
  focus according to cursor shape, Alt-Tab did nothing, nor did clicking
  on any desktop icons).  Console switching still worked.  SIGTERM
  failed to impress panel and desktop, so turned to SIGKILL.  No change
  on the desktop (still a working mouse cursor but no reaction to keys
  or clicks) when console-switching back.  Finally, switching back
  stopped working also, displaying just a blinking text cursor on a
  blank screen, then this abort.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.3-1ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-12.13-lowlatency 4.13.3
  Uname: Linux 4.13.0-12-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 11 16:14:49 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
 Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
  InstallationDate: Installed on 2011-10-14 (2189 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  MachineType: LENOVO 7661LN8
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-lowlatency 
root=UUID=a5b30f2d-d555-4bea-9b89-e322f13656be ro quiet splash threadirqs 
resume=UUID=29869a91-5410-4e9b-9bd9-2aea1ecb1637
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 7661LN8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 000L004051
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7661LN8:pvrThinkPadT61:rvnLENOVO:rn7661LN8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 7661LN8
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1675846] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I rebooted after initial update to a black screen and mouse cursor.  I
  was able to start a simple x session and run an 'apt update' 'apt
  upgrade' and was allowed to get to a desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Fri Mar 24 01:03:13 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2017-03-24 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=71ac57cc-bf3c-40c4-b2a6-baa5e1311ba7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/14/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.27
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4B
  dmi.chassis.asset.tag: BSC750627
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.27:bd06/14/2012:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
  xserver.bootTime: Fri Mar 24 09:36:08 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu9
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1678664] Re: Xorg crashed with SIGABRT after Zesty beta upgrade

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT after Zesty beta upgrade

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Steps:
   * upgrade Ubuntu 16.10 -> do_release_upgrade -d
   * reboot
   * login to Xfce

  Expected outcome:
   * see a working desktop

  Actual outcome:
   * see only the desktop background, no panel, no menu
   * switched to VT1, logged in to try to figure out what happened, but then X 
got restarted
   * login again, all good this time
   * got popup about Xorg crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  2 20:45:03 2017
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2016-11-29 (123 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-04-02 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1723260] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Probably crashed when I observed bug 1722988 happening to me.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 12 15:36:51 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2218]
  InstallationDate: Installed on 2015-04-30 (896 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A8X50300
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=ff9fee12-fd92-4cfd-88bf-c8f57ffba318 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET40WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8X50300
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8X50300:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8X50300:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8X50300
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Oct 12 15:44:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.4-1ubuntu2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1754866] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

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

Bug description:
  Xorg crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CrashCounter: 1
  Date: Sat Mar 10 16:56:09 2018
  DistUpgraded: 2018-01-16 12:35:14,056 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1)'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:2300]
 Subsystem: CLEVO/KAPOK Computer GM107M [GeForce GTX 860M] [1558:2300]
  InstallationDate: Installed on 2015-11-05 (856 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  LocalLibraries: /usr/local/lib/libffi.so.6
  MachineType: Notebook W230SS
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=/dev/sda3 
ro uveau.modeset=0 acpi_enforce_resources=lax nosplash uveau.modeset=0 
acpi_enforce_resources=lax acpi_enforce_resources=lax
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to artful on 2018-01-16 (53 days ago)
  UserGroups:
   
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Mar 10 16:56:22 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1727790] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Thu Oct 26 18:56:36 2017
  DistUpgraded: 2017-10-23 15:48:44,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2016-04-19 (554 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: LENOVO 20HGS1RG00
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency 
root=UUID=b8412798-404c-4b4f-bada-a6cc4220836d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to artful on 2017-10-23 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET35W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS1RG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET35W(1.14):bd07/12/2017:svnLENOVO:pn20HGS1RG00:pvrThinkPadT470s:rvnLENOVO:rn20HGS1RG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HGS1RG00
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1755708] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Do not know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu2
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Tue Mar 13 08:38:35 2018
  DistUpgraded: 2018-03-06 09:10:42,993 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:ff66]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:ff66]
  InstallationDate: Installed on 2018-02-21 (20 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite Pro L350
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ca4efcc2-79a0-46ee-a560-e56f5ad3d93a ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (7 days ago)
  UserGroups:
   
  dmi.bios.date: 09/23/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteProL350:pvrPSLD9E-00Y008IT:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite Pro L350
  dmi.product.version: PSLD9E-00Y008IT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1762697] Re: Xorg crashed with SIGABRT

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Do not know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 10 11:43:29 2018
  DistUpgraded: 2018-03-06 09:10:42,993 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:ff66]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:ff66]
  InstallationDate: Installed on 2018-02-21 (47 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite Pro L350
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=ca4efcc2-79a0-46ee-a560-e56f5ad3d93a ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 09/23/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteProL350:pvrPSLD9E-00Y008IT:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite Pro L350
  dmi.product.version: PSLD9E-00Y008IT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1726039] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()
** This bug has been marked a duplicate of private bug 1421808

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  Resumed from wake.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  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
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog: [4.625380] libvirt-guests.sh[887]: libvirt-guests is configured 
not to start any guests on boot
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Sun Oct 22 15:18:54 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0797]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0797]
  InstallationDate: Installed on 2017-10-18 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  MachineType: Dell Inc. Inspiron 7566
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=56ade247-936c-4a37-8332-6ac5ab0f6c6a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 0293F5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd10/26/2016:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn0293F5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Oct 22 15:23:43 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

[Daniel van Vugt]

** Summary changed:

- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() 
from glamor_pixmap_ensure_fb()

** Information type changed from Private to Public

-- 
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:
  Triaged

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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]

[Daniel van Vugt]

** Summary changed:

- Xorg crashed with SIGABRT in OsAbort() ["no screens found"]
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() 
from dix_main() ["no screens found"]

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from dix_main() ["no screens found"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530

  ---

  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Feb  8 17:07:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffc9e34fc8) at libc-start.c:289
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Mon Feb  8 17:08:14 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 9847 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.17.3-2ubuntu2

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

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

[Desktop-packages] [Bug 1546541] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

** Information type changed from Private to Public

** Summary changed:

- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() 
from CreateWellKnownSockets()

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Running in low graphics mode on Xenial if I run startx from the
  console I can get a desktop but this is the only way I can't get to
  either gdm or lightdm login screens.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
  Uname: Linux 4.4.0-4-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Feb 17 13:23:13 2016
  DistUpgraded: 2015-12-08 13:54:44,635 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0238]
  InstallationDate: Installed on 2012-11-18 (1185 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmGreeterLog: Error writing X authority: Failed to open X authority 
/var/lib/lightdm/.Xauthority: No such file or directory
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-5-generic 
root=UUID=83a5bb3c-2543-42d9-b253-914c5f894d4e ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   CreateWellKnownSockets ()
   ?? ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to xenial on 2015-12-08 (70 days ago)
  UserGroups:
   
  dmi.bios.date: 09/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0RK936
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0RK936:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Vostro 200
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Wed Feb 17 13:26:13 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 835 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5889 
   vendor PGE
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Desktop-packages] [Bug 1430083] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of private bug 1429927
** This bug has been marked a duplicate of bug 1546541
   Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() 
from CreateWellKnownSockets()

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  upon boot

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  Uname: Linux 4.0.0-04rc1-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Mar  9 19:10:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b8]
   NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b8]
  InstallationDate: Installed on 2015-02-25 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150225)
  MachineType: Dell Inc. Dell System XPS L702X
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.0-04rc1-generic 
root=UUID=9926f78a-e78e-4da2-8c45-43610f6e99e7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   CreateWellKnownSockets ()
   ?? ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0XN71K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L702X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Mar  9 20:37:53 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 730 
   vendor LGD
  xserver.version: 2:1.16.2.901-1ubuntu4

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

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

[Desktop-packages] [Bug 313514] Re: MASTER: evdev driver ignores keycodes > 255

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.

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: 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/313514

Title:
  MASTER: evdev driver ignores keycodes > 255

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  package Version: 1:2.0.99+git20080912-0ubuntu5
  Ubuntu 8.10

  Keyboards can use keycodes that go above 255. See 
http://lxr.linux.no/linux+v2.6.28/include/linux/input.h
  These are often multimedia keys for keyboards and remotes.

  These are ignored by the evdev driver:
  gimble:~/xserver-xorg-input-evdev-2.0.99+git20080912$ grep 255 src/evdev.c 
  if (code > 255 && ev->code < KEY_MAX) {
  /* The X server can't handle keycodes > 255 anyway, just drop them.  */

  Which means they never reach X and therefore cannot be used in anyway.

  The only workaround at the minute would be to use input-kdb to remap
  all keys for an input device to values lower than 255.

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

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

[Desktop-packages] [Bug 1338492] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

See also bug 1543192, which may be more relevant.

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  At startup, my screen flashes in light green, and can't log to lightdm. 
Adding the ATI driver, it will install with a missing link... Erasing cyrillic 
path and 75 and 100 dpi path folders.
  At this time, can't find again the missing link, and  just install missings 
fonts don't fix the bug..

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.15.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Jul  7 10:44:49 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-03 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4f6b2e78) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  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.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  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-1ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jul  7 10:48:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputEee PC WMI hotkeys   KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1057000] Re: [Ubuntu 12.04.1/12.10] nVidia drivers 304.51 prevent autohidden Unity launcher from revealing

[Daniel van Vugt]

** Changed in: nvidia-graphics-drivers-updates (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  [Ubuntu 12.04.1/12.10] nVidia drivers 304.51 prevent autohidden Unity
  launcher from revealing

Status in NVIDIA Drivers Ubuntu:
  Fix Released
Status in Unity:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-updates package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-updates source package in Precise:
  Invalid
Status in xorg-server source package in Precise:
  Won't Fix
Status in nvidia-graphics-drivers source package in Quantal:
  Fix Released
Status in nvidia-graphics-drivers-updates source package in Quantal:
  Won't Fix
Status in xorg-server source package in Quantal:
  Won't Fix

Bug description:
  The bug is as described in the title. Reverting to drivers 304.43
  solves the problem.

  This report is intended primarily for those suffering from this bug
  and not knowing how to solve it. Today I also reported it to nVidia,
  but it will take time for them to respond and fix it.

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

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

[Desktop-packages] [Bug 1338492] Re: Xorg crashed with SIGABRT in OsAbort()

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

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 log a new bug for it.

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => 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/1338492

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  At startup, my screen flashes in light green, and can't log to lightdm. 
Adding the ATI driver, it will install with a missing link... Erasing cyrillic 
path and 75 and 100 dpi path folders.
  At this time, can't find again the missing link, and  just install missings 
fonts don't fix the bug..

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.15.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Jul  7 10:44:49 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-03 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4f6b2e78) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  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.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  

[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-bionic

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1532625] Re: "Launchpad Contributions:" string isn't translatable

[Launchpad Bug Tracker]

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

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

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

Title:
  "Launchpad Contributions:" string isn't translatable

Status in Inkscape:
  Invalid
Status in inkscape package in Ubuntu:
  Expired

Bug description:
  Ubuntu 15.10
  Inkscape 0.91 r13725

  the string "Launchpad Contributions:" in the 'About' tab isn't
  translated and is untranslatable

  Thank for the work

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

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

[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Triaged => Fix Committed

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1710421] Re: Keyboard accelerators for window menus aren't implemented

[Daniel van Vugt]

Also worth noting: Keyboard navigation of the window menu is still
possible, just slower:

1. Alt+Space
2. Up/Down arrows
3. Enter


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

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

Title:
  Keyboard accelerators for window menus aren't implemented

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

Bug description:
  Description from duplicate bug 1725706:

  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Login to the default Ubuntu session
  3. Open any windowed application such as Nautilus or `gnome-terminal`
  3. Click  to show current window settings
  4. Try to set "Always on Top" property with keyboard shortcut ()

  Expected results:
  * window reacts on  and set on top as requested

  Actual results:
  * window does not react on 

  Notes:
  "Always on Top" is just an illustration. Mnemonics for other (Minimize, 
Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, 
etc) do not defined and do work too.

  
  Original description below:

  Other desktop systems including Microsoft Windows and Unity have
  accelerator keys in the window menu. This is typically accessible via
  ALT_Space on any window, then pressing a key to initiate the desired
  function.

  Typically Alt_Space can be used to bring up the menu, then use x to
  maximise a window, n to minimise a window, etc. GNOME Shell does not
  implement these accelerator keys, which seems inconsistent with other
  desktops, and internally inconsistent, as other menus in GNOME
  applications _do_ have accelerator keys.

  It would be great for people coming to GNOME Shell should be able to
  use the familiar keyboard shortcuts they're used to.

  As far as I can test (as far back as 16.04) this has always been the
  case.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 22:49:46 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-02 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1710421/+subscriptions

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

[Desktop-packages] [Bug 1769558] [NEW] package texlive-lang-greek (not installed) failed to install/upgrade: unable to open '/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/grmc1095.pfb.dpkg-

[Michael]

Public bug reported:

I'm using Ubuntu 18.4 (just installed) on a ThinkPad T470. While trying
to install the full texlive I got some error messages and was eventually
asked to run the following:

michael@michael-ThinkPad-T470:~$ sudo apt --fix-broken install
[sudo] password for michael: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following package was automatically installed and is no longer required:
  libmng2
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  texlive-lang-greek
The following NEW packages will be installed:
  texlive-lang-greek
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/76.3 MB of archives.
After this operation, 95.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 171692 files and directories currently installed.)
Preparing to unpack .../texlive-lang-greek_2017.20180305-1_all.deb ...
Unpacking texlive-lang-greek (2017.20180305-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/texlive-lang-greek_2017.20180305-1_all.deb (--unpack):
 unable to open 
'/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/gmxn1440.pfb.dpkg-new':
 Operation not permitted
Errors were encountered while processing:
 /var/cache/apt/archives/texlive-lang-greek_2017.20180305-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: texlive-lang-greek (not installed)
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
AptOrdering:
 texlive-lang-greek:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun May  6 21:47:08 2018
DpkgTerminalLog:
 Preparing to unpack .../texlive-lang-greek_2017.20180305-1_all.deb ...
 Unpacking texlive-lang-greek (2017.20180305-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/texlive-lang-greek_2017.20180305-1_all.deb (--unpack):
  unable to open 
'/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/grmc1095.pfb.dpkg-new':
 Operation not permitted
ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/grmc1095.pfb.dpkg-new':
 Operation not permitted
InstallationDate: Installed on 2018-05-05 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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: texlive-lang
Title: package texlive-lang-greek (not installed) failed to install/upgrade: 
unable to open 
'/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/grmc1095.pfb.dpkg-new':
 Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-lang (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package texlive-lang-greek (not installed) failed to install/upgrade:
  unable to open '/usr/share/texlive/texmf-
  dist/fonts/type1/public/cbfonts/grmc1095.pfb.dpkg-new': Operation not
  permitted

Status in texlive-lang package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.4 (just installed) on a ThinkPad T470. While
  trying to install the full texlive I got some error messages and was
  eventually asked to run the following:

  michael@michael-ThinkPad-T470:~$ sudo apt --fix-broken install
  [sudo] password for michael: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following package was automatically installed and is no longer required:
libmng2
  Use 'sudo apt autoremove' to remove it.
  The following additional packages will be installed:
texlive-lang-greek
  The following NEW packages will be installed:
texlive-lang-greek
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  Need to get 0 B/76.3 MB of archives.
  After this operation, 95.1 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 171692 files and directories currently installed.)
  Preparing to unpack .../texlive-lang-greek_2017.20180305-1_all.deb ...
  Unpacking texlive-lang-greek (2017.20180305-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-lang-greek_2017.20180305-1_all.deb (--unpack):
   unable to open 
'/usr/share/texlive/texmf-dist/fonts/type1/public/cbfonts/gmxn1440.pfb.dpkg-new':
 Operation not permitted
  Errors were 

[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Triaged

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1769556] [NEW] Snap branches shown in random order

[Robert Ancell]

Public bug reported:

[Impact]
Snap branches are shown in a random order.

[Test Case]
1. Open GNOME Software
2. Search for and select "communitheme" snap
3. Select available channels (requires LP: #1768779 to be fixed).

Expected result:
Branches are shown in some predictable order.

Observed result:
Branches are shown in a random order.

[Regression Potential]
Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Bionic)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Cosmic)
 Importance: Medium
 Status: Triaged

** Also affects: gnome-software (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Triaged

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name

[Robert Ancell]

** Summary changed:

- A lot of the same entries for Communitheme snap channels
+ Snap branches all show with same name

** Description changed:

+ [Impact]
+ Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.
+ 
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  
- Notice the names are all the same
+ Expected result:
+ All branches/channels are show, as shown by 'snap info communitheme'
  
- Screenshot attached
+ Observed result:
+ All branches have the same name.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: gnome-software 3.28.1-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: communitheme:ubuntu:GNOME
- Date: Thu May  3 10:38:37 2018
- InstallationDate: Installed on 2018-04-30 (2 days ago)
- InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
- InstalledPlugins:
-  gnome-software-plugin-flatpak 3.28.1-0ubuntu4
-  gnome-software-plugin-limba   N/A
-  gnome-software-plugin-snap3.28.1-0ubuntu4
- SourcePackage: gnome-software
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Regression Potential]
+ Fix was an invalid iterator, unlikely to cause further issues.

** Description changed:

  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.
  
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  
  Expected result:
- All branches/channels are show, as shown by 'snap info communitheme'
+ All branches/channels are shown.
  
  Observed result:
  All branches have the same name.
  
  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are shown.

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

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

[Desktop-packages] [Bug 152279] Re: Totem gets aspect ratio wrong when the monitor is rotated

[Daniel van Vugt]

It appears nobody has confirmed this bug since January 2016. Can you
confirm which release you see the problem in?

** Summary changed:

- Totem gets aspect ratio wrong
+ Totem gets aspect ratio wrong when the monitor is rotated

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

Title:
  Totem gets aspect ratio wrong when the monitor is rotated

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: totem

  I use a pivot monitor. When I rotate the screen with xrandr -o left or
  Grandr, totem gets the aspect ratio wrong. For instance a 4:3 film is
  shown as 3:4, that means higher than wide. It is also not possible to
  correct the aspect ratio from the GUI menu. New video thumbnails are
  also distorted, however in the other direction: They become much wider
  than hig.

  Kaffeine shows the same buggy behaviour as Totem, while VLC doesn't.
  VLC gets the aspect ratio right. This bug was also not there in
  Feisty.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Robert Ancell]

** Description changed:

- Ubuntu 18.04 Gnome Shell with Communitheme.
+ [Impact]
+ Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.
  
- Steps to reproduce:
+ [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries
  
  Expected result:
  You can scroll the list
  
  What happen instead:
  You cannot scroll the list
  
- Screenshot attached
+ [Regression Potential]
+ Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-bionic

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are show, as shown by 'snap info communitheme'

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-bionic

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are show, as shown by 'snap info communitheme'

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with many channels/branches (e.g. communitheme) make the channel 
selector too large - it should use a scrollable window if there are many.

  [Test Case]
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  [Regression Potential]
  Solution is to use a GtkScrolledWindow for the list. Could cause other UI 
bugs to occur.

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are show, as shown by 'snap info communitheme'

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Robert Ancell]

** No longer affects: gnome-software (Ubuntu Xenial)

** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are show, as shown by 'snap info communitheme'

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

[Daniel van Vugt]

Note to all readers:

1. A workaround to enable the (unfinished) feature is at the top of this
bug in the Bug Description.

2. An alternative solution, which I've found works fine for many systems
(lower than 3K resolution) is: gnome-tweaks > Fonts > Interface > choose
your own font size(s)

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  In Progress
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Robert Ancell]

Note this doesn't occur in Xenial as the code changes required for
backport fixed the issue there. Though the communitheme doesn't show
(LP: #1763736)

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Bionic:
  New
Status in gnome-software source package in Cosmic:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-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: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769553] [NEW] xfs blocks on unresponsive raid - blockdev module is missing

[Bruno Vasselle]

Public bug reported:

# lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

udisks2: 2.7.6-3
libblockdev-mdraid2: 2.16-2

Ubuntu 18.04, freshly upgraded from 16.04 via 17.10; system ran OK for about 
72h before issue.
Filesystem on faulty raid is XFS, and raid is raid 10 far-copies:

md3 : active raid10 sdb4[2] sda4[4]
  524155904 blocks super 1.2 512K chunks 2 far-copies [2/2] [UU]

What happened:

A "git commit" could not succeed. Process was impossible to kill. Load
reported by xload reached outstanding levels; system was still
responsive however, but impossible to halt, waiting for disk sync that
never occurred. I had to reboot the hard way.

After reboot, /home could not mount, and boot process dropped me to a
root console. I could see that mdadm reported ongoing reconstruction,
but frozen at some point. In the logs:

May  6 01:35:35 localhost kernel: [58614.835510] INFO: task xfsaild/md3:1056 
blocked for more than 120 seconds.
May  6 01:35:35 localhost kernel: [58614.835521]   Tainted: G   OE  
  4.15.0-20-lowlatency #21-Ubuntu
May  6 01:35:35 localhost kernel: [58614.835524] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May  6 01:35:35 localhost kernel: [58614.835529] xfsaild/md3 D0  1056   
   2 0x8000
May  6 01:35:35 localhost kernel: [58614.835535] Call Trace:
May  6 01:35:35 localhost kernel: [58614.835552]  __schedule+0x299/0x8c0
May  6 01:35:35 localhost kernel: [58614.835560]  schedule+0x33/0x90
May  6 01:35:35 localhost kernel: [58614.835570]  wait_barrier+0x134/0x190 
[raid10]
May  6 01:35:35 localhost kernel: [58614.835578]  ? wait_woken+0x80/0x80
May  6 01:35:35 localhost kernel: [58614.835585]  
raid10_write_request+0x77/0x950 [raid10]
...

Another line of interest:

May  6 02:05:59 localhost udisksd[1480]: failed to load module mdraid:
libbd_mdraid.so.2: cannot open shared object file: No such file or
directory

Actually, package libblockdev-mdraid2 is missing. Added it as well as
libblockdev-mpath2. Rebooted. mdadm starts reconstruction and is OK when
I come back from sleep.

System looks stable since then.

** Affects: udisks2 (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/1769553

Title:
  xfs blocks on unresponsive raid - blockdev module is missing

Status in udisks2 package in Ubuntu:
  New

Bug description:
  # lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  udisks2: 2.7.6-3
  libblockdev-mdraid2: 2.16-2

  Ubuntu 18.04, freshly upgraded from 16.04 via 17.10; system ran OK for about 
72h before issue.
  Filesystem on faulty raid is XFS, and raid is raid 10 far-copies:

  md3 : active raid10 sdb4[2] sda4[4]
524155904 blocks super 1.2 512K chunks 2 far-copies [2/2] [UU]

  What happened:

  A "git commit" could not succeed. Process was impossible to kill. Load
  reported by xload reached outstanding levels; system was still
  responsive however, but impossible to halt, waiting for disk sync that
  never occurred. I had to reboot the hard way.

  After reboot, /home could not mount, and boot process dropped me to a
  root console. I could see that mdadm reported ongoing reconstruction,
  but frozen at some point. In the logs:

  May  6 01:35:35 localhost kernel: [58614.835510] INFO: task xfsaild/md3:1056 
blocked for more than 120 seconds.
  May  6 01:35:35 localhost kernel: [58614.835521]   Tainted: G   
OE4.15.0-20-lowlatency #21-Ubuntu
  May  6 01:35:35 localhost kernel: [58614.835524] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  May  6 01:35:35 localhost kernel: [58614.835529] xfsaild/md3 D0  1056 
 2 0x8000
  May  6 01:35:35 localhost kernel: [58614.835535] Call Trace:
  May  6 01:35:35 localhost kernel: [58614.835552]  __schedule+0x299/0x8c0
  May  6 01:35:35 localhost kernel: [58614.835560]  schedule+0x33/0x90
  May  6 01:35:35 localhost kernel: [58614.835570]  wait_barrier+0x134/0x190 
[raid10]
  May  6 01:35:35 localhost kernel: [58614.835578]  ? wait_woken+0x80/0x80
  May  6 01:35:35 localhost kernel: [58614.835585]  
raid10_write_request+0x77/0x950 [raid10]
  ...

  Another line of interest:

  May  6 02:05:59 localhost udisksd[1480]: failed to load module mdraid:
  libbd_mdraid.so.2: cannot open shared object file: No such file or
  directory

  Actually, package libblockdev-mdraid2 is missing. Added it as well as
  libblockdev-mpath2. Rebooted. mdadm starts reconstruction and is OK
  when I come back from sleep.

  System looks stable since then.

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

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

[Desktop-packages] [Bug 1710421] Re: Keyboard accelerators for window menus aren't implemented

[Daniel van Vugt]

Ubuntu did not design or write the relevant code here. It's not our
choice. Just that nobody in the world has implemented it yet.

In order to get it implemented please either comment in
https://bugzilla.gnome.org/show_bug.cgi?id=733297 or log a new issue in
https://gitlab.gnome.org/GNOME/gnome-shell/issues

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

Title:
  Keyboard accelerators for window menus aren't implemented

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

Bug description:
  Description from duplicate bug 1725706:

  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Login to the default Ubuntu session
  3. Open any windowed application such as Nautilus or `gnome-terminal`
  3. Click  to show current window settings
  4. Try to set "Always on Top" property with keyboard shortcut ()

  Expected results:
  * window reacts on  and set on top as requested

  Actual results:
  * window does not react on 

  Notes:
  "Always on Top" is just an illustration. Mnemonics for other (Minimize, 
Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, 
etc) do not defined and do work too.

  
  Original description below:

  Other desktop systems including Microsoft Windows and Unity have
  accelerator keys in the window menu. This is typically accessible via
  ALT_Space on any window, then pressing a key to initiate the desired
  function.

  Typically Alt_Space can be used to bring up the menu, then use x to
  maximise a window, n to minimise a window, etc. GNOME Shell does not
  implement these accelerator keys, which seems inconsistent with other
  desktops, and internally inconsistent, as other menus in GNOME
  applications _do_ have accelerator keys.

  It would be great for people coming to GNOME Shell should be able to
  use the familiar keyboard shortcuts they're used to.

  As far as I can test (as far back as 16.04) this has always been the
  case.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 22:49:46 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-02 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1710421/+subscriptions

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

[Desktop-packages] [Bug 1727356] Re: Wayland sessions (including the login screen itself) don't start up on older Intel GPUs.

[Daniel van Vugt]

Bug confirmed by more users, including:

Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz
Intel(R) Atom(TM) CPU N550 @ 1.50GHz

This is reminiscent of bug 1583532, so we may need to review the shaders
used in mutter/clutter/cogl.

I now agree with "High" importance.

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

Title:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1727356] Re: Wayland sessions (including the login screen itself) don't start up on older Intel GPUs.

[Daniel van Vugt]

** Summary changed:

- Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": 
Shader compilation failed
+ Wayland sessions (including the login screen itself) don't start up on older 
Intel GPUs.

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Tags added: bionic

** Description changed:

+ Wayland sessions (including the login screen itself) don't start up on
+ older Intel GPUs.
+ 
+ ---
+ 
+ Workaround:
+ 
+ Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
+ #WaylandEnable=false
+ 
+ ---
+ 
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  Upgraded from 17.04 today.
  
  Steps to reproduce:
  
  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'
  
  Expected to happen:
  
  Desktop appears.
  
  Actually happening:
  
  5 seconds of black screen, then the login screen appears again.
  
  Partial diagnosis:
  
  - Logging in using 'Ubuntu on Xorg' works fine and as expected.
  
  - Extracted a syslog of such a failed attempt, see attached file.
- --- 
+ ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

Title:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1768015] Re: GDM3 defaults to Wayland problem

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1767606
   [Intel Merom/Pineview graphics] GDM login screen does not appear (unless 
Wayland is manually disabled)
** This bug has been marked a duplicate of bug 1727356
   Wayland sessions (including the login screen itself) don't start up on older 
Intel GPUs.

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

Title:
  GDM3 defaults to Wayland problem

Status in gdm3 package in Ubuntu:
  New

Bug description:
  By default gdm3 starts in Wayland mode, and my computer doesn't like
  that : the screen stay on Plymouth, and I can't do anything beside
  remote ssh login.

  To workaround this I must edit the file /etc/gdm3/custom.conf and
  uncomment the "WaylandEnable=false" line.

  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 i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:29:29 2018
  InstallationDate: Installed on 2010-11-10 (2727 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-04-30T14:02:41.481610

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

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

[Desktop-packages] [Bug 1767606] Re: [Intel Merom/Pineview graphics] GDM login screen does not appear (unless Wayland is manually disabled)

[Daniel van Vugt]

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

Let's group this with bug 1727356.

** This bug has been marked a duplicate of bug 1727356
   Wayland sessions (including the login screen itself) don't start up on older 
Intel GPUs.

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

Title:
  [Intel Merom/Pineview graphics] GDM login screen does not appear
  (unless Wayland is manually disabled)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of the final Ubuntu 18.04 the boot process hangs
  after GDM call (the login screen does not appear). After a few tests I
  realized that editing /etc/gdm3/custom.conf and removing the comment
  before "WaylandEnable=false" make the booting working again (with the
  wayland session option not available in GDM). I also tried using
  lightdm. In this case the login screen appears and I can choose xorg
  or wayland session from there. The latter (wayland) does not work and
  the system hangs on a black screen. This is also weird as the wayland
  session used to work flawlessly on the very same machine on 17.10. I
  don't need the wayland session but just found weird that system cannot
  start the login screen out-of-the-box and gdm does not automatically
  fallback.

  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: ubuntu:GNOME
  Date: Sat Apr 28 11:04:18 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-04-28T10:40:22.176527

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Артем]

After installing the switcheroo-control package, I got the same output as the 
Amir
But the discrete graphics card does not turn off. The fan rotates, the power 
consumption is at a high level.

-- 
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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

** Description changed:

  * 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 shouldn't hit an XError
+ Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.
  
  * Regression potential
- the fix is ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer
+ 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:

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

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[Daniel van Vugt]

To debug a crash we require a crash report. To do this, please:

1. Apply the workaround from bug 994921.

2. Reproduce the crash.

3. Run: ubuntu-bug /var/crash/YOURFILE.crash

4. Mention here the ID of the new bug create.

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

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Xorg crash

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  

[Desktop-packages] [Bug 1768532] Re: Nautilus-desktop popup behind the ubuntu-dock

[Daniel van Vugt]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Nautilus-desktop popup behind the ubuntu-dock

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

Bug description:
  Ubuntu 18.04 with Gnome Shell

  Steps to reproduce:
  1. Create a folder on the desktop
  2. Press F2 to change the folder's name

  Expected result:
  The popup where you can write new name is not obstructed by the dock

  What happens instead:
  The popup where you can write new name is partially covered by the dock

  Screenshot attached

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

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

[Desktop-packages] [Bug 1769298] Re: Unlock screen does not accept correct password

[Daniel van Vugt]

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

I believe this falls under bug 1765261. Upstream has a fix coming...

** This bug has been marked a duplicate of bug 1765261
   [regression] Ubuntu 18.04 login screen rejects a valid password on first 
attempt. Usually works on the second attempt

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

Title:
  Unlock screen does not accept correct password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The unlock screen that you get after locking the computer will
  sometimes not accept the correct password. If I switch to tty1 I can
  login with the same, correct password fine and if I reboot the
  computer (lose all my open apps and unsaved data), the password works
  fine as well.

  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
  NonfreeKernelModules: sep4_1 socperf2_0 pax nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 07:11:57 2018
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2233 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  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/1769298/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

We also need a GUI enhancement to gnome-control-center to expose the
setting, which already exists.

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Wishlist

** Description changed:

  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS
  2. Login to session
  3. Press ACPI Power button/key
- 
  
  Expected behavior:
  * Ubuntu asks user about action
  
  Actual behavior:
  * Ubuntu immediately shutdowns
+ 
+ Workaround/fix:
+ gsettings set org.gnome.settings-daemon.plugins.power power-button-action 
interactive
  
  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)

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

Title:
  Prompt the user when the power button is pressed

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

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

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Workaround/fix:
  gsettings set org.gnome.settings-daemon.plugins.power power-button-action 
interactive

  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)

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 1768199] Re: Chromium freezes

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Chromium freezes

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After I updated to Ubuntu 18.04 I noticed that chromium interactions
  (scroll for example) and mouse pointer itself started to freeze for
  hundreds of milliseconds (0.1s - 0.2s).

  So, I was constantly scrolling (in order to reproduce the bug) while
  running perf top, and it pointed to this function:

  sudo perf top -t 1892 -d 5 --call-graph fp

    Children  Self  Shared Object   Symbol

  -   80,55% 0,00%  libc-2.27.so[.] __GI___ioctl
     - 76,84% __GI___ioctl
  71,67% _nv029804rm
    - 1,12% _nv020749rm
   - 1,03% os_release_spinlock
    0,97% _raw_spin_unlock_irqrestore

  -   71,69%71,67%  [kernel][k] _nv029804rm
   71,58% 0x18012a
  __GI___ioctl
  _nv029804rm

  -   16,75% 0,00%  [unknown]   [k] 0x0018012a
   0x18012a
     - __GI___ioctl
  15,25% _nv029804rm

  -8,67% 0,25%  libc-2.27.so[.] syscall
     - 5,45% syscall
  1,89% syscall_return_via_sysret
    - 1,05% entry_SYSCALL_64_after_hwframe
   - 1,22% do_syscall_64

  top command also showed that this process was eating one core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  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: KDE
  Date: Tue May  1 10:38:19 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-12-16 (136 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  InstalledPlugins:

  Load-Avg-1min: 1.64
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (28 days ago)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

Here's a fix :)

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

It's just not the default.

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Fix Released => Triaged

** No longer affects: gnome-control-center (Ubuntu)

** No longer affects: gnome-shell (Ubuntu)

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

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

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

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Workaround/fix:
  gsettings set org.gnome.settings-daemon.plugins.power power-button-action 
interactive

  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)

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 1769372] Re: Prompt the user when the power button is pressed

[Daniel van Vugt]

Oh! The schema does support it already ("interactive"):

  




  


** No longer affects: systemd (Ubuntu)

** No longer affects: upower (Ubuntu)

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

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Prompt the user when the power button is pressed

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

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

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Workaround/fix:
  gsettings set org.gnome.settings-daemon.plugins.power power-button-action 
interactive

  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)

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 1769372] Re: Prompt the user when the power button is pressed

[Launchpad Bug Tracker]

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

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

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

Title:
  Prompt the user when the power button is pressed

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

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

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  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)

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 1769372] Re: Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Daniel van Vugt]

The default action is suspend:


  'suspend'
  Power button action
  The action to take when the system power button is pressed. 
This action is hard-coded (and the setting ignored) on virtual machines (power 
off) and tablets (suspend).


but you can change that in:

Settings >
Power >
Suspend & Power Button >
When the Power Button is pressed ...

Unfortunately no option exists to prompt the user. So that would be an
enhancement request...

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - 
immediately shutdowns
+ Prompt the user when the power button is pressed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Prompt the user when the power button is pressed

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

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

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  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)

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 1769372] Re: Prompt the user when the power button is pressed

[Launchpad Bug Tracker]

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

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

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

Title:
  Prompt the user when the power button is pressed

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

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

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  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)

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 1769409] Re: Support for global menu

[Daniel van Vugt]

We're aiming to make as much as possible unchanged from upstream. So for
now I suggest you work with the extension authors to add any features
you need.

** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/1769409

Title:
  Support for global menu

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The move to Gnome from Unity was ok except for two major features that
  got lost and those are global menus and pixel saving when maximized.

  Are there any chances of official support in future releases?

  Gnome extension for global menus exists https://github.com/lestcape
  /Gnome-Global-AppMenu and that may be used as a starting point. The
  Ubuntu team already did similar move by including the plugin dash-to-
  dock.

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

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

[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable

[Robert Ancell]

** Also affects: gnome-software (Ubuntu Cosmic)
   Importance: Low
   Status: Confirmed

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  Snap channel selection list not scrollable

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  Ubuntu 18.04 Gnome Shell with Communitheme.

  Steps to reproduce:
  1. Search for ”communitheme” in the store
  2. Open ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels
  5. Try to scroll to see more entries

  Expected result:
  You can scroll the list

  What happen instead:
  You cannot scroll the list

  Screenshot attached

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

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

[Desktop-packages] [Bug 1768794] Re: A lot of the same entries for Communitheme snap channels

[Robert Ancell]

** Also affects: gnome-software (Ubuntu Cosmic)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: Confirmed

** Also affects: gnome-software (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  A lot of the same entries for Communitheme snap channels

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Bionic:
  New
Status in gnome-software source package in Cosmic:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Notice the names are all the same

  Screenshot attached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-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: communitheme:ubuntu:GNOME
  Date: Thu May  3 10:38:37 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+

[林博仁]

According to the upstream developer the feature *does* exist, but has a
prerequisite requirement that the user's template folder must have at
least one template file in order to make the "New Document" submenu
appear.

The upstream report has been updated to make Files preserve the same
behavior as with the previous implementation in Ubuntu.

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  https://bazaar.launchpad.net/~ubuntu-
  desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

[Diego A . Zapata Häntsch]

Same issue in Ubuntu 18.04 LTS, HPLIP 3.18.4.
Every time at startup a popup error display the message "No system tray 
detected".
Please solve the problem.
Thanks.

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

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

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

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

  Expected results:
  hp-systray is compatible with modern GNOME

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

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

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

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

[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

[josvanr]

Correction: the nineth anniversary of this bug is only now coming up
soon:

ubuntu 18.04

xdg-open transmission-gtk.desktop

opens up a text editor instead of launching 'transmission'

It seems to work on xubuntu 17.10, though...

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

Title:
  xdg-open *.desktop opens text editor

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

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

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

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

[PJSingh5000]

This is still an issue on Ubuntu 18.04 using Xorg.

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

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

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

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in caribou package in Ubuntu:
  Confirmed

Bug description:
  Unable to type capital letters using onscreen keyboard:

  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769509] Re: package libp11-kit-gnome-keyring 3.28.0.2-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable

[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 gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1769509

Title:
  package libp11-kit-gnome-keyring 3.28.0.2-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:
  New

Bug description:
  during upgrade to ubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.28.0.2-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: Sun May  6 15:18:24 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   gnome-keyring-pkcs11 3.28.0.2-1ubuntu1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.28.0.2-1ubuntu1
   Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-hsJXDs/0496-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
  InstallationDate: Installed on 2011-09-15 (2425 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  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.28.0.2-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-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1769509] [NEW] package libp11-kit-gnome-keyring 3.28.0.2-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installab

[Ivan Bella]

Public bug reported:

during upgrade to ubuntu 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libp11-kit-gnome-keyring 3.28.0.2-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: Sun May  6 15:18:24 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 gnome-keyring-pkcs11 3.28.0.2-1ubuntu1
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libp11-kit-gnome-keyring:3.28.0.2-1ubuntu1
 Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-hsJXDs/0496-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
InstallationDate: Installed on 2011-09-15 (2425 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
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.28.0.2-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-06 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libp11-kit-gnome-keyring 3.28.0.2-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:
  New

Bug description:
  during upgrade to ubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.28.0.2-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: Sun May  6 15:18:24 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   gnome-keyring-pkcs11 3.28.0.2-1ubuntu1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.28.0.2-1ubuntu1
   Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-hsJXDs/0496-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
  InstallationDate: Installed on 2011-09-15 (2425 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  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.28.0.2-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-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1570227] Re: Open Recent Items show as always empty in Gedit

[donnyKerabatsos]

experiencing the same problem after upgrading to ubuntu 16.04

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

Title:
  Open Recent Items show as always empty in Gedit

Status in gedit:
  New
Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  Gedit doesn't show the recently opened files under File -> Open
  Recent. In Open Recent it only shows Reopen Closed Tabs but that is
  also not active (i.e not clickable).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr 14 13:16:33 2016
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729777] Re: [snap] Cannot open downloaded files

[Olivier Tilloy]

This is now fixed with recent versions of snapd. When clicking a
downloaded file, the user is prompted for confirmation to allow the
application to open the file, and then the file is open.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [snap] Cannot open downloaded files

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After downloading a file with the chromium snap (62.0.3202.75), if I
  open the Downloads page and click either on the filename or on the
  "Show in folder" link, nothing happens. I'm seeing the following
  message in the console:

  Error org.freedesktop.DBus.Error.AccessDenied: Supplied URL scheme "" is not 
allowed
  Error org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.SafeLauncher was not provided by any .service files

  This is due to snapd's re-implementation of xdg-open
  (https://github.com/snapcore/snapd/blob/master/userd/launcher.go#L73).

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

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

[Desktop-packages] [Bug 1769495] Re: [snap] Chromium snap should ask for "removable-media" interface

[Olivier Tilloy]

** Tags added: snap

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] Chromium snap should ask for "removable-media" interface

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This will helps people that keep lots of files on the external hard
  drive (for example). If I understand correctly, this interface should
  let me browse files in an external hard drive for upload. Currently,
  when I try to browse a file from an external hard drive, it'll say
  "permission denied".

  Even this interface isn't auto-connected, a person that needs it
  should be able to grant it.

  $ snap list
  Name  Version  Rev   Tracking  Developer  Notes
  chromium  65.0.3325.181277   stablecanonical  -
  core  16-2.32.54486  stablecanonical  core
  spotify   1.0.77.338.g758ebd78-41  13stablespotify-

  $ snap interfaces chromium
  Slot   Plug
  :browser-support   chromium:browser-sandbox,spotify
  :camerachromium
  :cups-control  chromium
  :desktop   chromium,spotify
  :gsettings chromium,spotify
  :home  chromium,spotify
  :mount-observe chromium
  :network   chromium,spotify
  :network-manager   chromium
  :openglchromium,spotify
  :password-manager-service  chromium
  :pulseaudiochromium,spotify
  :screen-inhibit-controlchromium
  :unity7chromium,spotify
  :upower-observechromium
  :x11   chromium,spotify

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

  $ LC_ALL=C apt policy snapd
  snapd:
Installed: 2.32.5+18.04
Candidate: 2.32.5+18.04
Version table:
   *** 2.32.5+18.04 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1769388] Re: Unable to install package # 66.5159: dependency problems - leaving unconfigured

[antonio balentinu]

I removed the problematic library and I have not had any problems for now. We 
will see with the subsequent updates how everything will work.
#  sudo apt remove libp11-kit-gnome-keyring

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

Title:
  Unable to install package # 66.5159: dependency problems - leaving
  unconfigured

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Unable to install package 
/tmp/apt-dpkg-install-hCWHsS/0412-libp11-kit-gnome-keyring_3.280.2-1ubuntu1_all.deb
  # 66.5159: dependency problems - leaving unconfigured
  I UPDATED FROM UBUNTU 17.10 TO UBUNTU 18.04 AND I HAVE BEEN REPORTED TO THE 
BUG TO MAKE ITEM WITH
   # 66.5159 WHAT DO YOU TELL ME?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 19:35:12 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  InstallationDate: Installed on 2010-11-27 (2716 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LD_PRELOAD=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Dustin Krysak]

For myself, it is happening much less frequently. I have only had it
once since the final release. I'm curious if there is pattern here with
upgrades vs fresh install. (I was a fresh install).

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

Title:
  Keyboard shortcuts not operational on 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Beavis]

So pascal based gpu cant be turned of because powermanagment for nouveau
is broken and disabled? And the loaded nouveau driver is causing freezes
and slow down and instabilities?

Is there a workaround? Or does Ubuntu 18.04 break every laptop with an
pascal gpu.

-- 
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 1632027] Re: New Document feature missing from Nautilus 3.20+

[林博仁]

I have filed the bug to GNOME upstream:
https://gitlab.gnome.org/GNOME/nautilus/issues/407

Unfortunately currently Launchpad doesn't support GitLab issues so it
can't be directly linked to this bug report.

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

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  https://bazaar.launchpad.net/~ubuntu-
  desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[antonio balentinu]

As Shomz I removed the problematic library and I have not had any
problems for now. We will see with the subsequent updates how everything
will work.

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

[Amir]

Correction - after two restarts switching back and forth, the output is
as follows:

sudo cat /sys/kernel/debug/vgaswitcheroo/switch 
0:IGD:+:Pwr::00:02.0
1:DIS: :Off::01:00.0

-- 
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 1769495] [NEW] [snap] Chromium snap should ask for "removable-media" interface

[Ratchanan Srirattanamet]

Public bug reported:

This will helps people that keep lots of files on the external hard
drive (for example). If I understand correctly, this interface should
let me browse files in an external hard drive for upload. Currently,
when I try to browse a file from an external hard drive, it'll say
"permission denied".

Even this interface isn't auto-connected, a person that needs it should
be able to grant it.

$ snap list
Name  Version  Rev   Tracking  Developer  Notes
chromium  65.0.3325.181277   stablecanonical  -
core  16-2.32.54486  stablecanonical  core
spotify   1.0.77.338.g758ebd78-41  13stablespotify-

$ snap interfaces chromium
Slot   Plug
:browser-support   chromium:browser-sandbox,spotify
:camerachromium
:cups-control  chromium
:desktop   chromium,spotify
:gsettings chromium,spotify
:home  chromium,spotify
:mount-observe chromium
:network   chromium,spotify
:network-manager   chromium
:openglchromium,spotify
:password-manager-service  chromium
:pulseaudiochromium,spotify
:screen-inhibit-controlchromium
:unity7chromium,spotify
:upower-observechromium
:x11   chromium,spotify

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

$ LC_ALL=C apt policy snapd
snapd:
  Installed: 2.32.5+18.04
  Candidate: 2.32.5+18.04
  Version table:
 *** 2.32.5+18.04 500
500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [snap] Chromium snap should ask for "removable-media" interface

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This will helps people that keep lots of files on the external hard
  drive (for example). If I understand correctly, this interface should
  let me browse files in an external hard drive for upload. Currently,
  when I try to browse a file from an external hard drive, it'll say
  "permission denied".

  Even this interface isn't auto-connected, a person that needs it
  should be able to grant it.

  $ snap list
  Name  Version  Rev   Tracking  Developer  Notes
  chromium  65.0.3325.181277   stablecanonical  -
  core  16-2.32.54486  stablecanonical  core
  spotify   1.0.77.338.g758ebd78-41  13stablespotify-

  $ snap interfaces chromium
  Slot   Plug
  :browser-support   chromium:browser-sandbox,spotify
  :camerachromium
  :cups-control  chromium
  :desktop   chromium,spotify
  :gsettings chromium,spotify
  :home  chromium,spotify
  :mount-observe chromium
  :network   chromium,spotify
  :network-manager   chromium
  :openglchromium,spotify
  :password-manager-service  chromium
  :pulseaudiochromium,spotify
  :screen-inhibit-controlchromium
  :unity7chromium,spotify
  :upower-observechromium
  :x11   chromium,spotify

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

  $ LC_ALL=C apt policy snapd
  snapd:
Installed: 2.32.5+18.04
Candidate: 2.32.5+18.04
Version table:
   *** 2.32.5+18.04 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+

[林博仁]

Affected to Ubuntu 18.04 as well, it's weird such basic feature doesn't
exist in upstream GNOME in the first place...

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  https://bazaar.launchpad.net/~ubuntu-
  desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Liam McDermott]

The fix mentioned in #1767468 did not fix this for me (AMD Radeon 7950).
Also installing libegl-mesa0 does not fix the issue.

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1129144] Re: Background can not be clicked in Files (Nautilus) 3.6.3, in listview mode

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  Background can not be clicked in Files (Nautilus) 3.6.3, in listview
  mode

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In listview mode, Nautilus does not allow clicking on background, when
  browsing a folder with more files than a single page.

  This must be classified as a bug because:
  1. Background click is necessary to unselect a file;
  2. Background click is available in iconview mode, so it is a doubtful 
behavior;
  3. Users are accustomed to access context menu right clicking background in 
order to create folder, share folder, create file, etc;
  4. Files can't be dragged & dropped into current folder.

  Furthermore, it is a kind of regression, since this error has been
  corrected in a earlier version.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Mon Feb 18 11:04:34 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+296+84'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'173'
  InstallationDate: Installed on 2013-02-17 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130208)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Park Ju Hyung]

I've been able to get a workaround for this issue.

I was using compiz(Unity) on my Ubuntu 18.04.
While GNOME seems to be fine, it looks like compiz is causing a race-condition 
with another process.

A workaround is to delay compiz launch for a few seconds.

Open up /usr/lib/systemd/user/unity7.service and add
ExecStartPre=/bin/sleep 2
before
ExecStart=/usr/bin/compiz

If this doesn't work, try increasing 2 to 3 or maybe 5.

This is a very dirty workaround and I'd like to see some real solutions,
but since compiz and Unity's development is pretty much banned,

I'm not sure if it'll ever get a fix.

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

Title:
  Keyboard shortcuts not operational on 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1683512] Re: No libcuda.so.1 after upgrading to 381-driver

[Rebecca Palmer]

('invalid' as in 'not our (theano's) bug')

Where did you obtain nvidia-381 (Ubuntu itself went straight from -375
to -384)? the Nvidia website? a PPA?

nvidia-graphics-drivers-384 is now available in xenial-updates: is that
any better?

(libcudata.so.8 is probably a different library, not the file you want.)

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

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

Title:
  No libcuda.so.1 after upgrading to 381-driver

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in theano package in Ubuntu:
  Invalid

Bug description:
  I had a problem with window edges after waking from suspend - see
  here: https://askubuntu.com/questions/896221/strange-artifacts-along-
  window-borders-after-waking-computer-from-sleep-mode/

  For this reason I upgraded to the newer driver, from 375.39 to 381.09.

  I have posted this question on AskUbuntu, with some extra information!
  
https://askubuntu.com/questions/905993/missing-libcuda-so-1-file-after-upgrading-to-newest-nvidia-driver

  Since upgrading, I have had to reinstall the Cuda Toolkit 8.0 (and CUDNN 
v5.1), however there seems to be a driver file missing, which prevents me from 
installing both Tensorflow and the gputools package in R, which build upon the 
Cuda Toolkit, which in turn needs the missing libcuda.so.1 file.
  Neither Tensorflow no gputools are able to locate the file: libcuda.so.1.
  Here is a similar issue, but with older drivers involved:  
https://github.com/tensorflow/tensorflow/issues/4078

  I have read that I could possibly create this file as it is a symlink, 
however I would prefer not to, as I do not know what other dependencies exist.
  Example of possible workaround:   
http://stackoverflow.com/questions/41890549/tensorflow-cannot-open-libcuda-so-1

  I am running Ubuntu 16.04.

  Can somebody see why this file is missing or propose a stable
  solution?

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

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

[Desktop-packages] [Bug 1710421] Re: Keyboard accelerators for window menus aren't implemented

[Norbert]

It is unbelievable, Ubuntu 18.04 LTS is released with this bug.
I can't understand for whom you are designing you smart new glossy desktop.

** Tags removed: gnome-17.10 wayland-session
** 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/1710421

Title:
  Keyboard accelerators for window menus aren't implemented

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

Bug description:
  Description from duplicate bug 1725706:

  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Login to the default Ubuntu session
  3. Open any windowed application such as Nautilus or `gnome-terminal`
  3. Click  to show current window settings
  4. Try to set "Always on Top" property with keyboard shortcut ()

  Expected results:
  * window reacts on  and set on top as requested

  Actual results:
  * window does not react on 

  Notes:
  "Always on Top" is just an illustration. Mnemonics for other (Minimize, 
Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, 
etc) do not defined and do work too.

  
  Original description below:

  Other desktop systems including Microsoft Windows and Unity have
  accelerator keys in the window menu. This is typically accessible via
  ALT_Space on any window, then pressing a key to initiate the desired
  function.

  Typically Alt_Space can be used to bring up the menu, then use x to
  maximise a window, n to minimise a window, etc. GNOME Shell does not
  implement these accelerator keys, which seems inconsistent with other
  desktops, and internally inconsistent, as other menus in GNOME
  applications _do_ have accelerator keys.

  It would be great for people coming to GNOME Shell should be able to
  use the familiar keyboard shortcuts they're used to.

  As far as I can test (as far back as 16.04) this has always been the
  case.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 22:49:46 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-02 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1710421/+subscriptions

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

[Desktop-packages] [Bug 152279] Re: Totem gets aspect ratio wrong

[Václav Šmilauer]

This bug is 11 years old by now. Totem is the default movie player for
Ubuntu and this deserves proper attention.

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

Title:
  Totem gets aspect ratio wrong

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: totem

  I use a pivot monitor. When I rotate the screen with xrandr -o left or
  Grandr, totem gets the aspect ratio wrong. For instance a 4:3 film is
  shown as 3:4, that means higher than wide. It is also not possible to
  correct the aspect ratio from the GUI menu. New video thumbnails are
  also distorted, however in the other direction: They become much wider
  than hig.

  Kaffeine shows the same buggy behaviour as Totem, while VLC doesn't.
  VLC gets the aspect ratio right. This bug was also not there in
  Feisty.

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Park Ju Hyung]

I'm also experiencing the exact same issues.

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

Title:
  Keyboard shortcuts not operational on 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Amir]

This bug was not fixed. It still affects me. The GPU doesn't go off, so
the power consumption remains pretty high (and the fan keeps on going).

-- 
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 1769372] Re: Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Norbert]

I posted my analysis in AskUbuntu question (
https://askubuntu.com/q/1032461/66509 ) .

Currently I can state that in terminal session aka `multi-user.target`
(`systemctl isolate multi-user.target`) all variables from
*/etc/systemd/logind.conf* are sourced normally. So the problem is with
GNOME session (`systemctl isolate graphical.target`) in `gnome-settings-
daemon` or something other.

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

Title:
  Ubuntu 18.04 LTS does not ask for action when I press ACPI Power
  button/key - immediately shutdowns

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

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

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+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 1769416] Re: Can't login on 18.04 after entering wrong password

[Gunnar Hjalmarsson]

** Package changed: lightdm (Ubuntu) => gdm3 (Ubuntu)

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

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

Title:
  Can't login on 18.04 after entering wrong password

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Hello,

  so I just installed Ubuntu 18.04LTS on my computer ( HP Spectre x360
  15 ), running in dual boot mode with windows 10, everything went well
  during the installation, the only problem I encountered is, if I type
  a wrong password and then I type the correct password, the desktop
  never loads... I waited like 20 minutes if anything would show up, but
  nothing, I can just see the cursor and the wallpaper nothing else, I
  had to manually turn off/on the computer multiple times, in order to
  see the boot manager again.

  If I enter the correct password at the first attempt,  the desktop
  loads and everything works just fine.

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

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

[Desktop-packages] [Bug 1769348] Re: libfreerdp does not support h264

[Launchpad Bug Tracker]

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

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

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

Title:
  libfreerdp does not support h264

Status in freerdp2 package in Ubuntu:
  Confirmed

Bug description:
  am on ubuntu 18.04  upgraded from  16.04

  now am seeing this bug on 18.04 only

  earlier i had no problem with color depth using remmina.

  
  could you please upgrade freerdp to support h264 mode.

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

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

[Desktop-packages] [Bug 1768678] Re: regional settings are far too restrictive

[Launchpad Bug Tracker]

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

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

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

Title:
  regional settings are far too restrictive

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

Bug description:
  Settings --> Region & Language --> Formats

  Allows me to select the country, not set the actual format.us
  I live in the US, so this means that I am stuck with

  date: mm/dd/
  time: HH:MM:SS AM/PM
  date:  the weird format which somehow starts with week and ends with 
am/pm
  numbers: 123,456,789.00
  measurements: imperial
  paper: us letter

  basically, since all paper is always "letter", no other country selection 
will work for me.
  however, I don't see why I have to be stuck with the US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units - not "imperial") 
and "infix" date/time formats.

  I could set date and time formats to ISO 8601 for the last 10 years at least, 
and still can do it on Mac.
  This appears to be a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 18:41:18 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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-control-center/+bug/1768678/+subscriptions

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

[Desktop-packages] [Bug 1769348] Re: libfreerdp does not support h264

[HUsam]

Having the same problem here too, I upgraded from 17.10.

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

Title:
  libfreerdp does not support h264

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  am on ubuntu 18.04  upgraded from  16.04

  now am seeing this bug on 18.04 only

  earlier i had no problem with color depth using remmina.

  
  could you please upgrade freerdp to support h264 mode.

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

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

[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list

[bugrasan]

$ sudo apt-get install fonts-symbola
solves the problem, origin: 
https://ubuntu-mate.community/t/thunderbird-with-huge-icons-emoticons-mate-18-04/16249/25

therefore the thunderbird package should depend on 'fonts-symbola'.

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

Title:
  Very large emojis displayed in subject line and in the email list

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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