[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list

[Wal]

The fix by bugrasan works OK and gets the emojis down to normal size
however the emoji's are no longer colour but black and white. This is at
least a good workaround for the time being.

I think you will find this problem will be fixed in a later version of
Thunderbird. I downloaded Thunderbird 60 Beta tar.bz2 from their
website. Without actually installing it I extracted the folder and ran
that version of Thunderbird from within that folder. It will
automatically pick up you settings and email addresses etc from the
version you have installed.

It worked fine and the emojis contained in this version of Thunderbird
are of normal size and are coloured.

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

[Desktop-packages] [Bug 986716] Re: Orca doesn't read the ubiquity promotional slides

[Launchpad Bug Tracker]

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

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

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

Title:
  Orca doesn't read the ubiquity promotional slides

Status in gnome-orca package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Expired

Bug description:
  Release of Ubuntu: Ubuntu precise, 12.04
  Package Version: ubiquity 2.10.16, gnome-orca 3.4.0-0ubuntu2
  Expected Results: Orca should read the promotional slides while the 
installation is on progress
  Actual Results: Orca only keeps track of the percentage of the installation

  Probably the ubiquity slides are images, which explains why orca
  doesn't read them, it also doesn't explain in what step of the
  installation it's working, for example when copying file, it shouts
  the percentage, and when starts repartitioning, or installing others
  packages the percentage reading is reset and gives no clue about why
  it happened or in what part of the installation it is.

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

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

[Desktop-packages] [Bug 986716] Re: Orca doesn't read the ubiquity promotional slides

[Launchpad Bug Tracker]

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

** Changed in: gnome-orca (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Orca doesn't read the ubiquity promotional slides

Status in gnome-orca package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Expired

Bug description:
  Release of Ubuntu: Ubuntu precise, 12.04
  Package Version: ubiquity 2.10.16, gnome-orca 3.4.0-0ubuntu2
  Expected Results: Orca should read the promotional slides while the 
installation is on progress
  Actual Results: Orca only keeps track of the percentage of the installation

  Probably the ubiquity slides are images, which explains why orca
  doesn't read them, it also doesn't explain in what step of the
  installation it's working, for example when copying file, it shouts
  the percentage, and when starts repartitioning, or installing others
  packages the percentage reading is reset and gives no clue about why
  it happened or in what part of the installation it is.

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

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

[Desktop-packages] [Bug 986716] Re: Orca doesn't read the ubiquity promotional slides

[Launchpad Bug Tracker]

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

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

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

Title:
  Orca doesn't read the ubiquity promotional slides

Status in gnome-orca package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Expired

Bug description:
  Release of Ubuntu: Ubuntu precise, 12.04
  Package Version: ubiquity 2.10.16, gnome-orca 3.4.0-0ubuntu2
  Expected Results: Orca should read the promotional slides while the 
installation is on progress
  Actual Results: Orca only keeps track of the percentage of the installation

  Probably the ubiquity slides are images, which explains why orca
  doesn't read them, it also doesn't explain in what step of the
  installation it's working, for example when copying file, it shouts
  the percentage, and when starts repartitioning, or installing others
  packages the percentage reading is reset and gives no clue about why
  it happened or in what part of the installation it is.

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

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

[Desktop-packages] [Bug 1733707] Re: Ambiance/Radiance: add styling for mate-panel

[Launchpad Bug Tracker]

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

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

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

Title:
  Ambiance/Radiance: add styling for mate-panel

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  Both themes look odd in MATE Desktop. Consider adding specific styling
  for mate-panel, like gnome-panel.

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

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

[Desktop-packages] [Bug 549629] Re: Feature request: Graphical method to mount selected drives within an encrypted LVM (made by altrnate installer)

[Launchpad Bug Tracker]

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

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

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

Title:
  Feature request: Graphical method to mount selected drives within an
  encrypted LVM (made by altrnate installer)

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Binary package hint: nautilus

  This bug is a request for a graphical method to mount selected drives
  within an encrypted LVM (made by alternate installer).

  What currently happens with LVM is that it is shown as two drives. One
  contains all the /boot file and is unprotected. The other (which is
  larger) contains my root drive (/) and my swap which are both
  encrypted.

  Nautilus presents it as:
  X.X GB Encrypted

  You can see this on the side pane or on the places menu, however, you
  cannot mount it from nautilus. This improvement should only affecting
  a LVM disk when booting from another disk (not when it is itself
  mounted and used as the system). More on that in Bug #441211 - Do not
  show LUKS devices of internal mounted disks.

  Currently what happens when clicking on the disk is the following
  error message shows up:

  Unable to mount X.X GB Encrypted
  Error starting job: Failed to execute child process "cryptsetup" (No such 
file or directory)

  
  What I expect, or would like to happen:
  When booting from a disk other then the one which is LVM setup (such as 
another partition, usb, Live CD), you would be presented with X.X GB Encrypted. 
Once you unlock the LVM, all the drives within it (with filesystems capable of 
being mounted) would be presented in the nautilus. The user can then select 
individual drives to mount them.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.29.92.1-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sat Mar 27 11:03:05 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 1179751] Re: Nautilus image folders cannot be used until thumbnailing is complete

[Launchpad Bug Tracker]

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

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

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

Title:
  Nautilus image folders cannot be used until thumbnailing is complete

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have lots of folders with images and of course, I use the file list
  with thumbnails. It would be great, but I cannot do any file operation
  because the file thumbnails have a different size and modify each
  line's height, so my files go down. See the attached movie for
  details.

  Each file should have a pre-determined max-height & max-width
  rectangle/square and the preview should always fit to that rectangle.
  Then, no matther the images are landscape or portrait, they will fit
  and this problem dissapears.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 04:37:53 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'808x550+49+24'"
  InstallationDate: Installed on 2013-04-25 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1121073] Re: Nautilus is not showing [encrypted] units after unmount

[Launchpad Bug Tracker]

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

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

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

Title:
  Nautilus is not showing [encrypted] units after unmount

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have an encrypted SD-card connected to my laptops card reader. After
  boot I start Nautilus and I can see the unit in the unit list, it is
  not mounted. I click on it to mount it and give the password with
  option Remind password for session, I then copy some files to it and
  the press the eject button to the right of it. Nautilus shuts down the
  active window. Later I want to copy some more files to it, so I start
  Nautilus again but the unit is not visible this time. I can see the
  SD-card in Disks but I cannot mount it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 10 12:19:34 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+118+75'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'193'
  InstallationDate: Installed on 2012-11-22 (79 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2012-11-22T15:57:26.024721

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

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

[Desktop-packages] [Bug 1084204] Re: Unmount message is not displayed

[Launchpad Bug Tracker]

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

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

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

Title:
  Unmount message is not displayed

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When writing to external USB devices (e.g., USB sticks or USB HDD),
  the write progress bar is displayed correctly. After the write
  progress bar is full and the progress window stops displaying, the
  status light of the device signals, that still data is written to the
  device. Previously, when you pressed the unmount button in nautilus, a
  window apeared and displayed a warning not to remove the device. Since
  about two weeks, this warning message is not displayed any more. When
  removing the device before the write cache is empty, the filesystem of
  the device is corrupted on the next mount. This behaviour is
  reproducable and occurs every time. It also happens on other
  installation of 12.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 28 20:03:37 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'917x683+65+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-11-13 (15 days ago)

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

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

[Desktop-packages] [Bug 1229303] Re: Regional settings (date format) is ignored

[Launchpad Bug Tracker]

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

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

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

Title:
  Regional settings (date format) is ignored

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  please see screenshot.
  Nautilus soes not use chosen date format.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 19:09:32 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1530x896+1920+155'"
  InstallationDate: Installed on 2013-04-02 (173 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago)

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

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

[Desktop-packages] [Bug 1760411] Re: I don know

[Launchpad Bug Tracker]

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

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

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

Title:
  I don know

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i don know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr  1 16:29:14 2018
  DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c1]
  InstallationDate: Installed on 2018-03-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: HP
  dmi.board.version: 96.51
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Mar 31 13:56:55 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1774757] Re: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from

[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 graphite2 in Ubuntu.
https://bugs.launchpad.net/bugs/1774757

Title:
  package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz',
  which is different from other instances of package libgraphite2-3:i386

Status in graphite2 package in Ubuntu:
  New

Bug description:
  everytime i turn on my pc it shows the error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgraphite2-3 1.3.11-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Jun  2 09:52:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libgraphite2-3:1.3.11-2
   Unpacking libgraphite2-3:i386 (1.3.11-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  InstallationDate: Installed on 2018-05-24 (8 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: graphite2
  Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1774757] [NEW] package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different fro

[Robert John P. Canare]

Public bug reported:

everytime i turn on my pc it shows the error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgraphite2-3 1.3.11-2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat Jun  2 09:52:02 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libgraphite2-3:1.3.11-2
 Unpacking libgraphite2-3:i386 (1.3.11-2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
InstallationDate: Installed on 2018-05-24 (8 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: graphite2
Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz',
  which is different from other instances of package libgraphite2-3:i386

Status in graphite2 package in Ubuntu:
  New

Bug description:
  everytime i turn on my pc it shows the error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgraphite2-3 1.3.11-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Jun  2 09:52:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libgraphite2-3:1.3.11-2
   Unpacking libgraphite2-3:i386 (1.3.11-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  InstallationDate: Installed on 2018-05-24 (8 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: graphite2
  Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759119] Re: gnome-shell crashed with signal 5

[Launchpad Bug Tracker]

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

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

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

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  just report bug, when ubuntu boot have bug aport.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 27 09:25:31 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-07 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1774751] [NEW] mouse

[Ismaila Jallow]

Public bug reported:

my mouse is malfunctioning

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
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: Sat Jun  2 01:09:52 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1962]
InstallationDate: Installed on 2018-04-18 (44 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP ENVY 15 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=8f0b1c00-fce6-4eb9-af73-8b962be4d947 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.66
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1962
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 93.52
dmi.chassis.asset.tag: 5CG414D6R1
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr098211405E032:rvnHewlett-Packard:rn1962:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY 15 Notebook PC
dmi.product.version: 098211405E032
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Jun  2 01:05:34 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  my mouse is malfunctioning

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Sat Jun  2 01:09:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1962]
  InstallationDate: Installed on 2018-04-18 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP ENVY 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=8f0b1c00-fce6-4eb9-af73-8b962be4d947 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1962
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 

[Desktop-packages] [Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

[beatmaggy]

gnome-shell[1493]: segfault at 20 ip 7fe7ecafeb17 sp
7fff5e70ba60 error 4 in libmutter-2.so.0.0.0[7fe7eca11000+156000]

I have this exact segfault too. I’m on a cherry trail atom z8350. 
Previously this segfault didn’t occur and the system went to suspend and it 
could be brought up via keyboard. 
I didn’t want it to suspens so changed the suspend settings which didn’t change 
anything. 
Suspend still occurred every 5 min. 

So I did disabled suspend via the command line through systemctl.
Then the libmitter2 segfault kept occurring and eventually made the system run 
out of memory. 

I’ll try and get a core dump if it’s available. But my problem is the 
libmitter2 segfault. 
I thought 18.04 defaults to xorg. Why is libmitter2 even segfaulting???

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

Title:
  Segfault in libmutter-2.so after suspend/resume using wayland. Core
  files are always truncated and invalid while the default shell is zsh.

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

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
  Mai 22 13:11:15 x1 kernel: OOM killer disabled.
  Mai 22 13:11:15 x1 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  Mai 22 13:11:15 x1 kernel: Suspending console(s) (use no_console_suspend to 
debug)
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unknown possible thermal alarm or 
keyboard event received
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unhandled HKEY event 0x6032
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: please report the conditions when 
this event happened to ibm-acpi-de...@lists.sourceforge.net
  Mai 22 13:11:15 x1 kernel: [drm] GuC: Loaded firmware 
i915/kbl_guc_ver9_39.bin (version 9.39)
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC firmware version 9.39
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC submission enabled
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: HuC disabled
  Mai 22 13:11:15 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: OOM killer enabled.
  Mai 22 13:11:15 x1 kernel: Restarting tasks ... done.
  Mai 22 13:11:15 x1 systemd-logind[986]: Lid opened.
  Mai 22 13:11:15 x1 kernel: rfkill: input handler enabled
  Mai 22 13:11:15 x1 systemd[1]: Started Run anacron jobs.
  Mai 22 13:11:15 x1 anacron[2420]: Anacron 2.3 started on 2018-05-22
  Mai 22 13:11:15 x1 anacron[2420]: Normal exit (0 jobs run)
  Mai 22 13:11:15 x1 kernel: thermal thermal_zone6: failed to read out thermal 
zone (-61)
  Mai 22 13:11:15 x1 tilix[1980]: Error reading events from display: Broken pipe
  Mai 22 13:11:15 x1 update-notifier[1901]: Error reading events from display: 
Broken pipe
  Mai 22 13:11:15 x1 systemd-sleep[2349]: System resumed.
  Mai 22 13:11:15 x1 kernel: PM: suspend exit
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: Fatal server error:
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE) failed to read Wayland 
events: Broken pipe
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 systemd[1]: Started Suspend.
  Mai 22 13:11:15 x1 systemd[1]: sleep.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Sleep.
  Mai 22 13:11:15 x1 systemd[1]: Reached target Suspend.
  Mai 22 13:11:15 x1 systemd[1]: suspend.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Suspend.
  Mai 22 13:11:15 x1 gnome-session[1455]: gnome-session-binary[1455]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

[Michael Schumacher]

The upstream bug tracker changed from bugzilla.gnome.org to
gitlab.gnome.org. All those recent Expired changes are bogus.

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Expired
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1774744] [NEW] Impossible to select files with long names in order

[Miikka-Markus Alhonen]

Public bug reported:

Selecting files with long filenames using Shift and arrow keys causes
nautilus in icon view not to advance sequentially or not to advance at
all. Here's a test case:

1) Create a new folder and create empty files with long names in it
using the command:

for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 
27 28 29 30 31 32 33 34 35 36 37 38 39 40; do touch "abcdef ghijklmn 
opqrstuvwxyz ABCDEF GHIJKLMN OPQRSTUVWXYZ$i.txt"; done
 
2) Open the folder in nautilus, hold Shift down and start selecting files by 
pressing the right arrow key.

Everything goes fine up to the end of the first row. However, when you
reach the first file on the second row and press the arrow key again
(still holding Shift down), the selection jumps back to the second file
of the first row. If you keep on pressing the arrow key, it will repeat
the process over and over. So by pressing the right arrow key, you can
never reach the end of the folder. As a user, I would expect nautilus to
progress sequentially to the second file of the second row and so on up
to the end of the folder.

In the example, I used default font settings and 50 % zoom.

Description:Ubuntu 18.04 LTS
Release:18.04

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

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  1 23:06:09 2018
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'search-view' b"'icon-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'203'
 b'org.gnome.nautilus.window-state' b'geometry' b"'888x580+117+77'"
InstallationDate: Installed on 2017-02-13 (473 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to bionic on 2018-05-31 (1 days ago)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

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

Title:
  Impossible to select files with long names in order

Status in nautilus package in Ubuntu:
  New

Bug description:
  Selecting files with long filenames using Shift and arrow keys causes
  nautilus in icon view not to advance sequentially or not to advance at
  all. Here's a test case:

  1) Create a new folder and create empty files with long names in it
  using the command:

  for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 
27 28 29 30 31 32 33 34 35 36 37 38 39 40; do touch "abcdef ghijklmn 
opqrstuvwxyz ABCDEF GHIJKLMN OPQRSTUVWXYZ$i.txt"; done
   
  2) Open the folder in nautilus, hold Shift down and start selecting files by 
pressing the right arrow key.

  Everything goes fine up to the end of the first row. However, when you
  reach the first file on the second row and press the arrow key again
  (still holding Shift down), the selection jumps back to the second
  file of the first row. If you keep on pressing the arrow key, it will
  repeat the process over and over. So by pressing the right arrow key,
  you can never reach the end of the folder. As a user, I would expect
  nautilus to progress sequentially to the second file of the second row
  and so on up to the end of the folder.

  In the example, I used default font settings and 50 % zoom.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 23:06:09 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'search-view' b"'icon-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'203'
   b'org.gnome.nautilus.window-state' b'geometry' b"'888x580+117+77'"
  InstallationDate: Installed on 2017-02-13 (473 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: nautilus
  

[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list

[Jeff Van Epps]

Is there (going to be) a solution which is a preference for "don't show
emoji in subject line"? I hardly ever understand them anyway. I'm a
grumpy old man who learned to read English 50+ years ago and I'd just
prefer to stick with text only. (unchecking Preferences / Display /
Display emoticons as graphics (under Plain Text Messages) doesn't have
any effect on this)

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

[Desktop-packages] [Bug 1393502] Re: [MacBookPro11, 3, Cirrus Logic CS4208, Pink Mic] Combo jack not recognized.

[EdSena]

having the same issue on a Macbook Air 7,2 on a fresh 18.04 install

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

Title:
  [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic] Combo jack not
  recognized.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New Macbook comes with a four-conductor TRRS jack for headset.

  With headset plugged in the microfone is recognized on Mac os-x.
  Ubuntu recognizes the external headphones but not the microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mikaelb2403 F pulseaudio
   /dev/snd/controlC0:  mikaelb2403 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:58:35 2014
  InstallationDate: Installed on 2014-10-20 (28 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Pink Mic, N/A
  Symptom_Type: No auto-switch between inputs
  Title: [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic, N/A] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-11-10T22:25:45.211791

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

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

[Tim Richardson]

Matthieu's code is the best solution I've seen, as long as you are ok with 
lightdm.
The multi-dispatch aspects of the new module are a good simplification, 
Matthieu's approach looks like it's now easy to switch between intel and hybrid 
modes; he just blacklists modules.

Dear maintainers, it seems a shame to stop using bbswitch, the cause of
all the functional and user-experience regressions of the new package.

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

[gene_wood]

For anyone looking for how to use this fix with the current Ubuntu 18.04
installation ISO, this page ( https://askubuntu.com/a/1040322/14601 )
has a good description how to use the patch produced above in Comment
37.

-- 
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:
  Fix Released
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 

[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Christopher M. Penalver]

Log in to Ubuntu (i.e. GNOME xorg) > double click
GS5007-GettingStartedWithDraw.odt > click Edit > Track Changes > Compare
Document... > highlight GS4207-GettingStartedWithDraw.odt > click button
Open > in window Manage Changes click button Close > File > Save As... >
in textbox Name GS5007-GettingStartedWithDraw-v2 > click button Save >
window pops up titled LibreOffice 6.0 Document Recovery with text "Due
to an unexpected error, LibreOffice crashed." but no files in /var/crash
generated by apport. However, apport does create crash files following
steps in
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/comments/7
so crash files not being being generated is dependent how LO crashes,
not always if LO crashes.

** Attachment added: "no-apport-crash-files-generated.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147686/+files/no-apport-crash-files-generated.PNG

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

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  

[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Christopher M. Penalver]

2 of 2 reproduction documents for Bionic.

** Attachment added: "GS4207-GettingStartedWithDraw.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147685/+files/GS4207-GettingStartedWithDraw.odt

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  

[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Christopher M. Penalver]

1 of 2 reproduction documents for Bionic.

** Attachment added: "GS5007-GettingStartedWithDraw.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147684/+files/GS5007-GettingStartedWithDraw.odt

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  

[Desktop-packages] [Bug 1646378] Re: Does not clear its user interface when it finishes

[Thomas Dickey]

Read the manual page description of "--keep-tite"

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

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

Title:
  Does not clear its user interface when it finishes

Status in dialog package in Ubuntu:
  Invalid

Bug description:
  This is unlike whiptail, which clears its UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dialog 1.2-20130928-1
  ProcVersionSignature: Ubuntu 4.4.0-51.72~14.04.1-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec  1 09:27:46 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (801 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: dialog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1774447] Re: Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04

[stan383]

Well, after uninstalling xserver-xorg-input-synaptics it seems to be
working fine. At least short testing looks promising. Bud bad is two-
finger scrolling stopped working. I can only switch to edge scrolling,
which works, but when two-finger scrolling is enabled, it does not work.

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

Title:
  Approx. 50% of tap to clicks does not work since upgrade to Ubuntu
  18.04

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Since upgrade from Ubuntu 17.10 to Ubuntu 18.04 I have issues with tap
  to click. Approximately 50% of taps does not work as clicks. I do not
  know if it is general issue or an issue related to my HW (Lenovo L450)
  but it is very annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.10.4-1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 17:38:44 2018
  DistUpgraded: 2018-05-04 10:19:30,946 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:503c]
  InstallationDate: Installed on 2015-10-05 (968 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20DT0003XS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=0ff426ff-3b6c-433c-81a3-8a8a4116c973 ro
  SourcePackage: libinput
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (27 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET57WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET57WW(1.19):bd03/16/2016:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L450
  dmi.product.name: 20DT0003XS
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  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.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: Sat Jan 20 21:06:39 2018
  xserver.configfile: default
  xserver.errors:
   Error loading keymap /var/lib/xkb/server-0.xkm
   Error loading keymap /var/lib/xkb/server-0.xkm
   XKB: Failed to load keymap. Loading default keymap instead.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.19.3-1ubuntu1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1774447/+subscriptions

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

[Desktop-packages] [Bug 1772425] Re: ODT document crashes when you open it in Writer

[Christopher M. Penalver]

Olivier Tilloy, would you have any insight on why this might not be
fixed in later versions of libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1?

I'm not able to generic keyword search the Ubuntu Error Tracker via
browser to do quick searches against just LibreOffice, and glancing at
ranked "Occurences" list for LibreOffice doesn't ring my warning bells.

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

Title:
  ODT document crashes when you open it in Writer

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  The attached document makes LibreOffice Writer crash immediately after
  opening it, along with the following error message:

  *** Error in `/usr/lib/libreoffice/program/soffice.bin':
  munmap_chunk(): invalid pointer: 0x55794428ad40 ***

  I created this ODT file by converting a Word document with Writer;
  "file" tells me the original was "Composite Document File V2 Document,
  Little Endian, Os: Windows, Version 5.0, Code page: -535, Template:
  Normal, Revision Number: 1, Name of Creating Application: Microsoft
  Word 10.0".

  The original document, which was sent to me by somebody else,
  contained parts which seemed to work fine but when I reached the end
  of the file, Writer crashed. This modified ODT version I'm attaching
  only contains the part which makes the program crash. The document is
  written in Arabic, in case it makes any difference.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 14:09:36 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.utf-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

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

[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Brian Murray]

I was unable to recreate this on bionic.

[ 11:31AM 10096 ]  [ bdmurray@impulse:~ ]
 $ pkill -11 lowriter
[  1:07PM 10113 ]  [ bdmurray@impulse:~ ]
 $ ls /var/crash/
_bin_cat.2001.uploaded
_bin_cat-kylin.uploaded
crash-in-postinst.0.uploaded
_usr_bin_apport-cli.2001.uploaded
_usr_bin_apport-unpack.2001.uploaded
_usr_bin_gnome-calculator.2001.uploaded
_usr_bin_gnome-calculator-awesome.uploaded
_usr_bin_lowriter.1000.crash
_usr_bin_xeyes.2001.uploaded
_usr_lib_dconf_dconf-service.2001.uploaded

Do you have libreoffice installed as a package or as a snap on Ubuntu
18.04?

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

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 

[Desktop-packages] [Bug 1768976] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1768976

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02

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

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

[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02

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

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

[Desktop-packages] [Bug 1772425] Re: ODT document crashes when you open it in Writer

[Miikka-Markus Alhonen]

I did what you suggested and installed LibreOffice 6.0.3.2 together with
a full system update from Ubuntu 17.10 to 18.04. Now the document seems
to work fine. Thank you for your help!

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

Title:
  ODT document crashes when you open it in Writer

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  The attached document makes LibreOffice Writer crash immediately after
  opening it, along with the following error message:

  *** Error in `/usr/lib/libreoffice/program/soffice.bin':
  munmap_chunk(): invalid pointer: 0x55794428ad40 ***

  I created this ODT file by converting a Word document with Writer;
  "file" tells me the original was "Composite Document File V2 Document,
  Little Endian, Os: Windows, Version 5.0, Code page: -535, Template:
  Normal, Revision Number: 1, Name of Creating Application: Microsoft
  Word 10.0".

  The original document, which was sent to me by somebody else,
  contained parts which seemed to work fine but when I reached the end
  of the file, Writer crashed. This modified ODT version I'm attaching
  only contains the part which makes the program crash. The document is
  written in Arabic, in case it makes any difference.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 14:09:36 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.utf-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

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

[Desktop-packages] [Bug 1772425] Re: ODT document crashes when you open it in Writer

[Miikka-Markus Alhonen]

I did what you suggested and installed LibreOffice 6.0.3.2 together with
a full system update from Ubuntu 17.10 to 18.04. Now the document seems
to work fine. Thank you for your help!

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

Title:
  ODT document crashes when you open it in Writer

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  The attached document makes LibreOffice Writer crash immediately after
  opening it, along with the following error message:

  *** Error in `/usr/lib/libreoffice/program/soffice.bin':
  munmap_chunk(): invalid pointer: 0x55794428ad40 ***

  I created this ODT file by converting a Word document with Writer;
  "file" tells me the original was "Composite Document File V2 Document,
  Little Endian, Os: Windows, Version 5.0, Code page: -535, Template:
  Normal, Revision Number: 1, Name of Creating Application: Microsoft
  Word 10.0".

  The original document, which was sent to me by somebody else,
  contained parts which seemed to work fine but when I reached the end
  of the file, Writer crashed. This modified ODT version I'm attaching
  only contains the part which makes the program crash. The document is
  written in Arabic, in case it makes any difference.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 14:09:36 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.utf-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

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

[Desktop-packages] [Bug 1774244] Re: Rotated Arabic text is displaced in PDF when substitute glyphs are used

[Miikka-Markus Alhonen]

Sorry, for some reason, my browser seems to have submitted the same bug
report twice, as #1774243 and #1774244. All the relevant information,
including all the attachments are posted in this report, so I marked the
other report as a duplicate.

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

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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

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

[Desktop-packages] [Bug 1774243] Re: Rotated Arabic text is displaced in PDF when substitute glyphs are used

[Miikka-Markus Alhonen]

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

** This bug has been marked a duplicate of bug 1774244
   Rotated Arabic text is displaced in PDF when substitute glyphs are used

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

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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

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

[Desktop-packages] [Bug 1774635] Re: Xorg crashes - SIGABRT - after resuming from suspend

[Vlad Dinulescu]

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

Title:
  Xorg crashes - SIGABRT - after resuming from suspend

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In the last months, Xorg started crashing randomly after I resume from sleep. 
  I've installed Xubuntu 18.04 from scratch (keeping only the /home partition) 
hoping that the problem would be gone. But it isn't. 

  It seems to be related to the external monitor - ie when there is an
  external monitor plugged in and I suspend the computer, and when I
  resume there's only the laptop. But it doesn't always happen, so I
  don't have clear steps for reproducing.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Thu May 31 18:01:17 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1523633505
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e3]
  InstallationDate: Installed on 2018-05-22 (10 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=0da52507-c787-46d7-9266-d53448c18283 ro quiet splash vt.handoff=1
  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: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: 0
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  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-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1767715] Re: Laptop does not suspend after lid is closed on nvidia drivers

[Damian]

Same issue, works only the first time you suspend after reboot any time
after that it fails. (Laptop Lenovo T400)


sudo lshw -c video
*-display:0   
   description: VGA compatible controller
   product: Mobile 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 07
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:16 memory:f440-f47f memory:d000-dfff 
ioport:1800(size=8) memory:c-d
  *-display:1 UNCLAIMED
   description: Display controller
   product: Mobile 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 07
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:f420-f42f


systemd-inhibit --list
 Who: gdm (UID 121/gdm, PID 1125/gsd-power)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: GNOME Shell (UID 1000/damian, PID 1552/gnome-shell)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: damian (UID 1000/damian, PID 1696/gsd-media-keys)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: damian (UID 1000/damian, PID 1649/gsd-power)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: gdm (UID 121/gdm, PID 1122/gsd-media-keys)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: ModemManager (UID 0/root, PID 764/ModemManager)
What: sleep
 Why: ModemManager needs to reset devices
Mode: delay

 Who: NetworkManager (UID 0/root, PID 786/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: gdm (UID 121/gdm, PID 1122/gsd-media-keys)
What: sleep
 Why: GNOME handling keypresses
Mode: delay

 Who: damian (UID 1000/damian, PID 1696/gsd-media-keys)
What: sleep
 Why: GNOME handling keypresses
Mode: delay

 Who: UPower (UID 0/root, PID 1021/upowerd)
What: sleep
 Why: Pause device polling
Mode: delay

10 inhibitors listed.

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

Title:
  Laptop does not suspend after lid is closed on nvidia drivers

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

Bug description:
  System: Ubuntu 18.04 fresh install
  HW: Macbook Pro Retina 15"

  Settings in Tweak: Suspend on Lid closed

  The machine does not suspend after lid is closed

  syslog: ---
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 

[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]

[Shawn]

That file (/etc/gdm3/custom.conf) doesn't exist on my system.  I haven't
been getting the popup for an error occurring today though.  (The
details in that dialog said it was a duplicate of this issue, which is
how I found this)

I still have an issue where if I lock the screen it goes black with a
blinking _ in the upper left.  I can ssh in and reboot, but the UI is
unresponsive no matter how long I wait (even Ctrl+Shift+F1-6 key combos
do nothing).  I'm not sure that is related, but the 'system error has
occurred' dialog with this crash only happened after I did a reboot to
get out of this.  I'm going to do more debugging on this later this
afternoon.

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

[Desktop-packages] [Bug 1774680] [NEW] duplicity Errors 243

[Battant]

Public bug reported:

Hello,

Step to reproduce

lanch a backup with duplicity
Actuel result : At end of backup I get errror 243

See bellow

StartTime 1527856743.74 (Fri Jun  1 14:39:03 2018)
EndTime 1527861735.49 (Fri Jun  1 16:02:15 2018)
ElapsedTime 4991.75 (1 hour 23 minutes 11.75 seconds)
SourceFiles 4059374
SourceFileSize 204866697649 (191 GB)
NewFiles 2230168
NewFileSize 204851936827 (191 GB)
DeletedFiles 3
ChangedFiles 54
ChangedFileSize 1982347 (1.89 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 2230225
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 0 (0 bytes)
Errors 243

Note : during history my backup my I have several change my computer
name and my backup disk is full. In this case on mac os 10 time machine
simply delete to oldest version in the history and if you change your
mac or change the computer name you can merge the backup

Question : whith duplicity how could I merge all my backups and delete
oldest version when backup disk is full ?

What say Error 2423 ?

Thanks for your support

Best regards

Battant

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  1 18:54:07 2018
InstallationDate: Installed on 2018-04-29 (33 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup
 Importance: Undecided
 Status: New

** Affects: python
 Importance: Undecided
 Status: New

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


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

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

** No longer affects: duplicity

** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

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

Title:
  duplicity Errors 243

Status in Déjà Dup:
  New
Status in Python:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Hello,

  Step to reproduce

  lanch a backup with duplicity
  Actuel result : At end of backup I get errror 243

  See bellow

  StartTime 1527856743.74 (Fri Jun  1 14:39:03 2018)
  EndTime 1527861735.49 (Fri Jun  1 16:02:15 2018)
  ElapsedTime 4991.75 (1 hour 23 minutes 11.75 seconds)
  SourceFiles 4059374
  SourceFileSize 204866697649 (191 GB)
  NewFiles 2230168
  NewFileSize 204851936827 (191 GB)
  DeletedFiles 3
  ChangedFiles 54
  ChangedFileSize 1982347 (1.89 MB)
  ChangedDeltaSize 0 (0 bytes)
  DeltaEntries 2230225
  RawDeltaSize 0 (0 bytes)
  TotalDestinationSizeChange 0 (0 bytes)
  Errors 243

  Note : during history my backup my I have several change my computer
  name and my backup disk is full. In this case on mac os 10 time
  machine simply delete to oldest version in the history and if you
  change your mac or change the computer name you can merge the backup

  Question : whith duplicity how could I merge all my backups and delete
  oldest version when backup disk is full ?

  What say Error 2423 ?

  Thanks for your support

  Best regards

  Battant

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 18:54:07 2018
  InstallationDate: Installed on 2018-04-29 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1774680/+subscriptions

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

[Desktop-packages] [Bug 1774642] Re: cups sees Xerox Phaser 3330 but doesnot print

[Till Kamppeter]

To find out whether the Xerox driver is perhaps broken. Have you already
tried to configure your printer on USB but with a generic PCL or
PostScript driver?

Is it perhaps possible to use your printer in driverless mode? Run the
command

driverless

in a terminal window and post the output here. Does your printer appear
in the output?

While your printer is connected to the USB and turned on, run

ps auxwww | grep ippusbxd

in a terminal window and post the output here. Is an "ippusbxd" process
listed?

Please also follow the instructions in the section "USB printer" on
https://wiki.ubuntu.com/DebuggingPrintingProblems


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

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

Title:
  cups sees Xerox Phaser 3330 but doesnot print

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,

  I have Xerox Phaser 3330 with installed official drivers.Cups sees
  this usb printer, sends the job and says that the job is completed. In
  fact nothing happens.

  I connected to this printer through the network, it works. But
  unfortunately i need the usb connection.

  Could you help me with this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Jun  1 16:31:14 2018
  InstallationDate: Installed on 2017-09-08 (266 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: device for Xerox-Phaser-3330: 
usb://Xerox/Phaser%203330?serial=3385783140=1
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Xerox-Phaser-3330: Xerox Tuscany, 1.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (10 days ago)
  dmi.bios.date: 11/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1706
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M
  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.:bvr1706:bd11/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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

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

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

[Desktop-packages] [Bug 1751076] Re: Xorg freeze when use mpv or cheese.

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:
   
  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  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/+bug/1751076/+subscriptions

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Andrei Dragan]

Same here on 18.04

:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic
:~# dpkg -l|egrep 'network(-)?manager|openconnect|openvpn|gnome-shell'
ii  gnome-shell3.28.1-0ubuntu2  
   amd64graphical shell for the GNOME desktop
ii  gnome-shell-common 3.28.1-0ubuntu2  
   all  common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator 18.04.1  
   all  App indicators for GNOME Shell
ii  gnome-shell-extension-ubuntu-dock  0.9.1
   all  Ubuntu Dock for GNOME Shell
ii  libopenconnect5:amd64  7.08-3   
   amd64open client for Cisco AnyConnect VPN - shared library
ii  libproxy1-plugin-networkmanager:amd64  0.4.15-1 
   amd64automatic proxy configuration management library (Network 
Manager plugin)
ii  network-manager1.10.6-2ubuntu1  
   amd64network management framework (daemon and userspace tools)
ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1  
   all  NetworkManager configuration to enable connectivity checking
ii  network-manager-gnome  1.8.10-2ubuntu1  
   amd64network management framework (GNOME frontend)
ii  network-manager-openconnect1.2.4-1  
   amd64network management framework (OpenConnect plugin core)
ii  network-manager-openconnect-gnome  1.2.4-1  
   amd64network management framework (OpenConnect plugin GNOME GUI)
ii  network-manager-openvpn1.8.2-1  
   amd64network management framework (OpenVPN plugin core)
ii  network-manager-openvpn-gnome  1.8.2-1  
   amd64network management framework (OpenVPN plugin GNOME GUI)
ii  network-manager-pptp   1.2.6-1  
   amd64network management framework (PPTP plugin core)
ii  network-manager-pptp-gnome 1.2.6-1  
   amd64network management framework (PPTP plugin GNOME GUI)
ii  openconnect7.08-3   
   amd64open client for Cisco AnyConnect VPN
ii  openvpn2.4.4-2ubuntu1   
   amd64virtual private network daemon
:~# 


Jun  1 18:49:14 nn NetworkManager[1023]:   [1527868154.6931] 
vpn-connection[0x55aa60ba0520,33f5f8d3-f496-464b-bd25-70f8db84addf,"nnvpn",0]: 
Started the VPN service, PID 5561
Jun  1 18:49:14 nn NetworkManager[1023]:   [1527868154.7036] 
vpn-connection[0x55aa60ba0520,33f5f8d3-f496-464b-bd25-70f8db84addf,"nnvpn",0]: 
Saw the service appear; activating connection
Jun  1 18:49:14 nn gnome-shell[1733]: Invalid VPN service type (cannot find 
authentication binary)

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm 

[Desktop-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

[Scott Moser]

** Description changed:

  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows removing
  the suid bit.
  
  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.
  
  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags
  
  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)
+  * bug 1302192: capabilities not preserved on installation

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

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Released
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Fix Released
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)
   * bug 1302192: capabilities not preserved on installation

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

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

[Desktop-packages] [Bug 1302192] Re: capabilities not preserved on installation

[Scott Moser]

** Description changed:

  Ping is not longer setuid root and I have to ping as root:
  
  [~]$ ping kubuntu.org
  ping: icmp open socket: Operation not permitted
  [~]$ sudo ping kubuntu.org
  PING kubuntu.org (91.189.94.156) 56(84) bytes of data.
  64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 
time=52.2 ms
  --- kubuntu.org ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms
  [~]$
+ 
+ Related bugs:
+  bug 1313550: ping does not work as a normal user on trusty tarball cloud 
images.

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

Title:
  capabilities not preserved on installation

Status in attr package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in live-installer package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in attr source package in Trusty:
  Fix Released
Status in iputils source package in Trusty:
  Confirmed
Status in live-installer source package in Trusty:
  Fix Released
Status in ubiquity source package in Trusty:
  Fix Released

Bug description:
  Ping is not longer setuid root and I have to ping as root:

  [~]$ ping kubuntu.org
  ping: icmp open socket: Operation not permitted
  [~]$ sudo ping kubuntu.org
  PING kubuntu.org (91.189.94.156) 56(84) bytes of data.
  64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 
time=52.2 ms
  --- kubuntu.org ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms
  [~]$

  Related bugs:
   bug 1313550: ping does not work as a normal user on trusty tarball cloud 
images.

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

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

[Desktop-packages] [Bug 1774657] [NEW] I945G don't load

[Isidro]

Public bug reported:

After upgrade, the video card not load properly

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu May 31 17:11:21 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller 
[103c:3011]
MachineType: Hewlett-Packard HP Compaq dc7600 Small Form Factor
ProcEnviron:
 LANGUAGE=es_ES:en
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=a9e49865-59bc-44ce-818f-6b5b2e1c89fe ro quiet splash drm.debug=0xe 
nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2005
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786D1 v01.03
dmi.board.name: 09F8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: Thor
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D1v01.03:bd05/18/2005:svnHewlett-Packard:pnHPCompaqdc7600SmallFormFactor:pvr:rvnHewlett-Packard:rn09F8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc7600 Small Form Factor
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.4-0ubuntu0~18.04.1~ppa1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.4-0ubuntu0~18.04.1~ppa1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May 31 16:13:00 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9
 inputHP WMI hotkeys   KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: apport-bug bionic i386 third-party-packages ubuntu

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

Title:
  I945G don't load

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade, the video card not load properly

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 31 17:11:21 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:3011]
  MachineType: Hewlett-Packard HP Compaq dc7600 Small Form Factor
  ProcEnviron:
   LANGUAGE=es_ES:en
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=a9e49865-59bc-44ce-818f-6b5b2e1c89fe ro quiet splash drm.debug=0xe 
nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2005
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D1 v01.03
  dmi.board.name: 09F8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: Thor
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D1v01.03:bd05/18/2005:svnHewlett-Packard:pnHPCompaqdc7600SmallFormFactor:pvr:rvnHewlett-Packard:rn09F8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7600 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.4-0ubuntu0~18.04.1~ppa1
  

[Desktop-packages] [Bug 1774656] [NEW] Fake axes detected on 8bitdo pro controllers

[LogicalDash]

Public bug reported:

Both the FC30 Pro and the SN30 Pro are detected by Ubuntu, and are
usable insofar as all of the buttons and axes they do have are all
present. However, they both present a pair of axes that look like
pedals, but which aren't really on the controller. Instead, these axes
default to -32767 and flip to positive 32767 when some buttons are
pressed -- buttons that are already accounted for by some other input.

Axis 4 flips when I press right on the D-pad or the L2 button (button 8).
Axis 5 flips when I press left on the D-pad or the R2 button (button 9).
The controllers also appear to have 14 buttons, but I can only really press 12. 
Buttons 2 and 12 cannot be pressed. I thought these would be the Star and Home 
buttons, but pressing those does nothing, and these extra buttons are not 
present on the FC30 Pro.

It's sometimes possible to work around this with remapping, but the
inability to press button 8 without flipping axis 5 makes it impossible
to do this in an automated fashion; you have to use something like
xboxdrv on the command line, which requires sudo.

** Affects: xserver-xorg-input-evdev (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Both the FC30 Pro and the SN30 Pro are detected by Ubuntu, and are
  usable insofar as all of the buttons and axes they do have are all
  present. However, they both present a pair of axes that look like
  pedals, but which aren't really on the controller. Instead, these axes
  default to -32767 and flip to positive 32767 when some buttons are
  pressed -- buttons that are already accounted for by some other input.
  
  Axis 4 flips when I press right on the D-pad or the L2 button (button 8).
- Axis 5 flips when I press left on the D-pad or the R2 button (button 9). 
+ Axis 5 flips when I press left on the D-pad or the R2 button (button 9).
  The controllers also appear to have 14 buttons, but I can only really press 
12. Buttons 2 and 12 cannot be pressed. I thought these would be the Star and 
Home buttons, but pressing those does nothing, and these extra buttons are not 
present on the FC30 Pro.
  
  It's sometimes possible to work around this with remapping, but the
- impossibility of pressing R2 without flipping axis 5 makes it impossible
- to do this in an automated fashion; you have to use something like
- xboxdrv, which requires sudo.
+ impossibility of pressing button 8 without flipping axis 5 makes it
+ impossible to do this in an automated fashion; you have to use something
+ like xboxdrv, which requires sudo.

** Description changed:

  Both the FC30 Pro and the SN30 Pro are detected by Ubuntu, and are
  usable insofar as all of the buttons and axes they do have are all
  present. However, they both present a pair of axes that look like
  pedals, but which aren't really on the controller. Instead, these axes
  default to -32767 and flip to positive 32767 when some buttons are
  pressed -- buttons that are already accounted for by some other input.
  
  Axis 4 flips when I press right on the D-pad or the L2 button (button 8).
  Axis 5 flips when I press left on the D-pad or the R2 button (button 9).
  The controllers also appear to have 14 buttons, but I can only really press 
12. Buttons 2 and 12 cannot be pressed. I thought these would be the Star and 
Home buttons, but pressing those does nothing, and these extra buttons are not 
present on the FC30 Pro.
  
  It's sometimes possible to work around this with remapping, but the
  impossibility of pressing button 8 without flipping axis 5 makes it
  impossible to do this in an automated fashion; you have to use something
- like xboxdrv, which requires sudo.
+ like xboxdrv on the command line, which requires sudo.

** Description changed:

  Both the FC30 Pro and the SN30 Pro are detected by Ubuntu, and are
  usable insofar as all of the buttons and axes they do have are all
  present. However, they both present a pair of axes that look like
  pedals, but which aren't really on the controller. Instead, these axes
  default to -32767 and flip to positive 32767 when some buttons are
  pressed -- buttons that are already accounted for by some other input.
  
  Axis 4 flips when I press right on the D-pad or the L2 button (button 8).
  Axis 5 flips when I press left on the D-pad or the R2 button (button 9).
  The controllers also appear to have 14 buttons, but I can only really press 
12. Buttons 2 and 12 cannot be pressed. I thought these would be the Star and 
Home buttons, but pressing those does nothing, and these extra buttons are not 
present on the FC30 Pro.
  
  It's sometimes possible to work around this with remapping, but the
- impossibility of pressing button 8 without flipping axis 5 makes it
- impossible to do this in an automated fashion; you have to use something
- like xboxdrv on the command line, which requires sudo.
+ inability to press button 8 without flipping axis 5 makes it impossible
+ to do this in an automated fashion; you 

[Desktop-packages] [Bug 1774652] Re: xorg stopped responding to keyboard. Killing xorg "fixed" it

[Launchpad Bug Tracker]

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

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

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

Title:
  xorg stopped responding to keyboard. Killing xorg "fixed" it

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I booted Ubuntu, and when I started using it, nothing would respond to the 
keyboard. Everything was responding normally to the mouse.
  It looked like the keystrokes were being "buffered" extremely slowly, I'll 
explain:

  For example, I opened Chrome and I started typing "facebook" in the
  address bar, but no character showed up, as if the keyboard wasn't
  even connected (however, I had used the same keyboard to type my
  password to log in and that had worked).

  So I opened a terminal, and then the characters "fa" showed up on the
  command line: that is two of the several characters that I had typed
  almost a minute before into another application.

  Then I started hitting keys randomly on my keyboard, like "lksjdbljb",
  and opening several applications (e.g. open Thunderbird, click "new
  message" - remember, the mouse was responding - and type random
  characters into the "to" address). With several seconds of delay, some
  other random characters that I had typed minutes before in another app
  would show up.

  That is, keyboard totally unusable, as if the keystroke buffer was
  slow. And this would happen with both the laptop's builtin keyboard
  and the external one connected via USB.

  
  I hit Ctrl+Alt+F1 (which responded immediately) to open a virtual terminal. I 
logged in on the virtual terminal, where the keyboard(s) would respond 
perfectly.
  I ran "top", and there was no process consuming an abnormal amount of CPU.

  I tried killing the "at-spi2-registr" process which was second in the
  list with like 2% CPU consumption and had caused me problems before
  (see #1772109), but that didn't help (I switched back to my xorg
  session via ctrl+alt+f7 and the keyboard was still berserk there).

  So finally I killed xorg, which obviously logged me out, and after I
  logged back in everything was working normally.

  
  About half of the fucking times I boot or reboot, the system is unusable due 
to some bug like this. Now this is a new one. Fucking pathetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun  1 15:59:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (1693 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  

[Desktop-packages] [Bug 1774652] [NEW] xorg stopped responding to keyboard. Killing xorg "fixed" it

[teo1978]

Public bug reported:

I booted Ubuntu, and when I started using it, nothing would respond to the 
keyboard. Everything was responding normally to the mouse.
It looked like the keystrokes were being "buffered" extremely slowly, I'll 
explain:

For example, I opened Chrome and I started typing "facebook" in the
address bar, but no character showed up, as if the keyboard wasn't even
connected (however, I had used the same keyboard to type my password to
log in and that had worked).

So I opened a terminal, and then the characters "fa" showed up on the
command line: that is two of the several characters that I had typed
almost a minute before into another application.

Then I started hitting keys randomly on my keyboard, like "lksjdbljb",
and opening several applications (e.g. open Thunderbird, click "new
message" - remember, the mouse was responding - and type random
characters into the "to" address). With several seconds of delay, some
other random characters that I had typed minutes before in another app
would show up.

That is, keyboard totally unusable, as if the keystroke buffer was slow.
And this would happen with both the laptop's builtin keyboard and the
external one connected via USB.


I hit Ctrl+Alt+F1 (which responded immediately) to open a virtual terminal. I 
logged in on the virtual terminal, where the keyboard(s) would respond 
perfectly.
I ran "top", and there was no process consuming an abnormal amount of CPU.

I tried killing the "at-spi2-registr" process which was second in the
list with like 2% CPU consumption and had caused me problems before (see
#1772109), but that didn't help (I switched back to my xorg session via
ctrl+alt+f7 and the keyboard was still berserk there).

So finally I killed xorg, which obviously logged me out, and after I
logged back in everything was working normally.


About half of the fucking times I boot or reboot, the system is unusable due to 
some bug like this. Now this is a new one. Fucking pathetic.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jun  1 15:59:54 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (1693 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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: 

[Desktop-packages] [Bug 1774642] [NEW] cups sees Xerox Phaser 3330 but doesnot print

[RCV]

Public bug reported:

Hey,

I have Xerox Phaser 3330 with installed official drivers.Cups sees this
usb printer, sends the job and says that the job is completed. In fact
nothing happens.

I connected to this printer through the network, it works. But
unfortunately i need the usb connection.

Could you help me with this?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Jun  1 16:31:14 2018
InstallationDate: Installed on 2017-09-08 (266 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lpstat: device for Xerox-Phaser-3330: 
usb://Xerox/Phaser%203330?serial=3385783140=1
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: Xerox-Phaser-3330: Xerox Tuscany, 1.0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2018-05-22 (10 days ago)
dmi.bios.date: 11/26/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1706
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88TD-M
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.:bvr1706:bd11/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
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

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


** Tags: amd64 apparmor apport-bug bionic

** Description changed:

  Hey,
  
  I have Xerox Phaser 3330 with installed official drivers.Cups sees this
  usb printer, sends the job and says that the job is completed. In fact
  nothing happens.
+ 
+ I connected to this printer through the network, it works. But
+ unfortunately i need the usb connection.
  
  Could you help me with this?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Jun  1 16:31:14 2018
  InstallationDate: Installed on 2017-09-08 (266 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: device for Xerox-Phaser-3330: 
usb://Xerox/Phaser%203330?serial=3385783140=1
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Xerox-Phaser-3330: Xerox Tuscany, 1.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (10 days ago)
  dmi.bios.date: 11/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1706
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M
  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.:bvr1706:bd11/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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

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

Title:
  cups sees Xerox Phaser 3330 but doesnot print

Status in cups package in Ubuntu:
  New

Bug description:
  Hey,

  I have Xerox Phaser 3330 with installed official drivers.Cups sees
  this usb printer, sends the job and says that the job is completed. In
  fact nothing happens.

  I connected to this printer through the network, it works. But
  unfortunately i need the usb connection.

  Could you help me with this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Jun  1 16:31:14 2018
  InstallationDate: Installed on 2017-09-08 (266 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 

[Desktop-packages] [Bug 1687505] Re: /usr/bin/simple-scan:11:_IO_new_fclose:sane_genesys_cancel:scanner_close_device:scanner_handle_requests:scanner_scan_thread

[Launchpad Bug Tracker]

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

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/simple-
  
scan:11:_IO_new_fclose:sane_genesys_cancel:scanner_close_device:scanner_handle_requests:scanner_scan_thread

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
simple-scan.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/937053fb85cbf2a4ef19c8bd0ed3b06ea42a5a4f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774188] Re: unlocking the screen takes 5 seconds

[Götz Waschk]

** Attachment added: "journalctl -b"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+attachment/5147385/+files/journal.txt

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

Title:
  unlocking the  screen takes 5 seconds

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755106] /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/

[Péter Prőhle]

The problem is much more frequent in the last few days.

What shall I test or record if this problem occures next?

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

Re: [Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[Ron McIlvaine]

I left gnome.

A servant of the Most High God,

Ron McIlvaine

On Fri, Jun 1, 2018, 5:05 AM Timo Aaltonen  wrote:

> Hello Felix, or anyone else affected,
>
> Accepted cups-pk-helper into bionic-proposed. The package will build now
> and be available at https://launchpad.net/ubuntu/+source/cups-pk-
> helper/0.2.6-1ubuntu1.1
>  in
> a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: cups-pk-helper (Ubuntu Bionic)
>Status: Triaged => Fix Committed
>
> ** Tags added: verification-needed verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/934291
>
> Title:
>   Deleting or stopping print jobs does not work
>
> Status in gnome-control-center:
>   Unknown
> Status in cups-pk-helper package in Ubuntu:
>   Fix Released
> Status in cups-pk-helper source package in Bionic:
>   Fix Committed
>
> Bug description:
>   Deleting or stopping print jobs through the "gnome-control-center ->
> printers" menu is not possible.
>   (Black rectangle for stopping can be pressed, nothing happens.)
>
>   Deleting with cups via webinterface does work. ( http://localhost:631/
>   )
>
>   Please let me know which information to provide.
>
>   Cheers
>
>
>   [Impact]
>
>   The most intuitive way for users to maintain printers and look after
>   print jobs is the printing part of the GNOME Control Center. As this
>   tool makes use of cups-pk-helper for authentication, a lot of its
>   functionality is not working dur to the non-working in cups-pk-helper
>   package.
>
>   This way a key functionality in Ubuntu Desktop is not working which
>   may people turn away from Linux on the desktop.
>
>   [Test Case]
>
>   Do job operations (remove, move to other printer, ...) with print jobs
>   using the printing tool of GNOME Control Center ("Devices" ->
>   "Printers"). You will see that most or all of these operations do not
>   work.
>
>   They will work after installing this update.
>
>   [Regression Potential]
>
>   cups-pk-helper is only used by some graphical user interfaces for
>   printer operations, like the mentioned GNOME tool. It does not impact
>   printing itself, CUPS command line operations, or the CUPS web admin
>   interface.
>
>   Also the changes on cups-pk-helper are not done in its code or its way
>   how it works but only in its configuration (using a system user).
>
>   This way the regression potential is low.
>
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 11.10
>   Package: gnome-control-center 1:3.2.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
>   Uname: Linux 3.0.0-16-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 1.23-0ubuntu4
>   Architecture: amd64
>   Date: Fri Feb 17 16:47:32 2012
>   InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64
> (20100429)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
>   usr_lib_gnome-control-center:
>deja-dup   22.0~bzr1290.37~oneiric1
>gnome-bluetooth3.2.0-0ubuntu2
>indicator-datetime 0.3.1-0ubuntu1.1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions
>

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

Title:
  Deleting or stopping print jobs does not work

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

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

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

  Please let me know which information to provide.

  Cheers

  
  [Impact]

  The most intuitive way for users to maintain printers and look after
  print jobs is the 

[Desktop-packages] [Bug 1774597] Re: G-C-C privacy option don't allow sending manual report

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu5

---
gnome-control-center (1:3.28.1-0ubuntu5) cosmic; urgency=medium

  * debian/{gbp.conf,control{,.in}}: Added and updated for Ubuntu
  * debian/patches/privacy-panel-whoopsie.patch:
- display and enable correct section of error reporting mode
  (never/manual/auto) (LP: #1774597)

 -- Didier Roche   Thu, 31 May 2018 17:21:59 +0200

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

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

Title:
  G-C-C privacy option don't allow sending manual report

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  New

Bug description:
  [ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely 
and not providing any graĥical way to set manual reports (which is our default 
on 18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is 
linked to sending error report: opt-in -> automated report is set; opt-out -> 
no report is set. We need a way to represent those 3 states of error reporting:
 - never
 - manual
 - auto
   
  [ Test Case ]
* Install new gnome-control-center version, go to the privacy panel
* Click on the error reporting line
* In the model window, play with the switch and toggle, and check in d-feet 
the whoopsie state. Basically you can't adapt error reporting mode 
(manual/auto) if you decided to not report error mode.
* Check as well that the main UI toggles between "never/manual/auto"

  [ Regression potential ]
* This code would affect the privacy g-c-c panel.
* Note that we have 3 new strings to translate ("never" is already 
translated in G-C-C). Those are:
  - "Send error reports to Canonical"
  - "Send reports automatically"
  - "Show a dialog for each error before reporting"

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

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[Timo Aaltonen]

Hello Felix, or anyone else affected,

Accepted cups-pk-helper into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cups-pk-
helper/0.2.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cups-pk-helper (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Deleting or stopping print jobs does not work

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

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

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

  Please let me know which information to provide.

  Cheers

  
  [Impact]

  The most intuitive way for users to maintain printers and look after
  print jobs is the printing part of the GNOME Control Center. As this
  tool makes use of cups-pk-helper for authentication, a lot of its
  functionality is not working dur to the non-working in cups-pk-helper
  package.

  This way a key functionality in Ubuntu Desktop is not working which
  may people turn away from Linux on the desktop.

  [Test Case]

  Do job operations (remove, move to other printer, ...) with print jobs
  using the printing tool of GNOME Control Center ("Devices" ->
  "Printers"). You will see that most or all of these operations do not
  work.

  They will work after installing this update.

  [Regression Potential]

  cups-pk-helper is only used by some graphical user interfaces for
  printer operations, like the mentioned GNOME tool. It does not impact
  printing itself, CUPS command line operations, or the CUPS web admin
  interface.

  Also the changes on cups-pk-helper are not done in its code or its way
  how it works but only in its configuration (using a system user).

  This way the regression potential is low.

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

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

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

[Desktop-packages] [Bug 1774601] [NEW] gio trash (or gvfs-trash) on a vboxsf partition fails with "Unable to find or create trash directory"

[Jon "The Nice Guy" Spriggs]

Public bug reported:

I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu-
mate-desktop tasksel applied to it. I mount a filesystem from the
Virtualbox Host using this line in /etc/fstab:

HostHome /HostHome vboxsf
_netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0

With this build, I have installed the atom snap package, and when I try
to remove a file from the file tree, I get an error saying:

The following file couldn't be moved to the trash.
/HostHome/Documents/01 
Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry
Is gvfs-trash installed?

On further investigation, I found that while gvfs-trash is installed
(via the gvfs-common package), it has been depreciated, preferring gio.
Running either `gio trash` or `gvfs-trash` specifying that path
(`/HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-
Machine/ansible_users.retry`) returns this report:

gio: file:///HostHome/Documents/01%20Projects/K5-Ansible-Openstack-
Development-Machine/ansible_users.retry: Unable to find or create trash
directory for /HostHome/Documents/01 Projects/K5-Ansible-Openstack-
Development-Machine/ansible_users.retry

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libglib2.0-bin 2.56.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Jun  1 08:26:04 2018
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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


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

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

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

Title:
  gio trash (or gvfs-trash) on a vboxsf partition fails with "Unable to
  find or create trash directory"

Status in glib2.0 package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu-
  mate-desktop tasksel applied to it. I mount a filesystem from the
  Virtualbox Host using this line in /etc/fstab:

  HostHome /HostHome vboxsf
  _netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0

  With this build, I have installed the atom snap package, and when I
  try to remove a file from the file tree, I get an error saying:

  The following file couldn't be moved to the trash.
  /HostHome/Documents/01 
Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry
  Is gvfs-trash installed?

  On further investigation, I found that while gvfs-trash is installed
  (via the gvfs-common package), it has been depreciated, preferring
  gio. Running either `gio trash` or `gvfs-trash` specifying that path
  (`/HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-
  Machine/ansible_users.retry`) returns this report:

  gio: file:///HostHome/Documents/01%20Projects/K5-Ansible-
  Openstack-Development-Machine/ansible_users.retry: Unable to find or
  create trash directory for /HostHome/Documents/01 Projects/K5-Ansible-
  Openstack-Development-Machine/ansible_users.retry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-bin 2.56.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun  1 08:26:04 2018
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 196785]

[TerryG]

http://love.hearofm.com
Terry Galati

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

Title:
  'sh' syntax highlighting actually for bash, and uses syntax invalid
  for Bourne shell

Status in GtkSourceView:
  Won't Fix
Status in gtksourceview2 package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gedit

  Gedit's syntax highlighting for 'sh' actually is for bash.

  Functions and arrays are not valid Bourne shell, and scripts starting with 
'/bin/sh' which use these will fail on:
  * Bourne shell (/bin/sh)
  * Bash version 3 and later on many systems, depending on the compile time 
options of bash. If bash version 3's default POSIX compatibility has been 
disabled, the behavior may be demonstrated using 'bash --posix file.sh'

  Simple fix: mark the syntax highlighting currently labeled as 'sh' as
  being 'bash'.

  Extended fix: include an actual Bourne shell syntax highlighting mode,
  which marks invalid bourne shell syntax in red.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Feb 29 09:39:52 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.21.2-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  Uname: Linux 2.6.24-10-generic i686

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

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

[Desktop-packages] [Bug 1773369] Re: Editors picks are random

[Will Cooke]

** Summary changed:

- Editors pics are random
+ Editors picks are random

** Changed in: gnome-software (Ubuntu)
 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/1773369

Title:
  Editors picks are random

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  In GNOME Software the editors picks are showing 10 of however many are
  tagged in the store as 'featured'. However the list is randomized. I
  believe we agreed not to randomize this list, but keep the list the
  same so we can effectively measure the benefit of being in slot 1 vs
  slot 10 (for example).

  Indeed in bug 1705953 and bug 1705953 we make reference to
  debian/patches/0048-Don-t-randomize-editors-picks.patch which suggests
  we should indeed not randomize the editors picks, but this doesn't
  appear to be working.

  Attached is a screenshot showing the current selection. However the
  list is as follows:-

  zenkit
  notepadqq
  vscode
  gravit-designer
  eclipse
  sublime-text
  noson
  hugo
  signal-desktop
  audovia
  corsixth
  zulip
  cloudtag
  discrographer
  htop
  ao
  codenamelt
  bitwarden
  mosquitto
  wekan
  nextcloud
  docker
  canonical-livepatch
  hiri

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

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

[Desktop-packages] [Bug 1774597] [NEW] G-C-C privacy option don't allow sending manual report

[Didier Roche]

Public bug reported:

[ Impact ]
  * The current label "Manual" is in fact shutting down whoopsie completely and 
not providing any graĥical way to set manual reports (which is our default on 
18.04)
  * We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is 
linked to sending error report: opt-in -> automated report is set; opt-out -> 
no report is set. We need a way to represent those 3 states of error reporting:
   - never
   - manual
   - auto
 
[ Test Case ]
  * Install new gnome-control-center version, go to the privacy panel
  * Click on the error reporting line
  * In the model window, play with the switch and toggle, and check in d-feet 
the whoopsie state. Basically you can't adapt error reporting mode 
(manual/auto) if you decided to not report error mode.
  * Check as well that the main UI toggles between "never/manual/auto"

[ Regression potential ]
  * This code would affect the privacy g-c-c panel.
  * Note that we have 3 new strings to translate ("never" is already translated 
in G-C-C). Those are:
- "Send error reports to Canonical"
- "Send reports automatically"
- "Show a dialog for each error before reporting"

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

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

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

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

Title:
  G-C-C privacy option don't allow sending manual report

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

Bug description:
  [ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely 
and not providing any graĥical way to set manual reports (which is our default 
on 18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is 
linked to sending error report: opt-in -> automated report is set; opt-out -> 
no report is set. We need a way to represent those 3 states of error reporting:
 - never
 - manual
 - auto
   
  [ Test Case ]
* Install new gnome-control-center version, go to the privacy panel
* Click on the error reporting line
* In the model window, play with the switch and toggle, and check in d-feet 
the whoopsie state. Basically you can't adapt error reporting mode 
(manual/auto) if you decided to not report error mode.
* Check as well that the main UI toggles between "never/manual/auto"

  [ Regression potential ]
* This code would affect the privacy g-c-c panel.
* Note that we have 3 new strings to translate ("never" is already 
translated in G-C-C). Those are:
  - "Send error reports to Canonical"
  - "Send reports automatically"
  - "Show a dialog for each error before reporting"

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

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

[Desktop-packages] [Bug 1774585] Re: Xwayland() crashed with signal 7 from XkbComputeGetMapReplySize() from ProcXkbGetMap() from Dispatch() from dix_main() from __libc_start_main()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/Xwayland:7:XkbComputeGetMapReplySize:ProcXkbGetMap:Dispatch:dix_main:__libc_start_main
+ Xwayland() crashed with signal 7 from XkbComputeGetMapReplySize() from 
ProcXkbGetMap() from Dispatch() from dix_main() from __libc_start_main()

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

Title:
  Xwayland() crashed with signal 7 from XkbComputeGetMapReplySize() from
  ProcXkbGetMap() from Dispatch() from dix_main() from
  __libc_start_main()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/3bc4dcdb404e900753261bcb9161a176755262c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1758651] Re: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

[Daniel van Vugt]

Tracking in:
https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970

** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970
+ 
+ ---
+ 
  Waking up my laptop from suspend, the whole gnome session and Xwayland
  crashed. After that gdm3 prompted me to login again. This is the first
  time this happened to me.
  
  (It's nice that even crashing it did it gracefully letting me log in
  again.)
  
  Related to bug #1758650 - https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1758650
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 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-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 25 15:00:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.15.0-12-generic, x86_64: installed
-  bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
+  bbswitch, 0.8, 4.15.0-12-generic, x86_64: installed
+  bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
-  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
-Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
+  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
+    Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2017-08-21 (215 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. 
-  Bus 001 Device 024: ID 13d3:3408 IMC Networks 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp.
+  Bus 001 Device 024: ID 13d3:3408 IMC Networks
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
-  mieqProcessDeviceEvent ()
-  ?? ()
-  ?? ()
-  ?? ()
-  __libc_start_main (main=0x557037a1baa0, argc=12, argv=0x7fff0eccf928, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff0eccf918) at ../csu/libc-start.c:310
+  mieqProcessDeviceEvent ()
+  ?? ()
+  ?? ()
+  ?? ()
+  __libc_start_main (main=0x557037a1baa0, argc=12, argv=0x7fff0eccf928, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff0eccf918) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Feb 15 20:44:12 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 

[Desktop-packages] [Bug 1774505] Re: OSD for volume/brightness should only appear on main display

[Daniel van Vugt]

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/327
+ 
+ ---
+ 
  When watching a movie on an external display it's often useful to adjust
  the volume. Currently gnome-shell will display the OSD on both displays
  creating an overlay over the video. Unity would only display on the
  screen of the app used at the moment. Ideally it would just always show
  up on the main display so that you can keep focus on the video app for
  other keybindings to still work. I tried searching for an extension to
  do this but couldn't find one.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 22:00:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1774505

Title:
  OSD for volume/brightness should only appear on main display

Status in gnome-shell package in Ubuntu:
  New

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

  ---

  When watching a movie on an external display it's often useful to
  adjust the volume. Currently gnome-shell will display the OSD on both
  displays creating an overlay over the video. Unity would only display
  on the screen of the app used at the moment. Ideally it would just
  always show up on the main display so that you can keep focus on the
  video app for other keybindings to still work. I tried searching for
  an extension to do this but couldn't find one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 22:00:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1774586] Re: /usr/bin/Xwayland:7:mieqProcessDeviceEvent:ProcXTestFakeInput:Dispatch:dix_main:__libc_start_main

[Daniel van Vugt]

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

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

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

Title:
  
/usr/bin/Xwayland:7:mieqProcessDeviceEvent:ProcXTestFakeInput:Dispatch:dix_main:__libc_start_main

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen

[Daniel van Vugt]

Yes, upstream requires bug reports from someone who experiences the bug.

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

Title:
  Personal scaling settings not used on the unlock screen

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I run my screen on 100% scaling even though the ubuntu default for my
  2560x1440 screen is 200%. After resume from suspend it's common for
  GDM to display at 200% and only after switch back to 100%. Sometimes
  this extends to after unlock with the mouse cursor being double size
  but only when hovering over the gnome shell top bar. I tried taking a
  screenshot but running the screenshot app fixed it and the cursor was
  normal sized again.

  I've now submitted or subscribed to several gnome-shell and gdm3 bugs.
  The 18.04 transition from unity to gnome-shell was clearly a step back
  in terms of polish of the desktop.

  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: Wed May 30 13:21:49 2018
  InstallationDate: Installed on 2016-10-27 (579 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

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

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

[Desktop-packages] [Bug 1774505] Re: OSD for volume/brightness should only appear on main display

[Pedro Côrte-Real]

Submitted here:

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

I mentioned it here because this is a regression for me compared to
Unity on 16.04.

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

Title:
  OSD for volume/brightness should only appear on main display

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When watching a movie on an external display it's often useful to
  adjust the volume. Currently gnome-shell will display the OSD on both
  displays creating an overlay over the video. Unity would only display
  on the screen of the app used at the moment. Ideally it would just
  always show up on the main display so that you can keep focus on the
  video app for other keybindings to still work. I tried searching for
  an extension to do this but couldn't find one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 22:00:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Netziro]

Same problem here in Kubuntu 18.04.
The authentication layer works fine, but for some reason it fails in 
configuring the network.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connection to open or WPA secured wifi works without any issues.
  Connection to WPA2/PEAP fails. Repeatedly asks for username/password.

  Possible gnome-shell integration issue.

  The system was updated from Xenial to Bionic in mid-January. At that
  time this WPA2/PEAP setup worked without any issues. With the updates
  coming in the last week of January / First February week - the bug was
  experienced.

  1)
  ➜  syncthing git:(master) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) - up to date packages
  [code]
  ➜  cat /etc/apt/sources.list |egrep -v '^#'
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
  deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main 
universe restricted
  [/code]

  Note:
  # some pkg version related to problem might be from proposed-updates repo

  2b)
  [code]
  dpkg -l |egrep -i 'network manager|networkm|libnm'
  ii  gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm-glib/libnm-util library
  ii  gir1.2-nm-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm library
  ii  gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1
amd64GObject introspection data for 
libnm-gtk
  ii  libnm-glib-vpn1:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib VPN shared library)
  ii  libnm-glib4:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib shared library)
  ii  libnm-gtk0:amd64   1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm-glib version)
  ii  libnm-util2:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(shared library)
  ii  libnm0:amd64   1.8.4-1ubuntu4 
amd64GObject-based client library 
for NetworkManager
  ii  libnma0:amd64  1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm version)
  ii  libproxy1-plugin-networkmanager:amd64  0.4.15-0ubuntu1
amd64automatic proxy configuration 
management library (Network Manager plugin)
  ii  network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 
all  NetworkManager configuration 
to enable connectivity checking
  ii  strongswan-nm  5.6.1-2ubuntu1 
amd64strongSwan plugin to interact 
with NetworkManager

  ii  wpasupplicant  2:2.6-15ubuntu2
  amd64client support for WPA and WPA2 (IEEE 802.11i)

  [/code]

  3,4)
  Connection to open or WPA secured wifi works withou any issues. Connection to 
WPA2/PLEAP (without cert, just with username/password fails). Although wifi 
layer get's is associated the client (network-manager) possibly due to bug 
deauthenticate itself without establishing an IP connection.

  Connect to network.

  5)
  Logs (syslog/kernel)

  Core moments:

  [code]
  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9125] 
keyfile: update /etc/NetworkManager/system-connections/WiFi 
(82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi")
  Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 
'G_VALUE_HOLDS_STRING (value)' failed

  and ...

  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9450] 
device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and 
secrets exist.  No new secrets needed.
  Feb 12 09:19:02 

[Desktop-packages] [Bug 1774587] [NEW] /usr/bin/nautilus:free(): invalid pointer

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic cosmic kylin-18.04

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

Title:
  /usr/bin/nautilus:free(): invalid pointer

Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774586] [NEW] /usr/bin/Xwayland:7:mieqProcessDeviceEvent:ProcXTestFakeInput:Dispatch:dix_main:__libc_start_main

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic cosmic kylin-18.04

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

Title:
  
/usr/bin/Xwayland:7:mieqProcessDeviceEvent:ProcXTestFakeInput:Dispatch:dix_main:__libc_start_main

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774585] [NEW] /usr/bin/Xwayland:7:XkbComputeGetMapReplySize:ProcXkbGetMap:Dispatch:dix_main:__libc_start_main

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/3bc4dcdb404e900753261bcb9161a176755262c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic cosmic kylin-18.04

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

Title:
  
/usr/bin/Xwayland:7:XkbComputeGetMapReplySize:ProcXkbGetMap:Dispatch:dix_main:__libc_start_main

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/3bc4dcdb404e900753261bcb9161a176755262c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774588] [NEW] /usr/bin/nautilus:malloc(): memory corruption (fast)

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic cosmic kylin-18.04

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

Title:
  /usr/bin/nautilus:malloc(): memory corruption (fast)

Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen

[Pedro Côrte-Real]

This is not the same bug. I can't reproduce it anymore since gdm is no
longer slow on resume. But is it really Ubuntu process to have the user
submit bug reports upstream?

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

Title:
  Personal scaling settings not used on the unlock screen

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I run my screen on 100% scaling even though the ubuntu default for my
  2560x1440 screen is 200%. After resume from suspend it's common for
  GDM to display at 200% and only after switch back to 100%. Sometimes
  this extends to after unlock with the mouse cursor being double size
  but only when hovering over the gnome shell top bar. I tried taking a
  screenshot but running the screenshot app fixed it and the cursor was
  normal sized again.

  I've now submitted or subscribed to several gnome-shell and gdm3 bugs.
  The 18.04 transition from unity to gnome-shell was clearly a step back
  in terms of polish of the desktop.

  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: Wed May 30 13:21:49 2018
  InstallationDate: Installed on 2016-10-27 (579 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

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

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

[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on virtual desktop change

[Pedro Côrte-Real]

This is really easy to reproduce. Just arrange your screens so your
external screen is above the internal one instead of to the left or
right. Now when you switch virtual desktops the contents are moved
through the external screen.

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

Title:
  Windows flash by external screen on virtual desktop change

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-shell has the very interesting default of only doing virtual
  desktops on the internal screen. This works fine but has a strange
  visual glitch when changing virtual desktops where the contents of the
  internal screen flash through the external one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 21:06:47 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1774447] Re: Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04

[Daniel van Vugt]

OK. You appear to be using the synaptics touchpad driver (which is
expected in Xorg sessions after an upgrade).

I will move this bug to the synaptics driver.

In the meantime you can switch to using libinput by removing synaptics:

  sudo apt remove xserver-xorg-input-synaptics

** Package changed: libinput (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Incomplete => New

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

Title:
  Approx. 50% of tap to clicks does not work since upgrade to Ubuntu
  18.04

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Since upgrade from Ubuntu 17.10 to Ubuntu 18.04 I have issues with tap
  to click. Approximately 50% of taps does not work as clicks. I do not
  know if it is general issue or an issue related to my HW (Lenovo L450)
  but it is very annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.10.4-1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 17:38:44 2018
  DistUpgraded: 2018-05-04 10:19:30,946 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:503c]
  InstallationDate: Installed on 2015-10-05 (968 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20DT0003XS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=0ff426ff-3b6c-433c-81a3-8a8a4116c973 ro
  SourcePackage: libinput
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (27 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET57WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET57WW(1.19):bd03/16/2016:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L450
  dmi.product.name: 20DT0003XS
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  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.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: Sat Jan 20 21:06:39 2018
  xserver.configfile: default
  xserver.errors:
   Error loading keymap /var/lib/xkb/server-0.xkm
   Error loading keymap /var/lib/xkb/server-0.xkm
   XKB: Failed to load keymap. Loading default keymap instead.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.19.3-1ubuntu1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1774447/+subscriptions

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

[Desktop-packages] [Bug 1774447] [NEW] Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Since upgrade from Ubuntu 17.10 to Ubuntu 18.04 I have issues with tap
to click. Approximately 50% of taps does not work as clicks. I do not
know if it is general issue or an issue related to my HW (Lenovo L450)
but it is very annoying.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libinput10 1.10.4-1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 31 17:38:44 2018
DistUpgraded: 2018-05-04 10:19:30,946 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:503c]
InstallationDate: Installed on 2015-10-05 (968 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20DT0003XS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=0ff426ff-3b6c-433c-81a3-8a8a4116c973 ro
SourcePackage: libinput
UpgradeStatus: Upgraded to bionic on 2018-05-04 (27 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: JDET57WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJDET57WW(1.19):bd03/16/2016:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L450
dmi.product.name: 20DT0003XS
dmi.product.version: ThinkPad L450
dmi.sys.vendor: LENOVO
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.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: Sat Jan 20 21:06:39 2018
xserver.configfile: default
xserver.errors:
 Error loading keymap /var/lib/xkb/server-0.xkm
 Error loading keymap /var/lib/xkb/server-0.xkm
 XKB: Failed to load keymap. Loading default keymap instead.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1094 
 vendor LGD
xserver.version: 2:1.19.3-1ubuntu1.3

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic noclick ubuntu
-- 
Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04
https://bugs.launchpad.net/bugs/1774447
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.

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

[Desktop-packages] [Bug 1717300] Re: gnome-keyring -ssh silently start and conflict with ssh-agent

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-keyring -ssh silently start and conflict with ssh-agent

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  According to /etc/xdg/autostart/gnome-keyring-ssh.desktop gnome-keyring 
launchers are visible in OnlyShowIn=GNOME;Unity;MATE;. I use Cinnamon and under 
Cinnamon gnome-keyring is not visible in the autostart menu. But it's started 
hidden ad steal SSH_AUTH_SOCK from the ssh_agent. And this creates confusion 
problems, because gnome-keyring don't support ECDSA and ED25519. And there was 
hard to investigate where this gnome-keyring was launched to switch it off.
  The problem script is from Ubuntu, perhaps
  /usr/share/upstart/sessions/gnome-keyring-ssh.conf
  There is a check of running ssh-agent, [ -z "$SSH_AUTH_SOCK" ], but obviously 
it don't work.

  What is needed to do is if gnome-keyring is running in any windows
  manager, thus it must be visible in any, thus anyone shall can quickly
  switch it off, if this will be needed. Or don't run where it is not
  visible as autostart application.

  Workaround is to copy file /etc/xdg/autostart/gnome-keyring-
  ssh.desktop to the user homedir, delete "OnlyShowIn=GNOME;Unity;MATE;"
  with any text editor in this file and switch it off later. Now all
  work fine.

  Ubuntu 17.04, gnome-keyring 3.20.0-3ubuntu2.

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

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